10-16-2017 11:31 AM - edited 03-17-2019 11:23 AM
Hi there,
We upgraded Cisco CUCM from 9.1 to 11.5.2. We have around 40 Cisco IP Phone 7940. On a couple of phones when users try to log in - using Extension Mobility - they get an error "HTTP Error [400]!". Most of Cisco IP Phone 7940 don't have this issue. IP addresses are used every where (CUCM Server, Enterprise Parameters, Extension Mobility etc). All the phones got the same firmware.
Please advise.
Regards,
Sam
Solved! Go to Solution.
10-17-2017 02:45 PM
I found the solution. If phones don't support Extension Mobility Cross Cluster, it will get this error message.
Example:
http://123.45.67.89:8080/emapp/EMAppServlet?device=#DEVICENAME#
Note |
If you append the Extension Mobility Cross Cluster suffix &EMCC=#EMCC#in the service URL for Extension Mobility, the Extension Mobility login fails with an HTTP 400 error on phones that do not support Extension Mobility Cross Cluster. Users will see a blank screen on the phone when the Extension Mobility service is not selected. |
10-17-2017 02:45 PM
I found the solution. If phones don't support Extension Mobility Cross Cluster, it will get this error message.
Example:
http://123.45.67.89:8080/emapp/EMAppServlet?device=#DEVICENAME#
Note |
If you append the Extension Mobility Cross Cluster suffix &EMCC=#EMCC#in the service URL for Extension Mobility, the Extension Mobility login fails with an HTTP 400 error on phones that do not support Extension Mobility Cross Cluster. Users will see a blank screen on the phone when the Extension Mobility service is not selected. |
02-01-2018 02:04 PM
We upgraded from 11.5 to 12.0 and it tacked on the &EMCC=#EMCC# part for some reason. We removed it and it worked again.
http://CMPUB:8080/emapp/EMAppServlet?device=#DEVICENAME#05-15-2018 02:03 AM
Thanks every one who o contributed to this thread - this helped me out a lot when we ran into the same issue following an upgrade from 11.0(1)SU1 to 11.5(1)SU4.
At the risk of teaching you all to suck eggs, just one additional piece of advice so that you don't make the same error I did:- Once you amend the service urls, don't forget to click the "update subscriptions" button to push to change out to your telephony end points.
Initially we got involved in unsubscribing and re-subscribing phones and users to EM which does work but doesn't scale well as a work around ;-).
All the best
Rich
07-13-2021 12:48 AM
Juste a note to the wise:- I've just upgraded again from 11.5(1) SU4 to 11.5(1) SU10 and the "&EMCC=#EMCC#" got appended again so the 7940/7960 HTTP Error [400!] issue re-occurred. The resolution is the same. Don't forget to "Update Subscriptions" afterwards.
Rich
08-16-2018 12:26 PM
After removing the &EMCC=#EMCC# at the end of the service URL, do any services need restarting?
08-17-2018 12:59 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide