Cisco Bug: CSCup99586 - Delay during enbloc dialing from SIP endpoints and Jabber client
May 16, 2018
- Cisco Unified IP Phone 7900 Series
Known Affected Releases
Symptom: When the Jabber client calls another E.164 number there is a 6 sec delay before the other endpoint rings, this matches the Inter Digit Timeout value configured on cluster. Also, Jabber does not have a dial-pad and the number is entered in full before placing the call, Enbloc dialing. CUCM should not wait any longer for additional digits and route the call right away. This issue happens on ALL Cisco SIP Hard Phones as well (99xx, 89xx, 79xx, 78xx, 88xx, EXxx, MXxx, SXxx, C20, C40, C60, C90 etc). But Cisco SCCP phones and third party SIP phones works fine. The 6 seconds is the interdigit timeout value on CUCM. Conditions: Delay occurs during enbloc dialing via pattens including '!' If we dial a number (Enbloc dialling) that hits the pattern , example : 3130! In digit analysis we can see below. Cisco SCCP phone : |PotentialMatches=NoPotentialMatchesExist Third Party SIP Phone: 1st DA== |PotentialMatches=NoPotentialMatchesExist 2nd DA==|PotentialMatches=NoPotentialMatchesExist Jabber Client: |PotentialMatches=PotentialMatchesExist Cisco SIP Phone: |PotentialMatches=ExclusivelyOffNetPotentialMatchesExist The issue here is the lack of any explicit indication from the SIP endpoint that dialing is complete. When the user dials while on-hook, then goes off hook, the digits are sent "en bloc" to CUCM. SCCP sends an explicit indication that the dial string is complete, but SIP endpoints and clients do not.
Related Community Discussions
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)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases