On 02/04/2013 06:07 PM, Klaus Darilion wrote:
On 04.02.2013 11:26, Vitaliy Aleksandrov wrote:
The problem was caused by memlog and memdbg options.
So, how the problem is triggered and how did you solved it?
regards
Klaus
Both memlog and memdbg were removed from a kamailio config as I don't
On 04.02.2013 11:26, Vitaliy Aleksandrov wrote:
The problem was caused by memlog and memdbg options.
So, how the problem is triggered and how did you solved it?
regards
Klaus
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing l
The problem was caused by memlog and memdbg options.
___
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On 02/01/2013 11:38 AM, Vitaliy Aleksandrov wrote:
Hi list.
I have a strange problem with syslog.
Kamailio doesn't send any messages to syslog from UDP workers that are
bound to sock=127.0.0.1:5060.
Neither LM_DBG() from a source code nor xlog("any level", "") works.
I use kamailio-3.2.4 with
Daniel-Constantin Mierla writes:
> looking at the code history, you added this check in the commit
> 019ab5e2d6730b764b20a890f9a3b5f9237b6338 .
>
> It is about checking if it is a valid domain, to avoid doing queries on
> invalid values. In this particular case is probably related to presence
Hello,
looking at the code history, you added this check in the commit
019ab5e2d6730b764b20a890f9a3b5f9237b6338 .
It is about checking if it is a valid domain, to avoid doing queries on
invalid values. In this particular case is probably related to presence
of characters [, ], and :.
Cheer
