VoIP Mailing List Archives

[brian at freeswitch.org]

This would be one thing to look at your DNS name isn't resolving
correctly.. you might consider using dynamic DNS and you can then set
the them to "host:myhost.dyndns.org"

/b

On Mar 16, 2009, at 12:55 PM, ludovic wrote:

[ludovic.fouquet at bew...]

Hi all,

Here is my setup :
------------------------------
local sipphone ------> |lan1 (router running FS) wan1|--->internet
------------------------------

local_ip_v4 is set to lan1 address

wan1 has a dynamic IP address.
On startup, when wan1 has an IP address, I add the entry in my /etc/host : xxx.xxx.xxx.xxx my_host

I would like to tell FS that the external profile has to be created on wan1 with :
<param name="rtp-ip" value="my_host"/>

It seems good, the external profile is created. But the registration of my SIP account failed.

The working conf for registration is to set rtp-ip and sip-ip to local_ip_v4, and to have ext-rtp-ip=$${external_rtp_ip} and sip-rtp-ip=$${external_sip_ip}
But in that case, it can't route outgoing calls (see attached file).

I don't konw how to fix it.

Thanks for your help.

Ludovic

[ludovic.fouquet at bew...]

Thanks.
It seems that it comes from my sip provider.
when using my_host as my hostname, reg fails
when using my_host.com as my hostname, reg succeeds (my_host.com does not exist as a domain internet)
when using ip address, reg succeeds.

Tested with version 1.0.3

Is it a way to force the IP address to be used in SIP header instead of hostname ?

Thanks

Ludovic

Brian West a écrit :

[brian at freeswitch.org]

What I provided you was an example. I don't think you understood what
I was talking about.

In the settings for ext-sip-ip and ext-rtp-ip you'll have to use
something like "host:yourdyndnshostname.blah.tld"

Then set the sip-ip and rtp-ip to what ever is auto detected.

/b


On Mar 17, 2009, at 6:22 AM, ludovic wrote:

[ludovic.fouquet at bew...]

I understood the example.
What I mean is that my DNS issue comes from sofia-sip and my sip provider (freephonie.net) name resolution which fails when calling whereas it is well resolved during the registration process.
Here is a trace :

[brian at freeswitch.org]

I checked, I don't see sw1.freephonie.net in the logs trying to
resolve it... and the SRV records are all correct as are the naptr
records which is shocking

/b

On Mar 17, 2009, at 1:16 PM, ludovic wrote:

[ludovic.fouquet at bew...]

Just to let you know.
My resolv issue comes from dnsmasq who filters request of SRV type and which name contains underscore. It is due to the option filterwin2k. But I have to let this option and find a way to force sofia to use DNS on external interface.

Regards,

Ludovic

Brian West a écrit :