Simple One

Unanswered Question
Apr 26th, 2007
User Badges:

CCM 4.X and Unity 4

Using Extention Mobility. A user want that when he is on a call, if a second Call arrives, caller should get busy tone instead of voicemail. Also the user wants that after he logs out of his phone using EM, that calls goes to Voicemail.

How can i achieve this? already setted busy trigger to 1, Forward Busy internal/external to voicemail. but doesnt meet what he wants.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
o.artigny Thu, 04/26/2007 - 06:37
User Badges:


You must not forward Busy to voicemail, if you want to have a busy tone.

Do not specify any busy destination.


Jayd000007 Thu, 04/26/2007 - 06:42
User Badges:

that worked thanks, but how did callmanager know that he should forward to voicemail if user not logged on? with voicemail profile?

o.artigny Thu, 04/26/2007 - 06:48
User Badges:

I suppose it's the "Forward No Coverage" option, but I am not sure.

Let me know if you find out.


Jayd000007 Fri, 05/04/2007 - 04:56
User Badges:

DO someone have answer to my question? how the Callmanager knows it?

Mark Turpin Fri, 05/04/2007 - 06:08
User Badges:

Yes, CFUR.

Device -> Device Settings -> Device Profile -> UserDevice Profile of User -> DN for User -> Call Forward Unregistered should be set to voicemail.


Rob Huffman Fri, 05/04/2007 - 05:42
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Jay,

The decision to Forward to Voicemail comes from the Logout profile. Have a look

User Device Profile

As system administrator, you configure a user device profile for each individual user. Using the Cisco CallManager User Options window, a user can access this profile and make changes, such as adding a service. You can add, modify or delete a user device profile in Cisco CallManager Administration.

When a user logs in to a phone that is configured for Cisco CallManager Extension Mobility and the user has a user device profile configured for that phone, the user device profile replaces the existing configuration of the device.

When a user logs out, the user device profile is replaced by the logout profile.

Logout Call Flow

This section describes the flow of events for the Cisco CallManager Extension Mobility logout from a system perspective. Understanding the call flow will help you troubleshoot any problems that you may have with the Cisco CallManager Extension Mobility feature.

1. A user presses the Services button on the Cisco IP Phone and requests to log out. This action invokes a URL for the Cisco CallManager Extension Mobility application.

2. The application determines the URL of the service.


Note Cisco CallManager Extension Mobility looks up the URL in the Cisco CallManager Directory on the first instance only; the URL is then stored as a static variable.


3. The application generates the XML to query the Cisco CallManager Extension Mobility service for the current state of the device.

4. The service responds to the application with the current state of device; for example, is logged in.

5. The application prompts the user to confirm that the user wants to log out.

6. When the user presses the Yes softkey to confirm that they want to log out, the application generates XML for the logout operation.

7. The application posts, via HTTP, the generated XML login request to the service URL (The application determined the service URL in step 2).

8. The service responds to the application request with a Success or Failure message in an XML format.

9. The application parses the received XML and creates an XML response message.

10. The XML gets returned as a suitable notification to the device, and the phone displays "Logout successful" to the user.

11. The phone restarts to load the original user profile or the **logout profile (autogenerated device profile).

From this good doc;

Hope this helps!



This Discussion