Guest

Preview Tool

Cisco Bug: CSCuo28512 - 3905 ip phone do not play any tone for 403 forbidden SIP message

Last Modified

Sep 11, 2014

Products (11)

  • Cisco IP Phone 8800 Series
  • Cisco Unified IP Phone 9951
  • Cisco Unified SIP Phone 3905
  • Cisco Unified IP Phone 6961
  • Cisco Unified IP Phone 6941
  • Cisco Unified IP Phone 8961
  • Cisco Unified IP Phone 8941
  • Cisco Unified IP Phone 9971
  • Cisco Unified IP Phone 8945
  • Cisco Unified IP Phone 6945
View all products in Bug Search Tool Login Required

Known Affected Releases

9.4(1)

Description (partial)

Symptom:
If we are dialing from a 3905 ip phone to any external PSTN number (called party) and if the Called Number is already busy on another call, then the calling Party (3905 phone) is NOT getting any busy tone or any tone. Instead the Dialed number just vanishes immediately as if nothing has happened.

After analyzing the issue we could see that the numbers are dialed out from ip phone via CUBE to Service Provider. As the Called party is already busy on another call, the Service Provider sends '403 Forbidden'. Ideally this should be '486 Busy Here' message. We have checked this with Service Provider. Unfortunately, the SP is aware that they should not send 403 Forbidden rather 486  message, but that's the way how the SP has configured their Ericcson IMS VoIP platform, and would be difficult for them to change the signaling.

So the problem here is, even if the 3905 ip phone receives '403 Forbidden' message it should play busy tone or some tone, not just vanish the dialed number.
We have tested this is lab and replicated the issue. When the 3905 ip phone receives '403 Forbidden' the dialed number just vanishes. We tested the same with several other model phones (sip and sccp) and it is working fine, getting some busy tone.

So the concern is why 3905 ip phone is not playing any tone when it receive '403 Forbidden'?

Conditions:
The issue occurs when 3905 phone receives a 403 Forbidden message.
Bug details contain sensitive information and therefore require a Cisco.com 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.