Hi, Tito!
Yes, the Dialog id is mandatory. You can find more info in Section 4.1.1
of RFC4235[1].
Now I am not sure what you are trying to do, but if you use the
pua_dialoginfo module[2], OpenSIPS will be able to generate the Publish
for each call.
[1]
The closest thing that resembles the sort of body I need is using
dialog_info but even that is lacking because it supposed to be used for the
user you are subscribed to. Can you tell me if the dialog id is necessary
during publish? I tried reading https://tools.ietf.org/html/rfc4235 but
cannot
Thanks for your reply Razvan,
I tried using the conference event with application/xml+conf but opensips
is replying with these errors:
: ERROR:presence:handle_subscribe: unrecognized value [conference] in Event
header
: INFO:presence:handle_subscribe: Missing or unsupported event header field
Hi, Tito!
The Content-Type indicates how to read and parse the Message body. This
is a mandatory header, and without it the client can't know how to
interpret the body.
The Event header is used by opensips (and clients) to figure out the
event that happened.
The idea is that the clients will
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
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]
I want to implement something similar to
https://tools.ietf.org/html/rfc4579
On Mon, Dec 19, 2016 at 1:58 PM, Tito Cumpen 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
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