Hi Daniel,

I wasn't able to update the software, but adding the extra lines to the config file helped.

Thanks,

Peter

On Sat, 2011-03-26 at 18:51 +0100, Daniel-Constantin Mierla wrote:
Hello,

can you try again after fetching the latest git version of branch 3.1? I 
did a commit to make sure the From and To URIs are parsed when handling 
SUBSCRIBEs in RLS. Normally, upon authentication and other actions 
executed prior to rls handling, these fields should be parsed (probably 
the reason that this was not noticed so far), but in your config it 
seems it is not that case.

If you have to stick to the version you have now, before handling the 
subscribe with rls, add following lines to force parsing From/To URIs:

$var(tmp) = $fU;
$var(tmp) = $tU;

Let me know if works this time.

Cheers,
Daniel

On 3/25/11 10:55 PM, Peter Dunkley wrote:
> Hi,
>
> The attached .zip file contains the full log and a .pcap file generated
> with ngrep for all SIP traffic on all interfaces.
>
> For me the interesting stuff in the log is from line 3315 to line 3335:
> 3315: rls_handle_subscribe() is called here
> 3316: this is where the "searching document for user sip:@" message appears
> 3328: this is where the RLS module logs that it (unsurprisingly) found no
> documents
> 3335: this is where the RLS modules states "list not found - searched for
> uri<sip:alice_all@46.38.172.248>"
>
> Thanks,
>
> Peter
>
>> Hello,
>>
>> can you send the log messages with debug=3 and ngrep of the SIP traffic
>> on all interfaces (including loopback) for such case (from the initial
>> subscribe, ideally sent for a resource list with one or two entries so
>> that there are not so many requests flowing around)? It will help to
>> understand and troubleshoot.
>>
>> Thanks,
>> Daniel
>


-- 
Peter Dunkley
Technical Director
Crocodile RCS Ltd