I have SCCP 8945 phone in my lab that I can't make authenticate with UCM 9.1. Diggin deep down revealed that for some misterious reason the phone tries to add a domain name to its device name. It tries to grab domain name from DHCP and if's not configured simply leaves trailing dot (.) so that device name looks like this "SEP20BBC020215D.". Naturally this name has no chance to be authenticated. Here's short exchange captured by wireshark:
GET /ccmcip/authenticate.jsp?UserID=phone&Password=phone&devicename=SEP20BBC020215D. HTTP/1.1\r\n HTTP/1.1 200 OK Set-Cookie: JSESSIONID=6BB2F3CEF1F001948B45A6E1056DF868; Path=/ccmcip/; HttpOnly Content-Type: text/html;charset=ISO-8859-1 Content-Length: 13 UN-AUTHORIZED
If I copy the GET request into browser address bar and remove trailing dot it authenticates alright. Same thing happen with my non-8945 phones. They don't try to add the dot to their name and authenticate fine:
GET /ccmcip/authenticate.jsp?UserID=phone&Password=phone&devicename=SEPE8B74838391B HTTP/1.1\r\n
HTTP/1.1 200 OK
So, my question, is this behavior expected from the 8945 phones and domain addition can be disabled somehow somewhere? To me it looks like a bug but maybe I'm missing on something there.
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...