sr-users

sr-users@lists.kamailio.org

22 participants
37573 discussions

[Serusers] Warning 392 : Noisy Feedback Tells
by Abdul Khadar 11 Dec '09

11 Dec '09

Hi, I need help for registering with iptel.org I have created one user called hitechabdul with iptel.org When I am trying to register with this domain, It is returing error *401 Unauthorized *with *Warning 392 : Noisy Feedback Tells* please find attached ethereal packet and help me to resolve this problem. The details filling with register message : username : hitechabdul password : xxxxxx Domain Name : iptel.org Other than this Is I have to given any more data ? -- thanks & regards, Abdul Khadar Shaik,

2 1

[Kamailio-Users] Rewrite $tU
by David 11 Dec '09

11 Dec '09

Hey, I need to rewrite the $tU variable on a packet before it is relayed. It is ok if the change is only on the relayed packet and the $tU variable change. The important thing is that I modify the To header, it seems that rewritting $tU would be the easiest. I know that user agents do not like this changing, but I am changing it on an intermediary server and when the reply comes back, I change it back to the original value. Thanks! David

5 6

Case sensitivity in usrloc "location" table
by Bruce McAlister 10 Dec '09

10 Dec '09

Hi All, I am trying to integrate Kamailio (1.5.2-notls) into our existing database structure using a view for the subscriber table and using the location table to store the registration information. I am successfully able to register a phone using this method. One of our requirements is to set an "outboundproxy" and "outboundproxyport" parameter in the location table for a particular sip account (username). I am trying to do this with the sqlops module. What I have come across though is that when the registration information is saved to the location table the username is stored in lower case. So when my sqlops query is run against the username it does not match. Is there a way to tell the usrloc module to store the username in the same case as it is received? For example, in the subscriber table I have view defined that for my user account returns the following information: ------------- select * from subscriber where username = 'BruceNW9440'; username | domain | password | ha1 | ha1b -------------+---------------+------------+----------------------------------+---------------------------------- BruceNW9440 | 10.10.10.10 | 00minger00 | 1f2d688f65be04a61cab36a1fb3f426a | 6529d45f5c418daf35be7b3dd4a858cb (1 row) ------------- Now, if I check the above against the location table: -------------- select * from location where username = 'BruceNW9440'; 0 rows returned -------------- If I run the same query using "brucenw9440" as the username (lowercase) then the correct information is returned. I have the following log line in my kamailio configuration script: xlog("L_INFO","Username: $au, OutboundProxy: $Ri, OutboundProxyPort: $Rp"); The details of this log appear correct when it is logged: Dec 9 14:21:03 ibis /opt/kamailio/sbin/kamailio[16972]: [ID 197553 local0.info] Username: BruceNW9440, OutboundProxy: 10.10.10.10, OutboundProxyPort: 5060 However, when my sqlopt query is run it does not find a match because of the incorrect case: sql_query("bfl", "UPDATE location SET outboundproxy = '$Ri', outboundproxyport = '$Rp' WHERE username = '$au'", "res"); I've had a read through the usrloc module documentation and I cannot seem to find a reference to any options that will preserve the case. I also cannot find if there is a parameter to save('location') that will preserve the case. I cant seem to find a reference to the save() function on the wiki. I must be missing something small. We have some sip usernames that are case sensitive so any help in being able to resolve this would be greatly appreciated. Thanks Bruce

4 9

[Kamailio-Users] Question regarding TM module DNS failover with SRV records
by Nathan Angelacos 10 Dec '09

10 Dec '09

According to the 1.5.x TM module documentation, DNS failover is triggered by a 503 reply or a timeout. When using SRV records, it appears a 503 triggers the failure_route instead. Given: host -t srv _sip._udp.voip.example.net _sip._udp.voip.example.net has SRV record 1 0 5060 fast-server.example.net. _sip._udp.voip.example.net has SRV record 2 0 5060 slow-server.example.net. On an invite to voip.example.net, if fast-server does not respond within "fr_timer" seconds, t_relay fires off a serial branch (t_on_branch is triggered) and the invite goes to slow-server. If fast-server responds with a 503, the t_on_failure route is triggered instead, and the invite is not sent on to slow-server. If its not a bug in the module, does anyone have clues of how to coax the next DNS SRV record out of the t_on_failure route? Or what can be done to get t_relay to consume the 503? Thanks!

3 7

[Kamailio-Users] ldap_search get result URL
by Andrey Utkin 10 Dec '09

10 Dec '09

How can i access LDAP URI of ldap_search() results in routing script? I need to do recursive search in company directory within persons that belong to groups, i need to get group id without storing groupid as person attribute, but as an element of resulting URL. Query base name: dc=example,dc=com. Query result is cn=user1,ou=group1,dc=example,dc=com. I can easily get user1 attributes, but how to get ou?

3 3

[Kamailio-Users] kam 1.5 dispatcher priority usage
by Robert McGilvray 10 Dec '09

10 Dec '09

What is the function of the priority field in dispatcher module? The docs are pretty light on the subject and it's not clear to me what it's meant to do. I'm looking for a way to assign a priority to preferred gateways within the same group. Thanks 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.

4 4

[Kamailio-Users] Siremis login page once and again.
by Vicente 10 Dec '09

10 Dec '09

Hello, I've installed siremis 0.9.4 with kamailio 3.0.0rc2 on a test computer and it was working without a problem. But now I'm trying to install it on a server and I can't go beyond the login screen. If I try a wrong password I get the error message. But if I use the right one I'm redirected to the login screen again and again. Both systems are ubuntu Linux with the following differences: Test computer Server Ubuntu 9.10 Ubuntu 8.10 apache 2.2.12 apache2.2.9 PHP 5.2.10 PHP 5.2.6 mysqld 5.1.37 mysqld 5.0.67 The bigger difference that I can see is mysqld version.But I've installed PHPOpenBiz framwork and the demo app creates and populates the demo data base. So it doesn't look like related to this. I've used the apache configuration on the siremis install page to set up apache for both systems. Although on the server there are some previous settings, I've created a new virtual server for siremis. apache logs only show: File does not exist: /var/www/siremis-0.9.4/siremis-web/js/sound.js But this error also appears on the working computer. And doesn't seem to be related with the problem. The log_DEBUG.html on siremis only shows the query to the database. ¿ Is there any log file on siremis that can point to the problem ? ¿ Has anyone else had this problem ? Sorry if I ask something silly but I've been trying to find what I'm doing wrong for two days. Best regards. Vicente.

2 1

Perl Module Logging Query
by Bruce McAlister 09 Dec '09

09 Dec '09

Hi All, I have been trying to use the perl module with Kamailio 1.5.3-notls. I have managed to load the module successfully. I have a simple script with a single function that strips the "<" or ">" from a contact header and logs the info, then sets an AVP. Kamailio seems to load the perl module and the script properly, but when it runs I get an error on the logging side of it. I cannot for the life of me see where the error lies. Could one of you guru's out there please cast an eye over my config and see if you can spot something I am missing. My kamailio configuration for perl is as such: ---- loadmodule "perl.so" modparam("perl", "modpath", "/opt/kamailio/lib64/perl") modparam("perl", "filename", "/opt/kamailio/perl-scripts/kamailio-perl.pl") ---- My perl script looks as follows: ---- use OpenSER ; use OpenSER::Message ; sub clean_contact { my $contact_header = shift; log("contact header passed: $contact_header\n"); $contact_header =~ s/^<|>$//g; log("contact header fixed: $contact_header\n"); OpenSER::AVP::add("clnct", "$contact_header"); return 1; } ---- I have the following section in the route logic that calls this function as follows: ---- perl_exec_simple("clean_contact","$ct"); ---- When the perl script executes, it gets to the first log line and dies with the following message: ---- ERROR:core:XS_OpenSER__Message_log: perl error: Can't take log of 0 at /opt/kamailio/perl-scripts/kamailio-perl.pl line 7. ---- I have had a look at the logging.pl script in the sample directory for the perl module, and have tried all the methods shown in the example, but I just cannot seem to get past this particular logging issue. Any tips would be greatly appreciated. Thanks Bruce

1 1

[Kamailio-Users] Problem with REGISTER
by Uriel Rozenbaum 09 Dec '09

09 Dec '09

Hello guys, I'm having a strange problem with my Kamailio 1.5.3 when trying to register an Audiocodes Gateway. I'm using authentication for REGISTER messages. The GW sends a REGISTER without credentials, so I do a proxy_challenge. Then the GW sends a REGISTER with credentials but the proxy_authorize is returning -4. I did an NGREP to check the messages and they don't seem malformed, can you tell me if there is something on the functions that might be loosing the Proxy-Authorization header? This happens only with this GW, not if i register a softphone (XLITE). Within route block: ... if (is_method("REGISTER")) { route(11); save("location"); exit(); } ... Route(11): route[11] { # ----- AUTENTICACION DE UN MENSAJE ----- if (!proxy_authorize("", "subscriber")) { switch($retcode) { case -1: xlog("L_INFO", "AUTH: Invalid username\n"); sl_send_reply("403", "Forbidden"); exit; case -2: xlog("L_INFO", "AUTH: Invalid password\n"); sl_send_reply("403", "Forbidden"); exit; case -3: xlog("L_INFO", "AUTH: Nonce ambiguo\n"); break; case -4: xlog("L_INFO", "AUTH: No credentials\n"); break; #default: #xlog("L_INFO", "AUTH: Unknown error\n"); #break; } #xlog("L_DBG", "AUTH: -Data- Auth Username = $au\n"); #xlog("L_DBG", "AUTH: -Data- Domain = $fd\n"); #xlog("L_DBG", "AUTH: -Data- From Username = $fU\n"); proxy_challenge("192.168.200.130","0"); exit; }; xlog("L_INFO", "AUTH: Valid username and credentials\n"); consume_credentials(); } NGREP: # U 10.0.1.200:5060 -> 192.168.200.130:5060 REGISTER sip:192.168.200.130 SIP/2.0. Via: SIP/2.0/UDP 10.0.1.200;branch=z9hG4bKac26395445. Max-Forwards: 70. From: <sip:testdevice@10.0.1.200 <sip%3Atestdevice(a)10.0.1.200> >;tag=1c26389068. To: <sip:testdevice@10.0.1.200 <sip%3Atestdevice(a)10.0.1.200>>. Call-ID: 154992670511200004613(a)10.0.1.200. CSeq: 68 REGISTER. Contact: <sip:testdevice@10.0.1.200:5060>;expires=180. Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE. Expires: 180. User-Agent: Audiocodes-Sip-Gateway-/v.5.80A.023.006. Content-Length: 0. . # U 192.168.200.130:5060 -> 10.0.1.200:5060 SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/UDP 10.0.1.200;branch=z9hG4bKac26395445. From: <sip:testdevice@10.0.1.200 <sip%3Atestdevice(a)10.0.1.200> >;tag=1c26389068. To: <sip:testdevice@10.0.1.200 <sip%3Atestdevice(a)10.0.1.200> >;tag=f8f2ab2c1295e90ed7dbb499b30f44b2.ee1a. Call-ID: 154992670511200004613(a)10.0.1.200. CSeq: 68 REGISTER. Proxy-Authenticate: Digest realm="192.168.200.130", nonce="4b142e8900000000188436d32ee472791b706f36952f4162". Server: Kamailio (1.5.3-notls (i386/linux)). Content-Length: 0. . # U 10.0.1.200:5060 -> 192.168.200.130:5060 REGISTER sip:192.168.200.130 SIP/2.0. Via: SIP/2.0/UDP 10.0.1.200;branch=z9hG4bKac26766380. Max-Forwards: 70. From: <sip:testdevice@10.0.1.200 <sip%3Atestdevice(a)10.0.1.200> >;tag=1c26389068. To: <sip:testdevice@10.0.1.200 <sip%3Atestdevice(a)10.0.1.200>>. Call-ID: 154992670511200004613(a)10.0.1.200. CSeq: 69 REGISTER. Proxy-Authorization: Digest username="testdevice",realm="192.168.200.130",nonce="4b142e8900000000188436d32ee472791b706f36952f4162",uri="sip:192.168.200.130",algorithm=MD5,response="9fa0904b94f94152619a16c46ffa6485". Contact: <sip:testdevice@10.0.1.200:5060>;expires=180. Allow: REGISTER,OPTIONS,INVITE,ACK,CANCEL,BYE,NOTIFY,PRACK,REFER,INFO,SUBSCRIBE,UPDATE. Expires: 180. User-Agent: Audiocodes-Sip-Gateway-/v.5.80A.023.006. Content-Length: 0. . # U 192.168.200.130:5060 -> 10.0.1.200:5060 SIP/2.0 407 Proxy Authentication Required. Via: SIP/2.0/UDP 10.0.1.200;branch=z9hG4bKac26766380. From: <sip:testdevice@10.0.1.200 <sip%3Atestdevice(a)10.0.1.200> >;tag=1c26389068. To: <sip:testdevice@10.0.1.200 <sip%3Atestdevice(a)10.0.1.200> >;tag=f8f2ab2c1295e90ed7dbb499b30f44b2.b7c8. Call-ID: 154992670511200004613(a)10.0.1.200. CSeq: 69 REGISTER. Proxy-Authenticate: Digest realm="192.168.200.130", nonce="4b142e8900000001515ab7891a3d534cc3f15e5627322da3". Server: Kamailio (1.5.3-notls (i386/linux)). Content-Length: 0. . Thanks in advance! Uriel

3 5

Upgrade Serweb from version 0.9.4 to version 2.0.1-dev1
by inge 09 Dec '09

09 Dec '09

Hi, I have to upgrade Serweb to the version 2.0.1-dev1 (that work with SER 2.0). Is it possible to use Serweb 0.9.4 (using PHP v.5.1.6) with SER 2.0 however the database "ser" has a new structure? Regards, David.

1 0

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