In the mean time I have to install a CCME (C2911 w/ version 10) in a remote branch with several conference ip-phones CP-8831 on the local LAN that after some months, has to be w/ under/migrated the center Call Managuer. I have check on CCW (to order CP-7937G) and it is on a AEOS status flag, and also have seen (if I am not wrong) that EoS/EoL Notice in CCO : http://www.cisco.com/en/US/partner/prod/collateral/voicesw/ps6788/phones/ps379/end_of_life_notice_c51-729487.html
So, as it Is not clear enoght to solve, There is a firware to be downloaded to the device?... etc.. there is any way to over came the issue?.
I would aprecciate any help and guidance.
Thanks a lot. Eduard.
Solved! Go to Solution.
Plataform is CCME on a ISRG2 (2911) device and not CUCM in the mean time, after that will SRST and CUCM 9.1.
We will try to check w/ a Cisco IOS: 15.4.1T ED and CME 10.0(1) but we have not seen any document from Cisco that helps us to clear clarify the situation we are.
Ah ok, I wasn't sure whether you were asking CME or CUCM so I guessed the later.
It appears CME is a no-go at the moment as it's not in the compatibility matrix nor the data sheet. You have three options:
7937s they are also EOS.
I have already asked for the support, I still waiting for a answer... It may that also impact to SRST.
After some testing I was able to get multiple 8831's to successfully register with CUCME 10.0.
The actual configuration process was quite easy after figuring out what the phone needed and it was just a matter of configuring the voice register settings as per normal SIP phones/extensions. To have the configuration files automatically created simply apply the "type" setting (I tested with other models in the 8xxx range) to the voice register pool configuration setting for the phone.
During testing the only functionality issue I could find was that I couldn't get the timezone to set correctly, other than that the phone appears to function as per normal.
End-user testing will tell if everything is successful but until the phone is officially supported this work around should suffice.