I noticed that when configuring a primary device for mobility under the user configuration, it reduces the number of DLUs consumed from 4 to 2, but will this affect the user in any way when using mobility?
I tried to find any difference from the user experience side by configuring a primary device under mobility and trying the features, then I removed the device and tried the features again, I tried them on the phone configured and on other phones as well, all was working fine with no problems.
Appreciate if any one can confirm this issue please, thanks a lot.
There is no impact to the functionality. You are seeing Mobility being placed into Adjunct Licensing mode. This lowers the quantity of DLUs required for the feature when a physical Cisco phone is also assigned to this user. It was a mechanism for making Unified Mobility more attractive for a-la-carte customers. The same principal applies when you associate a physical Cisco phone to a Cisco soft phone such as IP Communicator. A physical phone will allow up to two adjunct devices.
Note that this licensing model has been superceeded by User Connect Licensing starting in UCM 7.1(5) and 8.0(1). You may want to speak with your partner or Cisco Account Manager about the changes and whether Unified Workspace Licensing is a better fit for you.
Well each user here has an IP phone and EM Profile so I think it will be very benefical to use the adjunct licensing mode.
Just let me confirm that I am getting this right.
1. We have 10 employees.
2. Each employee has his own IP phone and his own EM Profile.
3. When we configure the "" field under each user account with his own IP phone, so the DLUs will be reduced by 2 x 10 = 20 DLUs.
4. If the user wants to log into any IP phone (not the one assigned under his account), he will use the mobility feature with no problems? Or he must log into his IP phone for the mobility feature to work properly? I made this test and found no problem when logging into any IP phone.
I just want to confirm everything before applying the changes on all the employees here, about 1500. It is very wierd actually as during the implementation our Cisco partner told us that this filed of the "Primary User Device" will not make a difference with us and so is not important.
Yes, Unified Mobility will work just fine in conjunction with Extension Mobility. In this case an incoming call would alert on the user's normal phone, the phone they have logged into, and their remote destination(s). Just be sure to set the soft key template on the user's device profile to something that includes the Mobility soft key.
I suspect you may be a little confused between some similarly named features here:
EM Profiles (by which you mean a Device Profiles for Extension Mobility) do not take any DLUs at all; they are 'free', if you like.
So you can't make them adjunct with a real phone, and there's no reason to want to. I think that's what your Cisco Partner was getting at.
So the 'primary user device' on the End User page is not related to EM, but to the Mobility feature (SNR/dial via office). If you are configuring Mobility for your users, then you will get the adjunct licensing saving, but not for standard EM users without Mobility configured.
Please rate helpful posts...
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
Many thanks for your replies, yes I know that EM will not use any DLUs but can u clarify for me please, what are the advantages and disadvantages (from the user experience side) of having a primary device configured for them???
I am thinking of it that, since the number of DLUs will be reduced when assigning a primary device, then there must be a certain limitation we will face.
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...