Running CCM 3.1(3a), Unity TSP 220.127.116.11<br><br>An operator is having extreme difficulties when transferring outside callers directly to a subscribers mailbox using the transfer, messages, xxxx#2, transfer method (no need for a # after the messages button, the phone does not have a subscriber associated with it).<br><br>I have watched her perform the procedure about 200 times. About 33% of the time, unity plays "sorry, I did not recognize that as a valid entry.". After she hears this error played to her, the operator tries the extension again followed by #2 and it works flawlessly. Sometimes, it takes up to 4 times entering the same extension before it accepts her input and enters the subscribers mailbox.<br><br>Would this be a CCM to Unity digit timing issue? DTMF not being sent properly? What setting can I play with to try and correct this problem?<br><br>Thanks in advance,<br><br>Logan<br><br>
We'd have to see if it is a digit timing issue, or if certain digits she dials are never sent. One thing that you could check is to see what the timing to wait for additional digits is set to on the Caller Input section of the Call Handler the operator hits when she transfers callers into Unity.
To check to see if all digits are making it, the easist thing to do is to open \commserver\techtools\statusmonitor.exe
The conversation window, I believe will show the digits dialed (unless it is some one's password that is being entered).
Normally I would create a range of DN's on CCM to FWD all to Unity (eg- if the extensions are 3xxx I would create a 2XXX range of 'phantom' phones) In Unity, a call handler is built for each 2XXX DN to always transfer to the greeting of the subscriber. Sometimes, a translation pattern in CCM like: *3.XXX (Predot and insert 2) is helpful for attendants. What that does is allow them to dial *3001 to "quick transfer" into a Subscribers box. There are docs out on CCO that detail this further I think.
More administration time is needed for this solution, but if they are having that much of a problem then it might be worth it.
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...