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
January 2012
- 41 participants
- 70 messages
Local calling areas & 7-digit dialing (NANP)
by marylou@backuptelecom.com
Local calling areas are noted in each of the LEC tariffs by rate centers.
They are based on what other rate centers you can call from a particular
rate center. I live in the Franklin TN and while Nashville TN is in my EAS
area and Murfreesboro TN is also in the Nashville TN EAS area, Franklin is
not in the EAS area of Murfreesboro and visa versa, so you can't make the
assumption that just because Franklin and Murfreesboro can both call
Nashville that they are EAS to each other.
To set up your switch with the correct EAS areas, you have to pull a list of
NXXs that are local or EAS to that rate center and program your switch to
know that if a call is made to any of these NXXs it is considered local. The
best free source to find this information is in localcallingguide.com
Mary Lou Carey
BackUP Telecom Consulting
CLEC Consultant
OFF: 615-791-9969
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of PE
Sent: Thursday, January 12, 2012 4:23 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] Local calling areas & 7-digit dialing (NANP)
The NANP link that Paul posted is a good start because it at least tells you
where 7-digit is allowed, etc. Not sure if the local calling data that you
can get from CCMI (et al) gives you this info. You'd think, although my
experience with any of those is that they are fraught with errors.
The proper thing (IMO) is that everywhere go 10 digits. It's only 3 more
digits, people!
On Thu, Jan 12, 2012 at 5:11 PM, Paul Timmins <paul at timmins.net> wrote:
http://www.nanpa.com/nas/public/npa_query_step1.do?method=resetNpaReportMode
l
Plus the ilec tariffs may tell you most of it.
Often the state PUC will know these strange little quirks, or can tell you
where they exist. I don't think they're catalogued in any one place.
-Paul
On 01/12/2012 04:35 PM, Nathan Anderson wrote:
So we have 7-digit dialing in place for NANP destinations. The
implementation is really stupid-simple: if 7 digits are dialed, take the
originating number's area code and tack it on to the front of the dialed
number. I am pretty sure this is how most commercial ITSPs do it (as tested
also on Vonage and Packet8).
But for certain areas, this doesn't properly mimic the 7-digit dialing that
people who still have a POTS circuit from their LEC are used to. Take ours
for example: I'm in Moscow, ID (NPA 208). We sit smack-dab on the WA/ID
state border. 8 miles to the west of us is Pullman, WA (NPA 509). Both
cities have the same ILEC: Frontier (f/k/a Verizon f/k/a GTE). There has
been an understanding here since (I think) the mid-80s that calls between
Moscow and Pullman are and will remain local. But on top of that, if you
dial a Pullman NXX from Moscow or a Moscow NXX from Pullman as 7-digits, the
call is patched through even though the NPA is different and even though (in
some cases) both NPAs have NXXes that overlap with each other (although the
corresponding NXX in the same NPA as the caller would be considered a
long-distance call in all cases I can think of). The ILEC phone switch
still does the "right" thing. It's been this way for YEARS, and people here
are used to it.
Now say I wanted to implement something like that for our customers. I know
what the special exceptions are for this local market, and could probably
make it work on our switch. But I only know about them because I've lived
here and know the drill as a result. And I don't know how common or not
this kind of thing is in other areas where you might be on the geographical
edge of one's NPA(s).
So the question I have is, is there some kind of central resource/authority
that I can go to in order to find out what the dialing rules are for a given
rate center (mandatory 10-digits/7-digits only within your own NPA/7-digits
for certain local NPA-NXX outside your own NPA)? ...or is the only way to
know for sure to find out from the locals?
-- Nathan
_______________________________________________
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
Jan. 12, 2012
Local calling areas & 7-digit dialing (NANP)
by peeip989@gmail.com
The NANP link that Paul posted is a good start because it at least tells
you where 7-digit is allowed, etc. Not sure if the local calling data that
you can get from CCMI (et al) gives you this info. You'd think, although my
experience with any of those is that they are fraught with errors.
The proper thing (IMO) is that everywhere go 10 digits. It's only 3 more
digits, people!
On Thu, Jan 12, 2012 at 5:11 PM, Paul Timmins <paul at timmins.net> wrote:
> http://www.nanpa.com/nas/**public/npa_query_step1.do?**
> method=resetNpaReportModel<http://www.nanpa.com/nas/public/npa_query_step1.do?method=resetNpaReportMod…>
>
> Plus the ilec tariffs may tell you most of it.
>
> Often the state PUC will know these strange little quirks, or can tell you
> where they exist. I don't think they're catalogued in any one place.
> -Paul
>
>
> On 01/12/2012 04:35 PM, Nathan Anderson wrote:
>
>> So we have 7-digit dialing in place for NANP destinations. The
>> implementation is really stupid-simple: if 7 digits are dialed, take the
>> originating number's area code and tack it on to the front of the dialed
>> number. I am pretty sure this is how most commercial ITSPs do it (as
>> tested also on Vonage and Packet8).
>>
>> But for certain areas, this doesn't properly mimic the 7-digit dialing
>> that people who still have a POTS circuit from their LEC are used to. Take
>> ours for example: I'm in Moscow, ID (NPA 208). We sit smack-dab on the
>> WA/ID state border. 8 miles to the west of us is Pullman, WA (NPA 509).
>> Both cities have the same ILEC: Frontier (f/k/a Verizon f/k/a GTE). There
>> has been an understanding here since (I think) the mid-80s that calls
>> between Moscow and Pullman are and will remain local. But on top of that,
>> if you dial a Pullman NXX from Moscow or a Moscow NXX from Pullman as
>> 7-digits, the call is patched through even though the NPA is different and
>> even though (in some cases) both NPAs have NXXes that overlap with each
>> other (although the corresponding NXX in the same NPA as the caller would
>> be considered a long-distance call in all cases I can think of). The ILEC
>> phone switch still does the "right" thing. It's been this way for YEARS,
>> and people here are used to it.
>>
>> Now say I wanted to implement something like that for our customers. I
>> know what the special exceptions are for this local market, and could
>> probably make it work on our switch. But I only know about them because
>> I've lived here and know the drill as a result. And I don't know how
>> common or not this kind of thing is in other areas where you might be on
>> the geographical edge of one's NPA(s).
>>
>> So the question I have is, is there some kind of central
>> resource/authority that I can go to in order to find out what the dialing
>> rules are for a given rate center (mandatory 10-digits/7-digits only within
>> your own NPA/7-digits for certain local NPA-NXX outside your own NPA)?
>> ...or is the only way to know for sure to find out from the locals?
>>
>> -- Nathan
>> ______________________________**_________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/**mailman/listinfo/voiceops<https://puck.nether.net/mailman/listinfo/voiceops>
>>
>>
>
>
> ______________________________**_________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/**mailman/listinfo/voiceops<https://puck.nether.net/mailman/listinfo/voiceops>
>
Jan. 12, 2012
Local calling areas & 7-digit dialing (NANP)
by paul@timmins.net
http://www.nanpa.com/nas/public/npa_query_step1.do?method=resetNpaReportMod…
Plus the ilec tariffs may tell you most of it.
Often the state PUC will know these strange little quirks, or can tell
you where they exist. I don't think they're catalogued in any one place.
-Paul
On 01/12/2012 04:35 PM, Nathan Anderson wrote:
> So we have 7-digit dialing in place for NANP destinations. The implementation is really stupid-simple: if 7 digits are dialed, take the originating number's area code and tack it on to the front of the dialed number. I am pretty sure this is how most commercial ITSPs do it (as tested also on Vonage and Packet8).
>
> But for certain areas, this doesn't properly mimic the 7-digit dialing that people who still have a POTS circuit from their LEC are used to. Take ours for example: I'm in Moscow, ID (NPA 208). We sit smack-dab on the WA/ID state border. 8 miles to the west of us is Pullman, WA (NPA 509). Both cities have the same ILEC: Frontier (f/k/a Verizon f/k/a GTE). There has been an understanding here since (I think) the mid-80s that calls between Moscow and Pullman are and will remain local. But on top of that, if you dial a Pullman NXX from Moscow or a Moscow NXX from Pullman as 7-digits, the call is patched through even though the NPA is different and even though (in some cases) both NPAs have NXXes that overlap with each other (although the corresponding NXX in the same NPA as the caller would be considered a long-distance call in all cases I can think of). The ILEC phone switch still does the "right" thing. It's been this way for YEARS, and people here are used to it.
>
> Now say I wanted to implement something like that for our customers. I know what the special exceptions are for this local market, and could probably make it work on our switch. But I only know about them because I've lived here and know the drill as a result. And I don't know how common or not this kind of thing is in other areas where you might be on the geographical edge of one's NPA(s).
>
> So the question I have is, is there some kind of central resource/authority that I can go to in order to find out what the dialing rules are for a given rate center (mandatory 10-digits/7-digits only within your own NPA/7-digits for certain local NPA-NXX outside your own NPA)? ...or is the only way to know for sure to find out from the locals?
>
> -- Nathan
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
Jan. 12, 2012
Local calling areas & 7-digit dialing (NANP)
by nathana@fsr.com
So we have 7-digit dialing in place for NANP destinations. The implementation is really stupid-simple: if 7 digits are dialed, take the originating number's area code and tack it on to the front of the dialed number. I am pretty sure this is how most commercial ITSPs do it (as tested also on Vonage and Packet8).
But for certain areas, this doesn't properly mimic the 7-digit dialing that people who still have a POTS circuit from their LEC are used to. Take ours for example: I'm in Moscow, ID (NPA 208). We sit smack-dab on the WA/ID state border. 8 miles to the west of us is Pullman, WA (NPA 509). Both cities have the same ILEC: Frontier (f/k/a Verizon f/k/a GTE). There has been an understanding here since (I think) the mid-80s that calls between Moscow and Pullman are and will remain local. But on top of that, if you dial a Pullman NXX from Moscow or a Moscow NXX from Pullman as 7-digits, the call is patched through even though the NPA is different and even though (in some cases) both NPAs have NXXes that overlap with each other (although the corresponding NXX in the same NPA as the caller would be considered a long-distance call in all cases I can think of). The ILEC phone switch still does the "right" thing. It's been this way for YEARS, and people here are used to it.
Now say I wanted to implement something like that for our customers. I know what the special exceptions are for this local market, and could probably make it work on our switch. But I only know about them because I've lived here and know the drill as a result. And I don't know how common or not this kind of thing is in other areas where you might be on the geographical edge of one's NPA(s).
So the question I have is, is there some kind of central resource/authority that I can go to in order to find out what the dialing rules are for a given rate center (mandatory 10-digits/7-digits only within your own NPA/7-digits for certain local NPA-NXX outside your own NPA)? ...or is the only way to know for sure to find out from the locals?
-- Nathan
Jan. 12, 2012
T.38 re-invites
by lindsey@e-c-group.com
It's true: you can go against the conventional "best practice" that everyone else is following.
But you cannot expect that everybody who looked at the IETF draft for their implementation planning is really implementing all of the possible combinations of features and permutations of operations. Especially when DSPs are on the line, vendors are very parsimonious about additional features. Some would consider the ability to accept or generate a T38 re-invite in either calling or called states to be an additional feature.
So if you are going to deviate from the BCPs, you should expect to have some interop fun.
I have given up the dream that every developer will implement every RFC in its fullest generality.
On Jan 10, 2012, at 1:15, Ryan Delgrosso <ryandelgrosso at gmail.com> wrote:
> Best practice and real-world are often very different things.
>
> I have seen numerous scenarios where a softswitch acting as a forking proxy will use a dummy SDP in its outgoing invite (Metaswitch and Sylantro both come to mind here), and immediately will re-invite when the far end has answered.
>
> I have also seen numerous scenarios where fax servers will send the initial invite with G711 and then instantly re-invite to T.38 upon answer.
>
> Dont stand on convention or BCP here, the re-invite often comes from the calling party, and sometimes a few times.
>
>
>
> On 01/04/2012 06:46 AM, Mark R Lindsey wrote:
>> The IETF informational draft: "SIP Support for Real-time Fax: Call Flow Examples And Best Current Practices" shows the re-INVITEs from the called party. This is still conventional best practice.
>>
>> http://tools.ietf.org/html/draft-ietf-sipping-realtimefax-01
>>
>>
>> Mike Coffee's talk at SIPNOC 2011 discussed the expectations, showed how things can fall apart:
>>
>> http://www.sipforum.org/component/option,com_docman/task,cat_view/gid,115/I…
>>
>>
>> -- Mark R Lindsey mark at ecg.co +1-229-316-0013 http://ecg.co/lindsey
>>
>>
>>
>>
>> On Jan 4, 2012, at 04:35 , Nathan Anderson wrote:
>>
>>> This might not be the most appropriate forum for such a question, but given that implementation bugs in either NOC gear or CPE gear can cause headaches for network operators, I offer this here in the hope that perhaps a fellow VoiceOp here may have run into this before and knows the answer...
>>>
>>> It is my understanding that with SIP, *either* party to a call can send another INVITE (a so-called "re-invite") at any time during an active session; this could be used to change the endpoint of a call or redirect it elsewhere, and is also commonly used to renegotiate the media in use (audio, video, image, and associated codecs) without dropping the call even while the endpoints remain the same.
>>>
>>> Does this hold true, though, for re-invites whose purpose is to switch from an RTP audio stream to a T.38 UDPTL stream? Can *either* peer send that INVITE? Or is there a rule -- spoken or unspoken -- that states that a T.38 re-invite can only be initiated by the *receiver* of the fax, and not the transmitter?
>>>
>>> I have some ATAs that appear to send out a T.38 re-invite upon detection of a fax tone regardless of whether the ATA placed the call or answered the call, and if I am understanding what I'm seeing in my packet captures, I think the fact that these ATAs do this even when they are going to play the role of the T.38 transmitter is confusing the heck out of my (Asterisk) SBC and the termination provider. But I can't find any concrete evidence to support the idea that T.38 re-invites should only be initiated by the receiver.
>>>
>>> --
>>> Nathan Anderson
>>> First Step Internet, LLC
>>> nathana at fsr.com
>>> _______________________________________________
>>> 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
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Jan. 10, 2012
Broadsoft SIP Trunks and ILD Fraud
by dpeak@broadsoft.com
What actually is happening in the case outlined below by Zak Rupas is probably something that everyone should be aware of. It is not about somehow finding a way to exceed the capacity configured for the given BroadWorks trunk group, it's ultimately about originating a call via a BW trunk group and then immediately transferring that call such that it is no longer on the BW trunk group.
Scenario goes like this, with four parties involved; Customer PBX with BW trunk, Bad Guy, Expensive International number, and US number. In this scenario, the Bad Guy wants to allow the US Number and Expensive International number to talk on PBX owner's dime.
1. Service Provider provides an authenticated BW SIP trunk to their customer's PBX, with let's say 5 sim calls.
2. Customer's PBX gets compromised somehow, and the Bad Guy now has control of some number of phones/endpoints behind that PBX.
3. ILD originations are allowed by the Service Provider from the PBX, so Bad Guy places a call to Expensive International number.
4. Bad Guy then immediately blind transfers the call to the US number, such that the call is no longer associated with the trunk group and the trunk group's sim call limitations.
5. US number and ILD destination are connected, they talk, with billing going to the PBX owner (as that's who the CDR will show as placing the original call and making the transfer).
6. Bad Guy repeats this many times, getting many calls going simultaneously, fundamentally unrestricted by the capacity of the trunk group.
With existing functionality, there are ways to mitigate this situation.
1. Ensure that PBX doesn't get compromised in the first place, but this is hard, and is bound to happen, so this is not sufficient to prevent fraud.
2. In BroadWorks, turn of ILD for all users altogether, and if some users actually do need ILD, only enable it for them explicitly using Comm Barring.
3. In BroadWorks, enforce an Authorization Code when dialing ILD destinations. This can be all ILD, or can be a subset of ILD destinations, using the Comm Barring feature with Auth Code as the action.
4. In BroadWorks, use Call Processing Policies to limit the number of redirected calls allowed by a given trunking user to some small number like 1 or 2. This does not solve the problem entirely, but will reduce the total number of calls that the Bad Guy can get pinned up to one or two time the number of compromised DIDs on the trunk. BroadSoft recommends that all users have such Call Processing Policies enabled and configured.
5. Use some fraud detection system (like Equinox IS Protector or whatever) that alerts you when a strange calling patterns occurs. If this is in place, then even if the system is compromised, you'll be alerted to it soon after it starts and then you can turn off that trunk.
For those of you with access to Xchange, there is a document that outlines all the layers of security that should be enabled to harden your networks against fraud. URL below:
http://xchange.broadsoft.com/php/xchange/support/broadworks/tac/technical-s…
Dag Peak
Senior Systems Engineer
dpeak at broadsoft.com<mailto:dpeak at broadsoft.com>
Twitter @dagpeak
From: Danijel [mailto:theghost101 at gmail.com]
Sent: Tuesday, January 10, 2012 8:31 AM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] Broadsoft SIP Trunks and ILD Fraud
That's unblocked only only per customer basis if the customer complains that he can't reach those numbers ;-)
--
*blap*
On Mon, Jan 2, 2012 at 15:49, Alex Balashov <abalashov at evaristesys.com<mailto:abalashov at evaristesys.com>> wrote:
Or Globalstar or Inmarsat. :-)
--
This message was painstakingly thumbed out on my mobile, so apologies for brevity, errors, and general sloppiness.
Alex Balashov - Principal
Evariste Systems LLC
260 Peachtree Street NW
Suite 2200
Atlanta, GA 30303
Tel: +1-678-954-0670<tel:%2B1-678-954-0670>
Fax: +1-404-961-1892<tel:%2B1-404-961-1892>
Web: http://www.evaristesys.com/
On Jan 2, 2012, at 5:17 AM, Danijel <theghost101 at gmail.com<mailto:theghost101 at gmail.com>> wrote:
5 simultaneous calls to Cuba or some African country is still a lots of money.
--
*blap*
On Fri, Dec 30, 2011 at 17:36, Zak Rupas <zak at simplesignal.com<mailto:zak at simplesignal.com>> wrote:
Good Morning Voice OPS
Is anyone else experiencing anything like this? If so please share what you have done / or will to make it stop
We have a series of smaller SIP trunk customers using Broadsoft trunk groups. By design the trunk groups have a concurrent call limitation based off the customer's order. These smaller SIP trunks groups when compromised are able to run up HUGE fraud bills even tho they only have 5 or 6 SIP trunks. Needing to know if anyone else is seeing this that has Broadsoft and what was done to protect yourselves?
Otherwise Happy NYE :)
Zak Rupas
VoIP Engineer
SimpleSignal
3600 S Yosemite Suite 150
Denver, CO 80237
One Number Rings All My Phones: 303-242-8606<tel:303-242-8606>
Jan. 10, 2012
Broadsoft SIP Trunks and ILD Fraud
by theghost101@gmail.com
That's unblocked only only per customer basis if the customer complains
that he can't reach those numbers ;-)
--
*blap*
On Mon, Jan 2, 2012 at 15:49, Alex Balashov <abalashov at evaristesys.com>wrote:
> Or Globalstar or Inmarsat. :-)
>
> --
> This message was painstakingly thumbed out on my mobile, so apologies for
> brevity, errors, and general sloppiness.
>
> Alex Balashov - Principal
> Evariste Systems LLC
> 260 Peachtree Street NW
> Suite 2200
> Atlanta, GA 30303
> Tel: +1-678-954-0670
> Fax: +1-404-961-1892
> Web: <http://www.evaristesys.com/>http://www.evaristesys.com/
>
> On Jan 2, 2012, at 5:17 AM, Danijel <theghost101 at gmail.com> wrote:
>
> 5 simultaneous calls to Cuba or some African country is still a lots of
> money.
>
> --
> *blap*
>
>
> On Fri, Dec 30, 2011 at 17:36, Zak Rupas < <zak at simplesignal.com>
> zak at simplesignal.com> wrote:
>
>> Good Morning Voice OPS
>>
>>
>>
>> Is anyone else experiencing anything like this? If so please share what
>> you have done / or will to make it stop
>>
>>
>>
>> We have a series of smaller SIP trunk customers using Broadsoft trunk
>> groups. By design the trunk groups have a concurrent call limitation based
>> off the customer?s order. These smaller SIP trunks groups when compromised
>> are able to run up HUGE fraud bills even tho they only have 5 or 6 SIP
>> trunks. Needing to know if anyone else is seeing this that has Broadsoft
>> and what was done to protect yourselves?
>>
>>
>>
>> Otherwise Happy NYE J
>>
>>
>>
>> Zak Rupas
>> VoIP Engineer
>>
>> *SimpleSignal*
>> 3600 S Yosemite Suite 150
>>
>> Denver, CO 80237
>> One Number Rings All My Phones: 303-242-8606
>>
>> SimpleSignal.com <http://www.simplesignal.com/> | Blog<http://www.simplesignal.com/blog>|
>> Facebook <http://www.facebook.com/SimpleSignal?ref=ts> | Twitter<http://twitter.com/simplesignal>
>>
>>
>>
>> _______________________________________________
>> VoiceOps mailing list
>> <VoiceOps at voiceops.org>VoiceOps at voiceops.org
>> <https://puck.nether.net/mailman/listinfo/voiceops>
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>
>
Jan. 10, 2012
T.38 re-invites
by ryandelgrosso@gmail.com
Best practice and real-world are often very different things.
I have seen numerous scenarios where a softswitch acting as a forking
proxy will use a dummy SDP in its outgoing invite (Metaswitch and
Sylantro both come to mind here), and immediately will re-invite when
the far end has answered.
I have also seen numerous scenarios where fax servers will send the
initial invite with G711 and then instantly re-invite to T.38 upon answer.
Dont stand on convention or BCP here, the re-invite often comes from the
calling party, and sometimes a few times.
On 01/04/2012 06:46 AM, Mark R Lindsey wrote:
> The IETF informational draft: "SIP Support for Real-time Fax: Call Flow Examples And Best Current Practices" shows the re-INVITEs from the called party. This is still conventional best practice.
>
> http://tools.ietf.org/html/draft-ietf-sipping-realtimefax-01
>
>
> Mike Coffee's talk at SIPNOC 2011 discussed the expectations, showed how things can fall apart:
>
> http://www.sipforum.org/component/option,com_docman/task,cat_view/gid,115/I…
>
>
> -- Mark R Lindsey mark at ecg.co +1-229-316-0013 http://ecg.co/lindsey
>
>
>
>
> On Jan 4, 2012, at 04:35 , Nathan Anderson wrote:
>
>> This might not be the most appropriate forum for such a question, but given that implementation bugs in either NOC gear or CPE gear can cause headaches for network operators, I offer this here in the hope that perhaps a fellow VoiceOp here may have run into this before and knows the answer...
>>
>> It is my understanding that with SIP, *either* party to a call can send another INVITE (a so-called "re-invite") at any time during an active session; this could be used to change the endpoint of a call or redirect it elsewhere, and is also commonly used to renegotiate the media in use (audio, video, image, and associated codecs) without dropping the call even while the endpoints remain the same.
>>
>> Does this hold true, though, for re-invites whose purpose is to switch from an RTP audio stream to a T.38 UDPTL stream? Can *either* peer send that INVITE? Or is there a rule -- spoken or unspoken -- that states that a T.38 re-invite can only be initiated by the *receiver* of the fax, and not the transmitter?
>>
>> I have some ATAs that appear to send out a T.38 re-invite upon detection of a fax tone regardless of whether the ATA placed the call or answered the call, and if I am understanding what I'm seeing in my packet captures, I think the fact that these ATAs do this even when they are going to play the role of the T.38 transmitter is confusing the heck out of my (Asterisk) SBC and the termination provider. But I can't find any concrete evidence to support the idea that T.38 re-invites should only be initiated by the receiver.
>>
>> --
>> Nathan Anderson
>> First Step Internet, LLC
>> nathana at fsr.com
>> _______________________________________________
>> 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
Jan. 10, 2012
Acme Packet/Broadsoft/ENUM
by lindsey@e-c-group.com
Would sag-recursion obviate the need for the two session groups?
It would allow the SD attempt more than one target within that SAG for the same SIP transaction.
But I haven't tried it with enum.
On Jan 5, 2012, at 18:03, Tim Thompson <timthompson at nicodem.us> wrote:
> Yessir:
>
> session-group
> group-name NetSrvr
> description Broadsoft_NetGroup
> state enabled
> app-protocol SIP
> strategy Hunt
> dest
> net1.bs.sip
> net2.bs.sip
>
> session-group
> group-name NetSrvr2
> description Broadsoft_NetGroup
> state enabled
> app-protocol SIP
> strategy Hunt
> dest
> net2.bs.sip
> net1.bs.sip
>
> Make sure if you go the SAG route, that enum-sag-match is enabled in the
> sip-config on the SD, else it won't match back to the SAG.
>
> -Tim
>
> On 01/05/2012 02:59 PM, Robert Dawson wrote:
>> Perfect - thanks again.
>>
>> Just to clarify, NetSrvr and NetSrvr2 are the actual names of the SAGs on the AP?
>>
>>> -----Original Message-----
>>> From: Tim Thompson [mailto:timthompson at nicodem.us]
>>> Sent: Thursday, January 05, 2012 5:51 PM
>>> To: Robert Dawson
>>> Cc: voiceops at voiceops.org
>>> Subject: Re: [VoiceOps] Acme Packet/Broadsoft/ENUM
>>>
>>> We also use powerdns, but use the pipe backend to pass it through some
>>> in-house code, which is itself backended by oracle. This works more or
>>> less the same, but you gain some additional control via the pipe
>>> backend.
>>>
>>> Here's the results of a 'show enum lookup'. DNs and FQDNs have been
>>> changed to protect the innocent.
>>>
>>> Enum Lookup Result:
>>> Query Name -->
>>> +9165551212
>>> Answers -->
>>> sip:+19165551212 at NetSrvr ttl= 120
>>> sip:+19165551212 at NetSrvr2 ttl= 120
>>>
>>> And the associated cache-entry:
>>> Query-->
>>> Q:NAPTR 2.1.2.1.5.5.5.6.1.9.tld ttl=48
>>> Answers-->
>>>
>>> order=50 pref=1 "u" "E2U+sip"
>>> "!^.*$!sip:+19165551212 at NetSrvr!" ""
>>>
>>> order=50 pref=2 "u" "E2U+sip"
>>> "!^.*$!sip:+19165551212 at NetSrvr2!" ""
>>>
>>> The same query via dig:
>>>
>>> ;; ANSWER SECTION:
>>> 2.1.2.1.5.5.5.6.1.9.tld. 120 IN NAPTR 50 1 "u" "E2U+sip"
>>> "!^.*$!sip:+19165551212 at NetSrvr!" .
>>> 2.1.2.1.5.5.5.6.1.9.tld. 120 IN NAPTR 50 2 "u" "E2U+sip"
>>> "!^.*$!sip:+19165551212 at NetSrvr2!" .
>>>
>>>
>>> Both NetSrvr and NetSrvr2 are SAGs, with the two netservers'
>>> session-agents in reverse orders, per best practices. (i.e. Net1/Net2,
>>> Net2/Net1.)
>>>
>>> Hope this helps,
>>> -Tim
>>>
>>>
>>> On 01/05/2012 02:19 PM, Robert Dawson wrote:
>>>> Sure, anything would be helpful. I am using powerdns with a mysql
>>> backend, sounds similar to your setup.
>>>>
>>>> Thanks,
>>>> Rob
>>>>
>>>>> -----Original Message-----
>>>>> From: voiceops-bounces at voiceops.org [mailto:voiceops-
>>>>> bounces at voiceops.org] On Behalf Of Tim Thompson
>>>>> Sent: Thursday, January 05, 2012 4:01 PM
>>>>> To: voiceops at voiceops.org
>>>>> Subject: Re: [VoiceOps] Acme Packet/Broadsoft/ENUM
>>>>>
>>>>> Rob,
>>>>>
>>>>> We use a custom in-house ENUM solution that queries a database in
>>> real
>>>>> time, so I can't offer you an actual zone snippet. I could give some
>>>>> examples of what 'show enum lookup' or dig would return, if that
>>> would
>>>>> be helpful.
>>>>>
>>>>> -Tim
>>>>>
>>>>>
>>>>> On 01/05/2012 11:12 AM, Robert Dawson wrote:
>>>>>> Is anyone using ENUM with their Acme/BS deployment that wouldn't
>>> mind
>>>>>> sharing a snippet of their zone file showing the proper record
>>>>>> configuration?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Rob
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
Jan. 7, 2012
Australian Broadsoft Sales Contact
by Marty_Sorensen@adp.com
I have provided Nick with a sales contact.....
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Nick Brown
Sent: Thursday, January 05, 2012 2:11 PM
To: voiceops at voiceops.org
Subject: [VoiceOps] Australian Broadsoft Sales Contact
While not entirely ontopic Is anyone on this list able to put me in
contact with someone who can assist with Broadsoft presales? I've had no
luck with the online contact form and was unable to get anyone to call
me back after calling through late last year.
Cheers
Nick Brown.
_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Jan. 5, 2012