sr-users

sr-users@lists.kamailio.org

23 participants
37378 discussions

503(service unavailable)
by masoud96＠mail.ru 11 Apr '24

11 Apr '24

Great everyone! It often happens to me that the service completely fails and refuses to service calls. For example, yesterday there was such a situation. I looked at the logs and at the beginning of the incident I noticed this strange entry: kamailio[283008]: WARNING: {1 14714 ACK clMGFB7OWsiT4fQp9TPvV-RlvGqv2zPa} <core> [core/tcp_main.c:1297]: find_listening_sock_info(): binding to source address 109.68.232.40:15061 failed: Address already in use [98] kamailio[283008]: WARNING: {1 14714 ACK clMGFB7OWsiT4fQp9TPvV-RlvGqv2zPa} <core> [core/tcp_main.c:1441]: tcp_do_connect(): 10.241.60.46:15061: could not find corresponding listening socket kamailio[283008]: ERROR: {1 14714 ACK clMGFB7OWsiT4fQp9TPvV-RlvGqv2zPa} <core> [core/tcp_main.c:3078]: tcpconn_1st_send(): connect 10.241.60.46:15061 failed (RST) Connection refused kamailio[283008]: ERROR: {1 14714 ACK clMGFB7OWsiT4fQp9TPvV-RlvGqv2zPa} <core> [core/tcp_main.c:3087]: tcpconn_1st_send(): 10.241.60.46:15061: connect & send for 0x7f7107e01750 (sock 39) kamailio[283008]: CRITICAL: {1 14714 ACK clMGFB7OWsiT4fQp9TPvV-RlvGqv2zPa} <core> [core/forward.h:290]: msg_send_buffer(): tcp_send failed kamailio[283008]: ERROR: {1 14714 ACK clMGFB7OWsiT4fQp9TPvV-RlvGqv2zPa} sl [sl_funcs.c:415]: sl_reply_error(): stateless error reply used: Unfortunately error on sending to next hop occurred (477/SL) And after several such entries this begins: /usr/local/sbin/kamailio[283069]: ERROR: <core> [core/tcp_main.c:4787]: tcpconn_main_timeout(): connect 31.173.85.36:10588 failed (timeout) /usr/local/sbin/kamailio[283069]: ERROR: <core> [core/tcp_main.c:4787]: tcpconn_main_timeout(): connect 95.24.163.132:48075 failed (timeout) /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668011 (state: 0) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668304 (state: 0) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668309 (state: 0) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668316 (state: 0) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668192 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668228 (state: 0) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668236 (state: 0) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668427 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668428 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668429 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668430 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668431 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668432 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668433 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668434 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668435 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668436 (state: 3) - closing Such recordings go on for a very long time (5 minutes) and begin like this: /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 20, socket 273: queue full, 286 requests queued (total handled 2421746) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 29, socket 291: queue full, 286 requests queued (total handled 2419460) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 4, socket 241: queue full, 287 requests queued (total handled 2451838) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 5, socket 243: queue full, 287 requests queued (total handled 2445182) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 18, socket 269: queue full, 287 requests queued (total handled 2422113) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 20, socket 273: queue full, 287 requests queued (total handled 2421747) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 27, socket 287: queue full, 287 requests queued (total handled 2419986) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 29, socket 291: queue full, 287 requests queued (total handled 2419461) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 30, socket 293: queue full, 287 requests queued (total handled 2419979) Also, my eyes are distracted by such records and it’s difficult to understand the logs: 1) kamailio[282798]: CRITICAL: {2 12704 INVITE 4cb232e6-9b5a-4a5b-aa0e-1ed73539039f} tm [../../core/forward.h:290]: msg_send_buffer(): tcp_send failed 2) /usr/local/sbin/kamailio[282970]: ERROR: sl [sl.c:285]: send_reply(): failed to reply stateful (tm) 3) kamailio[283053]: CRITICAL: <core> [core/tcp_read.c:267]: tcp_read_data(): error reading: Connection reset by peer (104) ([217.66.156.172]:11604 -> kamailio[283053]: CRITICAL: <core> [core/tcp_read.c:270]: tcp_read_data(): -> [109.68.232.40]:15061) kamailio[283053]: CRITICAL: <core> [core/tcp_read.c:1523]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f71215bb610 r: 0x7f71215bb738 (-1) kamailio[283007]: CRITICAL: <core> [core/tcp_read.c:267]: tcp_read_data(): error reading: Connection timed out (110) ([188.170.204.16]:52148 -> kamailio[283007]: CRITICAL: <core> [core/tcp_read.c:270]: tcp_read_data(): -> [109.68.232.40]:15061) kamailio[283007]: CRITICAL: <core> [core/tcp_read.c:1523]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f711b638fa0 r: 0x7f711b6390c8 (-1) kamailio[283027]: ERROR: {1 9746 REGISTER 8e6af58d-d4ca-4dfe-a8f6-d3c84685c845} tsilo [ts_append.c:121]: ts_append_to(): transaction [23428:1443020265] not found 4) kamailio[282820]: CRITICAL: {1 2 UPDATE 6da65a87-3224-46a1-961f-8f9ee50348cc} tm [../../core/forward.h:290]: msg_send_buffer(): tcp_send failed kamailio[282820]: WARNING: {1 2 UPDATE 6da65a87-3224-46a1-961f-8f9ee50348cc} tm [t_fwd.c:1581]: t_send_branch(): sending request on branch 0 failed kamailio[282820]: ERROR: {1 2 UPDATE 6da65a87-3224-46a1-961f-8f9ee50348cc} sl [sl_funcs.c:415]: sl_reply_error(): stateless error reply used: Unfortunately error on sending to next hop occurred (477/SL) Once the queue is full, the system stops servicing new calls and freezes. kamailio -v version: kamailio 5.7.2 (x86_64/linux) 95629c flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: 95629c OS: Debian 11, 64 cores, 125GB of DDR4 RAM; DB: MariaDB 10.5.15; udp_children: 30; tcp_children: 34; TLS: YES; async_workers: 64. Incoming calls are sent via push notifications( Federico Cabiddu method: https://www.voztovoice.org/sites/default/files/KamilioWorld2015%20-Federico…). NetBridging(for SIP and RTPEngine). ims_charging for billing (integration with our billing system using the Diameter protocol). As soon as the service starts responding with 503, it does not recover on its own, you have to restart. My server is powerful enough for the number of users of my service (what I mean is that there is no problem with resources). For example, 64 cores, 125GB of DDR4 RAM, 2TB of disk, of which 1TB SSD for the database, 10Gigabit channel, this is only a server for Kamailio for Rtpengines separate servers. Please help me figure out what causes a service failure!?

1 0

Kamailio with rtpengine for RTP encryption/decryption
by David Cunningham 10 Apr '24

10 Apr '24

Hello, We're using kamailio, with rtpengine for RTP encryption/decryption. It works fine but I would like to understand the integration better. How does rtpengine get the TLS certificates, and what crypto library does it use (openssl?). Thank you in advance, -- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

3 9

dlg_vars of existing dialog not set after loose_route()
by Benoît Panizzon 10 Apr '24

10 Apr '24

Hi Gang I have a strange issue after upgrading to 5.7 I use dlg_vars to keep some information until the end of the call to write them in a CDR. One of those variables records the timestamp of the first invite to determine how long it took from the invite to the 'connection established' if at all. The CDR is written when the BYE is being processed by the dialog module. Strangely, since updating to 5.7 (used to work with 5.5 and 5.6 I think, but I could be mistaking as other changes were made to the config) my dialog variables are null when BYE is being processed. reading the docs, I learned that that dlg_var are only polulated after loose_route() has been called. So I added some logging statement to track if the BYE in question is processed by loose_route(). Yes, it is, loose_route() returns success on the BYE in question. But when I log the content of my dlg_var after loose_route() it is still null. Any idea what the cause could be? -- Mit freundlichen Grüssen -Benoît Panizzon- @ HomeOffice und normal erreichbar -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

2 4

Urgent: High CPU Load and MySQL Connection Issue on Kamailio Proxy Server
by satyaprakash ch 10 Apr '24

10 Apr '24

Hi, We're encountering a CPU load of approximately 90% on the Kamailio proxy server. Additionally, there's an error logged indicating a lost connection to MySQL. Could this indicate a problem with the configuration file or is it related to MySQL itself? Your guidance would be appreciated. MySQL version: Ver 14.14 Distrib 5.5.47 Kamailio version: 5.5.5 Error in logs: /usr/local/sbin/kamailio[24933]: ERROR: db_mysql [km_dbase.c:122]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query (2013)

2 1

Newbie looking for advice
by Wayne Wenthin 09 Apr '24

09 Apr '24

Hi All, I'm new to Kamailio but have been running dozens of Freepbx systems for the last 10 years. We are an Education Service District and service K-12 schools. Many of these we provide dial tone to, the rest we have connections to to provide for toll avoidance and backup outbound calling when the LEC fails. Our main focus is to save schools money that can be used for education instead of infrastructure. Right now I have a single freepbx machine that is using inbound routes to send calls to the proper school district. I would like to replace this with a Kamailio server instead but can't seem to get my mind around the best way to do this. I have 119 inbound routes in my current system with 22 trunks to the other districts. This may increase in the future as we try to migrate districts off of the expensive systems to a more open source way of calling. Currently calls between districts take the route out of the system just to come right back in to be routed to a different district. I would like to avoid that if possible. I've been trying to educate myself on the best practice in this type of structure but can't seem to figure out the best way to make this work. Most of the videos and websites assume a pretty intimate knowledge of Kamailio. That and the database structure doesn't make sense to me. I would like to keep each freepbx as its own registrar as we have lots of crossover with extensions and a few of the districts have their own staff that manage that aspect of the machines. . Any suggestions would be appreciated. Please ask questions if this just looks like I'm rambling. -- Wayne Wenthin Wide Area Network Administrator | CTA@MESD 503.257.1562 Phone/Fax www.cascadetech.org

2 1

Troubleshooting acc_radius module with 5.7
by santiago.troncoso＠quobis.com 09 Apr '24

09 Apr '24

Hi community, I am preparing a setup of Kamailio with radius accounting on a docker-compose environment. When configuring the acc_radius module I had to navigate through some old doc by Daniel and inspecting the code itself. The thing is that it seems working, but not. And, yes, I already trying without docker :) Context: two containers, host newtork, to keep it simple - one with kamailio + modules (acc, acc_radius with rad_cli) + radius client configuration - another with freeradius + radius client configuration. I ensure that all data correspond and radius config is fine and spin them up. Run some radius commands to test and let's try some accounting... Executing a failed call and triggering the account flag method, I receive an opaque -1 error from the module: ``` kamailio-1 | 1(20) INFO: {1 22 INVITE yutncivdtflvzga@PT-96} <script>: Initial requests kamailio-1 | 1(20) INFO: {1 22 INVITE yutncivdtflvzga@PT-96} <script>: FLAG FLT_ACC set kamailio-1 | 1(20) NOTICE: {1 22 INVITE yutncivdtflvzga@PT-96} acc [acc.c:286]: acc_log_request(): ACC: call missed: timestamp=1709746392;method=INVITE;from_tag=wvaqi;to_tag=1a86669fc745788378faa461e7993953-78550000;call_id=yutncivdtflvzga@PT-96;code=404;reason=Not Found;src_user=1000;src_domain=kamailio-local;src_ip=172.20.0.1;dst_ouser=1001;dst_user=1001;dst_domain=kamailio-local kamailio-1 | 1(20) ERROR: {1 22 INVITE yutncivdtflvzga@PT-96} acc_radius [acc_radius_mod.c:497]: acc_radius_send_request(): Radius accounting - ERROR - result: -1 ``` Log accounting is working ok, but radius accounting not. Time for troubleshooting. I tried to enable client debugging, but the module does not respond. So I modify the source directly... tested with `radclient` , `radtest`, `radsniff`... all seems to work when trying manually... I also used an internal radcli fuction `rc_check()` and it works. Meanwhile, I was unable to make it work with the module and the radcli library. So another log output using internal functions to debug the configuration: ``` kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:312]: check_cfg(): Clave: nas-identifier, Valor: radius-wac kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:312]: check_cfg(): Clave: authserver, Valor: radius kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:312]: check_cfg(): Clave: acctserver, Valor: radius kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:306]: check_cfg(): Clave: servers, Valor: /usr/local/etc/radcli/servers - OK file found kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:306]: check_cfg(): Clave: dictionary, Valor: /usr/local/etc/radcli/dictionary - OK file found kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:300]: check_cfg(): Clave: default_realm, Valor: -- not set -- kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:312]: check_cfg(): Clave: radius_timeout, Valor: 10 kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:312]: check_cfg(): Clave: radius_retries, Valor: 3 kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:312]: check_cfg(): Clave: bindaddr, Valor: * kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:312]: check_cfg(): Clave: clientdebug, Valor: 1 kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:369]: init_acc_rad(): RC_ACCT_INIT: rc_test_config looks good kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:375]: init_acc_rad(): RC_ACCT_INIT: Config applyed ok ``` The configuration seems ok, accepted by the library and seems to be applied properly, but when trying to parse its values... all seems like rubish... ``` kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:401]: init_acc_rad(): RC_ACCT_INIT: Name: P�y:^ kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:402]: init_acc_rad(): RC_ACCT_INIT: Max 1 kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:403]: init_acc_rad(): RC_ACCT_INIT: Port: 125489528 kamailio-1 | 0(18) INFO: acc_radius [acc_radius_mod.c:404]: init_acc_rad(): RC_ACCT_INIT: Secret: kamailio-1 | 0(18) ERROR: acc_radius [acc_radius_mod.c:410]: init_acc_rad(): RC_CLIENTDEBUG: No clientdebug specified ``` I'm using `libradcli4 1.2.11-1+b2` for running on the container and `libradcli-dev 1.2.11-1build1` for compiling. Open to hear ideas, somebody using it actively on latest 5.7 release? Some updated documentation flying around? I was thinking to open a GitHub issue to handle the documentation issue. Thanks in advance!

1 1

Updating $fn malforms packet.
by James Lipski 09 Apr '24

09 Apr '24

Hello, I have remote users registering/ routing calls through my server. When calls do pass through the server, the server updates the from name, to uri and from uri via updating the pseudovariables $fn, $tu, and $fu respectively. While this is has been working, I do occasionally see calls failing to process as the remote gateway fails the call with a "400 Bad From header". Inspecting the A-leg INVITE and the B-leg INVITE after updating the pseudovariables, I see the following: A-leg INVITE: INVITE sip:15551112222@example.com SIP/2.0 Via: SIP/2.0/UDP 79..xx.xx.xx:61379;rport;branch=z9hG4bKPj2b8935f4460447538d0176dcfb5c74a1 Max-Forwards: 70 From: sip:12223334444@example.com;tag=dff3c585a6154f23898e1121918f1752 To: sip:15551112222@example.com Contact: <sip:12223334444@79..xx.xx.xx:61379;ob> Call-ID: d793331e066f47bdafc0ad957cb506cc CSeq: 30770 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 Proxy-Authorization: Digest username="12223334444", realm="example.com", nonce="ZhUw02YVL6cdi51KMymTxGpzCZCZhd8G", [uri="sip:15551112222@example.com](mailto:uri=)", response="3a25b4ea0b1154e31caee1184a92f12b" Content-Type: application/sdp Content-Length: 627 v=0 o=- 3921660487 3921660487 IN IP4 79..xx.xx.xx s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 4006 RTP/AVP 96 97 98 99 3 0 8 9 120 121 122 c=IN IP4 79..xx.xx.xx b=TIAS:64000 a=rtcp:4007 IN IP4 79..xx.xx.xx a=sendrecv a=rtpmap:96 speex/16000 a=rtpmap:97 speex/8000 a=rtpmap:98 speex/32000 a=rtpmap:99 iLBC/8000 a=fmtp:99 mode=30 a=rtpmap:3 GSM/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:120 telephone-event/16000 a=fmtp:120 0-16 a=rtpmap:121 telephone-event/8000 a=fmtp:121 0-16 a=rtpmap:122 telephone-event/32000 a=fmtp:122 0-16 a=ssrc:63772004 cname:3ff849bd611036a7 ---------------------------------- B-leg INVITE: INVITE sip:15551112222@togateway.com SIP/2.0 Record-Route: <sip:10.64.54.207;lr;ftag=dff3c585a6154f23898e1121918f1752;did=e21.65c1> Via: SIP/2.0/UDP 10.64.54.207:5060;branch=z9hG4bK919d.5ca83e030c0879093169546cd80591a6.0 Via: SIP/2.0/UDP 79..xx.xx.xx:61379;received=79..xx.xx.xx;rport=61379;branch=z9hG4bKPj2b8935f4460447538d0176dcfb5c74a1 Max-Forwards: 15 From: sip:12125557777@example.com"Updated Name" ;tag=dff3c585a6154f23898e1121918f1752 To: sip:15551112222@togateway.com Contact: <sip:12125557777@79..xx.xx.xx:61379;ob> Call-ID: d793331e066f47bdafc0ad957cb506cc CSeq: 30770 INVITE Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS Supported: replaces, 100rel, timer, norefersub Session-Expires: 1800 Min-SE: 90 Content-Type: application/sdp Content-Length: 609 v=0 o=- 3921660487 3921660487 IN IP4 10.64.54.207 s=pjmedia b=AS:84 t=0 0 a=X-nat:0 m=audio 18400 RTP/AVP 96 97 98 99 3 0 8 9 120 121 122 c=IN IP4 10.64.54.207 b=TIAS:64000 a=ssrc:63772004 cname:3ff849bd611036a7 a=rtpmap:96 speex/16000 a=rtpmap:97 speex/8000 a=rtpmap:98 speex/32000 a=rtpmap:99 iLBC/8000 a=fmtp:99 mode=30 a=rtpmap:3 GSM/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=rtpmap:9 G722/8000 a=rtpmap:120 telephone-event/16000 a=fmtp:120 0-16 a=rtpmap:121 telephone-event/8000 a=fmtp:121 0-16 a=rtpmap:122 telephone-event/32000 a=fmtp:122 0-16 a=sendrecv a=rtcp:18401 Note that I've updated the following on the B-leg: $fn = "Updated Name" // originally nothing $fu = sip:12125557777@example.com // originally sip:12223334444@example.com $tu = sip:15551112222@togateway.com // originally sip:15551112222@example.com While the from uri, and to uri do get updated, the from name is injected in the wrong place of the from header. This only seems to happen when the A-leg is missing the "<" and ">" characters enclosing the from headers. Should I not be updating the pseudo variables in this manner to update the from name, to uri and from uri; is there another way to update these attributes of the header without malforming it? Thank you.

2 1

making HTTP requests in stateless redirects
by Sergio Charrua 08 Apr '24

08 Apr '24

Hi all! For testing purposes, while I am waiting for the ST/SH REST API to be available from other teams, I developed a small python REST API that returns a mockup of a JSON object with some of the required values. The kamailio script, completely stateless as I do not need to keep track of the sessions, iterates through one of the JSON branches and adds the destination URLs to the Contact header and replies a SIP 300 Multiple Choices. This works: the UAC does receive the SIP response with the Contacts , but it also receives a SIP 500 error message right after, and I can't figure out why. And i bet this is simple to solve.... Any clue? I'm aware I'm not processing ACK messages, but the sl_send_reply 403 should do the trick right? ... at least while testing.... Also, as this is a stateless script, is there another way of using async http or making http requests to a REST API without having to use TM Module? Thanks in advance. The kamailio script is has follows: #!KAMAILIO > /* add API http timeout */ > #!define HTTP_API_TIMEOUT 5000 > #!define HTTP_API_ROUTING_ENDPOINT "http://some_python_rest_api/get_route" > ### LOG Levels: 3=DBG, 2=INFO, 1=NOTICE, 0=WARN, -1=ERR > debug=4 > log_stderror=no > memdbg=5 > memlog=5 > log_facility=LOG_LOCAL0 > log_prefix="{$mt $hdr(CSeq) $ci} " > /* number of SIP routing processes */ > children=2 > /* set paths to location of modules */ > loadmodule "tm.so" > loadmodule "jsonrpcs.so" > loadmodule "kex.so" > loadmodule "corex.so" > loadmodule "sl.so" > loadmodule "db_mysql.so" > loadmodule "rr.so" > loadmodule "pv.so" > loadmodule "maxfwd.so" > loadmodule "ipops.so" > loadmodule "textops.so" > loadmodule "siputils.so" > loadmodule "xlog.so" > loadmodule "sanity.so" > loadmodule "ctl.so" > loadmodule "cfg_rpc.so" > loadmodule "uac.so" > loadmodule "counters.so" > loadmodule "http_async_client.so" > loadmodule "jansson.so" > loadmodule "usrloc.so" > /* listen addresses */ > listen=udp:10.20.0.2:5060 > listen=udp:10.20.0.2:5062 > advertised_address="10.20.0.2"; > # ----- http_async_client params ----- > modparam("http_async_client", "workers", HTTP_ASYNC_CLIENT_WORKERS) > modparam("http_async_client", "connection_timeout", 2000) > request_route { > #route(HANDLE_DMQ); > route(HANDLE_OPTIONS); > if (is_method("INVITE")) > { > xlog("L_INFO","MAIN - calling TO_CARRIER"); > route(TO_CARRIER); > exit; > } > else{ > sl_send_reply("401","UNAUTHORIZED"); > } > } > route[TO_CARRIER]{ > xlog("L_INFO","TO_CARRIER - calling RELAY_API"); > route(RELAY_API); #Route relay > xlog("L_INFO","TO_CARRIER - return"); > return; > } > # Relay request using the API (response) > route[RELAY_API_RESPONSE] { > xlog("L_INFO","RELAY_API_RESPONSE - got response from REST API"); > if ($http_ok==1 && $http_rs==200) > { > xlog("L_INFO","RELAY_API_RESPONSE - HTTP RESPONSE: > $http_rb\n"); > if (jansson_get("json", $http_rb, "$var(json)")) { > xlog("L_INFO","RELAY_API_RESPONSE - JSON = > $var(json)"); > $var(count) = 0; > jansson_array_size("routes", $var(json), > "$var(size)"); > xlog("L_INFO","RELAY_API_RESPONSE - > jansson_array_size"); > >> >> while ( $var(count) < $var(size) ){ > > >> jansson_get("routes[$var(count)].headers.to.uri", $var(rtjson), "$var(v)"); > > xlog("L_INFO","JSON - routes[$var(count)] >> - $var(v)"); > > #$(avp(mycontacts)[$var(count)]) = >> $avp(mycontacts) + $var(v) + "\r\n"; > > $avp(mycontacts) = $avp(mycontacts) + >> $var(v) + ";"; > > > *append_to_reply("Contact: <" + $var(v) >> +">"+ "\r\n"); /* ---- IS THERE A BETTER ?? ..... */* > > > $var(count) = $var(count) + 1; > > } > > > xlog("L_INFO","RELAY_API_RESPONSE - RELAY"); > xlog("L_INFO","MAIN - calling REPLY_302"); > route(REPLY_302); > return; > } > } > send_reply(500, "API Not Available - http response = $http_rs > $http_ok"); > exit; > } > route[RELAY_API] { xlog("L_INFO","RELAY_API - from_ip $si:$sp from_number $fU > to_number $ru"); > $http_req(all) = $null; > $http_req(suspend) = 1; > $http_req(timeout) = HTTP_API_TIMEOUT; > $http_req(method) = "POST"; > $http_req(hdr) = "Content-Type: application/json"; > jansson_set("string","from_ip",$si, "$var(http_routing_query)"); > jansson_set("string","from_port",$sp, "$var(http_routing_query)"); > jansson_set("string","from_number",$fU, > "$var(http_routing_query)"); > jansson_set("string","to_number",$ru , "$var(http_routing_query)"); > > xlog("L_INFO","RELAY_API - API ASYNC ROUTING REQUEST: > $var(http_routing_query)\n"); > $http_req(body) = $var(http_routing_query); > t_newtran(); > http_async_query(HTTP_API_ROUTING_ENDPOINT, "RELAY_API_RESPONSE"); > xlog("L_INFO","RELAY_API - Waiting for Response"); > } > route[REPLY_302] { > # Sends a 300 Multiple Choices back to the proxy that requested the > routing lookup > xlog("L_INFO","REPLY_302 - send reply"); > sl_send_reply("300", "Multiple Choices"); > xlog("L_INFO","REPLY_302 - exit"); > exit; > } > route[HANDLE_OPTIONS]{ > if(is_method("OPTIONS")) > { > sl_send_reply(200, "OK"); > exit; > } > if ($fU=="ping") > { > sl_send_reply("200","OK"); > exit; > } > } SNGrep output: 1 - INVITE from UAC to Kamailio INVITE sip:918228990@10.20.0.2 SIP/2.0 > Via: SIP/2.0/UDP 10.20.0.1:5063;branch=z9hG4bK58aa83f4 > Max-Forwards: 70 > From: "Anonymous" <sip:anonymous@anonymous.invalid:5063>;tag=as192b8891 > To: <sip:918228990@10.20.0.2> > Contact: <sip:anonymous@10.20.0.1:5063> > Call-ID: 531668b959674f9f667f1c923d1d6c94@10.20.0.1:5063 > CSeq: 102 INVITE > User-Agent: SIPp > Date: Mon, 08 Apr 2024 15:09:51 GMT > Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, > PUBLISH, MESSAGE > Supported: replaces, timer > Content-Type: application/sdp > Content-Length: 270 > v=0 > o=root 2021555890 2021555890 IN IP4 10.20.0.1 > s=SIPp > c=IN IP4 10.20.0.1 > t=0 0 > m=audio 18422 RTP/AVP 8 0 101 > a=rtpmap:8 PCMA/8000 > a=rtpmap:0 PCMU/8000 > a=rtpmap:101 telephone-event/8000 > a=fmtp:101 0-16 > a=ptime:20 > a=maxptime:150 > a=sendrecv 2 - Reply from Kamailio to UAC SIP/2.0 100 trying -- your call is important to us > Via: SIP/2.0/UDP 10.20.0.1:5063;branch=z9hG4bK58aa83f4 > From: "Anonymous" <sip:anonymous@anonymous.invalid:5063>;tag=as192b8891 > To: <sip:918228990@10.20.0.2> > Call-ID: 531668b959674f9f667f1c923d1d6c94@10.20.0.1:5063 > CSeq: 102 INVITE > Server: kamailio (5.7.4 (x86_64/linux)) > Content-Length: 0 3 - SIP 300 Multiple Choices from Kamailio to UAC SIP/2.0 300 Multiple Choices > Via: SIP/2.0/UDP 10.20.0.1:5063;branch=z9hG4bK58aa83f4 > From: "Anonymous" <sip:anonymous@anonymous.invalid:5063>;tag=as192b8891 > To: <sip:918228990@10.20.0.2 > >;tag=57c593265e21c2b70aea50cb414df9cd.32679ccd > Call-ID: 531668b959674f9f667f1c923d1d6c94@10.20.0.1:5063 > CSeq: 102 INVITE > Contact: <sip:sip:918228990@10.20.0.2@sip.domain.io> > Contact: <sip:+351sip:918228990@10.20.0.2@10.20.0.3> > Server: kamailio (5.7.4 (x86_64/linux)) > Content-Length: 0 4 - SIP 500 from Kamailio to UAC SIP/2.0 500 I'm terribly sorry, server error occurred (1/TM) > Via: SIP/2.0/UDP 10.20.0.1:5063;branch=z9hG4bK58aa83f4 > From: "Anonymous" <sip:anonymous@anonymous.invalid:5063>;tag=as192b8891 > To: <sip:918228990@10.20.0.2 > >;tag=4eb2322b7d2b68e6fc3168f503344c21-32679ccd > Call-ID: 531668b959674f9f667f1c923d1d6c94@10.20.0.1:5063 > CSeq: 102 INVITE > Server: kamailio (5.7.4 (x86_64/linux)) > Content-Length: 0 5 - ACK from UAC to Kamailio ACK sip:918228990@10.20.0.2 SIP/2.0 > Via: SIP/2.0/UDP 10.20.0.1:5063;branch=z9hG4bK58aa83f4 > Max-Forwards: 70 > From: "Anonymous" <sip:anonymous@anonymous.invalid:5063>;tag=as192b8891 > To: <sip:918228990@10.20.0.2 > >;tag=57c593265e21c2b70aea50cb414df9cd.32679ccd > Contact: <sip:anonymous@10.20.0.1:5063> > Call-ID: 531668b959674f9f667f1c923d1d6c94@10.20.0.1:5063 > CSeq: 102 ACK > User-Agent: SIPp > Content-Length: 0 and continues with ACK and repeating SIP 500 above.... *Sérgio Charrua* .

4 6

Kamailio Admin Book email
by sadik.oualla.mohamed＠gmail.com 08 Apr '24

08 Apr '24

Hello, Last week, I submitted a request on the Asipto website to purchase the Kamailio Admin Book and received an automatic confirmation email. However, I have not received any further instructions on how to complete the purchase. I replied to the automatic email to follow up, but still, there has been no response. I need to get the book as soon as possible. Please note, I am writing from a different email address than the one I used to make the request on Asipto's site. If there are any issues with their contact email, or if further verification is needed, please let me know how to proceed securely without sharing personal details publicly on this list. Regards, Mohamed.

2 2

customizing the ds_ping_interval dispatcher parameter for destination
by Giuseppe Pandolfi 08 Apr '24

08 Apr '24

Hi, I have one question about dispatcher module in kamailio V.5.3.1. Why the ds_ping_interval parameter is only global value? Is it possible introduce the customization value for single destination? Customization from destination is already possible for ds_ping_from parameter using special attributes in destination list file or db table, is it possible introduce the same management for ds_ping_interval? Thanks, Giuseppe ________________________________ NOTA BENE: Le informazioni contenute nel presente messaggio, compresi gli eventuali allegati, sono strettamente confidenziali ed indirizzate unicamente al destinatario indicato. Qualora non foste il destinatario Vi invitiamo a cancellare il messaggio, ed ogni eventuale documento allegato, non divulgare il contenuto a terze persone ed a volerci avvisare a mezzo posta elettronica. Grazie. A TLC S.r.l. tratta i vostri dati personali nel rispetto della normativa vigente in materia di Privacy (D.Lgs.196/2003 modificato dal D.Lgs.101/2018 e GDPR Regolamento UE n.679/2016). Per consultare l’Informativa completa la invitiamo a visitare il nostro sito web “www.aethra.com<http://www.aethra.com/>” PLEASE NOTE: This message and any attachments are confidential and may contain privileged information. If you are not the intended recipient, you are kindly requested to cancel it, not to disclose the contents to any other person and to notify the sender immediately by return e-mail. Thanks. A TLC S.r.l. collects your personal data in compliance with applicable data protection laws (D.Lgs. 196/2003 amended by Legislative Decree 101/018 and GDPR EU Regulation n. 679/2016). Please visit our website ”www.aethra.com<http://www.aethra.com>” to consult the complete Policy.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users