<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>The precedence is Diversion > PAI > RPID > FROM since
in a forwarded call the original legs PAI/RPID/FROM can be
retained but the diversion would indicate a change in originator.</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 9/21/2018 7:41 AM, Pete Eisengrein
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAHm=SaJ9hoicw6WNLk765QGMK3EOT_jorbqoO4JnUPiZQhtPpw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="ltr">As mentioned, the P-Asserted-Id should do the
trick. I can't find an RFC for it, nor where I saw this
previously, but there is an order of precedence for the headers.
I don't remember them all but I do know that
<div><br>
<div>P-Asserted-Identity > Diversion > From</div>
</div>
<div><br>
</div>
<div>The other headers fit in there somewhere too, but I think
PAI is really what you want.</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr">On Thu, Sep 20, 2018 at 4:38 PM Peter Crawford
<<a href="mailto:pdcraw27@gmail.com" moz-do-not-send="true">pdcraw27@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">
<div>Hello voice-ops:</div>
<div><br>
</div>
<div>Enterprise admin here.</div>
<div><br>
</div>
<div>We just converted from ISDN to SIP (and changed
providers) and we're seeing some undesirable billing
behavior. I'm hoping I can get some objective feedback
from different providers.</div>
<div><br>
</div>
<div>If a call comes into our system, and we forward it
off-net using the SIP trunks (using either "standard" call
forwarding or a call forking/paralleling feature like
Avaya's EC500 or Cisco's Single Number Reach), we send the
call with the SIP FROM header of the original caller
(which is desirable to preserve callerID). We also
include a Diversion Header with one of our phone numbers
(the original destination of the call).</div>
<div><br>
</div>
<div>We're being billed based on the *original* calling
number, which sometimes results in long distance charges,
even if this leg of the call is local to us. This is
particularly onerous if the inbound call is international!</div>
<div><br>
</div>
<div>So, the question is- what *should* we be billed on:
FROM or DIVERSION.</div>
<div><br>
</div>
<div>At one point, the provider indicated that P-Charge-Info
was supported, but now backing away from that.</div>
<div><br>
</div>
<div>Do we have any recourse (technical or otherwise)?</div>
<div><br>
</div>
<div>Thanks.</div>
<div><br>
</div>
</div>
_______________________________________________<br>
VoiceOps mailing list<br>
<a href="mailto:VoiceOps@voiceops.org" target="_blank"
moz-do-not-send="true">VoiceOps@voiceops.org</a><br>
<a href="https://puck.nether.net/mailman/listinfo/voiceops"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://puck.nether.net/mailman/listinfo/voiceops</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
VoiceOps mailing list
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<br>
</body>
</html>