Re: [VoiceOps] Question about billing on SIP trunks

2018-09-20 Thread Ryan Delgrosso
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. That being said, does the provider youre with make a distinction between local/LD? thats relati

Re: [VoiceOps] Question about billing on SIP trunks

2018-09-20 Thread Aryn Nakaoka 808.356.2901
If you show nothing , I wonder how they'd bill you. Or if you edit from to a number within that area code, what then? I'm assuming larger carriers would want something constant. Aryn Nakaoka 808.356.2901 On Thu, Sep 20, 2018, 11:04 AM Joe Aponick wrote: > Does this provider have anything to

Re: [VoiceOps] Question about billing on SIP trunks

2018-09-20 Thread Joe Aponick
Does this provider have anything to say about the SIP privacy headers, P-Asserted-Identity and/or Remote-Party-ID? Those are typically preferred for routing/billing purposes whereas From is typically preferred for display. You might be able to keep the original caller in the From header, and se

Re: [VoiceOps] Question about billing on SIP trunks

2018-09-20 Thread Carlos Alvarez
That's an interesting question, and I think/hope several people on here will have answers. One thing I can say is that there may be legal issues requiring that behavior, to avoid "toll diversion." In our case we only sell flat-rate minutes so our customers don't see that detail. On Thu, Sep 20,

[VoiceOps] Question about billing on SIP trunks

2018-09-20 Thread Peter Crawford
Hello voice-ops: Enterprise admin here. 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. If a call comes into our system, and we forward it off-net using the SIP