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

[jokearns1]

Hi,

I do not see your device on the CUCM. Did you receive a mail stating that the device was created? did you create the device through the Collab endpoint portal?

Joe

[Josefine Mages]

No, this is by a customer.

[jokearns1]

Ok. do you know if the customer tried to add the endpoint to our Sandbox lab through the collaboration endpoint lab topology?

Joe

[Josefine Mages · Accepted solution]

I solved it. The UserID an Auth ID was invert.

[harshgow]

I found by keeping the DN/line same as End user name and on Avaya Endpoint Username same as End user name/DN resolved the issue.