sr-users October 2009

sr-users@lists.kamailio.org

63 participants
105 discussions

[Kamailio-Users] Problem with LCR "ping"

by Ricardo Martinez

Hello list. I have a question/problem regarding the LCR module. I'm using Kamailio version 1.5.2. The LCR tables have : gw table : 126 records lrc tables : 120 records. I'm using the "ping" (ping = 1) feature in all my gateways, part of the cfg file is as follows : modparam("lcr","db_url","mysql://openserro:openserro@localhost/openser") modparam("tm", "fr_inv_timer_avp", "$avp(i:704)") modparam("lcr", "gw_uri_avp", "$avp(i:709)") modparam("^auth$|lcr", "rpid_avp", "$avp(i:302)") modparam("lcr", "ruri_user_avp", "$avp(i:500)") modparam("lcr", "flags_avp", "$avp(i:712)") modparam("lcr", "fetch_rows", 3000) modparam("lcr", "ping_interval", 10) modparam("lcr", "ping_from", "sip:pinger@mydomain.net") modparam("lcr", "ping_method", "OPTIONS") >From time to time I can see 3 o 4 gateways marked as down (with the command kamctl lcr dump). I'm not manually monitoring the gateways every minute so is possible that in a particular moment the gateways could be unreachable, but when I run the command "kamctl lcr dump" the gateways are on-line, that's for sure. So I'm not understanding why LCR keep marking the gateways as down, even if they are answering to the OPTIONS request. Could this be a bug in the LCR module? Or maybe I'm missing something?. The silly part of all this is the gateways marked as down are always the same. Could this be related to a memory issue?? Can someone guide me here?. Thanks in advance, Regards, Ricardo Martinez.-

14 years, 7 months

[Kamailio-Users] dispatcher failover between two groups

by Robert McGilvray

Kam 1.5 I'm using dialplan module to return a setid for the matching regex which is passed onto dispatcher to select the proper gateways. This works fine including failover to the next gateway in the group in failure_route. What I can't quite wrap my head around is how I can setup failover between different dispatcher groups. The scenario is as follows: 2 external PSTN gateways (sip trunks) in group 1 6 internal gateways with PSTN access via PRIs. Two gateways per group for a total of three separate setids in dispatcher. I'm doing some LCR across the 6 internal gateways which are all in different cities via regex matching in dialplan. What I'd like to do is try one of the internal groups first if it matches the local NPA/NXX, and if ALL gateways in that group fail move on to the external gateway group, and try all those gateways (and vice versa in my external gateways fail for non matching numbers). I thought of two possible solutions but I'm not sure if either will work how I expect. 1) Use the priority field in dispatcher to setup a large gateway group that has all the gateways I want to use. - I tested this out in kam 1.5 and the priority field seems to be ignored when hasing on call-id. - What is the intended usage of priority? Will setting two gateways to 0 and the rest to 10 cause the load balancing functions to only select the ones with 0? It seems to be ignoring priority and using all 8 gateways 2) Once in a failure_route can I move the processing into a request_route and call ds_select_dst again with a different setid and append it as a branch? Is there a cleaner solution? Bob -------------------------------------------------------------------------- This email with all information contained herein or attached hereto may contain confidential and/or privileged information intended for the addressee(s) only. If you have received this email in error, please contact the sender and immediately delete this email in its entirety and any attachments thereto.

14 years, 7 months

[Kamailio-Users] Codecs

by Anders

Hi, A very basis 101-question, which I couldn't find the answer to elsewhere: how/where do I see/set codecs allowed and disallowed in Kamailio? Thanks!

14 years, 7 months

Re: [Kamailio-Users] Having problems using RTPProxy to bridge internal/external networks

by Örn Arnarson

Hi, I have exactly the same scenario; no NAT involved. Just trying to bridge between these two interfaces. Now, to clarify better what I have done; As I understand it, force_rtp_proxy / rtpproxy_offer needs to be used to inform RTP proxy that it will have to relay the packets. So, that pretty much makes it necessary to use that call. As I understand it, you can't call both fix_nated_sdp and force_rtp_proxy, as the SDP will be mangled (two IP addresses, one after the other). However, I can't get the SDP rewritten properly without using fix_nated_sdp. No matter how I call force_rtp_proxy, I can't specify my own IP address. It works as expected when using fix_nated_sdp though. Here's how I call it: force_rtp_proxy("coe","10.252.1.8"); I've tried multiple variants of flags, c, co, o, coe, coi, i, no flags, etc etc, but no matter what I do, the public interface IP address does not change to the one supplied in the function, and remains the public IP address. So, to summarize; I can change all the headers to be correct with the fix_nated_sdp function. When using that function, RTPProxy does not relay the RTP streams. When I use force_rtp_proxy / rtpproxy_offer, RTPProxy does indeed relay the streams, but does not alter the SDP IP address information to the required specifications. Is there something that I'm missing in the usage of the force_rtp_proxy function, or is it not working as documented? Best regards, Örn 2009/10/14 Alex Balashov <abalashov(a)evaristesys.com>: > Örn Arnarson wrote: > >> Oh, I forgot one thing; >> >> I'm using fix_nated_sdp, as previously mentioned. I have a hunch that >> because I'm not using force_rtp_proxy/rtpproxy_offer it's not being >> relayed (a hunch, because I don't fully understand how rtpproxy >> works). Problem is though, I can't get the IP addresses correct by >> using rtpproxy_offer. > > On behalf of Joe (same company) I will add that there is no NAT scenario > here. Both the private and public network are directly routable from the > rtpproxy box; there is no IP address oversubscription, and no reason to > ignore ports or addresses in SDP and replace them with received parameters. > This is not a far-end NAT traversal solution. > > What is basically being asked here is how to bridge between two interfaces > (internal, external) without NAT using rtpproxy, and if anyone can provide a > canonical implementation or example. > > We've got it running in bridge mode, e.g. > > rtpproxy -F -s udp:10.x.x.x:5050 -l 10.x.x.x/89.y.y.y > > ... and basically, are just wondering how to get this to work on the > Kamailio side using rtpproxy_offer()/rtpproxy_answer(). > > The RTP proxy machine is a dedicated host; the SIP proxies are virtual. > > > -- > Alex Balashov - Principal > Evariste Systems > Web : http://www.evaristesys.com/ > Tel : (+1) (678) 954-0670 > Direct : (+1) (678) 954-0671 >

14 years, 7 months

[Kamailio-Users] SIP-T messages

by Luis Jimenez

Hi, can some one please guide me on how can i parse the received SIP-T messages from the SDP in Kamailio. Thanks in advance Luis Jimenez

14 years, 7 months

[Kamailio-Users] How to remove route header field

by Mythili D

hii..Good morning. When we are making a call from one UA to other UA, it passes through proxies. ACK message also passes through the proxies. But i need the ACK message not to go through proxies. It must directly go from UA to UA. How can i make in cfg. There must not be route header filed in SIP meessage flow. Please help me. Thanks & Regards, Mythili.K

14 years, 7 months

[Kamailio-Users] AVP problem

by Ricardo Martinez

Hello list. I'm getting this error trying to start the kamailio process /usr/local/sbin/kamailio[29243]: INFO:core:init_mod: initializing module mediaproxy /usr/local/sbin/kamailio[29243]: ERROR:core:pv_parse_spec: error searching pvar "avp" /usr/local/sbin/kamailio[29243]: ERROR:core:pv_parse_spec: wrong char [s/115] in [$avp(s:signaling_ip)] at [5 (5)] /usr/local/sbin/kamailio[29243]: CRITICAL:mediaproxy:mod_init: invalid AVP specification for signaling_ip_avp: `$avp(s:signaling_ip)' /usr/local/sbin/kamailio[29243]: ERROR:core:init_mod: failed to initialize module mediaproxy This is the line in the kamailio.cfg file : modparam("mediaproxy", "signaling_ip_avp", "$avp(s:signaling_ip)") I'm using kamailio 1.5.2 What I'm missing here?. Thanks, Ricardo Martinez

14 years, 7 months

[Kamailio-Users] SIMPLE vs XMPP: The Resolution

by Iñaki Baz Castillo

Architectures of XMPP and SIMPLE (OMA specifications) for a full rich presence environment: - XMPP: http://oversip.net/public/XMPP.jpeg - SIMPLE (OMA): http://oversip.net/public/SIP_SIMPLE_OMA.jpeg -- Iñaki Baz Castillo <ibc(a)aliax.net>

14 years, 7 months

[Kamailio-Users] SIMPLE vs XMPP: The Resolution

by Iñaki Baz Castillo

Attached the architecture of XMPP and SIMPLE (OMA specifications) for a presence environment. Self explanatory. -- Iñaki Baz Castillo <ibc(a)aliax.net>

14 years, 7 months

[Kamailio-Users] Connecting two or more proxies

by Mythili D

Hi Good morning. I'm going to connect two proxies. I'm having two servers with openser installed. One user (UAC) will register with one server in one system which is not having openser and the other user (UAS) will register with second server in other syatem which is not having openser. I want to connect the two proxies through cfg file. Hoiw to give the connection. My IP's are UAC registered with 1000(a)192.168.64.77 at other system (192.168.64.85) 192.168.64.77 is one proxy. 192.168.64.94 is secind proxy. UAS registerd with 10(a)192.168.64.94 at other system (192.168.64.128) Now the person at 85 registered with 77 is going to call the person at 128 registered with 94. I have configuered my cfg's in this way: In 77 cfg file, i configuered *if(is_method("INVITE") && !src_ip=="192.168.64.77") * *{ * * rewritehost("192.168.64.77"); * *} * ** In 99 cfg file, i configuered *if(is_method("INVITE") && !src_ip=="192.168.64.94") * *{ * *rewritehost("192.168.64.94"); * *}* Is there any other way to connect. Please help me as soon as possible. Thanks & Regards, Mythili.K

14 years, 7 months

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

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 October 2009