2007/3/14, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > There is another discovery: a call does not get terminated cleanly if a > 401/407 response to INVITE is not handled with nua_authenticate(), e.g. due > to absence of credentials to submit. Instead, after the final ACK is sent as > per the call model, an orphaned ACK "transaction" is left hanging that > temporarily prevents proper shutdown later. I'll have to check though if > that's an artefact of our application logic, probably by creating a > simplified test.
Indeed, the call is not terminated cleanly if the 401/407 is not handled properly. You have two options, you either call nua_authenticate or destroy the handle. It is not nice and does not work well with the call state machine. > May it be that nua_authenticate() (possibly with no NUTAG_AUTH parameters?) > is mandatory to handle the authentication responses? That would be one option. Currently, I believe, the stack does not try to send same credentials twice if they have been rejected (without stale parameter). I'm afraid it is up to the application to avoid supplying same credentials. -- Pekka.Pessi mail at nokia.com ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Sofia-sip-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
