hello guys,
just wanted to add the snmpstats modules to our kamailio 4.2.1 installation.
but we are running into a libssnmp15 dependency.
searching google showed me that on 14.04 the lib is called libsnmp30 now.
does anybody know how to fix this?
thanks,
rené
-------------------
root@kamailio1:~# apt-get install kamailio-snmpstats-modules
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
kamailio-snmpstats-modules : Depends: libsnmp15 (>= 5.4.3~dfsg) but it is not
installable
E: Unable to correct problems, you have held broken packages.
root@kamailio1:~#
Hey Guys
I need assistance for the following case:
I receive dialog_end request from external component in
evapi:message-received block and would like to somehow kill the dialog
corresponding to h_id and h_entry I get in the message. Is there any way to
do that without involving mi_*?
Any tip appreciated!
Ta,
DanB.
Hello,
I´m doing a test with the ul.dump output on both Kamailio 4.1.5 or 4.2.1
and it works great if the number of registered users is 26 or lower.
Starting with 27 registered users the "kamcmd ul.dump" command returns the
error:
"error: 500 - Internal error creating aor struct"
In Kamailio 4.2.1 the new (and nice) "kamcmd stats.get_statistics usrloc:"
returns the correct number of registered_users without this "26 limit".
Its possible to check why ul.dump is failing this way?
Thanks,
Hello,
I need migrate users from the old proprietary softswitch but they have
predefined from/to header which is differ from auth username.
I read about flags in auth_check but I need strict pairs from user/auth
username.
How this authentication scheme could be implemented with Kamailio?
-- Dmitry
Hi,
I would like some help from a kamailio expert.
I have installed on a Debian7 64 kbytes VPS this tutorial:
http://kb.asipto.com/kamailio:skype-like-service-in-less-than-one-hour,
Problem is that there is no voice in a zrtp connection, but i hear only the ring sound ok.
Strange is that on my local wifi works all perfect including the voice, but with external ip no.
Any help? I would like to hire a kamailio expert for fixing this and also adding some extras.
Write me directly so we could get in contact.
regards, javier
Does anyone have feedback about this?
-H
From: Henry Fernandes <henry(a)usinternet.com>
Date: Wednesday, December 17, 2014 at 3:39 PM
To: "Kamailio (SER) - Users Mailing List" <sr-users(a)lists.sip-router.org>
Subject: bug in allow_source_address?
I¹m using allow_source_address in my Kamailio config and have been for
months/years. I¹ve had no issues with it until today.
The issue is that allow_source_address("1²) returns ³1" (for
$si=123.17.29.201 and $sp=5060) even though we don¹t have this IP address in
the address¹ table for group 1. We have defined this IP address for group
2 but not group 1.
select * from address order by mask;
+----+-----+---------------+------+------+----------+
| id | grp | ip_addr | mask | port | tag |
+----+-----+---------------+------+------+----------+
| 20 | 1 | 123.17.0.0 | 23 | 5061 | Testing |
| 22 | 1 | 123.17.0.0 | 23 | 5062 | Testing |
| 23 | 1 | 123.17.0.0 | 23 | 5063 | Testing |
| 24 | 1 | 123.17.0.0 | 23 | 5064 | Testing |
| 1 | 1 | 123.17.0.0 | 23 | 5060 | |
| 4 | 1 | 20.5.176.0 | 24 | 5060 | |
| 21 | 1 | 123.17.1.235 | 32 | 5060 | Override |
| 46 | 2 | 123.17.29.201 | 32 | 5060 | customer |
+----+-----+---------------+------+------+----------+
Can anyone explain this? I¹m wondering if there¹s a bug in how
allow_source_address does its net mask calculations.
-H
i made a test where domain name in request uri hostpart has two udp srv
records, one with higher priority than the other.
when i turn off the higher priority uac, there is about 5 sec delay
before the lower priority uac starts to ring. if i make another call
within a small number of seconds from the previous one, my sip proxy
remembers that the higher priority uac is dead and the lower priority
one starts to ring immediately. but if i wait about five seconds or
more, my sip proxy again first tries the higher priority uac and there
is again the about 5 second delay before the lower priority one starts
to ring.
i have in config
use_dst_blacklist=on
dst_blacklist_expire=20
from the docs i get the impression that my sip proxy should remember 20
seconds that the higher priority uac is dead, but it only remembers it
about 5 seconds. what could be the explanation?
-- juha