Thanks again for your help. I will read up on the document you provided. I’m at the point where I see SIP reg going out (do I even need that based one what John said? I don’t know yet), but there is data missing in the contact section that I’m trying to add by modifying the config. The registration has the Contact URI, but nothing else, and i suspect the authentication info CUCM needs is in the remaining part of the Contact info.
Here is what Jabber is sending in the SIP reg:
Contact URI: sip:firstname.lastname@example.org:60548;transport=tcp
Contact URI User Part: a25959fb-253b-a167-96ea-b67b75c77b15
Contact URI Host Part: 10.19.46.18
Contact URI Host Port: 60548
Contact URI parameter: transport=tcp
Contact parameter: +sip.instance="<urn:uuid:00000000-0000-0000-0000-58ef68e5cecc>"
Contact parameter: +u.sip!devicename.ccm.cisco.com="xxxxxxxxxxx"
Contact parameter: +u.sip!model.ccm.cisco.com="503"
Contact parameter: expires=0
Contact parameter: cisco-keep-alive
Contact parameter: video
And the reply I get from CUCM with my SIP reg (missing contact) is (blanked out my user@server):
<--- Received SIP response (502 bytes) from TCP:x.x.x.x.143:5060 --->
SIP/2.0 404 Not Found
Via: SIP/2.0/TCP 10.186.234.24:5060;rport;branch=z9hG4bKPj261ce833-700e-4590-865d-
Date: Sun, 06 Jan 2019 00:18:05 GMT
CSeq: 13849 REGISTER
Warning: 399 <sip server> "**Unable to find device/user in database**"
The fact CUCM can’t find the device, and devicename.ccm.cisco.com=“xxxxxxxxxxx” is in the Jabber SIP reg leads me to believe the “contact parameters” are required fields. But I don’t know for sure.
Anyway, I’ll read up on John’s document to see if I can make any progress. Would really be cool to get this working as it would simplify my workflow a lot.