Hi Daniel
I seem to see be having the issue with out with out defining the dstid_avp.
I guess it's a non issue but was wondering if there was a way to make it go
away.
Thanks again for the assistance.
Will
On Tue, Dec 9, 2014 at 4:06 PM, Will Ferrer
wrote:
> Hi Daniel
>
> Thanks for the write
Hi Daniel
Thanks for the write back.
We are using the dstid_avp but we are not using alg 10 for call load
distribution.
We have dstid_avp set because the distribution alg is a directive we set
for the deployment via the local.cfg. We leave the avp for it on incase we
switch the deployment to alg
Hello, i just installed Kamailio 4.2.1 on debian Wheezy, would like to know
why when Kamailio starts i see this on netstat -an ??
raw0 0 0.0.0.0:255 0.0.0.0:*
7
is it normal??
why?
Thanks in advance
___
SIP Express Router (SER
Hi Daniel,
Thanks a lot, we will give it a try and let you know how it goes!
On Mon, Dec 8, 2014 at 6:52 AM, Daniel-Constantin Mierla
wrote:
> Hello,
>
> the patch to fix this should be in master, 4.2 and 4.1 git branches.
>
> Thanks for helping to troubleshoot this. Let me know if all goes fi
That's because $ct refers to the value of the entire Contact header, not
just the URI portion.
You need to get at the URI portion first:
xlog("L_INFO", "$(ct{nameaddr.uri}{uri.user})\n");
--
Alex Balashov - Principal
Evariste Systems LLC
235 E Ponce de Leon Ave
Suite 106
Decatur, GA 30030
U
Hi Daniel,
The child process is terminated by signal 11 (SIGSEGV).
Dec 8 16:41:25 /sbin/kamailio[12000]: ALERT: [main.c:777]:
handle_sigs(): child process 12003 exited by a signal 11
Dec 8 16:41:25 /sbin/kamailio[12000]: ALERT: [main.c:780]:
handle_sigs(): core was generated
Dec 8
Hello,
kamailio itslef it is a sip signaling server with a proxy architecture,
if you look for a sbc like a b2bua, it isn't. If you look for a sbc like
edge proxy/load balancer, then it is.
Also, kamailio doesn't have any built it interaction with other sbcs,
but it has lot of tools that can be u
Hello,
do you use call load dispatching algorithm or have the dstid attribute set?
The log is harmless itself if not using the call load dispatching algorithm.
Cheers,
Daniel
On 05/12/14 02:03, Will Ferrer wrote:
> Hi All
>
> We recently discovered that our dispatcher boxes have this error
> co
Hello,
On 08/12/14 16:42, Timo Klecker wrote:
>
> Hi Daniel,
>
>
>
> I tried to increase shared memory by setting a parameter in kamctlrc:
>
> STARTOPTIONS="-m 64"
>
>
>
> When recreating the crash I counted pv_get_ruri_attr in the logfile
> just to see if the shared memory changed anything:
>
