[asterisk-bugs] [Asterisk 0010354]: [patch] Add Basic Support For RFC 4662 (Subscribe to lists)

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10354 
====================================================================== 
Reported By:                irroot
Assigned To:                putnopvut
====================================================================== 
Project:                    Asterisk
Issue ID:                   10354
Category:                   Channels/chan_sip/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     assigned
Asterisk Version:           1.6.0-beta8 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2007-08-01 07:56 CDT
Last Modified:              2008-08-25 17:21 CDT
====================================================================== 
Summary:                    [patch] Add Basic Support For RFC 4662 (Subscribe to
lists)
Description: 
Preamble to 4662

---
   This document presents an extension to the Session Initiation
   Protocol (SIP)-Specific Event Notification mechanism for subscribing
   to a homogeneous list of resources.  Instead of sending a SUBSCRIBE
   for each resource individually, the subscriber can subscribe to an
   entire list and then receive notifications when the state of any of
   the resources in the list changes.
---

the polycom 601 BLF uses this extension to populate and manage its BLF i
cant see why not to support it in asterisk ??

please see the packet trace (supplied by polycom thx this is invaluable
...) a comparison (summary of progress so far) and a patch against 1.4.9
(obviously this is for 1.6 ...) 
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0004903 [patch] SIP over TCP project
====================================================================== 

---------------------------------------------------------------------- 
 (0091720) putnopvut (administrator) - 2008-08-25 17:21
 http://bugs.digium.com/view.php?id=10354#c91720 
---------------------------------------------------------------------- 
I've been reading over the RFC and the latest patch submitted, and I have a
few questions regarding phone behavior when making use of this
functionality.

To preface this, I'm used to maintaining a buddy list on my phone. Either
some sort of button with a lamp represents a subscribed buddy, or there is
a directory of buddies I can access somehow. When implementing support for
this RFC, it appears that the buddy list is not maintained locally but is
maintained via some remote method. 

How does the phone represent the information that is sent back to it with
a NOTIFY? Does the phone populate its buttons and buddy list directory
itself? Can you also use your phone to subscribe to buddies not in the list
or are you restricted to just buddies in the remote list? Is it possible
for a phone to subscribe to a list that the phone itself generated? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-25 17:21 putnopvut      Note Added: 0091720                          
======================================================================