Hi Rakesh, Full trace of your scenario or at least the message body of the fresh REGISTER message sent from UE with new Call-ID may help figure out things.
Regards, Mohit Soni On Fri, Jan 6, 2017 at 4:02 PM, Rakesh <rak...@gmail.com> wrote: > Hi Expert, > > I need one info for the following below SIP REGISTER scenario. > > Step 1) UE sent REGISTER with CSeq =1 CallID=100001 > Step 2) 401 with CSeq =1 CallID=100001 > Step 3) After challenge UE sent the REGISTER with CSeq =2 CallID=100001 > Step 4 ) 200OK with same CSeq =2 CallID=100001 which is expected . > > Call Continue... Everything is OK > > Step 5) UE sent DE-REGISTRATION with CSeq =3 CallID=100001 > Step 6) 200OK for DE-REGISTRATION with same CSeq =3 CallID=100001 which is > expected . Here all contacts are removed (all AOR binding clear) > > Step 7) UE now sent another fresh REGISTER request with CSeq =1 > CallID=100002 > > Step 8) UAS is now rejecting continuously the REGISTER. > > So the question is in Step 7 ) the call id now changed to 100002 and as per > RFC 3261 it says > > The first question is, > > It says 8.1.1.4 Call-ID > > > The Call-ID header field acts as a unique identifier to group together > a series of messages. It MUST be the same for all requests > and responses sent by either UA in a dialogue. > *It SHOULD be the same in each registration from a UA.* > > *Best Regards* > > *Rakesh Kumar Mohanty* > _______________________________________________ > Sip-implementors mailing list > Sip-implementors@lists.cs.columbia.edu > https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list Sip-implementors@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
