This is an interesting issue, but I can't look at it right now. I suggest that you file a bug report at: http://projects.savoirfairelinux.net/projects/activity/sflphone
mod_on_rx_request is indeed one of the numerous callbacks used for sip events. You can see the whole list here: http://www.pjsip.org/pjsip/docs/html/structpjsip__module.htm#9e2baa7651d1ed440becd0df112df006 OPTION is handled more specifically in handle_incoming_options() (sipvoiplink.cpp) where we compare with our capability. Also check in pjsip_init() where we set the allowed[] array : I'm pretty sure that it's not up to date with what SFLPhone should return. Pierre-Luc Bacon On Fri, 2009-10-02 at 19:27 -0300, Thomas Alexander Ewald wrote: > Hello, > > I managed to insert the User-Agent in all outgoing messages, and now I > can make some calls. > The problem is that the SIP server send an OPTIONS message, and the > client doesn't respond with a 200 OK message, and the call is > interrupted after 45 seconds. > I looked into the sipvoiplink.cpp source file, and the callback function > pj_bool_t mod_on_rx_request (pjsip_rx_data *rdata) > is registered. > For my understanding, these callbacks methods are called in > pjsip_dlg_on_rx_request method. Am I right? > But, for some strange reason, nothing happens when the OPTION message > arrives. > Now a silly question: how can I debug, or at least see the _debug messages? > > Thanks again! > Thomas > > _______________________________________________ > SFLphone mailing list > [email protected] > http://lists.savoirfairelinux.net/mailman/listinfo/sflphone _______________________________________________ SFLphone mailing list [email protected] http://lists.savoirfairelinux.net/mailman/listinfo/sflphone
