Extension Mobility Phone Buttons across different phone types
I have a customer who I am moving to CUCM 11.5.
They currently have a mix of 6941 and 7941 phones and are replacing the 7941 phones with 7841 models as part of the upgrade.
The customer currently does not really use the programmable buttons on the phones but wants to start doing so for Pickup, HLog etc.
The issue I am having is getiing the buttons to work when logging a 6941 EM profile into a 7841 phone and vice-versa.
I know that I can set the Phone Button Template in the Default Device Profile for the phone type but really need more flexibility than this offers as each phone type has multiple Phone Button Templates.
Is there any way to do this or am I stuck with the single template supported by the Default Device Profile?
After some more testing I have discovered 6941 UDPs can log in to 7841 phones and display the correct buttons. Unfortunately the opposite is not true and given that end of software maintenance for the 6900 was reached in 2015 I guess it is not going to be fixed
This customer will have a 60:40 split of 7841 to 6941 phones and they are not willing to replace the older models yet.
They want users to have a consistent experience when logging into phones and one option that seems workable is to define all UDPs as 6941 SIP. This would allow the feature buttons to work whether a user logs in to a 6941 or 7841.
I am wondering about downsides to this option. Will the users lose anything significant by using a 6941 UDP on a 7841 phone?
One thing I can think of is Opus codec but the customer is not using that at the moment.
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...