sr-users

sr-users@lists.kamailio.org

21 participants
37573 discussions

Credit Control modules
by Shane Harrison 18 Feb '15

18 Feb '15

Hi all, As you will have seen from my posts, I have adapted the ims_charging module to work with usrloc module i.e. outside ims environment. I am interested in whether others see a use in having a Diameter Credit Control module that is standalone. There are already a number of Credit Control modules other than the ims one e.g. cncxx and I am not sure if the community sees a need for YACC. If there is interest then need to consider further how best to approach accommodating both ims dependence and standalone operation. Cheers Shane Shane Harrison Senior Software Engineer Imagination Technologies NZ Limited Level 2 1 Market Grove Lower Hutt, 5010 New Zealand PO Box 30-449 Lower Hutt, 5040 New Zealand Phone: +64 4 890-3681 ext 3361

2 1

rtpproxy bridge "ie" "ei" behind NAT (like in aws EC2)
by Giovanni Maruzzelli 17 Feb '15

17 Feb '15

dear Kamailians, I have Kamailio+rtpproxy in front of FreeSWITCH. Kamailio and FreeSWITCH are on the same private network. Public Internet IP address ports are redirected to Kamailio and rtpproxy (same situation as in Amazon EC2). Clients comes from Internet, and make calls to Internet, SIP signaling passing through FreeSWITCH (eg: A leg incoming INVITE, FreeSWITCH originate an outbound B leg INVITE, and then bridge the legs). Using rtpproxy with -A "advertise" patch from Daniel, this topology works fine in a "traditional" telco way: rtp goes from caller to rtpproxy to callee, and viceversa. Now I want to maintain FreeSWITCH in the middle of rtp flow all the time, in a pure b2bua way, so it can control and analyze the media streams. So, I need rtpproxy to act paying attention to direction, as in caller->rtpproxy->freeswitch->rtpproxy->callee (and viceversa). Normally I would use Kamailio multihomed and rtpproxy in bridging mode. But I cannot have a NIC on the public address. How I can use the "ie" "ei" feature of rtpproxy in an Amazon-EC2 like environment? (eg: no public address attached to machine, but ports redirection from public address). I read this trick from Hugh Waite: "I have used rtpproxy (with the advertised address patch) in Amazon to bridge media between internet facing and private subnets in a VPC. I found that I couldn’t use different advertised addresses depending on which direction the signalling was going on a single private IP address. I worked around this by allocating a second private ip address to the instance and used that in the ‘bridge’. -A 54.86.X.X/10.0.1.15 –l 10.0.1.10/10.0.1.15" Can you explain how to use this trick, or another way (without additional addresses is gladly accepted!) to reach the same result (rtp always passing through FreeSWITCH) ? Thank you all in advance, -giovanni -- Sincerely, Giovanni Maruzzelli Cell : +39-347-2665618

8 11

Session timers
by Eric Koome 17 Feb '15

17 Feb '15

How do I process session timers in Kamailio coming from particular upstream provider every 15mins during a call? At the moment the the call fails after 15 mins. Related to this, another provider sends re-invites during a dialog to check that my kamailio is alive. However Kamailio responds with "488 not here". How do I process these as well? Asterisk sits behind Kamailio. Thanks Eric

2 3

CAMARILLO : (9898) ERROR: ctl [ctl.c:382]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1)
by BY - Boujraf Youssef 17 Feb '15

17 Feb '15

Dear all, We get this error message : Using Kamailio V4.2 debian wheezy (9898) ERROR: ctl [ctl.c:382]: mod_destroy(): ERROR: ctl: could not delete unix socket /tmp/kamailio_ctl: Operation not permitted (1) We are not able to fix it. If anybody could help us it will be great. Best Regards, Youssef

1 0

load balancing + rtpengine
by Virmantas Variakojis 17 Feb '15

17 Feb '15

Hi, I want to use load balancing (dispatcher or carrierroute) but i have two upstream interfaces (separate vlan's to provider sides) and third interface to SIP clients side. Also i need to rewrite sdp fields with correct information with rtpengine, but it's impossible as i don't know whitch direction (provider) will be chosen by algorithm. Is it possible to use load dispatcher or carrierroute in conjunction with rtpengine or load balancing must be done manualy? — Regards, Virmantas -- __________________________________________________________________________ CONFIDENTIALITY NOTICE: The information contained in the present message (including any information contained in attachments herein) may be confidential and privileged. It may be read, copied and used only by the intended recipient. If you have received it in error please contact the sender (by return e-mail) immediately and delete this message. Any unauthorized use or dissemination of this message in whole or in parts is strictly prohibited. Print this message only if sharp necessary. УВЕДОМЛЕНИЕ О КОНФИДЕНЦИАЛЬНОСТИ: Информация, содержащаяся в настоящем сообщении (включая любое вложение) может быть конфиденциальной и охраняться действующим законодательством. Сообщение может быть прочитано, скопировано и использовано исключительно лицом, которому сообщение предназначается. Если Вы получили настоящее сообщение по ошибке, пожалуйста, незамедлительно сообщите об этом отправителю (ответным письмом по электронной почте). Любое несанкционированное использование или распространение информации, содержащейся в настоящем сообщении в целом или в части, строго запрещены. Не распечатывайте настоящее сообщение, если в этом нет крайней необходимости.

1 0

TLS certificates per domain
by Muhammad Shahzad 17 Feb '15

17 Feb '15

Hi, I want to deploy a kamailio v4.2.x setup with multiple domains, all resolve to same IPv4 address kamailio is listening on. I am bit confused about how to configure TLS certificates using tls config file as mentioned here, http://kamailio.org/docs/modules/4.2.x/modules/tls.html#tls.p.config The documentation states that, -- If set the TLS module will load a special config file or config files from config directory, in which different TLS parameters can be specified on a per role (server or client) and domain basis (*for now only IPs*). The corresponding module parameters will be ignored. -- since all domains resolve single IP, so i assume i can specify only one section in tls config file with pair of key/pem file path. How can i specify more server certificates for same ip but with different domains? Thank you.

2 2

Syntax issue?
by Igor Potjevlesch 17 Feb '15

17 Feb '15

Hello, I'm looking for a way to track a call by using basic AVP like this: Into a route that treats INVITE: $avp(s:state)="call_start"; Then, if I test this AVP into WITHINDLG route: if($avp(s:state)!="call_start") ; the test fails. Did I miss something? The goal is to update this AVP during the life of the transaction. Regards, Igor.

4 15

selective logging with debugger module
by Sharath Kumar 16 Feb '15

16 Feb '15

Hello, I followed the documentation from http://kamailio.org/docs/modules/4.2.x/modules/debugger.html#idp84752. I have the global debug flag at 9. modparam("debugger", "cfgtrace", 1) modparam("debugger", "mod_level_mode", 1) modparam("debugger", "mod_level", "core=3") My Kamailio complains with a parsing error of some sort and fails to start. - "dbg_mod_level_param(): cannot store parameter: core=3" My intention is to turn off/reduce the "core" module tracing while keeping the "script" module at debug. Any suggestions ? I am running version 4.1.4. thanks Sharath

1 0

Amazon VPS, long UDP packets are seen by sniffer, but don't reach application
by Andrey Utkin 16 Feb '15

16 Feb '15

We experience strange networking issue, not exactly specific to kamailio, but still related to it. Rtpengine's "ng" interface uses UDP. Protocol messages contains SDP, and for encrypted video call those messages exceed 1500 bytes. Everything works fine within localhost, but when rtpengine and Kamailio are on different hosts, and when hosts are Amazon-hosted, we have trouble. This is experienced with l3.large, t2.micro with Ubuntu 14. I believe we don't have any special settings over system defaults. We send a large datagram from remote host, e.g. with such trivial app in python: import socket UDP_IP = "123.123.123.123" # remote host IP UDP_PORT = 33333 MESSAGE = """ .....0010......0020......0030......0040......0050......0060......0070......0080......0090......0100 .....0110......0120......0130......0140......0150......0160......0170......0180......0190......0200 .....0210......0220......0230......0240......0250......0260......0270......0280......0290......0300 .....0310......0320......0330......0340......0350......0360......0370......0380......0390......0400 .....0410......0420......0430......0440......0450......0460......0470......0480......0490......0500 .....0510......0520......0530......0540......0550......0560......0570......0580......0590......0600 .....0610......0620......0630......0640......0650......0660......0670......0680......0690......0700 .....0710......0720......0730......0740......0750......0760......0770......0780......0790......0800 .....0810......0820......0830......0840......0850......0860......0870......0880......0890......0900 .....0910......0920......0930......0940......0950......0960......0970......0980......0990......1000 .....1010......1020......1030......1040......1050......1060......1070......1080......1090......1100 .....1110......1120......1130......1140......1150......1160......1170......1180......1190......1200 .....1210......1220......1230......1240......1250......1260......1270......1280......1290......1300 .....1310......1320......1330......1340......1350......1360......1370......1380......1390......1400 .....1410......1420......1430......1440......1450......1460......1470......1480......1490......1500 .....1510......1520......1530......1540......1550......1560......1570......1580......1590......1600 .....1610......1620......1630......1640......1650......1660......1670......1680......1690......1700 .....1710......1720......1730......1740......1750......1760......1770......1780......1790......1800 .....1810......1820......1830......1840......1850......1860......1870......1880......1890......1900 .....1910......1920......1930......1940......1950......1960......1970......1980......1990......2000""" print "UDP target IP:", UDP_IP print "UDP target port:", UDP_PORT print "message:", MESSAGE sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) sock.sendto(MESSAGE, (UDP_IP, UDP_PORT)) Then we listen on that port with such trivial python app: import socket UDP_IP = "172.31.4.102" # local ip UDP_PORT = 33333 sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM) sock.bind((UDP_IP, UDP_PORT)) while True: data, addr = sock.recvfrom(0x10000) print "received message:", data Meanwhile, we monitor the traffic with e.g. ngrep: ngrep -t -e -d any -W byline -O large_udp.pcap port 33333 or '(ip[6:2]' '&' '0x1fff)' '!=' '0' (the part after "or" catches segments of segmented packets) About the host: # uname -a Linux hostname 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 17:43:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Also linux-image-3.13.0-36-generic and linux-image-3.13.0-45-generic behave in same way. What we see: - ngrep shows the packets with correct contents. All segments are delivered. - application doesn't get any data at all Rarely dmesg shows such messages: [ 102.161679] UDP: bad checksum. From 123.123.123.124:56439 to 172.31.4.102:33333 ulen 2008 but it is logged really rarely, so this is surely not what happens on every packet transmission. This test works fine on e.g. cheapest DigitalOcean VPS. I am concerned with this issue because rtpengine software has UDP interface. So on Amazon hosts this interface works only within localhost, and I cannot distribute software to different nodes. Any thoughts? What's wrong, how to fix? -- Andrey Utkin

2 4

Log Media IP
by Ryan Brindley 16 Feb '15

16 Feb '15

Hey community, What's the best way to pull out the media ip from the SIP INVITE body (for logging)? Ryan Brindley

2 1

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