Hi all
Question about error handling with kamailio.
We send call to carrier and get back error 404.
In carrierfailureroute we catch up this error and send call to an internal freeswitch that plays a voiceprompt saying: "destination not available"
In accounting this calls is collected like a "normal" call - cause the internal freeswitch did the connection.
I would like to play the voiceprompt but get the error 404 and see the call in the missed calls acc table.
With 486 (busy) it is simple because we do not need an rtp response ... just fast busy.
How can we handle this for errors we need to play a voiceprompt?
What we do in failure route:
failure_route[MANAGE_FAILURE] {
sip_trace();
setflag(22);
if (t_grep_status("486")){
xlog("L_INFO", "Status 486 - busy");
t_reply("486", "Busy");
exit;
}
revert_uri();
route(NATMANAGE);
if (t_is_canceled()) {
exit;
}
xlog("L_INFO", "failure_route rd: $rd replCode: $T_reply_code trunk_in: $avp(s:trunk_in) Tree: $avp(s:tree), rU: $rU, todirection $avp(s:todirection) fu: $fu\n");
if(!cr_next_domain("$avp(s:cr_pref_carr)", "$avp(s:tree)", "$rU", "$avp(s:trunk_in)", "$T_reply_code", "$avp(s:tree)" )){
xlog("cr_next_domain failed");
exit;
}
if(!cr_route("$avp(s:cr_pref_carr)", "$avp(s:tree)", "$rU", "$rU", "call_id", "$avp(s:todirection)" )){
xlog("cr_route failed");
exit;
}
xlog("L_INFO", "failure_route rd: $rd replCode: $T_reply_code trunk_in: $avp(s:trunk_in) Tree: $avp(s:tree), rU: $rU, todirection $avp(s:todirection) fu: $fu \n");
$avp(s:trunk_out) = $avp(s:todirection);
xlog(, "L_INFO", "RELAY - FailureRoute: Outbound sent via $avp(s:trunk_out) rU $rU -------------------------------------------------------- ");
if (is_method("INVITE"))
{
setflag(FLT_ACC); # do accounting
setflag(FLT_ACCMISSED); # oro 28.10.13
}
route(ALTERHEADER);
t_on_failure("MANAGE_FAILURE");
#append_branch();
if (!t_relay()) {
xlog("failureroute t_relay failed");
exit;
}
}
I’m currently running Kamailio 4.0.3 in production and think I’m hitting bugs that looks like they are fixed in 4.0.4 but deb.kamailio.org does not have 4.0.4 yet? Any timeline when this will get released?
--
- Freddy
I’m currently running Kamailio 4.0.3 in production and think I’m hitting bugs that looks like they are fixed in 4.0.4 but deb.kamailio.org does not have 4.0.4 yet? Any timeline when this will get released?
--
- Freddy
Is Kamailio supports SIP MESSAGE request? Please let me know how to configure.
Regards,
Karthikeyan R
DISCLAIMER: This email message and all attachments are confidential and may contain information that is Privileged, Confidential or exempt from disclosure under applicable law. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email to mailadmin(a)spanservices.com and destroy the original message. Opinions, conclusions and other information in this message that do not relate to the official of SPAN, shall be understood to be nether given nor endorsed by SPAN.
Hello,
Is it possible to have the sipcapture module write the duplicated messages to multiple tables?
If not, is it possible to have the siptrace module duplicate the message to multiple Sip Capture instances?
Regards,
Grant
Hello,
I have Kamailio installed as an SBC with Freeswitch. I would like to add a SIP trunk to Kamailio. Is there any documentation on how to do this? Also, is it recommended to add trunks to Kamailio vs Freeswitch if so why?
Thanks
Hi All,
I'm trying to configure the Kamailio Server (V 4.0.3) as Registrar with OverSIP server (V 1.4.1) as a Proxy for my WebRTC client;
While calling UserB from UserA, the Kamailio is trying to find the UserB using address from Via address in UserB's REGISTER request;
I'm also using GRUU and enabled the same in configuration file.
Can someone help me what's wrong in my configuration / is Kamailio requires any additional settings to resolve this issue?
Attached Files.zip contains the following files:
OverSip-Kamailio.pcapng - Contains the packet capture between the OverSIP and Kamailio Servers.
Kamailio-Logs.txt - Shows the error message that Kamailio is trying to resolve address and it's failed.
User-records.txt - Output of "kamctl ul show".
Kamailio.cfg - Configuration file for Kamailio.
Note:
I have configured MySQL as DBENGINE, but haven't created any DB tables.
Thanks in Advance,
Karthikeyan R
DISCLAIMER: This email message and all attachments are confidential and may contain information that is Privileged, Confidential or exempt from disclosure under applicable law. If you are not the intended recipient, you are notified that any dissemination, distribution or copying of this email is strictly prohibited. If you have received this email in error, please notify us immediately by return email to mailadmin(a)spanservices.com and destroy the original message. Opinions, conclusions and other information in this message that do not relate to the official of SPAN, shall be understood to be nether given nor endorsed by SPAN.
Hi
I am trying to run the Ubuntu nightlies from
http://deb.kamailio.org/kamailiodev-nightly and loading the p-cscf config
files.
Things were working fine while I was on the 20130110 nightlies, but when I
upgraded to 20130122 I get the following errors. Any have an idea why
sem_post is undefined and how to fix this?
0(1980) ERROR: <core> [sr_module.c:572]: ERROR: load_module: could not
open module </usr/lib64/kamailio/modules/ims_registrar_pcscf.so>:
/usr/lib64/kamailio/modules/ims_registrar_pcscf.so: undefined symbol:
sem_post
0(1980) ERROR: <core> [sr_module.c:572]: ERROR: load_module: could not
open module </usr/lib64/kamailio/modules/cdp.so>:
/usr/lib64/kamailio/modules/cdp.so: undefined symbol: sem_post
0(1980) ERROR: <core> [sr_module.c:572]: ERROR: load_module: could not
open module </usr/lib64/kamailio/modules/ims_qos.so>:
/usr/lib64/kamailio/modules/ims_qos.so: undefined symbol: sem_post
Thanks
-Barry Flanagan
Hello,
I'm executing the following code for both the BYE and CANCEL in request_route:
if (is_method("BYE|CANCEL")) {
#finished
$var(finished) = $TS;
append_hf("X-Finished: $var(finished)\r\n");
}
For some reason, the X-Finished header is appended to the BYE, but not the CANCEL. The CANCEL is forwarded further.
I have the setflag(22); set, so all outbound messages are sent to the Capture server.
Does append_hf not work for CANCEL requests?
