Re: [reSIProcate-users] a question about info() in InviteSession.cxx
I think, as long as we have an established dialog (ie. both to and
from tag, and remote contact), then we are probably good to allow info
requests to be sent. If we have an invite session then we have a
dialog - so it seems that we should be ok to just remove the
isConnected check. Can you please try this out? If everything
appears to working as expected, then I can get that change moved into
SVN.
If anyone believes this is in violation to an RFC, then please let me know.
Thanks,
Scott
2010/2/2 吴振宇 <ssosun@xxxxxxxxx>:
> sorry,something i said is vague.
> can we not test the "isConnected()".
> as another word,before connect state ,can we send a info message.
> some app maybe like RFC5168.
> and what trouble may be come sending info before connect state?
>
> 2010/2/3 Scott Godin <sgodin@xxxxxxxxxxxxxxx>:
>> ReceivedReinvite is included as one of the "connected" states (see the
>> implementation for isConnected) - so INFO messages will be allowed
>> during re-invite. I don't recall reading anywhere that this is
>> illegal - since Info transactions do not effect invite session state.
>>
>> Scott
>>
>> On Sun, Jan 31, 2010 at 11:44 PM, 吴振宇 <ssosun@xxxxxxxxx> wrote:
>>> hi,in the info() function,why it tests isConnected().
>>> sending info message will change the mNitState,but not mState.
>>> and there is "// ?slg? likely not safe in any state except Connected -
>>> what should behaviour be if state is ReceivedReinvite?"
>>> if the state isn't the ReceivedReinvite,safe?
>>> has some rfc describing this condition?
>>> thanks.
>>> _______________________________________________
>>> resiprocate-users mailing list
>>> resiprocate-users@xxxxxxxxxxxxxxx
>>> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>>>
>>
>