<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>So if it were me operating whoever your provider is, I would take
the diversion as the originating number of the leg in question and
bill appropriately, as the PAI/FROM in this case is display only.
<br>
</p>
<p>That being said, does the provider youre with make a distinction
between local/LD? thats relatively archaic these days as the
aggregate cost of national termination is so low most stopped
caring, it might be worth considering moving to another provider.<br>
</p>
<br>
<div class="moz-cite-prefix">On 9/20/2018 1:34 PM, Peter Crawford
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFYS9p2YN5KzAUrexZk5HMD8sNWJguuBx5ddqR-B2fhBgmaMdA@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<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>
<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>