VoIP Mailing List Archives

[jason at jasonjgw.net]

this is an issue which I've been discussing with Brian West on IRC and in
e-mail correspondence, which I thought I should bring to the list so that
others can look at it as well.

The configuration

My external SIP profile has its ext-sip-ip and ext-rtp-ip set to
stun:stun.freeswitch.org. This is necessary for nat traversal.

I have an internal-ipv6 profile as well, which is working, but for some reason
it's interfering with calls on the external profile (which of course is an
IPv4 profile).

The symptom is the following line in outgoing SIP messages while attempting to
establish a call to a gateway via the external profile:

o=FreeSWITCH 1245193059 1245193060 IN IP6 stun:stun.freeswitch.org

in response to which, the other side returns a 488 (invalid session
description).

I can confirm that ext-sip-ip and ext-rtp-ip are *not* set in the
internal-ipv6.xml profile, but they are said as explained above in the
external profile, where the problem lies.

This looks like a bug to me but I want to rule out misconfiguration first.

This has been tested on revision 13806.



_______________________________________________
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

[jason at jasonjgw.net]

Jason White <jason@jasonjgw.net> wrote:

[jim at evolutiontel.net]

IMHO, as FS is a B2BUA the new leg should state ownership in the SDP. Add to this the fact the IPV6 is blindly copied from leg 1 and the IP address was not decoded correctly there does appear to be a defficiency in the code.


- original message -
Subject: [Freeswitch-users] SIP and nat traversal IPv4/IPv6 issue
From: Jason White <jason@jasonjgw.net>
Date: 17/06/2009 07:01

this is an issue which I've been discussing with Brian West on IRC and in
e-mail correspondence, which I thought I should bring to the list so that
others can look at it as well.

The configuration

My external SIP profile has its ext-sip-ip and ext-rtp-ip set to
stun:stun.freeswitch.org. This is necessary for nat traversal.

I have an internal-ipv6 profile as well, which is working, but for some reason
it's interfering with calls on the external profile (which of course is an
IPv4 profile).

The symptom is the following line in outgoing SIP messages while attempting to
establish a call to a gateway via the external profile:

o=FreeSWITCH 1245193059 1245193060 IN IP6 stun:stun.freeswitch.org

in response to which, the other side returns a 488 (invalid session
description).

I can confirm that ext-sip-ip and ext-rtp-ip are *not* set in the
internal-ipv6.xml profile, but they are said as explained above in the
external profile, where the problem lies.

This looks like a bug to me but I want to rule out misconfiguration first.

This has been tested on revision 13806.



_______________________________________________
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


_______________________________________________
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

[brian at freeswitch.org]

Right which is what you have to do... I haven't been able to reproduce
the issue... which is odd.

/b

On Jun 17, 2009, at 2:36 AM, Jason White wrote:

[brian at freeswitch.org]

On Jun 17, 2009, at 8:14 AM, Jim Burke wrote:

[anthony.minessale at g...]

can you confirm that they are not being inherited by some of the helper variables exported from vars.xml?
can you minimalise your ip4 profile by cutting all the commented lines and actually remove the ext-rtp-ip and ext-sip-ip params?
Then possibly post your config for each profile.


On Wed, Jun 17, 2009 at 2:00 AM, Jason White <jason@jasonjgw.net (jason@jasonjgw.net)> wrote:

[raul at etellicom.com]

I can confirm the same issue, but it happens even with all the IPv6 stuff removed. This is my sofia status: freeswitch@internal> sofia status Name Type Data State ================================================================================================= internal profile sip:mod_sofia@10.0.13.10:5060 RUNNING (0) imxtony.sytes.net alias internal ALIASED external profile sip:mod_sofia@10.0.13.10:5080 RUNNING (0) example.com gateway 1.0.trunk-@SWITCH_VERSION_REVISION ([email]1.0.trunk-@SWITCH_VERSION_REVISION[/email])@ Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO Supported: timer, precondition, path, replaces Allow-Events: talk, refer Proxy-Authorization: Digest username="6499744074", realm="italk.co.nz", nonce="75444262", algorithm=MD5, uri="sip:6499744074@akl.italk.co.nz", response="89bb5673f48252622025641153b882de" Content-Type: application/sdp Content-Disposition: session Content-Length: 315 Remote-Party-ID: "FreeSWITCH" <jason@jasonjgw.net (jason@jasonjgw.net)> wrote: > The symptom is the following line in outgoing SIP messages while attempting to > establish a call to a gateway via the external profile: > > o=FreeSWITCH 1245193059 1245193060 IN IP6 stun:stun.freeswitch.org However, if I place an IPv6 call via the internal-ipv6 profile, the o= line contains the correct IPv6 address - so this is only adversely affecting the IPv4 external profile, it seems. _______________________________________________ Freeswitch-users mailing list Freeswitch-users@lists.freeswitch.org (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

[jason at jasonjgw.net]

Raul Fragoso <raul@etellicom.com> wrote:

[brian at freeswitch.org]

I need in one of your boxs... there is no way this is doing this
unless you are putting stun:stun.freeswitch.org into the ext-rtp-ip or
sip ip... which could make it trigger the ipv6 check since its just
looking for : in the ip address. And stun: has that.. so you're
triggering it... tar up your entire conf folder and mail it to me ASAP.

/b

On Jun 17, 2009, at 8:01 PM, Jason White wrote:

[brian at freeswitch.org]

Ok you both didn't notice you CAN NOT put stun:stun.freeswitch.org in rtp-ip, thats the problem. It clearly says IP ADDRESSES ONLY in the comments. DO not use $${external_rtp_ip} for rtp-ip either

/b

On Jun 17, 2009, at 3:10 PM, Raul Fragoso wrote:

[brian at freeswitch.org]

I no longer need your configs... I didn't try to put
stun:stun.freeswitch.org in sip-ip or rtp-ip because I know you
shouldn't. We clearly can not try to do a stun request in either of
these fields because you can't bind to IP's that aren't directly on
the machine... so do as per the config and put ONLY ip's that are
local on the machine... if you need to set the external rtp or sip ip
please set them with the ext-rtp-ip and ext-sip-ip params on the
profile. You CAN set the ext-rtp-ip and ext-sip-ip to
stun:stun.freeswitch.org and those will resolve.

/b

On Jun 17, 2009, at 3:10 PM, Raul Fragoso wrote: