An outbound proxy should not have to rely on the main proxy. It is a
stand-alone proxy. There are typically 2 choices:
1. The outboundproxy (OBP) stores the NATed contact in it's own usrloc
table and forwards the modified request to the main proxy. The main just
"sees" the outbound proxy which forwards requests to the client.
2. The OBP is stateless (no DB needed) and forwards requests using the
Path: header introduced in CVS head. Then, the main proxy sees the NATed
client, but forwards the requests to the outbound proxy. RFC3327
But you do not need a dedicated outbound proxy for NAT traversal. Doing
the NAT traversal in the main proxy also works.
regards
klaus
Sam Lee wrote:
I tried the cacheless mode, it didn't work for me.
I'm just wondering , how did those people out there do their OUTBOUND
proxy ?
Can anyone give me some hint ?
Regards,
Sam
-----Original Message-----
From: Klaus Darilion [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 4:57 PM
To: Sam Lee
Cc: [email protected]
Subject: Re: [Users] 2 Openser Instances
Sam Lee wrote:
Hi Klaus,
Thanks for the quick reply. My purpose is one of the instance being a
normal Openser, the other with a FORCE RTPproxy. This is so that if
they have a symmetric NAT going on in their network, they can make use
of this rtpproxy as an outbound proxy but still able to call those
register with the normal openser.
Care to explain what is cacheless userloc mode ? How do I set it ?
http://openser.org/docs/modules/devel/usrloc.html#AEN252
it's mode 3 (only available in CVS head)
Because of the normal and force RTPproxy , these 2 instances has
different routing patterns, and they are handled differently.
I still would use only one proxy and apply NAT traversal only for
clients which use the "NAT traversal" port on your openser.
The idea is:
...
if ( dst_port = 6060) { # needs NAT traversal
if (is_method("REGISTER")) {
setflag(9);
# this is the natflag specified in userloc module #
http://openser.org/docs/modules/1.0.x/registrar.html#AEN103
fix_nated_register();
} else {
# do all the NAT traversal, activate RTP proxy
}
}
# now do the normal call and REGISTER handling
...
...
lookup("location");
if(isflagset(9)) {
...#force rtp proxy
}
....
regards
klaus
Any ideas ?
Regards,
Sam
-----Original Message-----
From: Klaus Darilion [mailto:[EMAIL PROTECTED]
Sent: Friday, May 26, 2006 4:28 PM
To: Sam Lee
Cc: [email protected]
Subject: Re: [Users] 2 Openser Instances
1. You can run several instances of openser on the same PC, but what
is your purpose?
2. If 2 openser proxies share the same userloc database, you have to
use the cacheless userloc mode
3. If you just want to listen on several ports, use a single proxy
with multiple listen directives
listen=udp:1.2.3.4:5060
listen=udp:1.2.3.4:6060
listen=udp:1.2.3.4:7060
regards
klaus
Sam Lee wrote:
Have anyone tried running 2 separate instances on OpenSER (running on
different ports) ?
Both these instances are doing almost exactly the same thing, they
take in REGISTER and save them into the locations database. They all
do all the other processing like INVITE.
Will this causes a problem in MYSQL ? I'm asking this because i got a
very strange problem. I register 1 UA to each instances. When i did a
ul show , it always only have either the UA from instance A or UA
from
instance B . Note, these 2 UA have different numbers. Why can't it
just save both into the MYSQL DB ?
I would be glad to clarify any doubts. Please assist as far as you
can.
Thanks!
Regards,
Sam
---------------------------------------------------------------------
-
--
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://openser.org/cgi-bin/mailman/listinfo/users
