Extension Mobility - Where do the original extensions go?
When a user logs into a phone, what happens to that orginal extension once a new user is logged on?
I have a user that only comes in on Friday's, but on any other day another user is signed on to that phone. However, when the Monday-Thursday user is logged on and some tries to call the original user, the Extension Mobility user is logged off and the orginal extension on the shows and rings.... is this right?
I always thought that when a user logs on to a phone, the original extension would just busy itself and everything would forward to voicemail.
Re: Extension Mobility - Where do the original extensions go?
Thats were ADPs come from. ADP stands for Autogenerated Device Profiles. ADP stores the original phone settings and retrieve the settings on the phone back, depending upon your Extn. Mobility logout settings. If your extn mobility logout settings say, Use original device settings, the settings that got stored in ADP will be used to retrieve the original phone settings. ADP shares the same DN with the actual device.
When a user logs into EM on a different phone, his original phone and the new phone he logged in will share the same DN and will act like a shared line appearance.
Also, when a user logs into EM on a phone, the original phone number will roll over to voicemail immediately (provided the forward settings are properly set to go to voicemail).
Re: Extension Mobility - Where do the original extensions go?
when you created Extension Mobility your are given primary ext and once logged in you are using the new subcribe #, thats been assigned to the phone and user.
yes, if your EM # is assigned VM it should go to VM, sounds like there may be a configuration conflict between the original user and EM user, device profile, and logout profile. could be just one thing or a few.
Understanding Extension Mobility and Phone Logins
The Extension Mobility feature allows users to configure any Cisco IP Phone 7940 or Cisco IP Phone 7940 IP phone as their own, on a temporary basis, by logging in to that phone. Once a user logs in, the phone adopts the user individual user default device profile information, including line numbers, speed dials, services links, and other user-specific properties of a phone. For example, when user A occupies a desk and logs in to the phone, her directory number(s), services, speed dials, and other properties appear on that phone; but when user B uses the same desk at a different time, his information appears. The Extension Mobility feature dynamically configures a phone according to the current user.
Note If a login device profile is configured for a Cisco IP Phone 7960 but the user logs into a Cisco IP Phone 7940, the phone takes on the attributes and capabilities of the Cisco IP Phone 7940. This is because there are fewer lines on a Cisco IP Phone 7940 than a Cisco IP Phone 7960. The Cisco IP Phone 7960 capabilities return when the user logs into a Cisco IP Phone 7960.
Previously, only administrators could change phone settings only through Cisco CallManager Administration. The Extension Mobility feature allows users to change phone settings themselves without accessing Cisco CallManager Administration. Instead, when users authenticate themselves at the phone, a login service performs the administrative updates.
The programmable login service enforces a variety of uses, including duration limits on phone configuration (persistence) and authorization to log in to a particular phone. A Cisco IP phone XML service provides the user interface to the login service provided in this release. Refer to the Cisco CallManager Administration Guide for more information.
Supported Phones and Features
This release provides Extension Mobility feature availability on Cisco IP phones that support Cisco IP phone XML services; currently, only the Cisco IP Phone 7940 and the Cisco IP Phone 7960 offer this feature.
Managing Device Profiles
A device profile comprises the set of attributes (services and/or features) associated with a particular device. Device profiles include name, description, phone template, add-on modules, directory numbers, subscribed services, and speed-dial information. Two kinds of device profiles exist: autogenerated and user. You can assign the user device profile to a user, so that, when the user logs into a device, the user device profile you have assigned to that user loads onto that device as a default login device profile. Once a user device profile is loaded onto the phone, the phone picks up the attributes of that device profile.
You can also assign a user device profile to be the default logout device profile for a particular device. When a user logs out of a phone, for instance, the logout device profile loads onto the phone, giving that phone the attributes of the logout device profile. You can create, modify, or delete the user device profile in the Cisco CallManager Administration web pages.
Note On some phones, if a user device profile is used as the logout device profile, you cannot delete the user device profile.
The autogenerated device profile automatically generates when you update the phone settings and choose a current setting to generate an autogenerated device profile. The autogenerated device profile associates with a specific phone to be the logout device profile. You can modify the autogenerated device profile but not delete it or change the profile name.
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...