> -----Original Message-----
> From: Barry Desborough [mailto:[EMAIL PROTECTED]]
> Sent: Friday, December 01, 2000 9:49 AM
> To: [EMAIL PROTECTED] (E-mail)
> Subject: Receiving forked INVITES to a multiple-endpoint application
>
>
>
> Hi
>
> I'm a multiport gateway. If I receive INVITES forked from a single
> originator and aimed towards more than one of my ports,
> should I expect the
> call-legs to be different? If they are not, should I inspect
> the RURI or any
> other data when trying to distinguish their call-legs?
So, the case you are describing is where some user A sends an INVITE, and it
forks, and both forked requests arrive at your gateway B, each with a
different request URI?
The call leg is created when you respond. Each response (assuming you accept
both for some odd reason) would have a different tag in the To field, thus
making each a different call leg. Normally, though, you would reject one of
them as a merged request, since the caller did indeed launch an INVITE to a
single URI.
-Jonathan R.
---
Jonathan D. Rosenberg 72 Eagle Rock Ave.
Chief Scientist First Floor
dynamicsoft East Hanover, NJ 07936
[EMAIL PROTECTED] FAX: (973) 952-5050
http://www.cs.columbia.edu/~jdrosen PHONE: (973) 952-5000
http://www.dynamicsoft.com
