TIPS SPA112 Won't Register

jeremytourville

New Member
Joined
Jun 30, 2016
Messages
5
Reaction score
0
I installed this version of pbxiaf from github -incrediblepbx13-raspbian8-gvoauth.zip.
I did all the normal security updates from the script, configured my trunks, routes and extensions. Everything is working except getting my ATA to register to the PBX. My ATA is at the latest firmware release 1.4.1 from Cisco. I did a factory reset on the ATA to set everything stock and put in the extension, secret and made sure the port numbers matched. Both devices are one the same subnet. If I power cycle the device you can see it go from "not registered" to "failed" You can review my support thread over at Cisco forums if that helps.
https://supportforums.cisco.com/discussion/13060006/spa112-not-registering

I am able to get a softphone to register. The issue seems to be specific to my ATA. I did try turning on SIP debugging and looking through /var/log/asterisk/full. I can see in the log where the softphone registers but I don't see any activity from the ATA. Any thoughts on where to start on this?
 

atsak

Guru
Joined
Sep 7, 2009
Messages
1,784
Reaction score
171
Try changing the port on the Cisco to 5061 from 5060 for registration?
 

jeremytourville

New Member
Joined
Jun 30, 2016
Messages
5
Reaction score
0
I'll try that. I see now you can choose chan_sip or PJSIP. Make a difference on which one to use? I am trying to get up to speed on the newer PJSIP.
 

jeremytourville

New Member
Joined
Jun 30, 2016
Messages
5
Reaction score
0
Thanks for the tips. I'll report back later this afternoon when I get home from work.
 

jeremytourville

New Member
Joined
Jun 30, 2016
Messages
5
Reaction score
0
ok, as I thought about this more I realized maybe the firewall was blocking my ATA, especially since I wasn't seeing evidence of the ATA trying to connect in the logs. I issued iptables -A INPUT -i eth0 -s 172.30.42.33/27 -j ACCEPT. I issued a quick iptables -L and I could see the new rule in the input chain. Now I tried again to get the ATA to connect. This time it worked. As a final test I wanted to make sure everything continued to work after a reboot. I issued an Amportal stop and reboot on the PBX. At this point the PBX started to reboot and I could still see the registration lights were on for my ATA. After the PBX came up and Asterisk was running I rebooted my ATA. When the ATA finished bootup it connected. As a final check I ran iptables -L to see my rules. I no longer see my input chain allowing the subnet. While I am happy to be connected I am not sure why everything is working. What else gets written to that allows the ATA to connect?

-signed happy and confused at the same time
 

Members online

PIAF 5 - Powered by 3CX

Forum statistics

Threads
22,317
Messages
136,983
Members
14,545
Latest member
aigyu