One of Cisco employees shared a document on how to configure Cisco SPA 112 ATA on CUCM. The document walk you through the setup and common issues encountered with solutions. My challenge was I had difficulty in registering Cisco SPA 112 ATA to CUCM 10.5.
I took a packet capture on the registration process and a 404 Not Found message was sent from CUCM to Cisco SPA 112 ATA. Then the registration was terminated.
Time Source Destination Protocol Length Info 98.128001 192.168.1.243 192.168.1.242 SIP 648 Request: REGISTER sip:192.168.1.242 (fetch bindings) | 98.132134 192.168.1.243 192.168.1.242 SIP 648 Request: REGISTER sip:192.168.1.242 (fetch bindings) | 98.143224 192.168.1.242 192.168.1.243 SIP 384 Status: 100 Trying (0 bindings) | 98.144496 192.168.1.242 192.168.1.243 SIP 399 Status: 100 Trying (0 bindings) | 98.145221 192.168.1.242 192.168.1.243 SIP 507 Status: 401 Unauthorized (0 bindings) | 98.235552 192.168.1.243 192.168.1.242 SIP 833 Request: REGISTER sip:192.168.1.242 (fetch bindings) | 98.236518 192.168.1.242 192.168.1.243 SIP 384 Status: 100 Trying (0 bindings) | 98.240406 192.168.1.242 192.168.1.243 SIP 479 Status: 404 Not Found (0 bindings) |
Went through the details of 404 Not Found SIP message, it contained a warning message Line not configured. This error message was interesting and the same time a clue to the problem.
Session Initiation Protocol (404) Status-Line: SIP/2.0 404 Not Found Message Header Via: SIP/2.0/TCP 192.168.1.243:5076;branch=z9hG4bK-2909dc63 From: "SPA112" <sip:[email protected]>;tag=ae8d93bc28a05ac6o0 To: "SPA112" <sip:[email protected]>;tag=1282891069 Date: Sun, 14 Sep 2014 23:43:05 GMT Call-ID: [email protected] Server: Cisco-CUCM10.5 CSeq: 17101 REGISTER Warning: 399 cucm-pub "Line not configured" Content-Length: 0
Checked my configuration on the CUCM all looked good. Thinking of the Line not configured warning message, what made CUCM spit out this message?! The parameters that were related to the error message that I could think of were user/line association and username format (i.e. alpha, numeric and combination of both).
Tested different combinations and finally found the answer. CUCM didn’t accpet a user ID that contained alpha only and alphanumeric characters. It must be numeric only and line or extension number should also be the user ID. For instance, if you had an extension of 1000 then the user ID should also be 1000.
Here is a a packet capture of a successful registration.