Hi All,
On register we store the contact in an avp variable and do a t_relay().
After t_relay() the $avp variable becomes null.
I printed the value before after t_relay() to determine this behavior.
This happens only on registration load test around 2000 subcribers with ( 4
REGISTER/sec). This ha
Gary Chen writes:
> I added lcr module in my kamailio.cfg file.
> After run this: ./kamctl -E I got this error:
> 0(23744) ERROR: lcr [lcr_mod.c:1235]: lcr_gw params at row <0> does
> not start with ';' 0
if you include a value in uri params field, it (as the error message
tells), needs to star
I am using Kamailio 3.1.2.
I added lcr module in my kamailio.cfg file.
After run this: ./kamctl -E I got this error:
0(23744) ERROR: lcr [lcr_mod.c:1235]: lcr_gw params at row <0> does not start
with ';' 0
I have set up some gateway information in lcr_gw , lcr_rule and
lcr_rule_target. From
On 02/15/2011 06:31 PM, Thomas Baumann wrote:
Hello
I have made a patch to 3.1(e914f97b4) . The poll() event list was not
cleared when a response was received so when 2 servers responded one
after the other it might block in an incorrect recv(). Can you please
test with this?
Marius
Hello,
Hello,
I did a fallback to the original source, without sucess. I still have massive
timeouts. So far I have no idea, how to go on.
ps. what lenght of the carrier codes would be ok ? 3...10 digits, additional
characters needed like A,B,C,D,E,F?
regards,
Thomas
Hi Henning,
this change
Hi all,
I am trying to integrate Kamailio and Asterisk as explained in
http://kb.asipto.com/asterisk:realtime:kamailio-3.0.x-asterisk-1.6.2-astdb
document but I have some problems.
1. When Asterisk sends the call back to Kamailio, Asterisk generates
new INVITE but with wrong From URI. In From hea
Hi,
I downloaded the kamailio 3.1.2 and the piece of code where core is
generated didn't change. Now I'll test this version to know if the problem
continues... Has anyone found core described in the previous mail in version
3.1.2 of kamailio?
Best Regards
2011/2/15 Daniel-Constantin Mierla
>
Hi Stagg,
with regards to the failing function, there was a bugfix in the dialog
module which, unfortunately, didn't make it into 1.5.5 in time (revision
6049). Could you try the latest SVN of 1.5 and see if it solves the issue?
Thanks.
Cheers,
--Timo
On 14.02.2011 21:07, Stagg Shelton wrot
Hello,
first, for postgres users i recommend to use version 3.1.2, since it has
the reconnect part solved.
As for 1.5.0, you should try with 1.5.5, since between 1.5.0 and 1.5.5
were many fixes (the config and db structure are the same so you don't
need to change anything to update to 1.5.5)
