Dear Klaus <br>I am little bit new to linux debugging. Please let me know below stuff.<br><br>1. Whats the extension of core file.<br>2. Will the core files be generated in /home/user path or some other default path<br>3. Do I need to recompile Kamailio source with -g option , or by default it is compiled with -g option<br>
4. I hope we need to run "ulimit" before we start the program or it is not required.<br><br>My observation is if I run directly kamailio it is crashing, if I run with gdb it is not crashing, not sure why this happens.<br>
<br>Best Regards<br>kamal<br><br><br><br><div class="gmail_quote">On Thu, Oct 25, 2012 at 8:01 PM, Klaus Darilion <span dir="ltr"><<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@pernau.at</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">SIGABRT 6 Core Abort signal from abort(3)<br>
<br>
This means that there was an error condition detected in the Kamailio code and the abort(3) function was called. As you see in the logs a core file was generated. Find the core file and load it into gdb and execute "backtrace". It will show you were the problem happened and post it here.<br>
<br>
regards<br>
Klaus<div class="im"><br>
<br>
On 25.10.2012 16:23, Kamal Palei wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
Dear Klaus<br>
The certificate verification I have disabled.<br>
<br>
Facing a new problem.<br>
When there is a connection reset, that time Kamailio is crashing.<br>
During crash, I get below logs. Any idea why it is crashing and how can<br>
I avoid it.<br>
<br></div>
/oot@B2BUA:/usr/local/src/<u></u>scripts# 9(9557) : <core><div class="im"><br>
[mem/q_malloc.c:431]: BUG: qm_free: bad pointer (nil) (out of memory<br>
block!) - aborting<br>
0(9548) ALERT: <core> [main.c:742]: child process 9557 exited by a<br>
signal 6<br>
0(9548) ALERT: <core> [main.c:745]: core was generated<br>
0(9548) INFO: <core> [main.c:757]: INFO: terminating due to SIGCHLD<br>
6(9554) INFO: <core> [main.c:808]: INFO: signal 15 received<br>
8(9556) INFO: <core> [main.c:808]: INFO: signal 15 received<br>
4(9552) INFO: <core> [main.c:808]: INFO: signal 15 received<br>
5(9553) INFO: <core> [main.c:808]: INFO: signal 15 received<br>
3(9551) INFO: <core> [main.c:808]: INFO: signal 15 received<br>
7(9555) INFO: <core> [main.c:808]: INFO: signal 15 received<br>
1(9549) INFO: <core> [main.c:808]: INFO: signal 15 received<br>
2(9550) INFO: <core> [main.c:808]: INFO: signal 15 received<br>
0(9548) : <core> [mem/q_malloc.c:431]: BUG: qm_free: bad pointer (nil)<br>
(out of memory block!) - aborting<br>
<br>
<br>
THANKS<br>
kamal<br>
/<br>
On Thu, Oct 25, 2012 at 7:43 PM, Klaus Darilion<br></div><div class="im">
<<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@pernau.at</a> <mailto:<a href="mailto:klaus.mailinglists@pernau.at" target="_blank">klaus.mailinglists@<u></u>pernau.at</a>>> wrote:<br>
<br>
Hi Kamal!<br>
<br>
Are you familiar with SSL/TLS and certificates? With TLS the trust<br>
between TLS server and TLS client is usually via a trusted<br>
certification authority (CA). For example, if the intermediate proxy<br>
uses a certificate which is issued by CA FOOBAR-XYZ, the you have to<br>
configure Kamailio to accept certificates singed by FOOBAR-XYZ. This<br>
is done by copying the public root certificate of FOOBAR-XYZ to the<br>
Kamailio server and configure Kamailio to use the FOOBAR-XYZ<br>
certificate as trusted CA. Of course then you automatically also<br>
trust all others certificates issued by FOOBAR-XYZ.<br>
<br>
To configure the trusted CAs use:<br></div>
<a href="http://kamailio.org/docs/__modules/3.3.x/modules/tls.__html#ca_list" target="_blank">http://kamailio.org/docs/__<u></u>modules/3.3.x/modules/tls.__<u></u>html#ca_list</a><div class="im"><br>
<<a href="http://kamailio.org/docs/modules/3.3.x/modules/tls.html#ca_list" target="_blank">http://kamailio.org/docs/<u></u>modules/3.3.x/modules/tls.<u></u>html#ca_list</a>><br>
<br>
You could also disable the certificate validation with:<br></div>
<a href="http://kamailio.org/docs/__modules/3.3.x/modules/tls.__html#verify_certificate" target="_blank">http://kamailio.org/docs/__<u></u>modules/3.3.x/modules/tls.__<u></u>html#verify_certificate</a><div class="im">
<br>
<<a href="http://kamailio.org/docs/modules/3.3.x/modules/tls.html#verify_certificate" target="_blank">http://kamailio.org/docs/<u></u>modules/3.3.x/modules/tls.<u></u>html#verify_certificate</a>><br>
<br>
But of course this reduces TLS benefits to encryption-only.<br>
<br>
regards<br>
Klaus<br>
<br>
<br>
On 22.10.2012 13:53, Kamal Palei wrote:<br>
<br>
Dear All<br>
I have modified kamailio,cfg and compiled all the modules with TLS<br>
enabled, and able to bring up the kamailio proxy properly.<br>
<br>
Kamailio proxy will receive the REGISTER message from endpoints<br>
in UDP ,<br>
and want to send this REGISTER message to another intermediate<br>
proxy in<br>
TLS. For this purpose, I have added few lines in kamailio.cfg<br>
file as below.<br>
<br>
I have created the certificates, private keys as explained by README<br>
file in kamailio-3.1.5/modules/tls/ path.<br>
<br>
if(is_method("REGISTER"))<br>
{<br></div>
t_relay_to("tls:<a href="http://115.114.48.75" target="_blank">115.114.48.75</a>:<u></u>__443<br>
<<a href="http://115.114.48.75:443" target="_blank">http://115.114.48.75:443</a>><div class="im"><br>
<<a href="http://115.114.48.75:443" target="_blank">http://115.114.48.75:443</a>>");<br>
<br>
exit();<br>
}<br>
<br>
Looks like this is taking effect. When Kamailio receives REGISTER<br>
message it is trying to do handshake with intermediate proxy.<br>
I used wireshark to see the handshake messages.<br>
<br>
1. From Kamailio proxy, a TCP SYNC message is going to<br>
intermediate proxy.<br>
2. intermediate proxy sends SYNC + ACK<br>
3. Kamailio sends CLIENT HELLO<br>
4. intermediate proxy sends SERVER HELLO, CERTIFICATE and SERVER<br>
HELLO DONE<br>
5. The Kamailio sends ALERT (Level: Fatal, Description: Unknown CA)<br>
---> IS something going wrong here..............<br>
6. Then Kamailio sends FIN + ACK<br>
<br>
Can somebody please let me know why the certificate verification<br>
fails<br>
(I get this log in console).<br>
How can I put a work around to avoid certification verification<br>
failure.<br>
<br>
Best Regards<br>
kamal<br>
<br>
<br>
<br>
<br></div>
______________________________<u></u>___________________<div class="im"><br>
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users<br>
mailing list<br></div>
<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-router.org</a> <mailto:<a href="mailto:sr-users@lists.sip-router.org" target="_blank">sr-users@lists.sip-<u></u>router.org</a>><br>
<a href="http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users" target="_blank">http://lists.sip-router.org/__<u></u>cgi-bin/mailman/listinfo/sr-__<u></u>users</a> <<a href="http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users" target="_blank">http://lists.sip-router.org/<u></u>cgi-bin/mailman/listinfo/sr-<u></u>users</a>><br>
<br>
<br>
</blockquote>
</blockquote></div><br>