Still trying to get a response to my question from the Kamailio dev
team. Does Kamailio support OMA presence rules - like the one below.
I got this from the xcap server module documentation on the Kamailio website:
"
rls-services
pidf-manipulation
xcap-caps
resource-lists
p
Any input on the question below.
After further looking into it, the XML is from the following RCS spec:
http://www.gsma.com/rcs/wp-content/uploads/2012/03/1technicalrealv1.pdf
Is the Kamailio Presence module capable of handling the presence rule
xml below?
Thanks,
Sangeeta
On Mon, Oct 15, 2012
So based on the pres rules inserted by the clients, see example below
it's unclear how Kamailio is handling all the rules. Is Kamailio OMA
compliant. It definitely doesn't seem to like a condition without an
identity. IT should be matching the following rule below:
confirm
But since it doe
I meant Kamailio does a case-sensitive search.
Anyways, I am still trying to get the client working with Kamailio.
This client is proven to work with other presence server, so just
trying to piece things together so it works with the Kamailio PS.
I do not have RLS. The client does put the resourc
The path is from the resource list xml inserted by the client. The
issue over here was that the Kamalio code does a case insensitive
search for %5b and %5d and doesn't replace the path below with the "["
brackets.
This was the fix I had referred to in another thread
(update_subs_rlsdb: NO MATCH) t
This path does not look ok:
/xmlns:resource-lists/xmlns:list%5B@name="rcs"%5D
Where is it coming from?
Cheers,
Daniel
On 10/10/12 4:50 PM, Sangeeta Shah wrote:
Any clue what the correct path is supposed to be - per the data in the
xml and the path that's printed out by the module?
Thanks,
Sa
Any clue what the correct path is supposed to be - per the data in the
xml and the path that's printed out by the module?
Thanks,
Sangeeta
On Tue, Oct 9, 2012 at 2:38 PM, Sangeeta Shah wrote:
> Daniel,
>I don't know if this corresponds to the errors I was seeing before.
> But on a closer loo
Daniel,
I don't know if this corresponds to the errors I was seeing before.
But on a closer look I see the following errors when a subscribe
request comes in. This is how I am handling subscribe requests:
if( is_method("SUBSCRIBE"))
{
xdbg(" Handling subscribe re
Hello,
the error messages seem to be due to a broken XML document in a NOTIFY
-- they are printed because of errors reported by libxml2 parser. Can
you get a sip trace for such requests that throw these error messages in
the log?
Cheers,
Daniel
On 10/8/12 11:17 PM, Sangeeta Shah wrote:
Hi,
