VoIP echo issue ...
-
Also what codec do you have setup on your PBX install and the phones?
-
-
-
@BraswellJay isn't ulaw g711? And not g729.
G729, also requires that you be licensed for it.
*Typo fixed
-
@DustinB3403 said in VoIP echo issue ...:
@BraswellJay isn't ulaw g711? And not g729.
G729, also requires that you be lice see for it.
ulaw is g711. That's the PCMU in the yealink config and the FreePBX config only allows ulaw.
Still I can take the other 3 codecs out of the phones as they aren't being used.
-
I would start with removing the codec's you don't use and leave PCMU and PCMA (g711).
Could be a codec conflict.
-
Not sure this matters, but why not ask - what kind of firewall do you have?
-
@Dashrender said in VoIP echo issue ...:
why kind of firewall do you have?
I assume you meant "what kind of firewall do you have?" and this is irrelevant as the routing is working, he's just getting a lot of echo.
@BraswellJay another question I have are the people reporting this all speaking with the same remote location/customer etc or a variety of remote numbers?
-
@DustinB3403 said in VoIP echo issue ...:
@Dashrender said in VoIP echo issue ...:
why kind of firewall do you have?
I assume you meant "what kind of firewall do you have?" and this is irrelevant as the routing is working, he's just getting a lot of echo.
I agree I also don't think it is related but nonetheless it is a Meraki MX67.
It is the the same site that I posted this issue on a couple of weeks ago :
https://mangolassi.it/topic/20255/freepbx-skyetel-inbound-call-rejecting-unknown-sip-connection
but as you mentioned I don't appear to have any issues with the routing. Just this echo on a small number of calls.
@BraswellJay another question I have are the people reporting this all speaking with the same remote location/customer etc or a variety of remote numbers?
It is different in each case. Of the 3 instances that they have told me about they have all been different Caller IDs. Two of them have identified as the generic "Wireless Caller" on Caller Name and the third was simply a name of a city so I think it was likely a cell phone caller as well.
-
@BraswellJay Do you know if any of the remote callers were on speaker phone? I've had that cause issues, but generally speaking, having Echo Cancellation on fixes it.
-
@DustinB3403 said in VoIP echo issue ...:
@BraswellJay Do you know if any of the remote callers were on speaker phone? I've had that cause issues, but generally speaking, having Echo Cancellation on fixes it.
No I don't know if they were or not.
-
@BraswellJay You mentioned cell phones; by chance were they all on the same carrier? I know that is hard to determine but with my last carrier pretty much every incoming call issue we had (echo, packet dropping) turned out to be a Verizon cell phone on the other end. We reported to the carrier several times and they still never fixed it.
-
@jt1001001 said in VoIP echo issue ...:
We reported to the carrier several times and they still never fixed it.
Like screaming at a hurricane makes it stop flooding your house, Verizon just doesn't care.
-
@jt1001001 said in VoIP echo issue ...:
@BraswellJay You mentioned cell phones; by chance were they all on the same carrier? I know that is hard to determine but with my last carrier pretty much every incoming call issue we had (echo, packet dropping) turned out to be a Verizon cell phone on the other end. We reported to the carrier several times and they still never fixed it.
I don't know nor how to find out at the moment. I was guessing they were cell phones just based off of the caller name supplied on the incoming call. Two were "Wireless caller" (but different phone numbers) and the other had the name of a nearby city for the caller name so I was speculating that all 3 were cell phones but as to which carrier they are on I don't know.
-
We had the same problem with VitalPBX, and @ScottAlanMiller's suggestion, we made the Opus codec the highest priority and it resolved the issue for us. Maybe it is worth a try for you?
