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
March 2013
- 44 participants
- 116 messages
+44 190 prefix
by abalashov@evaristesys.com
A customer of mine is seeing aggressive attempts to dial +441904891769
through their system, but I can't find +44 190, or any superset or
subset thereof (beyond '44', obviously) in any rate decks easily at my
disposal. None of the usual retail suspects have it listed in any of
their online pricing, either.
I assume this means it's a new prefix, but can anyone tell if it's a
premium number?
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
United States
Tel: +1-678-954-0670
Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
March 23, 2013
What is a Modern SIP Phone?
by jra@baylink.com
----- Original Message -----
> From: "Michael Graves" <mgraves at mstvp.com>
> I'm often heard to say that, "I live in Houston. I know rocket science
> when I see it."
Hee.
Dragging this back on topic by force, it seems the Yealink phones may be
being built by Cortelco, possibly even in the US, if this thread is to be
believed""
http://www.pbxinaflash.com/community/index.php?threads/under-20-sip-phones.…
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA #natog +1 727 647 1274
March 23, 2013
What is a Modern SIP Phone?
by mgraves@mstvp.com
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org]
On Behalf Of Jay Ashworth
Sent: Thursday, March 21, 2013 1:42 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] What is a Modern SIP Phone?
This isn't... rocket science. (NASA has a big Cisco install, presumably CM
:-).
I'm often heard to say that, "I live in Houston. I know rocket science when
I see it."
Michael
March 22, 2013
What is a Modern SIP Phone?
by jra@baylink.com
----- Original Message -----
> From: "Mark R Lindsey" <lindsey at e-c-group.com>
> (There are some interesting points buried in this area about the
> fundamental "end to end argument in system design" and how that works
> for dynamically negotiated features. We'd all like to believe that we
> humans could specify standards and the two endpoints could negotiate
> the best common set of compatible features on each individual call.
> But we haven't proven that it's even possible.)
>
> When you're evaluating a SIP access device -- phone or PBX -- you're
> working in this weird milieux of non-standardized-yet-important
> features, for which interop testing is the only compliance that
> matters.
I love Starting Conversations. :-)
At that point, Mark, I should probably remind everyone why Interop got
started. I went to a very early one, at the Georgia World Congress Center,
and let me tell you, it was pretty impressive back then.
I don't see why someone isn't doing a well publicized shootout at an
annual event of some type, where each PBX vendor brings along their best
people, and each phone vendor brings *their* best people, and a set of
independent VoIP/PBX guys judge a shootout. Bring programming talent
along and have a hackathon between first day and last day, and see how
much you can fix.
This isn't... rocket science. (NASA has a big Cisco install, presumably
CM :-).
Cheers,
-- jra
--
Jay R. Ashworth Baylink jra at baylink.com
Designer The Things I Think RFC 2100
Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII
St Petersburg FL USA #natog +1 727 647 1274
March 21, 2013
Call Forwarding is broken; or, when CF meets LCR
by mike@astrocompanies.com
Hi Nathan,
For simplicity, perhaps it's better that we stop using the term ANI, which
itself is becoming deprecated. ANI is really a Class 4 term, primarily used
to identify the originating subscriber for toll calls on a Class 4 LD
switching platform. The Class 5 switching platform does in fact call this
CallingNumber rather than ANI. If we stick to the terms "CallingNumber" and
"BillingNumber" this probably becomes a lot clearer given all of the
confusion out there about what exactly ANI is. The SIP model has much more
in common with Class 5 than it does Class 4, despite its lack of a
BillingNumber field at present.
On your example of MCI's ANAC service, don't forget that MCI is primarily an
IXC. So their ANAC is more likely to be concerned with BillingNumber than
with CallingNumber. Why don't you try our ANAC on our Class 5 platform
(8138675309) and see what it tells you. I suspect you will get a different
result. BTW, I give permission for anyone to use this ANAC service that we
provide for free if it is helpful to you. A few years ago we were really in
need of a reliable ANAC service and couldn't find one, so I can relate to
that need.
I don't disagree about the negative impact of all the ANI/Access Cost
nonsense. And that's why we're happy to see ICC coming to a close. ICC
ended up being a vehicle that some CLECs used for arbitrage that the ILECs
hated, and a vehicle that the ILECs used to put CLECs out of business
through the use of various and sometimes questionable access billing
schemes. The FCC's decision that access cost impedes competition and needs
to be abolished is a welcome one (even though they are just following the
ILECs current desires which by some odd twist of fate are aligned with ours
here). I think it will also usher in a new era of simplicity, as all of
these schemes to charge or avoid access costs are made obsolete and common
sense call routing using best practices and current technology will win the
day.
Mike
Mike Ray, MBA, CNE, CTE
Astro Companies, LLC
11523 Palm Brush Trail #401
Lakewood Ranch, FL 34202
DIRECT: 941 600-0207
http://www.astrocompanies.com
-----Original Message-----
From: Nathan Anderson [mailto:nathana at fsr.com]
Sent: Wednesday, March 20, 2013 11:06 PM
To: 'Mike Ray'; 'voiceops at voiceops.org'
Subject: RE: [VoiceOps] Call Forwarding is broken; or, when CF meets LCR
Mike,
I haven't meant to leave your message sitting without a reply for so long;
my apologies. :) It's been a hectic last couple of days.
I'm not sure where I got the idea that CNID was a separate field from ANI,
then. Perhaps it was from everybody who kept repeating the mantra "ANI is
*not* Caller-ID. I repeat: ..." I mean, I know they're not the same
because Caller-ID is technically the name for a service provided over normal
loop-start lines that is modulated/transmitted by the local switch, but some
of the stuff you read leads you to believe that calling party number and the
ANI are two separate things, that the local switch doesn't consult ANI for
the number to display for Caller-ID, and that the two can differ for any
given call.
There seems to be so much misinformation and conflicting information out
there; it's crazy:
http://en.wikipedia.org/wiki/Caller_ID ("However, CNID and ANI are not the
same thing.") http://www.egyed.com/faq/cid.htm ("Thus while ANI is similar
to CALLER-ID and may provide the same information, they are actually two
different services and ANI information is not necessarily the same as what
will appear on a CALLER-ID display."
http://www.telcomp.com/cidani.html (not sure what's up with the large
type...)
http://docs.voxeo.com/ccxml/1.0-final/frame.jsp?page=anispoofing_ccxml10.htm
("One common misconception these days is that ANI and Caller ID to be used
synonymously. This is *not* the case.")
http://wiki.docdroppers.org/index.php?title=ANI_and_Caller_ID_Spoofing
(suggests ANI transmission via PRI only changes the "CPN", and not the
"ANI")
So who can help sort this out for us? It seems to me that most people in
these articles are using ANI and BTN synonymously, and treating CNID/CPN as
a different thing entirely. It's very confusing when different people are
throwing around different terms for (possibly) the same thing, and then
others are re-using some of those same terms to refer to different things.
When I call the MCI ANI readback number (800-437-7950), I hear "calling ANI"
and "charge ANI" read back to me. What do they mean? What is what?
You'd definitely know the FCC regs better than me, so I trust you on this,
but still...using ANI to determine jurisdiction of ALL call legs in an RCF
scenario just seems completely upside-down to me. In an RCF scenario, there
are going to be *two* carriers asking for compensation: the one for the
originally-called party, and then one for the final destination number. The
originally-called party's carrier is going to charge the caller's carrier,
and the carrier for the final destination is going to charge the
originally-called party's carrier. For the first leg of the call, of
course: use the ANI of the caller. But for the second leg, that doesn't
seem fair or right. The originally-called party's carrier should charge
him/her for the forwarded call, and that charge should be based on what the
call would have cost if the originally-called party had *dialed the CF
target number themselves* without a forward in place. Isn't that just
common-sense?
I was not aware that ICC was going to be dissolved permanently; very
interesting.
Thanks for the very informative posts,
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com
-----Original Message-----
From: Mike Ray [mailto:mike at astrocompanies.com]
Sent: Monday, March 18, 2013 10:42 PM
To: Nathan Anderson; voiceops at voiceops.org
Subject: RE: [VoiceOps] Call Forwarding is broken; or, when CF meets LCR
Hi Nathan,
I agree that nobody will likely ever get into trouble for doing as you
describe; stuffing the CallerID to match your subscriber's BTN as the call
passes through. However, the FCC defines proper jurisdiction of a call as
the two actual endpoints being connected, regardless of what's "in the
middle". So much for hairsplitting, but as you mentioned there is a
disincentive for you to do that anyway because of customer perception.
On your "industry standard fields" question, there may be a terminology
difference here, but in the Class 5 switching SS7 (and even PRI) world there
are two fields. One is intended to identify the calling party (ANI) which
is sometimes also called CPN, and the other to identify the billed party and
jurisdiction (BillingNumber), sometimes called BTN. In the Class 4 world,
the use of the term ANI is more prevalent, while the same field in the Class
5 world is sometimes called CallingNumber. But it is in fact the same field
as ANI. The BillingNumber field is also sometimes called the ChargeNumber.
Your "Charge ANI" reference is probably just a variant of that terminology.
In recent years, Least Cost Routing carriers have become more creative with
their efforts to commit access charge fraud when terminating calls. One of
the more popular methods they used initially is to stuff the BillingNumber
field with a number that is local in scope, then pass through the actual
correct ANI of the caller. This results in met expectations for the caller
and the called party, and viola! No access charges. Or so they argued.
However, some of the more spectacular CLEC failures (Global NAPS,
CommPartners) were directly caused by the FCC and courts disagreeing that
this actually let the carrier out of their access charge obligations to the
big ILECs. This eventually led to the FCC's decree that the actual physical
location of the calling and called parties was to be used for determining
jurisdiction.
Therefore, in the wake of those failures, LCR carriers now often will stuff
the ANI as a number with local scope, and stuff the BillingNumber to match
that. Without the actual caller's ANI to compare to, the terminating
carrier does not have an easy way to see where the call actually originates
to prove that the BillingNumber is fraudulent. This is an issue that we've
all been dealing with for several years now, and I am hopeful that the FCC's
recent ICC order last year will eventually bring this madness to a close, as
access charges are phased down and then out. There will no longer be any
incentive for carriers to stuff the ANI or the ChargeNumber to avoid access
charges, which at least for us will be a big headache avoided. There are
many tangential issues that are caused for the terminating carrier when this
happens, including LCR carriers terminating toll calls into the local
tandems improperly, which throws off trunk provisioning and we've seen
several cases where calls just don't complete properly through the local
tandem when the LCR carrier sends them there and they aren't actually local.
This results in customer displeasure on the terminating end, as the
terminating CLEC's subscribers can come to feel that they didn't have those
issues before they left the ILEC.
Although we have long wished for a SIP field for billingnumber, the solution
is likely to look different than that. With the phasing out of access
charges, the entire concept of billingnumber in the carrier world is
becoming obsolete. The fact is, the originating carrier knows who to bill
for the call; they can look to the originating trunkgroup for that
regardless of ANI. LD carriers may do the same. In an RCF situation, your
switch will capture the "OrigDialedNumber", which can be used to determine
who to bill for the RCF scenario that started this thread. Therefore, the
primary purpose of the BillingNumber field is for intercarrier compensation,
and when that's gone there is likely to be no practical use for the
BillingNumber field anymore.
So the reason that the ANI is used to determine jurisdiction is that the FCC
has decreed that is How To Do It for access cost billing. Business process
dictates that carriers need to pass along those access costs to their
wholesale subscribers, and so the methodology flows to how you're billed. I
predict that as access charges fade away, so too will any distinction of
local/nonlocal calling. You're likely to see more wholesale flat-rate
offerings, where the jurisdiction of the call doesn't matter at any level.
That's a few years away, but it's coming. We revised our wholesale rates
last year to remove the distinction between intrastate and interstate LD
termination. The change going into effect THIS year is parity between
interstate and intrastate access cost rates. That's a huge change that was
sorely needed, and I suspect it will bring down retail and wholesale
intrastate LD rates when that takes effect in July. We all had to revise
our access tariffs last July, and are having to do so again this July to
comply. Here in Florida, many carriers are going from around a 0.09 rate
for intrastate access down to around 0.01 to match the FCC-approved
interstate access rates, which will then phase down to zero over the next
several years. That's a big savings for you and end users alike, and
frankly a big legal headache that is finally over for those CLECs who were
not taking advantage of that inter/intra rate disparity to gouge other
carriers on intrastate access.
So in the end, the "less mature" SIP model where only the ANI is passed may
win the day when BillingNumber becomes obsolete. Who knew?
Mike
Mike Ray, MBA, CNE, CTE
Astro Companies, LLC
11523 Palm Brush Trail #401
Lakewood Ranch, FL 34202
DIRECT: 941 600-0207
http://www.astrocompanies.com
-----Original Message-----
From: Nathan Anderson [mailto:nathana at fsr.com]
Sent: Monday, March 18, 2013 7:50 PM
To: 'Mike Ray'; 'voiceops at voiceops.org'
Subject: RE: [VoiceOps] Call Forwarding is broken; or, when CF meets LCR
On Monday, March 18, 2013 12:40 PM, Mike Ray <> wrote:
> Many factors went into our decision on how to handle these situations.
> Regulation is one of those; it is illegal to stuff the ANI to change
> the jurisdiction of the call although we know that many carriers/ITSPs
> do that anyway.
Perhaps this is splitting hairs (and I admittedly have not read the actual
language of the law(s) you are citing), but I would argue that in my
example, if I were to "stuff" the ANI in the way I describe (take called
party/forwarder's number and use that for ANI), I wouldn't be doing so to
necessarily change the jurisdiction of the call to be in my favor; there
would be scenarios in which it would be advantageous for me from a billing
perspective to *not* do that. I would, in fact, be doing it to actually set
the *correct* jurisdiction of that leg of the call, regardless of whether it
happens to be in my favor or not. Using the caller's ANI as ANI for the
forwarded leg is causing the *incorrect* jurisdiction to be selected, but is
the only way to get the correct Caller-ID passed through end-to-end. *That*
is the frustrating part.
> However, as you noted, if you stuff the ANI it will negatively affect
> your customer's perception of your service, since that is not how a
> PSTN forward would be handled.
Thus, a disincentive to me and other reputable ITSPs to engage in such
activity.
> The real issue is that the PSTN, both at the SS7 and PRI signalling
> levels, recognizes both the ANI and the BillingNumber fields for any
> call but SIP does not have that construct. The "PSTN-proper" way to
> handle this would be to pass the original caller's ANI for CallerID,
> but to pass your forwarded customer's BillingNumber. However, SIP
> just has ANI and that's it.
Actually, as I understand it, PSTN doesn't "automatically" pass the caller's
ANI for CNID, which is another reason to consider the "industry-standard"
methods of SIP->SS7 interop to be broken. There are, to my knowledge,
*three* separate fields:
1) CNID
2) ANI
3) BTN
(Then there is also ANI2, but that's not terribly relevant to this
discussion, I don't think.)
I have also heard #2 and #3 referred to as "ANI" and "Charge ANI"
respectively. What I have never quite understood is what the relationship
between the two are, and if someone could explain that, I would be grateful.
However, I am quite sure that CNID does *not* have to match ANI, and I would
be quite content if, instead of adding a new field to the SIP header for BTN
(leaving CNID+ANI the way it is now), ANI+BTN were instead combined, CNID
was split out into its own thing, and new field was added instead for either
CNID or ANI+BIN. (Of course, ultimately, it would be best for all 3 to be
separate if that is how they are signalled on SS7.)
> So the way we decided to handle this in the final analysis is that we
> already bill our wholesale ITSP subscribers for outbound calls on two
> levels: one for local and the other for non-local. We use the actual
> ANI of the calling party to determine this jurisdiction
> (local/non-local) because that is what will trigger the terminating
> carrier's access billing to us, and we bill our ITSP customer the
> proper rate based upon that, regardless of the forwarding-customer's
number.
Right, and that's how everybody seems to be doing it. But, again, the
problem I'm pointing out is that using the calling party's number to
determine this juristiction is horribly broken and wrong, IMO.
--
Nathan Anderson
First Step Internet, LLC
nathana at fsr.com
March 21, 2013
Call Forwarding is broken; or, when CF meets LCR
by paul@timmins.net
In SS7 the parameters are called:
CallingPartyNumber
ChargeNumber
You also commonly see:
GenericAddressParameter (if the number is ported into you, the call will enter your switch with the CalledPartyNumber of your LRN, with the real destination number hidden in the Generic Address Parameter)
GenericName (uncommon in US, common in Canada, this is used to send the caller ID with name data inband (typically you do a TCAP dip to a special point code set up by your SS7 provider that redirects your query to the correct carrier CNAM database using Global Title Translation) but in Canada, they don't do this, so you get your caller ID data this way)
JurisdictionalInformationParameter (a/k/a JIP - This is the NPA/NXX homed off the originating switch (generally switches use the LRN's NPA/NXX specifically), so you can track usage back to the originating LEC even if CallingPartyNumber and ChargeNumber are blank)
Commonly CallingPartyNumber is your "Caller ID" or CPN
Commonly ChargeNumber is your ANI/BTN
If you send a call to an IXC across a tandem, they'll typically be screening your subscriber based on the ChargeNumber. And the ChargeNumber is supposed to be sent even if the customer sends no CallingPartyNumber So I'd refer to this as the ANI.
However, every wholesale carrier termination product I've seen bills your call jurisdiction based on the location of your switch (even our SS7 based interconnects) and that's what appears in our CDRs (even when we can otherwise specify ChargeNumber) so the ChargeNumber is ignored for that jurisdictional information, so this may all be a moot point unless you're handing the call off directly to another carrier.
-Paul
On Mar 20, 2013, at 23:05 , Nathan Anderson <nathana at fsr.com> wrote:
> Mike,
>
> I haven't meant to leave your message sitting without a reply for so long; my apologies. :) It's been a hectic last couple of days.
>
> I'm not sure where I got the idea that CNID was a separate field from ANI, then. Perhaps it was from everybody who kept repeating the mantra "ANI is *not* Caller-ID. I repeat: ..." I mean, I know they're not the same because Caller-ID is technically the name for a service provided over normal loop-start lines that is modulated/transmitted by the local switch, but some of the stuff you read leads you to believe that calling party number and the ANI are two separate things, that the local switch doesn't consult ANI for the number to display for Caller-ID, and that the two can differ for any given call.
>
> There seems to be so much misinformation and conflicting information out there; it's crazy:
>
> http://en.wikipedia.org/wiki/Caller_ID ("However, CNID and ANI are not the same thing.")
> http://www.egyed.com/faq/cid.htm ("Thus while ANI is similar to CALLER-ID and may provide the same information, they are actually two different services and ANI information is not necessarily the same as what will appear on a CALLER-ID display."
> http://www.telcomp.com/cidani.html (not sure what's up with the large type...)
> http://docs.voxeo.com/ccxml/1.0-final/frame.jsp?page=anispoofing_ccxml10.htm ("One common misconception these days is that ANI and Caller ID to be used synonymously. This is *not* the case.")
> http://wiki.docdroppers.org/index.php?title=ANI_and_Caller_ID_Spoofing (suggests ANI transmission via PRI only changes the "CPN", and not the "ANI")
>
> So who can help sort this out for us? It seems to me that most people in these articles are using ANI and BTN synonymously, and treating CNID/CPN as a different thing entirely. It's very confusing when different people are throwing around different terms for (possibly) the same thing, and then others are re-using some of those same terms to refer to different things. When I call the MCI ANI readback number (800-437-7950), I hear "calling ANI" and "charge ANI" read back to me. What do they mean? What is what?
>
> You'd definitely know the FCC regs better than me, so I trust you on this, but still...using ANI to determine jurisdiction of ALL call legs in an RCF scenario just seems completely upside-down to me. In an RCF scenario, there are going to be *two* carriers asking for compensation: the one for the originally-called party, and then one for the final destination number. The originally-called party's carrier is going to charge the caller's carrier, and the carrier for the final destination is going to charge the originally-called party's carrier. For the first leg of the call, of course: use the ANI of the caller. But for the second leg, that doesn't seem fair or right. The originally-called party's carrier should charge him/her for the forwarded call, and that charge should be based on what the call would have cost if the originally-called party had *dialed the CF target number themselves* without a forward in place. Isn't that just common-sense?
>
> I was not aware that ICC was going to be dissolved permanently; very interesting.
>
> Thanks for the very informative posts,
>
> --
> Nathan Anderson
> First Step Internet, LLC
> nathana at fsr.com
>
> -----Original Message-----
> From: Mike Ray [mailto:mike at astrocompanies.com]
> Sent: Monday, March 18, 2013 10:42 PM
> To: Nathan Anderson; voiceops at voiceops.org
> Subject: RE: [VoiceOps] Call Forwarding is broken; or, when CF meets LCR
>
> Hi Nathan,
>
> I agree that nobody will likely ever get into trouble for doing as you
> describe; stuffing the CallerID to match your subscriber's BTN as the call
> passes through. However, the FCC defines proper jurisdiction of a call as
> the two actual endpoints being connected, regardless of what's "in the
> middle". So much for hairsplitting, but as you mentioned there is a
> disincentive for you to do that anyway because of customer perception.
>
> On your "industry standard fields" question, there may be a terminology
> difference here, but in the Class 5 switching SS7 (and even PRI) world there
> are two fields. One is intended to identify the calling party (ANI) which
> is sometimes also called CPN, and the other to identify the billed party and
> jurisdiction (BillingNumber), sometimes called BTN. In the Class 4 world,
> the use of the term ANI is more prevalent, while the same field in the Class
> 5 world is sometimes called CallingNumber. But it is in fact the same field
> as ANI. The BillingNumber field is also sometimes called the ChargeNumber.
> Your "Charge ANI" reference is probably just a variant of that terminology.
>
> In recent years, Least Cost Routing carriers have become more creative with
> their efforts to commit access charge fraud when terminating calls. One of
> the more popular methods they used initially is to stuff the BillingNumber
> field with a number that is local in scope, then pass through the actual
> correct ANI of the caller. This results in met expectations for the caller
> and the called party, and viola! No access charges. Or so they argued.
>
> However, some of the more spectacular CLEC failures (Global NAPS,
> CommPartners) were directly caused by the FCC and courts disagreeing that
> this actually let the carrier out of their access charge obligations to the
> big ILECs. This eventually led to the FCC's decree that the actual physical
> location of the calling and called parties was to be used for determining
> jurisdiction.
>
> Therefore, in the wake of those failures, LCR carriers now often will stuff
> the ANI as a number with local scope, and stuff the BillingNumber to match
> that. Without the actual caller's ANI to compare to, the terminating
> carrier does not have an easy way to see where the call actually originates
> to prove that the BillingNumber is fraudulent. This is an issue that we've
> all been dealing with for several years now, and I am hopeful that the FCC's
> recent ICC order last year will eventually bring this madness to a close, as
> access charges are phased down and then out. There will no longer be any
> incentive for carriers to stuff the ANI or the ChargeNumber to avoid access
> charges, which at least for us will be a big headache avoided. There are
> many tangential issues that are caused for the terminating carrier when this
> happens, including LCR carriers terminating toll calls into the local
> tandems improperly, which throws off trunk provisioning and we've seen
> several cases where calls just don't complete properly through the local
> tandem when the LCR carrier sends them there and they aren't actually local.
> This results in customer displeasure on the terminating end, as the
> terminating CLEC's subscribers can come to feel that they didn't have those
> issues before they left the ILEC.
>
> Although we have long wished for a SIP field for billingnumber, the solution
> is likely to look different than that. With the phasing out of access
> charges, the entire concept of billingnumber in the carrier world is
> becoming obsolete. The fact is, the originating carrier knows who to bill
> for the call; they can look to the originating trunkgroup for that
> regardless of ANI. LD carriers may do the same. In an RCF situation, your
> switch will capture the "OrigDialedNumber", which can be used to determine
> who to bill for the RCF scenario that started this thread. Therefore, the
> primary purpose of the BillingNumber field is for intercarrier compensation,
> and when that's gone there is likely to be no practical use for the
> BillingNumber field anymore.
>
> So the reason that the ANI is used to determine jurisdiction is that the FCC
> has decreed that is How To Do It for access cost billing. Business process
> dictates that carriers need to pass along those access costs to their
> wholesale subscribers, and so the methodology flows to how you're billed. I
> predict that as access charges fade away, so too will any distinction of
> local/nonlocal calling. You're likely to see more wholesale flat-rate
> offerings, where the jurisdiction of the call doesn't matter at any level.
> That's a few years away, but it's coming. We revised our wholesale rates
> last year to remove the distinction between intrastate and interstate LD
> termination. The change going into effect THIS year is parity between
> interstate and intrastate access cost rates. That's a huge change that was
> sorely needed, and I suspect it will bring down retail and wholesale
> intrastate LD rates when that takes effect in July. We all had to revise
> our access tariffs last July, and are having to do so again this July to
> comply. Here in Florida, many carriers are going from around a 0.09 rate
> for intrastate access down to around 0.01 to match the FCC-approved
> interstate access rates, which will then phase down to zero over the next
> several years. That's a big savings for you and end users alike, and
> frankly a big legal headache that is finally over for those CLECs who were
> not taking advantage of that inter/intra rate disparity to gouge other
> carriers on intrastate access.
>
> So in the end, the "less mature" SIP model where only the ANI is passed may
> win the day when BillingNumber becomes obsolete. Who knew?
>
> Mike
>
> Mike Ray, MBA, CNE, CTE
> Astro Companies, LLC
> 11523 Palm Brush Trail #401
> Lakewood Ranch, FL 34202
> DIRECT: 941 600-0207
> http://www.astrocompanies.com
>
>
> -----Original Message-----
> From: Nathan Anderson [mailto:nathana at fsr.com]
> Sent: Monday, March 18, 2013 7:50 PM
> To: 'Mike Ray'; 'voiceops at voiceops.org'
> Subject: RE: [VoiceOps] Call Forwarding is broken; or, when CF meets LCR
>
> On Monday, March 18, 2013 12:40 PM, Mike Ray <> wrote:
>
>> Many factors went into our decision on how to handle these situations.
>> Regulation is one of those; it is illegal to stuff the ANI to change
>> the jurisdiction of the call although we know that many carriers/ITSPs
>> do that anyway.
>
> Perhaps this is splitting hairs (and I admittedly have not read the actual
> language of the law(s) you are citing), but I would argue that in my
> example, if I were to "stuff" the ANI in the way I describe (take called
> party/forwarder's number and use that for ANI), I wouldn't be doing so to
> necessarily change the jurisdiction of the call to be in my favor; there
> would be scenarios in which it would be advantageous for me from a billing
> perspective to *not* do that. I would, in fact, be doing it to actually set
> the *correct* jurisdiction of that leg of the call, regardless of whether it
> happens to be in my favor or not. Using the caller's ANI as ANI for the
> forwarded leg is causing the *incorrect* jurisdiction to be selected, but is
> the only way to get the correct Caller-ID passed through end-to-end. *That*
> is the frustrating part.
>
>> However, as you noted, if you stuff the ANI it will negatively affect
>> your customer's perception of your service, since that is not how a
>> PSTN forward would be handled.
>
> Thus, a disincentive to me and other reputable ITSPs to engage in such
> activity.
>
>> The real issue is that the PSTN, both at the SS7 and PRI signalling
>> levels, recognizes both the ANI and the BillingNumber fields for any
>> call but SIP does not have that construct. The "PSTN-proper" way to
>> handle this would be to pass the original caller's ANI for CallerID,
>> but to pass your forwarded customer's BillingNumber. However, SIP
>> just has ANI and that's it.
>
> Actually, as I understand it, PSTN doesn't "automatically" pass the caller's
> ANI for CNID, which is another reason to consider the "industry-standard"
> methods of SIP->SS7 interop to be broken. There are, to my knowledge,
> *three* separate fields:
>
> 1) CNID
> 2) ANI
> 3) BTN
>
> (Then there is also ANI2, but that's not terribly relevant to this
> discussion, I don't think.)
>
> I have also heard #2 and #3 referred to as "ANI" and "Charge ANI"
> respectively. What I have never quite understood is what the relationship
> between the two are, and if someone could explain that, I would be grateful.
> However, I am quite sure that CNID does *not* have to match ANI, and I would
> be quite content if, instead of adding a new field to the SIP header for BTN
> (leaving CNID+ANI the way it is now), ANI+BTN were instead combined, CNID
> was split out into its own thing, and new field was added instead for either
> CNID or ANI+BIN. (Of course, ultimately, it would be best for all 3 to be
> separate if that is how they are signalled on SS7.)
>
>> So the way we decided to handle this in the final analysis is that we
>> already bill our wholesale ITSP subscribers for outbound calls on two
>> levels: one for local and the other for non-local. We use the actual
>> ANI of the calling party to determine this jurisdiction
>> (local/non-local) because that is what will trigger the terminating
>> carrier's access billing to us, and we bill our ITSP customer the
>> proper rate based upon that, regardless of the forwarding-customer's
> number.
>
> Right, and that's how everybody seems to be doing it. But, again, the
> problem I'm pointing out is that using the calling party's number to
> determine this juristiction is horribly broken and wrong, IMO.
>
> --
> Nathan Anderson
> First Step Internet, LLC
> nathana at fsr.com
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
March 21, 2013
711 relay
by brandon@kamikos.com
We used 933 to verify 911 info, leaving 811 for OneCall utility locates.
Carlos Alvarez <carlos at televolve.com> wrote:
>On Wed, Mar 20, 2013 at 7:12 PM, Mike Ray <mike at astrocompanies.com> wrote:
>
>> Are you sure that your CLEC provider isn't doing this for you? We do.
>> CLECs are required to provide this service, and the translations happen in
>> our switch when you send us an x11 call. So you shouldn't have to do
>> anything.
>>
>
>I can tell you that if we send 811 to Vitelity, they just read back our
>CID. We, and they, use this for testing 911 systems. We have the
>customers dial 811 to verify the 911 CID is right. Which in light of
>today's conversation is clearly not legal, though arguably far more useful
>than having someone come out and mark utility lines.
>
>I have not tried sending 711 to any of our carriers. They are all
>SIP-based and I have no idea how they will handle it, but I'm going to try
>it.
>
>--
>Carlos Alvarez
>TelEvolve
>602-889-3003
>
>_______________________________________________
>VoiceOps mailing list
>VoiceOps at voiceops.org
>https://puck.nether.net/mailman/listinfo/voiceops
March 21, 2013
711 relay
by nathana@fsr.com
Good to know; thanks.
I also just learned of a different IETF standard, V.151, that *is* precisely to TDD what T.38 is to fax.
I've never heard of "V.151 support" as an advertised feature in ATAs, nor have I heard of any IP<->PSTN carriers advertising V.151 gateways, either. Anyone know something about this? Anybody doing it?
-- Nathan
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins
Sent: Wednesday, March 20, 2013 3:22 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] 711 relay
I've used TDDs over G711 for an extended period of time. They work fine,
because there's no need to maintain an idle tone in the conversation.
It's just FSK.
On 03/20/2013 06:10 PM, Nathan Anderson wrote:
> This is another great question, and one that I was also wondering about.
>
> I know that T.140 exists, but it is not clear to me...
>
> 1) ...whether it is considered the analogue of what T.38 is in the FoIP world (T.38 is to T.30 as T.140 is to TDD?)
> 2) ...if #1 is true, whether any consumer-grade ATAs support T.140 in this capacity, and/or whether any IP->PSTN term providers run T.140-to-TDD gateways themselves.
>
> T.38 basically encapsulates T.30 events, messages, and data inside of IP datagrams, but from what little I've read about T.140, it sounds more like a protocol designed to replace TDD/TTY, not encapsulate it. Thus, gatewaying TDD to T.140 and vice-versa is a bit of a different proposition than T.38 gatewaying.
>
> Given that TDD is relatively low bitrate, I'd wager that simply doing G.711 passthrough would work the majority of the time. We have had some success hooking up telephone-based security systems (ADT) through our network after switching the system over to using FSK instead of DTMF (DTMF would get intercepted by the ATA and translated to out-of-band RTP events, which neither side apparently liked too much; the FSK encoding seems to work flawlessly), and that is similarly low bitrate, but calls being generated by such systems are also relatively short.
>
> -- Nathan
>
> -----Original Message-----
> From: Eric Fort [mailto:eric.fort at gmail.com]
> Sent: Wednesday, March 20, 2013 2:58 PM
> To: Nathan Anderson
> Cc: voiceops at voiceops.org
> Subject: Re: [VoiceOps] 711 relay
>
> 711 poses an interesting proposition for VoIP as relay services go both ways. It's not always a voice caller dialing 711 but TDD calls as well. Generally inbound calls get sorted by some sort of auto attendant where calls that detect some form of modem tone (TDD) signaling go to one operator and other calls are voice. While the TDD traffic is relatively low bit rate fsk it's still modem traffic conveying digital rather than analogue data. How is the TDD case being handled?
>
> Eric Fort
> FortConsulting
>
>
> On Wed, Mar 20, 2013 at 2:25 PM, Nathan Anderson <nathana at fsr.com> wrote:
>
>
> Question for other ITSPs out there: what are you doing for 711 TTY relay services?
>
> I know so little about this area it's sad. Are we supposed to either staff our own relay staff, pass them off to a third-party relay service, or pass the calls off to a state-provided service? Can this be done with a third-party service a-la what 911Enable and friends do for 911 PSAP routing? What companies out there provide services like this?
>
> If the states you provide service in have an 800 number for connecting to a state-run relay service, can I simply translate 711 to the appropriate 800 number and terminate the 800 call as I normally would?
>
> Thanks,
>
> --
> 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
March 21, 2013
711 relay
by nathana@fsr.com
Hmm. We have access to Dash/iNetwork through a reseller, but it's only provisioned for E911. I might have to get in touch with them and ask if it would be possible to have N11 enabled on our account...
-- Nathan
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Ken Mix
Sent: Wednesday, March 20, 2013 4:34 PM
To: Carlos Alvarez; voiceops at voiceops.org
Subject: Re: [VoiceOps] 711 relay
We have a termination trunk to bandwidth.com specifically for 511,711 & 811 routing. This was a legacy product we that was migrated over when they acquired Dash CS so I'm not sure if they still offer it as a standalone product, but it is a lot cleaner than the manual translations we had in place before.
Ken
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Carlos Alvarez
Sent: Wednesday, March 20, 2013 5:01 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] 711 relay
On Wed, Mar 20, 2013 at 3:23 PM, Paul Timmins <paul at timmins.net> wrote:
http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-257293A1.pdf
That's between you and your regulatory agencies you feel regulate you, but I consider it a mandate if for no other reason than "I have cables under there and I don't want my customers digging them up".
Ugh, a mandate I was unaware of. For an ITSP with customers nationally, that's going to be a bit of a challenge.
How do most of you handle routing this?
--
Carlos Alvarez
TelEvolve
602-889-3003
March 21, 2013
711 relay
by nathana@fsr.com
How do you do the translations? Do you simply look at the number of the caller and assume that they are calling from the state that their NPA belongs to? What if the customer has a DID from one state but is physically located in another? Do you consult their on-file E911 address to determine what number to send the call to?
-- Nathan
-----Original Message-----
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Paul Timmins
Sent: Wednesday, March 20, 2013 5:19 PM
To: voiceops at voiceops.org
Subject: Re: [VoiceOps] 711 relay
On 03/20/2013 07:01 PM, Carlos Alvarez wrote:
On Wed, Mar 20, 2013 at 3:23 PM, Paul Timmins <paul at timmins.net> wrote:
http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-257293A1.pdf
That's between you and your regulatory agencies you feel regulate you, but I consider it a mandate if for no other reason than "I have cables under there and I don't want my customers digging them up".
Ugh, a mandate I was unaware of. For an ITSP with customers nationally, that's going to be a bit of a challenge.
How do most of you handle routing this?
The Common Ground Alliance publishes a state by state list here: http://www.call811.com/state-specific.aspx
They're all toll free numbers and usually 1 number per state so digit translations are easy.
March 21, 2013