Since registration just creates a transaction  ( unlike INVITE or
SUBSCRIBE which will create dialog/session etc ) which is destroyed
after receiving a final response and expiry of associated transaction
timers to handle duplicate REGISTERs.

Keeping the call-id is the way to differentiate the new registration
with the registration re-fresh ( if the call-id is same and the branch
id is different then it is a registration re-fresh). That is what I
think is one of the reasons for keeping the call-id same.

Regards,

Indresh 

>>-----Original Message-----
>>From: [EMAIL PROTECTED] 
>>[mailto:[EMAIL PROTECTED] On Behalf 
>>Of ext sumanth achar
>>Sent: Monday, June 04, 2007 1:34 PM
>>To: [email protected]
>>Subject: [Sip-implementors] call-id in register
>>
>>Hi,
>>     i want to know why call-id has to be same for all the register
>>message from a particular UAC.
>>
>>Thanks,
>>Sumanth
>>_______________________________________________
>>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

Reply via email to