search for: nat_en

...ven though in the Grandstream config I have "NAT traversal: no" and leave "Use NAT IP" blank. All the clever stuff is done automatically by Asterisk. However, with the Cisco, that doesn't seem to be the case. I have found it necessary in the SIPDefault.cnf file to set "nat_enable: 1" and then specify as nat_address the public address of my router. Is this normal? What is different between the Grandstream and the Cisco? Is there any way to avoid having to program the external address into the Cisco when it is behind NAT? Thanks in advance for any advice. Cheers T...

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 regis...

...emergency_port: "5060" # Backup Proxy info proxy_backup: "10.6.0.223" proxy_backup_port: "5060" # Outbound Proxy info outbound_proxy: "10.6.0.223" outbound_proxy_port: "5060" proxy_register: 1 timer_register_expires : 120 # NAT/Firewall Traversal nat_enable: "1" nat_address: "" voip_control_port: "5060" start_media_port: "16384" end_media_port: "32766" nat_received_processing: "1" # Phone Label (Text desired to be displayed in upper right corner) phone_label: "Garrett - "...

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

...AN. 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 by the Asterisk box. It works like a charm with the Cisco phone by using the following config info: voip_control_port: 5077 nat_enable: 1 nat_address: "" nat_received_processing: 0 Every time the Cisco phone registers with Asterisk, it does so using port 5077 and with the corresponding port-forwarding rule added to the firewall, it works great. However, for the life of me, I can't get the Aastra to do the same...

...: dialplan messages_uri: 3688 telnet_level: 2 phone_label: "Nat One" line1_name: 3115552368 line1_shortname: 3115552368 line1_authname: 3115552368 line1_password: 3115552368 line1_displayname: "Nat One" logo_url: "http://192.168.1.45/pts.bmp" nat_address: 64.169.xx.xxx nat_enable: 1 nat_received_processing: 1 proxy1_address: myserver.outthere.com My NatTwo phone is similar. The only difference is the name/password using 8115552368. ----sip.conf------------- [3115552368] type=friend host=dynamic username=3115552368 secret=3115552368 nat=1 context=wholesale9 disallow=a...

...e 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 happen to all the phones either. sip fixup is enabled on the PIX phone config parts: nat_enable : 1 nat_received_processing : 0 nat_address: [public ip of PIX] Thank you. -- James (Please CC me on all replies)

...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 /...

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: Shorewal...

...cnf image_version: P0S3-08-9-00 proxy1_address: neocipher.net ; Can be dotted IP or FQDN proxy_register: 1 messages_uri: "100" phone_password: "cisco" ; Limited to 31 characters (Default - cisco) sntp_server: 10.10.10.1 time_zone: EST dial_template: DIALPLAN nat_enable: 1 nat_address: 172.16.2.1 nat_received_processing: 1 outbound_proxy_port: 5060 outbond_proxy: ns1.neocipher.net SIP0112B9EAFF72.cnf image_version: P0S3-08-9-00 # Line 1 Setup line1_name: 101 line1_authname: 101 line1_shortname: "Line 101" line1_password: "test" line1_dis...

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

...proxy_emergency: "10.150.200.165" proxy_emergency_port: "5060" # Backup Proxy info proxy_backup: "10.150.200.165" proxy_backup_port: "5060" # Outbound Proxy info outbound_proxy: "" outbound_proxy_port: "5060" # NAT/Firewall Traversal nat_enable: "0" nat_address: "" voip_control_port: "5061" start_media_port: "16384" end_media_port: "32766" nat_received_processing: "0" # Proxy Registration (0-disable (default), 1-enable) proxy_register: "1" # Phone Registration...

...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 sayi...

...7960 phone at another location. This one is on a private LAN, and uses NAT to get out on to the Internet. I have been successful in registering the 7960 to the local * server. There's no NAT here, so it's easy. I have registered the phone to the remote * server (using nat=yes in *, and nat_enable plus nat_received_processing on the 7960). This works fine too. BUT, I want a line button on the local * box, plus a line button on the remote * box. This works too, for a while. After a short while, usually once I've completed a call to/from the remote * box, the phone starts dishing out...

...n Password # Emergency Proxy info proxy_emergency: "" proxy_emergency_port: "5060" # Backup Proxy info proxy_backup: "" proxy_backup_port: "5060" # Outbound Proxy info outbound_proxy: "" outbound_proxy_port: "" # NAT/Firewall Traversal nat_enable: "1" nat_address: "64.123.190.68" voip_control_port: "5060" start_media_port: "16000" end_media_port: "32768" nat_received_processing: "1" # Phone Label (Text desired to be displayed in upper right corner) phone_label: "Home &q...

...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 detec...