[reSIProcate] In Dialog OPTIONS Question

[Scott Godin]

I think I found a use case for Options to be handled by the invite
session....

 

With my latest commit (to the teltel branch), we are attempting to store the
peer capabilities (ie. Allow/Support/etc headers) if they are sent in an
inbound INVITE or 200 response to our INVITE.  We do this in order to
determine whether or not the peer supports UPDATE requests (currently for
SessionTimers and TargetRefreshes).  But it is not a requirement that a UA
provide this info during call setup.  You can, of course, query this info by
forming an OPTIONS request.  Thus to have the InviteSession store the info
in an Options response, the response should be dispatched through the
InviteSession.

 

How do you guys feel about the following?

1.	Adding onOptions to InviteSessionHandler
2.	Having Invite session perform an automatic options query if peer
didn't provide info in call setup messaging - enable/disabled via Profile.
Note:  Pingtel phones currently do this.  Note:  this is something that can
be left entirely up to the application.

 

  _____  

From: Derek MacDonald [mailto:derek at xten.com] 
Sent: Tuesday, September 14, 2004 2:26 PM
To: 'Scott Godin'; resiprocate-devel at list.sipfoundry.org
Subject: RE: [reSIProcate] In Dialog OPTIONS Question

 

A general question about OPTIONS: is anybody doing something different with
options requests if they are in our out of dialog?  Before we implement
anything, we should see if we can unify our options handling logic.

 

OPTIONS are valid in subscribe dialogs.

 

 

 

  _____  

From: resiprocate-devel-bounces at list.sipfoundry.org
[mailto:resiprocate-devel-bounces at list.sipfoundry.org] On Behalf Of Scott
Godin
Sent: Tuesday, September 14, 2004 10:35 AM
To: resiprocate-devel at list.sipfoundry.org
Subject: [reSIProcate] In Dialog OPTIONS Question

 

Does anyone know if the OPTIONS request is valid in Dialogs other than ones
initiated via INVITE (ie. Subscription)?  

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