Re: [reSIProcate-users] Parse headers in BYE response message

[RJJJM RJJJM <rjjkm@xxxxxxxxxxx>]

Hey Scott,

Thanks for the proposed workaround, I was able to prototype a solution using an incoming feature.  Perfect example in resip/dum/test/treg.cxx.

Yes an onByeConfirmed callback would be a better/simpler approach, mainly because it would have an InviteSessionHandle.  Hopefully this can make it to the enhancement roadmap at some point.

Thanks for the support,

Rex

---

Date: Wed, 27 May 2015 13:19:55 -0400
Subject: Re: [reSIProcate-users] Parse headers in BYE response message
From: sgodin@xxxxxxxxxxxxxxx
To: rjjkm@xxxxxxxxxxx
CC: resiprocate-users@xxxxxxxxxxxxxxx

There is no way to access the BYE response through the InviteSessionHandler.  Seems you could benefit from a onByeConfirmed callback - but that doesn't exist today.

To get acess without resip code modification.....  it's a little convoluted but you could try using an incoming feature.  These get access to all inbound messages.  See DialogUsageManager::addIncomingFeature and IdentityHandler as a sample.

Scott

On Wed, May 27, 2015 at 12:49 PM, RJJJM RJJJM <rjjkm@xxxxxxxxxxx> wrote:

Hi,

When my client application sends a BYE request the server adds a custom header in the 200 response that I need to read.  I don't see any virtual callbacks for this case in the InviteSession handlers.  From tracing it seems the only action taken is the 200 response is written in the stack log just before it is destroyed in InviteSession::dispatchTerminated(const SipMessage& msg).

Am I missing something or is there another way to bubble up this message to the client application?

Thanks,

Rex Martin

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/