After Auto Attendant, call gets lost in translation.

Answered Question
Sep 24th, 2008

I built a 7941 almost 6 months ago. It is not connected to the Unity server for voice mail. I will call our main number, get the Auto-Attendant (AA) and then I will dial the entension. It will ring the phone. Recently, I have build some phone the same way and when I call and get the AA, I will dial the extension and it is not able to connect to that new phone. It goes back to the main auto attendant. I even copied the phone that works and still it will not work. I have made sure that it is set up as a new user and is associted to a number. Not sure what has changed or what I am missing between 6 months ago and now. One last thing, if I set up voice mail on Unity, it will ring the extension. Once I remove the voice mail, it again, gets lost in translation.

I have this problem too.
0 votes
Correct Answer by rob.huffman about 8 years 2 months ago

Hi Erik,

There are a couple of ways to do this. Have a look at the following on how to set up the Call Handler (lock a key to the Caller System Transfer) in Unity to allow callers to Transfer to non-subscribers;

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.

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:

You can route callers to either system transfer conversation in several ways, including: Caller System Transfer, This conversation prompts callers to enter the number that they want to transfer to.

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.

Call Management > Call Handlers > Caller Input Page

Action Indicate the action that Cisco Unity performs after a caller presses the corresponding key.

Send Caller To - Cisco Unity sends the call to the destination that you select:

Caller System Transfer - Sends the call to a conversation that allows callers to transfer to a number that they specify. For example, callers may want to dial a lobby or conference room phone that is not associated with a Cisco Unity subscriber. Cisco Unity performs the transfer only when the CS_Default_System_Transfer restriction table permits it.

You could also set up these special clients as Internet Subscribers, which does not require a User License but does allow them to be listed in the directory and to be able to be dialled from the Call Handler. Perhaps the first (working) 7941 Directory Number was set up as an Internet Subscriber :)

Hope this helps!

Rob

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (3 ratings)
Loading.
jbarcena Wed, 09/24/2008 - 13:37

What is the Unity version that you are using?

What do you hear when you can not transfer the call?

If you open the Port Status Monitor on both calls (the one that works and the one that doesn't work) what differences do you see?

Erik Townsend Fri, 09/26/2008 - 12:33

What is the Unity version that you are using? Answer: 4.1.3sr6 Callmanager, 4.0(5) Unity

What do you hear when you can not transfer the call? Answer: "I did not recognize that as a valid entry. Wait while I transfer your call." Then it returns to our main auto attendant.

If you open the Port Status Monitor on both calls (the one that works and the one that doesn't work) what differences do you see?

Answer: Actually, how do you do that?

esa786_2 Fri, 09/26/2008 - 19:43

Hi, Just log into unity server

start>programefiles>uniyt>cisco unity tooldepot(click)

you will get window where u will find switching integration tools, doubld click,u will see port status monitor(click) u will get window, make test call and see the status for both the call and post it in the forum.

Erik Townsend Fri, 10/03/2008 - 12:12

To esa786,

This was a cool tool. It did not help me resolve the issue. But it was showing the call going in and then be redirected to the Main Menu. The difference between the one that transfered and the one that did not is that after 3 Idle (all diffent symbols) then it went to "AttemptFoward" and "PHTransfer" and then the "State" and "Event is" etc. The one that worked just rang the phone. and the events ended. I ended up just adding the number to the callhandler. The ones that worked I don't recall having to do that. So I am thinking there must be something else. If you think of anything, please let me know. I would guess that it is in the CallManager or a deeper seeded set up in Unity.

Correct Answer
rob.huffman Sat, 09/27/2008 - 07:51

Hi Erik,

There are a couple of ways to do this. Have a look at the following on how to set up the Call Handler (lock a key to the Caller System Transfer) in Unity to allow callers to Transfer to non-subscribers;

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.

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:

You can route callers to either system transfer conversation in several ways, including: Caller System Transfer, This conversation prompts callers to enter the number that they want to transfer to.

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.

Call Management > Call Handlers > Caller Input Page

Action Indicate the action that Cisco Unity performs after a caller presses the corresponding key.

Send Caller To - Cisco Unity sends the call to the destination that you select:

Caller System Transfer - Sends the call to a conversation that allows callers to transfer to a number that they specify. For example, callers may want to dial a lobby or conference room phone that is not associated with a Cisco Unity subscriber. Cisco Unity performs the transfer only when the CS_Default_System_Transfer restriction table permits it.

You could also set up these special clients as Internet Subscribers, which does not require a User License but does allow them to be listed in the directory and to be able to be dialled from the Call Handler. Perhaps the first (working) 7941 Directory Number was set up as an Internet Subscriber :)

Hope this helps!

Rob

Erik Townsend Fri, 10/03/2008 - 12:18

Rob,

This helped me with the solution of creating a call handler with the extension in question. It does not use a license but I think there must be a different way, maybe on the CallManager side. Or something else with Unity. There are definitly some things for me to think about and learn from your message. I just thought I did not have to go into Unity to make this happen...actually it should not have to go to the Unity server at all. At least when I think of the logic of 1) call comes in, 2) CallManager ID's the number, 3) Phone set up in CallManager found, 4) CallManager Rings phone. Now if the actual "ringing of the phone" is done by Unity, then I stand corrected. I just thought that Unity was for Voicemail and Auto Attendant set up. If you have any thoughts that you want to add to this, please send me what you got. Thanks, for your help!

Actions

This Discussion