Re: [SR-Users] Keep-Alive in dialog freeing a free fragment
Hello, thanks for reporting and troubleshooting. Can you refer to the code (file+lines) for step 3 and 4? It will save me some time to look into the code and fix the issue. Cheers, Daniel On 07/05/15 08:46, Dirk Teurlings - SIGNET B.V. wrote: Hi, (Kamailio 4.2.3) Working to get dialogs closed and cleaned up nicely I'm looking into the ka_interval and ka_timer parameter of the dialog module. The following is now happening. Scenario: 1. Call gets setup 2. Callee's internet connection drops 3. Call gets terminated (nicely) due to ka_timer/ka_interval 4. Log fills with freeing a free fragment after about 10 seconds Digging into this I saw that the dialog is being closed and cleaned properly in step 3. But it fails to remove/clean the timers used for the keep-alive. That's what triggers step 4, which in turn tries to clean the (or some of the) dialog space again. Is this expected behaviour when using the keep-alive options, or am I running into somekind of (known) bug? Thanks in advance for any help. -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] TCP connection reset by peer
Hello, On 07/05/15 09:02, Mickael Marrache wrote: Hi, I sometimes see the following in the logs: kamailio[14433]: ERROR: core [tcp_read.c:271]: tcp_read_data(): error reading: Connection reset by peer (104) kamailio[14433]: ERROR: core [tcp_read.c:1296]: tcp_read_req(): ERROR: tcp_read_req: error reading It looks like Kamailio tries to read a request from a TCP socket but the connection has been reset (not properly ended) by the remote peer. Is it an error? Does it prevent Kamailio from working properly? If yes, what is the solution? this is normal situation that can happen out there (e.g., connections can be cut by home routers or user on mobile device loses the signal) -- those logs messages should be made NOTICE or INFO. Or set to corelog level so they can be disabled if wanted. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Keep-Alive in dialog freeing a free fragment
Hi again, File dlg_req_within.c function bye_reply_cb line: 166-236 functino dlg_ka_cb line: 240-275 To help you out a bit more, this is important part of the log. May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_hash.c:1066]: next_state_dlg(): dialog 0x7f812f2585e8 changed from state 4 to state 5, due event 7 (ref 5) May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_req_within.c:195]: bye_reply_cb(): removing dialog with h_entry 1231 and h_id 1142 May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: WARNING: dialog [dlg_req_within.c:212]: bye_reply_cb(): inconsitent dlg timer data on dlg 0x7f812f2585e8 [1231:1142] with clid '6fcb9a946131aad41e1deda730c6b76a@192.168.10.245:5060' and tags 'as57b6a153' 'c42610a13600fe22i0' May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_cb.c:256]: run_dlg_callbacks(): dialog=0x7f812f2585e8, type=64 May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_req_within.c:219]: bye_reply_cb(): first final reply May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_hash.c:872]: dlg_unref(): unref dlg 0x7f812f2585e8 with 2 - 3 May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_handlers.c:324]: dlg_iuid_sfree(): freeing dlg iuid [1231:1142] (0x7f812f2529f0) May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: tm [t_reply.c:1653]: cleanup_uac_timers(): DEBUG: cleanup_uac_timers: RETR/FR timers reset May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_var.c:81]: cb_dlg_locals_reset(): resetting the local dialog shortcuts on script callback: 2147483652 ... May 4 18:10:02 vps-host /usr/sbin/kamailio[24484]: DEBUG: core [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil) May 4 18:10:02 vps-host /usr/sbin/kamailio[24484]: DEBUG: core [receive.c:298]: receive_msg(): receive_msg: cleaning up May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: tm [t_reply.c:1294]: t_should_relay_response(): - T_code=0, new_code=408 May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: tm [t_reply.c:2080]: local_reply(): DEBUG: local_reply: branch=0, save=0, winner=0 May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: tm [t_reply.c:2117]: local_reply(): DEBUG: local transaction completed May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7f812f256fd0, callback type 1024, id 0 entered May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: dialog [dlg_req_within.c:255]: dlg_ka_cb(): receiving a final reply 408 May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: dialog [dlg_hash.c:663]: dlg_lookup(): no dialog id=1142 found on entry 1231 May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: dialog [dlg_handlers.c:324]: dlg_iuid_sfree(): freeing dlg iuid [1231:1142] (0x7f812f252ba0) May 4 18:10:02 vps-host /usr/sbin/kamailio[24493]: DEBUG: dialog [dlg_hash.c:663]: dlg_lookup(): no dialog id=1142 found on entry 1231 May 4 18:10:02 vps-host /usr/sbin/kamailio[24493]: DEBUG: dialog [dlg_hash.c:663]: dlg_lookup(): no dialog id=11917 found on entry 68 May 4 18:10:02 vps-host /usr/sbin/kamailio[24493]: DEBUG: dialog [dlg_hash.c:663]: dlg_lookup(): no dialog id=1142 found on entry 1231 May 4 18:10:02 vps-host /usr/sbin/kamailio[24493]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7f812f252ad0/0x7f812f252b08) - ignore May 4 18:10:02 vps-host /usr/sbin/kamailio[24493]: DEBUG: dialog [dlg_hash.c:663]: dlg_lookup(): no dialog id=11917 found on entry 68 etc... Cheers, Dirk Teurlings On 07-05-15 09:03, Daniel-Constantin Mierla wrote: Hello, thanks for reporting and troubleshooting. Can you refer to the code (file+lines) for step 3 and 4? It will save me some time to look into the code and fix the issue. Cheers, Daniel On 07/05/15 08:46, Dirk Teurlings - SIGNET B.V. wrote: Hi, (Kamailio 4.2.3) Working to get dialogs closed and cleaned up nicely I'm looking into the ka_interval and ka_timer parameter of the dialog module. The following is now happening. Scenario: 1. Call gets setup 2. Callee's internet connection drops 3. Call gets terminated (nicely) due to ka_timer/ka_interval 4. Log fills with freeing a free fragment after about 10 seconds Digging into this I saw that the dialog is being closed and cleaned properly in step 3. But it fails to remove/clean the timers used for the keep-alive. That's what triggers step 4, which in turn tries to clean the (or some of the) dialog space again. Is this expected behaviour when using the keep-alive options, or am I running into somekind of (known) bug? Thanks in advance for any help. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] Keep-Alive in dialog freeing a free fragment
Hi, (Kamailio 4.2.3) Working to get dialogs closed and cleaned up nicely I'm looking into the ka_interval and ka_timer parameter of the dialog module. The following is now happening. Scenario: 1. Call gets setup 2. Callee's internet connection drops 3. Call gets terminated (nicely) due to ka_timer/ka_interval 4. Log fills with freeing a free fragment after about 10 seconds Digging into this I saw that the dialog is being closed and cleaned properly in step 3. But it fails to remove/clean the timers used for the keep-alive. That's what triggers step 4, which in turn tries to clean the (or some of the) dialog space again. Is this expected behaviour when using the keep-alive options, or am I running into somekind of (known) bug? Thanks in advance for any help. -- Cheers, Dirk Teurlings ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] db_mongodb get columns error
Hi, Sorry not to have answered before, I just did a restart and there was no error. We don't restart often so I can't tell you how often this issue appears but I will keep an eye on it. It may be a bug in the insert or update code in db_mongodb that misses the caller_sock column but I'm not sure. Is it possible a dialog is inserted without caller_sock field? Or, is it possible $unset is used somewhere for the caller_sock? Mickael From: Daniel-Constantin Mierla [mailto:mico...@gmail.com] Sent: Thursday, May 07, 2015 10:23 AM To: Kamailio (SER) - Users Mailing List; Mickael Marrache Subject: Re: [SR-Users] db_mongodb get columns error Hello, On 27/04/15 23:46, Daniel-Constantin Mierla wrote: Hello, On 22/04/15 14:00, Mickael Marrache wrote: Hi, After restarting Kamailio, I got the following errors during the startup: kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:381]: db_mongodb_get_columns(): field [caller_sock] not found in result iterator kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:739]: db_mongodb_store_result(): failed to set the columns kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:918]: db_mongodb_query(): failed to store result kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:927]: db_mongodb_query(): failed to do the query kamailio[12614]: ERROR: dialog [dlg_db_handler.c:257]: select_entire_dialog_table(): Error while querying database What may be causing the issue? I should always have a caller_sock in every dialog document. the error is thrown when the caller_sock field is not found in the b/json document returned by mongodb. Do you get the error every time you restart? Any update on this? As I am spending some time with testing for 4.3, I would like to close this issue if there is something to fix. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio authentication method
Hello Daniel, Thank you for your answer, this is exactly what I need. Modification of the auth module seems to be a better solution, but this lead to some questions for me... - Could you explain a little bit how the auth module is working? Which files do I have to modify to change the hash method? - If I used another auth_* module to get username / password, the modification in the auth module is enough for the www_authentication? In other words, the authentication is always done in this module? Even If I use auth_radius or auth_diameter or a self-made auth_* module? Regards, Frederic From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Wednesday 6 May 2015 16:44 To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio authentication method Hello, to understand properly, do you need to have: HA1=SHA(username:realm:password) HA2=SHA(method:digestURI) response=SHA(HA1:nonce:HA2) Perhaps it can be done with config file scripting, if you are familiar with transformations and header manipulation. But I think it will be simpler to extend auth module to support different hashing algorithm. The code for computing shaX is already in kamailio (used for shaX transformations), so the change in auth should be about advertising and detecting when the new algorithm has to be used. Cheers, Daniel On 06/05/15 16:28, Mathys Frédéric wrote: Hello, In my scenario with a Kamailio server, I have a VOIP client connecting to the server which, for some reasons, cannot calculate MD5 hashes but only SHA. In this situation, would it be possible to change the authentication algorithm by either modifying Kamailio scripts or writing an external module to do that? As far as I know, the authentication response is calculated as follow (standard HTTP Digest authentication) : HA1=MD5(username:realm:password) HA2=MD5(method:digestURI) response=MD5(HA1:nonce:HA2) For that, I have to save ha1 and ha1b values in the DB with the SHA function directly (with a trigger for example), and then change the authentication method too. What is the best solution to do that? Does a module already exists? Thank you! Frederic Mathys System Integration Validation ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] db_mongodb get columns error
Hello, On 27/04/15 23:46, Daniel-Constantin Mierla wrote: Hello, On 22/04/15 14:00, Mickael Marrache wrote: Hi, After restarting Kamailio, I got the following errors during the startup: kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:381]: db_mongodb_get_columns(): field [caller_sock] not found in result iterator kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:739]: db_mongodb_store_result(): failed to set the columns kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:918]: db_mongodb_query(): failed to store result kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:927]: db_mongodb_query(): failed to do the query kamailio[12614]: ERROR: dialog [dlg_db_handler.c:257]: select_entire_dialog_table(): Error while querying database What may be causing the issue? I should always have a caller_sock in every dialog document. the error is thrown when the caller_sock field is not found in the b/json document returned by mongodb. Do you get the error every time you restart? Any update on this? As I am spending some time with testing for 4.3, I would like to close this issue if there is something to fix. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Setup kamalio at AWS server
I sent an answer to this same question from you yesterday. Fred Posner The Palner Group, Inc. http://www.palner.com (web) +1-503-914-0999 (direct) On 05/06/2015 10:44 AM, Yogendra Gupta wrote: Hello, I have setup kamailio at AWS server and it is connecting at private IP not public ip. I am getting following error: ERROR: core [udp_server.c:392]: udp_init(): bind(7, 0x7f9eca5f11bc, 16) on 54.149.7.246: Cannot assign requested address Let me know where I need to fixed it Thanks *From:*Yogendra Gupta [mailto:yogen...@konstantinfosolutions.com] *Sent:* Tuesday, April 07, 2015 10:45 AM *To:* 'Kamailio (SER) - Users Mailing List'; 'Daniel-Constantin Mierla' *Subject:* RE: Kamailio audio call not working at some DNS network Hello, We have added domain and now call is connected but audio is not coming. What can be issue with audio call? Following is details: Username : user2 Domain : mobileappplatform.com Password : 123456 Let me know what can be issue? thanks *From:*Yogendra Gupta [mailto:yogen...@konstantinfosolutions.com] *Sent:* Wednesday, April 01, 2015 7:57 PM *To:* 'Kamailio (SER) - Users Mailing List'; 'Daniel-Constantin Mierla' *Subject:* Kamailio audio call not working at some DNS network Hello, We have setup Kamailio (SIP) at linux ubuntu server and it is working fine for call and text chat with users that are registered at server for some DNS networks. Audio call is not working at some DNS and chat is working at same DNS. We have already disabled firewall at server. What can be problem at server. I have also attached config file .. please check if there is any error. Let us know any communication option so we can sort out this issue at our server. Thanks *From:*sr-users [mailto:sr-users-boun...@lists.sip-router.org] *On Behalf Of *jay binks *Sent:* Wednesday, April 01, 2015 6:16 PM *To:* Daniel-Constantin Mierla; Kamailio (SER) - Users Mailing List *Subject:* Re: [SR-Users] Make deb Sorry, this confused me a little.. can you give an example of what you mean ? On 1 April 2015 at 22:40, Daniel-Constantin Mierla mico...@gmail.com mailto:mico...@gmail.com wrote: Hello, you have to edit spec files and remove the other modules in the folder matching your debian distribution inside 'pkg/kamailio/deb/'. This is the only way I know to change the packaging content for debs. Then make a symlink inside root folder of kamailio server named 'debian' to the respective folder inside 'pkg/kamailio/deb/' and run 'make deb'. Cheers, Daniel On 01/04/15 13:50, jay binks wrote: is there any way to make deb packages for only 1 of the modules ?? currently it takes a long time to run make deb im simply trying to build and package db_cassandra ( need the package for my environment ) As a side note, is there any chance db_cassandra could be added to the kamailio deb packages ? -- Sincerely Jay ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org mailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Sincerely Jay ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
[SR-Users] TCP connection reset by peer
Hi, I sometimes see the following in the logs: kamailio[14433]: ERROR: core [tcp_read.c:271]: tcp_read_data(): error reading: Connection reset by peer (104) kamailio[14433]: ERROR: core [tcp_read.c:1296]: tcp_read_req(): ERROR: tcp_read_req: error reading It looks like Kamailio tries to read a request from a TCP socket but the connection has been reset (not properly ended) by the remote peer. Is it an error? Does it prevent Kamailio from working properly? If yes, what is the solution? Thanks, Mickael ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Keep-Alive in dialog freeing a free fragment
Hello, I couldn't correlate the log message for double free with the code for bye_reply_cb and dlg_ka_cb. The logs from pid 24493 shows only dialog lookups and that double free message. Do you have the instance still running? Can you send the output of: kamctl ps Also, would be helpful to see some other logs messages printed just before by pid 24493. By analyzing the code I found an improvement to be done, already committed in master via: - https://github.com/kamailio/kamailio/commit/04410aef38f5ed40c8f4a6796d95658407e1597c It is about being sure the dialog is still in confirmed state when the keepalive callback is handled. But I can't be sure yet if that was the case resulting in double free. Cheers, Daniel On 07/05/15 09:34, Dirk Teurlings - SIGNET B.V. wrote: Hi again, File dlg_req_within.c function bye_reply_cb line: 166-236 functino dlg_ka_cb line: 240-275 To help you out a bit more, this is important part of the log. May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_hash.c:1066]: next_state_dlg(): dialog 0x7f812f2585e8 changed from state 4 to state 5, due event 7 (ref 5) May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_req_within.c:195]: bye_reply_cb(): removing dialog with h_entry 1231 and h_id 1142 May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: WARNING: dialog [dlg_req_within.c:212]: bye_reply_cb(): inconsitent dlg timer data on dlg 0x7f812f2585e8 [1231:1142] with clid '6fcb9a946131aad41e1deda730c6b76a@192.168.10.245:5060' and tags 'as57b6a153' 'c42610a13600fe22i0' May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_cb.c:256]: run_dlg_callbacks(): dialog=0x7f812f2585e8, type=64 May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_req_within.c:219]: bye_reply_cb(): first final reply May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_hash.c:872]: dlg_unref(): unref dlg 0x7f812f2585e8 with 2 - 3 May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_handlers.c:324]: dlg_iuid_sfree(): freeing dlg iuid [1231:1142] (0x7f812f2529f0) May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: tm [t_reply.c:1653]: cleanup_uac_timers(): DEBUG: cleanup_uac_timers: RETR/FR timers reset May 4 18:09:42 vps-host /usr/sbin/kamailio[24484]: DEBUG: dialog [dlg_var.c:81]: cb_dlg_locals_reset(): resetting the local dialog shortcuts on script callback: 2147483652 ... May 4 18:10:02 vps-host /usr/sbin/kamailio[24484]: DEBUG: core [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil) May 4 18:10:02 vps-host /usr/sbin/kamailio[24484]: DEBUG: core [receive.c:298]: receive_msg(): receive_msg: cleaning up May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: tm [t_reply.c:1294]: t_should_relay_response(): - T_code=0, new_code=408 May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: tm [t_reply.c:2080]: local_reply(): DEBUG: local_reply: branch=0, save=0, winner=0 May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: tm [t_reply.c:2117]: local_reply(): DEBUG: local transaction completed May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: tm [t_hooks.c:288]: run_trans_callbacks_internal(): DBG: trans=0x7f812f256fd0, callback type 1024, id 0 entered May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: dialog [dlg_req_within.c:255]: dlg_ka_cb(): receiving a final reply 408 May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: dialog [dlg_hash.c:663]: dlg_lookup(): no dialog id=1142 found on entry 1231 May 4 18:10:02 vps-host /usr/sbin/kamailio[24488]: DEBUG: dialog [dlg_handlers.c:324]: dlg_iuid_sfree(): freeing dlg iuid [1231:1142] (0x7f812f252ba0) May 4 18:10:02 vps-host /usr/sbin/kamailio[24493]: DEBUG: dialog [dlg_hash.c:663]: dlg_lookup(): no dialog id=1142 found on entry 1231 May 4 18:10:02 vps-host /usr/sbin/kamailio[24493]: DEBUG: dialog [dlg_hash.c:663]: dlg_lookup(): no dialog id=11917 found on entry 68 May 4 18:10:02 vps-host /usr/sbin/kamailio[24493]: DEBUG: dialog [dlg_hash.c:663]: dlg_lookup(): no dialog id=1142 found on entry 1231 May 4 18:10:02 vps-host /usr/sbin/kamailio[24493]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7f812f252ad0/0x7f812f252b08) - ignore May 4 18:10:02 vps-host /usr/sbin/kamailio[24493]: DEBUG: dialog [dlg_hash.c:663]: dlg_lookup(): no dialog id=11917 found on entry 68 etc... Cheers, Dirk Teurlings On 07-05-15 09:03, Daniel-Constantin Mierla wrote: Hello, thanks for reporting and troubleshooting. Can you refer to the code (file+lines) for step 3 and 4? It will save me some time to look into the code and fix the issue. Cheers, Daniel On 07/05/15 08:46, Dirk Teurlings - SIGNET B.V. wrote: Hi, (Kamailio 4.2.3) Working to get dialogs closed and cleaned up nicely I'm looking into the ka_interval and ka_timer parameter of the dialog module. The following is now happening. Scenario: 1.
[SR-Users] kamailio V 4.2.4 IMS_Charging ro_session_timeout question
Hello; i am trying to understand how is ims_charging working . Kamailio is a S-CSCF here. kamailio and call dont have a problem but ro_session. i always get ro_session_ontimeout() ERROR. when look diameter trace , ims_charging module dont request for 30 more sec for granted and kill dialog. Thanks for helps. 14:22:51S-CSCF -CC-Time 15 .. Sec CCR --- Java-Diamaeter Server (INITIAL REQ) 14:22:51S-CSCF -CC-Time 15 .. Sec CCA --- Java-Diamaeter Server (INITIAL REQ) 14:23:01S-CSCF -CC-Time 10 .. Sec CCR --- Java-Diamaeter Server (UPDATE ) 14:23:01S-CSCF -CC-Time 30 .. Sec CCA --- Java-Diamaeter Server (UPDATE ) 14:23:31S-CSCF -CC-Time 30 .. Sec CCR --- Java-Diamaeter Server (TERMINATE ) 14:23:31S-CSCF -CC-Time 30 .. Sec CCA --- Java-Diamaeter Server (TERMINATE ) -- LOG - May 7 14:23:31 /usr/local/sbin/kamailio[7602]: ERROR: ims_charging [ro_timer.c:449]: ro_session_ontimeout(): Diameter call session - event [2] May 7 14:23:31 /usr/local/sbin/kamailio[7602]: INFO: ims_charging [ro_timer.c:452]: ro_session_ontimeout(): Call/session must be ended - no more funds. May 7 14:23:31 /usr/local/sbin/kamailio[7600]: WARNING: ims_charging [dialog.c:167]: dlg_terminated(): inconsistent ro timer data on ro_session 0x7ff1eb4543b8 [] CFG -- $var(cc_ret) = Ro_CCR(CHARGING_CCR_REPLY, orig, SCUR, , 15, location); CFG -- ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] db_mongodb get columns error
Hello, On 07/05/15 09:29, Mickael Marrache wrote: Hi, Sorry not to have answered before, I just did a restart and there was no error. We don't restart often so I can't tell you how often this issue appears but I will keep an eye on it. It may be a bug in the insert or update code in db_mongodb that misses the caller_sock column but I'm not sure. Is it possible a dialog is inserted without caller_sock field? Or, is it possible $unset is used somewhere for the caller_sock? iirc, the socket for both caller and callee should be set when the dialog is inserted. Cheers, Daniel Mickael *From:*Daniel-Constantin Mierla [mailto:mico...@gmail.com] *Sent:* Thursday, May 07, 2015 10:23 AM *To:* Kamailio (SER) - Users Mailing List; Mickael Marrache *Subject:* Re: [SR-Users] db_mongodb get columns error Hello, On 27/04/15 23:46, Daniel-Constantin Mierla wrote: Hello, On 22/04/15 14:00, Mickael Marrache wrote: Hi, After restarting Kamailio, I got the following errors during the startup: kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:381]: db_mongodb_get_columns(): field [caller_sock] not found in result iterator kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:739]: db_mongodb_store_result(): failed to set the columns kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:918]: db_mongodb_query(): failed to store result kamailio[12614]: ERROR: db_mongodb [mongodb_dbase.c:927]: db_mongodb_query(): failed to do the query kamailio[12614]: ERROR: dialog [dlg_db_handler.c:257]: select_entire_dialog_table(): Error while querying database What may be causing the issue? I should always have a caller_sock in every dialog document. the error is thrown when the caller_sock field is not found in the b/json document returned by mongodb. Do you get the error every time you restart? Any update on this? As I am spending some time with testing for 4.3, I would like to close this issue if there is something to fix. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] kamailio V 4.2.4 IMS_Charging ro_session_timeout question
Thanks Carsten; As you wrote , in Update transaction there is Final Unit.. it is all problem. Thanks. I read your blog and stories. These are really cool. I winned to fight with our manager about IMS and begin to diggin IMS. if i succes i am gonna entegrate to IMS our Voice system. Could you give me any book ,pdf advice to learn Diameter CSCF . And does CSCF supports User-Data Request/Answer ? Thanks -- View this message in context: http://sip-router.1086192.n5.nabble.com/kamailio-V-4-2-4-IMS-Charging-ro-session-timeout-question-tp137628p137641.html Sent from the Users mailing list archive at Nabble.com. ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio proxy for far-end nat traversal
Hi Daniel I have rtpproxy to perform media relaying. The case where it just timeouts: 1. Client A behind NAT (wifi) calling Client B on 3G Sent from Samsung Mobile Original message From: Daniel-Constantin Mierla mico...@gmail.com Date:05/05/2015 12:52 (GMT+05:30) To: Kamailio (SER) - Users Mailing List sr-users@lists.sip-router.org Subject: Re: [SR-Users] Kamailio proxy for far-end nat traversal Hello, do you have rtpproxy or rtpengine for relaying rtp packets? Kamailio is routing only sip packets, you need the rtp relay application to help with media streams. Cheers, Daniel On 01/05/15 13:15, rahul.ultimate wrote: Hello I need a small guidance on creating a light weight proxy which only forwards the msgs to my sip server and also does supports symmetrical nated clients. The way I have created the configuration is a slight modification of : https://github.com/xlab1/sipfe_kamailio/blob/master/kamailio.cfg Problem is unless the sip clients use STUN media packets are not routed. And sometimes even the signalling does not pass through. Should i not use fix_nated_register and switch to fix _ nated_contact always ? Because in all those cases where signalling does not pass through, I see RTO. My best guess is kamailio trying to communicate with private ip. Anything which I can try that you could suggest from the top of yourmind woyld be muc appreciated. Thanks Rahul Sent from Samsung Mobile ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Kamailio authentication method
Still on the subject, we are exploring the possibilities and one of them would be to use the diameter module. As stated in the documentation : NOTE: diameter support was developed for DISC (DIameter Server Client project at http://developer.berlios.de/projects/disc/). This project seems to be no longer maintained and DIAMETER specifications were updated in the meantime. Thus, the module is obsolete and needs rework to be usable with opendiameter or other DIAMETER servers. Is it planned to update this module on your side on not? One other solution would be to write our own module to connect to another server (which contains the users/passwords and calculate the HA1 and HA2 values), tcp layer would still be done by auth module. To do that, is there a spec on how to communicate with auth module? And any documentation on custom module development and deployment? The principle would be more or less the same as diameter, but maybe our server would not use radius nor diameter protocols. By doing it, we try to reach two goals : use SHA instead of MD5 and increase the security of the user management by hosting it in a different way as Kamailio does. Thank you, Frederic From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Wednesday 6 May 2015 16:44 To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Kamailio authentication method Hello, to understand properly, do you need to have: HA1=SHA(username:realm:password) HA2=SHA(method:digestURI) response=SHA(HA1:nonce:HA2) Perhaps it can be done with config file scripting, if you are familiar with transformations and header manipulation. But I think it will be simpler to extend auth module to support different hashing algorithm. The code for computing shaX is already in kamailio (used for shaX transformations), so the change in auth should be about advertising and detecting when the new algorithm has to be used. Cheers, Daniel On 06/05/15 16:28, Mathys Frédéric wrote: Hello, In my scenario with a Kamailio server, I have a VOIP client connecting to the server which, for some reasons, cannot calculate MD5 hashes but only SHA. In this situation, would it be possible to change the authentication algorithm by either modifying Kamailio scripts or writing an external module to do that? As far as I know, the authentication response is calculated as follow (standard HTTP Digest authentication) : HA1=MD5(username:realm:password) HA2=MD5(method:digestURI) response=MD5(HA1:nonce:HA2) For that, I have to save ha1 and ha1b values in the DB with the SHA function directly (with a trigger for example), and then change the authentication method too. What is the best solution to do that? Does a module already exists? Thank you! Frederic Mathys System Integration Validation ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.orgmailto:sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] permissions module, regular expression matching Request URI
Hello, I've submitted the pull request. Please review and let me know, thank you. Emmanuel On Wed, May 6, 2015 at 5:57 PM, Daniel-Constantin Mierla mico...@gmail.com wrote: Hello, can you create a pull request to github project: - https://github.com/kamailio/kamailio It will make the review process easier as we can add comments to the patch, if needed. If all ok, the patch will be merged once the development is unfrozen -- now we are in the testing period for next major release 4.3. Cheers, Daniel On 06/05/15 22:11, E. Schmidbauer wrote: Hello, I have written a patch to add checking for the Request-URI. Please see attached diff. I hope you consider pushing this code upstream. Thanks, Emmanuel On Wed, May 6, 2015 at 12:14 PM, Vik Killa vipki...@gmail.com wrote: Hello, We would like to match specific calls based on two factors: 1. the source IP address 2. the Request URI I see in the permissions module, it is possible to match based on the Source IP + the From URI. We need two match both in order to return the appropriate 'tag' attribute from table. Would anyone know of a way to accomplish this? Also, I noticed that matching source IP + from uri, you cannot control which result is returned by permissions module based on regular expression. In other words if more than one match is made, permissions module seems to return the first result. Thank you and I look forward to your response. V ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-us...@lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Keep-Alive in dialog freeing a free fragment
Hi Daniel, Good to see you found an improvement, not sure yet if it'll help us. Here is the non-debug log first. Just now I noticed that the initial dialog doesn't get ended as well now, 5fa4dc3670596fb626269f083b0c9480 in the log. The setup is like this Leg 1 Kamailio - Asterisk Leg 2 (initialized by Asterisk) - Kamailio - Gateway First the output of ps Process:: ID=0 PID=21528 Type=attendant Process:: ID=1 PID=21530 Type=udp receiver child=0 sock=127.0.0.1:5060 Process:: ID=2 PID=21531 Type=udp receiver child=0 sock=192.168.10.246:5060 Process:: ID=3 PID=21532 Type=udp receiver child=0 sock=31.223.168.246:5060 Process:: ID=4 PID=21533 Type=udp receiver child=0 sock=[::1]:5060 Process:: ID=5 PID=21534 Type=udp receiver child=0 sock=[2001:4cb8:34a:10::246]:5060 Process:: ID=6 PID=21535 Type=slow timer Process:: ID=7 PID=21536 Type=timer Process:: ID=8 PID=21537 Type=MI FIFO Process:: ID=9 PID=21538 Type=ctl handler Process:: ID=10 PID=21539 Type=TIMER NH Process:: ID=11 PID=21540 Type=Dialog KA Timer Process:: ID=12 PID=21541 Type=Dialog Clean Timer Process:: ID=13 PID=21542 Type=WLCC TB TIMER Process:: ID=14 PID=21543 Type=LLCC TB TIMER Process:: ID=15 PID=21544 Type=tcp receiver (generic) child=0 Process:: ID=16 PID=21545 Type=tcp main process And the log May 7 18:54:43 vps-host /usr/sbin/kamailio[21532]: INFO: script: 5fa4dc3670596fb626269f083b0c9480@192.168.10.245:5060 - CC, dialog:start May 7 18:54:44 vps-host /usr/sbin/kamailio[21531]: INFO: script: 4d263e35-89ea921c@172.16.0.205 - CC, dialog:start May 7 18:55:57 vps-host /usr/sbin/kamailio[21535]: INFO: script: 123 - CC, dialog:end May 7 18:55:57 vps-host /usr/sbin/kamailio[21535]: INFO: script: 123 - WLCC: ENDCALL May 7 18:55:57 vps-host /usr/sbin/kamailio[21531]: WARNING: dialog [dlg_req_within.c:212]: bye_reply_cb(): inconsitent dlg timer data on dlg 0x7fa76e546600 [869:4705] with clid '5fa4dc3670596fb626269f083b0c9480@192.168.10.245:5060' and tags 'as155a87b8' '95b0a07565f99244i0' May 7 18:55:57 vps-host /usr/sbin/kamailio[21531]: INFO: script: 4d263e35-89ea921c@172.16.0.205 - CC, dialog:end May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54a4a8/0x7fa76e54a4e0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54aeb8/0x7fa76e54aef0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54a4a8/0x7fa76e54a4e0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54aeb8/0x7fa76e54aef0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54a4a8/0x7fa76e54a4e0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54aeb8/0x7fa76e54aef0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54a4a8/0x7fa76e54a4e0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54aeb8/0x7fa76e54aef0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54a4a8/0x7fa76e54a4e0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54aeb8/0x7fa76e54aef0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54a4a8/0x7fa76e54a4e0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54aeb8/0x7fa76e54aef0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54a4a8/0x7fa76e54a4e0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54aeb8/0x7fa76e54aef0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54a4a8/0x7fa76e54a4e0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54aeb8/0x7fa76e54aef0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core [mem/f_malloc.c:599]: fm_free(): freeing a free fragment (0x7fa76e54a4a8/0x7fa76e54a4e0) - ignore May 7 18:56:17 vps-host /usr/sbin/kamailio[21540]: INFO: core
Re: [SR-Users] kamailio V 4.2.4 IMS_Charging ro_session_timeout question
Hi Yasin, can you check, if the CCA to the Update has the final unit indicator set? If the CCA (for the Update) has this flag set, then we should not ask anymore, as it is the final unit. Thanks, Carsten 2015-05-07 13:59 GMT+02:00 Yasin CANER yasin.ca...@netgsm.com.tr: Hello; i am trying to understand how is ims_charging working . Kamailio is a S-CSCF here. kamailio and call dont have a problem but ro_session. i always get ro_session_ontimeout() ERROR. when look diameter trace , ims_charging module dont request for 30 more sec for granted and kill dialog. Thanks for helps. 14:22:51S-CSCF -CC-Time 15 .. Sec CCR --- Java-Diamaeter Server (INITIAL REQ) 14:22:51S-CSCF -CC-Time 15 .. Sec CCA --- Java-Diamaeter Server (INITIAL REQ) 14:23:01S-CSCF -CC-Time 10 .. Sec CCR --- Java-Diamaeter Server (UPDATE ) 14:23:01S-CSCF -CC-Time 30 .. Sec CCA --- Java-Diamaeter Server (UPDATE ) 14:23:31S-CSCF -CC-Time 30 .. Sec CCR --- Java-Diamaeter Server (TERMINATE ) 14:23:31S-CSCF -CC-Time 30 .. Sec CCA --- Java-Diamaeter Server (TERMINATE ) -- LOG - May 7 14:23:31 /usr/local/sbin/kamailio[7602]: ERROR: ims_charging [ro_timer.c:449]: ro_session_ontimeout(): Diameter call session - event [2] May 7 14:23:31 /usr/local/sbin/kamailio[7602]: INFO: ims_charging [ro_timer.c:452]: ro_session_ontimeout(): Call/session must be ended - no more funds. May 7 14:23:31 /usr/local/sbin/kamailio[7600]: WARNING: ims_charging [dialog.c:167]: dlg_terminated(): inconsistent ro timer data on ro_session 0x7ff1eb4543b8 [] CFG -- $var(cc_ret) = Ro_CCR(CHARGING_CCR_REPLY, orig, SCUR, , 15, location); CFG -- ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Carsten Bock CEO (Geschäftsführer) ng-voice GmbH Schomburgstr. 80 D-22767 Hamburg / Germany http://www.ng-voice.com mailto:cars...@ng-voice.com Office +49 40 5247593-0 Fax +49 40 5247593-99 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/ ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Re: [SR-Users] Recommended configuration for TCP support
Thanks for your explanation, the problem is that the actual lookup is done by a proxy which is located after our load balancer. Therefore, the TCP connection with the UA should not be visible by the proxy but by the load balancer. How does that work in such case? From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Vitaliy Aleksandrov Sent: Wednesday, May 06, 2015 10:34 AM To: sr-users@lists.sip-router.org Subject: Re: [SR-Users] Recommended configuration for TCP support set_forward_no_connect() called after lookup() prevents kamailio from making a new connection to a phone if there is no active connection. This is useful when you are trying to call to a UA which kamailio still keeps registration record for, but TCP/TLS connect to this phone is already gone (due to timeout, network problem, etc...). On 05/05/15 14:54, Mickael Marrache wrote: In general, it happens in our network (as more and more Via headers are added). Sorry, I didn't understand your last sentence. What do you mean by not connect if there is no active connection after location lookup? From: sr-users [mailto:sr-users-boun...@lists.sip-router.org] On Behalf Of Daniel-Constantin Mierla Sent: Monday, May 04, 2015 11:07 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Recommended configuration for TCP support Hello, where are typically those issues with truncated SDP? On the phones? If you use tcp and have phones behind the nat, it is recommended to not connect if there is no active connection after location lookup -- see core functions for tcp. Cheers, Daniel On 04/05/15 13:54, Mickael Marrache wrote: Hi, We sometimes get issues caused by truncated SDP bodies. Therefore, we are looking at using TCP instead of UDP. What is the recommended configuration when TCP is used? Currently, I only have the following: children=16 listen=udp:ip:5060 listen=tcp:ip:5060 disable_tcp=no tcp_connection_lifetime=605 (registration expiry is 600) Also, is there a difference with UDP regarding NAT handling? Thanks, Mickael ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla http://twitter.com/#!/miconda http://twitter.com/#%21/miconda - http://www.linkedin.com/in/miconda Kamailio World Conference, May 27-29, 2015 Berlin, Germany - http://www.kamailioworld.com ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ___ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
