Hello Henning,
Thank you!
Regards,
Igor.
De : Henning Westerholt
Envoyé : vendredi 1 novembre 2019 18:32
À : Kamailio (SER) - Users Mailing List ;
igor.potjevle...@gmail.com; mico...@gmail.com
Objet : Re: [SR-Users] lookup(aliases) issues with 5.2
Hello Igor,
functional exten
Hello Daniel,
Thank you!
Is it pushed in one of the latest release? Because we don't have a
connection to git on our server. We build from tar.
Regards,
Igor.
De : Daniel-Constantin Mierla
Envoyé : jeudi 10 octobre 2019 14:40
À : igor.potjevle...@gmail.com; 'Kamailio (SER) - Users
Hello Daniel,
I confirm that we did that indeed. Just added the support of "_" instead of
rollback on the whole code.
Thank you!
Regards,
Igor.
De : Daniel-Constantin Mierla
Envoyé : mercredi 11 septembre 2019 09:51
À : igor.potjevle...@gmail.com; 'Kamailio (SER) - Users Maili
Hello Daniel, Henning,
I'd be interested, but if I'm the only one... Otherwise I can indeed remove
this patch as Henning suggests, but it embarrasses me to have a different
source code.
Tell me if it's possible to make it customizable. Otherwise I will consider
either removing the patch or fin
Hello,
Hmm, ok. Saw it.
Is it possible to reconsider a less strict control?
Regards,
Igor.
De : Daniel-Constantin Mierla
Envoyé : mercredi 28 août 2019 10:25
À : igor.potjevle...@gmail.com; 'Kamailio (SER) - Users Mailing List'
Objet : Re: [SR-Users] lookup(aliases) issues with
Hello Daniel,
We moved to the latest 5.2.4 but hostname with underscore are still not
handle properly.
Is it a real design choice or a mistake somewhere in the code that handle
domain name?
Regards,
Igor.
De : igor.potjevle...@gmail.com
Envoyé : mardi 27 août 2019 11:53
À : mico
Hello Daniel,
Thank you for getting back to me.
We will update with 5.2.4 and I'll let you know if it's solved.
Regards,
Igor.
De : Daniel-Constantin Mierla
Envoyé : mardi 27 août 2019 09:39
À : Kamailio (SER) - Users Mailing List ;
igor.potjevle...@gmail.com
Objet : Re: [SR-User
Hello!
Any help on that matter? Sounds like the domain parsing have been updated.
Is it possible to back on the previous mode?
Regards,
Igor.
De : igor.potjevle...@gmail.com
Envoyé : vendredi 23 août 2019 18:53
À : 'Kamailio (SER) - Users Mailing List'
Objet : lookup(aliases) iss
Hello!
I have notice some issues with lookup(aliases) since I upgraded to 5.2 from
5.1:
First with kamctl: If this default command is executed:
ctl_cmd_run ul.add "$USRLOC_TABLE" "$OSERUSER@$OSERDOMAIN" "$2" \
"$UL_EXPIRES" "$DEFAULT_Q" "$UL_PATH" "$UL_FLAGS" "$BR_FLAGS" "$ALL_METHODS"
hi Dmitri,
Having 2 dpid and use rand_event() seems to work like a charm! Thank you for
the suggestion.
Regards,
Igor.
De : sr-users De la part de Dmitri
Savolainen
Envoyé : lundi 20 août 2018 19:41
À : Kamailio (SER) - Users Mailing List
Objet : Re: [SR-Users] Dialplan priority
Hello,
I'm not sure to understand in which situation "pr" value is used. For
example: if I have two identical rules except pr value: 1 with 1 and the
second with 2, then the rule with pr 2 is never used.
Someone can help me to understand? Thank you.
The finality I'd like to accomplish i
Hello,
I'm maybe confused on how to use dialplan module.
I have a dialplan setup for a long time now and I'd like to add a new rule
with the same match_exp than an existing one but with a different repl_exp.
If I set the same priority, the latest entry is used systematically. If I
set priori
Thank you. I'm running 4.2.7 but I think both options are available too.
I'm not sure to understand the first thing about t_set_fr. Currently, when I do
lookup(aliases), the default behaviour is to send both calls simultaneously if
there is 2 entries in aliases table. So, first, I'm wondering ho
Hello,
I know that the default behaviour of two aliases in kamailio.aliases result
in parallel forking.
I'm wondering if its possible to do serial forking instead? For example, in
case that the first INVITE has no 180/183, or neither 100 Trying, then send
the INVITE to the second entry?
Re
Hello Henning,
Thank you !!
Regards,
Igor.
-Message d'origine-
De : Henning Westerholt
Envoyé : vendredi 13 avril 2018 17:43
À : sr-users@lists.kamailio.org
Cc : igor.potjevle...@gmail.com; mico...@gmail.com
Objet : Re: [SR-Users] Kamailio 4.2.8 has crashed
On Friday, 13 April 2018 0
Hello Daniel,
I got a new occurrence last night with the following backtrace, looks like
the same:
(gdb) backtrace
#0 0x7f92366761f7 in raise () from /lib64/libc.so.6
#1 0x7f92366778e8 in abort () from /lib64/libc.so.6
#2 0x0061fb2c in qm_free (qm=0x7f91f4eaf000, p=0x7f92
Hello Daniel,
Ok, thank you for your feedback. mem_safety is available in 4.2?
Regards,
Igor.
De : Daniel-Constantin Mierla
Envoyé : mercredi 11 avril 2018 16:06
À : Kamailio (SER) - Users Mailing List ;
igor.potjevle...@gmail.com
Objet : Re: [SR-Users] Kamailio 4.2.8 has crashed
Hi Dmitri,
Nice, thank you. Sounds good for the moment!
Regards,
Igor.
De : sr-users De la part de Dmitri
Savolainen
Envoyé : mercredi 11 avril 2018 14:41
À : Kamailio (SER) - Users Mailing List
Objet : Re: [SR-Users] Kamailio logs in RHEL 7 environment
Hi. i set for it in my
Hello,
I had a crash on one Kamailio instance with the following backtrace:
Core was generated by `/usr/local/sbin/kamailio -m 704 -M 128 -P
/run/kamailio/kamailio.pid'.
Program terminated with signal 6, Aborted.
#0 0x7f92366761f7 in raise () from /lib64/libc.so.6
Missing separate d
Hello !
Since I moved my OS to RHEL 7, the logs management has changed. I cannot
have all logs in /var/log/messages as I used to have. Indeed, there is
journald/rsyslog which blocked logs to be written after hundreds/thousands
of messages.
I tried to set these values to 0:
vim /etc/systemd
Hello Daniel,
Thank you. Do you know some OS counters (in /proc I guess?) I can look to in
order to diagnose deeper?
Anyway, I'm already sure that the CAPS was higher than during another period
of time.
Regards,
Igor.
De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Envoyé
Hello Daniel,
Both Kamailio and MySQL are running under RHEL. But SELinux is deactivated.
Regards,
Igor.
De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Envoyé : jeudi 23 novembre 2017 12:56
À : Kamailio (SER) - Users Mailing List ;
igor.potjevle...@gmail.com
Objet : Re: [
Hello,
We suddenly had an issue on one Kamailio instance: we were not able to
restart. Kamailio started to boot and fork and suddenly crashed.
The last logs reported a failure regarding the ability to connect to one
MySQL instance.
I finally succeed to restart after increasing: fork_delay
Hello Daniel,
Thank you for pinpoint.
Is this commit into branch 5 only?
Regards,
Igor.
De : Daniel-Constantin Mierla [mailto:mico...@gmail.com]
Envoyé : mardi 3 octobre 2017 20:23
À : Kamailio (SER) - Users Mailing List ;
igor.potjevle...@gmail.com
Objet : Re: [SR-Users] Multi cr
Hello !
I have multi crashes on a Kamailio 4.2.8 instance.
Already 6 coredump today, same time with the same scenario. Below the output
of the last coredump:
(gdb) where
#0 0x003d6f6328a5 in raise () from /lib64/libc.so.6
#1 0x003d6f634085 in abort () from /lib64/libc.so.6
#2
25 matches
Mail list logo