[OpenSIPS-Users] custom presence bodies

[Tito Cumpen]

Razvan,


Thanks for pointing that out. Will my subscribers get this xml via notify
regardless of the content type? say :

application/xml+conf"

or

application/pidf+xml

does the application header or Event:presence header mean anything to
opensips?

On Tue, Dec 20, 2016 at 12:04 AM, Răzvan Crainea <razvan at opensips.org>
wrote:

> Hi, Tito!
>
> I ran your example in an XML validator, and I noticed that your XML has an
> "error on line 2 at column 86: attributes construct error"[1]. If you add a
> space before the "state" attribute, the XML gets parsed properly[2].
>
> [1] http://www.utilities-online.info/xmltojson/?save=5a6721b1-
> 55f9-46c2-8bda-cf21e15e38b3-xmltojson
> [2] http://www.utilities-online.info/xmltojson/?save=320f586b-
> c2eb-4e73-b564-3f73f0120662-xmltojson
>
> Best regards,
>
> Răzvan Crainea
> OpenSIPS Solutionswww.opensips-solutions.com
>
> On 12/20/2016 01:38 AM, Tito Cumpen wrote:
>
> I want to implement something similar to
>
> https://tools.ietf.org/html/rfc4579
>
> On Mon, Dec 19, 2016 at 1:58 PM, Tito Cumpen <tito at xsvoce.com> wrote:
>
>> Group or Devs,
>>
>> Is there any way to allow custom bodies during a presence publish?
>>
>> I am trying to implement presence notifies for a conferencing scenario to
>> allow participants of a conference to subscribe to the conference events.
>> The events will send information about who connected to and disconnected
>> with the intention of syncing the UI. I am trying to publish the following:
>>
>> PUBLISH sip:ap5badj at blah.org SIP/2.0.
>> Call-ID: 861f3c86868d8a4b00276064d1205e0a at x.x.x.x.x.x.
>> CSeq: 2 PUBLISH.
>> From: "Dave Drummond" <sip:ddrummondahblh at blah.org>;
>> tag=62944280_a75dd11f_3a41c2f1_a8e175ca.
>> To: <sip:ap5badj at nurseliveconnect.org>.
>> Max-Forwards: 70.
>> User-Agent: Mobicents Sip Servlets 3.0.0-SNAPSHOT.
>> Event: presence.
>> Via: SIP/2.0/TCP 192.237.207.220:5080;branch=z9
>> hG4bKa8e175ca_3a41c2f1_7d6e0f5b-7595-4432-849e-500f6d4fe940.
>> Content-Type: application/pidf+xml.
>> Proxy-Authorization: Digest username="ddrummond.blah at blah.org",realm="
>> blah.org",nonce="585857390000212cd09ec487455386e318963e82d972f333",uri="
>> sip:ap5badj at blah.org",response="670c0336b89491900c284014c12b62ac".
>> Content-Length: 263.
>> .
>> <?xml version="1.0" encoding="utf-8" ?>.
>> <conference-info xmlns="urn:ietf:params:xml:ns:conference-info"
>> entity="sips:ap5badj"state="full" version="1">.
>> <users><endpoint entity="99999999">.
>> <status>connected</status>.
>> </endpoint>.
>> </users>.
>> </conference-info>.
>>
>>
>> but I get a 415 unsupported media type
>>
>> Dec 19 21:53:15 cloud-server-06 /sbin/opensips[31135]:
>> ERROR:presence_xml:xml_publ_handl: bad body format
>> Dec 19 21:53:15 cloud-server-06 /sbin/opensips[31135]:
>> ERROR:presence:handle_publish: in event specific publish handling
>>
>>
>> Can someone tell me how I can modify the body to make this work?
>>
>>
>> Thanks,
>> Tito
>>
>
>
>
> _______________________________________________
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
> _______________________________________________
> 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/20161220/7dcbc053/attachment-0001.html>