[Freeswitch-users] Can't hear outbound calls

Lars Zeb larclap at yahoo.com
Tue Jun 9 14:26:00 PDT 2009


Rupa,

 

Thanks for the detailed response. After upgrading from 13639 to 13732, I see
no log errors. I am accessing Freeswitch vi fs_cli, but I did look in
log/freeswitch.log. Certainly I see nothing that looks like your ERR below.

 

I too have a dlink router. I will look at its configuration and see if upnp
is enabled.

 

Lars

 

From: freeswitch-users-bounces at lists.freeswitch.org
[mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Rupa
Schomaker
Sent: Tuesday, June 09, 2009 11:16 AM
To: freeswitch-users
Subject: Re: [Freeswitch-users] Can't hear outbound calls

 

If we get 0.0.0.0 as a public address, upnp support is disabled since we're
getting the info from a gateway that can't route us to the internet.  It is
broken, so we don't trust it.

The message you should see in the logs is something like:

2009-06-08 13:51:44.587812 [ERR] switch_nat.c:126 uPNP Device (url:
http://192.168.1.2:4444/wipconn) returned an invalid external address of
0.0.0.0.  Disabling uPNP
2009-06-08 13:51:44.587812 [INFO] switch_nat.c:380 No PMP or UPnP NAT
detected!

You'll probably not see this if you start fs in the background and then
connect with fs_cli.  So, look in your log files for it.

The url will give you an idea as to which device is sending you invalid
info.  In my case it is a dlink router setup as a access point but still was
implementing upnp (bad).  I was able to disable upnp on that router.

My printer (Epson Artisan 800) also participates in upnp, but it doesn't
respond to the internet gateway stuff, so it was not the source of a problem
for address discovery.  It is causing me other issues but that is another
story for another day for code that isn't committed yet.

2009/6/9 Lars Zeb <larclap at yahoo.com>

Thanks, Brian and Mike J and Ken R and Jason W.

 

Outbound calls are now working OK.

 

Brian, I don't know where to look for the 0.0.0.0 addr error message. I
checked the log/freeswitch.log but did not recognize anything.

 

I also noticed that nat_public_addr is not longer displayed in the
global_getvar command. How is this value set?

 

From: freeswitch-users-bounces at lists.freeswitch.org
[mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Brian
West
Sent: Tuesday, June 09, 2009 9:06 AM


To: freeswitch-users at lists.freeswitch.org
Subject: Re: [Freeswitch-users] Can't hear outbound calls

 

Because rupa on IRC is having the same problem.. Check the error message I
print now and the device url will be printed thanks to rupa's patch.

 

/b

 

On Jun 9, 2009, at 11:03 AM, Lars Zeb wrote:

 

Brian, I'm curious, how can you tell that a printer is giving out the
0.0.0.0 addr?

 

Brian West

brian at freeswitch.org

 

-- Meet us at ClueCon!  http://www.cluecon.com <http://www.cluecon.com/> 

 

 

 

 


_______________________________________________
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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20090609/81946ee9/attachment-0002.html 


More information about the FreeSWITCH-users mailing list