Hi all,
current documentation for the nua_i_refer event states:
Incoming REFER call transfer.
The tag list will contain tag NUTAG_REFER_EVENT() with the Event header
constructed from the REFER request. It will also contain the
SIPTAG_REFERRED_BY() tag with the Referred-By header containing the identity of
the party sending the REFER. The Referred-By structure contained in the tag is
constructed from the From header if the Referred-By header was not present in
the REFER request.
The application can let the nua to send NOTIFYs from the call it initiates with
nua_invite() if it includes in the nua_invite() arguments both the
NUTAG_NOTIFY_REFER() with the handle with which nua_i_refer was received and
the NUTAG_REFER_EVENT() from nua_i_refer event tags.
Parameters:
status status code of response sent automatically by stack
phrase a short textual description of status code
nh operation handle associated with the incoming request
hmagic application context associated with the handle (NULL if outside
of an already established session)
sip incoming REFER request
tags NUTAG_REFER_EVENT()
SIPTAG_REFERRED_BY()
and seems to *assume* that the response to the REFER event will be
automatically sent, and I experienced the sofia-sip stack will
automatically send a response with status 202.
I wonder if it is possible to disable this behavior, and manually
choose (e.g. with nua_respond()) which response to give to the REFER
method.
Many thanks in advance.
Regards.
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
