- sr-users - kamailio.org

dispatcher/carrierroute and branches across SBC and remote peer
by Nathan Ward 28 Nov '17

28 Nov '17

Hi, We use Kamailio as a SIP server, and SEMS as an SBC. We have a need to use the dispatcher/carrierroute modules to provide HA/load sharing across two different parts of our environment: 1) Our SBCs 2) Our peer’s SIP servers We have pairs of SBCs (for now) and they have the same network connectivity - different IPs of course, but they can reach the same things. Our peer’s network has 2 SIP servers (again, for now) reachable through either SBC. We select which SBC pair to use based on where the calls are going, in a branch route. In some cases, we use parallel forking, in others we use serial forking (i.e. to a media server for a prompt, then sending the call to wherever it needs to go). Right now there is no automatic failover or load sharing, so this is all simple logic - if call is to x peer or y customer, use x SBC or y SBC. I’m trying to add the failover/loadbalancing now. I have a few half baked ideas about how to achieve a network like this, but thought I’d ask if anyone else had done this first before I went too overboard. Currently I’m thinking of calling cr_route to figure out which peer SIP server, from there figuring out which SBC pair, and then calling ds_select_dst to select which SBC in the pair to set $du. I’m being tripped up though, as I can’t call cr_route or ds_select_dst in a branch route, but, as far as I’m aware that’s where I’d need to do so in order to handle this for multiple branches. Should I be looping the request through the SIP server to achieve this (i.e. force $du = 127.0.0.1 in my branch_route), or, can I avoid that complexity? -- Nathan Ward

1 0

Kamailio didn't start before increasing fork_delay
by igor.potjevlesch＠gmail.com 27 Nov '17

27 Nov '17

Hello, We suddenly had an issue on one Kamailio instance: we were not able to restart. Kamailio started to boot and fork and suddenly crashed. The last logs reported a failure regarding the ability to connect to one MySQL instance. I finally succeed to restart after increasing: fork_delay=5000 to fork_delay=9000. How this could happen suddenly? We already restarted Kamailio on this server. Regards, Igor.

2 5

Does Kamailio support RFC4117?
by Ye, Charlie (NSB - CN/Qingdao) 27 Nov '17

27 Nov '17

Hi Friends, Does Kamailio support RFC4117? Do you have any suggestions if I want support RFC4117 through Kamailio? Thanks and Best Regards, Charlie

2 2

Dispatcher with kam & fs behind nat
by Daniel Greenwald 27 Nov '17

27 Nov '17

Dispatcher is sending inbound calls to Freeswitch boxes. Both the FS boxes and Kam are behind the same nat. What is the correct way to pass calls to the FS boxes so that all SIP between FS & Kam use local IP's? Should Kam put two record-route headers on, one with PUBLICIP and one with PRIVATEIP? How is this accomplished? Thanks

2 3

Kamailio 5.0 Android Calling Not working
by Zeeshan M 25 Nov '17

25 Nov '17

Hello Friends, I had successfully installed and configured Kamailio 5.0 on linux machine. And tried it with linphone app & following are the issues i am facing, 1) IOS to Android Calling not working with timeout error on server end when we checked logs 2) Android to Android calls also not working same error. Kindly let me know what could be the issue. Regards, Zeeshan.

1 0

Re: [SR-Users] sipML5 through kamailio
by Wilkins, Steve 24 Nov '17

24 Nov '17

I just verified that I do have logging in all pertinent areas. I added tls and I do see "TLS accept successful" in the kamailio logs, however, I see no log being generated in route[xhttp:request], and I do have logging in the first line of this route. I don't think it is getting there. Also, I noticed I have event_route[xhttp:request] not route[xhttp:request]. Thank you, -Steve

1 0

sipML5 through kamailio
by Wilkins, Steve 24 Nov '17

24 Nov '17

Hello, I am attempting to use sipML5 to test WebRTC. I have not been successful in getting messages through to Kamailio though. I am running Kamailio 5.0.3 on Cento 7. My listen's in the kamailio configuration file are => listen=tcp:112.22.3.108:5060 advertise 34.226.187.61:5060 listen=udp:112.22.3.108:5060 advertise 34.226.187.61:5060 listen=tcp:112.22.3.108:10443 (which I will use in the sipML5 Expert mode) My sipML5 settings are => Public Identity - sip:user1@112.22.3.108 Realm - 112.22.3.108 Export mode setting are => WebSocket Server URL - wss://112.22.3.108:10443 (I have also tried wss://112.22.3.108:10443/ws) SIP outbound Proxy URL - udp://112.22.3.108:5060 (I have also left this blank) When I make a call I see no Kamailio activity (I have logging at the start of request_route) so I am not sure where the configuration error is. If I change the sipML5 configuration IP Address to use the asterisk IP Address, sipML5 works. My goal is to go WebRTC Client => Kamailio => Asterisk and eventually through some sort of media proxy. Thank you, -Steve

2 5

Re: [SR-Users] Cannot disable EC Diffie Hellman cipher suite
by otron2016＠gmail.com 24 Nov '17

24 Nov '17

Just a guess but maybe later entries [like +HIGH:+MEDIUM:+LOW] put it back. Try switching the order so that !ECDHE and the others you're trying to exclude come after. Sent from Samsung Mobile -------- Original message -------- From: Ilyas Keskin <ilyask92(a)gmx.de> Date: 11/24/2017 10:19 AM (GMT-08:00) To: miconda(a)gmail.com,"Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] Cannot disable EC Diffie Hellman cipher suite Hi Daniel, yes I am using the tls.cfg file. I tried your suggestion to add the cipher suite string (notice the !EDCHE which I also added to the httpd ssl.conf) but nothing changed. [server:default] method = TLSv1 cipher_list = !DH:!ECDHE:!EDH:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL verify_certificate = no require_certificate = no private_key = /etc/letsencrypt/live/webrtc.ddnss.de/privkey.pem certificate = /etc/letsencrypt/live/webrtc.ddnss.de/fullchain.pem #ca_list = ./modules/tls/cacert.pem #crl = ./modules/tls/crl.pem Also here is a log snippet from tls module section of kamailio initialization. Notice first two lines. Also it seems to me the module actually ignores the local openssl installation and uses its own which has been compiled with the module itself (?). Other than that it seems to be accepting the cipher_list value just fine: Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_mod.c:355]: mod_init(): With ECDH-Support! Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_mod.c:358]: mod_init(): With Diffie Hellman Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_init.c:587]: init_tls_h(): tls: _init_tls_h: compiled with openssl version "OpenSSL 1.0.1e-fips 11 Feb 2013" (0x1000105f), kerberos support: on, compression: on Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_init.c:595]: init_tls_h(): tls: init_tls_h: installed openssl library version "OpenSSL 1.0.1e-fips 11 Feb 2013" (0x1000105f), kerberos support: on, zlib compression: compiler: gcc -I. -I.. -I../include -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT -m64 -DL_ENDIAN -Wall -O2 -g -pipe -Wall -Wp,-D_ Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: WARNING: tls [tls_init.c:649]: init_tls_h(): tls: openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: <core> [cfg/cfg_ctx.c:613]: cfg_set_now(): INFO: cfg_set_now(): tls.low_mem_threshold1 has been changed to 7864320 Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: <core> [cfg/cfg_ctx.c:613]: cfg_set_now(): INFO: cfg_set_now(): tls.low_mem_threshold2 has been changed to 3932160 Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: WARNING: tm [tm.c:594]: fixup_routes(): WARNING: t_on_branch("MANAGE_BRANCH"): empty/non existing route Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: WARNING: tm [tm.c:594]: fixup_routes(): WARNING: t_on_reply("MANAGE_REPLY"): empty/non existing route Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: WARNING: tm [tm.c:594]: fixup_routes(): WARNING: t_on_failure("MANAGE_FAILURE"): empty/non existing route Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: <core> [udp_server.c:175]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: <core> [udp_server.c:225]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:275]: fill_missing(): TLSs<default>: tls_method=12 Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:287]: fill_missing(): TLSs<default>: certificate='/etc/letsencrypt/live/webrtc.ddnss.de/fullchain.pem' Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:294]: fill_missing(): TLSs<default>: ca_list='(null)' Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:301]: fill_missing(): TLSs<default>: crl='(null)' Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:305]: fill_missing(): TLSs<default>: require_certificate=0 Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:312]: fill_missing(): TLSs<default>: cipher_list='!DH:!ECDHE:!EDH:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL' Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:319]: fill_missing(): TLSs<default>: private_key='/etc/letsencrypt/live/webrtc.ddnss.de/privkey.pem' Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:323]: fill_missing(): TLSs<default>: verify_certificate=0 Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:326]: fill_missing(): TLSs<default>: verify_depth=9 Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:670]: set_verification(): TLSs<default>: No client certificate required and no checks performed Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:275]: fill_missing(): TLSc<default>: tls_method=12 Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:287]: fill_missing(): TLSc<default>: certificate='(null)' Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:294]: fill_missing(): TLSc<default>: ca_list='(null)' Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:301]: fill_missing(): TLSc<default>: crl='(null)' Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:305]: fill_missing(): TLSc<default>: require_certificate=1 Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:312]: fill_missing(): TLSc<default>: cipher_list='(null)' Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:319]: fill_missing(): TLSc<default>: private_key='(null)' Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:323]: fill_missing(): TLSc<default>: verify_certificate=1 Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:326]: fill_missing(): TLSc<default>: verify_depth=9 Nov 24 18:56:20 kamailio-sip /usr/sbin/kamailio[2864]: INFO: tls [tls_domain.c:655]: set_verification(): TLSc<default>: Server MUST present valid certificate Would it be possible to compile the tls module with certain openssl config switches (i.e. no-ec no-dh)? Any other ideas? Best regards, Ilyas Keskin Am 24.11.2017 um 15:45 schrieb Daniel-Constantin Mierla: Hello, On 23.11.17 22:42, Ilyas Keskin wrote: Hi there, I have set up a Kamailio 4.2.0 SIP server (centOS 7) for a university project regarding WebRTC comunication. While kamailio handles the signaling path I use the SIP.js demo phone js application (hosted on the same machine as kamaillio) for actual WebRTC stuff. For a deeper understanding and documetation purposes I have been trying to sniff the traffic with wireshark but failed due to the fact that kamailio uses Elliptic Curve Diffie Hellmann cipher suite (see wireshark snippet below) which is not decryptable. Secure Sockets Layer TLSv1.2 Record Layer: Handshake Protocol: Server Hello Content Type: Handshake (22) Version: TLS 1.2 (0x0303) Length: 89 Handshake Protocol: Server Hello Handshake Type: Server Hello (2) Length: 85 Version: TLS 1.2 (0x0303) Random: b8916e4e0f7c712503a77afcf4c9228598092c166353be50... Session ID Length: 32 Session ID: b0a31a6699a001b7991645dc61064ca4c4b073eff6913f26... Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) Compression Method: null (0) Extensions Length: 13 Extension: renegotiation_info (len=1) Extension: ec_point_formats (len=4) I already tried importing captured SSLKEYLOG pre master secret from chrome and private key file issued by letsencrypt without success. On top of that I set this line SSLCipherSuite !DH:!ECDH:!EDH:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL in /etc/httpd/conf.d/ssl.conf and compiled openssl with no-ec no-dh (which worked see below). [admin@kamailio-sip ~]$ openssl ciphers SRP-DSS-AES-256-CBC-SHA:SRP-RSA-AES-256-CBC-SHA:SRP-AES-256-CBC-SHA:AES256-GCM-SHA384:AES256-SHA256:AES256-SHA:CAMELLIA256-SHA:PSK-AES256-CBC-SHA:SRP-DSS-AES-128-CBC-SHA:SRP-RSA-AES-128-CBC-SHA:SRP-AES-128-CBC-SHA:AES128-GCM-SHA256:AES128-SHA256:AES128-SHA:SEED-SHA:CAMELLIA128-SHA:IDEA-CBC-SHA:PSK-AES128-CBC-SHA:RC4-SHA:RC4-MD5:PSK-RC4-SHA:SRP-DSS-3DES-EDE-CBC-SHA:SRP-RSA-3DES-EDE-CBC-SHA:SRP-3DES-EDE-CBC-SHA:DES-CBC3-SHA:PSK-3DES-EDE-CBC-SHA [admin@kamailio-sip ~]$ Setting modparam("tls", "cipher_list", "AESCCM") (or different ciphers) in /etc/kamailio/kamailio.cfg seems to have no effect on the actual negoiated cipher suite. Am I missing something? Any help or pointers into the right direction will be much appreciated. are you also using tls.cfg? If yes, there is an attribute for chiper list in it as well, try and see if works with it. Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 1

Re: [SR-Users] sipML5 through kamailio
by otron2016＠gmail.com 24 Nov '17

24 Nov '17

"So, tls is required for wss?" Yes, as of the last rfc. It can work without it if the client software (browser) will accept it though by now most will treat it as insecure. I forget whether sipML5 will but my guess would be no. -------- Original message -------- From: "Wilkins, Steve" <swwilkins(a)mitre.org> Date: 11/24/2017 9:57 AM (GMT-08:00) To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] sipML5 through kamailio Hello SamyGo, So, tls is required for wss? I thought that when I set a listen to Kamailio-Server-IPAddress:10443 and I sent a request through that IP and Port, that Kamailio would at least see the request and attempt to do something with it. I will go add tls and try again. Thank you! From: sr-users [mailto:sr-users-bounces@lists.kamailio.org] On Behalf Of SamyGo Sent: Thursday, November 23, 2017 12:40 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] sipML5 through kamailio Can you clarify the IP addressing scheme as you've mentioned. There is no TLS interface? Advertised address for 5060 but not for WSS interface. Both listen and advertise are public IPs ? Also,you're handling WSS requests. Do you've xlog ines in the route[xhttp:request] to view when a request lands.! My config has this: #!substdef "!MY_IP_ADDR!123.134.156.167!g" #!substdef "!MY_WS_PORT!6010!g" #!substdef "!MY_WSS_PORT!6011!g" listen=tcp:MY_IP_ADDR:MY_WS_PORT listen=tls:MY_IP_ADDR:MY_WSS_PORT Then the xhttp event route: ``` event_route[xhttp:request] { set_reply_close(); set_reply_no_connect(); #Deny any HTTP requests on any port other than WS/WSS ports. if ($Rp != MY_WS_PORT && $Rp != MY_WSS_PORT ) { xlog("L_WARN", "HTTP request received on $Rp\n"); xhttp_reply("403", "Forbidden", "", ""); exit; } #Handle HTTP(s) onwards. xlog("L_INFO", "HTTP Request Received\n"); ``` On Thu, Nov 23, 2017 at 12:18 PM, Wilkins, Steve <swwilkins(a)mitre.org> wrote: Hi Sammy, First of all, thank you for taking the time to respond. Yes, port 10443 is opened. I have used this port before as asterisk’s WebRTC port and iptables shows it as open. No, I can’t even get a registration using the configuration I listed. I have an xdbg log statement right after the request_route, and I see nothing. I do know that my xdbg logs are working though because, if I register or make a call using any sip tool, I see all my logging and everything works correctly. -Steve From: sr-users [mailto:sr-users-bounces@lists.kamailio.org] On Behalf Of SamyGo Sent: Thursday, November 23, 2017 12:00 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] sipML5 through kamailio Hi Steve, Can you confirm that port 10443 is reachable behind the NAT to Kamailio server, validate iptables too Does your SIPml5 demo client register successfully to Kamailio? are there enough xlog lines to print out if anything lands in Kamailio. Regards, Sammy On Thu, Nov 23, 2017 at 11:34 AM, Wilkins, Steve <swwilkins(a)mitre.org> wrote: Hello, I am attempting to use sipML5 to test WebRTC. I have not been successful in getting messages through to Kamailio though. I am running Kamailio 5.0.3 on Cento 7. My listen’s in the kamailio configuration file are => listen=tcp:112.22.3.108:5060 advertise 34.226.187.61:5060 listen=udp:112.22.3.108:5060 advertise 34.226.187.61:5060 listen=tcp:112.22.3.108:10443 (which I will use in the sipML5 Expert mode) My sipML5 settings are => Public Identity - sip:user1@112.22.3.108 Realm - 112.22.3.108 Export mode setting are => WebSocket Server URL - wss://112.22.3.108:10443 (I have also tried wss://112.22.3.108:10443/ws) SIP outbound Proxy URL - udp://112.22.3.108:5060 (I have also left this blank) When I make a call I see no Kamailio activity (I have logging at the start of request_route) so I am not sure where the configuration error is. If I change the sipML5 configuration IP Address to use the asterisk IP Address, sipML5 works. My goal is to go WebRTC Client => Kamailio => Asterisk and eventually through some sort of media proxy. Thank you, -Steve _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

1 0

Cannot disable EC Diffie Hellman cipher suite
by Ilyas Keskin 24 Nov '17

24 Nov '17

Hi there, I have set up a Kamailio 4.2.0 SIP server (centOS 7) for a university project regarding WebRTC comunication. While kamailio handles the signaling path I use the SIP.js demo phone js application (hosted on the same machine as kamaillio) for actual WebRTC stuff. For a deeper understanding and documetation purposes I have been trying to sniff the traffic with wireshark but failed due to the fact that kamailio uses Elliptic Curve Diffie Hellmann cipher suite (see wireshark snippet below) which is not decryptable. Secure Sockets Layer TLSv1.2 Record Layer: Handshake Protocol: Server Hello Content Type: Handshake (22) Version: TLS 1.2 (0x0303) Length: 89 Handshake Protocol: Server Hello Handshake Type: Server Hello (2) Length: 85 Version: TLS 1.2 (0x0303) Random: b8916e4e0f7c712503a77afcf4c9228598092c166353be50... Session ID Length: 32 Session ID: b0a31a6699a001b7991645dc61064ca4c4b073eff6913f26... Cipher Suite: TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (0xc02f) Compression Method: null (0) Extensions Length: 13 Extension: renegotiation_info (len=1) Extension: ec_point_formats (len=4) I already tried importing captured SSLKEYLOG pre master secret from chrome and private key file issued by letsencrypt without success. On top of that I set this line SSLCipherSuite !DH:!ECDH:!EDH:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL in /etc/httpd/conf.d/ssl.conf and compiled openssl with no-ec no-dh (which worked see below). [admin@kamailio-sip ~]$ openssl ciphers SRP-DSS-AES-256-CBC-SHA:SRP-RSA-AES-256-CBC-SHA:SRP-AES-256-CBC-SHA:AES256-GCM-SHA384:AES256-SHA256:AES256-SHA:CAMELLIA256-SHA:PSK-AES256-CBC-SHA:SRP-DSS-AES-128-CBC-SHA:SRP-RSA-AES-128-CBC-SHA:SRP-AES-128-CBC-SHA:AES128-GCM-SHA256:AES128-SHA256:AES128-SHA:SEED-SHA:CAMELLIA128-SHA:IDEA-CBC-SHA:PSK-AES128-CBC-SHA:RC4-SHA:RC4-MD5:PSK-RC4-SHA:SRP-DSS-3DES-EDE-CBC-SHA:SRP-RSA-3DES-EDE-CBC-SHA:SRP-3DES-EDE-CBC-SHA:DES-CBC3-SHA:PSK-3DES-EDE-CBC-SHA [admin@kamailio-sip ~]$ Setting modparam("tls", "cipher_list", "AESCCM") (or different ciphers) in /etc/kamailio/kamailio.cfg seems to have no effect on the actual negoiated cipher suite. Am I missing something? Any help or pointers into the right direction will be much appreciated. Best regards, Ilyas Keskin

2 2

Kamailio KEMI Framework Tutorial
by Daniel-Constantin Mierla 24 Nov '17

24 Nov '17

Hello, I started a tutorial for Kamailio KEMI Framework written in markdown format targeting use of mkdocs. It is published on github as part of kamailio-docs repository: * https://github.com/kamailio/kamailio-docs/tree/master/kamailio-kemi-framewo… The mkdocs build (to browse and read) is online at: * http://kamailio.org/docs/tutorials/devel/kamailio-kemi-framework/ It is work in progress and contributions from the community are more than welcome -- doing push requests on github project is the recommended way for contributions: * https://github.com/kamailio/kamailio-docs/ The main goal is document the role of KEMI, its benefits and how it can be used. It addition it should cover the list of functions exported to KEMI by core as well as special KEMI functions. Regarding the functions exported by kamailio modules to KEMI I added as an skeleton the ones exported by acc module. However, I am not sure if we should do it there or add them to the existing docs of the modules. Opinions on this?!? Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

2 10

Request Time Out
by Vasim Antule 24 Nov '17

24 Nov '17

Hello, I am new to SIP/Kamailio , I am attempting to use Kamailio 5.0 in test environment. I am getting Request Time Out for Android Phones. Apple to Apple phones are working fine. But Android to Apple and Android to Android I am getting Request Time Out. Please Guide. Regards, Vasim Antule

1 0

Issue dumping an huge htable through xmlrpc
by Marco Capetta 24 Nov '17

24 Nov '17

Hello everyone, On Kamailio version 4.4.6 I have an issue dumping an huge htable through xmlrpc. We are using htables to store the subscriber registration attempts to prevent bruteforcing password attacks. Usually there aren't any issues to dump information using xmlrpc. On the contrary, if the number of records in the htable become huge (in the order of 10.000), xmlrpc output is truncated, therefore it is not possible to parse it. I have the same results either using a Perl library or the "xmlrpc_test.py" script included in package. I tried to increase the module parameters "binrpc_max_body_size" and "binrpc_struct_max_body_size" without success. Do you have any other suggestion? Thank you Regards Marco -- *Marco Capetta * Operations Engineer Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15 AT-2345 Brunn am Gebirge Phone: +43(0)1 301 2044 <tel:+4313012044> Email: mcapetta(a)sipwise.com <mailto:mcapetta@sipwise.com> Website: www.sipwise.com <http://www.sipwise.com> Particulars according Austrian Companies Code paragraph 14 "Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge FN:305595f, Commercial Court Vienna, ATU64002206

2 1

Failed to find command http_client_query
by Alexandru Covalschi 24 Nov '17

24 Nov '17

Hello everyone, Updated to 5.0.4 from repo, up-to-date debian 8, http_client.so is certainly loaded. When I try to change http_query to http_client_query it fails to load with error "failed to find command http_client_query". Any ideas? It is same on all my test servers. ________________________________ Alexandru Covalschi VoIP Engineer and System Administrator tel: +373 673 98 493

2 12

msilo support for picture, audio and video?
by sscc 24 Nov '17

24 Nov '17

Hello Folks does msilo support picture, audio and video? regards sscc? -- Sent from: http://sip-router.1086192.n5.nabble.com/Users-f3.html

2 5

Loadbalancing authenticated agetways
by SamyGo 23 Nov '17

23 Nov '17

Hi, I've a scenario where multiple mediaservers will be registered to Kamailio and for any incoming call from Upstream provider I've to perform load-balancing to the actively registered media-servers. dispatcher module does load-balancing for IP endpoints, is there any other module where I can perform load-balancing on registered clients(media-servers)? Thanks, Sammy

3 3

why do I need rtpproxy
by Wilkins, Steve 23 Nov '17

23 Nov '17

The way I understand it, rtpproxy is needed to pass video/audio through Kamailio to Asterisk. However, even without rtpproxy running, I get video through to Asterisk via Kamailio, and the video plays with no issues on a sip device (e.g. MicroSIP). I am confused what I need rtpproxy for. Thank you

3 2

rfc: clang format the code
by Daniel-Constantin Mierla 23 Nov '17

23 Nov '17

Hello, it was discussed during the last irc devel meeting and everyone there agreed to use clang-format to format the source code: - https://clang.llvm.org/docs/ClangFormat.html Is any developer (maybe not present during the irc devel meeting) opposing this? It is not going to be all at once, because some of the structures and initialization of them may be preferred to be kept with a custom format for being easier to read -- to have a section in the file not formatted, it has to be enclosed in between comments: /* clang-format off */ ... /* clang-format o. */ But for the rest of the code (i.e., functions) I think it will be better to agree on a format and try to use it. The clang-formatting should be done when one needs to update code in some files. Over the years, developers come and go, having each one with a custom formatting style is hard to maintain properly in long term. There are modules that do not indent coherently code inside blocks, using a mixture, more or less no style. This makes it hard for other developers to review in case of reported issues, but also for new comers to get familiar with the code. In the source tree there is already a .clang-format file which defines the options for formatting. It was used by me and other developers already -- I did it mainly in my modules or those components that do not have an active maintainer. But I plan to do it also on the components that have currently a maintainer at the moment I need to work on that code (e.g., fix some issue or export functions to kemi framework). My process of clang-formatting a module is like: - edit the files to add clang-format off/on comments around the parts I want to preserve as they are (typically mod exports -- params, functions, kemi -- and intialization of structures that are aligned to a specific indentation that makes it easier to read). - run: clang-format -i src/modules/modname/*.{c,h} - commit with these changes, no new feature or bug fix must be done in the same commit (can be combined with removing the history comments) If one wants different options inside .clang-format, please propose and let's discuss which one is preferred by the majority of the current developers. If no one shows anything against in a matter of few days, it will be considered accepted (after all, one can re-indent on own style if the rule is not accepted or overturned). Cheers, Daniel -- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com

1 0

Error when attempting to use rtpproxy
by Wilkins, Steve 23 Nov '17

23 Nov '17

Hello, I entered this question before but did not include the tcpdump file. I am re-posting just in case this message was over looked for lack of information. I am using Kamailio version 5.0.3 (x86_64/linux), and it is installed and working on a Centos 7 Sever. I use Kamailio as a SIP Proxy Server for Asterisk and things seem to work fine, however, I do have an issue and a question for which I am trying to understand and am hoping someone can help me with. My server name is vadev2 (Kamailio run on this server), and it's IP Address and port are 172.21.1.108:5060; Asterisk servers are (172.21.1.97:5060, and 172.21.1.124:5060). The rtpproxy is 172.21.1.108:17722 Issue: Every 10 seconds I get an Error message in the Kamailio log which says => Nov 13 18:10:55 vadev2/usr/local/sbin/kamailio[29188]: ERROR: <core> [core/tcp_main.c:2660]: tcpconn_1st_send(): connect 172.21.1.108:59794<http://172.1.1.13:59794> failed (RST) Connection refused. I do not know what triggers this error, and as mentioned, things do seem to work, other than I do not believe anything is going through rtpproxy; I can make calls and use sip tools which pass requests through Kamailio to Asterisk. Does anyone know what could be causing this Error? I do not understand what is trying to connect to what and why. Should I be using rtpengine instead of rtpproxy? I did attempt rtpengine but it would not compile due to missing json.h files. Thank you for any help -Steve

1 0

MSILO with encryption/decryption
by SamyGo 23 Nov '17

23 Nov '17

Hi, Is there any internal mechanism for msilo to store messages encrypted and retrieve them decrypted before sending? Thanks, Sammy

1 0

RV: CANCEL not being matched by tm module when via address does not have port included
by CARLOS GARCIA MORCHON 23 Nov '17

23 Nov '17

Hi, I have an IMS core deployed using kamailio 5.0.2. Calls from clients are reaching the core pcscf from a freeswitch (with address A.A.A.A) + a kamailio acting as proxy (with address B.B.B.B), so the INVITE request looks like this: INVITE sip:1111111111@mnc001.mcc001.3gppnetwork.org SIP/2.0 Record-Route: <sip:A.A.A.A;lr> Via: SIP/2.0/UDP A.A.A.A;branch=z9hG4bK8735.ef7a61e110f335b2e92a8c1d430de585.0 Via: SIP/2.0/UDP B.B.B.B:5080;received=B.B.B.B;rport=5080;branch=z9hG4bKHpB704ZaXSKtm Max-Forwards: 65 From: "222222222" <sip:222222222@B.B.B.B>;tag=eytD49ymQr71S To: <sip:1111111111@mnc001.mcc001.3gppnetwork.org> Call-ID: 77d249c0-487c-1236-1997-00163edbaa97 CSeq: 115249948 INVITE Contact: <sip:mod_sofia@B.B.B.B:5080> User-Agent: FreeSWITCH-mod_sofia/1.6.19+git~20170927T175834Z~38f568d343~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY Supported: timer, path, replaces Allow-Events: talk, hold, conference, refer Content-Type: application/sdp Content-Disposition: session Content-Length: 224 P-Charge-Info: <sip:222222222@mobile.tuenti.int>;npi=ISDN;noa=4 X-FS-Support: update_display,send_info Remote-Party-ID: "222222222" <sip:222222222@B.B.B.B>;party=calling;screen=yes;privacy=off If the client cancels the request, the CANCEL request that gets to the core pcscf looks like this: CANCEL sip:1111111111@mnc001.mcc001.3gppnetwork.org SIP/2.0 Via: SIP/2.0/UDP A.A.A.A;branch=z9hG4bK8735.ef7a61e110f335b2e92a8c1d430de585.0 Max-Forwards: 65 From: "222222222" <sip:222222222@B.B.B.B>;tag=eytD49ymQr71S To: <sip:1111111111@mnc001.mcc001.3gppnetwork.org> Call-ID: 77d249c0-487c-1236-1997-00163edbaa97 CSeq: 115249948 CANCEL Content-Length: 0 Reason: Q.850;cause=16;text="Normal Call Clearing" The processing of the CANCEL at the pcscf is eventually reaching the t_check_trans() function, but the logs return “no CANCEL matching found!” and thus the processing ends. I have followed the code up to the via_matching function in the t_lookup.c file of the tm module source and added some logs. The via matching is failing at the port comparison (the port stored for the INVITE is “5060”, the port stored for the CANCEL is “0”. The flow works ok with a different client (connected directly to the core) which includes the port in the Via headers. ¿Can this be a bug in kamailio or am I doing something wrong?. AFAIK The RFC 3261 does not mandate to include the ports in the sent-by element of the Via header Thanks! Carlos ________________________________ Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción. The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it. Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição

3 4

Kamailio new install, unable to create users
by Atux Atux 23 Nov '17

23 Nov '17

Hi. New to the area and trying to find my way around with kamailio. In one of my debian servers i need to have kamailio with a gui to start playing around with it. i am following the http://kb.asipto.com/kamailio:skype-like-service-in-less-than-one-hour to install kamailio. When running kamdbctl create it asks what format coding that i must have to configure the DB. i simply add latin1 and it goes on. then when i issue kamctl add daniel 1234qwet it comes with the following error: root@debian:~# kamctl add daniel 1234qwet MySQL password for user 'kamailio@localhost': ERROR 1045 (28000): Access denied for user 'kamailio'@'localhost' (using password: YES) ERROR: introducing the new user 'daniel' to the database failed root@debian:~# Any ideas on how to proceed with the following error please?

2 3

kemi with lua and dispatcher - attempt to index field 'dispatcher' (a nil value)
by Karsten Horsmann 23 Nov '17

23 Nov '17

Hello Daniel, hello List, after reading the fresh released kemi documentation (Thanks for that!) on github i start to configure an kemi lua configuration. It seems to be that there is not an dispatcher export to kemi in my installation. Or i missconfigured something? How to use dispatcher with kemi? 1.) First try to solve this - use param "register" "modulename" to app_lua - doesnt work 2.) grep around in the auto kemi in/export messages in debug startup - nothing to see. 3.) grep around in the kamcmd api.list command for lua - no dispatcher here the intressting parts of the configs and lua-script: kamailio.cfg ... loadmodule "dispatcher.so" loadmodule "permissions.so" loadmodule "avpops.so" #!ifdef WITH_CFGLUA loadmodule "app_lua.so" modparam("app_lua", "reload", 1) modparam("app_lua", "register", "dispatcher") #!endif #!ifdef WITH_CFGLUA modparam("app_lua", "load", "/etc/kamailio/lua/kamailio-kemi-lua.lua") cfgengine "lua" #!else import_file "request-route.cfg" #!endif ... kamailio-kemi-lua.lua function ksr_request_route() ... -- dispatch destinations if KSR.permissions.allow_source_address(FLT_EDGE) then KSR.info("new $fU -> $rU in permissions"); direction = "inbound"; routing_target = FLT_FSNODE; ksr_route_dispatch(direction, routing_target); KSR.x.exit(); end KSR.info("NOT-OKAY - $rU dropped"); -- End of Route() KSR.sl.sl_send_reply(407, "Proxy Authentication Required. See IP GUI"); return 1; ... end --- dispatcher route function ksr_route_dispatch(direction, routing_target) KSR.xlog.xinfo("new $fU -> $rU in routing_target ksr_route_dispatch"); KSR.info(routing_target); if (routing_target == nil) then KSR.xlog.xinfo("routing_target nil"); KSR.sl.sl_send_reply(604, "Does Not Exist Anywhere"); KSR.x.exit(); end if KSR.dispatcher.ds_select_dst(routing_target, 4) then send_reply(404, "No destination"); KSR.x.exit(); end ksr_route_myheader(); ksr_route_relay(); KSR.x.exit(); end /usr/sbin/kamailio[26763]: ERROR: app_lua [app_lua_api.c:713]: app_lua_run_ex(): error from Lua: /etc/kamailio/lua/kamailio-kemi-lua.lua:131: attempt to index field 'dispatcher' (a nil value) kamailio -v version: kamailio 5.0.4 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, 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_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled on 20:20:24 Nov 16 2017 with gcc 4.8.5 rpm -aq | grep kam kamailio-mysql-5.0.4-26.el7.centos.x86_64 kamailio-5.0.4-26.el7.centos.x86_64 kamailio-lua-5.0.4-26.el7.centos.x86_64 kamailio-ims-5.0.4-26.el7.centos.x86_64 rpm -ql kamailio-5.0.4 | grep disp /usr/lib64/kamailio/modules/dispatcher.so /usr/share/doc/kamailio/modules/README.dispatcher /usr/share/kamailio/dbtext/kamailio/dispatcher -- Kind Regards *Karsten Horsmann*

2 5

"Federated" PBX solution with GUI to use with Kamailio - Suggestions needed
by George Diamantopoulos 23 Nov '17

23 Nov '17

Hello all! I'm looking at "PBX" platforms to use with kamailio as a load-balancer. This is not a strictly kamailio question, but I thought that if anyone has a suggestion to make, they would be watching this list. I'm investigating a use case with the following requirements: * Kamailio will act as a load-balancer, dispatching initial requests to PBX entities (e.g. Asterisk, Freeswitch) * PBX solution must have a single GUI interface to manage PBX functions (think FreePBX, FusionPBX etc) * Configuration via the GUI must apply to all PBX instances * Some sort of "asterisk-realtime + device state synchronization"-like setup must ensure every PBX box can service any request at any time (for failover) * Solution needn't be multi-tenant oriented, but if it is, it must work fine for single-tenant setups as well without multi-tenant capability getting in the way all the time * Feature list needn't be as full as, say, FreePBX's, but most common functionality must be available (inbound/outbound routing, trunks, queues, hunting to name a few) * Must be open source As a proprietary example, MiRTA PBX seems to check all the boxes above, apart from being open source. Now this "product" also offers high availability for databases and web apps, which is beyond the scope of this investigation. I'm only looking at a solution that provides a federated, synchronized farm of PBX instances. Any input would be greatly appreciated. Thanks! Best regards, George

3 2

Re: [SR-Users] Kamailio IMS + Asterisk PBX
by Amar Tinawi 22 Nov '17

22 Nov '17

My tests results : Unfortunately, no scenario was success, maybe because Asterisk does not support sh interface (Diameter) My test was for presence service and couldn’t get it done. The results of Having asterisk as an AS with kamailio IMS : with sip trunk configured towards S-cscf And whether the user is identified in Asterisk as extension user or not asterisk responded with 404 user not found. Sent from Mail for Windows 10

2 1

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