Re: [reSIProcate-users] Application-specific "Reason" for response via DUM
There are a number of interfaces for adorning messages before they are sent out on the wire - the easiest one for you would be to use the InviteSessionHandler::onReadyToSend method - using this you can modify the message before it is sent.
Scott
On Tue, Oct 5, 2010 at 11:03 AM, Paul Kurmas
<pkurmas@xxxxxxxxxxxxx> wrote:
I've been asked to apply an application-specific textual description to the Status Line in some non-standard (but valid) 4xx responses. At the stack level, Resiprocate allows this -- I see the argument "reason" to Helper::makeResponse, which if not specified uses the string returned by Helper::getResponseCodeReason.
But we get to Helper::makeResponse through Dialog::makeResponse called from InviteSession::reject. There is no means to pass in the reason to the reject function. I do see the "Warning" mechanism, but our situation isn't sufficiently consistent with the examples in RFC3261 to make me think Warning is the right solution.
My system is still using Resiprocate 1.3.5, if I recall correctly. If these interfaces have been enhanced since, please be gentle. :-)
Thanks.
PK
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/