IP Office 500 - IP Phones echo issue

[edsopercng]

I have a customer w/ an IP 500 running 4.2.101104 having echo issues on IP phones. They have a VCM 32 and a PRI. They are using 2 x Adtran 1224ST POE switches to connect the phones. The PCs connect through the phones to access the network.

The echo occurs intermittently on various extentions, both inbound and outbound over the PRI. It only seems to happen over IP sets, the digital sets on the system do not have this issue

The switches and phones have VLANs configured and QOS configured. The circuit has been tested and the padding adjusted, the VCM has been replaced, PRI gain levels have been adjusted (to -4), and various network settings on the switches (LLDP disabled, Spanning Tree disabled, 100/full duplex speeds forced) have been changed, all to no effect. I will be replacing the IP500 control unit and the PRI card early next week in an attempt to solve this issue, though I'm not certain it will solve the problem. Does anyone else have any advice?

 

[tlpeter]

IF you have a 5610 or 20/21 then press the options button and look for call quality
Press that option when on a call
If you see jitter or delay then it is your network

Are you aware your customer is on an fieldtrail version ?
At this moment the fieldtrial is on 4.2(101110

ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[edsopercng]

Thanks for the network advice, I will check next time I'm on site.

Re: the firmware version, that version was installed to correct a specific issue. Avaya has not given any indication that this firmware should cause this issue. I have a case open with them, and they are aware of the firmware version, and no one has commenmted that it should be changed/updated.

 

[tlpeter]

Logical reason

Next week the new version will be available FYI
Echo can be a network issue but also analog trunks could be so there are a couple of reason for echo


ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[IPOfficeIreland]

intermittant voice quality problems are probably one of the worst problems to diagnose.

switch on port mirroring on the switch and set up wireshark and tracing until the fault occurs. This will tell you exactly what is wrong on the network.

Do the faults happen on 1 of the switches and not the other? You could try defaulting the switches and reprogramming and upgrading, may be a config error or bad firmware.

 

[BusinessPhoneSystems]

We have exactly the same with IP Dect on 4.2.x.

We have good local latancey etc but we are running over sip trunks and believe we have some lazy lines on the trunk side but we are still not convinced as it only seems to effect the IP Dect.

We have done a lot of work with SIP Trunks

http://www.alfred-ashley.co.uk

and have got SIP trunks to be a standard choice but problems like this are challenging.

Hence we would recommend a look at the trunk side as whilst it may plague IP handsets it appears they are more sensitive to trunk issues as well. However please note this is still Work In Progress.

http://www.alfred-ashley.co.uk

Business Phone Systems from Alfred Ashley - Voip and Avaya Digital Telephones for Offices in North West London

 

[IPOfficeIreland]

if you have intermittant voice issues you have a network problem and if using SIP then you have bandwidth issues, however, planning ahead, are your settings correct, what codec have you set to your IP DECT line and for extenesions?
Have you upgraded the IP DECT master unit (can't remember the 3 letter abbreviation), and handsets to current bug fixed version?

 

[edsopercng]

I replaced the 500 cabinet and the PRI board this morning, adjusted the gain levels on a few stations, and made a few network changes (changed speed back to auto, turned BPDUfilter on) and now calls are dropping. What else should I try?

 

[IPOfficeIreland]

edsopercng - you will have to do a network trace, you have basically replaced everything bar the POE switches.

 

[amriddle01]

Are you using the WAN/LAN 2 port and not the LAN port? As only the Wan port is tagged/marked for QoS.

ACS - IP Office Implement

 

[edsopercng]

TheTaker - I am currently running a wireshark trace. Am working w/ Adtran to analyze it.

amriddle01 - The Voice VLAN is connected to the WAN port. The LAN port goes to the data network/VLAN.

 

[edsopercng]

Also, I changed firmware to 4.2.4 this morning. Would that affect call dropping?

 

[edsopercng]

I changed the firmware to 4.2.101110 on the advice for my Avaya tier 3, and still no success. It seems as the the talkpath drops migrating between IP/non-ip (digital, PRI, etc.)

 

[Notsetinstone]

Do you have allow direct media path checked on the extensions? If so uncheck it reboot and try again

 

[edsopercng]

It's not checked.

 

[Bas1234]

Check if the IPO/phones are connected 100MbFD, it could be the they are 10MbHD.

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________

 

[MrIPO]

What PRI card P/N do you have in the IPO ?, has tier 3/4/5+ advised you to change the gain levels via the DTE port for the DSP's on the PRI card.


Mr IPO

ACA - Avaya Certified Associate
ACS - Avaya Certified Specialist
ACI - Avaya Certified Instructor

http://www.iporesource.com

 

[Maxwell1001]

did this ever get sorted out??

have you tried under system>vcm you can resolve echo issues there

 

[eddiebullman]

Hi we had the same problem with echo on IP and TDM handsets with the first release of 4.2 but our problem was to do with contactstore it was only when calls are recorded and i think that the problem is still there with 4.2.11 release we are testing a later PB release which is ok so far but .

 

[crashtest1000]

Two things

Make sure you are using the G711 codec. G729 has more delay there for more echo.

We have found at one site with an IP500 on version 4.2.11 that the echo was caused by the IP500 PRI card we went back to the IP400 card with the legacy carrier and the problem was fixed. This site was running DS and had no IP go figure