My environment is as follows: Centralized callmanagers with gateways running SRST and CUE.
My issue is with users that have voicemail accounts but no phone. In steady-state the DID os forwarded to CUE by CTI port. When in SRST mode the call is busy. Since the CTI ports dont register with SRST, there is nothing to forward the call to CUE. Has anyone heard of a workaround for this?
Are the calls for the CUE site coming into the same router where the CUE is located? Basically, if the calls are being plar'd to the Route Point in CUE (or if it's a PRI that is MGCP controlled); then in SRST mode, it should be H323 and there should be a dial-peer in the router (for that destination number--the one being plar'd to or the DID numbers) pointing to CUE. Then in CUE there need to be triggers ("show ccn trigger" in CUE) for those numbers which spawn the voicemail application.
Hmm... ok, that makes sense, since it's not a forwarded call. You'll need CUE 2.1.1 or later. What you can do is create a custom auto attendant script associated with that number that you're plar'ing to (i.e. so you'll send the call to the custom AA instead of voicemail). In there, all you do is have the steps:
Call Subflow (xfermailbox.aef)
You'll need to add an 'mbox' variable (type String) that contains the extension of the mailbox that you want to send the call to.
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...