This is SS7 so there is no SBC in the mix. We have a path to fix it yet my concern is they are not accepting E.164 properly and was curious how many other SS7 peers have this same issue From: Alihan Arica [mailto:alihanarica at yahoo.com] Sent: Wednesday, March 16, 2011 3:34 PM To: Chet Curry Subject: Re: [VoiceOps] Verizon and E.164 Hi Chet, I believe that you can ask them to strip off the preceeding 1 and/or +1 from the incoming INVITE request on their Session Border Controller; I am pretty sure that your signal first hits their Session Border Controller and these boxes have such ability. Sorry, I can not provide further more information since I don't like to commend any architecture that I did not work on before. Hope this helps! ________________________________ Alihan Arica Overland Park, KC, USA --- On Wed, 3/16/11, Chet Curry <CCurry at telovations.com<mailto:CCurry at telovations.com>> wrote: From: Chet Curry <CCurry at telovations.com<mailto:CCurry at telovations.com>> Subject: [VoiceOps] Verizon and E.164 To: "voiceops at voiceops.org<mailto:voiceops at voiceops.org>" <voiceops at voiceops.org<mailto:voiceops at voiceops.org>> Date: Wednesday, March 16, 2011, 11:57 AM 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? [cid:image001.png at 01CBE3F5.53C652B0] -----Inline Attachment Follows----- _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<http://us.mc393.mail.yahoo.com/mc/compose?to=VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops