I want to put a "91" as the PREDial parameter for the Fast Dials service. It seems as though only one digit will be recognized as only the 9 shows up when I use a fast dial entry. Any ideas how I can get both the 9 and 1 to show up?
To my knowledge there is not really a limit on number of digits that can be used for the predial parameter (at least, on CallManager 3.3(3)), so I'm not sure why the entire predial parameter is not being prepended to your phone number. A two-digit pre-dial works here! (and examining the ASP script, it treats the predial as a string and not a single character).
Do you have any digit translations or something similar that are being applied and affecting the number? What version of CallManager are you currently using?
You could also try looking at the XML produced by the fastdials page itself by navigating with your web browser to:
Wow, thats pretty neat! It does show the proper predial entries. It still does not show up when I dial on the phone itself. The predial parameter is set properly, but does not dial. I am using CCM 3.33. Thanks for your help.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...