A forking proxy will cause you grief. Here's a little telephony example to clarify:
Let's say an INVITE for [EMAIL PROTECTED] is sent out. The proxy "someProxy" forks the INVITE to [EMAIL PROTECTED] and [EMAIL PROTECTED] Notice, both numbers that the user is reachable at are sent to same UA because they are both in the same area code. Your SIP UA will receive two similar but different INVITEs (each to different phone numbers). Both INVITEs will share the same CallID and CSeq header. You should treat these as independent call attempts (ring both phone numbers), and will eventually send final responses for both of these INVITEs. Each FRs will generate an ACKs retaliation, and each ACK will share the same CallID and CSeq header - breaking your existing implementation. Hope that helps a bit. Enjoy, Dave At 03:58 AM 3/26/02 +0530, Radhika wrote: >Hello All, > > I have a doubt regarding matching an INVITE with its corresponding ACK. In my >current application, I have done so using the CallId and CSeq header values and am >having no problems regarding the working of this aspect. > > However, in one of the mails on this list, I read that even From and Request-URI >headers need to be used to perform this match. > > Under what conditions will my check fail. I shall be grateful if any suggestions or >solutions are given. > >Thanks and Regards, >Radhika. > _______________________________________________ Sip-implementors mailing list [EMAIL PROTECTED] http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
