sr-users December 2014

sr-users@lists.kamailio.org

84 participants
123 discussions

by Cibin Paul

Hi, I have a kamailio 4.1 as a gateway and registrar behind asterisk servers. On asterisk, I save the IP address of the originating call parsing the SIPURI or SIPCHANNEL(recvip). In both cases, I am receiving the private ip of the user agent registered with kamailio. Do I need to change anything in kamailio to receive the actual IP address. Please suggest. Regards Cibin

9 years, 4 months

Meddling with password during authentication

by Olli Heiskanen

Hello all, During authentication, is there any way to affect the password user is sending? I do suspect not as it is a clear security matter, but won't hurt to ask. I use auth_db module with calculate_ha1 parameter set to 1. For reasons in integrating Kamailio into my system architecture there is a need to store a password in some other format than for example md5('555:domain.com:password)') while not allowing any passwords to be stored as plaintext. For example: md5('555:domain.com:md5('password')') but this would require me to hash the password before authentication, in Kamailio script as I can't do it in the clients. Reason for this question is to have my users in a separate database, and these users could have 0-n sip peers assigned to them, and have users authenticate to my software and the sip peers using the same password. cheers, Olli

9 years, 4 months

Authorization Issue kamailio 4.2

by Ahmed Salem

Hi, I'm using kamailio 4.2 some of my clients are getting 401 unauthorized after a couple of days of usage without any problems, their usernames and passwords are still in the database server unchanged. Any idea what's going on? Thanks Ahmed

9 years, 4 months

Merry Christmas!

by Daniel-Constantin Mierla

Another year getting slowly to the end, an excellent opportunity to thank to all old and new friends of Kamailio project, from contributing code to using it, helping on mailing lists and other places online, or advertising it across the world! Merry Christmas and Happy Winter Holidays! Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

9 years, 4 months

Media trouble with kamailio/rtpengine

by Marc Soda

I'm trying to use Kamailio and rtpengine as a webrtc gateway. I'm not getting audio back to my browser. From a packet capture I can see media from the browser to rtpengine, and then bi-directional RTP back and forth from my asterisk server, but rtpengine is not sending the media on to the browser, i.e.: browser ---------> kamailio/rtpengine <---------> asterisk This is the output from rtpengine: https://gist.github.com/marcantonio/bfe72644306b205cc7e1 Thanks.

9 years, 4 months

Dispatcher weight nor working

by Yuriy Gorlichenko

Hello. We use kamailio 4.3 and dispatcher with 9 algorithm. We use db instanse for dispatcher and at attrs column for our backend servers set WEIGHT=40 and 60 for first and second server, but packets sended only at first server ignoring weight

9 years, 4 months

Re: [SR-Users] Mediaproxy do not work well with Kamailio SIP server issue

by Alfred C.M. Lu

|---------+-----------------------------> | | dong-ming.li(a)mail.| | | foxconn.com | | | | | | 2014/12/24 上午 | | | 11:54 | |---------+-----------------------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| | | | To: alfred.lu(a)foxconn.com | | cc: | | Subject: Mediaproxy do not work well with Kamailio SIP server issue | >--------------------------------------------------------------------------------------------------------------------------------------------------| Secret Level: |------------------------| | ( ) 1.Non-Confidential | | ( ) 2.Confidential | | ( ) 3.Secret | | ( ) 4.Top Secret | |------------------------| Priority Level: |--------------------| | ( ) 1.Normal | | ( ) 2.Urgent | | ( ) 3.Extra Urgent | |--------------------| ------------------------------------------------------------------------- Hi, sir, We try to setup Mediaproxy on CentOS 6.6 with kamailio-4.2.1 SIP server. We use Linphone android version as SIP client to test. attached kamailio.cfg.txt is our kamailio-4.2.1 SIP server config file. pls help to rename kamailio.cfg.txt to kamailio.cfg. kamailio-4.2.1 SIP server is run on public IP server,and Linphone SIP client is run behind NAT. The problem is that only callee can hear caller's rtp audio data. caller can not hear callee's audio data. And the call will auto disconnect after about 30s time out. Below's our modification regarding the kamailio.cfg file,pls help to check if this is OK or not ? #foxconn gallice add start #### MediaProxy module loadmodule "mediaproxy.so" modparam("mediaproxy", "disable", 0) modparam("mediaproxy", "ice_candidate", "high-priority") modparam("mediaproxy", "mediaproxy_socket", "/var/run/mediaproxy/dispatcher.sock") modparam("mediaproxy", "mediaproxy_timeout", 500) modparam("mediaproxy", "signaling_ip_avp", "$avp(nat_ip)") modparam("mediaproxy", "media_relay_avp", "$avp(media_relay)") #foxconn gallice add end # account only INVITEs if (is_method("INVITE")) { setflag(FLT_ACC); # do accounting use_media_proxy(); #foxconn gallice add } # Manage incoming replies onreply_route[MANAGE_REPLY] { xdbg("incoming reply\n"); if(status=~"[12][0-9][0-9]") { #foxconn gallice add #route(NATMANAGE); #foxconn gallice delete use_media_proxy(); #foxconn gallice add } #foxconn gallice add } For mediaproxy,we can see the media related processes are already run. 31212 ? SL 0:01 python ./media-dispatcher start 31218 ? SL 0:16 python ./media-relay start ***************************************************** dong-ming / 李東明 Foxconn Electronics Inc. HH Precision Ind. Co., Ltd. CNSBG NSDI TIPBU R&D Dept. LH Office 地址:深圳市龍華新區龍華東環二路二號富士康科技集團分機 : +86-0755-2812-9588 #26109 Mobile : 13510123670 Mail : dong-ming.li(a)mail.foxconn.com, ***************************************************** 溫馨提醒﹕入廠人員須遵守富士康出入管制,請勿攜帶手提電腦、各種攝像、U盤、MP3 等存儲設備本電子郵件及附件所載信息均為保密信息，受合同保護或依法不得洩漏。其內容僅供指定收件人按限定範圍或特殊目的使用。未經授權者收到此信息均無權閱讀、使用、複製、洩漏或散佈。若您因為誤傳而收到本郵件或者非本郵件之指定收件人，請即刻回覆郵件或致電Super Notes郵件客服熱線 560-104，並永久刪除此郵件及其附件和銷毀所有複印件。謝謝您的合作！ This e-mail message together with any attachments thereto (if any) is confidential, protected under an enforceable non-disclosure agreement, intended only for the use of the named recipient(s) above and may contain information that is privileged, belonging to professional work products or exempt from disclosure under applicable laws.Any unauthorized review, use, copying, disclosure, or distribution of any information contained in or attached to this transmission is STRICTLY PROHIBITED and may be against the laws. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender by e-mail or telephone at Super Notes support hotline 560-104 and delete this e-mail message and any attached documentation from your computer. Receipt by anyone other than the intended recipient(s) is not a waiver of any attorney-client or work product privilege. Thank you! mail from ip-->192.168.2.2 mail from pc-->MICROSOF-700F48 Version: Super Notes 1.6.4.5B (See attached file: kamailio.cfg.txt)

9 years, 4 months

TLS enable false.

by Thanh Truong

Hi all, I have tried several configure TLS in kamailio but no luck. Please give me some suggestion that I can make it work correctly. This is my configure in TLS module. modparam("tls", "tls_method", "SSLv23") modparam("tls", "private_key", "/usr/local/etc/kamailio/ca/privkey.pem") modparam("tls", "certificate", "/usr/local/etc/kamailio/ca/kamailio1_cert.pem") modparam("tls", "ca_list", "/usr/local/etc/kamailio/ca/calist.pem") modparam("tls", "verify_certificate", 1) modparam("tls", "require_certificate", 1) I am only getting issue with verify_certifiate = 1, it i let it to 0, my client can register correctly. When I set this flag, i got message from server as: Dec 18 10:26:31 17237 /usr/local/sbin/kamailio[12655]: ERROR: <core> [tcp_read.c:1279]: tcp_read_req(): ERROR: tcp_read_req: error reading Dec 18 10:26:46 17237 /usr/local/sbin/kamailio[12656]: ERROR: tls [tls_server.c:1193]: tls_read_f(): TLS accept:error:140890C7:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:peer did not return a certificate Dec 18 10:26:46 17237 /usr/local/sbin/kamailio[12656]: ERROR: <core> [tcp_read.c:1279]: tcp_read_req(): ERROR: tcp_read_req: error reading I Cant add any pem file into client, i have used Blink phone but no luck. Thank all in advance. ThanhTruong.

9 years, 4 months

[BOUNTY] Configs for Video calls between Linphone Android App and WebRTC clients (JsSIP, SIPML)

by Andrey Utkin

I hope the subject line says it all. I need to set up a backend to establish calls between browser clients and usual SIP clients, and the abovementioned applications are of the highest interest. (Of course, calls between same UAs must work, too.) If Linphone is not going to work due to its internal issues, then other established open source mobile apps for iOS and Android will be fine. Currently I have configured latest kamailio+rtpengine with configs from here https://github.com/caruizdiaz/kamailio-ws The calls pass this way currently: jssip -> android: no sound from phone to the browser, i see that jssip sends "sendonly" attribute for audio in INVITE's SDP. Audio from browser to phone, and both video streams appear immediately, everything is fine with them. android -> jssip: video from browser to the phone appears in 1-2 _minutes_ after the call is answered. All other media streams are fine. The above results are the same in such browsers [IP-] [ ] www-client/firefox-bin-31.3.0:0 [IP-] [ ~] www-client/google-chrome-unstable-41.0.2243.0_p1:0 With sipml currently i have no stable results, so it's hard to describe what happens. Please contact me if you have configs to make the needed things work, or if you have experience of such things working stable, and can configure it quickly. -- Andrey Utkin

9 years, 4 months

websocket ws_handle_handshake() error

by jaflong jaflong

Hi list, I am getting this error "ERROR: websocket [ws_handshake.c:153]: ws_handle_handshake(): retrieving connection" Any idea why? This is the debug log 12(24113) DEBUG: <core> [receive.c:154]: receive_msg(): After parse_msg... 12(24113) DEBUG: xhttp [xhttp_mod.c:358]: xhttp_handler(): new fake msg created (537 bytes): <GET /ws HTTP/1.1 Via: SIP/2.0/TLS 10.1.1.1:45968 Host: 10.1.1.2:10443 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:34.0) Gecko/20100101 Firefox/34.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate Sec-WebSocket-Version: 13 Origin: http://mydomain.co.uk Sec-WebSocket-Protocol: sip Sec-WebSocket-Key: GRbV+ovG+DKIBJtwb4pRiQ== Connection: keep-alive, Upgrade Pragma: no-cache Cache-Control: no-cache Upgrade: websocket > 12(24113) DEBUG: <core> [parser/msg_parser.c:623]: parse_msg(): SIP Request: 12(24113) DEBUG: <core> [parser/msg_parser.c:625]: parse_msg(): method: <GET> 12(24113) DEBUG: <core> [parser/msg_parser.c:627]: parse_msg(): uri: </ws> 12(24113) DEBUG: <core> [parser/msg_parser.c:629]: parse_msg(): version: <HTTP/1.1> 12(24113) DEBUG: <core> [parser/parse_via.c:2672]: parse_via(): end of header reached, state=5 12(24113) DEBUG: <core> [parser/msg_parser.c:513]: parse_headers(): parse_headers: Via found, flags=2 12(24113) DEBUG: <core> [parser/msg_parser.c:515]: parse_headers(): parse_headers: this is the first via 12(24113) DEBUG: sl [sl.c:288]: send_reply(): reply in stateless mode (sl) 12(24113) DEBUG: <core> [parser/msg_parser.c:106]: get_hdr_field(): found end of header 12(24113) DEBUG: <core> [msg_translator.c:205]: check_via_address(): check_via_address(10.1.1.1, 10.1.1.1, 0) 12(24113) DEBUG: <core> [tcp_main.c:2281]: tcpconn_send_put(): tcp_send: send from reader (24113 (12)), reusing fd 12(24113) DEBUG: <core> [tcp_main.c:2516]: tcpconn_do_send(): tcp_send: sending... 12(24113) DEBUG: <core> [tcp_main.c:2550]: tcpconn_do_send(): tcp_send: after real write: c= 0x7fc08162ad68 n=421 fd=7 12(24113) DEBUG: <core> [tcp_main.c:2551]: tcpconn_do_send(): tcp_send: buf= �/�*�޹��!��S��zo�e�/D��V�Gs��s�� ^cd��S"Ŏ�K��<�c7��4lx�<Z��#�c(AJ�8V��d� ��4bF��Wu�(�w�a� f��n��s�KjQv�݈�q|Z��64{Wk��Z\ױ��M�,[�Arٵ��Q�_��u�d�Gza�f��I�fI��z��Š9=��Ħ3�ȀJPx�}��S?��eVe��\id��y�wP�r(kZs��Z�"��4`�N_MR��z�!��Eb}��+�\;�8�3��V��l��M�|�1�2��VVK�@%�a�B&�P��k 12(24113) INFO: <script>: Received HTTP request to /ws from [10.1.1.1:45968] with protocol tls 14(24115) DEBUG: <core> [tcp_main.c:3565]: handle_ser_child(): handle_ser_child: read response= 7fc08162ad68, -1, fd -1 from 12 (24113) 14(24115) DEBUG: tls [tls_server.c:604]: tls_h_close(): Closing SSL connection 0x7fc081626e20 12(24113) ERROR: websocket [ws_handshake.c:153]: ws_handle_handshake(): retrieving connection 12(24113) DEBUG: sl [sl.c:288]: send_reply(): reply in stateless mode (sl) 12(24113) DEBUG: <core> [msg_translator.c:205]: check_via_address(): check_via_address(10.1.1.1, 10.1.1.1, 0) 12(24113) ERROR: sl [../../forward.h:247]: msg_send(): tcp_send failed 12(24113) ERROR: websocket [ws_handshake.c:113]: ws_send_reply(): sending reply 12(24113) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 12(24113) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 12(24113) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 12(24113) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 12(24113) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 12(24113) DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) 12(24113) DEBUG: <core> [xavp.c:448]: xavp_destroy_list(): destroying xavp list (nil) 12(24113) DEBUG: <core> [receive.c:298]: receive_msg(): receive_msg: cleaning up 12(24113) DEBUG: <core> [io_wait.h:610]: io_watch_del(): DBG: io_watch_del (0xa31f40, 7, -1, 0x10) fd_no=2 called 12(24113) DEBUG: <core> [tcp_read.c:1434]: release_tcpconn(): releasing con 0x7fc08162ad68, state -2, fd=7, id=3 12(24113) DEBUG: <core> [tcp_read.c:1435]: release_tcpconn(): extra_data 0x7fc081626e20 14(24115) DEBUG: <core> [tcp_main.c:3331]: handle_tcp_child(): handle_tcp_child: reader response= 7fc08162ad68, -2 from 2 9(24110) DEBUG: websocket [ws_conn.c:459]: wsconn_get_list(): wsconn_get_list

9 years, 4 months

← Newer
1
2
3
4
5
6
7
8
...
13
Older →

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 December 2014