Jonathan Rosenberg ([EMAIL PROTECTED]):
>> 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.
The request forks to two seperate ports, each with a distinct URI, and
each may handle the call differently (one port may be busy, the other
may ring. Think SIP-POTS phone gateway not a PSTN gateway).
So, of course they are two seperate call legs. The request-URI first
determines which sub-UA handles the call, and that sub-UA terminates the
call to create the leg.
--
Billy Biggs, 3Com Email: [EMAIL PROTECTED]
http://www.div8.net/billy/ Phone: [EMAIL PROTECTED]
