[Freeswitch-users] FS not detecting public IP address change
Mark Campbell-Smith
mcampbellsmith at gmail.com
Tue Oct 26 22:13:31 PDT 2010
That gives me quite a bit....
Can there be the case that nat_map status has a different IP address to what
I would see in sofia status profile internal? And does sofia reregister if
there is detected a public IP address change?
Thanks
freeswitch at internal> nat_map reinit
[DEBUG] libs/esl/src/esl.c:1141 esl_send() SEND
api nat_map reinit
console_execute: true
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Content-Type] =
[api/response]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Content-Length]
= [130]
Nat Type: NAT-PMP, ExtIP: 210.xx.xxx.xx
port,proto,proto_num,sticky
5060,udp,0,0
5060,tcp,1,0
5080,udp,0,0
5080,tcp,1,0
4 total.
freeswitch at internal> [DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV
HEADER [Content-Type] = [log/data]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Content-Length]
= [68]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Log-Level] =
[6]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Text-Channel] =
[0]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Log-File] =
[switch_nat.c]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Log-Func] =
[switch_nat_init]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Log-Line] =
[410]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [User-Data] = []
[DEBUG] libs/esl/src/esl.c:1115 esl_recv_event() RECV MESSAGE
Event-Name: SOCKET_DATA
Content-Type: log/data
Content-Length: 68
Log-Level: 6
Text-Channel: 0
Log-File: switch_nat.c
Log-Func: switch_nat_init
Log-Line: 410
User-Data: _undef_
2010-10-27 16:10:07.003208 [INFO] switch_nat.c:410 Scanning for NAT
2010-10-27 16:10:07.003208 [INFO] switch_nat.c:410 Scanning for NAT
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Content-Type] =
[log/data]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Content-Length]
= [73]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Log-Level] =
[7]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Text-Channel] =
[0]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Log-File] =
[switch_nat.c]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Log-Func] =
[get_pmp_pubaddr]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Log-Line] =
[167]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [User-Data] = []
[DEBUG] libs/esl/src/esl.c:1115 esl_recv_event() RECV MESSAGE
Event-Name: SOCKET_DATA
Content-Type: log/data
Content-Length: 73
Log-Level: 7
Text-Channel: 0
Log-File: switch_nat.c
Log-Func: get_pmp_pubaddr
Log-Line: 167
User-Data: _undef_
2010-10-27 16:10:07.003208 [DEBUG] switch_nat.c:167 Checking for PMP 1/5
2010-10-27 16:10:07.003208 [DEBUG] switch_nat.c:167 Checking for PMP 1/5
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Content-Type] =
[log/data]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Content-Length]
= [98]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Log-Level] =
[6]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Text-Channel] =
[0]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Log-File] =
[switch_nat.c]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Log-Func] =
[switch_nat_init]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [Log-Line] =
[423]
[DEBUG] libs/esl/src/esl.c:989 esl_recv_event() RECV HEADER [User-Data] = []
[DEBUG] libs/esl/src/esl.c:1115 esl_recv_event() RECV MESSAGE
Event-Name: SOCKET_DATA
Content-Type: log/data
Content-Length: 98
Log-Level: 6
Text-Channel: 0
Log-File: switch_nat.c
Log-Func: switch_nat_init
Log-Line: 423
User-Data: _undef_
2010-10-27 16:10:07.013797 [INFO] switch_nat.c:423 NAT detected type: pmp,
ExtIP: '210.xx.xxx.xx'
2010-10-27 16:10:07.013797 [INFO] switch_nat.c:423 NAT detected type: pmp,
ExtIP: '210.xx.xxx.xx'
On Wed, Oct 27, 2010 at 4:01 PM, Rupa Schomaker <rupa at rupa.com> wrote:
> Then I have no idea why you aren't seeing upnp messages on the console.
> What do you see when you do a "nat_map reinit" ?
>
>
> On Tue, Oct 26, 2010 at 8:09 PM, Mark Campbell-Smith <
> mcampbellsmith at gmail.com> wrote:
>
>> I see debug from sofia.c, switch_core_state_machine, mod_sofia, diaplan
>> parsing, sofia_glue, switch_rtp, switch_ivr_play_say etc.
>>
>>
>>
>> On Wed, Oct 27, 2010 at 11:41 AM, Rupa Schomaker <rupa at rupa.com> wrote:
>>
>>> Do you see ANY debug messages on your console from any other FS module?
>>> fsctl loglevel 7 sets the base log level, but not necessarily the log level
>>> on your screen.
>>>
>>> /log 7
>>>
>>> sets the log level in fs_cli.
>>>
>>> Your screen should get VERY busy especially when processing a call.
>>>
>>> On Tue, Oct 26, 2010 at 4:21 PM, Mark Campbell-Smith <
>>> mcampbellsmith at gmail.com> wrote:
>>>
>>>> I have it set to debug in switch.conf.xml and enable fsctl loglevel 7 in
>>>> fs_cli....
>>>>
>>>> :~$ cat /usr/local/freeswitch/conf/autoload_configs/switch.conf.xml |
>>>> egrep "param.*loglevel"
>>>> <param name="loglevel" value="debug"/>
>>>>
>>>> With regards to sofia: how does it determine if the external IP has
>>>> changed? And when it does, does sofia initiate a reregister of all external
>>>> sip providers?
>>>>
>>>> Thanks!
>>>>
>>>> On Wed, Oct 27, 2010 at 3:14 AM, Mario G <mario_fs at mgtech.com> wrote:
>>>>
>>>>> What you said: "And nat_map status shows me which ports have been
>>>>> forwarded and the external ip address (which is sometimes wrong). I also
>>>>> see this in the router gui." is also happening to me on a Linksys/Cisco
>>>>> RV042 router. Can't keep FS working for more than 2-5 hours without doing a
>>>>> restart or nat_map reinit. I think the routers upnp has a problem with dual
>>>>> wans, I have one static and one dynamic DSL.
>>>>>
>>>>> On Oct 26, 2010, at 6:43 AM, Rupa Schomaker wrote:
>>>>>
>>>>> What do you have set for loglevel in switch.conf.xml? My guess is that
>>>>> you have it set to something other than debug. If that is set to (say)
>>>>> info, then info is as low as you can go. Setting the console log level to
>>>>> debug will not give you debug output.
>>>>>
>>>>> sofia is unaware of upnp so a keepalive packet should have no impact on
>>>>> it's operation. I'm not familiar enough with sofia to tell what triggers
>>>>> that event.
>>>>>
>>>>> On Tue, Oct 26, 2010 at 6:24 AM, Mark Campbell-Smith <
>>>>> mcampbellsmith at gmail.com> wrote:
>>>>>
>>>>>> OK.. tcpdump gave me this and I still do not see anything on FS
>>>>>> except for this line:
>>>>>>
>>>>>> 2010-10-26 22:02:51.235608 [DEBUG] sofia.c:957 nua_i_outbound: unknown
>>>>>> event 8: 102 NAT binding changed
>>>>>>
>>>>>> Hypertext Transfer Protocol
>>>>>> NOTIFY * HTTP/1.1\r\n
>>>>>> HOST:239.255.255.250:1900\r\n
>>>>>> Cache-Control:max-age=120\r\n
>>>>>> Location:http://192.168.1.1:1278/rootDesc.xml\r\n<http://192.168.1.1:1278/rootDesc.xml%5Cr%5Cn>
>>>>>> Server: Tomato UPnP/1.0 MiniUPnPd/1.4\r\n
>>>>>> NT:urn:schemas-upnp-org:service:WANIPConnection:1\r\n
>>>>>>
>>>>>> USN:uuid:882dbe81-c28a-4992-baf7-410c05f1caf4::urn:schemas-upnp-org:service:WANIPConnection:1\r\n
>>>>>> NTS:ssdp:alive\r\n
>>>>>> \r\n
>>>>>>
>>>>>> This looks the same as you posted before, so why do I get the unknown
>>>>>> event 8 (is this related)?
>>>>>>
>>>>>> Thanks!
>>>>>>
>>>>>> On Tue, Oct 26, 2010 at 3:32 PM, Mark Campbell-Smith <
>>>>>> mcampbellsmith at gmail.com> wrote:
>>>>>>
>>>>>>> :) that was the first thing I did, but I get nothing; no keep alive
>>>>>>> packets.
>>>>>>>
>>>>>>> in the logfile at startup I see:
>>>>>>>
>>>>>>> 2010-10-26 10:19:45.484258 [INFO] switch_nat.c:410 Scanning for NAT
>>>>>>> 2010-10-26 10:19:45.485991 [DEBUG] switch_nat.c:167 Checking for PMP
>>>>>>> 1/5
>>>>>>> 2010-10-26 10:19:45.488575 [INFO] switch_nat.c:423 NAT detected type:
>>>>>>> pmp, ExtIP: '203.xxx.xxx.xxx'
>>>>>>> 2010-10-26 10:19:45.490683 [DEBUG] switch_nat.c:256 NAT thread
>>>>>>> configured
>>>>>>> 2010-10-26 10:19:45.492180 [DEBUG] switch_nat.c:267 NAT thread
>>>>>>> started
>>>>>>>
>>>>>>> And nat_map status shows me which ports have been forwarded and the
>>>>>>> external ip address (which is sometimes wrong). I also see this in the
>>>>>>> router gui.
>>>>>>>
>>>>>>> But I never see the keep alive packets.
>>>>>>>
>>>>>>> On Tue, Oct 26, 2010 at 3:13 PM, Rupa Schomaker <rupa at rupa.com>wrote:
>>>>>>>
>>>>>>>> Just turn up console logging to level 7.
>>>>>>>>
>>>>>>>> /log 7 if using fs_cli
>>>>>>>>
>>>>>>>>
>>>>>>>> On Mon, Oct 25, 2010 at 6:53 PM, Mark Campbell-Smith <
>>>>>>>> mcampbellsmith at gmail.com> wrote:
>>>>>>>>
>>>>>>>>> Hi!
>>>>>>>>>
>>>>>>>>> How do I enable debugging to get the UPnP keep alive packets?
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>>
>>>>>>>>> On Tue, Oct 26, 2010 at 1:15 AM, Rupa Schomaker <rupa at rupa.com>wrote:
>>>>>>>>>
>>>>>>>>>> I need the debug logging from the upnp stuff. It should look
>>>>>>>>>> something like:
>>>>>>>>>>
>>>>>>>>>> +OK log level 7 [7]
>>>>>>>>>> freeswitch at internal> 2010-10-25 09:13:59.926861 [DEBUG]
>>>>>>>>>> switch_nat.c:299 got UPnP keep alive packet:
>>>>>>>>>> NOTIFY * HTTP/1.1
>>>>>>>>>> HOST:239.255.255.250:1900
>>>>>>>>>> Cache-Control:max-age=60
>>>>>>>>>> Location:http://192.168.1.1:5000/rootDesc.xml
>>>>>>>>>> Server: Tomato UPnP/1.0 MiniUPnPd/1.4
>>>>>>>>>> NT:urn:schemas-upnp-org:service:WANIPConnection:1
>>>>>>>>>>
>>>>>>>>>> USN:uuid:00000000-0000-0000-0000-000000000000::urn:schemas-upnp-org:service:WANIPConnection:1
>>>>>>>>>> NTS:ssdp:alive
>>>>>>>>>>
>>>>>>>>>> I also run tomato and haven't had trouble with the upnp support so
>>>>>>>>>> at least we have that part working.
>>>>>>>>>>
>>>>>>>>>> You should see the above keepalive appear periodically every 30s
>>>>>>>>>> or so. You should see another set of messages when you terminate the DSL
>>>>>>>>>> connection and when that dsl connection comes back online.
>>>>>>>>>>
>>>>>>>>>> On Sat, Oct 23, 2010 at 5:36 PM, Mark Campbell-Smith <
>>>>>>>>>> mcampbellsmith at gmail.com> wrote:
>>>>>>>>>>
>>>>>>>>>>> Hi!
>>>>>>>>>>>
>>>>>>>>>>> The router is a ASUS router but it is running the tomato firmware
>>>>>>>>>>> which runs miniupnd.
>>>>>>>>>>>
>>>>>>>>>>> In the debug I see the message: 2010-10-24 08:02:59.178918
>>>>>>>>>>> [DEBUG] sofia.c:956 nua_i_outbound: unknown event 8: 101 NAT detected
>>>>>>>>>>>
>>>>>>>>>>> This is what I see below. I hope I enabled all debug messages. I
>>>>>>>>>>> thought I saw some xml type messages earlier, but not sure how I enabled
>>>>>>>>>>> them.
>>>>>>>>>>>
>>>>>>>>>>> nta_outgoing: RTT is 67.958 ms
>>>>>>>>>>> outbound(0xb6e07c00): NAT binding changed: [210.xx.xxx.xx]:5080
>>>>>>>>>>> != [58.xxx.xx.xx]:5080
>>>>>>>>>>> nua(0xb6e07c00): event i_outbound 102 NAT binding changed
>>>>>>>>>>> nua: nua_application_event: entering
>>>>>>>>>>> 2010-10-24 09:05:08.849525 [DEBUG] sofia.c:956 nua_i_outbound:
>>>>>>>>>>> unknown event 8: 102 NAT binding changed
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> On Sun, Oct 24, 2010 at 1:08 AM, Rupa Schomaker <rupa at rupa.com>wrote:
>>>>>>>>>>>
>>>>>>>>>>>> btw: what router are you using?
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Sat, Oct 23, 2010 at 9:06 AM, Rupa Schomaker <rupa at rupa.com>wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>> In a upnp config, FS is depending on the router to notify it of
>>>>>>>>>>>>> the ip address change. It is possible the upnp message(s) aren't formatted
>>>>>>>>>>>>> as expected. If you turn on debug logging you'll get the upnp messages on
>>>>>>>>>>>>> the console. If you can pastebin the capture of those while dropping and
>>>>>>>>>>>>> restarting the dsl connection I can maybe see if there is something obvious
>>>>>>>>>>>>> going on. The debug should also have messages related to the processing of
>>>>>>>>>>>>> those upnp messages.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Sat, Oct 23, 2010 at 7:04 AM, Mark Campbell-Smith <
>>>>>>>>>>>>> mcampbellsmith at gmail.com> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>> HI!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I know this question must have been answered 100's of
>>>>>>>>>>>>>> times....
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> My adsl is a bit dodgy at the moment and tends to go up and
>>>>>>>>>>>>>> down; which means I get assigned a new ip address from my ISP. FS is nat'd
>>>>>>>>>>>>>> behind a upnp capable router.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> The problem is that FS does not seem to be detecting the
>>>>>>>>>>>>>> change. For both the internal and external profile, I have auto-nat setup,
>>>>>>>>>>>>>> and I have tried stun and host settings in vars.conf. When I issue
>>>>>>>>>>>>>> a nat_map status I see my old IP address, and if I then issue a nat_map
>>>>>>>>>>>>>> reinit, I see the new public IP address. How can I get this to be
>>>>>>>>>>>>>> automatic?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Also the public IP address shown in the nat_map status is not
>>>>>>>>>>>>>> the same as shown in the sofia profile internal/external printouts. Why is
>>>>>>>>>>>>>> this?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> I'm sure this is configuration, just not sure what to change.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks!
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>>>> FreeSWITCH-users mailing list
>>>>>>>>>>>>>> FreeSWITCH-users at lists.freeswitch.org
>>>>>>>>>>>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>>>>>>>>>>>> UNSUBSCRIBE:
>>>>>>>>>>>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>>>>>>>>>>>>> http://www.freeswitch.org
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> -Rupa
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> -Rupa
>>>>>>>>>>>>
>>>>>>>>>>>> _______________________________________________
>>>>>>>>>>>> FreeSWITCH-users mailing list
>>>>>>>>>>>> FreeSWITCH-users at lists.freeswitch.org
>>>>>>>>>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>>>>>>>>>> UNSUBSCRIBE:
>>>>>>>>>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>>>>>>>>>>> http://www.freeswitch.org
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>> _______________________________________________
>>>>>>>>>>> FreeSWITCH-users mailing list
>>>>>>>>>>> FreeSWITCH-users at lists.freeswitch.org
>>>>>>>>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>>>>>>>>> UNSUBSCRIBE:
>>>>>>>>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>>>>>>>>>> http://www.freeswitch.org
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> -Rupa
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> FreeSWITCH-users mailing list
>>>>>>>>>> FreeSWITCH-users at lists.freeswitch.org
>>>>>>>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>>>>>>>> UNSUBSCRIBE:
>>>>>>>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>>>>>>>>> http://www.freeswitch.org
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> FreeSWITCH-users mailing list
>>>>>>>>> FreeSWITCH-users at lists.freeswitch.org
>>>>>>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>>>>>>> UNSUBSCRIBE:
>>>>>>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>>>>>>>> http://www.freeswitch.org
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> -Rupa
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> FreeSWITCH-users mailing list
>>>>>>>> FreeSWITCH-users at lists.freeswitch.org
>>>>>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>>>>>> UNSUBSCRIBE:
>>>>>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>>>>>>> http://www.freeswitch.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> FreeSWITCH-users mailing list
>>>>>> FreeSWITCH-users at lists.freeswitch.org
>>>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>>>> UNSUBSCRIBE:
>>>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>>>>> http://www.freeswitch.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> -Rupa
>>>>> _______________________________________________
>>>>> FreeSWITCH-users mailing list
>>>>> FreeSWITCH-users at lists.freeswitch.org
>>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>>> UNSUBSCRIBE:
>>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>>>> http://www.freeswitch.org
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> FreeSWITCH-users mailing list
>>>>> FreeSWITCH-users at lists.freeswitch.org
>>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>>> UNSUBSCRIBE:
>>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>>>> http://www.freeswitch.org
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> FreeSWITCH-users mailing list
>>>> FreeSWITCH-users at lists.freeswitch.org
>>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>>> UNSUBSCRIBE:
>>>> http://lists.freeswitch.org/mailman/options/freeswitch-users
>>>> http://www.freeswitch.org
>>>>
>>>>
>>>
>>>
>>> --
>>> -Rupa
>>>
>>> _______________________________________________
>>> FreeSWITCH-users mailing list
>>> FreeSWITCH-users at lists.freeswitch.org
>>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>>> http://www.freeswitch.org
>>>
>>>
>>
>> _______________________________________________
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>>
>>
>
>
> --
> -Rupa
>
> _______________________________________________
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20101027/2ab6e285/attachment-0001.html
More information about the FreeSWITCH-users
mailing list