sr-users February 2014

sr-users@lists.kamailio.org

114 participants
157 discussions

by davy van de moere

Gents, I’ve stumbled upon a coredump when using jsonrpc_request. I might be expecting the wrong things from jsonrpc_request. I was hoping to use it in combination with CNXCC, and have jsonrpc_request get a maximum duration for every call, as a fraud avoidance mechanism. I tried this with the branch 4.1 and master. Both behave identical. So from the kamailio-basic.cfg example, I just added this line around line 350 (just above route(SIPOUT)): jsonrpc_request("bar.sendsms", "{'ru':'$rU','rb':'$rb'}", "JSONRESPONSE", "JSONERROR", "$var(result)"); Doing a ngrep on the netstrings I have: interface: venet0 (127.0.0.2/255.255.255.255) filter: (ip or ip6) and ( port 7080 ) # T 10.66.8.42:44995 -> 192.168.60.45:7080 [AP] 94:{ "id": 2, "jsonrpc": "2.0", "method": "bar.sendsms", "params": { "ru": "", "rb": "" } }, ## T 192.168.60.45:7080 -> 10.66.8.42:44995 [AP] 43:{"jsonrpc": "2.0", "result": "12", "id": 2}, ####^Cexit 7 received, 0 dropped I do get some results from the JSONRESPONSE route. But when launching a call, or when sending just a register packet, kamailio gives up with: Feb 26 06:29:11 SBC01 kamailio[18043]: WARNING: tm [t_lookup.c:1537]: t_unref(): WARNING: script writer didn't release transaction Feb 26 06:29:12 SBC01 kamailio[18033]: : [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0xb4c01624), called from tm: h_table.c: free_cell(157), first free tm: h_table.c: free_cell(157) - aborting Feb 26 06:29:12 SBC01 kamailio[18023]: ALERT: [main.c:775]: handle_sigs(): child process 18033 exited by a signal 6 Feb 26 06:29:12 SBC01 kamailio[18023]: ALERT: [main.c:778]: handle_sigs(): core was generated Feb 26 06:29:12 SBC01 kamailio[18023]: INFO: [main.c:790]: handle_sigs(): INFO: terminating due to SIGCHLD Feb 26 06:29:12 SBC01 kamailio[18041]: INFO: [main.c:841]: sig_usr(): INFO: signal 15 received Feb 26 06:29:12 SBC01 kamailio[18047]: INFO: [main.c:841]: sig_usr(): INFO: signal 15 received Feb 26 06:29:12 SBC01 kamailio[18043]: INFO: [main.c:841]: sig_usr(): INFO: signal 15 received Feb 26 06:29:12 SBC01 kamailio[18048]: INFO: [main.c:841]: sig_usr(): INFO: signal 15 received Feb 26 06:29:12 SBC01 kamailio[18023]: : [mem/q_malloc.c:468]: qm_free(): BUG: qm_free: freeing already freed pointer (0xb4c01624), called from tm: h_table.c: free_cell(157), first free tm: h_table.c: free_cell(157) - aborting Using the jsonrpc_notification works like a charm. I got coredumps of it, if someone is interested. Side questions are offcourse, am I aiming to use jsonrpc_request for the correct purpose? Are there any other good alternatives? (next to using plain db queries?) Grtz, Davy -- davy van de moere

10 years, 10 months

Kamailio World 2014 - Agenda

by Daniel-Constantin Mierla

The first version of the schedule during Kamailio World 2014 <http://www.kamailioworld.com> [1] has been published. Over 30 sessions grouped in two days of conference and pre-conference technical tutorials, spanning from various use cases for Kamailio to presentations approaching related VoIP applications such as Jitsi, Sems, Asterisk or FreeSwitch. Among the topics: WebRTC, IMS or VoIP security and fraud detection, tools for testing and troubleshooting VoIP systems, scalability with OpenStack and asynchronous processing, real time charging. First version of agenda has been published at: - http://conference.kamailio.com/k02/schedule/ Information about speakers can be found at: - http://conference.kamailio.com/k02/speakers/ Many thanks to the sponsors [2], they are making possible this event: FhG Fokus <http://www.fokus.fraunhofer.de/en/fokus/index.html>, Asipto <http://www.asipto.com>, Sipwise <http://www.sipwise.com>, Sipgate <http://www.sipgate.de>, IT Center <http://www.itcenter.com.pt/>, Simwood <http://www.simwood.com>, and NG Voice <http://www.ng-voice.com/>. Should you consider sponsoring, contact us via email at <conference [at] kamailio.com>**and we can present you more details. If you plan to attend, do not delay the registration, the number of seats is limited – see more details in Registration page <http://conference.kamailio.com/k02/registration/> [3]. /Looking forward to meeting many of you in Berlin! / Daniel/ / [1] - http://conference.kamailio.com [2] - http://conference.kamailio.com/k02/sponsors/ [3] - http://conference.kamailio.com/k02/registration/ -- Daniel-Constantin Mierla http://www.asipto.com

10 years, 10 months

debian packages from opensuse.org

by Jöran Vinzens

Hi All, we are using Kamailio 4.1.0 packages from opensuse: http://download.opensuse.org/repositories/home:/kamailio:/telephony-debs/De… During installation it seems, the packages are malformed. Installation of kamailio-mysql-modules and kamailio-xml-modules stops during unpacking with failure: "trying to overwrite '/usr/lib64/kamailio/libsrdb2.so.1.0', which is also in package kamailio 4.1.0" it seem this one file is part of all three packages. There is a way to enforce the installation using dpkg -i --force-all.. but it seems not the right way. Does anyone have an idea how to solve without building own packages? Maybe this is an bug in kamailio Project? Many thanks for all proposals. BR Jöran -- Jöran Vinzens sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.at - www.sipgate.co.uk

10 years, 10 months

Re: [SR-Users] RTPProxy/Mediaproxy issue

by Daniel Grotti

Hi, Yes packet loss is very high. Please investigate around that. Daniel Ravi <wingsravi777(a)gmail.com> wrote: >_______________________________________________ >SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >sr-users(a)lists.sip-router.org >http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

10 years, 10 months

Problems while reading from location and parsing expires

by Jöran Vinzens

Hi All, we are upgrading from kamailio 3.1 to 4.1 and we got stuck at a Problem with usrloc module. While starting up kamailio reads location from DB and try to parse expires date from DB. this is the Problem: Feb 25 11:42:11 hagi /usr/sbin/kamailio[19580]: ERROR: <core> [db_ut.c:90]: db_str2int(): Unexpected characters: [-02-25 11:27:08] Feb 25 11:42:11 hagi /usr/sbin/kamailio[19580]: ERROR: <core> [db_val.c:75]: db_str2val(): error while converting integer value from string Feb 25 11:42:11 hagi /usr/sbin/kamailio[19580]: ERROR: db_mysql[km_row.c:68]: db_ mysql_convert_row(): failed to convert value Feb 25 11:42:11 hagi /usr/sbin/kamailio[19580]: ERROR: db_mysql [km_dbase.c:375]: db_mysql_fetch_result(): error while converting row #0 Feb 25 11:42:11 hagi /usr/sbin/kamailio[19580]: ERROR: usrloc [udomain.c:420]: preload_udomain(): fetching rows failed usrloc Module is configured with db_mode "1" so it saves it's entries by itself. When i have a look on the database it looks good and the expires field is an datetime. From logs it looks like it try to parse a unixtimestamp instead of the datetime. when i truncate the location table it starts perfectly, since there are no entries stored where it could fail parsing expires date. does anybody has similar issue or any suggestions how to solve? found in Version: 4.1.0 many thanks! BR Jöran -- Jöran Vinzens sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391 www.sipgate.de - www.sipgate.at - www.sipgate.co.uk

10 years, 10 months

Re: [SR-Users] Kamailio as redirect

by Daniel Tryba

On Monday 24 February 2014 14:45:18 Mike Claudi Pedersen wrote: > okay i somewhat get that.. but cant i use something like a lookup in a > textfile instead of a db? You can. alias_db also accepts dbtext as backend: http://kamailio.org/docs/modules/stable/modules/db_text.html But TIMTOWTDI, alias_db was just a suggestion. Please keep the mailing list included. -- POCOS B.V. - Croy 9c - 5653 LC Eindhoven Telefoon: 040 293 8661 - Fax: 040 293 8658 http://www.pocos.nl/ - http://www.sipo.nl/ K.v.K. Eindhoven 17097024

10 years, 10 months

Re: [SR-Users] Configuring Kamailio as an upstream proxy for FreeSwitch and which RTP proxy to choose

by Fred Posner

On Mon Feb 24 10:50:07 CET 2014 Sean Kemball wrote: > New to Kamailio and FreeSwitch, loosely familiar with SIP mechanics, > and not a complete network idiot... but please be gentle. :) Welcome!s, > Questions: > > 1. Should the proposed topology, with Kamailio + an RTP proxy > behind a firewall, relaying to FS on an inside interface, work? > (Can't see why not) Yes, you said that your upstream is on the same private network. So it should be pretty straight forward. > 2. Does it need a local RTP proxy on the Kamailio box, particularly > if we turn off the ASA SIP inspect stuff? If you are all on the same private network, I would let FreeSWITCH handle the RTP, but you can do this a variety of ways. > 3. Can you recommend which RTP proxy to use? There seem to be at > least 3 that work with Kamailio. The box is CentOS 6.5, and it would > be nice to use known-to-work packages rather than compile from source. > (But eh, if I haveta). On your scenario, I'd just use FreeSWITCH for the media proxy. Again, many different ways to go here. > 4. Can anyone point me to some docs to explain what ports need to > be open between the Kamailio box and my upstream proxy/media server? > I can be more liberal between inside and DMZ I guess. Your upstream provider would generally tell you which rtp ports they would want opened. > 5. Is static NAT in this environment going to bite me, or should > it be OK? I've never had an upstream provider communicate with me on private nat. > 6. Is there any better documentation that we should be using to > make this easier, or should I just man up and try harder? Man up. =) Practive makes perfect. -- Fred Posner The Palner Group, Inc.

10 years, 10 months

pcscf - removing registration entries from hash table

by Daniel Ciprus

Hello, Our current setup is Kamailio as IMS core and we're observing following behavior: Clients register themselves over TCP so pcscf creates hash table which keeps these information in memory. Once tcp reset occurs for any reason, registration entry stays in the memory and client re-registers himself with new pair ip:port. This kind of behavior creates problem because outbound SIP messages are being forked and requests are sent to non-existent tcp sessions which creates a lot of timeouts and confusion for AS. We're using ims_usrloc_pcscf module to keep reg entries in and as I noticed, with usrloc module, there was an option which automatically removed entry from hash table once tcp session was closed which is not the case in this module. Any suggestions how to get out of this ? thanks for any hints/suggestions. -- Daniel Ciprus Integration engineer http://www.acision.com 9954 Mayland Dr Suite 3100 Richmond, VA 23233 USA T: +1 804 762 5601 E: daniel.ciprus(a)acision.com<mailto:daniel.ciprus@acision.com> ________________________________ This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.

10 years, 10 months

Kamailio as redirect

by Mike Claudi Pedersen

i want to setup a test environment to see how kamailio handles redirection. i want to be able to reroute calls between servers, where do i insert the configuration for this? can i append a list of user and destination to make the configuration go through, to see where the call is going? im new at kamailio, and im having a really hard time finding the right documentation to support a redirect server. could somone please give me an example? lets say i have 3 user 1000 1001 1002 and they are at 3 different servers eg. 1000(a)192.168.1.10 1001(a)192.168.1.11 1002(a)192.168.1.12 then i call user 1002 from user 1000, through the kamailio redirect server, which redirects to corresponding servers. Mike Claudi Pedersen

10 years, 10 months

Configuring Kamailio as an upstream proxy for FreeSwitch and which RTP proxy to choose

by Sean Kemball

Hi New to Kamailio and FreeSwitch, loosely familiar with SIP mechanics, and not a complete network idiot... but please be gentle. :) We're trying to get Kamailio set up in front of a FreeSwitch-based SIP application server, to do some simple policy controls and, using one of the RTP proxy modules, to help handle the media side of things. Our SIP trunks come from our provider on a VLAN addressed as 10.x, and they provide an upstream proxy/media server (10.y address). The link also carries Internet traffic so we're running it through a Cisco ASA which breaks out the VLANs and static NATs the SIP stuff to our DMZ (10.z address). This is where we want to put the Kamailio box, where it should receive the calls and route them back through the ASA to the internal address (10.w range - all 10.w/x/y/z are separate, non-overlapping networks). Outbound calls from the application server (there are very few) should pass back up to Kamailio which will validate the numbers against an approved list (the app should only dial a subset of numbers) and pass them to the upstream proxy if necessary. We need to ensure that inbound calls from outside trombone through our application server so that the caller doesn't get billed for any calls, but this should be the default I think as that side of things is handled by FS (the app stands up a new call and bridges it to the incoming). This topology should allow us to use Kamailio to hide details of the FS app from the outside world, and make life easier for the app developer who should just send/receive to the Kamailio box with no further thought or complexity. If we put the FreeSwitch box in the DMZ where we want to put Kamailio, and then turn on SIP packet inspection in the ASA, calls flow but quality is poor for some callers. If we turn off SIP packet inspection, we get no audio - I can't find any clear Cisco documentation for this but I think the SIP inspection stuff in the ASA seems to handle RTP NAT fixups and the like too. But with no docs it may as well be magic, and I want to remove it if possible. With Kamailio in the DMZ and FS internal, we loosely followed http://kb.asipto.com/freeswitch:kamailio-3.3.x-freeswitch-1.2.x-sbc and hacked out the voicemail and Lua stuff, but couldn't get calls to flow, whether or not we used the SIP inspection on the ASA. We were confused why this example isn't define as WITH_NAT and doesn't use a local RTP proxy. Surely that would be needed? Questions: 1. Should the proposed topology, with Kamailio + an RTP proxy behind a firewall, relaying to FS on an inside interface, work? (Can't see why not) 2. Does it need a local RTP proxy on the Kamailio box, particularly if we turn off the ASA SIP inspect stuff? 3. Can you recommend which RTP proxy to use? There seem to be at least 3 that work with Kamailio. The box is CentOS 6.5, and it would be nice to use known-to-work packages rather than compile from source. (But eh, if I haveta). 4. Can anyone point me to some docs to explain what ports need to be open between the Kamailio box and my upstream proxy/media server? I can be more liberal between inside and DMZ I guess. 5. Is static NAT in this environment going to bite me, or should it be OK? 6. Is there any better documentation that we should be using to make this easier, or should I just man up and try harder? TIA Sean Volunteer for our Red Puppy street appeal to help puppies like Gordy become guide dogs. ############################################################################# This email, including any attachments, is intended solely for the addressee(s) It is confidential and may be legally privileged. If you are not the intended recipient, you must not copy, disclose, distribute or otherwise use it or the information in it. Please notify the sender at once and delete it from your system immediately. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Blind Foundation. The Blind Foundation does not accept responsibility for any viruses or other malicious code that may be transmitted with this email. #############################################################################

10 years, 10 months

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

Jump to page:

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