[OpenSIPS-Users] pidf-manipulation - Openxcap spits error when saving pidf.

[mani sivaraman]

It was a type error. Instead of opensips sending Notify to watchers, I typed
as openxcap. I'm aware that openxcap sends xmlrpc to inform opensips about
the change in pidf document. It is opensips that consolidates the pidf that
was recevied via Publish and the xmlrpc pidf from xcap server and then send
the final pidf via spi notify to all watchers. That's why tihs feature is
called pidf manipulation.

The issue I'm facing is to debug why the pidf post by xcap server is not
reaching opensips via xmlrpc. PLease let me know how I can debug this. What
to look for ? etc.

All the xmlrpc logs and openxcap logs looks good and the xmlrpc post is
configured correctly on boith the server.

Your inout is much appreciated.

On Tue, Nov 10, 2009 at 5:40 PM, Iñaki Baz Castillo <ibc at aliax.net> wrote:

> 2009/11/10 mani sivaraman <mani.opensips at gmail.com>:
> > OPenxcap sends the Notify pidf to the
> > watcher with only offline status. It is not sending the full pidf with
> all
> > the tuple and person info. It sends a second Notify with no pidf payload
> and
> > with subscription status active and expires value = 1222.
>
> First you should study how XCAP works as a XCAP server doesn't send a
> "presence" NOTIFY to watchers. Instead it notifies to OpenSIPS
> presence server (via mi_xmlrpc) about a pidf change for a specific
> user so OpenSIPS presence server re-read the pidf document stored in
> XCAP table and generates the new NOTIFY merging presentity uploaded by
> that user via SIP (PUBLISH) and presentity uploaded by the client via
> XCAP (HTTP).
>
>
>
>
>
> --
> Iñaki Baz Castillo
> <ibc at aliax.net>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20091111/3d666f74/attachment-0001.htm