jgn1013, I'm just starting to get active on the forum again. I'll see if I can get the code packaged up and posted somewhere. Were you able to post the code anywhere? Also I'm looking for a job myself, if anyone knows of anything in the Southeast US area: https://www.linkedin.com/in/justinpaulgoldb...

Chip, correct, for a single remote phone, you'll only need to NAT forward udp/506x.

For the Allworx server side, I believe that you only need to forwarding 5060 regardless of the remote phones port.

SunLink, that's a good resource, so I'll leave it here.

I may sticky this post, since it's something possibly not mentioned here before. Allworx support has stated that you only need to forward the SIP messaging port (5060/udp default), and the remote (AllWorx!) phone will work; NAT handles the audio/signaling ports; then if you have no audio or can't re...

There's been a lot of DoS attacks against allworx servers, some after being patched against sip attacks. This has led to them being corrupted and requiring a subsequent factory defaulting and reprograming from scratch. To prevent this, do the following: For single sites, disable smtp port 25 on Netw...

You would need a vpn connection that has a route to the phone vlan.

Interact is out!

http://get.allworx.com/interact/

Here's the user guide:

https://allworxportal.com/documents/sup ... _Guide.pdf

mw, if there's no problem then ignore that error. The event logs are for debugging the system.

The option for sip nat keep-alive interval is for remote firewalls that timeout the connection.

Did you enable Intercom Auto Answer (speakerphone activates automatically) in the phones handset preference group?

Try putting the allworx in front of the firewall. This will tell you which firewall is having trouble.