hi
i want to run kamailio in kubernetes deployment and i want to run
this kamailio/kamailio-ci:5.2 image in to the kubernetse .. can anyone help
thank you
--
*Regards:*
Gaurav Kumar
Hi,
After a month of fight with SIP signalling I made it but now I have problem
with incoming audio from Asterisk. Kamailio and Asterisk are their own
public IPs I dont use rtpproxy.
When Asterisk sends rtp I'm able to see RTP on my router but it not going
to my computer. Maybe somebody have idea why ?
Hello,
we ran into a trouble with sharing variable into reply route...
We are going to match asterisk's uniqueid with rtpengine records like this:
route[from_asterisk]{
$var(UniqueId)=$hdr(X-UniqueId);
$var(rtp_flags) = $var(rtp_flags) + "
label={uid:$var(UniqueId),stream:outgoing} record-call=on";
rtpengine_manage($var(rtp_flags));
}
it nicely work for outgoing request, but doesn't for reply....
reply_route[from_pstn]{
rtpengine_manage("replace-origin replace-session-connection ICE=remove
RTP/AVP rtcp-mux-demux label={uid:$var(UniqueId),stream:outgoing");
}
and it doesn't work... The one possible way what we found its using $shv
instead of $var/$avp... But its unsecure way, cuz it may confus our
bussines logic...
Do you have any idea how to implement this, how we can assign $shv within
current call only?
Many thanks!
Hello,
I'm running into what I believe a weird situation when comparing <null> to
0.
I have the following lines:
xlog("L_NOTICE", "DEBUG: sel(contact.expires)=$sel(contact.expires)
- hdr(Expires)=$hdr(Expires)\n");
if ($hdr(Expires)==0 || $sel(contact.expires)==0) {
xlog("L_NOTICE", "[end] removed user location\n");
} else {
xlog("L_NOTICE", "[end] saved user location\n");
}
I registered with 3 devices, one sends expires as header, another as
contact param, and the last uses both header AND contact param.
My surprise was this:
1- Both header and contact param:
Sep 12 19:37:48 csbc01 csbc[8036]: NOTICE: {1 4 REGISTER
02c3ea6ee623916d37532188031017c9@0:0:0:0:0:0:0:0} <script>: DEBUG:
sel(contact.expires)=600 - hdr(Expires)=600
Sep 12 19:37:48 csbc01 csbc[8036]: NOTICE: {1 4 REGISTER
02c3ea6ee623916d37532188031017c9@0:0:0:0:0:0:0:0} <script>: [end]
saved user location
2- Only contact param:
Sep 12 19:36:15 csbc01 csbc[8035]: NOTICE: {1 40629 REGISTER
f2cbaa53-eabfd633(a)84.121.150.224} <script>: DEBUG:
sel(contact.expires)=600 - hdr(Expires)=<null>
Sep 12 19:36:15 csbc01 csbc[8035]: NOTICE: {1 40629 REGISTER
f2cbaa53-eabfd633(a)84.121.150.224} <script>: [end] removed user
location
2- Only header:
Sep 12 19:29:33 csbc01 csbc[8033]: NOTICE: {1 402 REGISTER
2_1804628355(a)192.168.30.31} <script>: DEBUG:
sel(contact.expires)=<null> - hdr(Expires)=3600
Sep 12 19:29:33 csbc01 csbc[8033]: NOTICE: {1 402 REGISTER
2_1804628355(a)192.168.30.31} <script>: [end] removed user location
I can workaround the header by using is_present_hf() before comparing, I
can also probably parse the $ct to see if it has some Expires in it, but I
really want to know if my understanding is incorrect and I'm doing
something wrong or if this is a bug?
Thanks!
Joel.
Hi all,
As part of a custom monitoring solution, I’m writing a simple script that sends an OPTIONS via netcat to a Kamailio server. However the server doesn’t appear to like it.
Here’s the text - options.sip:
OPTIONS sip:10.0.0.10 SIP/2.0
Via: SIP/2.0/UDP 10.0.0.20:5060
From: <sip:monitoring@10.0.0.20>
To: sip:monitoring@10.0.0.10
Call-ID: monitoring(a)10.0.0.20
CSeq: 1 OPTIONS
I’m running the following command from the 10.0.0.20 machine:
nc -u 10.0.0.10 5060 < options.sip
And I get the following error in the Kamailio logs:
ERROR: <core> [core/parser/parse_cseq.c:56]: parse_cseq(): method terminated unexpectedly
ERROR: <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq
ERROR: <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq
ERROR: <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [CSeq: 1 OPTIONS]
ERROR: <core> [core/parser/parse_cseq.c:56]: parse_cseq(): method terminated unexpectedly
ERROR: <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq
ERROR: <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq
ERROR: <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [CSeq: 1 OPTIONS]
WARNING: <core> [core/receive.c:319]: receive_msg(): parsing relevant headers failed
ERROR: <core> [core/parser/parse_cseq.c:56]: parse_cseq(): method terminated unexpectedly
ERROR: <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq
ERROR: <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq
ERROR: <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [CSeq: 1 OPTIONS]
ERROR: pv [pv_core.c:1893]: pv_get_hdr(): error parsing headers
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/parse_cseq.c:56]: parse_cseq(): method terminated unexpectedly
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [CSeq: 1 OPTIONS]
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/parse_cseq.c:56]: parse_cseq(): method terminated unexpectedly
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [CSeq: 1 OPTIONS]
ERROR: {1 <null> monitoring(a)13.236.91.139} maxfwd [mf_funcs.c:51]: is_maxfwd_present(): parsing MAX_FORWARD header failed!
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/parse_cseq.c:56]: parse_cseq(): method terminated unexpectedly
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/parse_cseq.c:92]: parse_cseq(): bad cseq
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/msg_parser.c:144]: get_hdr_field(): bad cseq
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [CSeq: 1 OPTIONS]
ERROR: {1 <null> monitoring(a)13.236.91.139} <core> [core/msg_translator.c:2361]: build_res_buf_from_sip_req(): alas, parse_headers failed
As far as I can see, the message itself is valid. It appears parse_cseq() is expecting a higher cseq, or more headers? I’ve looked at another OPTIONS message we get regularly from one of our upstream, and it’s almost identical to this one. Can anyone point me the right way here?
Thanks!
Andrew
Hi All,
We have installed Kamailio as IMS setup pcscf icscf scscf - 3 instances
running on Ubuntu..
Users alice and bob are online however unable to call.
When we check the logs the FHoSS is hunting for values in sh_subscription
table for alice / bob user.
Can you please share:
1. A sample database table values to be inserted across all tables in FHoSS
helpful for the call and
2, Maybe, if possible, some description to understand table structures/
importance of fields of FHoSS.
Thanks and Regards,
Jack.
hi
i m using kamailio 5.1, with -m 512 -M 8
it stop registering user SIP
anf in status it shows
------------------------------
● kamailio.service - LSB: Start the Kamailio SIP proxy server
Loaded: loaded (/etc/init.d/kamailio; generated)
Active: active (exited) since Sat 2019-09-07 11:05:16 UTC; 3 days ago
Docs: man:systemd-sysv-generator(8)
Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17708]: INFO: <core>
[main.c:819]: sig_usr(): signal 15 received
Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17677]: INFO: <core>
[main.c:819]: sig_usr(): signal 15 received
Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17714]: INFO: <core>
[main.c:819]: sig_usr(): signal 15 received
Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17685]: INFO: <core>
[main.c:819]: sig_usr(): signal 15 received
Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17681]: {1 1094155754 NOTIFY
TwGwmzx4wINnraJs1Gh3Kg..} INFO: <core> [main.c:819]: sig_usr(): s… received
Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17704]: INFO: <core>
[main.c:819]: sig_usr(): signal 15 received
Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17689]: INFO: <core>
[main.c:819]: sig_usr(): signal 15 received
Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17693]: INFO: <core>
[main.c:819]: sig_usr(): signal 15 received
Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17691]: INFO: <core>
[main.c:819]: sig_usr(): signal 15 received
Sep 11 06:38:36 talk /usr/local/sbin/kamailio[17674]: INFO: <core>
[core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized
Hint: Some lines were ellipsized, use -l to show in full.
---------------------------------------------------------------------
plz help
thank you
--
*Regards:*
Gaurav Kumar
Hi all,
I just installed kamailio 5.2.4 on two separate aws instances in two
separate regions. Both regions uses the same configuration template and
share the same db in AWS RDS. The issue I see is this:
- SJO location was able to launch fine without any issues.
- ASH location could not start up kamailio process due to db connection
failure:
Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8043]: ERROR: db_mysql
[km_my_con.c:139]: db_mysql_new_connection(): driver error: Too many
connections
Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8043]: ERROR: <core>
[db.c:319]: db_do_init2(): could not add connection to the pool
Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: db_mysql
[km_my_con.c:139]: db_mysql_new_connection(): driver error: Too many
connections
Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: <core>
[db.c:319]: db_do_init2(): could not add connection to the pool
Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: carrierroute
[db_carrierroute.c:141]: carrierroute_db_open(): can't connect to database.
Sep 10 21:24:13 ashmainkama51 /usr/sbin/kamailio[8045]: ERROR: <core>
[core/sr_module.c:847]: init_mod_child(): error while initializing module
carrierroute (/usr/lib/x86_64-linux-gnu/kamailio/modules/carrierroute.so)
(idx: 30 rank: 18 desc: [tcp receiver (generic) child=9])
- In ASH instance, I can manually mysql to the RDS host using the
credentials in the config file.
- I checked db user permissions and it's opened for the subnet in our ASH
location (which is also proven using manual connection).
So I don't get why one works and the other doesn't
Thoughts?
--
Andy Chen
Sr. Telephony Lead Engineer
--
*Confidentiality Notice: The information contained in this e-mail and any
attachments may be confidential. If you are not an intended recipient, you
are hereby notified that any dissemination, distribution or copying of this
e-mail is strictly prohibited. If you have received this e-mail in error,
please notify the sender and permanently delete the e-mail and any
attachments immediately. You should not retain, copy or use this e-mail or
any attachment for any purpose, nor disclose all or any part of the
contents to any other person. Thank you.*