sr-users

sr-users@lists.kamailio.org

42 participants
37517 discussions

Push proxy and load balancer for asterisk?
by Gerrit Jacobsen 29 May '19

29 May '19

Good morning, I want to realise a push notification proxy to signal incoming calls from asterisk to softphones. Is Kamailio the preferred solution for this? I looked also at Flexisip and Asterisk scripts and was told by a seasoned professional that Kamailio is the preferable solution as its scalable. True? I would be glad if someone could share his experiences. Also can one Kamailio instance be used as an asterisk load balancer and also push notification proxy ? I have been a heavy openser user a long time ago. I used first openser as my core routing engine but then switched to yate. Please excuse my rather broad questions. From my experience with Openser the devil is in the detail. So any hints on where this setup may cause problems would be great. Thanks a lot for your input. Gerry

3 2

Kamailio Lord Balance
by Gaurav Bmotra 29 May '19

29 May '19

hi i m using kamailio 5.1 with Ubuntu 18.04.2 LTS and freeswitch as Media server -- *Regards:* Gaurav Kumar

4 4

RFC: split out old sr api from app_lua
by Daniel-Constantin Mierla 29 May '19

29 May '19

Hello, I am considering to split the app_lua module in order to move the older style API available under Lua 'sr' module in a dedicated module (like app_lua_sr). Later this module can be obsoleted and removed, once we know that everything there is covered by KEMI KSR Lua module. In this way, we make it more clear that KSR is the preferred API to use as well have the app_lua smaller, for those using only KSR and not needing 'sr' API. Therefore I am starting the discussion to see if anyone has something against or other suggestions. I cc-ed sr-dev to make developers aware, but I think the best place for discussion is sr-users, being related to how Kamailio is used, therefore reply only to sr-users. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 2

RTPEngine / Transcoding question
by Carsten Bock 29 May '19

29 May '19

Hi, I want to implement selective transcoding, e.g. avoiding Transcoding between a HD codec (G722) and a non HD Codec (G711). In case the caller does offer HD codecs, this is fine, e.g. if(sdp_with_codecs_by_name("G722,OPUS")) { rtpengine_offer("codec-transcode=OPUS codec-transcode=G722 codec-transcode=PCMA"); } else { rtpengine_manage("codec-transcode=PCMA"); } Now I have the issue, if the callee only sends me G711, I don't want to offer G722 or Opus to the caller. However, rtpengine_answer() does not seem to accept "codec-strip=G722 codec-strip=OPUS", e.g.: onreply_route() { if(!sdp_with_codecs_by_name("G722,OPUS")) { rtpengine_ manage("codec-strip=OPUS codec-strip=G722"); } } As a result, the SDP always contains the transcoding options, e.g. G722 and OPUS. I always end up in transcoding G722 to G711, which is meaningless in that case. Any ideas on how to solve that? (above examples very simplified) Thanks, Carsten -- Carsten Bock I Managing Director ng-voice GmbH Millerntorplatz 1 I 20359 Hamburg I Germany www.ng-voice.com Mobile +49 (0)179-20 21 244 I Direct +49 (0)40-52 47 593-40 I Fax +49 (0)40-52 47 593-99 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock, Dr. David Bachmann Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/

2 5

RTPEngine: rtpengine_manage(), Subsequent requests, Transcoding
by Carsten Bock 29 May '19

29 May '19

Hi, quick question: If understood it correctly in the past (and it worked for me quite well this way), I can simply call rtpengine_manage() for subsequent requests without adding any additional information (e.g. used interfaces, RTP/SRTP translation or anything like that), as this information is stored in the internal hash table of the RTPEngine module during call setup and initial offer/answer. However, this does not seem to apply to the transcoding options. When I just call "rtpengine_manage()" for a Re-INVITE of a transcoded call (in my case AMR-WB to G722), the transcoding options are no longer applied. The forwarded offer does not get the transcoded codecs added (e.g. in my case G722 is not added to the list of AMR/AMR-WB from the phone). Did I misunderstand something or is it a bug? My RTPEngine is still on 7.2, but I will double check with more recent versions today or tomorrow. However, I also found no commit messages relating to this. Thanks, Carsten -- Carsten Bock I Managing Director ng-voice GmbH Millerntorplatz 1 I 20359 Hamburg I Germany www.ng-voice.com Mobile +49 (0)179-20 21 244 I Direct +49 (0)40-52 47 593-40 I Fax +49 (0)40-52 47 593-99 Sitz der Gesellschaft: Hamburg Registergericht: Amtsgericht Hamburg, HRB 120189 Geschäftsführer: Carsten Bock, Dr. David Bachmann Ust-ID: DE279344284 Hier finden Sie unsere handelsrechtlichen Pflichtangaben: http://www.ng-voice.com/imprint/

3 2

Call Routing at IMS
by Iman Mohammadi 29 May '19

29 May '19

Hi Everyone When P-CSCF receives INVITE from client it sends INVITE to S-CSCF then S-CSCF without any look up(checking the user is registered or not)sends INVITE to I-CSCF then I-CSCF sends LIR and receives LIA and sends INVITE to same S-CSCF (in case of one S-CSCF exists).My Question is here why without any look up S-CSCF sends INVITE to I-CSCF??this procedure affects system performance and increases call set up time

2 1

WebRTC bad message (offset: 22)
by Ilie Soltanici 28 May '19

28 May '19

Hello, Can someone help me to discard those messages from kamailio log files? ERROR: <core> [core/parser/parse_fline.c:262]: parse_first_line(): parse_first_line: bad message (offset: 22) ERROR: <core> [core/parser/msg_parser.c:681]: parse_msg(): ERROR: parse_msg: message=<HTTP/1.1 101 Switching Protocols#015#012Sia: SIP/2.0/TLS 212.2.161.34:60477#015#012Sec-WebSocket-Protocol: sip#015#012Upgrade: websocket#015#012Connection: upgrade#015#012Sec-WebSocket-Accept: VeiXbJClWneIrIyYgM5v3XKYHLA=#015#012Server: WebRTC GW#015#012Content-Length: 0#015#012#015#012> As I understand this is just an HTTP response to the first request, and shouldn't go through config file execution, but I don't understand why it is getting through it. Thank you

1 0

kamailio webrtc 183 early media.
by Zhan Bazarov 28 May '19

28 May '19

Hello! I have setup kamailio+rtpengine+asterisk.. And I have issue with early media for WEBrtc endpoints... As I understood right, for this case I need to use rel100(PRACK) for sending early media... But I didn't find any example for solve this issue... Can you help me with it? It would be greatly appreciated!

1 0

mem leak on 5.1.2?
by Andrew Chen 27 May '19

27 May '19

Hey guys, Need some help with possible run away memory issue on my 5.1.2 Kamailio. I noticed I'm getting this memory error from kam logs: May 24 13:47:52 ashintgtpsg51 /usr/sbin/kamailio[1857]: WARNING: http_client [functions.c:298]: curL_query_url(): Curl library out of memory (url:https://<some url>) my -m on kamailio startup is currently set to 64 but there is only 1 call going through. In our check_mk, I noticed the memory usage is ramping up: [image: image.png] What's the cause of this? -- Andy Chen Sr. Telephony Lead Engineer achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

4 8

Getting the following error when sending INVITE request for calling
by Mohit Chawla 27 May '19

27 May '19

Hi , I am getting the following error in trying to send INVITE message from SIP client. {2 2 INVITE 4_Do2VIMWLR6Wf5ubiBxgg..} NOTICE: acc [acc.c:281]: acc_log_request(): ACC: transaction answered: timestamp=1558902843;method=INVITE;from_tag=69588468;to_tag=ebd29a60;call_id=4_Do2VIMWLR6Wf5ubiBxgg..;code=200;reason=OK;src_user=1016;src_domain=172.25.22.23;src_ip=172.25.22.40;dst_ouser=1015;dst_user=1015;dst_domain=172.25.22.40 May 27 02:04:03 epc-srv-03 /usr/sbin/kamailio[17238]: {2 2 INVITE 4_Do2VIMWLR6Wf5ubiBxgg..} ERROR: db_mysql [km_dbase.c:128]: db_mysql_submit_query(): driver error on query: Unknown column 'src_user' in 'field list' (1054) May 27 02:04:03 epc-srv-03 /usr/sbin/kamailio[17238]: {2 2 INVITE 4_Do2VIMWLR6Wf5ubiBxgg..} ERROR: <core> [db_query.c:243]: db_do_insert_cmd(): error while submitting query May 27 02:04:03 epc-srv-03 /usr/sbin/kamailio[17238]: {2 2 INVITE 4_Do2VIMWLR6Wf5ubiBxgg..} ERROR: acc [acc.c:477]: acc_db_request(): failed to insert into database May 27 02:04:10 epc-srv-03 /usr/sbin/kamailio[17229]: {2 3 BYE 4_Do2VIMWLR6Wf5ubiBxgg..} NOTICE: acc [acc.c:281]: acc_log_request(): ACC: transaction answered: *Can anyone help me understand the reason for this error.* *I am attaching the used kamailio.cfg file in this message.* *Thanks and Regards,* *Mohit* -- _Disclaimer: This email and any files transmitted along with it may contain Azcom confidential and proprietary information. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action based on the contents of the information contained herein is strictly prohibited. If you are not an intended recipient of this transmission and you received it in error, please inform the sender by reply e-mail and destroy this and all other copies of this transmission to which you have access. The sender of this email or Azcom does not accept liability for any errors or omissions in the contents of this message that may occur as a result._

2 6

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users