Cannot register a third party SIP phone in the UC Endpoint lab

[preichl]

I have been using the UC Endpoint lab to create a third party SIP phone.

I am able to login to the VPN and connect to CUCM 10.5.2. and send SIP messages to it. The problem that I am having is the my system cannot register the phone using the assigned directory number.

Here is an example of the SIP transactions. CUCM is return a 404 Not Found response.

Is there any way to configure CUCM to register the assigned directory number for the extension?

Sent at: 08/14/2015 15:58:48.3554
REGISTER sip:10.10.20.1 SIP/2.0
Via: SIP/2.0/UDP 172.16.255.78:5064;branch=z9hG4bKe8b62881933f4b5fa77014cc2a992226
From: "3522" <sip:3522@10.10.20.1>;tag=10b355a6f51f46a7a53b1336141d230f
To: <sip:3522@10.10.20.1>
Contact: "3522" <sip:3522@172.16.255.78:5064>
Authorization: Digest username="3522", realm="ccmsipline", algorithm=MD5, uri="sip:3522@10.10.20.1:5060", nonce="WfUamNYsQ3r7c4fpcUvIT0wNTnl4aGcQ", qop="auth", response="6f32172334d5c54632cee89b6e225c54"
Call-ID: cc71c9cfc77a4f9898cd32070d4090d3@172.16.255.78
CSeq: 10003 REGISTER
Expires: 150
User-Agent: AdminUa
Max-Forwards: 70
Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,PRACK
Content-Length: 0

Received at: 08/14/2015 15:58:48.5576
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 172.16.255.78:5064;branch=z9hG4bKe8b62881933f4b5fa77014cc2a992226
From: "3522" <sip:3522@10.10.20.1>;tag=10b355a6f51f46a7a53b1336141d230f
To: <sip:3522@10.10.20.1>
Date: Fri, 14 Aug 2015 22:58:52 GMT
Call-ID: cc71c9cfc77a4f9898cd32070d4090d3@172.16.255.78
CSeq: 10003 REGISTER
Content-Length: 0

Received at: 08/14/2015 15:58:48.6718
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP 172.16.255.78:5064;branch=z9hG4bKe8b62881933f4b5fa77014cc2a992226
From: "3522" <sip:3522@10.10.20.1>;tag=10b355a6f51f46a7a53b1336141d230f
To: <sip:3522@10.10.20.1>;tag=364768070
Date: Fri, 14 Aug 2015 22:58:52 GMT
Call-ID: cc71c9cfc77a4f9898cd32070d4090d3@172.16.255.78
Server: Cisco-CUCM10.5
CSeq: 10003 REGISTER
Warning: 399 hq-cucm-pub "Unable to find device/user in database"
Content-Length: 0

[dstaudt]

This checklist for configuring 3rd party SIP phones may help:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/7_1_2/ccmcfg/bccm-712-cm/b09sip3p.html

Steps 3/6/8 are possibly involved with the SIP flow given.

[preichl]

Step 8 indicates that it is necessary to associate the third-party SIP phone with a user using Device Association. This seems to suggest that it is necessary to connect to CUCM from the Sandbox Lab in order to do this. When I click on the CUCM icon in the Sandbox Lab screen and select Connect --> HTTP, the Sandbox opens an new Web page. When I select Cisco Unified communication Manager, it takes me to Cisco Unified CM Administration. This page asks for a username and password. I tried the username and password that I use to log into DevNet but this does not work. What username and password should I use?

[jacoadam]

Hello Philip-

This is a shared lab by many users, so we can't offer administrative access to the UCM manager. If you'd like administrative access to Call Manager, try reserving the Collaboration 10.5 lab - that should meet your requirements.

However - I have verified the settings of your SIP device. The SIP device ABCD12XXXXXX (DN: 3522) is currently associated to the user preichl@XXXXXXX.com69. Please review the settings in the attached screenshots. Please note you should of received an email with the credentials for the above account. I'm not sure if you need them but make sure that you use those and not your DevNet credentials! The user in CUCM is just a local user so please use that password. Please let me know if you have any additional questions and I'd be happy to help out!

Thanks!

Jacob Adams

DevNet Sandbox Team 

NOTE: I have masked out all sensitive info, the blanked info in the username is your email domain associated with this account.

[preichl]

I started using the Collaboration 10.5 lab instead of the UC Endpoint lab. I am able to log into CUCM and have administrative privileges. The lab contains two instances of CUCM. One is called ...Cisco UCM 10.5 Publisher... and one is called ...Cisco UCM 10.5 Subscriber... What is the difference between these two instances and which one should I be using?

[jacoadam]

The Publisher and Subscriber work together as they are in one call processing cluster. To keep it simple, the publisher is the main administrative node in the cluster, and it holds a the writable configuration database. The Subscriber (subscribes to the publisher) contains a read only configuration database from the publisher. When changes are made on the Pub, the database is replicated to the sub.

For the sake of this lab and learning, your best bet is to register phones with the Pub, and make all config changes there.

Does that answer your question?

Thanks!

Jacob

[preichl]

I can connect to the publisher instance of CUCM in the Collaboration 10.5 Lab. I created two phone devices and two users and am able to get our application to successfully perform a SIP REGISTER with the first digest user but CUCM returns 401 Unauthorized for the second digest user. I have captured a Wireshark trace and exported and downloaded the configuration file for CUCM. I would like to send you these files to look at but I don't see any way to upload files on this forum.

[jacoadam]

Hello Philip-

I have selected to "add you as a friend" on this forum. Once you approve this I we can set up a WebEx and I can take a look at your issue. Please let me know once you have done this.

Thanks!

Jacob

[preichl]

Jacob,

I have approved. But right now I cannot get to the sandbox. It appears as if there is some kind or outage.

Regards,

Philip H. Reichl

Modular Communication Systems

[jacoadam]

Philip-

This is correct. We're currently experiencing a link outage. We're working on it and hope to have things up shortly. I'll let you know. Apologies for any inconvenience.

Thanks!

Jacob

[oliverbodden]

Hello,

Not sure if this is solved, but I had a very similar issue, briefly, when registering a Media5Fone app to CUCM 11.

To solve it, I used the user assigned to the actual device under option Digest User (this is located under Protocol specific information not under Owner User ID) as the Authentication ID on the app (the one used on the AUTHORIZATION header of the SIP message), and the actual DN or Line assigned to the device as the username (the one used on the FROM header of the SIP message).

Also, make sure you added the Line association with the SIP device, in other words the extension or DN that the device will use.

Let me know if this helps!

[preichl]

Oliver,

I had already found the solution and have registration working correctly.

Thank you anyway.

[Josefine Mages]

Hello Philip,

what is the solution? I have the same problem.  Registration State is Failed 404.

Can you help me?

Best regards,

Josefine

[jokearns1]

Hi Josefine,

What is the MAC address of your endpoint?

Joe

[Josefine Mages]

this is my Mac Adress: 10BD18AE7EAF. I have this problem by a customer.