Someone dials the AA number, selects an option (in this case the HQs option), the call is connected to the HQs and the HQs person realizes that the call is, after all, to be placed to one of the other options from AA script.
HQs person transfers the call back to where it came (AA number) selects the correct option, establishes a connection with the correct person but when they press the transfer key again this call gets disconnected thus making the transfer inoperable.
Could this be related to the configured transfer mode under ccn subsystem sip?
By default, in this version, it is "bye-also". Already tried changing this to attended and semi-attended with no satisfactory results.
The reason is probably because it's using the BYE/Also blind transfer method (in CUE). So if something goes wrong during a transfer (any transfer), it will hang up and disconnect. I suspect the transfer is failing if it's basically routing from one SIP endpoint to another SIP endpoint (CUE again). This type of voip tandem routing has to be enabled.
You could try one of two things (or both):
on CME, configure:
voice service voip
allow-connections sip to sip
on CUE, instead of doing the Call Redirect, you could do Call Subflow.
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...