[reSIProcate] reINVITEs

[Fischl jason]

In an early dialog, after calling provideAnswer you need to
subsequently call ServerInviteSession::provisional or
ServerInviteSession::accept to cause the message to go out. There are
some contexts where calling provideAnswer will immediately send out
signaling (where PRACK is involved)

On 8/10/05, Christian_Gavin at logitech.com <Christian_Gavin at logitech.com> wrote:
> Hi,
> 
> (Using DUM) When a reINVITE is received, and pSession->provideAnswer( ) is
> called, the call state transitions from receivedReinvite to connected, but
> there doesn't seem to be any callback fired (eg. OnConnected).
> 
> Is this the intended behavior ? If so, should the client restart streaming
> with new parameters (eg. different codec, different remote IP, etc.) right
> after calling provideAnswer( ) ?
> 
> Thanks!
> CG
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel at list.sipfoundry.org
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>