Atle is right, the only (really) reliable way (from server side) is manual configuration based on knowledge of the network setup for a group of users :-)
The NAT optimization paper found as part of the What's New 2.0 on iptel.org shows how this can be accomplished through the use of a realm attribute per account.
g-)

Atle Samuelsen wrote:
Hi rafael,

I might be wrong.. but it's REALLY hard to know if a user is behind the
same nat.. due to that : 

on sip-proxy you see that user Alice and Bob come from the same IP, and
that they have the same "ip-range" in say contact. 

you say "Oh, we see he's behind the same nat.."
but..

you dont really know what other equitment the other user has behind
his nat. Say a user has 3 routers
router 1: 
192.168.1.1 on "inside"
193.212.1.10 on "outside"

router 2: is conected to inside of router 1: 
192.168.9.1 on "inside"
192.168.1.2 on "outside"

router 3: is concted to router 2's inside:
192.168.1.1 on "inside"
192.168.9.1 on "outside"

one phone is now connected to router 3, and one to router 1.

on router 3 the phone gets the "internal" ip: 192.168.1.2. 
on router 1 the phone gets the ip 192.168.1.3

the phone on router 1, can not send rtppackets to the phone on router
3.. and router 3, can not send to router 1.. evenwhilethey are "looking"
to be behind the same nat.

- Atle

ps: if anybody has a working solutio for this, exept ice/turn/stun
whatever it's now called.. fel free to update me :)

* Rafael J. Risco G.V. <rafael.risco@gmail.com> [070305 22:06]:
  
Hi
does anyone has a working example for this escenario?

thanks
rafael

_______________________________________________
Users mailing list
Users@openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
    
_______________________________________________
Serusers mailing list
Serusers@lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers