Resolved this issue. In Call Manager CUCM under enterprise parameters there is a section called Clusterwide Domain Configuration. Put the parent domain in the 'organization top level domain' field like "domain.com" and in the 'cluster fully qualified domain name' field put all the domains in which you are using DNS SRV records, delimited by a space like "domain.com *.domain.com" where an asterix is wildcard and in my example it allows all subdomains of the parent as valid.
This makes the SPA device register the line, receive incoming calls, and be able to make outbound calls.
Debug on the SPA was showing Warning: 399 CUCMSERVERNAME "Invalid host or domain in request URI" in the SIP traffic that occurred when outbound calls failed, which lead to research that discovered this solution.
... View more
With no other changes to either call manager or the SPA device, if I enter one call manager's IP address as the proxy and set the spa to NOT use DNS SRV, everything works perfectly. If I enter a domain as proxy and tell the spa to USE DNS SRV then the lines register and can take incoming calls, but cannot place outbound calls. Call Manager plays the recording like it might if your line did have a CSS that could place that call.
Again, with no other changes in call manager or the SPA, just changing the SPA from ip address as proxy to domain with DNS SRV as proxy breaks outbound calling ability.
Anyone know why?
... View more
Use the ip of whichever CUCM server you prefer it to register to. Alternately, use a domain name in that field and create SRV records in that domain which point to your call manager servers with your chosen priority/weight configuration. This allows the device to fail to a different call manager if the first one goes down.
You make an SRV record in dns in the zone you entered as proxy in your SPA (voip.domain.com, for example) and then the SRV record would be like _sip._udp.voip.domain.com with your SIP port (5060 usually), and a priority and weight for each call manager server based on the order you want the device to try to register to them. Lower number is higher priority, think of weight as load balancing within servers with the same priority number. Easiest if you have three CUCM and you want the device to register to them in one specific order, top down, is to set them as priority 1,2, and 3 and weight 100 for all.
On the spa you would have to set use dns srv to yes and the auto prefix based on if you're using the default (_sip._udp.) and whether you manually included it in your proxy address or just left it as voip.domain.com or domain.com or whichever domain you created your SRV records in.
... View more
SPA 8000 firmware 6.1.12SR1
Ports 3-8 seem to be sending an IP address on the SPA's own LAN (192.168.101.X) in their SIP registration messages. Ports 1-2 send the IP of the device itself. Any way to get the device to use its own actual IP (WAN static IP) in the SIP registration for ALL ports? Call manager is rejecting registration of lines 3-8 because of this IP issue. The device shows a different IP on its own local LAN 101.X for each pair of ports (ports 3-4 as 101.2, ports 5-6 as 101.3. ports 7-8 as 101.4).
The management console for the device does not appear to allow turning the device's local LAN on/off, or making any changes to its configuration. The admin guide indicated IVR option 201 can be used to switch the device between router (assumed default) and Bridge/Switch mode (assumed what I need) but the device says option 201 is invalid when I try to use it in the IVR.
... View more
One CUCM end user (one license), one (or possibly more) SPA device, multiple lines. Here's how:
(valid for CUCM 11.5 and SPA112 firmware 1.4.1)
under System -> Security -> Phone Security Profile, added a phone security profile called SPA112 which was a copy of the third party SIP ADVANCED profile but with the "enable digest authentication" box checked
the SPA device is then added as a third party ADVANCED device type phone, with device security profile of SPA112 and "owner user ID" and "digest user" both set to the one CUCM end user account created for faxing (in this example 0586 is the user ID, I think it must be numeric only)
added two lines to the SPA device, for each one being sure the full 10-digit number of the fax as the external phone number mask, max calls and busy trigger both to 1, and check the caller name and dialed number boxes for forwarded call information display. also must associate the user (0586) with the line after saving line for the first time.
then on the SPA device:
after basic IP and administrative config
on the voice tab, for line 1 set SIP transport to TCP make sure SIP port is 5060 (default for line 1 on SPA but not for line 2, 5060 is defined in CUCM on the SPA112 device security profile that was created above) set proxy to IP of CUCM subscriber display name (optional I think) to same as caller ID for the line in CUCM user ID as the 4-digit extension of the line (last four of fax number) auth ID as the ID of the CUCM end user (0586 in this example) password as the digest credential for the CUCM end user use auth ID set to YES
then for line 2 do the same thing, making sure the user ID is the 4 digit extension you want line 2 to be but the other ID and password fields are the same as line 1 because both use the same CUCM end user, and making sure the SIP port is 5060 NOT 5061 like is likely the default for line 2 in the SPA device
all other settings for the lines on the SPA probably don't have to be modified. I was able to get faxes in and out without changes any of the other factory default settings not explicitly mentioned here.
make sure your inbound and outbound call routing, however you are doing it, is set up properly and then test and you should be good to go. be sure you know if, from the analog phone or fax you need to be dialing a 9 or anything to get an outside line, or if you have to dial a # after a 4-digit extension if you didn't modify the dialing plan on the SPA device and don't want to wait for the inter-digit timeout.
NOTE: the SPA device as registered in CUCM will show "Partial Registered" status but this doesn't seem to matter. both lines work and can be used simultaneously
have only done this with 2 lines at this point but I would guess that you could have another SPA device with 2 lines, configure them with different extensions but use the same CUCM end user, and make them lines 3 and 4 (or 5 and 6, or 7 and 8) on the "phone" you added already and it would probably work without consuming more licenses as it seems a third party SIP device can take 8 lines. UPDATE: This works for OUTBOUND only. Inbound only one SPA per 3rd party phone registered will work (whichever one has its IP registered to call manager which is probably the last one installed). So if you are looking to minimize licenses consumed, buy a SPA8000 for 8 analog lines to 1 user license and I would guess you'd be fine. otherwise its 1 user license per SPA/ATA (1 user license per however many FXS ports are on the physical SPA/ATA device).
SPA8000 and SPA8800 also exist and have more ports, but I don't have any hands-on time with those
... View more