![]() 13:25:07 switch_core_session.c:1085 switch_core_session_thread() Session 7 Ended ![]() 13:25:07 switch_ivr_bridge.c:505 audio_bridge_on_exchange_media() Hangup [ Edit lines in your SIP conf files and change them as follows:.Starting with a fresh default configuration: You do not need UPnP if you have 1-to-1 NAT or if you have a static public IP address and can put it in your ext-sip-ip and ext-rtp-ip profile parameters. If you do use it, be sure to take protective measures like changing default passwords. Do not use UPnP unless you absolutely have to. One "feature" of UPnP is that it opens a hole in the firewall/NAT device that can (and often does) allow outside hosts to access your FreeSWITCH server. 10 NAT-PMP Devices known to work with auto-nat.4 Making A Test Call and bridging to a SIP phone.This is useful for those routers whose NAT-PMP or UPnP are not working reliably. If you want to use STUN keep the option external rtp, external sip. The auto-nat feature will only perform NAT-PMP and UPnP requests and will NOT fall back in mechanisms like STUN. The default conf/sip_profiles/external.xml is set up specifically for use with providers. NOTE: It is still recommended that you use a second profile for your SIP providers. When the auto-nat feature is fully functioning, only a single SIP profile is needed. The device performing the NAT must support UPnP or NAT-PMP for the auto-nat feature to work. Minupnpd handles both upnp and nat-pmp and doesn't have the same problems.The FreeSWITCH "auto-nat" feature allows FreeSWITCH to use NAT-PMP or UPnP to discover the external IP address. Weird.Ĭode: Select all Mem: 5476K used, 784K free, 0K shrd, 0K buff, 1048K cachedĬPU: 0.0% usr 0.3% sys 0.0% nice 99.6% idle 0.0% io 0.0% irq 0.0% softirqĩ4 92 root S 3456 55.1 0.0 /usr/bin/cm_logic -m /dev/ticfg -c /etĢ05 92 root S 2348 37.4 0.0 /usr/sbin/pppd plugin pppoa 0.38 userĩ1 1 root S 1284 20.5 0.0 /usr/sbin/thttpd -d /usr//sbin/msntp -r 2 -t 5 -p 30 -s uk.poolĢ27 92 root S 704 11.2 0.0 /usr/sbin/upnpd ppp0 br0Ģ28 92 root S 684 10.9 0.0 /usr/sbin/udhcpd /var/tmp/nfġ13 92 root S 640 10.2 0.0 /sbin/dproxy -c / etc/nf -dĮdit Note- this is an old thread, the version of upnpd prior to RT2.5 definitely did have a memory leak over time, would spawn multiple processes and clutter up iptables with old diverts by not cleaning up properly on WAN IP change. I can't show the correct commands to enter here because the forum is configured to reject posts containing references to the specific pathname involved. The RT_cmd_* environment variables need to use the ">" operator to append each command to the end of the file rather than the ">" operator which just truncates and overwrites the file each time it's used. ![]() ![]() Here's a tip for the unwary: if in order to eliminate the memory leaks you are both enabling NAT-PMP *and* disabling UPNP (as I have) then the instructions - if entered exactly as written in upnp.txt - will turn off UPnP but won't enable NAT-SMP. I eventually found the instructions in the routertech docs (upnp.txt) explaining that you need to configure the router's UPnP daemon to switch protocols. I then tried telling uTorrent to use NAT-PMP instead. However having read through the material on this forum I tried disabling UPnP in utorrent and the modem became a lot more stable (although torrent speeds were way down). There's no easy way to see what's going on with it because the first things to go are the thttpd and telnetd services, followed by DNS proxy service, even while it continues to route existing connections for a bit longer before dying completely. UTorrent has been causing my (routertech-2.6) DSL-320T to need rebooting several times a day.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |