[VoiceOps] Verizon and E.164

[Spencer]

What type of product are you using for SS7 to/from SIP translation? There is a 
good chance that your SS7 to SIP translation device may have the ability to 
manipulate ANI and DNIS as required. In the application we use on our net the 
M3UA server manages E.164 vs 10 Digit National decisions quite well.

Also, do you plan to use this SS7 route for any international termination? If 
not, it might be as simple as limiting all calls over that trunk group to 10 
digit ANI/DNIS outbound then prefix a (+)1 on the inbound.

Thanks,
 Spencer




*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?


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