search for: nat_enabled

I have used Grandstream phones for years, and have just started testing a Cisco 7940 (with SIP firmware 7.4). I have found something puzzling and don't know whether it's just a limitation or something I haven't done correctly. The Asterisk server is directly on the Internet with a public IP. The phones are on a private LAN with a NAT router to the Internet. The sip.conf entries for

Hi List, I've got a 7960 that's behind NAT (nat_enabled: 1 and nat_received_processing: 1) and for whatever reason doesn't seem to register, or at least hold a registration. If both the phone and the router (netgear) are rebooted, the phone will register, take a few incoming/outgoing calls no problems, then a few hours later, it drops the registrati...

Hi all, So I have been reading through the docs available online and the different threads on this list, but I cannot seem to get this phone to work. I have configured the OS79XX.TXT and SIP/SEP*.cnf files (see attached), when I configure the phone to point to my tftp server and reboot it I get this message: Connection received from 10.6.0.224 on port 50608 [09/02 12:16:11.750] Read request

Hi I have a problem with Shorewall on my two-interface connection. I run Debian unstable. The setup looks like this: Internet -------- router ------- server 213.237.12.137 192.168.1.3 192.168.1.2 192.168.0.7 --- local net 192.168.0.{...} I can ping the server from the local net, and the local net from the

I've been pulling out my hair all day on this one. If anyone can help, I'd really appreciate it. :-( I've got an Aastra 9133i (with the latest firmware version) and a Cisco 7960 sitting behind a NAT device on my LAN. The Asterisk server is hosted offsite and has a public IP address. I've set up port-forwarding on the firewall for both phones to tunnel the SIP messages initiated

I need to set up an office full of Cisco 7960 phones behind NAT with the server out in Colo. The first test phone registers fine, but the second one does not register. The first phone's registration looks like so: /SIP/Registry/3115552368 :64.169.xx.yyy:38836:3600:3115552368:sip:3115552368@64.169.xx.yyy:5060 When the second phone tries to register, it gets back a 404 not found. Not a

Hi, I have about 10 Cisco 7960s behind a PIX 506E (IOS v6.3) firewall. After some period of time, asterisk says that some of them are unreachable, and the phones lose their registration. The only way to make the phones recover is to clear the NAT translation tables for the phones on the PIX (clear xlate...) Does anyone know how to fix this? As you can imagine, it is quite annoying. And it does not

...ions, an undocumented feature allowed entries in the host file as follows: z eth1:192.168.1.0/24,eth2:192.168.2.0/24 This capability was never documented and has been removed in 1.4.6 to allow entries of the following format: z eth1:192.168.1.0/24,192.168.2.0/24 2) The NAT_ENABLED, MANGLE_ENABLED and MULTIPORT options have been removed from /etc/shorewall/shorewall.conf. These capabilities are now automatically detected by Shorewall (see below). New Features: 1) A ''newnotsyn'' interface option has been added. This option may be specified in /etc/s...

I am having a problem registering my cisco phones which is exactly like that described in http://lists.digium.com/pipermail/asterisk-users/2011-May/262306.html except that I am on Asterisk 1.8.3.3 and using sip level POS3-07-4-00 The symptoms are: o 7960 lines show [X] o Outbound calls can be made from the phone, including call pickup of inbound calls, but not to it. o Trace shows REGISTER

...combination of a DNAT-rule and one or more ACCEPT rules. That technique is still preferable for load-balancing over a large number of servers (> 16) since specifying a range in the DNAT rule causes one filter table ACCEPT rule to be generated for each IP address in the range. 5) The NAT_ENABLED, MANGLE_ENABLED and MULTIPORT configuration options have been removed and have been replaced by code that detects whether these capabilities are present in the current kernel. The output of the start, restart and check commands have been enhanced to report the outcome: Shorewall has...

I've searched around and found a few similar situations where the phone will call out when using a Asterisk server but not receive inbound calls. My issue is a little stranger. If I call out from the phone then the phone will receive the next inbound call. The phone will not receive another inbound call until a call out again from it first. Any ideas? I am using SIP and am using the latest

Hi people, I am running the latest version of Debian ''Sarge''. I have installed hopefully the latest version of shorewall, as followed by the website. The firewall has been installed with no problems, runs ok, but I have found a strange problem, maybe it me *shrug* My setup: Internet<-->cablemodem<-->Debainfirewall<-->hub<-->windowspc I am cable, and

Hi, I'm experimenting with the dev kit lite and now past the USB unpleasantness it's working great with standard phones and lines. The priority right now is getting soft phones (under Windows XP) working well. So far, I've only been able to get the XTEN Lite phone working and I really don't understand how I set it up. I used "xten" for every option everywhere (display

I cannot get incoming calls to sip phones behind a PIX to work, outgoing is fine. Asterisk (Public IP) --> Internet --> PIX (NAT) --> Sip Phones I have tried no fixup protocol sip, I have punched a hole in the Pix allowing anything from the Asterisk box into the network, still no incoming. I have done all the Wiki suggests in regarding to NAT. Is their a trick getting the

Hi, I am upgrading a Cisco 7960 phone from SIP V.5.1 to 6.0 and then will to go up to 7.5 However in my first attempt to go from V.5.1 to 6.0 this is hat happens: - The phone reboots - The phone then reads the file OS79XX.TXT from the TFP server. In the file I added the version "P0S3-06-0-00" - It starts upgrading firmware - Then I get the following message: (Upgrade Failed -

...wall to add aliases to other than the first subnet on an interface. 6) Add support for load-balancing. 7) Toned down the disclaimer for the ''check'' command. 8) Implemented support for the Connection Tracking Match extension in iptables 1.2.8/Kernel 2.4.21. 9) Removed the NAT_ENABLED and MANGLE_ENABLED configuration parameters and replaced them with code that detects these capabilities. -Tom -- Tom Eastep \ Shorewall - iptables made easy Shoreline, \ http://www.shorewall.net Washington USA \ teastep@shorewall.net

...In the QuickStart Guides, you will find: ------------------------------------------------------------------------------- If you are using the Debian package, please check your shorewall.conf file to ensure that the following are set correctly; if they are not, change them appropriately: * NAT_ENABLED=Yes (Shorewall versions earlier than 1.4.6) * IP_FORWARDING=On ------------------------------------------------------------------------------- I really don''t know where to repeat this information in the documentation. Seems wrong to include a section in the Upgrade article saying:...

I'm having an interesting problem with a Cisco 7960 phone, and two Asterisk servers. I'm not sure if this problem is specific to the 7960, or even to Asterisk for that matter. Here's the scenario. I have an * server at one location with a public IP address (i.e. not behing NAT). I have a second * server and 7960 phone at another location. This one is on a private LAN, and uses NAT to

Running those versions of code, my 7960 will not register with Asterisk. The same 7960 is authenticating against another * server on line 2 just fine though - with the same settings in sip.conf. On the failing * server I am just getting 401 unauthorized errors on the console. From the phone's shell I get that t is registering, but not authenticated .1. from show reg. Any ideas would be

...combination of a DNAT-rule and one or more ACCEPT rules. That technique is still preferable for load-balancing over a large number of servers (> 16) since specifying a range in the DNAT rule causes one filter table ACCEPT rule to be generated for each IP address in the range. 5) The NAT_ENABLED and MANGLE_ENABLED configuration options have been removed and have been replaced by code that detects whether these capabilities are present in the current kernel. The output of the start, restart and check commands have been enhanced to report the outcome: Shorewall has detected t...