[reSIProcate] InviteSession Offer/Answer Storing

[David Baker]

Hi Scott,

Ah, I believe that was my mistake - It will actually be in the 
On2xxAnswer state, but both On2xxAnswer and On2xxOffer fall into the 
same block of code, and I just read the last one.


Dave



On 25/09/2012 19:36, Scott Godin wrote:
> Hi David,
>
> Not sure how you are getting to the SentReinvite state and then
> receiving an On2xxOffer.
>
> I'm assuming the re-invite went out with no SDP (offer) in order for you
> to get to the On2xxOffer event.  However if that's the case, then you
> should be in the SentReinviteNoOffer state.  We should figure out why
> you are in the wrong state.  Are you using requestOffer to send a
> re-invite without SDP?
>
> Scott
>
> On Tue, Sep 25, 2012 at 2:15 PM, David Baker <david.baker at openmarket.com
> <mailto:david.baker at openmarket.com>> wrote:
>
>     Hi,
>
>     I've just been looking at and trying to understand how
>     InviteSession.cxx stores the OfferAnswer data that flows through it
>     (mCurrentLocalOfferAnswer / mCurrentRemoteOfferAnswer etc). In
>     particular, in dispatchSentReinvite in the On2xxOffer case, it calls
>     setCurrentLocalOfferAnswer(). If I understand correctly, should this
>     not be setting the remote OfferAnswer rather than the local, since
>     the OfferAnswer data is coming from the other party in this case?
>
>     The symptom of this (and my reason for looking) is that using
>     reinvites has caused getRemoteSdp to return SDP sent in the original
>     offer/answer exchange rather than the latest SDP in use that's been
>     updated by a reinvite.
>
>
>
>     David
>     _________________________________________________
>     resiprocate-devel mailing list
>     resiprocate-devel at resiprocate.__org
>     <mailto:resiprocate-devel at resiprocate.org>
>     https://list.resiprocate.org/__mailman/listinfo/resiprocate-__devel
>     <https://list.resiprocate.org/mailman/listinfo/resiprocate-devel>
>
>