Hi!
We recently upgraded our Kamailio 4.1 to 4.2.1. With the newer version Kamailio crashes after just running a few minutes. After some debugging it looks as though the problem is in exec_msg (which is used in our config). After disabling this 4.2.1 seem to run just fine.
Core file exists, here's the output:
(gdb) backtrace
#0 0x00000000005ebf0f in fm_extract_free (frag=0x7f053ea08d18, qm=0x7f053e88e010) at mem/f_malloc.c:206
#1 fm_malloc (qm=0x7f053e88e010, size=<optimized out>, file=file@entry=0x7f053cbedfd4 "exec: exec_hf.c", func=func@entry=0x7f053cbef378 "replace_env", line=line@entry=375) at mem/f_malloc.c:490
#2 0x00007f053cbe7953 in replace_env (list=0x7f053ea08868) at exec_hf.c:375
#3 0x00007f053cbe862e in set_env (msg=0x7f053e91d690) at exec_hf.c:547
#4 0x00007f053cbeb835 in w_exec_msg (msg=0x7f053e87c480, cmd=0x7f053ea5e168 "X֤>\005\177", foo=<optimized out>) at exec_mod.c:164
#5 0x00000000004274f7 in do_action (h=h@entry=0x7fff02e9cf90, a=a@entry=0x7f053ea5cfb8, msg=msg@entry=0x7f053e87c480) at action.c:1094
#6 0x00000000004261a9 in run_actions (h=h@entry=0x7fff02e9cf90, a=a@entry=0x7f053ea5cfb8, msg=msg@entry=0x7f053e87c480) at action.c:1583
#7 0x0000000000432980 in run_top_route (a=0x7f053ea5cfb8, msg=msg@entry=0x7f053e87c480, c=c@entry=0x0) at action.c:1669
#8 0x00007f053e610d2a in run_failure_handlers (t=t@entry=0x7f0534ecc770, rpl=0x7f053ea71040, code=486, extra_flags=extra_flags@entry=64) at t_reply.c:1051
#9 0x00007f053e612aa3 in t_should_relay_response (Trans=Trans@entry=0x7f0534ecc770, new_code=new_code@entry=486, branch=branch@entry=0, should_store=should_store@entry=0x7fff02e9d2a0, should_relay=should_relay@entry=0x7fff02e9d290,
cancel_data=cancel_data@entry=0x7fff02e9d490, reply=reply@entry=0x7f053ea71040) at t_reply.c:1406
#10 0x00007f053e616126 in relay_reply (t=t@entry=0x7f0534ecc770, p_msg=p_msg@entry=0x7f053ea71040, branch=0, msg_status=msg_status@entry=486, cancel_data=cancel_data@entry=0x7fff02e9d490, do_put_on_wait=do_put_on_wait@entry=1)
at t_reply.c:1809
#11 0x00007f053e61a9f3 in reply_received (p_msg=0x7f053ea71040) at t_reply.c:2493
#12 0x00000000004920a6 in do_forward_reply (msg=msg@entry=0x7f053ea71040, mode=mode@entry=0) at forward.c:783
#13 0x0000000000493637 in forward_reply (msg=msg@entry=0x7f053ea71040) at forward.c:885
#14 0x00000000004f5634 in receive_msg (buf=<optimized out>, len=<optimized out>, rcv_info=<optimized out>) at receive.c:275
#15 0x00000000005d929d in udp_rcv_loop () at udp_server.c:521
#16 0x00000000004a73f1 in main_loop () at main.c:1629
#17 0x0000000000425085 in main (argc=<optimized out>, argv=<optimized out>) at main.c:2561
Kind regards,/Tobias
I would like to know if there's a way to do parallel forking via lua code.
So specifically, I'd like to be able to do something like this:
seturi("sip:a@example.com");
append_branch("sip:b@example.com");
append_branch("sip:c@example.com");
append_branch("sip:d@example.com");
t_relay();
except via lua, because the list of branches is dynamic. I've tried
the following:
sr.modf("append_branch","sip:10.x.x.x")
but the error message I'm getting is:
/usr/sbin/kamailio[7437]: ERROR: app_lua [app_lua_sr.c:177]:
lua_sr_modf(): function 'append_branch' is not available
Just wondering if I "should" be able to do this.
I've been reading
http://www.kamailio.org/wiki/embeddedapi/devel/lua#srtm_package but
haven't seen any references to append_branch.
The other alternative I'm looking at is to just use lua to generate
the list of destinations and pass back a hashtable of sorts to
the cfg file. Then from there I will try to loop through the hashtable
and do the append_branch command for each entry
in the table.
If you have other suggestions, I'd appreciate it.
Thanks.
Hi,
I wish to update dialog timeout when i receive the 200ok in the on_reply
route
I try to make it with the dlg_set_timeout but it give an error "bogus
dialog..."
How can i make it?
Thanks
Hello,
I'm wondering if I can configure Kamailio to get in 3rd party REGISTER
request's body the initial REGISTER request received from user ?
Thanks in advance and best regards.
Hi All,
I am running ims servers(pcscf,scscf,icscf and hss) as part of kamailio
proxy.
And I am trying to register and unregister the end-points, with help osip
lib.
But I see the below ERROR message.
ERROR: *** cfgtrace:failure_route=[REGISTER_failure]
c=[/etc/kamailio/pcscf/kamailio.cfg] l=908 a=25 n=t_check_status
Please help me to fix the issue.
Thanks and Regards,
Anil
Hi Dears,
I have successfully configured Kamailio HA using Heartbeat and Pacemaker so
if one of the two servers should go down the other server will own the
virtual IP address and take over.
But i have two questions:
1.This model is considered to be Active / Passive redundancy so one server
will process the SIP signaling until it goes down and i'm wondering is
there is any way two achieve Active / Active redundancy and if so how the
signaling will be handled on the servers so they can be aware of the
transactions and dialogs traversing the servers ? does the signalling will
be replicated or synchronized between the servers or what ?!
2.What about the servers DB and how they should be designed in a cluster
mode ? i want to replicate all the DBs of the server to get consistent user
registration using the subscriber table for example.
Thanks in advance and Best regards.
Hello,
We are upgrading our servers to Kamailio 4.2 and we see a lot of error
messages "Failed to delete subscription from memory".
Scenario:
This happens every time there is a Notify Timeout (408) and Kamailio tries
to delete the subscription.
Consequences:
I don't know whether the delete fails because the entry did never exist,
was already deleted or because the comparison (to_tag, callid or from_tag)
is incorrect. It would be nice to at least have some details in the log
message.
I have not noticed any consequences to general functionality.
I suspect the commit (74d73953327ad7702922b27ba37c71e3283659c3) to be
responsible for this error because it introduced some extra checks on
deletion.
Does this happen to anybody else? What may be configured incorrectly on
our system?
Kind regards
*Jan **Gaida*
Ingeniero Desarrollo Software C/ Marconi 3 (PTM)
28760 Tres Cantos
Spain
jan.gaida(a)grupoamper.com | www.grupoamper.com
--
This message and any attachments are intended only for the use of the
individual to whom they are addressed and it may contain information that
is privileged or confidential. If you have received this communication by
mistake, please notify us immediately by e-mail or telephone.The storage,
recording, use or disclosure of this e-mail and its attachments by anyone
other than the intended recipient is strictly prohibited. This message has
been verified using antivirus software; however, the sender is not
responsible for any damage to hardware or software resulting from the
presence of any virus.
Este mensaje y cualquier anexo son exclusivamente para la persona a quien
van dirigidos y pueden contener información privilegiada o confidencial. Si
usted ha recibido esta comunicación por error, le agradecemos notificarlo
de inmediato por esta misma vía o por teléfono. Está prohibida su
retención, grabación, utilización o divulgación con cualquier propósito.
Este mensaje ha sido verificado con software antivirus; sin embargo, el
remitente no se hace responsable en caso de que en éste o en los archivos
adjuntos haya presencia de algún virus que pueda generar daños en los
equipos o programas del destinatario.
Greetings.
I'm trying to adopt kamailio to handle incoming calls / generate push
notifications for softphone running on Windows Phone 8.
Starting point was this publication
http://www.kamailio.org/events/2014-KamailioWorld/day2/26-Daniel-Constantin…
I adopted the script from publication a bit - now notification URI is
extracted from REGISTER messages + INVITE transactions are not
resuming when unregistering happens.
However it does not work for me yet.
I see the suspicious output in kamailio log when softphone registers
after incoming push notification.
Please ignore ERROR: level name - it is just dirty logging call, not
real problem.
Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: ERROR:
<script>: resuming trasaction [40951:63820139] dbogovych
(40951:63820139)
Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG: tm
[t_lookup.c:1635]: t_lookup_ident(): DEBUG: t_lookup_ident:
transaction found
Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG:
registrar [lookup.c:181]: lookup(): contact for [dbogovych] found by
address
Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG:
registrar [lookup.c:327]: lookup(): instance is 90211984
Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG:
registrar [lookup.c:327]: lookup(): instance is 91061218
Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG:
registrar [lookup.c:327]: lookup(): instance is 91229062
Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG:
registrar [lookup.c:327]: lookup(): instance is 90750343
Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG:
registrar [lookup.c:327]: lookup(): instance is 87612750
Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: DEBUG:
registrar [lookup.c:327]: lookup(): instance is 91841578
Dec 17 14:20:11 voipobjects /usr/local/sbin/kamailio[29652]: WARNING:
tm [t_lookup.c:1537]: t_unref(): WARNING: script writer didn't release
transaction
Can this "script writer didn't release transaction" be the problem?
Thank you :)
A very dynamic 2014 for Kamailio has reached its end! Thank you everyone
for contributing to it!
Looking forward to 2015, a lot of new features in Kamailio and new
contributors! I wish a healthy and prosperous year to all Kamailio
friends, hoping to meet many of you at Kamailio World Conference and
other events around the globe!
Happy New Year!
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Hi,
I'm trying use two instances of rtpproxy listening to two different public
IPs, to handle incoming and outgoing legs.
That means i want to implement this network topology:
SipClient--------->media from client to proxy--->rtpproxy1
Sipclient<----------media from proxy to client<---rtpproxy2
Where rtpproxy1 listening to IP1
and rtpproxy2 listening to IP2
in kamailio cfg :
modparam("rtpproxy", "rtpproxy_sock", " udp:127.0.0.1:22222 udp:
127.0.0.1:22223")
if (is_request()) {
if (!has_totag()) {
add_rr_param(";nat=yes");
}
rtpproxy_offer("IP1");
}
if (is_reply()) {
if(isbflagset(FLB_NATB)) {
fix_nated_contact();
}
rtpproxy_answer("IP2");
}
But its not working.
Thanks in advance
