If it maintains same Call-Id and tags, then yes the new binding will take effect. But will call-id be same if phone is moved from one location to another and is power cycled in the process
Sanjay >-----Original Message----- >From: Sarkar, Uttam [mailto:[EMAIL PROTECTED] >Sent: Tuesday, November 07, 2006 2:19 PM >To: Sanjay Sinha (sanjsinh); Prasad, Santosh; >[email protected] >Subject: RE: [Sip-implementors] Adding Bindings rfc3261 sec10.2.1 > >How about if somebody moves a SIP phone from one location to >the other and connected to the network. >SIP Phone is going to send new REGISTER message with new contact. >Is not the new binding should replace the old binding if the >REGISTER message contains the same old call id? > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of >Sanjay Sinha (sanjsinh) >Sent: Tuesday, November 07, 2006 1:39 PM >To: Prasad, Santosh; [email protected] >Subject: Re: [Sip-implementors] Adding Bindings rfc3261 sec10.2.1 > >I think registrar should create a separate binding when user >register with a different ip address/port combination. > >>-----Original Message----- >>From: [EMAIL PROTECTED] >>[mailto:[EMAIL PROTECTED] On Behalf >Of Prasad, >>Santosh >>Sent: Tuesday, November 07, 2006 12:12 PM >>To: [email protected] >>Subject: [Sip-implementors] Adding Bindings rfc3261 sec10.2.1 >> >>WRT RFC 3261 sec 10.2.1 Adding Bindings >> >> >> >>My question is should the SIP Registrar create two bindings in the >>database for Registration with same user-id but different IP Port >>combination (IP being in the same subnet or NAT )? >>This is not scenario for forking at multiple AOR. >> >> >> >>The following flow describes an issue whereby calls made to a >user that >>had been logged out from one Machine (IP:Port) as he/she >logged in from >>a different Machine (IP:Port) fails. >>Please see the steps below: >> >>Machine A and B are behind same NAT device >> >>Machine A points to Proxy 1 say EP01 >> >>Machine B points to Proxy 2 say EP02 >> >> >>At time t0 - User 'abc' logs into SIP server (EP01) from Machine 'A'. >> >>At time t1 - User 'abc' logs into SIP server (EP02 )from Machine 'B'. >>At time t2 - The Presence server realizes that this user 'abc' >>is logged in at another location, so the Presence server >indicates user >>'abc' on Machine 'A' to logout informing him that he is logged in at >>another location and the client also will log user out of SIP server. >> >>At time t3 - user 'def' tries to call user 'abc', the call request >>fails. >> >> >> >>This is what I see in DB >> >> >> >>At time t0 there is an entry [EMAIL PROTECTED]:PortA >> >>At time t1 the entry gets updated with [EMAIL PROTECTED]:PortB --> There >>should >>be two bindings as this is a new Registration from different IP:Port >>but (IP being in the same subnet)? >> >>At time t2 there is a request from Machine A to logout >>(De-Register) [EMAIL PROTECTED]:PortA but the SIP Registrar removes >[EMAIL PROTECTED]:PortB >> >>I see from the logs that the application doesn't create new >binding or >>entry in DB when the User 'abc' logs from Machine 'B' (at time t1) it >>overrides the old IP port. So at time instance t2 there is no >entry in >>the database >> >> >> >>But the client is logged in on Machine B and can originate >the call but >>cannot receive any calls. >> >> >> >> >> >>Thanks for your time. >> >> >> >>Regards, >> >>Santosh Prasad >> >> >> >>_______________________________________________ >>Sip-implementors mailing list >>[email protected] >>https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors >> > >_______________________________________________ >Sip-implementors mailing list >[email protected] >https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > >This email and any attached files herein contain information >that is intended only for the use of the individual or entity >to whom it is addressed and may contain information that is >legally privileged, confidential or otherwise exempt from >disclosure under applicable laws. If the reader of this >message is not the recipient, any disclosure, dissemination, >distribution, copying or other use or retention of this >communication or its substance is prohibited. > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
