VoIP Mailing List Archives

[kristjan.ugrin at gmai...]

I'm trying to change internal address to something else than default external, so I would be able to make calls from phone on wireless
to e.g. gtalk users. I already tried this scenario at different location and it work, but everything was on same lan, now I have
eth0 interface with external ip e.g. 212.235.180.41
eth1 interface with internal ip 192.168.0.1

on eth1 is wireless router attached with wireless clients (my phone is 192.168.0.102), messages are going trough, no problem with that.
If I got it right I have to change:
<param name="rtp-ip" value="$${local_ip_v4}"/>
<param name="sip-ip" value="$${local_ip_v4}"/>

to 192.168.0.1, after that I modified acl.conf.xml domains section to:
<list name="domains" default="deny">
<node type="allow" domain="$${domain}"/>
<node type="allow" domain="192.168.0.1"/>
</list>


but I'm getting forbidden:
2009-01-03 09:39:42 [WARNING] sofia_reg.c:1533 sofia_reg_parse_auth() Can't find user [1000@192.168.0.1]
You must define a domain called '192.168.0.1' in your directory and add a user with the id="1000" attribute
and you must configure your device to use the proper domain in it's authentication credentials.

What directory? Should I delete added node from acl.conf.xml?

--
kriko



_______________________________________________
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]

What is the output of "sofia status"?


And what have you changed from the default config ie in vars.xml?


/b



On Jan 3, 2009, at 2:43 AM, kriko wrote:

[kristjan.ugrin at gmai...]

This is sofia status:
http://pastebin.com/m2d6d4a80

When registering I get:
http://pastebin.com/m2381d6a5

I can also provide a wireshark trace, but I don't see anything unusual or network related-problem.
FS actually replies to the phone with 403 Forbidden

On Sat, 03 Jan 2009 17:07:35 +0100, Brian West <brian@freeswitch.org> wrote:

[brian at freeswitch.org]

You changed the ip and domain ?

Sent from my iPhone

On Jan 3, 2009, at 11:23 AM, kriko <kristjan.ugrin@gmail.com> wrote:

[kristjan.ugrin at gmai...]

I changed exactly what I wrote in previous mails.
Everything else is default.

Is there anything else to change?

On Sat, 03 Jan 2009 18:42:04 +0100, Brian West <brian@freeswitch.org> wrote:

[brian at freeswitch.org]

The detected domain is 212.235.180.41 which caused this problem.

You have two options here.

Since we detected and set your default domain to 212.235.180.41 on
start up... you're registering to the 192.168.0.1 ip aka the internal
interface.

The inbound register packet has:

From: <sip:1000@192.168.0.1>

We take the part before the @ aka the username, then we take the part
after the @ aka the domain name.

FreeSWITCH will then look thru your directory looking for domain which
in this case is 192.168.0.1
which it can't find because we detected your public IP and set it up
as 212.235.180.41.
So the error message is telling you that you do not have a domain
called 192.168.0.1 with a user 1000 in it.

So what you have to do here is understand that SIP like email works on
the concept of domains. user@host.

A few things you need to know are this:

(SOMEONE WIKIFY THIS PLEASE and expand on it. Find me on IRC if you
have questions)
<wiki>
sofia profile params:
challenge-realm:

<param name="challenge-realm" value="auto_from"/> (default
configuration uses auto_from)

Choose the realm challenge key. Default is auto_to if not set.

auto_from - uses the from field as the value for the sip realm.
auto_to - uses the to field as the value for the sip realm.
<anyvalue> - you can input any value to use for the sip realm.

force-register-domain:

<param name="force-register-domain" value="$${domain}"/>

This will force the profile to ignore the domain in the to or from
packet and force
it to the value listed here for this param.

This will store the info into the database with the user@<from domain
in sip packet>

force-register-db-domain:

<param name="force-register-db-domain" value="$${domain}"/>

This will work in conjunction with force-register-domain so that the
forced domain
is stored in the database also.

</wiki>

ATTENTION HERE IS WHAT YOU SHOULD DO:

So what I recommend for you is to open up internal.xml and uncomment
the force-register-domain
and force-register-db-domain params on the internal profile. Also
make sure internal.xml has
sip-ip and rtp-ip set to 192.168.0.1 and make sure your phones
register to 192.168.0.1.

/b

On Jan 3, 2009, at 11:46 AM, kriko wrote: