Hi Juha
Thank you very much for the info. I will try to make out special LCR
handling support that full standard.
I hope you have a great weekend.
All the best
Will Ferrer
On Fri, Oct 31, 2014 at 12:56 AM, Juha Heinanen wrote:
> Will Ferrer writes:
>
> > It is odd this happened only after up
Will Ferrer writes:
> It is odd this happened only after upgrading to 1.4.6. I am guessing
> something got more strict about the formating. Also strange is that the
> tables for lcr_gw have type INT for both those columns (uri_scheme and
> transport). None the less changing my code to remove the t
Hi Juha
Correct as usual :).
It is odd this happened only after upgrading to 1.4.6. I am guessing
something got more strict about the formating. Also strange is that the
tables for lcr_gw have type INT for both those columns (uri_scheme and
transport). None the less changing my code to remove the
Will Ferrer writes:
> We are having an odd issue with our LCR. This started after we upgraded
> from kamailio 4.1.0 to 4.1.6.
i checked and there was no changes to lcr module from 4.1.0 to 4.1.6.
> Here is the situation:
>
> We populate our gw_uri_avp (stored in: $avp(i:709)) as follows:
> 16|1
Hi
We are having an odd issue with our LCR. This started after we upgraded
from kamailio 4.1.0 to 4.1.6.
Here is the situation:
We populate our gw_uri_avp (stored in: $avp(i:709)) as follows:
16|1[gateway ip address]||5060||1|1.
The $ru before running next gateway shows: sip:[destination nu
