Opened 17 years ago

Last modified 17 years ago

#73 closed defect

Unregistration does not respond to authentication challenge (401/407) after it has been marked for deletion — at Version 3

Reported by: bennylp Owned by: bennylp
Priority: normal Milestone: release-0.5.10
Component: pjsip Version: 0.5.9
Keywords: Cc:
Backport to 1.x milestone: Backported:

Description (last modified by bennylp)

After application has marked client registration session for deletion(pjsip_regc_destroy() is called), the client registration session does not respond to authentication challenge in 401/407 response.

Here are the steps to reproduce it:

 // Create Un-REGISTER request
 status = pjsip_regc_unregister(regc, &tdata);

 // Send the request.
 status = pjsip_regc_send(regc, tdata);

 // Signal regc to destroy itself after all transactions complete
 status = pjsip_regc_destroy(regc);  

Change History (3)

comment:1 Changed 17 years ago by bennylp

  • Description modified (diff)

comment:2 Changed 17 years ago by bennylp

  • Cc bennylp@… added

comment:3 Changed 17 years ago by bennylp

  • Description modified (diff)
  • Summary changed from Unregistration does not respond to authentication challenge (401/407) in some cases to Unregistration does not respond to authentication challenge (401/407) after it has been marked for deletion
Note: See TracTickets for help on using tickets.