sr-users June 2014

sr-users@lists.kamailio.org

86 participants
144 discussions

Specifying Upstream and Downstream Servers for a simple SIP proxy

by AliReza Khoshgoftar Monfared

Dear Kamailio users, I am trying to set up a simple scenario as follows: UAC --> Proxy_1 --> Proxy_2 --> Proxy_3 --> UAC I am new to Kamailio and had the following basic questions that came to my mind after reading the documentation an the default kamilio.cfg config script: 1) Is there any good example of the above scenario in which the UAC and UAS (caller and callee) are modeled using SIPp and proxies are simple kamailio instances run on different machines that simply forward the SIP packets? 2) In specific, I want the proxies to simply forward the messages to their downstream (I do not care about registration or other operations and look for a minimally working simple SIP scenario). Is there any example of such configuration? 3) Let's imagine Proxy_2 in the above example, in the default config, it looks like that with modifying line 164, "listen=udp:10.0.0.10:5060" I can specify the address of its upstream, Proxy_1, but how and where shall I set the specifications of the downstream, Proxy_3? I suspect it is somewhere in the Routing Logic block (line 449) but not sure how it is exactly done. I see a "route(SIPOUT)" call for example but I am not sure how and where the value of SIPOUT is modified. Is it a representation of the downstream servers in the config file? Thanks, Alireza

9 years, 11 months

Is Kamailio PacketCable 2.0 compatible

by Horo, Priyam

I was looking at installing Kamailio and was wondering it is Packetcable 2.0 compatible? Thanks!

9 years, 11 months

Disabling rtpengine abrt handler

by Alex Balashov

Hello, Despite this fix https://github.com/sipwise/rtpengine/commit/cbe1f805363b3d6a117e9e5425d7994… I am continuing to experience periodic crash problems under high loads with rtpengine. This is after upgrading mediaproxy-ng -> rtpengine. Unfortunately, after this upgrade, it is impossible to tell the cause of the crash because the [seemingly] newer rtpengine SIGABRT and/or crash handler is not running properly and is getting in my way: Jun 20 15:47:55 rtphost abrtd: Directory 'ccpp-2014-06-20-15:47:54-1123' creation detected Jun 20 15:47:55 rtphost abrt[2159]: Saved core dump of pid 1123 (/usr/sbin/rtpengine) to /var/spool/abrt/ccpp-2014-06-20-15:47:54-1123 (97013760 bytes) Jun 20 15:47:55 rtphost abrtd: Executable '/usr/sbin/rtpengine' doesn't belong to any package and ProcessUnpackaged is set to 'no' Jun 20 15:47:55 rtphost abrtd: 'post-create' on '/var/spool/abrt/ccpp-2014-06-20-15:47:54-1123' exited with 1 Jun 20 15:47:55 rtphost abrtd: Deleting problem directory '/var/spool/abrt/ccpp-2014-06-20-15:47:54-1123' I am not sure why this script is exiting, but the result is that I have no /var/spool/abrt/ccpp-2014-06-20-15:47:54-1123 and no core dump to work with. This is on a standard minimal CentOS 6.5.x install. Is there any way to either disable this signal handler and just let it dump core normally, or, otherwise, to definitively fix the crash handler? Thanks, -- Alex Balashov - Principal Evariste Systems LLC Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ Please be kind to the English language: http://www.entrepreneur.com/article/232906

9 years, 11 months

MSILO storing wrong content-type.

by Prasun Bheri

Hi All, I have Kamailio 4.0.0 configured with MSILO in centos 6. When a Message destined to offline recipient is received by kamailio, MSILO stores the message with wrong content type. In my scenario Incoming message has content type "message/cpim" where as in database its is stored as "text/plain". and obviously when recipient registers back in the stored message is sent with content type as "text/plain". I have attached a wireshark capture where in you can see packet #23 (recived Message) and #88 (dispatched Message). Could you guys let me know how to fix this. Thanks & Regards, Prasun

9 years, 11 months

UAC module refresh registration, could not reuse callid/fromtag !!!

by nevious

Hello all! I make kamailio1 remotely register to kamailio2. Here I set K1 modparam("uac", "reg_timer_interval", 15), and expires in uacreg as 30s. Then K1 should refresh registration after 15s. However the callid and from tag of every registration are different, and the Cseq just 10 or 11,never increased.In RFC3261, when UAC want refresh bindings, A UA SHOULD use the same Call-ID for all registrations during a single boot cycle. Is there any way to reuse the callid and fromtag during refresh registration ? Many thanks! And how to make the Cseq become 12 or more?

9 years, 11 months

Kamailio clean unconfirmed dialog

by Arun Kumar

Hi Server : kamailio 4.0 Configuration :Outbound with engage_media_proxy (See the attachment ) Shared Mem : 1024 MB Dialog TimeOut : 600 (Seconds) Problem : Dialog's are not cleared sometimes , So after sometime server is not responding (out of memory error), After investigating long time , the problem is non confirmed dialog's are not cleared even dialog timeout Thanks Arunkumar

9 years, 11 months

Re: [SR-Users] SIP Trunk

by Keith

Hi, So when I use the uac_reg_request_to, for some reason it sends an invite and not a register?? This means I'm not getting a 407 back to the use sac_auth in the failure route. Any ideas? Thanks Keith

9 years, 11 months

mediaproxy-ng query

by Alex Balashov

Hello, I'm invoking mediaproxy-ng with rtpproxy_offer/answer("ow") and am getting a scenario where: INVITE is forwarded to signalling gateway xxx.xxx.xxx.xxx, which returns an SDP answer of yyy.yyy.yyy.yyy:51964. rtpproxy is invoked in both directions. However, media forwarded from media endpoint A is sent to xxx.xxx.xxx.xxx:51964 (the correct port, but to the signalling gateway), rather than yyy.yyy.yyy.yyy:51964, which is what's specified in the SDP answer in the 200 OK from xxx.xxx.xxx.xxx. No media is coming back to mediaproxy-ng from yyy.yyy.yyy.yyy:51964. The cause of this is a separate and logically unrelated issue. Nevertheless, I am curious as to why mediaproxy-ng doesn't send media from the near end to yyy.yyy.yyy.yyy:51964--in other words, to the specified SDP endpoint on the far end, rather than to the signalling gateway. I initially imagined that this might be due to the "w" option to rtpproxy_offer(), which the documentation says forces symmetric RTP. However, this behaviour is not elaborated upon or defined. I tried removing the 'w' option but seem to be getting the same result. Is this a default behaviour of COMEDIA-style source port latching? In other words, does mediaproxy-ng need to latch onto incoming RTP from yyy.yyy.yyy.yyy:51964 before it will send media there, as opposed to the signalling gateway? If so, is there any way this behaviour can be disabled, so that mediaproxy-ng simply follows SDP in all cases? Thanks, -- Alex Balashov - Principal Evariste Systems LLC Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/ Please be kind to the English language: http://www.entrepreneur.com/article/232906

9 years, 11 months

Kamailio b2bua

by Grant Bagdasarian

Hello, OpenSIPS has a module for B2BUA. Does Kamailio have a similar one or one that comes close to it? Perhaps by combining modules to make Kamailio act as a B2BUA?

9 years, 11 months

Initial Install

by Phil Daws

Hello and good evening all! Am trying to build a Kamailio installation in my lab and have hit the first hurdle; database build. I have a three node MariaDB cluster in place and attempting to get kamdbctl create to set up the tables. What seems apparent is that command requires the database to not already exist. Where can I find the necessary schema to load into MariaDB myself please ? Thank you. Phil

9 years, 11 months

← Newer
1
...
4
5
6
7
8
9
10
...
15
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 June 2014