[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:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   10354
Category:                   Channels/chan_sip/NewFeature
Reproducibility:            N/A
Severity:                   feature
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.2.0-beta1 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2007-08-01 07:56 CDT
Last Modified:              2009-04-10 17:51 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
====================================================================== 

---------------------------------------------------------------------- 
 (0103096) dvossel (administrator) - 2009-04-10 17:51
 http://bugs.digium.com/view.php?id=10354#c103096 
---------------------------------------------------------------------- 
I've written a patch for this in trunk, but am having trouble testing it.

I have the following enabled within my polycom 650's phone config
<attendant
  attendant.uri="1234"
  attendant.reg="3"
/>

with this option set, I get rlmi SUBSCRIBE requests from the phone, When I
send a NOTIFY (an example is given below), the phone responds with a 200ok,
but nothing happens.  I'd expect the phone's expansion module to be
populated with the resources within the RLMI list, but it doesn't happen. 
Since I don't have a server that supports rlmi to test the Polycom with, I
really don't know what the expected behavior is.  I've looked through the
polycom admin guide but its rather vague about the whole thing...

So, has anyone gotten a rfc4662 capable Polycom phone to work with an rlmi
capable server. if so, how was the phone configured and what were the
results. 


NOTIFY sip:5006 at 10.24.22.246 SIP/2.0
Via: SIP/2.0/UDP 10.24.18.230:5060;branch=z9hG4bK3d440288;rport
Max-Forwards: 70
From: <sip:1234 at manbearpig>;tag=as3ecb08bc
To: "5006" <sip:5006 at manbearpig>;tag=2EE85E33-7BBC79C4
Contact: <sip:1234 at 10.24.18.230>
Call-ID: 138c3240-c616fe71-effd8bc2 at 10.24.22.246
CSeq: 115 NOTIFY
User-Agent: Asterisk PBX
SVN-dvossel-sip_resource_list_trunk-r187311M-/trunk
Subscription-State: active
Require: eventlist
Content-Type:
multipart/related;type="application/rlmi+xml";start="<280322ac at manbearpig>";boundary="50UBfW7LSCVLtggUPe5z"
Event: dialog
Content-Length: 922

--50UBfW7LSCVLtggUPe5z
Content-Transfer-Encoding: binary
Content-ID: <280322ac at manbearpig>
Content-Type: application/rlmi+xml; charset="UTF-8"

<?xml version="1.0" encoding="UTF-8"?>
<list xmlns="urn:ietf:params:xml:ns:rlmi" uri="sip:1234 at manbearpig"
version="0" fullState="true">
<resource uri="sip:custom3 at manbearpig">
<name>custom3</name>
<instance id="099291ed" state="active" cid="7a551027 at manbearpig"/>
</resource>
</list>

--50UBfW7LSCVLtggUPe5z
Content-Transfer-Encoding: binary
Content-ID: <7a551027 at manbearpig>
Content-Type: application/dialog-info+xml

<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0"
state="full" entity="sip:custom3 at manbearpig">
<dialog id="custom3">
<state>terminated</state>
</dialog>
</dialog-info> 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-10 17:51 dvossel        Note Added: 0103096                          
======================================================================