just to complete this thread, it turned out that from uri matching
didn't happen because load_gws() was called without caller uri
argument.
-- juha
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
Geoffrey Mina writes:
> What can I do to debug this? I checked and we aren't seeing any of the
> "failed to compile regex" errors in the logs. We have 4 servers that are
> all displaying the same behavior (read: ignoring the from_uri match on a
> lower priority).
you didn't answer if this issue
Juha,
Thank you for all of your help so far, but we are still totally stuck
trying to make this work. We have double and triple checked our
configuration, database, and INVITE and everything is in-line with what
previously worked (in 1.5). We are running 4.1.3, is that what you were
testing on?
Geoffrey Mina writes:
> Right now, I would think that with our Priority of 0 on the route with the
> from_URI match, the algorithm should always look at that one first and
> route the calls accordingly.
>
> Since we have the priority correctly set to evaluate in the order we want,
> what next can
OK, has this behavior changed since Kamailio 1.5 because this previously
worked.
Right now, I would think that with our Priority of 0 on the route with the
from_URI match, the algorithm should always look at that one first and
route the calls accordingly.
Since we have the priority correctly set
Geoffrey Mina writes:
> OK. WE have made a change so that the priority is 0 for the route that has
> the from_uri. We are still not seeing this route get matched
> properly.
i tried to say that from uri plays no role in your lcr setup, because +1
matches both rules 31 and 5. if you want it mat
OK. WE have made a change so that the priority is 0 for the route that has
the from_uri. We are still not seeing this route get matched properly.
Here is what the INVITE looks like:
INVITE sip:+19137274555@1.2.3.4:5060 SIP/2.0
Via: SIP/2.0/UDP 1.2.3.4:5060;branch=z9hG4bK5b52e524;rport
From: "20
Geoffrey Mina writes:
> The LCR module is behaving in a way that is inconsistent with our old 1.5
> versions. We have a customer that passes a certain caller-id. That
> from_uri should be routing over a specific trunk. Here are the relevant
> bits of the LCR data from kamcmd.
>
> I would expec
Greetings,
I need a little help with the LCR module. I am running Kamailio 4.1.2.
The LCR module is behaving in a way that is inconsistent with our old 1.5
versions. We have a customer that passes a certain caller-id. That
from_uri should be routing over a specific trunk. Here are the relevant
