________________________________________
From: Rene Pankratz (JIRA) [no-re...@track.sipfoundry.org]

Snom RLS subscription fails in SipX 4.2.1
-----------------------------------------

                 Key: XX-8652
                 URL: http://track.sipfoundry.org/browse/XX-8652
             Project: sipXecs
          Issue Type: Bug
          Components: sipXrls
    Affects Versions: 4.2.0
         Environment: Clean Install from ISO (4.2) updated to 4.2.1-018930
            Reporter: Rene Pankratz
         Attachments: subscribe_failed_4.2.1-018930.pcap, 
subscribe_successful_4.0.4-017289.pcap

Snom Telephones are not able to subscribe RLS with SipX 4.2 anymore.

sipxrls sends "415 Unsupported Media Type or Content Encoding"
___________________________________________

I'm not sure how far the discussion has gotten on this issue, but the problem 
stems from the fact hat 4.2 enforces the requirement for a resource-list 
SUBSCRIBE to include "Accept: application/rlmi+xml", as the RLMI part of the 
notification describes the resources in the list.  See section 4.2 of RFC 4662:

4.3.  NOTIFY Bodies

   An implementation compliant to this specification MUST support the
   multipart/related and application/rlmi+xml MIME types.  These types
   MUST be included in an Accept header sent in a SUBSCRIBE message, in
   addition to any other types supported by the client (including any
   types required by the event package being used).

In general, if a subscription has notifications of type multipart/related, the 
MIME type of the "root component" of the notification must also be named in the 
Accept of the SUBSCRIBE.

The solution is for Snom to add the above value to the Accept list in its 
SUBSCRIBE.

Dale
_______________________________________________
sipx-users mailing list
sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to