samuel wrote:
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...
This could be possible. However, all of the authencation information in stored in our commercial server in a Sybase database. Seeing that openser doens't have a sybase module this makes things very tricky. Not to mention that I'm not sure how the commercial server crypts/decrypts passwords.
I was hoping that I could do it in reverse, i.e. only register users locally if they were able to register on the commercial server. But as far as I can see this would mean running save("location") in a onreply_route for a register request where status is 200. But save doesn't run in onreply_route's and I'm assuming there is a good reason for it.
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).
This may be the sort of thing I am trying to achieve. I will have a look for these threads. Thanks.
Jeff