sr-users

sr-users@lists.kamailio.org

18 participants
37571 discussions

[Kamailio-Users] Fwd: Kamailio as a proxy between Trunk and PBX.
by Espen Berg 26 Mar '10

26 Mar '10

We are planning a new voip system. The trunk is provided to us on a private 10.x.x.x/29 range, and therefore not available direct to our end customers. We plan to have some kind of SIP/RTP proxy in front of the trunk, and a PBX in front of this. The trunk doesn't have any authentication, the end customers should connect and authenticate to the PBX in front, and the RTP streams should terminate to the proxy. Is this possible to achieve by using Kamailio and RTPProxy? Trunk | | 10.x.x.x/29 | SIP Proxy | PBX Asterisk etc. | Customer I have tried many different configurations and browsed every bundled example and web, but still I am not able to do what I want. This have already given me some grey hears, so I guess it's time to check if this is even possible. If not, is there any other approach that is more recommendable? If someone has done this before I would appreciate some example configuration that I could work with. Regards Espen, Norway

2 2

[Serusers] change in mailing list management
by Pavel Kasparek 26 Mar '10

26 Mar '10

Hello all, since now it is possible to use only web interface to manage mailing lists hosted on lists.iptel.org server. We had to disable the email commands interface as part of fight against spam (it was causing too many messages being sent from us, recognized by some blacklists as spam). This means that for all actions like subscribing, un-subscribing, changing your preferences etc. you have to use the web interface. You can find a link to it at end of every message sent to the mailing list. Sorry if it causes any inconvenience to you. Pavel Kasparek

1 0

[Kamailio-Users] Kamailio 3.0.1
by dotnetdub 26 Mar '10

26 Mar '10

Hi List, I have Kamailio 3.0.1 running from GIT with my old 1.5.3 config file. Everything seems fine except the RPID. I'm not getting any RPID sent in the SIP message and if I put debug=3 I see: DEBUG: auth [rpid.c:177]: no rpid AVP My config: # auth modparam("auth", "rpid_avp", "$avp(s:rpid)") modparam("auth", "rpid_prefix", "<sip:") modparam("auth", "rpid_suffix","@asterisk.ie ;party=calling;id-type=subscriber;privacy=off;screen=yes>") # auth_db modparam("auth_db", "db_url", "mysql://openser:XSXXXX@localhost/openser") modparam("auth_db", "calculate_ha1", 1) modparam("auth_db", "password_column", "password") modparam("auth_db", "load_credentials", "$avp(s:rpid)=rpid") in my route: append_rpid_hf(); Probably missing something very simple. Any help would be appreciated. Thanks, Stephen.

2 13

route() call with pv argument
by jh＠tutpro.com 25 Mar '10

25 Mar '10

i just made a test and noticed that route() accepts a pv argument. at least i didn't get anhy syntax error from route("$var(test)"); this is good if it works. Core functions section of http://sip-router.org/wiki/cookbooks/core-cookbook/devel#route does not list route() function call at all. -- juha

2 6

[Kamailio-Users] fr_inv_timer not honored (fr_inv_timer/2 is used in fact)
by Iñaki Baz Castillo 25 Mar '10

25 Mar '10

Hi, I set fr_inv_timer=150 and use lcr module to balance (and failover) between two gateways. In the failure route I set (simplified): failure_route[FAILURE_ROUTE_OUT] { if (t_local_replied("last")) { next_gw(); t_relay(); } } This means that if a INVITE routed to gateway-1 replies a provisional response but no final response within 150 seconds, then Kamailio should generate a local 408 and failure route would relaty to gateway-2. But what I see is that such "timeout" time is 75 seconds (the half of 150 !). I remember a similar "issue" when handling with SRV DNS domains returning more than one destinations, but in my case I just use single IP's in lcr module. But the fact is that I use exactly 2 gateways in lcr (150/2 = 75). But anyhow it doesn't make sense. Do I miss something? Thanks. PD: Important, could occur the same with fr_timer? -- Iñaki Baz Castillo <ibc(a)aliax.net>

2 11

route is not called and no error is produced
by jh＠tutpro.com 25 Mar '10

25 Mar '10

i tested if route() with pv arg would work. i created a route block: route [test] { xlog("here we are\n"); return; } and then as the very first thing in the main route block i have: $var(test) = "test"; route("$var(test)"); then i send the proxy a sip request and don't get anything related to this to syslog, i.e., no "here we are" line nor any error message. this looks like i bug to me, since if route() accepts a pv, i should see "here we are" syslog entry or if it doesn't, i should see some kind of error message. comments? -- juha

1 0

[Kamailio-Users] Establish Call but no audio transferred on different network
by RAJNIKANT VANZA 25 Mar '10

25 Mar '10

Hello all, I am using kamailio-1.5.0 + mediaproxy. it works properly when connection is in between two clients between same lan. But when I connecting between two client who are on differet proxy and behind different NAT, call has been established but no audio get transferred. What are the changed i suppose to do, or any parameters should get enabled while compilation, Thanks in advance. -- Best Regards, Rajnikant Vanza

2 1

[Kamailio-Users] Radius
by dotnetdub 25 Mar '10

25 Mar '10

Hi, I'm using Kamailio - posted this to the opensips list as I thought I may get support from the ag guys but nothing.. Has anyone else experienced this or have an idea as to what it may be? Having a very small but annoying issue with Radius Accounting. Everything is getting written fine except for 'Source-Port' This appears in radius.log everytime a record is written/updated. - Error: rlm_radutmp: NAS OpenSER port 5060 unknown packet type 15 It's writing this into the text files and value to the radacct table: Source-Port = "\304\023" All other information is being written correctly. CDRTool version: 7.0 Freeradius version: 1.1.7-4 mediaproxy version: 2.3.10 Kamailio Version: 1.5.3 Using the dictionary files that ship with CDRTool >From accounting: modparam("acc", "db_url", "mysql://openser:XXXXXXXXXXXX@localhost/openser") modparam("acc", "db_flag", 2) modparam("acc", "log_flag", 2) modparam("acc", "db_missed_flag", 3) modparam("acc", "radius_config", "/etc/radiusclient-ng/radiusclient.conf") modparam("acc", "radius_flag", 2) modparam("acc", "radius_missed_flag", 3) modparam("acc", "radius_extra", "User-Name=$Au; \ Calling-Station-Id=$from; \ Called-Station-Id=$to; \ Sip-Translated-Request-URI=$avp(s:translated_uri); \ Sip-RPid=$avp(s:rpid); \ Source-IP=$si; \ Source-Port=$sp; \ Canonical-URI=$avp(s:can_uri); \ Billing-Party=$avp(s:billing_party); \ Divert-Reason=$avp(s:divert_reason); \ X-RTP-Stat=$hdr(X-RTP-Stat); \ Contact=$hdr(contact); \ Event=$hdr(event); \ SIP-Proxy-IP=$avp(s:sip_proxy_ip); \ ENUM-TLD=$avp(s:enum_tld)") Obviously it's not a show stopper but it's just bugging the hell out of me :) If any more info is required please let me know and I will provide ASAP. TIA, Stephen

2 2

[Kamailio-Users] Kamdbctl not installing and Install error
by Nathaniel L Keeling 24 Mar '10

24 Mar '10

I have installed Kamailio 3.0 but without db support. When I tried to add support for postgres, the install errors and the kamdbctl does not install in order to create the database tables. I am installing on Solaris 10 and have included the error from the install: Makefile.defs defs skipped gmake[1]: Entering directory `/usr/local/src/kamailio-3.0.0/modules_k/xlog' touch /usr/local/kamailio-3.0.0/lib/kamailio/modules_k/xlog.so ginstall -m 755 xlog.so /usr/local/kamailio-3.0.0/lib/kamailio/modules_k gmake[1]: Leaving directory `/usr/local/src/kamailio-3.0.0/modules_k/xlog' # other configs /bin/sh: syntax error at line 1: `;' unexpected gmake: *** [install-cfg] Error 2 Thanks Nathaniel

4 7

why is while loop not terminated?
by jh＠tutpro.com 24 Mar '10

24 Mar '10

i'm in the process of enhancing enum mudule enum_query, so that suffic param can be given in a pseudo variable. before committing to git, i tested if the new version is working correctly, and for that purpose wrote this kind of route: route [PERFORM_ENUM_QUERIES] { xlog("L_INFO", "suffix_list = <$var(suffix_list)>\n"); $var(i) = 0; $var(domain) = $(var(domain_list){s.select,0,,}); while ($var(domain) != "") { xlog("L_INFO", "Query $var(i) for $var(domain)\n"); if (enum_query("$var(domain)")) { xlog("L_INFO", "Return success!\n"); return(1); }; $var(i) = $var(i) + 1; $var(domain) = $(var(domain_list){s.select,$var(i),,}); }; return(-1); } looks like the enhanced enum_query works as expected, but the while loop is not terminating by the return(1) statement (see below). i'm puzzled. have i done some stupid mistake that i cannot see? -- juha Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: suffix_list = <e164.test.fi.> Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: enum [enum.c:724]: Got suffix <e164.test.fi.> Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Return success! Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: INFO: Query 0 for e164.test.fi. Mar 24 18:29:56 localhost /usr/sbin/sip-proxy[24589]: ERROR: <core> [action.c:1144]: ERROR: runaway while (1342, 25): more then 100 loops

1 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