On Fri, 2007-02-23 at 22:07 +0200, erol turac wrote: > I mean that register packets sent to the registrar server at a > specific intervals after the sending first register. Its aim is to > reset session expire timer to make registration permanently. > > Of course, UAC sends these messages. my problem is actually about call > waiting feature of sip. > > There are 2 different SIP EPs whose register to registrar server using > same pin, password and URI but their IP address are different from > each other. > > They are sending reg messages to registrar at specific intervals. So > think that UAC1 registered with IP address A, and UAC2 registered with > ip adress B. > > When UAC1 sends an invite and starts a dialog with another UAC3, if > UAC2 wants to create a seperate dialog (say that UC2 is calling UAC4), > UAC2 sends a register message before sending its INVITE. > > Firstly, location service maps URI to A , but with the new register > message of UAC2, location service maps same URI to B. At this point, > UAC1 is talking with UAC3 and UAC2 is talking with UAC4 and everything > is ok. > > Here if UAC5 (any other UC) calls UAC1, loction service will lookup > the location of UAC1 and map it to B whereas UAC1 location is A. And > so, new invite will be routed to UAC2. > > What can be solution ? Preventing a register request with a different > IP if there is any binding in location service for same URI ? I could > not see any MUST in rfc 3261.
The two UAs are both using the same Address Of Record - if they use unique Call-Id values for the registrations (and keep that same value for the refreshes), then the location service should just create two mappings for that AOR and there is no confusion. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
