when trying to 0 out to an operator from the main greeting on 2.4.6, it doesn't transfer the call to the operator but rather loops a greeting back that says "sorry the operator is not available". Any ideas?<br>email@example.com<br><br>
It could be trying the extension but having it pop back at us on another port (it's hard to tell what's going on from over the phone). Try popping open StatusMonitor.exe (found under the \commserver directory), monitor all ports and then watch what happens when you call in and hit 0 again. I'm guessing you'll see the call on one port, the transfer attempt will go through and then the call will slam back at us on another port.
also, is it a release or a supervised transfer that's setup for the operator box? You can try switching back and forth to see if it behaves differently as well.
it'd be helpful to see what the status monitor puts up here. It may be necessary to add a pause to the dial string (seen that before) or there may be a CM configuration issue tripping us up or something similiar.
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...