<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>Thanks for the thoughtful response. I think that it has been by some happy accident that I have not run into more NAT issues. I usually expect to have problems and then rarely do. For example, I have a FreePBX server sitting behind the pfSense as well (on a different subnet) which is my main office phone system, it is connected to my ITSP (Teliax) with absolutely no problems - no port forward or static port NATing needed - as soon as I cut over to the pfSense, I was up and running.<br><br>I think you are right re: with the rport issue. At the end of the day, I think the combination of Freeswitch not detecting NAT and the HT-287 not supporting rport was what caused the problem. <br><br>Will be doing some more investigating on all this - in particular I am now curious to look into how/why my RTP streams work. I have about a dozen customers running various combination's of FreePBX/ATAs/Etc and have never had audio issues - again, probably a happy accident, but now I am motivated to understand the dance that is happening between everything.<br><br>Thanks again,<br><br>Dave <br><br>----- Original Message -----<br>From: "David Ponzone" <david.ponzone@ipeva.fr><br>To: "FreeSWITCH Users Help" <freeswitch-users@lists.freeswitch.org><br>Sent: Sunday, August 29, 2010 5:06:36 PM GMT -06:00 US/Canada Central<br>Subject: Re: [Freeswitch-users] NAT traversal questions - (long)...<br><br>Dave,<div><br></div><div>I misread your mail the first time and did not see you sent traces.</div><div><br></div><div>I think there are some interesting things in those.</div><div><br></div><div>For the packet coming from your HT-287 without the static port NAT:</div><div><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; font-size: medium;"><div><div style="font-family: 'Times New Roman'; font-size: 12pt; color: rgb(0, 0, 0);">Via: SIP/2.0/UDP 10.8.11.149:5062;branch=z9hG4bKda48f838c8689e41</div></div></span>-> rport is missing</div><div><br></div><div>For the packet coming from the one behind a DD-WRT:</div><div>rport is missing too, but the source port in the Via matches the source port of the packet, so it works, the same way it works with your pfSense if you add the static port NAT.</div><div>But why FS manages to guess it's behind NAT eludes me, but the NAT detecting algo in FS is clearly complex.</div><div><br></div><div>For the packet coming from the HT-503:</div><div>I think you made a mistake. You said at the beginning of your mail that it is behind DD-WRT, but before the trace, you say "one more packet coming from Comcast/SMC".</div><div>Anyway, this one is interesting.</div><div>rport is there, so HT-503 is rport-capable (but HT-287 is not).</div><div>I would check if a configuration or a firmware upgrade could enable rport on the HT-287.</div><div><br></div><div>Also, you wonder if modern routers have some automatic static NAT.</div><div>Actually, no, but what they do quite often is to not change the source port of the packet if this port is available on the external interface.</div><div>For instance, if your device sends a packet from port 5060, and this port is free on the external side of the router, it will preserve 5060.</div><div>Then if a second device sends a packet from port 5060, as it is already used, it will use a random port.</div><div>You end up having a pseudo static NAT behaviour for the first device on your network.</div><div>I saw that on business routers from Draytek, Funkwerk and others.</div><div>So perhaps your ipcop was doing that ?</div><div>Wild guess: if you add a second phone with the same source port 5060 behind a DD-WRT router, I am pretty sure you will have issues with its registration.</div><div><br></div><div>About your question "is FreeSWITCH not tagging the device as behind nat because it is on the same subnet as pfSense ?".</div><div>That's quite possible.</div><div>I think there are places in FS conf where you define what is local. I think it's the special keyword localnet.auto.</div><div><br></div><div>But I really think the end of all isues is rport.</div><div>If rport is not available on your device, you can still force rport on FS side:</div><div><param name="NDLB-force-rport" value="true"/></div><div><br></div><div><div> <div style="word-wrap: break-word; font-size: 14px;"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 14px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px;"><div style="word-wrap: break-word;"><div><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" color="#1c00ff">David Ponzone </font><font class="Apple-style-span" color="#000000" size="3"><span class="Apple-style-span" style="font-size: 12px;">Direction Technique</span></font></font></div><div><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px;">email: <a href="mailto:david.ponzone@ipeva.fr" target="_blank">david.ponzone@ipeva.fr</a></span></font></font></div><div><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px;">tel: 01 74 03 18 97</span></font></font></div><div><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px;">gsm: 06 66 98 76 34</span></font></font></div><div><font class="Apple-style-span" face="'Helvetica Neue'"><br></font></div><div><font class="Apple-style-span" color="#1c00ff" face="'Helvetica Neue'">Service Client<span class="Apple-converted-space"> </span></font><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" color="#ff0000">IP</font></font><font class="Apple-style-span" color="#1c00ff" face="'Helvetica Neue'">eva</font></div><div><font class="Apple-style-span" color="#1c00ff" face="'Helvetica Neue'"><span class="Apple-style-span" style="color: rgb(0, 0, 0); font-family: Helvetica;"><div><font class="Apple-style-span" face="'Helvetica Neue'"><font class="Apple-style-span" size="3"><span class="Apple-style-span" style="font-size: 13px;">tel: 0811 46 26 26</span></font></font></div><div><font class="Apple-style-span" face="'Helvetica Neue'" size="3"><span class="Apple-style-span" style="font-size: 13px;"><div style="margin: 0px; font: 10px Arial; color: rgb(0, 34, 243);"><span style="text-decoration: underline;"><a href="about:blank" target="_blank">www.ipeva.fr</a></span><span style="color: rgb(101, 104, 149);"> - <span style="color: rgb(0, 34, 243); text-decoration: underline;"><a href="about:blank" target="_blank">www.ipeva-studio.com</a></span></span></div><div style="margin: 0px; font: 10px Arial; color: rgb(0, 34, 243);"><span class="Apple-style-span" style="text-decoration: underline;"><br></span></div><div style="margin: 0px; font: 10px Arial; color: rgb(0, 34, 243);"><span class="Apple-style-span"><div style="margin: 0px; text-align: justify; font: 10px Arial; color: rgb(192, 192, 192);"><i>Ce message et toutes les pièces jointes sont confidentiels et établis à l'intention exclusive de ses destinataires. Toute utilisation ou diffusion non autorisée est interdite. Tout message électronique est susceptible d'altération. </i><b><i>IPeva</i></b><i> décline toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. Si vous n'êtes pas destinataire de ce message, merci de le détruire immédiatement et d'avertir l'expéditeur.</i></div><div style="text-decoration: underline; text-align: justify;"><font class="Apple-style-span" color="#c0c0c0"><i><br></i></font></div></span></div></span></font></div></span></font></div></div></span><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"> </div><br><div><div>Le 29/08/2010 à 09:01, Dave Redmore a écrit :</div><br class="Apple-interchange-newline"><blockquote><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; font-size: medium;"><div><div style="font-family: 'Times New Roman'; font-size: 12pt; color: rgb(0, 0, 0);">Hello All,<br><br>I ran into an issue today that has burned up most of my day troubleshooting. I have resolved the problem, but would really like to understand what caused it, or some of the internal Freeswitch plumbing that is at play so that I can learn something from all of this time I have invested.<br><br>I have a Freeswitch server running that acts as a proxy to an account with an ITSP for doing T38 faxing. The Freeswitch server has a public IP address - there are four "users" who register simple FXS ATAs to my server and it then proxies to the ITSP using the "proxy_media" functionality. It has been working very well for the last 6 months or so. I have never had to deal with any NAT traversal issues - I just point the ATA to the IP to register and everything is great.<br><br>Here is what the four users "looked" like -<span class="Apple-converted-space"> </span><br><br>User1 : Grandstream HT-287 -> DD-WRT Router (NAT) -> Internet -> Freeswitch Proxy<br>User2 : Grandstream HT-503 -> DD-WRT Router (NAT) -> Internet -> Freeswitch Proxy<br>User3 : Grandstream HT-502 -> Comcast/SMC Router (NAT) -> Internet -> Freeswitch Proxy<br>User4 : Grandstream HT-287 -> IPCOP 1.4.11 (NAT) -> Comcast Gateway -> Freeswitch Proxy<br><br>(User4 is my office, so the IPCOP firewall and the Freeswitch Proxy sit on the same Comcast Gateway)<br><br>As I said, this all worked perfectly without any need to "fiddle" with anything on any firewalls - worked right out of the box.<br><br>So, today I changed out my IPCOP firewall for a pfsense firewall - and my HT-287 would no longer register.<br><br>After much head-scratching, packet captures, etc. I found that I needed to set up a Static Port NAT for the port the HT-287 was using (5062) in order to get this to work. <span class="Apple-converted-space"> </span><br><br>So, I see WHAT is happening, but I really want to know WHY it is happening.<br><br>Here are the gory details:<br><br>The sofia status of the profile looks like this - when the I have the Static Port NAT in place (details changed for security):<br><br>_______________________________________________________________<br>Call-ID: <span class="Apple-converted-space"> </span><a href="mailto:0e551b3c694a793c@192.168.1.137" target="_blank">0e551b3c694a793c@192.168.1.137</a><br>User: <span class="Apple-converted-space"> </span><a href="mailto:8885554525@173.11.22.111" target="_blank">8885554525@173.11.22.111</a><br>Contact: "user" <<a href="about:blank" target="_blank">sip:8885554525@192.168.1.137;fs_nat=yes;fs_path=sip%3A8885554525%40173.22.22.55%3A5060</a>><br>Agent: Grandstream HT287 1.1.0.45 DevId 000b821203c5<br>Status: Registered(UDP-NAT)(unknown) EXP(2010-08-29 01:17:03)<br>Host: 173-11-22-111-illinois.hfc.comcastbusiness.net<br>IP: 173.22.22.55<br>Port: 5060<br>Auth-User: 8885554525<br>Auth-Realm: 173.11.22.111<br>MWI-Account: <span class="Apple-converted-space"> </span><a href="mailto:8885554525@173.11.22.111" target="_blank">8885554525@173.11.22.111</a><br><br>Call-ID: <span class="Apple-converted-space"> </span><a href="mailto:1716488819-5062-1@192.168.7.150" target="_blank">1716488819-5062-1@192.168.7.150</a><br>User: <span class="Apple-converted-space"> </span><a href="mailto:8885554544@173.11.22.111" target="_blank">8885554544@173.11.22.111</a><br>Contact: "user" <<a href="about:blank" target="_blank">sip:8885554544@192.168.7.150:5062;user=phone;fs_nat=yes</a>; fs_path=sip%3A8885554544%4098.255.0.11%3A5062%3Buser%3Dphone><br>Agent: Grandstream HT-502 V1.1B 1.0.1.63<br>Status: Registered(UDP-NAT)(unknown) EXP(2010-08-29 01:48:35)<br>Host: 173-11-22-111-illinois.hfc.comcastbusiness.net<br>IP: 98.255.0.11<br>Port: 5062<br>Auth-User: 8885554544<br>Auth-Realm: 173.11.22.111<br>MWI-Account: <span class="Apple-converted-space"> </span><a href="mailto:8885554544@173.11.22.111" target="_blank">8885554544@173.11.22.111</a><br><br><span style="color: rgb(255, 0, 0);">Call-ID: <span class="Apple-converted-space"> </span><a href="mailto:090ee80e1a0ec9ed@10.8.11.149" target="_blank">090ee80e1a0ec9ed@10.8.11.149</a></span><br style="color: rgb(255, 0, 0);"><span style="color: rgb(255, 0, 0);">User: <span class="Apple-converted-space"> </span><a href="mailto:8885554549@173.11.22.111" target="_blank">8885554549@173.11.22.111</a></span><br style="color: rgb(255, 0, 0);"><span style="color: rgb(255, 0, 0);">Contact: "user" <<a href="about:blank" target="_blank">sip:8885554549@10.8.11.149:5062</a>></span><br style="color: rgb(255, 0, 0);"><span style="color: rgb(255, 0, 0);">Agent: Grandstream HT287 1.1.0.45 DevId 000b82127390</span><br style="color: rgb(255, 0, 0);"><span style="color: rgb(255, 0, 0);">Status: Registered(UDP)(unknown) EXP(2010-08-29 02:00:42)</span><br style="color: rgb(255, 0, 0);"><span style="color: rgb(255, 0, 0);">Host: 173-11-22-111-illinois.hfc.comcastbusiness.net</span><br style="color: rgb(255, 0, 0);"><span style="color: rgb(255, 0, 0);">IP: 173.11.22.99</span><br style="color: rgb(255, 0, 0);"><span style="color: rgb(255, 0, 0);">Port: 5062</span><br style="color: rgb(255, 0, 0);"><span style="color: rgb(255, 0, 0);">Auth-User: 8885554549</span><br style="color: rgb(255, 0, 0);"><span style="color: rgb(255, 0, 0);">Auth-Realm: 173.11.22.111</span><br style="color: rgb(255, 0, 0);"><span style="color: rgb(255, 0, 0);">MWI-Account: <span class="Apple-converted-space"> </span><a href="mailto:8885554549@173.11.22.111" target="_blank">8885554549@173.11.22.111</a></span><br><br>Call-ID: <span class="Apple-converted-space"> </span><a href="mailto:1035241259-5060-1@10.1.10.150" target="_blank">1035241259-5060-1@10.1.10.150</a><br>User: <span class="Apple-converted-space"> </span><a href="mailto:8885554547@173.11.22.111" target="_blank">8885554547@173.11.22.111</a><br>Contact: "user" <<a href="about:blank" target="_blank">sip:8885554547@10.1.10.150:5060;user=phone;fs_nat=yes;fs</a> _path=sip%3A8885554547%4098.222.55.100%3A5060%3Buser%3Dphone><br>Agent: Grandstream HT-503 V1.1B 1.0.1.63<br>Status: Registered(UDP-NAT)(unknown) EXP(2010-08-29 00:15:09)<br>Host: 173-11-22-111-illinois.hfc.comcastbusiness.net<br>IP: 98.222.55.100<br>Port: 5060<br>Auth-User: 8885554547<br>Auth-Realm: 173.11.22.111<br>MWI-Account: <span class="Apple-converted-space"> </span><a href="mailto:8885554547@173.11.22.111" target="_blank">8885554547@173.11.22.111</a><br>___________________________________________________________<br><br>The "User4" account is in red. The "Contact" field is substantially different and the "Status" indicates "Registered (UDP)", rather than "Registered (UDP-NAT)" as the others.<br><br>When I do a packet capture on the external NIC interface (eth0) - I see the following when the HT-287 tries to register and the Static Port NAT is NOT in place:<br><br>___________________________________________________________________<br>Internet Protocol, Src: 173.11.22.99 (173.11.22.99), Dst: 173.11.22.111 (173.11.22.111)<br>User Datagram Protocol, Src Port: 11521 (11521), Dst Port: 5090 (5090)<br>Session Initiation Protocol<br> Request-Line: REGISTER<span class="Apple-converted-space"> </span><a href="about:blank" target="_blank">sip:173.11.22.111:5090</a><span class="Apple-converted-space"> </span>SIP/2.0<br> Method: REGISTER<br> Request-URI:<span class="Apple-converted-space"> </span><a href="about:blank" target="_blank">sip:173.11.22.111:5090</a><br> Request-URI Host Part: 173.11.22.111<br> Request-URI Host Port: 5090<br> Message Header<br> Via: SIP/2.0/UDP 10.8.11.149:5062;branch=z9hG4bKda48f838c8689e41<br> Transport: UDP<br> Sent-by Address: 10.8.11.149<br> Sent-by port: 5062<br> Branch: z9hG4bKda48f838c8689e41<br> From: <<a href="about:blank" target="_blank">sip:8885554549@173.11.22.111:5090</a>>;tag=c8a0d452edc5ac4b<br> SIP from address:<span class="Apple-converted-space"> </span><a href="about:blank" target="_blank">sip:8885554549@173.11.22.111:5090</a><br> SIP tag: c8a0d452edc5ac4b<br> To: <<a href="about:blank" target="_blank">sip:8885554549@173.11.22.111:5090</a>><br> Contact: <<a href="about:blank" target="_blank">sip:88855564549@10.8.11.149:5062</a>><br> Contact Binding: <<a href="about:blank" target="_blank">sip:8885554549@10.8.11.149:5062</a>><br> Supported: replaces, timer<br> Call-ID:<span class="Apple-converted-space"> </span><a href="mailto:aa77d777bae71be6@10.8.11.149" target="_blank">aa77d777bae71be6@10.8.11.149</a><br> CSeq: 100 REGISTER<br> Sequence Number: 100<br> Method: REGISTER<br> Expires: 3600<br> User-Agent: Grandstream HT287 1.1.0.45 DevId 000b82127390<br> Max-Forwards: 70<br> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE<br> Content-Length: 0<br>_______________________________________________________________<br><br>When Freeswitch replies back with a "401 Unauthorized" - asking for further Auth - it replies back to port 5062 - so the packet never comes back (pfsense is looking for a packet back on port 11521 in this case). <span class="Apple-converted-space"> </span><br><br>If I put the Static Port NAT in place - all is well, because the "Source" port shows as "5062" - the rest of the packet looks pretty much the same.<br><br>Now, here is a packet coming from one of the other Users - this one comes through a DD-WRT router - here we see that the Source Port is 5060 :<br><br>_________________________________________________________________<br>Internet Protocol, Src: 173.22.22.55 (173.22.22.55), Dst: 173.11.22.111 (173.11.22.111)<br>User Datagram Protocol, Src Port: sip (5060), Dst Port: 5090 (5090)<br>Session Initiation Protocol<br> Request-Line: REGISTER<span class="Apple-converted-space"> </span><a href="about:blank" target="_blank">sip:173.11.22.111:5090</a><span class="Apple-converted-space"> </span>SIP/2.0<br> Method: REGISTER<br> Request-URI:<span class="Apple-converted-space"> </span><a href="about:blank" target="_blank">sip:173.11.22.111:5090</a><br> [Resent Packet: False]<br> Message Header<br> Via: SIP/2.0/UDP 192.168.1.137;branch=z9hG4bK665bc67a1c64292b<br> Transport: UDP<br> Sent-by Address: 192.168.1.137<br> Branch: z9hG4bK665bc67a1c64292b<br> From: "fax" <<a href="about:blank" target="_blank">sip:8885554525@173.11.22.111:5090</a>>;tag=8dc68b35111c4261<br> To: <<a href="about:blank" target="_blank">sip:8156564525@173.15.28.101:5090</a>><br> Contact: <<a href="about:blank" target="_blank">sip:8885554525@192.168.1.137</a>><br> Contact Binding: <<a href="about:blank" target="_blank">sip:8885554525@192.168.1.137</a>><br> Call-ID:<span class="Apple-converted-space"> </span><a href="mailto:0e551b3c694a793c@192.168.1.137" target="_blank">0e551b3c694a793c@192.168.1.137</a><br> CSeq: 503 REGISTER<br> Sequence Number: 503<br> Method: REGISTER<br> Expires: 3600<br> User-Agent: Grandstream HT287 1.1.0.45 DevId 000b821203c5<br> Max-Forwards: 70<br> Allow: INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE<br> Content-Length: 0<br>______________________________________________________________________<br><br>Here is one more packet coming from a Comcast/SMC Router - again, the source port is correct:<br><br>______________________________________________________________________<br> Internet Protocol, Src: 98.244.55.100 (98.244.55.100), Dst: 173.11.22.111 (173.11.22.111)<br>User Datagram Protocol, Src Port: sip (5060), Dst Port: 5090 (5090)<br>Session Initiation Protocol<br> Request-Line: REGISTER<span class="Apple-converted-space"> </span><a href="about:blank" target="_blank">sip:173.11.22.111:5090</a><span class="Apple-converted-space"> </span>SIP/2.0<br> Message Header<br> Via: SIP/2.0/UDP 10.1.10.150:5060;branch=z9hG4bK58981045;rport<br> Transport: UDP<br> Sent-by Address: 10.1.10.150<br> Sent-by port: 5060<br> Branch: z9hG4bK58981045<br> RPort: rport<br> From: <<a href="about:blank" target="_blank">sip:8885554547@173.11.22.111:5090;user=phone</a>>;tag=138706651<br> To: <<a href="about:blank" target="_blank">sip:8885554547@173.11.22.111:5090;user=phone</a>><br> Call-ID:<span class="Apple-converted-space"> </span><a href="mailto:1035241259-5060-1@10.1.10.150" target="_blank">1035241259-5060-1@10.1.10.150</a><br> CSeq: 79875 REGISTER<br> Sequence Number: 79875<br> Method: REGISTER<br> Contact: <<a href="about:blank" target="_blank">sip:8885554547@10.1.10.150:5060;user=phone</a>>;reg-id=1;+sip.instance="<<a href="about:blank" target="_blank">urn:uuid:00000000-0000-1000-8000-000B821F9A84</a>>"<br> Contact Binding: <<a href="about:blank" target="_blank">sip:8885554547@10.1.10.150:5060;user=phone</a>>;reg-id=1;+sip.instance="<<a href="about:blank" target="_blank">urn:uuid:00000000-0000-1000-8000-000B821F9A84</a>>"<br> Max-Forwards: 70<br> User-Agent: Grandstream HT-503 V1.1B 1.0.1.63<br> Supported: path<br> Expires: 300<br> Allow: INVITE, ACK, OPTIONS, CANCEL, BYE, SUBSCRIBE, NOTIFY, INFO, REFER, UPDATE<br> Content-Length: 0<br>___________________________________________________________<br><br>So, here are my questions:<br><br>- Why is the Sofia Status so much different for the registration coming through the pfSense firewall. It looks like it doesn't get tagged as being NAT'd and the "Contact" info is much less.<br><br>- Do most modern routers automatically Static Port NAT any SIP traffic? Both DD-WRT and SMC routers appear to be doing this - and not just on a simple Port bases (UDP 5060 only), because one of these examples is on 5062. Are these "SIP aware" firewalls that are doing this automatically, as the IPCOP did before?<br><br>- Is the extra "Contact" data in the last packet example different because it is a different UA (HT-503 rather than an HT-287)<br><br>- Is Freeswitch not flagging the registration from my office (User4) as being NAT'd because it is coming in on the same subnet as the interface Freeswitch received the packet on (Freeswitch is at 173.11.22.111 and pfsense is at 173.11.22.99)?<br><br>Sorry for this terribly long posting - I'm just very curious to understand what is going on here, now that I have collected all this information.<br><br>Thanks,<br><br>Dave<br><br> <br></div>_______________________________________________<br>FreeSWITCH-users mailing list<br><a href="mailto:FreeSWITCH-users@lists.freeswitch.org" target="_blank">FreeSWITCH-users@lists.freeswitch.org</a><br><a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br><a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br></div></span></blockquote></div><br></div><br>_______________________________________________
FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org
</div></body></html>