SIP REGISTER fails with 580 but server has no logs

r0nh · ‎03-14-2024

I am trying to send a SIP REGISTER and it fails with 580.

I cannot find out how to determine what is being denied. ie: what i am sending wrong that could result in a 580

is there a way in CUCM to find in a log file somewhere what might be wrong with the packet.

Thanks for anyone reading this.

REGISTER sip:192.168.30.220 SIP/2.0
Via: SIP/2.0/TCP 192.168.208.157:63047;branch=95a1b2a72b10418a3f3f
Contact: <sip:44d955db-d9d4-f630-fe5e-01686318fe2d@192.168.208.157:63047;transport=tcp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-A45630BB643A>";+u.sip!devicename.ccm.cisco.com="SEPA45630BB643A";+u.sip!model.ccm.cisco.com="436"
Supported: replaces,join,sdp-anat,norefersub,resource-priority,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-6.0.0,X-cisco-xsi-8.5.1
Max-Forwards: 70
Expires: 120
Mime-Version: 1.0
Reason: SIP;cause=200;text="cisco-alarm:23 Name=SEPA45630BB643A Load=SIP45.9-4-2SR4-3S Last=reset-restart"
Content-Type: multipart/mixed; boundary=uniqueBoundary
To: <sip:1247@192.168.30.220>
From: <sip:1247@192.168.30.220>;tag=00007ff77ba8d355
Call-ID: 44d955db-d9d4-f630-fe5e-01686318fe2d@192.168.208.157
CSeq: 2999 REGISTER
Date: Fri, 15 Mar 2024 02:29:31 GMT
User-Agent: Cisco-CP7965G//9.4.2
Content-Length: 1356

--uniqueBoundary
Content-Type: application/x-cisco-remotecc-request+xml
Content-Disposition: session;handling=optional

<?xml version="1.0" encoding="UTF-8"?>
<x-cisco-remotecc-request>
<bulkregisterreq>
<contact all="true">
<register></register>
</contact>
</bulkregisterreq>
</x-cisco-remotecc-request>

--uniqueBoundary
Content-Type: application /x-cisco-remotecc-request + xml
Content-Disposition: session; handling = optional

<?xml version="1.0" encoding="UTF-8"?>
<x-cisco-remotecc-request>
<optionsind>
<combine max="6">
<remotecc>
<status></status>
</remotecc>
<service-control></service-control>
</combine>
<dialog usage="hook status">
<unot></unot>

</dialog>
<dialog usage="shared line">
<unot></unot>

</dialog>
<presence usage = "blf speed dial">
<unot></unot>

</presence>
<joinreq></joinreq>
<cfwdall-anyline>No</cfwdall-anyline>
<coaching></coaching>
<oosalarm></oosalarm>
<rpid-orig-called>
</rpid-orig-called>
</optionsind>
</x-cisco-remotecc-request>

--uniqueBoundary--

Maren Mahoney · ‎03-15-2024

A 580 is a "precondition failure" meaning CUCM could not service some aspect of the registration message. (Super helpful, eh?) It could be model, MAC, firmware, or a host of other things. Can you post the 500 error message? That might have more information.

Maren

Maren Mahoney · ‎03-15-2024

Here is a doc describing troubleshooting phone registration in CUCM. Much of it is easy stuff, but the doc does describe what logs to collect and how to do that:

Troubleshoot IP Phone Unregistration Issues in CUCM - https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-version-115/220670-troubleshoot-ip-phone-unregistration-iss.html

Maren

r0nh · ‎03-15-2024

Thank you we have tried almost all of these solutions in the documentation. Nothing showed even a trace of the device showing up as being rejected. But we do get response from the server (as posted above) but none of these logs even show the rejection. I have tried the event logs as well. I see other devices registering but nothing about the rejection. or 580 error indicating anything that might be wrong. And i have tried everything like using the IP address instead of the host. various changes in the supports User-Agent etc. but i am just guessing.

Maren Mahoney · ‎03-15-2024

The above looks like the REGISTER message coming from the phone and not the 580 response from the server. Am I missing something?

Are you saying that the CallManager trace file does not have this REGISTER message in it? If it does include it, can you post (as an attachment to your reply) the trace file so we can see what's going on in CUCM that would generate a 580?

Maren

r0nh · ‎03-15-2024

I do not have any logs on the server side. I did look at them but i cannot find any rejection or anything with this device or any type of error message for this device in the logs. The only reason i know it is a 580 is my wireshark trace.

Roger Kallberg · ‎03-15-2024

Can you please share a screenshot of the trace settings you have for the call manager service? If you don’t have any SDL logs at all then likely you might have deselected all options and unchecked that logs are enabled. If that’s the case you may want to use the option to reset it to default values and then select to set that on all the nodes in the cluster. But before you do that please take a screenshot of this page and share it here.

r0nh · ‎03-15-2024

Here are my settings.

r0nh · ‎03-15-2024

It does download the cnf.xml file and then sends the sip REGISTER

so i know it is actually connecting to the backend. I

r0nh · ‎03-15-2024

Ok so we set everything and I found this

Roger Kallberg · ‎03-15-2024

Those are not the default values. I would recommend you to use the option to set the default values and set that to be used on all nodes. The second picture looks very odd as it’s set to show TFTP service, but the options shown are for the call manager service.

r0nh · ‎03-15-2024

Thank you we changed the server settings and got some valuable information. i see the following do you know what this means. I am trying to figure out what might be wrong but you can see it decided the 508. Hopefully it shows something.

Maren Mahoney · ‎03-28-2024

Also if you would, please pretty please, put your configs and/or debugs in a text file and attach them to a post (rather than pasting your output into the post itself). It makes things much easier for us to look at. Thank you.

Maren

r0nh · ‎03-27-2024

i am still unable to figure out why i cannot register. Hopefully someone will see this .

Maren Mahoney · ‎03-27-2024

There is something funky going on with the ports. The initial request comes in on port 62465, but it's almost like the phone is using that port for communication but embedding 62466 inside the communications. Because of the conflict (if I'm reading this right) CUCM cannot establish communications.

Is this phone behind NAT? Or is there a firewall between the phone and CUCM?

Maren