[reSIProcate] build challenge (407) after requiresChallenge() in DUM

[Justin Matthews]

Are there at least any objections to adding this functionality to DUM?

 

"Anyone..Anyone.......Bueller..Bueller"

 

:-)

 

Thanks,

-justin

 

  _____  

From: Justin Matthews [mailto:jmatthewsr at gmail.com] 
Sent: Tuesday, January 16, 2007 10:58 AM
To: 'resiprocate-devel at list.sipfoundry.org'
Subject: RE: build challenge (407) after requiresChallenge() in DUM

 

Doing this would require DUM ServerInviteSession->Reject() to be able to
recognize the 407/401 and do special handling to create the challenge and
then handle the subsequent re-tried INVITE correct?  What happens to the
DialogSet, Dialog, InviteSession in this case?  If all were destroyed when
sending the 407/401, which is what normally happens when a
ServerInvitesession->Reject(4xx) is sent, is there a timing problem if the
dset, dialog, invitesession are not torn down completely and the retried
INVITE w/auth comes in?  To solve this would a new state need to be added to
ServerInviteSession to wait for the ACK to 401/407 and then hang around for
a bit (32s) to see if a retried INVITE w/auth is coming?  

 

Thanks!

 

-justin

 

  _____  

From: Justin Matthews [mailto:jmatthewsr at gmail.com] 
Sent: Monday, January 15, 2007 4:06 PM
To: 'resiprocate-devel at list.sipfoundry.org'
Subject: build challenge (407) after requiresChallenge() in DUM

 

Is it possible to build a 407 (with challenge info) after returning False to
requiresChallenge() in DUM?  The reason for this is that invite requests are
shipped as events somewhere else in the system and challenges to invites are
the exception not the general rule.  It would save time to just allow the
other portion of our system to end these particular calls with 407 rather
than asking if a challenge is required for every invite.

 

Thanks,

-justin

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20070117/e96abe3c/attachment.htm>