On 10/28/10 1:41 PM, Sergey Okhapkin wrote:
I've found one more feature missed in 3.1 - error_route is eliminated and
sanity module added. But if received SIP message is malformed and can't be
parsed, routing script is not executed and I have no way to log the message to
kamailio log. I did it
Hello,
one more thing ...
When you start a new topic, please create a new message, do not reply to
an old email received from the list because it will be added to that
discussion thread. For example, your message is part of Billing party
and radius accounting. Starting a new thread makes
Hello,
On 10/28/10 6:53 PM, Efelin Novak wrote:
Unfortunately I was wrong about variables ($var). They are same across
whole kamailio process. Neither $avp is good for me as they are
transaction aware. I need to store variable in the current dialog. I
was looking into dialog module, but no
Does tm.t_uac_wait RPC call block a worker process while waiting for a
reply, or use some sort of asynchronous callback?
Thanks,
--
Alex Balashov - Principal
Evariste Systems LLC
1170 Peachtree Street
12th Floor, Suite 1200
Atlanta, GA 30309
Tel: +1-678-954-0670
Fax: +1-404-961-1892
Web:
Daniel, I think this could be implemented without re-introduction of
error_route, what about core parameter route_on_error=yes/no (default no)? If
route on error is enabled, then sanity module will do the trick:
route{
if(!sanity_check(1159)) {
xlog(L_INFO,Bad message
Can someone post an example of usage of tm.t_uac_start from the
command line using sercmd over a UNIX domain socket (e.g.
/tmp/ser_ctl)? I am quite unclear on how to pass minimally necessary
header values to it in this form and cannot seem to get the syntax right.
Thanks!
--
Alex Balashov -
Hi Andrei,
Which version has this change? I don't see it in 3.0.4, the realease note
says that it is fixed. Here is the function
int tls_h_fix_read_conn(struct tcp_connection *c)
{
int ret;
struct tls_extra_data* tls_c;
ret = -1;=== Isn't it to be zero. Thats what i understood from the
On 10/29/10 11:53 AM, Sergey Okhapkin wrote:
Daniel, I think this could be implemented without re-introduction of
error_route,
it will not be re-introduced for sure, we have now a different core
framework which care reuse event_route mechanism.
In the past the error route was executed
I just realized that 3.1 executes main routing block when broken SIP message
is received! But sanity_check() function returns 0 on failed checks and script
execution stops, my favorite xlog() is not executed.
Oct 29 09:48:54 west /usr/local/sbin/kamailio[12225]: ERROR: core
On 10/29/10 4:09 PM, Sergey Okhapkin wrote:
I just realized that 3.1 executes main routing block when broken SIP message
is received! But sanity_check() function returns 0 on failed checks and script
execution stops, my favorite xlog() is not executed.
OK, that can be fixed very easy. Iirc, in
On 10/29/10 4:33 PM, Daniel-Constantin Mierla wrote:
On 10/29/10 4:09 PM, Sergey Okhapkin wrote:
I just realized that 3.1 executes main routing block when broken SIP
message
is received! But sanity_check() function returns 0 on failed checks
and script
execution stops, my favorite xlog()
On 10/29/10 5:40 PM, Sergey Okhapkin wrote:
I can't test now - high volume traffic is running. But I looked at the diff, it
seems to me OK, I see no reason why it could not work:-)
Because of the law, the Murphy law ;-)
Probably I will test sometime next week if you don't do it before and
On 10/29/2010 11:55 AM, Sergey Okhapkin wrote:
Kamailio 3.1 log is filled with lines like
Oct 29 03:32:46 west /usr/local/sbin/kamailio[632]: INFO:script: incoming
reply from udp:188.62.4.186:65333 SIP/2.0 404 Not Found Via: SIP/2.0/UDP
204.74.213.5:5060;branch=0
13 matches
Mail list logo
