[VoiceOps] Verizon and E.164

Thu Mar 17 11:28:59 EDT 2011

Thanks Paul and Scott.  I am not a SS7 guru by no means and the NOA may help.  I need to do a trace to see what I am sending to verizon to insure I am sending NOA of national.

________________________________________
From: voiceops-bounces at voiceops.org [voiceops-bounces at voiceops.org] On Behalf Of voiceops-request at voiceops.org [voiceops-request at voiceops.org]
Sent: Wednesday, March 16, 2011 4:50 PM
To: voiceops at voiceops.org
Subject: VoiceOps Digest, Vol 21, Issue 11

Send VoiceOps mailing list submissions to
        voiceops at voiceops.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://puck.nether.net/mailman/listinfo/voiceops
or, via email, send a message with subject or body 'help' to
        voiceops-request at voiceops.org

You can reach the person managing the list at
        voiceops-owner at voiceops.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of VoiceOps digest..."

Today's Topics:

   1. (no subject) (Mark Wiles)
   2. Re: Verizon and E.164 (Paul Timmins)

----------------------------------------------------------------------

Message: 1
Date: Wed, 16 Mar 2011 16:38:50 -0400
From: "Mark Wiles" <mwiles at akabis.com>
To: <voiceops at voiceops.org>
Subject: [VoiceOps] (no subject)
Message-ID: <033201cbe41a$29064330$7b12c990$@com>
Content-Type: text/plain; charset="us-ascii"

Does anyone have experience with VoIP Innovations (www.voipinnovations.com)?

Thanks!

Mark

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110316/ac24c843/attachment-0001.html>

------------------------------

Message: 2
Date: Wed, 16 Mar 2011 16:49:56 -0400
From: Paul Timmins <paul at timmins.net>
To: Scott Berkman <scott at sberkman.net>
Cc: voiceops at voiceops.org, 'Chet Curry' <CCurry at telovations.com>
Subject: Re: [VoiceOps] Verizon and E.164
Message-ID: <4D812274.7000102 at timmins.net>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

These are SS7 as he said earlier.

The compliant way in all cases would be to send the number without an
international outdial prefix and set the Nature of Address Indicator to
indicate if it's a national number, so:

01144207499000 would become

NAI: International Number: 44207499000

2485551212 would become
NAI: National Number: 2485551212

many switches will accept 011 if you set NAI as unknown, at least in the
US. Otherwise they assume unknown is in-country.

That's also the same in PRI, as it has a nature of address indicator,
and some of my customers actually use it as intended, shock horror. The
amount of random trash flowing over the D channel of most of my
customers, however, belies the idea that most PRI CPE are sophisticated
enough to use NAI properly.

-Paul

On 03/16/2011 04:21 PM, Scott Berkman wrote:
>
> In E-164 format, 011 is not normally used on carrier trunks, at least
> in my experience.  National calls should be something like
> +1NPANXXXXXX.  An international call would never begin with +1 unless
> you start getting into the NANPA "International" destinations such as
> Canada and the Caribbean that share the 1 CC.  For example, if I send
> an international call to another major SIP trunking vendor, the URI
> would be +442074999000 (this is the US Embassy in London).
>
> I have never personally worked with Verizon's SIP trunks, but I would
> expect them to have a reasonably sophisticated rating engine that
> knows all of those details.  They should also have an interop or
> testing process and supporting documentation that goes over these
> different call flows and what they expect to see from you for each.
>
>                 -Scott
>
> *From:* voiceops-bounces at voiceops.org
> [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Chet Curry
> *Sent:* Wednesday, March 16, 2011 12:58 PM
> *To:* voiceops at voiceops.org
> *Subject:* [VoiceOps] Verizon and E.164
>
> Many carriers request that you send sip messaging using E.164
> compliant #'s.  We have a TDM/SS7 peering to Verizon and we tried
> sending calls to them with the "Calling" # in E.164 format.
>
> Unfortunately they see the call as International because there is a 1
> prepending the 10 digit #.  This makes no sense to me as international
> starts as 011.   Has anyone had this issue with Verizon or any other
> carrier?
>
> Description: signature2
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110316/c7d77a5a/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 56691 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20110316/c7d77a5a/attachment.png>

------------------------------

_______________________________________________
VoiceOps mailing list
VoiceOps at voiceops.org
https://puck.nether.net/mailman/listinfo/voiceops

End of VoiceOps Digest, Vol 21, Issue 11
****************************************