sr-users

sr-users@lists.kamailio.org

10 participants
37525 discussions

Re: [SR-Users] uac.reg_refresh not removing records from memory
by DanB 22 Jun '16

22 Jun '16

Hey Daniel, Thanks for so fast feedback! No difference as far as I can tell before and after removing the record from db. I have also not disabled specifically the record inside uacreg table but completely removed it from db. I should mention that I have just upgraded to latest 4.4.1 so I should have the flags also saved in db. Here is the record before removal: """ root@iPBXDev1:/etc/ipbxrp# kamcmd -s tcp:127.0.0.1:2046 uac.reg_dump { l_uuid: rsua1_172.16.254.101 l_username: rsua1 l_domain: 172.16.254.101 r_username: cust_sua1 r_domain: 172.16.254.102 realm: auth_username: cust_sua1 auth_password: check123 auth_proxy: sip:172.16.254.102:5060 expires: 3600 flags: 20 diff_expires: 3588 timer_expires: 1466349066 reg_init: 1466345451 reg_delay: 0 } """ and the one after: """ root@iPBXDev1:/etc/ipbxrp# kamcmd -s tcp:127.0.0.1:2046 uac.reg_dump { l_uuid: rsua1_172.16.254.101 l_username: rsua1 l_domain: 172.16.254.101 r_username: cust_sua1 r_domain: 172.16.254.102 realm: auth_username: cust_sua1 auth_password: check123 auth_proxy: sip:172.16.254.102:5060 expires: 3600 flags: 20 diff_expires: 3526 timer_expires: 1466349066 reg_init: 1466345451 reg_delay: 0 } """ Also here is the command refreshing the record (after that is not longer in db): """ POST /jsonrpc HTTP/1.1. Host: 172.16.254.101:5090. User-Agent: Go-http-client/1.1. Content-Length: 85. Content-Type: application/json. Accept-Encoding: gzip. . {"jsonrpc":"2.0","method":"uac.reg_refresh","params":["rsua1_172.16.254.101"],"id":7} # T 2016/06/19 16:17:47.275473 172.16.254.101:5090 -> 172.16.254.102:58172 [AP] HTTP/1.1 200 OK. Sia: SIP/2.0/TCP 172.16.254.102:58172. Content-Type: application/json. Server: Sipean-RP 4.3.2. Content-Length: 36. . {"jsonrpc":"2.0","result":{},"id":7} """ Ta, DanB On 16.06.2016 12:00, sr-users-request(a)lists.sip-router.org wrote: > Message: 10 Date: Thu, 16 Jun 2016 08:17:53 +0200 From: > Daniel-Constantin Mierla <miconda(a)gmail.com> To: "Kamailio (SER) - > Users Mailing List" <sr-users(a)lists.sip-router.org> Subject: Re: > [SR-Users] uac.reg_refresh not removing records from memory > Message-ID: <76d9f2eb-26f7-c0db-8b74-37c93a5d3ef4(a)gmail.com> > Content-Type: text/plain; charset=utf-8 Hello, On 14/06/16 16:52, DanB > wrote: >> > >> >Hey Guys, >> > >> >I was wondering if there is any dynamic way today to remove a single >> >registration out of memory (and implicitly to force un-REGISTER) >> > >> >Eg: I add one record using uac.reg_refresh (which works fine) but after >> >removing the record from the database and executing uac.reg_refresh >> >again, the record stays in memory until expire. >> >Is there a better way to enforce un-register on remote side? >> > > do the flags in memory of the uac_reg account show that it is disabled? > > Cheers, > Daniel

4 3

WS to WS calls - No ACK received for 200OK
by Amit Patkar 21 Jun '16

21 Jun '16

Hi I am using Kamailio as Websocket proxy. User 1 & User 2 are registered on Kamailio over WebSocket. When User 1 calls User 2, User 2 gets ring and answers the call. 200 OK message is received by User 1 but ACK response sent by User 1 does not reach User 2. Since User 2 didn't get ACS, after 30 sec timeout it drops the call. Media is exchanged for 30 seconds, which means ICE is successful. I am running kamailio 4.3.3 on Kamailio is behind firewall and running on private IP. rtpengine is configured to handle media. All ports are forwarded to kamailio server and Kamailio is allowed to send data on any public IP. I used jssip & sipml framework to test. Result was same for both frameworks. No ACK received I can see following errors in log file. What could be the reason which indicate ACK was not forwarded Jun 21 14:55:41 acstemplate /usr/sbin/kamailio[6584]: NOTICE: acc [acc.c:317]: acc_log_request(): ACC: transaction answered: timestamp=1466501141;method=INVITE;from_tag=7926B9NR7U0X99ZfAr1T;to_tag=w3D2JGd2EUFJpobTcFyo;call_id=1edc8e15-f1f1-584d-df81-71c3d59d713d;code=200;reason=OK;src_user=10001;src_domain=xxxx.com;src_ip=xxx.yyy.zzz.aaa;dst_ouser=10002;dst_user=10002;dst_domain=df7jal23ls0d.invalid Jun 21 14:55:41 acstemplate /usr/sbin/kamailio[6582]: ERROR: <core> [forward.c:529]: forward_request(): cannot forward to af 2, proto 5 no corresponding listening socket Jun 21 14:55:41 acstemplate /usr/sbin/kamailio[6582]: ERROR: sl [sl_funcs.c:363]: sl_reply_error(): ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (7/SL) Jun 21 14:55:42 acstemplate /usr/sbin/kamailio[6584]: INFO: <script>: WS to WS Jun 21 14:55:42 acstemplate /usr/sbin/kamailio[6582]: ERROR: <core> [forward.c:529]: forward_request(): cannot forward to af 2, proto 5 no corresponding listening socket Jun 21 14:55:42 acstemplate /usr/sbin/kamailio[6582]: ERROR: sl [sl_funcs.c:363]: sl_reply_error(): ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (7/SL) Jun 21 14:55:46 acstemplate /usr/sbin/kamailio[6582]: ERROR: <core> [forward.c:529]: forward_request(): cannot forward to af 2, proto 5 no corresponding listening socket Jun 21 14:55:46 acstemplate /usr/sbin/kamailio[6582]: ERROR: sl [sl_funcs.c:363]: sl_reply_error(): ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (7/SL) Jun 21 14:55:51 acstemplate /usr/sbin/kamailio[6582]: ERROR: <core> [forward.c:529]: forward_request(): cannot forward to af 2, proto 5 no corresponding listening socket Jun 21 14:55:51 acstemplate /usr/sbin/kamailio[6582]: ERROR: sl [sl_funcs.c:363]: sl_reply_error(): ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (7/SL) Jun 21 14:55:57 acstemplate /usr/sbin/kamailio[6582]: ERROR: <core> [forward.c:529]: forward_request(): cannot forward to af 2, proto 5 no corresponding listening socket Jun 21 14:55:57 acstemplate /usr/sbin/kamailio[6582]: ERROR: sl [sl_funcs.c:363]: sl_reply_error(): ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (7/SL) Jun 21 14:56:13 acstemplate /usr/sbin/kamailio[6581]: ERROR: <core> [forward.c:529]: forward_request(): cannot forward to af 2, proto 5 no corresponding listening socket Jun 21 14:56:13 acstemplate /usr/sbin/kamailio[6581]: ERROR: sl [sl_funcs.c:363]: sl_reply_error(): ERROR: sl_reply_error used: I'm terribly sorry, server error occurred (7/SL) I searched list for similar issues but could not find match any Help to resolve this issue is appreciated. Thanks & Regards, Amit Patkar

3 4

Kamailio consult CNAM server through SIP Subscribe.
by José Seabra 21 Jun '16

21 Jun '16

Hello there, I need to use kamailio to consult an CNAM server in order to get the caller id name and number to the call, the diagram bellow represents what i need implement: Can I implement this behavior through the following kamailio modules: 1. tm and tmx module (call the function t_suspend and t_continue in order to stop INVITE transaction and resume it). 2. UAC module (generate the SUBSCRIBE sip message) 3. Some kamailio scripting logic to manage this behavior. what are your advices to implement this scenario? Thank you for your help Regards -- Cumprimentos José Seabra

4 17

kamailio question
by Irakli Nanobashvili 21 Jun '16

21 Jun '16

dear sr_users i have a little problem about kamailio sip server and who can help me ?

2 1

Equivalent of OpenSIP's binary interface in Kamailio
by Gholamreza Sabery 21 Jun '16

21 Jun '16

In OpenSIPS binary interface ( https://www.opensips.org/Documentation/Interface-Binary-2-2) provides a more efficient way of replicating state between multiple OpenSIPs instances. What is the equivalent feature in Kamailio? Regards

2 2

RTPENGINE rtp errors
by Dmitry 21 Jun '16

21 Jun '16

Hi 1)I encountered such errors when I make an internal call between 2 yate client SIP softphones:rtpengine is used and no audio: | Jun 19 10:02:35 kazootest2 rtpengine[2066]: [918508371(a)kazootest2.siplabs.local port 30942] Error parsing RTP header: short packet (header) when I turn off the rtpengine:THe Freeswitch handles such RTP packets correctly and audio is ok. I compared manually rtp packets from Yate: they comply to the RTP specification. 2) A call from WS client(jssip) to an ordinary sip softphone: | Jun 19 09:58:36 kazootest2 rtpengine[2066]: [s2m2k70tu0d12bjnnamr port 30814] Error parsing RTP header: invalid header version | How to fix these errors? The rtpengine looks through all incoming packets while looking for a new RTP stream. May be packets parsing is too strict? |

1 1

No other running SIP apllication on the machine.//答复: Kamailio ERROR "Address already in use" in tcp_init().
by joey.ren＠yulong.com 20 Jun '16

20 Jun '16

2 1

Kamailio dispatcher module - keep alives
by José Seabra 20 Jun '16

20 Jun '16

Hello there, I have a Kamailio server using dispatcher module to monitor several peers, some of them are in the same network, others are in an external network, for the peers that are in the external network kamailio has to send the OPTIONS(dispatcher keep alives) through another kamailio located in the border and acting as loadbalancer. If i set the dispatcher option "outbound_proxy" all SIP OPTIONS are sent to the outbound proxy configured and it isn't what i need, I need to have by some way a possibility to set outbound_proxy only for the peers that are located on the external network. How can I do that? Regards -- Cumprimentos José Seabra

3 5

Kamailio ERROR "Address already in use" in tcp_init().
by joey.ren＠yulong.com 20 Jun '16

20 Jun '16

3 2

Why SDPOPS does not remove attributes in SDP
by Dmitry 18 Jun '16

18 Jun '16

Hi allI have the following code: if($T_reply_code=="200") { if(has_body("application/sdp")) { xlog("L_INFO", "RTPENGINE received internal reply $T_reply_code $rr SDP extra lines will be removed"); set_rtpengine_set("0"); rtpengine_manage(); sdp_remove_line_by_prefix("a=rtcp"); sdp_remove_line_by_prefix("a=ssrc"); sdp_remove_line_by_prefix("a=ice"); sdp_remove_line_by_prefix("a=candidate"); xlog("L_INFO", "RTPENGINE received internal reply $T_reply_code $rr SDP extra lines removed with SDPOPS"); } }When I look through traces - I see that 200 ok(with SDP) has all these attributes and they are not removed. Why SDPOPS does not remove these attributes?

4 5

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