> Dear colleagues, > > I have a query regarding the determination of the values > in a branch parameter for REQUESTS. > From RFC3261, chapter 17.2.3 Matching Requests to Server Transactions: > The branch parameter in the topmost Via header field of the request > is examined. If it is present and begins with the magic cookie > "z9hG4bK", the request was generated by a client transaction > compliant to this specification. Therefore, the branch parameter > will be unique across all transactions sent by that client. The > request matches a transaction if: .... > > > How can a server distinguish the unique "transaction id" beginning with the magic >cookie > from the branch id or loop id (if the client performs loop detection). > > Assume the following example: > INVITE containing via: > Via: SIP/2.0/UDP sip.siemens.net:5060;branch=z9hG4bK94635769.1 > > where the transaction id is ment as 94635769.1 but might be interpreted as 94635769 >and branch id 1 for forked request. > > > Appreciating your help. > > Mit freundlichen Gr��en / with best regards / cordialement Andreas Wilhelm
SIEMENS Siemens AG MchH/Sc8 ICN WN CC NA D15, Geb.7201/613 Hofmannstra�e 51 D-81359 M�nchen, Germany Tel.: +49/89/722-35974 FAX: +49/89/722-13035974 E-Mail: mailto:[EMAIL PROTECTED] _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
