[OpenSIPS-Devel] OpenXCAP refreshWatchers error

Anca Vamanu anca at voice-system.ro
Wed Sep 24 10:15:15 CEST 2008


Hi Andrew,

You are right about what happened when force_active was set.
As for the mysql logs, you should watch for the queries done by 
OpenSIPS. Look for something starting with 'SELECT doc from xcap' and 
check if the username and domain are correct.

regards,
Anca



Andrew Pogrebennyk wrote:
> Andrew Pogrebennyk wrote:
>> The document appears truncated while I see that eyeBeam sends correct
>> document on the wire. This could be a bug in the query sniffer, but 
>> in the opensips log it's also truncated so it could have happened 
>> somewhere in db_mysql. I have attached the log. Parameters were:
>> modparam("presence_xml", "force_active", 0)
>> modparam("presence_xml", "xcap_table", "xcap")
>> modparam("presence_xml", "pidf_manipulation", 1)
>> modparam("presence_xml", "integrated_xcap_server", 1)
>>
>> Thanks for looking.
>
> However, after looking more carefully I see that the properly formed 
> document is now saved to the DB and OpenXCAP works well now. So I 
> guess that truncation is in the logs only.
>
> As to why I was getting that error with force_active set to 1, it's 
> clear for me. in the beginning of get_rules_doc function there's such 
> block:
>
> if(force_active)
> {
>         *rules_doc= NULL;
>         return 0;
> }
>
> in presence.c line 535 there is then:
>
> result= ev->get_rules_doc(&uri.user,&uri.host,&rules_doc);
> if(result< 0 || rules_doc==NULL || rules_doc->s== NULL)
> {
>     LM_ERR( "no rules doc found for the user\n");
>     goto error;
> }
>
> So it looks like the module can't fetch the document for the user...
>




More information about the Devel mailing list