2009/3/11 Scott Lawrence <[email protected]>: > They should repeat the resolution and selection when they refresh the > registration returned by sip2 (which is what most clients we've worked > with do). > > If you wanted to force clients to move back as quickly as possible, you > could arrange to have sip2 return shorter registrations than sip1 does. > There's danger in this, though, since it means sip2 will have higher > load than sip1 did (in a large system with short registration times, > registration load can be significantly higher than calls).
Ok, thanks a lot. > In our system, we make the priorities equal and synchronize the > registrations between registrars, so they provide both redundancy and > load sharing. It doesn't matter which registrar a client uses. In this case that is not feasible since the server is a PBX and all the SIP traffic must use the PBX in sip1 or the PBX in sip2. Regards. -- Iñaki Baz Castillo <[email protected]> _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
