< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate] Bug with Multiple Accept headers


So I found the issue. We had strict mimetype checking on and MasterProfile.cxx doesn't add application/sdp for BYE. But this brings up an interesting question...Should the stack be validating Accept for an inbound request on a message that has no body?

-Aron

Aron Rosenberg
Logitech Inc, (SightSpeed Group)

__________________

So adding just

m.header(h_Accepts).push_back(resip::Mime("application","sdp"));

to the onReadyToSend for InviteSession if its a BYE, causes the stack to issue a 406 when receiving it. Let me step debug inside resiprocate to figure out whats going on.


Aron Rosenberg
Sr. Director, Engineering
Phone: +1 (510) 713-5801
Logitech Inc, (SightSpeed Group)

Inactive hide details for Scott Godin ---05/20/2010 01:39:17 PM---The easiest way to decorate the BYE message is to use the onRScott Godin ---05/20/2010 01:39:17 PM---The easiest way to decorate the BYE message is to use the onReadyToSend InviteSession callback.

From: Scott Godin <sgodin@xxxxxxxxxxxxxxx>
To: aron_rosenberg@xxxxxxxxxxxx
Cc: resiprocate-devel <resiprocate-devel@xxxxxxxxxxxxxxxxxxxx>
Date: 05/20/2010 01:39 PM
Subject: Re: [reSIProcate] Bug with Multiple Accept headers
Sent by: slgodin@xxxxxxxxx





The easiest way to decorate the BYE message is to use the onReadyToSend InviteSession callback.

Scott

On Thu, May 20, 2010 at 3:42 PM, <aron_rosenberg@xxxxxxxxxxxx> wrote: