sr-users June 2019

sr-users@lists.kamailio.org

63 participants
93 discussions

ATCF/ATGW functionality
by Maryam Baghdadi 01 Jul '19

01 Jul '19

Hello, Is it possible to add ATCF/ATGW functionality in kamailio as P-cscf ? I have IMS network with kamailio as P-cscf, icscf, scscf and FHoss . ATCF/ATGW is necessary for handovers between 2G/3G and LTE networks.

2 3

Kamailio 5.x and Call_control module
by Efelin Novak 30 Jun '19

30 Jun '19

Hi Folks, I'm migrating to Kamailio 5.2.x from 4.4.x. Everything seems to be fine, however I have came to an issue with call_control module as this one is still using old MI interface. Standard situations work nice (maximum debit, prepaid, "CDRs") however when call_control needs to kill a call (credit is gone), it tries to send dlg_end_dlg over MI and it fails. Question are: Is call_control still supported? I haven't found any note about it. Is there any workaround from Kamailio point of view? I'm running last versions of both applications. I'm also rising a ticket at ag-projects side. Thanks Efelin

3 7

Re: [SR-Users] sr-users Digest, Vol 169, Issue 27
by ali mahfouz 29 Jun '19

29 Jun '19

if I send my kamailio.cfg file can you edit it to me please because it is so urgent On Thu, Jun 27, 2019 at 1:06 PM <sr-users-request(a)lists.kamailio.org> wrote: > Send sr-users mailing list submissions to > sr-users(a)lists.kamailio.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > or, via email, send a message with subject or body 'help' to > sr-users-request(a)lists.kamailio.org > > You can reach the person managing the list at > sr-users-owner(a)lists.kamailio.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of sr-users digest..." > > > Today's Topics: > > 1. Re: TOPOS uid in contact param instead of username > (Daniel-Constantin Mierla) > 2. Kamailio 5.x and Call_control module (Efelin Novak) > 3. Re: Kamailio 5.x and Call_control module > (Daniel-Constantin Mierla) > 4. Statistics for locally generated replies (Duarte Rocha) > 5. Re: Kamailio 5.x and Call_control module > (Daniel-Constantin Mierla) > 6. Re: Kamailio 5.x and Call_control module (Efelin Novak) > 7. Re: kamailio as UAC and NAPTR / sendsocket question > (Karsten Horsmann) > 8. MongoDB for Kamailio (Gaurav Bmotra) > 9. Presence publish manipulation (Gertjan Wolzak) > 10. Re: Question about registrar behavior > (Володимир Іванець) > 11. Re: MongoDB for Kamailio (Henning Westerholt) > 12. Re: DMQ: dmq_t_replicate() (Henning Westerholt) > 13. Re: does kamailio support graph database ?? (Henning Westerholt) > 14. Re: Question about registrar behavior (Henning Westerholt) > 15. Need help with "no branches for forwarding" message (Andrew Chen) > 16. Topos / Remove HF_re (Nicolas Breuer) > 17. Re: Kamailio 5.x and Call_control module (Efelin Novak) > 18. Re: Question about registrar behavior > (Володимир Іванець) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 26 Jun 2019 12:52:05 +0200 > From: Daniel-Constantin Mierla <miconda(a)gmail.com> > To: "Kamailio (SER) - Users Mailing List" > <sr-users(a)lists.kamailio.org> > Subject: Re: [SR-Users] TOPOS uid in contact param instead of username > Message-ID: > < > CAFRry4VMJd9aaJ_teWd3E-CYg-O9K+qutW699n9GDc9is7wAxQ(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hello, > ok, feel free to ask question if something is not clear ... and I think > topoh might help looking at its code, iirc, it uses uri param for contact > masking ... > > Anyhow, there is no better fun that C coding ;-) ... > Cheers, > Daniel > > On Wed, Jun 26, 2019 at 10:12 AM Thomas Weber <thomas.weber(a)pascom.net> > wrote: > > > Hello, > > > > thank you for your opinions. > > > > So i will give it a try throughout the next weeks because we have some > > customer pressure here. > > Didn't do a C project since some 10 years, so it could be fun to "learn > it > > again". > > > > Cheers, > > > > > > Thomas > > > > _______________________________________________ > > Kamailio (SER) - Users Mailing List > > sr-users(a)lists.kamailio.org > > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > > > -- > Daniel-Constantin Mierla - http://www.asipto.com > http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda >

2 2

Re: [SR-Users] Kamailio next_state_dlg(): bogus event
by Olli Attila 29 Jun '19

29 Jun '19

Hello, The prack is for the initial INVITE establishing the call. No re-INVITE messages are generated in the dialog. --Olli Message: 11 Date: Fri, 28 Jun 2019 08:35:09 +0200 From: Daniel-Constantin Mierla <miconda(a)gmail.com> To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.kamailio.org> Subject: Re: [SR-Users] Kamailio next_state_dlg(): bogus event Message-ID: <CAFRry4XAF5qYqRxgJA4tzsuUt-56ON1KnzzwvJnxeKOdTUaxSA(a)mail.gmail.com> Content-Type: text/plain; charset="utf-8" Hello, is the PRACK following a re-INVITE or is for the initial INVITE establishing the call? Cheers, Daniel On Fri, Jun 28, 2019 at 8:13 AM Olli Attila <attiolli(a)gmail.com> wrote: > Hello, > > I'm getting this error in Kamailio log every now and then. Can anyone > suggest methods to debug this further for root cause? > > Jun 27 10:04:09 /usr/sbin/kamailio[26341]: CRITICAL: dialog > [dlg_hash.c:1098]: next_state_dlg(): bogus event 5 in state 4 for dlg > 0x7fceeabf8d38 [749:3185] with clid > 'SDceked01-e4d2e93d7f9ffe88907206a25ccdbcc2-v300g00030' and tags > 'SDceked01-ecd4281b' '14001358846426' > > Behaviour in the call: > When I look at the SIP flow from this call I can see that a PRACK > message which is routed to Kamailio gets discarded (=the proxy does > not route the PRACK onwards to the UA that requested the usage of the > 100rel in 183 session progress message.) The PRACK message itself > seems valid and when compared to a PRACK from a working call, there is > no difference in the content. > > Cheers, > Olli

2 1

Htable not reloading from db on expiry
by Daniel Greenwald 28 Jun '19

28 Jun '19

I have an htable that loads from mysql. The data loads fine on startup but disappears on expiry. If I issue kamcmd htable.reload it loads again until expiry. It seems as if db_expires is not taking affect. I see them expiring in the debug log but not an errors. Mysql general log does not show any attempt to connect on expiry. Another odd thing is that if I set the expires column in db to anything other than 0 the data doesn't load at all. Any ideas would be appreciated. modparam("htable", "timer_interval", 10) modparam("htable", "htable", "h=>size=20;autoexpire=20;dbtable=validdomains;updateexpire=0;") modparam("htable", "db_url", AUTHDBURL) modparam("htable", "db_expires", 1) create or replace view validdomains as select distinct subscriber.domain as key_name, 1 as key_value, 0 as key_type, 0 as value_type, 0 as expires from subscriber;

2 1

Kamailio next_state_dlg(): bogus event
by Olli Attila 28 Jun '19

28 Jun '19

Hello, I'm getting this error in Kamailio log every now and then. Can anyone suggest methods to debug this further for root cause? Jun 27 10:04:09 /usr/sbin/kamailio[26341]: CRITICAL: dialog [dlg_hash.c:1098]: next_state_dlg(): bogus event 5 in state 4 for dlg 0x7fceeabf8d38 [749:3185] with clid 'SDceked01-e4d2e93d7f9ffe88907206a25ccdbcc2-v300g00030' and tags 'SDceked01-ecd4281b' '14001358846426' Behaviour in the call: When I look at the SIP flow from this call I can see that a PRACK message which is routed to Kamailio gets discarded (=the proxy does not route the PRACK onwards to the UA that requested the usage of the 100rel in 183 session progress message.) The PRACK message itself seems valid and when compared to a PRACK from a working call, there is no difference in the content. Cheers, Olli

2 1

Statistics for locally generated replies
by Duarte Rocha 27 Jun '19

27 Jun '19

Greetings, Does the statistics command "kamcmd tm.stats" has an argument or a way to only list locally generated replies? As far as i know, sl.stats only lists local generated replies. Can tm work the same way? Best Regards, Duarte Rocha

2 1

Need help with "no branches for forwarding" message
by Andrew Chen 27 Jun '19

27 Jun '19

Hey guys, I need help to identify the cause of this is error: Jun 26 12:03:53 ashintgtpsg51 /usr/sbin/kamailio[1651]: ERROR: tm [t_fwd.c:1728]: t_forward_nonack(): no branches for forwarding This message was shortly printed after I xlog a message in onsend_route[] block. What else is strange is that the dialog continued on with that same SIP Call-ID. This is what it looks like in the wireshark flow diagram: [image: image.png] The dispatcher entry is an SRV record which lists available hosts. Any thoughts on how I can identify the cause of this? Thanks. -- Andy Chen Sr. Telephony Lead Engineer 415 516 5535 (M) 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.*

1 1

Topos / Remove HF_re
by Nicolas Breuer 27 Jun '19

27 Jun '19

Hello, When using TOPOS module, Kamailio add this header : P-SR-XBranch before executing the topos module. Doing this "remove_hf_re("P-")" in the scripting seems to bypass the addition of the P-SR-XBranch in the sip message. In my mind, remove header function just remove the headers based on the incoming message. What do you think ?

2 1

Question about registrar behavior
by Lars Olsson 27 Jun '19

27 Jun '19

Hi, I have found a behavior in the registrar module that I do have a question about. Is the current behavior correct and wanted? Using the save() method in the script I see the following: * Processing a register request for a user gives return code 1 ( or 2 ) * Processing a unregister request (expires=0) for registered user gives return code 3 * Processing a unregister request (expires=0) for a user which is NOT registered gives return code 1. Why? What is the reason behind this? No database entry is added which is expected. Test performed on 5.1.4, using DB mode 3. For handling a late unregister request ( where registration has already expired) return code does not reflect the the action. I assume that manually checking $expires(max) is the option to go then if I want to detect the unregister request or? Cheers, Lars

3 3

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

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 June 2019