Hi, I would like to set full-consult transfer on my 7914 expansion module. Now it works like blind transfer. I have 6 phones. On one phone is 7914 (agent), and all the incomming calls are coming on that phone. And when I want to make trasfer from an agent to some other phone, I push the transfer button, and then line button of the extension to which I wish to transfer the call, but it's always blind transfer. I would like it to be full-consult transfer.
Defines the call transfer method to allow call transfer with consultation for all lines served by the router.
Cisco CME 3.0 and later versions should use only the full-blind or full-consult keyword. Cisco ITS 2.1 and earlier versions should use the local-consult or blind keyword. (Cisco ITS 2.1 can use the full-blind or full-consult keyword by also using the Tcl script in the file called app-h450-transfer.x.x.x.x.zip.)
For SIP networks, use only the full-blind or full-consult keyword. For more information about SIP, refer to "Appendix B: Providing Cisco CME Support for SIP" in this guide and to the Cisco IOS SIP Configuration Guide.
?blind?Calls are transferred without consultation with a single phone line using the Cisco-proprietary method. This is the default if this command is not used.
?full-blind?Calls are transferred without consultation using H.450.2 standard methods.
?full-consult?Calls are transferred with consultation using H.450.2 standard methods and a second phone line if available. The calls fall back to full-blind if the second line is unavailable.
?local-consult?Calls are transferred with local consultation using a second phone line if available. The calls fall back to blind for nonlocal consultation or nonlocal transfer target.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.