5 Apr
2006
5 Apr
'06
10:35 a.m.
It might not be 100% reliable, but you can use t_replicate in your
openser and, after users are locally register, you can send the
REGISTER to your comercial SIP server.
By unreliability I mean that you can not assure 100% that data in
openser and your comercial server is identical...some REGISTER might
get lost...
Another option you can consider is to look at older threads about high
availability and load balancing. The idea is to have a load balancer
on front of your openser farms. Playing with Path header you can have
a few instances of openser acting as load balancers of your comercial
SIP server. I might be wrong but I think it's not yet finished (what's
not yet done is the NAT pinging....please correct me if I'm wrong).
Hope it helps
Samuel.
2006/4/4, Simon Morvan <garphy(a)gmail.com>om>:
I'm not a mediaproxy/rtpproxy expert but as far as
your users are still
registered with OpenSER it should work.
Can someone confirm that?
2006/4/4, Jeff Williams < jeffw(a)globaldial.com>gt;:
Simon Morvan wrote:
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
It seems that what you want is third party
registration. I'm pretty
sure you can tell OpenSER to register your users on your other SIP
server by diverting the 'REGISTER' request.
But does the mediaproxy/rtpproxy work if the REGISTER request is
diverted to a third party?
Jeff