Connect unsupported ATA (Linksys PAP2 or Cisco SPA122) to 3CX cloud via VPN

[Heath]

Leejor and Andrily

I take back that the activity log not showing a registration attempt. I had to dig deep in the logs. There was an attempt. Says invalid/unknown/outofdialog request But what is also interesting when I plugged the ATA in my internet went down. And my modem rebooted. I first thought that was too odd. Then I unplugged it and plugged it back in and bam my internet went down again.

 

[leejor]

Well...that's not normal. If plugging in a device knocks down your network, then perhaps something in the network settings of the device are causing the crash. Did you assign the 122 a static IP, gateway and DNS server, or is it using DHCP?

Do you have the Ethernet cable plugged into the correct socket?

You want to use the Blue "Internet" port. the yellow "Ethernet" port will be trying to assign Ip addresses unless you have changed it to Bridge mode.This device is also a router, the SPA112 and is over-kill for most users. You must also allow access from the WAN side before you make the changes or you won't be able to communicate with it.

 

[Heath]

No static IP. It’s using DHCP. But I set up a DHCP reservation in my routerand it is plugged in to the internet port. Nothing plugged in to Ethernet

 

[leejor]

Can you post the 3CX Activity Log, that you got, when the 122 attempted to register?

Since it sounds like you have an SBC on the same network, I'm wondering if there might be some conflicts. Causing things, like a modem to re-boot is not something a device should be able to to. Are there other SIP devices NOT using the SBC, on the same network? Do you have access to any other location that has no other SIP devices, just to confirm the 122 works?

 

[Heath]

I can try to find and copy and paste it. I currently have 4 other devices that connect through SBC without any issues and the ATA will connect thought SBC without any issues as well. I have 5 other devices that connect through STUN without any issues as well. All on the same network. The 4 that are on SBC I would love to connect through STUN, but those devices don’t support it until I eventually replace them

 

[leejor]

I have 5 other devices that connect through STUN without any issues as well. All on the same network.

And that might be the cause of some of the problems you are having trying to add the 122.

 

[Heath]

And that might be the cause of some of the problems you are having trying to add the 122.

How could that be. And how would I split off my network. I only have 1 internet coming in and 1 router at the internet modem

 

[Shawn]

I'm not expert in this topic but was just reading about STUN on the 3CX site and ran into the following statement at:

https://www.3cx.com/blog/voip-howto/stun-voip-1/



I wonder if you're having connectivity issues after a certain amount of time because of your firewall not being setup as full cone which can result in ports being remapped.

 

[leejor]

How do you have the STUN devices configured? Are each assigned a unique local port? Are each of the extensions using the PBX delivers Audio option? Even if that is the case, some routers can have problems keeping track of the audio ports, which can result in no audio one way. Since you seem to have 4 devices working, your router may be able to handle that, adding a 5th might be a problem. three may also be another setting in the 122 that need correction

This is all speculation as i have don't have all the details of your network set-up. Since you have devices working through an SBC, I don't see why you would not run all of them through it. Sending all audio, between remote devices, back through the server, is not a good use of bandwidth.

 

[Heath]

My network setup is My Internet Modem / Router. HubSwitch, then all devices connect through the HubSwitch... My 3CX is running in a cloud. I have those devices running through SBC as they are legacy devices that evidently do not support STUN, so I have no choice, but to run those devices through SBC. The others running STUN so as to be able to connect directly to the PBX in the cloud. eventually I am going to upgrade those devices that is running through SBC so to connect to STUN. Eventually I do not want anything being ran through my location. Otherwise I'd have the 3CX running in my office. I'm already having issues with the SBC that if my internet connection goes out briefly, I have to re-boot the computer that the SBC is running on. And this is an issue that no one at 3CX can figure out why once the internet connection comes back up, the SBC comes back on line.. Now Another issue that has popped up with the SPA112, is for some reason it keeps crashing my internet connection and my modem reboots. I was having internet connect issues, and it was determined to be the SPA112 device as after I plugged it in, in a matter of seconds it crashed my internet connection. I even tried a different Cat5 cord, and as soon as it plugged it in Crashed again, and after the internet came back up, within 5-10 minutes would crash again... Now I even took the device to my house to see if it would do the same (trying process of elimination), and would you know it, it crashed my internet at my house too. So now I need to figure out why the SPA ATA keeps crashing the internet.

 

[leejor]

All i can say is that the SPA122 should not be crashing your network. I have no idea what is causing that to happen, but perhaps Wireshark may be of some help in diagnosing it.

As far as STUN...while it will work, or in some cases, "may" work, it is not the best solution for a location with more than a couple of devices. the idea of moving towards using STUN on all devices is not a good idea. I can certainly understand the frustration with the SBC issues, but it if it were me, I'd be more concerned with why the internet is failing on a regular basis, and makje my provider fix it once and for all. You might consider trying the Raspberry Pi SBC. For about $35 US, it is not a big investment, and the power savings alone would probably pay for the device over time.

Without being there, it is very difficult to diagnose the problems you are having. If you are serious in making this work, you might consider local tech support, whether that be a 3CX partner, or simply someone familiar with networks.