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
Hi Juha,
All of the NOTIFYs in the trace are generated by either the Kamailio
presence module or the Kamailio RLS module.
I have no idea why this is happening.
Regards,
Peter
On Sat, 2011-03-26 at 06:45 +0200, Juha Heinanen wrote:
> peter,
>
> another weird thing is that all notifys contain
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
th
peter,
another weird thing is that all notifys contain two 'transport=tcp
params in their contact uris. any idea where they come from?
-- juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
ht
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
und
Hi Juha,
My configuration is trying to achieve exactly what you suggest.
The Kamailio presence and RLS modules send NOTIFYs using the route-set
established by the SUBSCRIBE. This means that if I call
add_contact_alias() and just pass the SUBSCRIBE to the module the NOTIFY
will use that contact a
peter,
i don't have experience with k rls module, but in my environment if
initial subscribe comes from behind nat, i just call add_contact_alias
and add a nat param to r-r header for in-dialog requests. notifys from
rls server then contain ;alias param in request uri and the nat param in
route h
Hello,
I am using Kamailio and nathelper to connect UAs behind a NAT. However,
I want to use presence and RLS in this system as well. The problem I
have is that the presence and RLS modules are not nathelper aware and
the NOTIFY requests that they generate are targeted at the private
network IP
