> I assume you are looking at this as a UAC > and not a proxy since this approach makes > no sense for a proxy at all. > > You'll be ok until the first time you have > to send a request to a second destination > while working through the algorithm in RFC3263. > At that point, you'll be broken.
Another issue is converting definition of a call-id (words and '@') into the reduced syntax of a via branch (token). Another potential issue is associated with the interpretation of the "globally unique" statement in rfc3261 section 8.1.1.7. If this only applies in relation to source address, there is no problem. Otherwise there will potentially be a problem if the other UA uses the same algorithm and starts with approximately the same cseq. > On Mon, 2003-09-15 at 09:31, Sudharsana Krishnan wrote: > > All > > > > I had a question related to creation of the branch > > parameter for outgoing requests. > > > > I want to use the CSeq number appended to the > > call-id in the sip request as > > the branch parameter. > > (after the magic cookie) > > > > Since Call-ID will be globally and spatially unique, > > what I am doing I think > > will ensure uniqueness for branch creations. > > > > Does somebody out there forsee an issue? _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
