Directory handler can transfer incoming calls to user's voicemail box but when people dial user's direct number, it goes to main Unity answering system instead of their own voicemail box. Could you please let me know how can I fix this problem? Thanks <br><br>
The last sentence in your post there points to the problem at hand... if you call a user's extension directly and it forwards to voice mail, the switch SHOULD be sending us information (via serial or analog or digital means depending on which switch you're hooked up to) that tells us which extension is calling, where it forwarded from and why it got to us (i.e. it forwarded ring no answer). Armed with this information we will get the caller to the greeting of the user who owns that extension number.
If this isn't working your switch is not programmed properly or the integration to that switch is not properly configured in Unity. You definitely need to get this squared away regardless.
If we're doing supervised transfers this should still work since we're not letting go of the call. We simply hookflash, dial the extension and wait to see if someone answers or not or it's busy or whatever. If no one answers the phone we hook flash again and take the caller back. This should always work. The only reason it wouldn't is if the call progress information (i.e. the ringback tones or busy tones the switch is playing back to us when we dial the extension) is not being recognized properly. For instance you have some weird ring pattern programmed into the switch (i.e. a double ring or something) and the call progress routines think a user has answered the phone and we release the call.... the switch then will forward the call back to us.
It would be unusual for the ringback patterns to be so out of whack they were not recognized like that... I'm deeply skeptical that's the issue. It sounds to me like you have it setup to do release transfers and the switch programming/Unity integration configuration is not properly setup so the calls are not being forwarded where they should be.
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...
[toc:faq]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 discusse...