Preview Tool

Cisco Bug: CSCuq26302 - Jabber will send wrong codec for Telemetry data

Last Modified

Oct 25, 2014

Products (1)

  • Cisco Unified Mobile Communicator

Known Affected Releases


Description (partial)

This only happened when User A and UserB use different codect .If User A puts the call on hold and then resume, User B will see G711 as being the codec used even though Wireshark shows G722 has been signaled and is being received in RTP. Due to the wrong data provied by CPVE, Jabber will collect wrong data to Square, so the Telemetry data will be wrong.

Step to reproduce:
1, BOT userA calls CSF userB
2, BOT userA calls CSF userC
3, userA resumes the call 
4, userB ends the call
5, userC ends the call

(See Eng-notes.p2 in enclosures for simpler reproduction steps)

Expected Result:
Two calls should use codec 722.1, and UserB & C should get g.722.1 printed when end the call

Actual Result:
Two calls were using codec 722.1 as expected(confirmed on wireshark trace), but when CSF users ended the call, g.711 codec was printed on the console.
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.