Re: [Stox] core issues

[Paul Kyzivat <[e-mail]>]

On 8/20/13 6:41 PM, Daniel-Constantin Mierla wrote:
>
> On 8/21/13 12:27 AM, Peter Saint-Andre wrote:
>> On 8/20/13 12:32 AM, Olle E. Johansson wrote:
>>> 19 aug 2013 kl. 20:02 skrev Peter Saint-Andre <[e-mail]>:
>>>
>>>> On 8/14/13 1:19 PM, [e-mail] wrote:
>>>>
>>>>> * Core
>>>>>
>>>>> - Issue: Should something general about forking be defined here
>>>>> or is it purely a -media issue?
>>>> I think this is best left for the stox-media spec.
>>> Do remember to handle the case where one sip INVITE can get multiple
>>> 200 OK. It's a corner case, but it does happen. And it's signalling.
>> That sounds like fun.
> This should be caught by the gateway, handled locally, like any SIP
> endpoint UA (and how is happening for PSTN gateways). Only one 200ok
> should be propagated to xmpp/jingle side. Which one? A matter of the
> implementation, most I have seen they go with the first response
> received, for the others they send ACK followed quickly by BYE (I mean,
> the good SIP UA implementations, some just crash in such cases :-) ).
> Daniel

You can make it sound easy by ignoring the details, but at the expense 
of quality of implementation.

The problem is that you may get multiple early dialogs, with media. At 
that time you don't know which one will answer first. So what do you do 
with the media while awaiting a 2xx?

You can't "pick one" without the risk that it is the wrong one.

You can "pick one" and switch it if it turns out to be the wrong one. 
But unless you relay the media the xmpp side will see a change, and so 
there must be some plan for how that is handled.

	Thanks,
	Paul