Hi,
hmm, it seems that if stack ends up selecting OPTIONS as the keep-alive
mechanism, but the proxy challenges the OPTIONS, the stack does not quite
work right -> the 407 is never delivered to the client which could
authorize it (that's my guess, could be something else of course).
If I try plain ol' OPTIONS (not related to keep-alive), I get the
challenge and can handle it with nua_auth().
How's this suppose to work?
--
under work: Sofia-SIP at http://sofia-sip.sf.net
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Sofia-sip-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel