9611 not outputting traceroute information 1

[vulcanccit]

We just stood up the Nectar RIG monitoring system. It is working well except we found that the 9611 phones do not give us traceroute information. 9630s and 9650s do on the same network. Nectar believes it is a settings file issue. I do have a ticket open with Avaya, but I thought I would see if one of you might know what is going on. I find this forum to be a lot faster than Avaya

 

[latitude12]

When I last looked at this issue (six months ago) this was broken for 96x1 phones (H323 and SIP). It isn't a settings issue (there are no settings for this feature), it just doesn't work. What firmware version are you running? I would have thought Avaya would have fixed this by now...

 

[marcuspb]

We are using Prognosis for to monitor our AVAYA gear and we have the same problem with our H323 9608's. I opened a ticket with AVAYA and they said it would be addressed in a future firmware update.
I've updated firmware twice since then and it still doesn't work.

 

[vulcanccit]

Avaya is sending my issue to the SME (Subject Matter Expert). They wanted me to do a wireshark capture from my desktop to capture the phone traffic from my deskphone to my cell but I don't see that traffic in the trace. I sent it to them anyway. I am trying to get help with the trace from our WAN guys but they are so swamped and this is very low priority. Avaya said this might need to go to Tier 4 or development. I do know this issue is present in all of our locations (19 of them around the country, so it is not localized or intermittent.

To answer Latitude12 we are running 6.2209 on the 9611 and 3.103s on the 9630 phones. I am told I am on the latest firmware for the 9611 and behind one for the 9630.

 

[vulcanccit]

I am updating this thread. Avaya advised me that their latest 9611 patch might solve the issue. I tried it here at the Core and in one of our LSP markets and it did indeed fix the issue. Posting it here for the group, I hope this helps you folks.

https://support.avaya.com/downloads...contentId=C2013524927303950_3&productId=P0553

6.2sp3: Deskphones SDES information in RTCP packets contains some non-printable characters.

6.2sp4: RTCP field population is sometimes missing