Are the calls that fail originating from the losing carrier? i.e did the numbers port from XYZ Telecom and XYZ Telecom customers are having issues? I have seen instances where even though the numbers were ported they were still provisioned on the switches and would cause failures for on-net customers.
You can try opening a ticket from the originating carrier – for example if Verizon is the originating carrier duplicate a failing call from a cell or other number that you own and work it from that end. Rob From: cisco-voip [mailto:[email protected]] On Behalf Of Jason Aarons (AM) Sent: Monday, May 04, 2015 2:28 PM To: Robert Kulagowski; Cisco VOIP Subject: Re: [cisco-voip] Troubleshooting carrier issues That echelon does not exist. Keep calling the people your sending money to each month that is selling you a service, involve your account manager. Or find another carrier ☺ From: cisco-voip [mailto:[email protected]] On Behalf Of Robert Kulagowski Sent: Monday, May 4, 2015 2:02 PM To: Cisco VOIP Subject: [cisco-voip] Troubleshooting carrier issues We recently ported numbers from PRI to a SIP service provider. Probably 99% of the calls work, but sometimes the calling party hears, "The number you've dialed is not in service". Well, it is, because the DN gets calls. And sometimes a call back works. Or a call to the main number. But the issue is that it's persistent, and all of the numbers are in the same range. The gaining carrier has told us that they're "broadcasting" the range in the big database in the sky, which is why we get calls. The losing carrier says that the numbers were ported away, and that the LNP Toolkit (whatever that it, but I'm guessing it makes dips against SS7) shows the "point code" is our new carrier. When we provide date/time, calling party and called party numbers, the new carrier says that they never got the call, which of course is why my logs don't show anything; there was nothing for them to send me. Thoughts on how to proceed? How do I open a trouble ticket at the "above the carrier" echelon? Sheesh. _______________________________________________ cisco-voip mailing list [email protected]<mailto:[email protected]> https://puck.nether.net/mailman/listinfo/cisco-voip itevomcid
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
