20 Mar
2010
20 Mar
'10
6:02 p.m.
2010/3/20 Ovidiu Sas <osas(a)voipembedded.com>om>:
It's one of the goals, yes. One of the current lacks of the Dialog
module is the forking support as just an unique dialog entry is
generated (not wnough for modules like mediaproxy).
The question
would be, is there somebody who prefers the spiral
multiple dialogs approach? why?
Does this new design takes in consideration the modules that are on
top of the existing dialog module? 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.
This is a good argument to come back to the multiple dialogs approach
in case of spiral. There is no problem in using it as with the current
proposal it involves no failures even in exotic cases.
In any case, I would prefer to keep the existing
dialog module as is
and any new work to be done in a new module.
Most probably it's a good idea as the required changes are enough to
make the transition complex.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>