Echo on SIP trunk

busster8
Posts: 388
Member Since:
2006-06-25

We are getting echo on our sip trunks. Is it possible that IAX2 trunks would resolve this? Since IAX is a native protocol to Asterisk, is there a advantage of IAX trunking over SIP when it comes to this?



telecomchina
Posts: 29
Member Since:
2008-03-07
it is better to check where is the echo from?

for example, you could use a normal sip ATA or softphone to check if the sip trunk has echo?

if the echo is from your trixbox, it is better to use echo cancel module or use some ATA box.

Luis

http://www.telecomchinasourcing.com



onecomms
Posts: 289
Member Since:
2006-10-26
Do you have echo on internal

Do you have echo on internal calls?
If so its an internal equipment/network issue.

If you have echo only on external then its a problem with your DSL line (assuming thats what you have)
try doing a ping to your trunk provider and seeing what the latency is, the higher the ping times, the worse the call quality is likely to be.

changing from IAX to SIP will not solve your problem - its sounds more likely to be a network issue

--

_________________________________
Andy Thompson
1comms
http://www.1comms.co.uk
sales@1comms.co.uk



busster8
Posts: 388
Member Since:
2006-06-25
Echo

No echo on internal calls. No echo on analog calls. Echo only on SIP calls. Assume latency is the issue. I have been told echo cancellation has no effect on sip calls. T-1 service being used and only 4 users on the system. We are looking at other trunk providers now.



SkykingOH
Posts: 9541
Member Since:
2007-12-17
Load MTR on the system to

Load MTR on the system to test for packet loss to your provider.

yum install mtr

then mtr your.providers.server.name

--

Scott

aka "Skyking"



busster8
Posts: 388
Member Since:
2006-06-25
mtr results

mtr results show avg ping of 45.3 on the worst host site. All other hosts were below this. One site had a worst ping of 208.9, but the avg was 8.3. 0 packet loss on all hosts. Ran this for 500 pings.



onecomms
Posts: 289
Member Since:
2006-10-26
I think you will find that

I think you will find that any latency over 100ms is going to give you problems!
The times for each host need to be pretty consistant too - if you have varying ping times for a host, then this is usually jitter, which is often the cause of SIP echo or dropped voice packets.

MTR should give you an idea where the problem lies, but in all honesty you may have to change your internet connection, your ISP or your VoIP provider.

--

_________________________________
Andy Thompson
1comms
http://www.1comms.co.uk
sales@1comms.co.uk



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.