Hi Juha,
thanks a lot for your investigations!
After looking a bit into the problem I would use another solution: get rid of
onEarlySessionStart and use onSessionStart only.
In my opinion the session (in the meaning of media session here!) starts when
SDPs are exchanged (doesn't matter if the answer comes in 183, 200, PRACK or ACK
or who-knows-where). The application always has the possibility to check the
dialog state itself (or handle the dialog state changes when it gets from early
to connected for example).
Anyway, my opinion here doesn't need to match anybody elses understanding of how
the things are expected to work or expected to be understood so I'm not going to
change this now.
Vaclav
On Po, pro 30, 2013 at 02:59:10 +0200, Juha Heinanen wrote:
> Juha Heinanen writes:
>
> > i debugged this problem a bit more. as i have mentioned earlier, if 183
> > with sdp precedes 200 ok with dsp, onSessionStart event is not called.
> >
> > i then searched where onSessionStart event is called and found only one
> > place (in AmSipDialog.cpp):
> >
> > int AmSipDialog::onSdpCompleted()
>
> thinking this further, why is onSessionStart call bound to
> onSdpCompleted? would it be better to bind it to receiving of 200 ok,
> which may or may not contain sdp?
>
> -- juha
> _______________________________________________
> Sems mailing list
> [email protected]
> http://lists.iptel.org/mailman/listinfo/sems
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
