Thanks Daniel. Config can be found here:
https://gist.github.com/benlangfeld/1b61f41c31129e8f2db3
INVITEs as provided (with a Route with two comma-separated elements) get
routed via the Contact header (instead of the second Route element).
When I use loose_route() on the INVITE, it goes into a lo
You should put the config somewhere for review. Note that default
kamailio.cfg ignores Route headers for initial requests. You have to
handle initial requests with loose_route().
Cheers,
Daniel
On 04/12/14 13:35, Ben Langfeld wrote:
> In that case the issue would have to be with the Kamailio-base
In that case the issue would have to be with the Kamailio-based edge proxy
which is not routing based on the second Route in the list. Is that a known
issue? I can provide more details if you think I'm on the right track.
On 4 December 2014 at 10:09, Daniel-Constantin Mierla
wrote:
> Hello,
>
>
Hello,
having more record-route addresses in the same header, separated by
comma, it is valid. Other headers (Via, Record-Route, Supported,
Required ...) can have same format, it is a matter of UAC how it builds
them, each with a header name or all under same header name.
Cheers,
Daniel
On 04/12
I'm facing a problem which I believe may be a bug in the registrar module's
lookup. When a registration comes with multiple Path headers, these are
recorded in the location table as comma separated. When the lookup is
performed and these are used to construct the Route header(s) on an INVITE,
this
