Hi, many thanks, we'll give that a try
--- On Tue, 6/12/11, Vlad Paiu <[email protected]> wrote: > From: Vlad Paiu <[email protected]> > Subject: Re: [OpenSIPS-Users] REGISTER destination issue > To: [email protected] > Date: Tuesday, 6 December, 2011, 15:29 > Hi, > > Just a suggestion, you could use caching. > > When you receive a 401 response, you could save in > localcache, for the > key register_$tu the value $si, with a short expiry. > When you receive a new Register request, check whether you > have > register_$tu in cache. If you do, then route the Register > to that value, > the old $si. > > Regards, > > Vlad Paiu > OpenSIPS Developer > > > On 12/06/2011 04:33 PM, Nauman Sulaiman wrote: > > Hi > > > > We are using Opensips as proxy, when Opensips sends a > REGISTER message it resolves the domain of the RURI however > if the registrar has a bank of servers this could result in > the 2nd REGISTER message(with auth details) being sent to a > different server. Some registrars don't seem to keep auth > state across servers. The simple solution is to send the 2nd > REGISTER to the same address as the first. I thought of > storing the si variable from the 401 response and just send > the 2nd register to this ip address. > > > > But i can't use avps to store nor the Dialog state > stuff. Can anyone say what is the best way to fix this. > > > > Thanks > > > > _______________________________________________ > > Users mailing list > > [email protected] > > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
