sr-users February 2021

sr-users@lists.kamailio.org

56 participants
78 discussions

Cockroachdb and kamailio 5.4
by Jonathan Hunter 17 Feb '21

17 Feb '21

Hi Guys, Hope all are well? We are looking to implement kamailio with cockroachdb due to the advantages it gives us in terms of postgres management and clustering. I can see from a previous string http://sip-router.1086192.n5.nabble.com/CockroachDB-and-Kamailio-td189233.h… that someone has attempted this and even created their own branch. Has any further work been done on this, and if so has anyone got any advice/tips relating to it? As I am nervous about potentially using a branch and not a general release of kamailio moving forwards. I appreciate you cant support all database types but I would just be interested to hear people’s thoughts on the topic. Many thanks! Jon Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10

2 2

pipelimit with a kamailio cluster
by Daniel Donoghue 17 Feb '21

17 Feb '21

Hello, I have 2 stateful kamailio servers that receive incoming requests, load balanced across the 2 servers by our carrier trunk partners (outside of our control). I am looking at putting certain invites from these trunks into pipelimit to rate limit under some conditions but I have some questions: 1. How will pipelimit establish rates when requests can come in to either of my servers? 2. If pipelimit decides it is time to limit the requests, will both servers respect that limit? 3. does pipelimit rely on a db or can it use dmq, redis or other methods for cross-server communication? 4. Is there a maximum number of pipes that can be defined? Hope somebody can help me answer these questions. With every blessing, — Daniel Donoghue

3 4

haproxy and set_advertised_address()
by Sergey Safarov 16 Feb '21

16 Feb '21

haproxy sed dst_ip address from haproxy protocol https://github.com/kamailio/kamailio/blob/master/src/core/tcp_main.c#L987-L… How I can use this value inside set_advertised_address() function? Like set_advertised_address(dst_ip)

2 2

http_client/http_connect in request_route: INFO: <core> [main.c:857]: sig_usr(): signal 13 received
by Anthony Joseph Messina 16 Feb '21

16 Feb '21

With the following config # ----- http_client params ----- modparam("http_client", "httpredirect", 0) modparam("http_client", "connection_timeout", 2) modparam("http_client", "keep_connections", 1) modparam("http_client", "query_result", 0) modparam("http_client", "httpcon", "api=>https://api.example.com"); and after calling the following from request_route, $xavu(http=>rs)=http_connect("api", "/kamailio/message", "application/json", "$var(message_api)", "$xavu(http=>rb)"); if($xavu(http=>rs)==200) { jansson_get("result.code", $xavu(http=>rb), "$xavu(http=>code)"); jansson_get("result.message", $xavu(http=>rb), "$xavu(http=>message)"); sd_journal_print("LOG_DEBUG", "[$cfg(route)] Result: $xavu(http=>code), $xavu(http=>message)"); sl_send_reply("202", "Accepted"); exit; } I see the following in the log: INFO: <core> [main.c:857]: sig_usr(): signal 13 received It doesn't seem to have any negative effect, but I am wondering if it's something I should look into. If so, any pointers on where/how to begin? -- Anthony - https://messinet.com F9B6 560E 68EA 037D 8C3D D1C9 FF31 3BDB D9D8 99B6

1 0

Advice on handling SIP trunk to a Perimeta SBC
by Björn Bylander 16 Feb '21

16 Feb '21

Hi, So I’m tasked with setting up a SIP trunk to a Perimeta SBC (https://www.metaswitch.com/products/perimeta-sbc). Apparently, > Perimeta hides the topology of networks by rewriting or removing topology-sensitive information from SIP messages. By default, your Session Controller will make the following changes to SIP messages. > > The Session Controller generates new dialog identifiers (call-IDs, From tags and To tags) for each side of the call, so that it does not expose information about your core network to your access networks. > The Session Controller strips Record-Route and Route information from the message. > The Session Controller rewrites Contact and Via headers so that the source IP address is replaced with the local address of the outbound adjacency. > The Session Controller replaces the IP addresses in c= lines in SDP with the addresses it has allocated for media forwarding. For more information on this, see Media addresses and gates. My problem is this: When the Perimeta SBC sends its first INVITE (I can't say anything about any succeeding INVITEs yet) it's added a Record-Route header with the "lr" parameter included which, as far as I can see makes Kamailio think it should use loose routing which is all well I think. But when the SBC sends an ACK for the "200 OK" from the Kamailio side it doesn't include any Route headers and I think that makes it hard for Kamailio (at least with the standard script which is basically what I'm using) to know where to relay the ACK, at least it makes the t_check_trans() call in WITHINDLG after 'is_method("ACK")' return false which makes the script ignore the ACK. Any thoughts or suggestions on how to handle this? Thanks in advance, Björn Bylander

2 1

Usage of ldap/db2_ldap
by DEV 16 Feb '21

16 Feb '21

Hi! I'm trying to use the ldap / db2_ldap module in kamailio but I'm stuck because the docs seem to either be outdated or me being on the wrong track. >From what I understand, I need a single ldap.conf but there are two example files with different syntax: 1) https://github.com/kamailio/kamailio/blob/master/src/modules/db2_ldap/ldap.… 2) https://github.com/kamailio/kamailio/blob/master/src/modules/ldap/etc/ldap.… I'm already using ldap realtime for asterisk and want to switch kamailio to use the same objects by using this schema: https://github.com/kamailio/kamailio/blob/master/src/modules/db2_ldap/ser.s… When using syntax from (1) I receive this error: ERROR: ldap [ldap_mod.c:198]: mod_init(): no section found in config_file [/etc/kamailio/ldap.cfg] I double-checked my conf and it matches (1). When using (2), I got an error, telling me I left some tables unconfigured (even when mixing both syntax). What is the correct syntax to use ldap as my auth module and replace mysql auth tables? Thank you. Kind regards Kevin

3 5

Runnning kamailio (docker) with remote connection with MYSQL (docker) fails on start/restart due to socket or database connection
by Nuñez, Mario 16 Feb '21

16 Feb '21

Hi, I am running docker with this: https://hub.docker.com/layers/kamailio/kamailio/5.4.3-trusty/images/sha256-… and https://hub.docker.com/layers/mysql/library/mysql/8.0.23/images/sha256-8708… I made some configurations in Kamailio container: /etc/default/kamailio RUN_KAMAILIO=yes USER=kamailio GROUP=kamailio CFGFILE=/etc/kamailio/kamailio.cfg DUMP_CORE=yes /etc/kamailio/kamailio.cfg #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB /etc/kamailio/kamctlrc SIP_DOMAIN=kamailio.org DBENGINE=MYSQL DBHOST=172.19.0.3 DBPORT=3306 DBNAME=kamailio DBRWUSER="kamailio" DBRWPW="kamailiorw" DBROUSER="kamailioro" DBROPW="kamailioro" DBACCESSHOST=172.19.0.5 DBROOTUSER="root" DBROOTPW="whatever" CHARSET="latin1" USERCOL="user" Then I run creation of database: /usr/sbin/kamdbctl create All was ok so I can see in MYSQL database: +------------------+------------+-----------------------+ | user | host | plugin | +------------------+------------+-----------------------+ | root | % | mysql_native_password | | kamailio | 172.19.0.3 | mysql_native_password | | kamailioro | 172.19.0.3 | mysql_native_password | | kamailio | 172.19.0.5 | mysql_native_password | | kamailioro | 172.19.0.5 | mysql_native_password | | kamailio | localhost | mysql_native_password | | kamailioro | localhost | mysql_native_password | | mysql.infoschema | localhost | caching_sha2_password | | mysql.session | localhost | caching_sha2_password | | mysql.sys | localhost | caching_sha2_password | | root | localhost | mysql_native_password | +------------------+------------+-----------------------+ At this point, if I try to restart kamailio i get an error and container will never go up again, so I had to delete it and restart the whole installation and configuration process. Log details are: ==========================================ON RESTART KAMAILIO FROM CONTAINER CONSOLE: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.4:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.4:5060 Aliases: tcp: mykamailio:5060 tcp: localhost:5060 udp: mykamailio:5060 udp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1) INFO: <core> [main.c:2834]: main(): processes (at least): 33 - shm size: 67108864 - pkg size: 8388608 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 21(28) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/28 23(30) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 0(1) ALERT: <core> [main.c:774]: handle_sigs(): child process 205 exited normally, status=255 0(1) INFO: <core> [main.c:802]: handle_sigs(): terminating due to SIGCHLD 2(9) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 1(8) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 3(10) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 4(11) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 6(13) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 5(12) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 7(14) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 10(17) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 12(19) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 14(21) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 29(36) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 24(31) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 28(35) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 15(22) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 19(26) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 13(20) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 17(24) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 8(15) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 23(30) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 22(29) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 21(28) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 26(33) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 20(27) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 31(38) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 32(39) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 9(16) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 30(37) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 11(18) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 16(23) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 27(34) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 18(25) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 25(32) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 0(1) ERROR: ctl [ctl.c:390]: mod_destroy(): ERROR: ctl: could not delete unix socket /var/run/kamailio//kamailio_ctl: No such file or directory (2) 0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ==========================================SO CONTAINER WAS DOWN, AND THEN IF I TRY TO START CONTAINER AGAIN: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.4:5060 udp: 172.19.0.5:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.4:5060 tcp: 172.19.0.5:5060 Aliases: tcp: mykamailio:5060 tcp: localhost:5060 udp: mykamailio:5060 udp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1) INFO: auth [auth_mod.c:346]: mod_init(): qop set, but nonce-count (nonce_count) support disabled 0(1) INFO: <core> [main.c:2834]: main(): processes (at least): 41 - shm size: 67108864 - pkg size: 8388608 0(1) ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) 0(1) ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool 0(1) ERROR: usrloc [dlist.c:852]: register_udomain(): failed to open database connection 0(1) ERROR: registrar [registrar.c:711]: domain_fixup(): failed to register domain 0(1) ERROR: <core> [core/route.c:1167]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:698 0(1) ERROR: <core> [core/rvalue.c:3869]: fix_rval_expr(): failure in cfg at line: 698 col: 22 0(1) ERROR: <core> [core/rvalue.c:3869]: fix_rval_expr(): failure in cfg at line: 698 col: 22 0(1) ERROR: <core> [core/route.c:1167]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:701 error -1 while trying to fix configuration 0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ======================================================SO NO WAY TO GET IT UP. Any idea on what could be the problem? I tried giving permissions to some folders in Kamailio docker container: chown kamailio:kamailio /usr/sbin/kam* chmod 755 /usr/sbin/kam* chown -R kamailio:kamailio /etc/kamailio chmod -R 755 /etc/kamailio chown -R root:kamailio /var/run chmod -R 755 /var/run chown -R kamailio:kamailio /run/kamailio chown -R 755 /run/kamailio But had no effect... and I do not know if there is any misconfiguration out there. Indeed I tried to configure it to use remote Postgresql and failed, so I came back to MYSQL as it looks somekind of default config. To Kamailio. Thank you in advance. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional. Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes. Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.

1 0

Runnning kamailio (docker) with remote connection with MYSQL (docker) fails on start/restart due to socket or database connection
by Nuñez, Mario 16 Feb '21

16 Feb '21

Hi, I am running docker with this: https://hub.docker.com/layers/kamailio/kamailio/5.4.3-trusty/images/sha256-… and https://hub.docker.com/layers/mysql/library/mysql/8.0.23/images/sha256-8708… I made some configurations in Kamailio container: /etc/default/kamailio RUN_KAMAILIO=yes USER=kamailio GROUP=kamailio CFGFILE=/etc/kamailio/kamailio.cfg DUMP_CORE=yes /etc/kamailio/kamailio.cfg #!define WITH_MYSQL #!define WITH_AUTH #!define WITH_USRLOCDB /etc/kamailio/kamctlrc SIP_DOMAIN=kamailio.org DBENGINE=MYSQL DBHOST=172.19.0.3 DBPORT=3306 DBNAME=kamailio DBRWUSER="kamailio" DBRWPW="kamailiorw" DBROUSER="kamailioro" DBROPW="kamailioro" DBACCESSHOST=172.19.0.5 DBROOTUSER="root" DBROOTPW="whatever" CHARSET="latin1" USERCOL="user" Then I run creation of database: /usr/sbin/kamdbctl create All was ok so I can see in MYSQL database: +------------------+------------+-----------------------+ | user | host | plugin | +------------------+------------+-----------------------+ | root | % | mysql_native_password | | kamailio | 172.19.0.3 | mysql_native_password | | kamailioro | 172.19.0.3 | mysql_native_password | | kamailio | 172.19.0.5 | mysql_native_password | | kamailioro | 172.19.0.5 | mysql_native_password | | kamailio | localhost | mysql_native_password | | kamailioro | localhost | mysql_native_password | | mysql.infoschema | localhost | caching_sha2_password | | mysql.session | localhost | caching_sha2_password | | mysql.sys | localhost | caching_sha2_password | | root | localhost | mysql_native_password | +------------------+------------+-----------------------+ At this point, if I try to restart kamailio i get an error and container will never go up again, so I had to delete it and restart the whole installation and configuration process. Log details are: ==========================================ON RESTART KAMAILIO FROM CONTAINER CONSOLE: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.4:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.4:5060 Aliases: tcp: mykamailio:5060 tcp: localhost:5060 udp: mykamailio:5060 udp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1) INFO: <core> [main.c:2834]: main(): processes (at least): 33 - shm size: 67108864 - pkg size: 8388608 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 0(1) INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 0(1) INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 21(28) INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/28 23(30) INFO: ctl [io_listener.c:214]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) 0(1) ALERT: <core> [main.c:774]: handle_sigs(): child process 205 exited normally, status=255 0(1) INFO: <core> [main.c:802]: handle_sigs(): terminating due to SIGCHLD 2(9) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 1(8) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 3(10) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 4(11) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 6(13) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 5(12) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 7(14) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 10(17) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 12(19) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 14(21) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 29(36) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 24(31) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 28(35) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 15(22) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 19(26) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 13(20) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 17(24) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 8(15) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 23(30) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 22(29) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 21(28) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 26(33) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 20(27) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 31(38) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 32(39) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 9(16) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 30(37) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 11(18) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 16(23) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 27(34) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 18(25) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 25(32) INFO: <core> [main.c:857]: sig_usr(): signal 15 received 0(1) ERROR: ctl [ctl.c:390]: mod_destroy(): ERROR: ctl: could not delete unix socket /var/run/kamailio//kamailio_ctl: No such file or directory (2) 0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ==========================================SO CONTAINER WAS DOWN, AND THEN IF I TRY TO START CONTAINER AGAIN: Listening on udp: 127.0.0.1:5060 udp: 172.17.0.4:5060 udp: 172.19.0.5:5060 tcp: 127.0.0.1:5060 tcp: 172.17.0.4:5060 tcp: 172.19.0.5:5060 Aliases: tcp: mykamailio:5060 tcp: localhost:5060 udp: mykamailio:5060 udp: localhost:5060 0(1) INFO: <core> [core/tcp_main.c:4984]: init_tcp(): using epoll_lt as the io watch method (auto detected) 0(1) INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded 0(1) INFO: rr [rr_mod.c:185]: mod_init(): outbound module not available 0(1) INFO: auth [auth_mod.c:346]: mod_init(): qop set, but nonce-count (nonce_count) support disabled 0(1) INFO: <core> [main.c:2834]: main(): processes (at least): 41 - shm size: 67108864 - pkg size: 8388608 0(1) ERROR: db_mysql [km_my_con.c:163]: db_mysql_new_connection(): driver error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) 0(1) ERROR: <core> [db.c:319]: db_do_init2(): could not add connection to the pool 0(1) ERROR: usrloc [dlist.c:852]: register_udomain(): failed to open database connection 0(1) ERROR: registrar [registrar.c:711]: domain_fixup(): failed to register domain 0(1) ERROR: <core> [core/route.c:1167]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:698 0(1) ERROR: <core> [core/rvalue.c:3869]: fix_rval_expr(): failure in cfg at line: 698 col: 22 0(1) ERROR: <core> [core/rvalue.c:3869]: fix_rval_expr(): failure in cfg at line: 698 col: 22 0(1) ERROR: <core> [core/route.c:1167]: fix_actions(): fixing failed (code=-1) at cfg:/etc/kamailio/kamailio.cfg:701 error -1 while trying to fix configuration 0(1) INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ======================================================SO NO WAY TO GET IT UP. Any idea on what could be the problem? I tried giving permissions to some folders in Kamailio docker container: chown kamailio:kamailio /usr/sbin/kam* chmod 755 /usr/sbin/kam* chown -R kamailio:kamailio /etc/kamailio chmod -R 755 /etc/kamailio chown -R root:kamailio /var/run chmod -R 755 /var/run chown -R kamailio:kamailio /run/kamailio chown -R 755 /run/kamailio But had no effect... Thank you in advance. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted. Este mensaje y los ficheros adjuntos pueden contener información confidencial destinada solamente a la(s) persona(s) mencionadas anteriormente y pueden estar protegidos por secreto profesional. Si usted recibe este correo electrónico por error, gracias por informar inmediatamente al remitente y destruir el mensaje. Al no estar asegurada la integridad de este mensaje sobre la red, Atos no se hace responsable por su contenido. Su contenido no constituye ningún compromiso para el grupo Atos, salvo ratificación escrita por ambas partes. Aunque se esfuerza al máximo por mantener su red libre de virus, el emisor no puede garantizar nada al respecto y no será responsable de cualesquiera daños que puedan resultar de una transmisión de virus.

1 0

Info: Kamailio presentations later today at ClueCon TGI
by Daniel-Constantin Mierla 16 Feb '21

16 Feb '21

Hello, short note to inform that later today will be 3 sessions related to Kamailio at ClueCon TGI (online event): * a workshop about basics of SIP routing with Kamailio * a presentation about DID routing with Kamailio * a presentation about outsourcing services from FreeSwitch to Kamailio The first two are done by me, the last one by Fred Posner. The event is free to attend, by participating to a video conference or watch the youtube stream -- more details at: * https://www.cluecon.com/ Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla

2 2

Re: [SR-Users] Advice on handling SIP trunk to a Perimeta SBC
by Björn Bylander 16 Feb '21

16 Feb '21

Hi again, I'm using Kamailio 5.3.2 by the way. Björn Bylander writes: > Hi, > > So I’m tasked with setting up a SIP trunk to a Perimeta SBC (https://www.metaswitch.com/products/perimeta-sbc). > > Apparently, > > Perimeta hides the topology of networks by rewriting or removing topology-sensitive information from SIP messages. By default, your Session Controller will make the following changes to SIP messages. > > > > The Session Controller generates new dialog identifiers (call-IDs, From tags and To tags) for each side of the call, so that it does not expose information about your core network to your access networks. > > The Session Controller strips Record-Route and Route information from the message. > > The Session Controller rewrites Contact and Via headers so that the source IP address is replaced with the local address of the outbound adjacency. > > The Session Controller replaces the IP addresses in c= lines in SDP with the addresses it has allocated for media forwarding. For more information on this, see Media addresses and gates. > > My problem is this: When the Perimeta SBC sends its first INVITE (I can't say anything about any succeeding INVITEs yet) it's added a Record-Route header with the "lr" parameter included which, as far as I can see makes Kamailio think it should use loose routing which is all well I think. But when the SBC sends an ACK for the "200 OK" from the Kamailio side it doesn't include any Route headers and I think that makes it hard for Kamailio (at least with the standard script which is basically what I'm using) to know where to relay the ACK, at least it makes the t_check_trans() call in WITHINDLG after 'is_method("ACK")' return false which makes the script ignore the ACK. > > Any thoughts or suggestions on how to handle this? > > Thanks in advance, > Björn Bylander

1 0

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 February 2021