VoiceOps
By thread
voiceops@voiceops.org
By month
Messages by month
- ----- 2026 -----
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
September 2018
- 12 participants
- 23 messages
SIPNOC 2018 - ICYMI
by slocoach@gmail.com
With the talk about SHAKEN on the list lately, thought this might be
useful info.
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.sipnoc.…>
*Canadian Radio-Television and **Telecomm**unications Commission (CRTC)
Chairman and CEO Ian Scott, and Current and Former FCC Chief Technology
Officers Dr. Eric Burger and SIP Pioneer Dr. Henning Schulzrinne to Keynote
at SIPNOC 2018!*
*Extraordinary Lineup of Keynote Speakers to Take the Podium at SIPNOC
2018, the 8th Annual SIP Network Operators Conference, December 4-6, 2018 *
*Also, New Discounted Government/Military Registration Passes now
Available! (see below for details.)*
The SIP Forum
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.sipfor…>
recently announced an extraordinary lineup of keynote speakers at the
association's annual 2018 SIP Network Operators Conference (*SIPNOC 2018*)
that includes Canadian Radio-Television and Telecommunications Commission
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcrtc.gc.ca…>
(CRTC) Chairman and CEO Ian Scott, current United States Federal
Communications Commission Chief Technology Officer Dr. Eric Burger, and
former FCC CTO Dr. Henning Schulzrinne.
CRTC Chairman and CEO Ian Scott has over 25 years of policy and regulatory
experience in broadcasting and telecommunications both in the public and
private sectors. After working at the Competition Bureau, he joined the
CRTC from 1990 to 1994, where he collaborated on the development of a
framework for long-distance telephone service competition in Canada.
Between 2007 and 2008, as part of the Executive Interchange Program, he was
Senior Policy Advisor to the Chairman at the CRTC.
Before rejoining the CRTC in 2017, Mr Scott held various executive
positions in the communications industry, including at Telesat Canada,
Telus and Call-Net Enterprises, one of the first companies to offer
competition in the Canadian long-distance market. He also provided
leadership on broadcasting policy and regulatory issues as an executive at
the Canadian Cable Television Association.
The United States Federal Communications Commission's Chief Technology
Officer Dr. Eric Burger serves as an advisor to the Chairman and as the
senior technology expert in the agency.
* DIAMOND SPONSOR*
[image: Image]
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fribboncomm…>
* PLATINUM SPONSOR *
[image: Image]
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.home.n…>
* GOLD SPONSORS *
[image: Image]
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fecg.co%2F&d…>
[image: Image]
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.secure…>
[image: Image]
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.telcob…>
Prior to joining the Commission, Dr. Burger served as director of the
Security and Software Engineering Research Center in Washington, DC. The
center helps propose solutions to network problems like Robocalling, rural
call completion, accessibility of communications for Americans with hearing
and speech impairments, reducing the cost of deploying and operating
communications networks, and ensuring communication network security and
stability. He holds patents in telecommunications and is an expert in
standards for telecommunications, network, and Internet technologies.
Dr. Burger has also held senior engineering and technology positions in
various telecommunications companies and served as a technology consultant
to others. He is also the Former Chairman of the SIP Forum, and he has
taught computer science at Georgetown University, George Mason University,
and The George Washington University. He holds a Ph.D. in computer science
from Illinois Institute of Technology, an MBA from Katholieke Universiteit
Leuven in Belgium, and bachelor?s degree from Massachusetts Institute of
Technology.
Serving as CTO and in various other roles at the FCC from 2010 to 2017, Dr.
Schulzrinne guided the organization's work on technology and engineering
issues, together with the FCC?s Office of Engineering and Technology.
Dr. Schulzrinne holds the Julian Clarence Levi Chair of Mathematical
Methods and Computer Science at the Fu Foundation School of Engineering at
Columbia University. Over the course of his career, he has published more
than 250 journal and conference papers and more than 70 Internet Requests
for Comment (RFCs) ? working to shape the key protocols for enabling
voice-over-IP (VoIP) and other multimedia applications, including the
Session Initiation Protocol (SIP) which have become Internet Standards. His
research interests include Internet multimedia systems, applied network
engineering, wireless networks, security, communication policy, and
performance evaluation.
*About SIPNOC 2018*
*The Eighth Annual SIPNOC 2018*, being held at the Hyatt Regency Dulles
Hotel in Herndon, VA, December 4 -6, 2018, is a unique three-day
educational conference focusing on the challenges and opportunities related
to the reliable and successful deployment and operation of SIP-based
services.
The *SIPNOC 2018* agenda will feature special presentations, tutorials,
panel discussions and workshops covering key topics related to SIP-based
services, applications, and infrastructure.
Attendees at *SIPNOC 2018* will include engineers and network architects
from telecommunications providers, major backbone operators, interconnect
and wholesale solution providers, ISPs, cable operators, wireless network
operators as well as large enterprises deploying major SIP initiatives.
As part of *SIPNOC 2018*, the SIP Forum will host a special Robocall Summit
to be held on Tuesday, December 4th, 2018, focused on Robocall and Caller
ID Spoofing elimination and mitigation and specifically developed for
industry stakeholders in that ecosystem, including service providers
seeking to deploy new solutions, governmental regulators and agencies,
equipment manufacturers, enterprise and government agency contact centers,
application providers and data analytics firms.
*SIPNOC 2018 Call for Presentations General Info*
- To view the official call for presentations, which includes
instructions on submitting material, key dates of interest, and specific
SIPNOC policies, please visit
https://www.sipforum.org/news-events/sipnoc-2018-overview/sipnoc-2018-call-…
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.sipfor…>.
To submit, visit https://www.easychair.org/conferences/?conf=sipnoc2018
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.easych…>
.
*SIPNOC 2018 Registration*
*Regular All-Access Conference Pass:* The regular "All-Access" SIPNOC 2018
conference registration fee is $1295 and includes access to the Robocall
Summit, followed by two days of conference proceedings. This
"all-inclusive" fee also includes breakfasts, lunches and break
refreshments and snacks, and special networking receptions the first and
second nights of the event!
*Full Member All-Access Pass:* Individuals from SIP Forum Full Member
companies save more ($200 to be exact) on an early-bird All-Access Pass!
Send an email to sipnocinfo at sipforum.org to request the Full Member
discount code.
*NEW! Gov't/Military Employee All-Access Pass:* Individuals who work for
government agencies or the military are entitled to a special savings of
$445 on the All-Access Pass (for a total fee of $850). Please send an email
to sipnocinfo at sipforum.org to request the exclusive discount code.
*Conference Sessions-Only Pass*: Aren't interested in the Robocall Summit
but want to attend the General Sessions part of the conference? We have you
covered! Register by selecting the "Conference Sessions Only" option. The
regular "Conference Sessions Only" Pass is $1095 for two days of conference
proceedings, meals and breaks, and the Beer and Gear Networking Dinner
reception.
*NEW! Gov't/Military Employee Conference Sessions-Only Pass:* Individuals
who work for government agencies or the military are entitled to a special
savings of $345 on the Conference Sessions-Only Pass (for a total fee of
$750). Please send an email to sipnocinfo at sipforum.org to request the
exclusive discount code.
*Robocall Summit-Only Pass*: Just want to attend the Robocall Summit? No
problem! Simply select this registration type, with an associated fee of
$595.
*Register *at https://www.regonline.com/sipnoc2018
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.regonl…>.
*SIPNOC 2018 General Event Information*
- For more information about *SIPNOC 2018*, please visit www.sipnoc.org
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.sipnoc.…>
or send an email to sipnocinfo at sipforum.org.
*SIPNOC 2018 Sponsorship Information*
- *Learn more about SIPNOC 2018 Sponsorship Opportunities by downloading
the SIPNOC 2018 Sponsorship Brochure!
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.sipfor…>*
For additional information about corporate sponsorship
opportunities at *SIPNOC
2018*, please contact Marc Robins, SIP Forum President and Managing
Director, at
203-829-6307 or marc.robins "at" sipforum.org.
*For more information, please visit:*
* www.sipnoc.org
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.sipnoc.…>
or email sipnocinfo at sipforum.org*
Sept. 26, 2018
Question about billing on SIP trunks
by pdcraw27@gmail.com
Thank you all for the feedback.
This confirms my initial thought- that FROM is probably the last thing that
should be used.
On Fri, Sep 21, 2018 at 10:41 AM Pete Eisengrein <peeip989 at gmail.com> wrote:
> 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
>
> P-Asserted-Identity > Diversion > From
>
> The other headers fit in there somewhere too, but I think PAI is really
> what you want.
>
> On Thu, Sep 20, 2018 at 4:38 PM Peter Crawford <pdcraw27 at gmail.com> wrote:
>
>> 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
>> 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).
>>
>> 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!
>>
>> So, the question is- what *should* we be billed on: FROM or DIVERSION.
>>
>> At one point, the provider indicated that P-Charge-Info was supported,
>> but now backing away from that.
>>
>> Do we have any recourse (technical or otherwise)?
>>
>> Thanks.
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>
Sept. 24, 2018
Question about billing on SIP trunks
by ryandelgrosso@gmail.com
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.
On 9/21/2018 7:41 AM, Pete Eisengrein wrote:
> 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
>
> P-Asserted-Identity > Diversion > From
>
> The other headers fit in there somewhere too, but I think PAI is
> really what you want.
>
> On Thu, Sep 20, 2018 at 4:38 PM Peter Crawford <pdcraw27 at gmail.com
> <mailto:pdcraw27 at gmail.com>> wrote:
>
> 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 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).
>
> 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!
>
> So, the question is- what *should* we be billed on: FROM or DIVERSION.
>
> At one point, the provider indicated that P-Charge-Info was
> supported, but now backing away from that.
>
> Do we have any recourse (technical or otherwise)?
>
> Thanks.
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org <mailto:VoiceOps at voiceops.org>
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Sept. 23, 2018
Question about billing on SIP trunks
by peeip989@gmail.com
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
P-Asserted-Identity > Diversion > From
The other headers fit in there somewhere too, but I think PAI is really
what you want.
On Thu, Sep 20, 2018 at 4:38 PM Peter Crawford <pdcraw27 at gmail.com> wrote:
> 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
> 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).
>
> 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!
>
> So, the question is- what *should* we be billed on: FROM or DIVERSION.
>
> At one point, the provider indicated that P-Charge-Info was supported, but
> now backing away from that.
>
> Do we have any recourse (technical or otherwise)?
>
> Thanks.
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Sept. 21, 2018
Question about billing on SIP trunks
by marylou@backuptelecom.com
I would think it would only matter if the called party is served by the
PSTN network because that's the only time that MOU billing should take
place. However, it may be that your service provider doesn't
differentiate and just bills you MOU charges based on what you send
them so that they're covered just in case it hits the PSTN network.
Mary Lou Carey
BackUP Telecom Consulting
Office: 615-771-7868 (temporary)
Cell: 615-796-1111
On 2018-09-20 06:20 PM, Ryan Delgrosso wrote:
> 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 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.
>
> On 9/20/2018 1:34 PM, Peter Crawford wrote:
>
>> 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 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).
>>
>> 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!
>>
>> So, the question is- what *should* we be billed on: FROM or
>> DIVERSION.
>>
>> At one point, the provider indicated that P-Charge-Info was
>> supported, but now backing away from that.
>>
>> Do we have any recourse (technical or otherwise)?
>>
>> Thanks.
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Sept. 21, 2018
Question about billing on SIP trunks
by pdcraw27@gmail.com
Thanks for the replies.
I'll withhold the both organizations' names publicly at this point....still
a bit sensitive :)
We've been looking into PAI, but haven't done any testing yet.
As for modifying the FROM number, the billing absolutely reflects what we
send. If I originate a local call from our network, but send a FROM that
looks long distance, we get billed long distance. Caller ID aside, we can
completely avoid long distance charges if we set our FROM field to be
something local to the TO field.
On Thu, Sep 20, 2018 at 5:09 PM Aryn Nakaoka 808.356.2901 <
anakaoka at trinet-hi.com> wrote:
> 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 <joea at voipinnovations.com>
> wrote:
>
>> 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 set
>> the P-Asserted-Identity or RPID to the original destination and have the
>> call be routed and billed based on that.
>>
>>
>>
>>
>>
>>
>>
>> *From:* VoiceOps <voiceops-bounces at voiceops.org> *On Behalf Of *Peter
>> Crawford
>> *Sent:* Thursday, September 20, 2018 4:35 PM
>> *To:* voiceops at voiceops.org
>> *Subject:* [VoiceOps] Question about billing on SIP trunks
>>
>>
>>
>> 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
>> 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).
>>
>>
>>
>> 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!
>>
>>
>>
>> So, the question is- what *should* we be billed on: FROM or DIVERSION.
>>
>>
>>
>> At one point, the provider indicated that P-Charge-Info was supported,
>> but now backing away from that.
>>
>>
>>
>> Do we have any recourse (technical or otherwise)?
>>
>>
>>
>> Thanks.
>>
>>
>> This message is for the designated recipient only and may contain
>> privileged, proprietary, or otherwise confidential information. If you have
>> received this message in error, please notify the sender immediately and
>> delete the original. Any other use of the e-mail by you is prohibited.
>> Unauthorized interception of this e-mail is a violation of federal criminal
>> law. We reserve the right, when permitted by law, to scan electronic
>> communications, including e-mail and instant messaging, for the purposes of
>> security and compliance with our internal policy.
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>
Sept. 21, 2018
Question about billing on SIP trunks
by ryandelgrosso@gmail.com
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 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.
On 9/20/2018 1:34 PM, Peter Crawford wrote:
> 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 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).
>
> 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!
>
> So, the question is- what *should* we be billed on: FROM or DIVERSION.
>
> At one point, the provider indicated that P-Charge-Info was supported,
> but now backing away from that.
>
> Do we have any recourse (technical or otherwise)?
>
> Thanks.
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Sept. 20, 2018
Question about billing on SIP trunks
by anakaoka@trinet-hi.com
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 <joea at voipinnovations.com> wrote:
> 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 set
> the P-Asserted-Identity or RPID to the original destination and have the
> call be routed and billed based on that.
>
>
>
>
>
>
>
> *From:* VoiceOps <voiceops-bounces at voiceops.org> *On Behalf Of *Peter
> Crawford
> *Sent:* Thursday, September 20, 2018 4:35 PM
> *To:* voiceops at voiceops.org
> *Subject:* [VoiceOps] Question about billing on SIP trunks
>
>
>
> 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
> 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).
>
>
>
> 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!
>
>
>
> So, the question is- what *should* we be billed on: FROM or DIVERSION.
>
>
>
> At one point, the provider indicated that P-Charge-Info was supported, but
> now backing away from that.
>
>
>
> Do we have any recourse (technical or otherwise)?
>
>
>
> Thanks.
>
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received this message in error, please notify the sender immediately and
> delete the original. Any other use of the e-mail by you is prohibited.
> Unauthorized interception of this e-mail is a violation of federal criminal
> law. We reserve the right, when permitted by law, to scan electronic
> communications, including e-mail and instant messaging, for the purposes of
> security and compliance with our internal policy.
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Sept. 20, 2018
Question about billing on SIP trunks
by joea@voipinnovations.com
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 set the P-Asserted-Identity or RPID to the original destination and have the call be routed and billed based on that.
From: VoiceOps <voiceops-bounces at voiceops.org> On Behalf Of Peter Crawford
Sent: Thursday, September 20, 2018 4:35 PM
To: voiceops at voiceops.org
Subject: [VoiceOps] Question about billing on SIP trunks
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 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).
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!
So, the question is- what *should* we be billed on: FROM or DIVERSION.
At one point, the provider indicated that P-Charge-Info was supported, but now backing away from that.
Do we have any recourse (technical or otherwise)?
Thanks.
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received this message in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Unauthorized interception of this e-mail is a violation of federal criminal law. We reserve the right, when permitted by law, to scan electronic communications, including e-mail and instant messaging, for the purposes of security and compliance with our internal policy.
Sept. 20, 2018
Question about billing on SIP trunks
by caalvarez@gmail.com
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, 2018 at 1:38 PM Peter Crawford <pdcraw27 at gmail.com> wrote:
> 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
> 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).
>
> 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!
>
> So, the question is- what *should* we be billed on: FROM or DIVERSION.
>
> At one point, the provider indicated that P-Charge-Info was supported, but
> now backing away from that.
>
> Do we have any recourse (technical or otherwise)?
>
> Thanks.
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Sept. 20, 2018