Trashy audio on ported number

WhyADuck

I need to be just a little vague on the details on this one, but the issue is that after porting a number to an upstream provider, on most incoming calls the audio is “trashy” and distorted. It is not the connection to the provider because the issue only affects the newly ported number. The best I can describe it is that the ringtone the caller hears is quite “trashy” and then both the caller and the called party hear audio that sort of sounds like someone is talking underwater or through an audio distortion box. I have recorded test calls at my switch and this is how they are being received at the switch, it is not the connection to the endpoint. The upstream provider (to which the number was ported) doesn’t seem to know what is causing this to happen (not yet anyway), but it doesn’t happen with their other numbers.

I just wondered if anyone here has experienced anything like this, and if so did you ever figure out the cause and/or get it fixed? I should mention that not all calls are affected, and it seems more likely to happen during higher usage periods (almost 100% certain it will happen then) but can happen at any time of day.

px_eliezer_

WhyADuck It is not the connection to the provider because the issue only affects the newly ported number.

Thoughts:

1) Each number has to be provided by a CLEC.

(Assuming this is a VoIP situation).

A VoIP provider might not happen to use the same CLEC for each of your numbers.

For example, suppose your existing numbers are serviced by the good CLEC formerly called XO (now part of Verizon) while your new number was assigned to a not-quite-as-good CLEC (which your provider might be using because it’s cheaper, or because of porting logistics, or because not all CLEC’s can serve all local exchanges).

You MIGHT be able to check the actual carriers with this lookup.
https://freecarrierlookup.com/
However, very recent ports might not show up.

2) Related: Each ported number is related to an LRN (location routing number) as you know. The LRN system can introduce increased routing complexity, and some companies try to tweak the system to reduce costs (LCR: Least Cost Routing).
https://sangoma.com/blog/understanding-location-routing-numbers/

3) It may be none of that, if this is quite recent it’s possible that the port is still somewhat incomplete….

In simpler answer to your question, I’ve done a lot of ports of all sorts, but fortunately have not run into voice quality issues.

Stewart

WhyADuck Is the problematic number in the same country as the good ones?

WhyADuck The best I can describe it is that the ringtone the caller hears is quite “trashy”

Is your system “playing” the ringtone (183 Progress or 180 Ringing with media)? If not (ringtone is generated by provider or earlier), then it’s clear that the problem is not at your end and you should open a ticket with them.

If your system is generating the ringtone, do you have a way (for testing) to get it out of the loop? For example, by sending 180 without media, or (if supported by provider) setting up call forwarding at their end.

WhyADuck

px_eliezer_ Tank you for the detailed response. I am definitely using the same CLEC for all the numbers, and the link you gave does show the correct carrier. I have n way of knowing if they are doing something strange with the routing though. It is possible (though I do not think likely) the port is not fully complete, if so I can hope this issue will resolve itself on its own.

WhyADuck

Stewart Thanks for the response. The new numbers are not only in the same country, they are in the same U.S. rate center as the good ones.

As for the ringtone, It’s doing whatever FreePBX does on a normal PJSIP trunk. Which I realize is probably not very helpful but I will put it this way, I made a bunch of test calls and in a very few cases I heard no ringtone at all and yet the called extension still rang, and the actual voice audio was still trashy most of the time. I would guess that when I did not hear the ringtone the call might have been going through Google Voice, which is somewhat notorious for not playing ringtone on calls to VoIP numbers, in part because I did not think much of it when it happened (because I am used to that happening with Google Voice). I am fairly certain that calls from non-GV numbers always played the ringtone, and I am pretty sure that is generated by FreePBX. And if there is a way to disable the ringtone in FreePBX, I’m not aware of it offhand.

But in any case other tests have pretty conclusively shown that the issue is upstream of me. The CLEC is aware of the problem but the last time I communicated with them (about a week ago maybe) they seemed somewhat stumped, which is why I was wondering if this has happened to anyone else - I was hoping maybe I could suggest something that might cause this, that they could then investigate.

DWDM

px_eliezer_ Yes and if the free carrier llookup site sometimes does not update same day -ain that instance carrierlookup.com does update almost immediately but the only allow you ONE free lookup per day and it is filtered by IP address. They allow you to purchase 1000 free lookups for a reasonable cost…

Davesworld

WhyADuck
Are you using an SBC such as Anveo Direct? When you moved your number, did it stay with the same CLEC? I know the ratecenter, but the actual CLEC?

I know with my setup with my PBX going through Anveo Direct, Anveo Direct ONLY handles the SIP signaling. The RTP streams are direct between my server and the CLEC in use. I have it set up to use the CLEC of the person I am calling if available on outgoing calls, so both their server and my server only connect to one CLEC between the two.

WhyADuck

Well the problem seems to have resolved itself, audio is good now. No idea what changed though.