Hello everybody,
If I understood the below article correctly, the Speed Dial function is reserved for the patterns *1 to *199.
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cata/190/1_0/english/administration/guide/sip/ATA190/a190_agAsup.html
Speed Dial
This feature allows users to speed dial a phone number by entering an assigned index code (from *1 to *199) on the phone keypad.
I have a customer with around 1000 translation patterns: *3XXX translating to different external or internal numbers (different customer sites or mobile phones).
For the last 4 months, none of the different types of phones connected to the ATA190 devices can dial these *3XXX anymore (at least the ones verified by the customer). They are receiving a FastBusy tone. So far we have NOT found a single device that works anymore so we assume they are all affected. We are not aware of any CUCM changes and the ATA190 Software is the latest 1-2-2-003_SR2. Same issue happens also with ATA190 v.1-2-1-003 and v1-2-2-003.
Partitions/CSSs should not be a problem since IP Phones are able to call *3XXX and the DECT Phones connected to ATAs can also call #3001 which is just a test pattern created by copying the *3001.
Every setting on the Device page is standard, and I already tried enabling/disabling the "Require DTMF Reception" on the Device page and configured a ## in front of every Vertical Service Activation Code on the ATA190. Nothing seems to show any change. The ATA behaviour is the same:
ATA190 and ATA191 Debug log is showing the pattern *XXX being sent directly to CUCM as Speel Dial.
ATA190 log:
- Digits dialed
Line 105291: Mar 29 15:56:06 ATA190 daemon.debug sprvoip: <159>line:0 DTMFON event received digit *
Line 105318: Mar 29 15:56:06 ATA190 daemon.debug sprvoip: <159>line:0 DTMFOFF event received digit *
Line 105348: Mar 29 15:56:06 ATA190 daemon.debug sprvoip: <159>line:0 DTMFON event received digit 3
Line 105376: Mar 29 15:56:06 ATA190 daemon.debug sprvoip: <159>line:0 DTMFOFF event received digit 3
Line 105406: Mar 29 15:56:07 ATA190 daemon.debug sprvoip: <159>line:0 DTMFON event received digit 0
Line 105434: Mar 29 15:56:07 ATA190 daemon.debug sprvoip: <159>line:0 DTMFOFF event received digit 0
Line 105464: Mar 29 15:56:07 ATA190 daemon.debug sprvoip: <159>line:0 DTMFON event received digit 0
Line 105492: Mar 29 15:56:07 ATA190 daemon.debug sprvoip: <159>line:0 DTMFOFF event received digit 0
Line 105583: Mar 29 15:56:07 ATA190 daemon.debug sprvoip: <159>line:0 DTMFON event received digit 1
Line 105586: Mar 29 15:56:07 ATA190 daemon.debug sprvoip: <159>line:0 DTMFOFF event received digit 1
After the * 3 0 0 are finished to be dialed, ATA sends it as a speed Dial to CUCM and since there are no Speed Dials configured, it fails:
Mar 29 15:56:07 ATA190 daemon.debug sprvoip: <159>[cucm_abbr_dial_final: 184]abbreviate dialing: *300
Mar 29 15:56:07 ATA190 daemon.debug sprvoip: <159>[cucm_feature_code_check: 676]CUCM Feature Code: Abbreviate Dial
Mar 29 15:56:07 ATA190 daemon.debug sprvoip: <159>[cucm_feature_code_process: 1075]dialed string: x-cisco-serviceuri-abbrdial-300
Mar 29 15:56:07 ATA190 daemon.debug sprvoip: <151>Calling:x-cisco-serviceuri-abbrdial-300@REMOVED_IP_ADDRESS:0, rc=0
Mar 29 15:56:07 ATA190 daemon.debug sprvoip: <159>++++ called number = x-cisco-serviceuri-abbrdial-300
Mar 29 15:56:08 ATA190 daemon.debug sprvoip: <159>[rcc_refer_parser: 397]unknown remote cc request: <?xml version=\"1.0\" encoding=\"iso-8859-1\"?> <x-cisco-remotecc-request> <statuslineupdatereq> <action>notify_display</action> <dialogid> <callid>7817f762-99a7943c@REMOVED_IP_ADDRESS</callid> <localtag>176185070</localtag> <remotetag>7e1c0d2a9cf93914o0</remotetag> </dialogid> <statustext>Number Not Configured</statustext> <displaytimeout>10</displaytimeout> <priority>1</priority> </statuslineupdatereq> </x-cisco-remotecc-request>
Mar 29 15:56:08 ATA190 daemon.debug sprvoip: <134>CUCM ERROR!!! [rcc_refer_parser: 402]fail to parse <?xml version=\"1.0\" encoding=\"iso-8859-1\"?> <x-cisco-remotecc-request> <statuslineupdatereq> <action>notify_display</action> <dialogid> <callid>7817f762-99a7943c@REMOVED_IP_ADDRESS</callid> <localtag>176185070</localtag> <remotetag>7e1c0d2a9cf93914o0</remotetag> </dialogid> <statustext>Number Not Configured</statustext> <displaytimeout>10</displaytimeout> <priority>1</priority> </statuslineupdatereq> </x-cisco-remotecc-request> for remote call control
CUCM SDL Log:
09338694.001 |15:56:08.455 |AppInfo |//SIP/SIPUdp/wait_SdlDataInd: Incoming SIP UDP message size 1409 from REMOVED_IP_ADDRESS:[5060]:
Line 14: INVITE sip:x-cisco-serviceuri-abbrdial-300@REMOVED_IP_ADDRESS SIP/2.0
Although we are not aware of any CUCM/ATA global configuration changes, the customer insists that dialing the *3XXX pattern from a ATA end point worked fine until 4 months ago.
So the question is, has anybody been able to call from an ATA to a *3XXX translation pattern which is not configured as a Speed Dial in CUCM?
Thank you!
