[cisco-voip] Troubleshooting carrier issues

[Jose Colon II]

We had a issue like this where some calls would make it and then randomly a
call would get a "The number you've dialed is not in service" message. What
the issue was after 3 months of searching was that one of the trunks
between the carriers was being over utilized. So a call would get through
sometimes and then get a busy or error messages depending on where the call
originated.

Hope that helps. Took us forever to get figured out

On Mon, May 4, 2015 at 1:02 PM, Robert Kulagowski <rkulagow at gmail.com>
wrote:

> 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
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150504/27c9ddbe/attachment.html>