Alfred E. Heggestad wrote:
Hi Lada
I found your document about optimizing RTP proxy really useful!
thanks a lot.
thanks :)
my comment is that storing preferences per user about
the network
topology is not very scalable.
Could you describe this in more details?
User can define the name of his realm and other described features at
his user preferences in Serweb.
It is on my todo list for next revision to describe the way of
configuring serweb where user will be able define those AVPs.
They are stored through attr_types table in SER DB.
Also the user preference is stored
per user account, and not per location. you might have one user
with two UAs, one behind NAT and the other on the public internet
This is a quite problem how to distinguish two SIP phones at different
network location.
I have focused on this before and couldn't find the way of separating 2
SIP phones with the same username.
If someone has a suggestion, it is more then welcomed and I will be
happy to include it in the document.
also can I ask that you update the sample ser.cfg to be more
aligned to the default ser.cfg from CVS, with the same named
routes etc? I found it very hard to "port" the RTPproxy ser.cfg
into the default ser.cfg ..
thanks!
This is also in the todo list and currently I'm updating the document.
Lada
/alfred
Ladislav Andel wrote:
I just add, try to look at
http://www.iptel.org/ser/howtos/optimizing_the_use_of_rtp_proxy
Feel free to give me any feedback about the document. It is based on
SER Ottendorf.
Lada
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(a)gmail.com> [070305 22:06]:
Hi
does anyone has a working example for this escenario?
thanks
rafael
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers