NAT Blues
Submitted by wsieber on Thu, 07/31/2008 - 6:59am.
I am running TB 2.2 I have a Grandstream 2000 at my home office. I am able to dial out with no problems; however, I am unable to hear inbound ringing, and when other extensions try to connect to me they get a busy signal.
I have the routers on both ends with the correct settings. I believe that my config files have the correct settings as well. Not sure what I am missing.
Has anyone else seen this behavior, and if so, what was your solution?
Thanks,
Willie
Router
Thu, 07/31/2008 - 6:27pm
Scott,
I appreciate you taking time to reply. I have spent the day reading and trying to absorb all the threads relative to remote extensions via SIP and NAT.
My router is a D-link 655 on both the client and the TB server side. I have ports 5060-5082 and 10000-20000 forwarded on the server side.
After spending the afternoon fussing with the Grandstream, I dropped a Linksys 942 on to try instead with identical results. My sip_nat.conf contains the following:
port=5060
nat=yes
externip=mystatictserverip
localnet=192.168.1.0/255.255.255.0
externrefresh=10
disallow=all
allow=ulaw
allow=alaw
allow=gsm
I have reviewed the 942 phone settings; they are essentially stock from Kerry G's setup tutorial. As I indicated, the phone registers without a problem (as did the Grandstream). I can make outbound calls from the remote with no problems, audio or otherwise; however, the remote extension will not ring. When someone in my office trys to connect to my remote extension they receive a busy signal.
Thanks,
Willie
give this a try
Thu, 07/31/2008 - 7:44pm
i am no expert but here is what works for us in the sip_nat.conf file
nat=yes
externalhost=mstaticserverip
localnet=192.168.1.0/255.255.255.0
note that this assumes that your remote phone is on the 192.168.1.0 subnet.
we have exactly the same symptoms until we put these three lines in sip_nat.conf.
Quote:
note that this
Thu, 07/31/2008 - 7:55pm
Member Since:
2007-03-08