[cisco-voip] Transfer to MeetMe from Unity

Brian Henry Brian.Henry at apptis.com
Sat Mar 11 17:08:09 EST 2006


This part comes from the link that I am providing:

Setting Up System Transfers 

In your organization, you may find that callers want to be able to dial numbers that are not typically listed in directory assistance. For example, subscribers and outsider callers may find it convenient to be able to call Cisco Unity and transfer from the Opening Greeting or another call handler to a lobby extension, conference room extension, or an extension assigned to someone in the organization who is not a Cisco Unity subscriber, such as an employee who is visiting from another site and is using a guest office. In addition, some subscribers may want to be able to call Cisco Unity and then transfer to phone numbers outside of the organization-such as frequently called customers or vendors-so that they do not have to hang up after checking messages to place another call, or so that they will not incur long-distance charges while on business travel. 

You can route callers to one of two "system transfer" conversations, both of which offer callers the ability to transfer to numbers that are not associated with Cisco Unity subscribers: 

Caller System Transfer 
This conversation prompts callers to enter the number that they want to transfer to. 

To protect Cisco Unity from toll fraud and unauthorized use, Cisco Unity performs the transfer only when the CS_Default_System_Transfer restriction table permits it. 

Subscriber System Transfer 
This conversation prompts callers to log on to Cisco Unity. After callers enter their Cisco Unity IDs and passwords, Cisco Unity prompts them to enter the number that they want to transfer to. 

To protect Cisco Unity from toll fraud and unauthorized use, Cisco Unity performs the transfer only when permitted by the transfer restriction table that is associated with the class of service for the subscriber who logged on. 


You can route callers to either system transfer conversation in several ways, including: 

* <http://www.cisco.com/univercd/illus/images/blank.gif> By offering a system transfer as a "one-key dialing" option. You can specify either system transfer (on the Caller Input page for any call handler or subscriber greeting) as the action that Cisco Unity performs when a caller presses a particular key during the greeting. 

For example, to allow all callers to transfer to a lobby phone, guest office, or a conference room from the Opening Greeting, you could specify that Cisco Unity will offer Caller System Transfers when callers press 3. To offer system transfers to a particular subscriber, you could specify that Cisco Unity will offer Subscriber System Transfers when the subscriber presses a particular key during the Opening Greeting or even during his or her own greeting. 

* <http://www.cisco.com/univercd/illus/images/blank.gif> By creating a new phone number and a corresponding routing rule to send callers to either system transfer conversation. In this way, when callers dial the number, Cisco Unity sends calls to the system transfer conversation you specify. 

 <http://www.cisco.com/univercd/illus/images/note.gif> 
________________________________

Note  <http://www.cisco.com/univercd/illus/images/blank.gif> Regardless of how you offer callers either type of system transfer, Cisco Unity releases calls to the phone system, which handles the transfer to the specified number. 

________________________________

Follow the applicable task list in this section to set up Caller and Subscriber System Transfers. For both types of transfers, Cisco Unity prompts subscribers and callers to confirm the number that they enter before performing the transfer. To disable the confirmation prompt, use the Advanced Settings tool to change the Conversation-Confirm Number Before System Transfer Conversation setting. Refer to the Advanced Settings Help for details. (The Advanced Settings tool is available in Tools Depot.) 

Task List: Offering Caller System Transfers 

1.  <http://www.cisco.com/univercd/illus/images/blank.gif> Modify the CS_Default_System_Transfer restriction table. See the "Restriction Tables" chapter for details on how restriction tables work and how to modify them to allow the numbers you want. 

2.  <http://www.cisco.com/univercd/illus/images/blank.gif> Set up a one-key dialing option or a new phone number that callers can use for system transfers: 

* <http://www.cisco.com/univercd/illus/images/blank.gif> Setting Up a One-key Dialing Option-Use caller input settings for a call handler to send callers to the Caller System Transfer conversation when they press the key that you specify during a call handler greeting. Then, enable caller input for the applicable greeting and re-record the greeting to mention the key that callers can press in the call handler greeting. (For example, "...to reach a conference room, press 3.") See the "Call Handler Caller Input Settings" section on page 19-13. 

* <http://www.cisco.com/univercd/illus/images/blank.gif> Setting Up a "System Transfers" Phone Number-Refer to the documentation for the phone system to set up a new phone number. Then, on the Call Management > Call Routing > Direct Calls page in the Cisco Unity Administrator, create a routing rule that sends any call that arrives for the new number to the Caller System Transfer conversation. Distribute the new number to callers who will find Caller System Transfers convenient. See the "Creating and Modifying Call Routing Rules" section on page 22-3 and the "Direct Calls and Forwarded Calls Routing Table Settings" section on page 22-4 for details on creating routing rules for direct calls. 

Task List: Offering Subscriber System Transfers 

1.  <http://www.cisco.com/univercd/illus/images/blank.gif> For the subscribers who will use Subscriber System Transfers, modify the transfer restriction table that is associated with the subscriber class of service so that the subscribers can dial numbers that are not associated with Cisco Unity entities. See the "Restriction Tables" chapter for details on how transfer restriction tables work and how to modify them to allow the numbers you want. 

 <http://www.cisco.com/univercd/illus/images/tip.gif> 
________________________________

Tip  <http://www.cisco.com/univercd/illus/images/blank.gif> If you are not offering system transfers to all subscribers in a single class of service, reassign those who will use it to a new class of service that has a transfer restriction table that will allow them to dial the applicable numbers. 

________________________________

2.  <http://www.cisco.com/univercd/illus/images/blank.gif> Set up a one-key dialing option or a new phone number that callers can use for system transfers: 

* <http://www.cisco.com/univercd/illus/images/blank.gif> Setting Up a One-key Dialing Option-Use caller input settings for a call handler or a subscriber greeting to send callers to the Subscriber System Transfer conversation when they press the key that you specify during the greeting. Then, enable caller input for the applicable greeting. Tell subscribers which key to press to access the Subscriber System Transfer conversation when they listen to the greeting, or if you are not concerned about other callers hearing the option and not being able to use it, re-record the greeting to mention the key. (For example, "...to reach a conference room, press 3.") See the "Call Handler Caller Input Settings" section on page 19-13 and the "Subscriber Caller Input Settings" section on page 14-23. 

* <http://www.cisco.com/univercd/illus/images/blank.gif> Setting Up a "System Transfers" Phone Number-Refer to the documentation for the phone system to set up a new phone number. Then, on the Call Management > Call Routing > Direct Calls page in the Cisco Unity Administrator, create a routing rule that sends any calls to the new number to the Subscriber System Transfer conversation. Distribute the new number only to the subscribers who will use Subscriber System Transfers. See the "Creating and Modifying Call Routing Rules" section on page 22-3 and the "Direct Calls and Forwarded Calls Routing Table Settings" section on page 22-4 for details on creating routing rules for direct calls. 

http://www.cisco.com/en/US/products/sw/voicesw/ps2237/products_administration_guide_chapter09186a0080449c12.html#wp1269891

 

Brian

 


________________________________

From: Jonathan Charles [mailto:jonvoip at gmail.com]
Sent: Sat 3/11/2006 5:01 PM
To: Brian Henry
Cc: adman at adman.net; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Transfer to MeetMe from Unity


What do you mean?


On 3/11/06, Brian Henry <Brian.Henry at apptis.com> wrote: 

	Did you set you tranfer rule to allow it?
	--------------------------
	Sent from my BlackBerry Wireless Handheld

	
	
	
	
	-----Original Message-----
	From: cisco-voip-bounces at puck.nether.net
	To: Adam Blomfield
	CC: Cisco Voip
	Sent: Sat Mar 11 15:11:24 2006
	Subject: Re: [cisco-voip] Transfer to MeetMe from Unity
	
	It is opened by an internal subscriber... After which, someone else dials into the call handler and I want them to be able to transfer into the meetme (that has already been opened).
	
	
	
	Jonathan
	
	
	On 3/11/06, Adam Blomfield <adman at adman.net> wrote:
	
	        On 3/11/06, Jonathan Charles <jonvoip at gmail.com> wrote:
	        > OK, so, I created a boat-load of MeetMe numbers, and I want to be able to
	        > have users be able to call a DID, and hit a call handler in unity that says,
	        > 'enter a conference id'... and then transfer them to that meetme conference
	        > (which is opened by an internal subscriber).
	        >
	        > However, I keep getting a 'you can not be transferred to this number, check
	        > the number and try again' from unity if I use the caller system transfer...
	        > I have confirmed the conference is active...
	        >
	        > If I try to just dial the meetme extension during the greeting, I get 'i did
	        > not recognize that as a valid entry' from unity...
	        >
	        >
	        >
	        > What am I missing?
	        >
	        >
	        > Unity version is 4.1(1)
	        >
	        > Though it might be 4.2(1) in another hour or so...
	       
	        MeetMe numbers have to be activated from a 79XX handset using the
	        softkeys. TTBOMK there's no way to have them just sitting open at all
	        times waiting for someone to dial in.
	       
	        -Adam
	       
	
	
	

	


-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20060311/3e843ba1/attachment-0001.html 


More information about the cisco-voip mailing list