[sr-dev] Proposal: New Dialog Module Design

[Timo Reimann]

Ovidiu Sas wrote:
> On Sat, Mar 20, 2010 at 6:00 PM, Iñaki Baz Castillo <ibc at aliax.net> wrote:
>> 2010/3/20 Ovidiu Sas <osas at voipembedded.com>:
>>
>>> For instance the qos module is keeping track of the media endpoints
>>> for the dialog.
>>> As I pointed out in a previous e-mail, in a spiral case when P2 is
>>> proxying the media, the SDP for the first INVITE that is hitting P1
>>> will be different then the SDP for the second INVITE that is hitting
>>> P1 and in this case the single dialog approach will not work.
>>>
>>> UA1 --> P1 --> P2 --> P1 --> UA2
>>
>> Hi Ovidiu, let me a question:
>>
>> In your case, wouldn't be enought if the dialog is created after the
>> spiral occurs?
> How do you know that a spiral will occur?

Assuming a single-dialog approach, what about a new dialog callback type
that is executed when a spiral is detected, e.g., something like
DLGCB_SPIRALING? Couldn't mediaproxy and akin hook up to that in
addition and thereby continue to work just like they did before?


Cheers,

--Timo