Hi,
last week we upgraded without problems the CUCM from 8.6.2 to 10.5.2
We work with Cisco IP Phones 7961/7962/7965/7970 (SCCP Protocol)
After successfull upgrade we begän to change the Cisco IP-Phones for some Users.They got the new Cisco 8861 (SIP Protocol) with Expansion Module.
After replacing the phones this User complains, that there was a delay on calls initiated from the Cisco 8861 phone outside to PSTN.
Customer dials the whole number (on-hook) - then he pushes the speaker or the dial button (goes off-hook) .
With the "old" SCCP Phones the call to an external target alerts about 6 Sec (Called Number Ringing)
. - with the "new" SIP Phones it takes about 10-12 Sec.There is a significant delay on the SIP Phones vs SCCP Phones.
Problem seems to be the interdigit-timer ? (we found the bug-id CSCup99586) -
We told the Telephone User to dial the called number with a # at the end ot the called number. The # at the end of the called number indeed helps to reduce the time waiting for the alerting tone.
The user told us, that this workaround do not force the acceptance of the "new" phones - They are not happy about this workaround ....
Does anyone find a better solution for this problem ?
CUCM is located in Germany - Here we have a Dial-Plan with variable length, therefore we must work with route pattern for example 0! ...
Thanks
regards
Alex
Attached the Bug Description
Delay during enbloc dialing from SIP endpoints and Jabber client
CSCup99586
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.
Workaround:
N/A
