More about PA...
I have created the resource list for the user's contact list and I am sending a SUBSCRIBE to it with Req-URI sam-list@test.mydomain.com.
Unfortunately I've got next ERROR in the log:
5(30685) list named default 5(30685) XCAP uri 'http://localhost/xcap/resource-lists/users/sam/resource-list.xml' 5(30685) parse_headers: flags=21 5(30685) ERROR: rls_handler.c:201: required type multipart/related not in Accept headers
Is there some config issue either in my eyeBeam or in the SER that is causing this problem?
Any comment is really wellcome!!
Samuel.
If you are using eyeBeam's feature "subscribe to resource list" (or how it is called) it doesn't send required headers (like this Accept and Supported: eventlist). But if you add a resource list URI manually to your contact list, it works (it sends this headers and processes NOTIFY bodies correctly). I think that this is a bug in eyebeam (I have written this to them long time ago, but I haven't received any response).
Vaclav
On Mon, May 15, 2006 at 01:56:15PM +0200, samuel wrote:
More about PA...
I have created the resource list for the user's contact list and I am sending a SUBSCRIBE to it with Req-URI sam-list@test.mydomain.com.
Unfortunately I've got next ERROR in the log:
5(30685) list named default 5(30685) XCAP uri 'http://localhost/xcap/resource-lists/users/sam/resource-list.xml' 5(30685) parse_headers: flags=21 5(30685) ERROR: rls_handler.c:201: required type multipart/related not in Accept headers
Is there some config issue either in my eyeBeam or in the SER that is causing this problem?
Any comment is really wellcome!!
Samuel.
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers