Hello,
I've setup Kamailio 4 + Asterisk 11
following asipto guide (
http://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb)
I've got my Kamailio listening on Public IP+ loopback and Asterisk only on
loopback.
Configuring RPTProxy in bridge mode I've been able to get it everything
working.
My question is hwo can I replace rtpproxy by ngcp-mediaproxy-ng in bridge
mode ?
Does it possible ?
I use "rwie" and "rwei" flags but in ngcp-mediaproxy-ng e and i seems
to be used for IPv4 / IPv6 ..
Thank you for your help
Best regards
hi all
OS ubuntu 12.04 or ubuntu 10.04 - just did a check with debian 7 - same problem
Module carrierroute not working starting from version kamailio 4.0.x
trying to activate carrierroute in kamailio.cfg
loadmodule "carrierroute.so"
i get the following error when starting kamailio
0(7547) ERROR: <core> [sr_module.c:572]: load_module(): ERROR: load_module: could not open module </usr/lib64/kamailio/modules/carrierroute.so>: /usr/lib64/kamailio/modules/carrierroute.so: undefined symbol: cfg_set_error_function
0(7547) : <core> [cfg.y:3567]: yyerror_at(): parse error in config file /etc/kamailio/kamailio.cfg, line 219, column 12-28: failed to load module
ERROR: bad config file (1 errors)
the function "cfg_set_error_function" is different, if i use another linux system. I tested with ubuntu 12.04 & 10.04.
I installed with apt-get install and I also compiled the version using GIT.
I did a crosscheck with kamailio 3.3 and there it seems to work!
Any idea?
Regards,
Oli
Freundliche Grüsse
Oliver Roth | TRIOTEL AG
Leiter IT & Entwicklung | Mitglied der Geschäftsleitung
D +41 44 506 06 30 | M +41 79 456 77 35 | oliver.roth(a)triotel.ch<mailto:oliver.roth@triotel.ch>
Kempttalstrasse 113 | 8308 Illnau | www.triotel.ch<http://www.triotel.ch/>
[Beschreibung: stempel]
Hi All,
In nathelper module till kamailio version 3.0 rtpproxy_sock parameter was
available , if I want to use rtp proxy with respect to latest kamailio
version may know in which parameter I have to configure rtp proxy ip. I
kindly request to help us.
Regards,
Prem Chandiran M
Hi,
Klaus, thank you for pointing me in the right direction with SIP trunks,
got it working so thanks! Basically I did exactly what you said:
- Dialled number
- Match that number to a registered user (had to create a new table for
that)
- Lookup user
- Replace dialled s@ with original number dialled
Works like a charm, however, I have a question over speed and performance.
As this is a SQL query and not held in memory is this SQL lookup doing to
cause me problems? It's not a big query at the moment, but it could get
quite big as I will need to map each number to a registered trunk.
Many thanks,
Keith
Just to precise, I seen another discussion with a similar problem.
I test with children=1 and it works (result in 6 MySQL connections!). But it
would be insufficient for production uses.
How can we grow the number of children and keep Kamailio working?
Regards,
Igor.
De : Igor Potjevlesch [mailto:igor.potjevlesch@gmail.com]
Envoyé : vendredi 11 octobre 2013 16:31
À : 'sr-users(a)lists.sip-router.org'
Objet : Kamailio 4.0.4 won't start
Hello,
I dont figure out why Kamailio cant connect to MySQL DB.
DBURL is set :
# *** Value defines - IDs used later in config
#!ifdef WITH_MYSQL
# - database URL - used to connect to database server by modules such
# as: auth_db, acc, usrloc, a.s.o.
#!define DBURL "mysql://kamailio:PASSWORD@192.168.2.6/kamailio"
#!endif
Each module refer to DBURL, like acc :
# ----- acc params -----
/* what special events should be accounted ? */
modparam("acc", "early_media", 0)
modparam("acc", "report_ack", 1)
modparam("acc", "report_cancels", 1)
/* by default ww do not adjust the direct of the sequential requests.
if you enable this parameter, be sure the enable "append_fromtag"
in "rr" module */
modparam("acc", "detect_direction", 0)
/* account triggers (flags) */
modparam("acc", "log_flag", FLT_ACC)
modparam("acc", "log_missed_flag", FLT_ACCMISSED)
modparam("acc", "log_extra",
"src_user=$fU;src_domain=$fd;src_ip=$si;"
"dst_ouser=$tU;dst_user=$rU;dst_domain=$rd")
modparam("acc", "failed_transaction_flag", FLT_ACCFAILED)
/* enhanced DB accounting */
#!ifdef WITH_ACCDB
modparam("acc", "db_flag", FLT_ACC)
modparam("acc", "db_missed_flag", FLT_ACCMISSED)
modparam("acc", "db_url", DBURL)
modparam("acc", "db_extra",
"src_user=$fU;src_domain=$fd;src_ip=$si;"
"dst_ouser=$tU;dst_user=$rU;dst_domain=$rd")
#!endif
When I try a connection from MySQL CLI with the same login and password, it
works.
Here are the output from /var/log/messages (note that public IP address
appears as A.B.C.X) :
Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: rr
[../outbound/api.h:49]: ob_load_api(): Failed to import bind_ob
Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: rr
[rr_mod.c:159]: mod_init(): outbound module not available
Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: usrloc
[hslot.c:53]: ul_init_locks(): locks array size 512
Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: auth
[auth_mod.c:350]: mod_init(): auth: qop set, but nonce-count (nc_enabled)
support disabled
Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: <core>
[udp_server.c:179]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF is
initially 229376
Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: <core>
[udp_server.c:230]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF is
finally 262142
Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: <core>
[udp_server.c:179]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF is
initially 229376
Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: <core>
[udp_server.c:230]: probe_max_receive_buffer(): INFO: udp_init: SO_RCVBUF is
finally 262142
Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10300]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10301]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Oct 11 16:29:38 localhost /usr/local/sbin/kamailio[10302]: INFO: rtpproxy
[rtpproxy.c:1559]: rtpp_test(): rtp proxy <udp:127.0.0.1:7722> found,
support for it enabled
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: ERROR: db_mysql
[km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to
MySQL server on '192.168.2.6' (4)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: ERROR: db_mysql
[km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to
MySQL server on '192.168.2.6' (4)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: ERROR: acc
[acc.c:359]: acc_db_init_child(): unable to connect to the database
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: ERROR: acc
[acc.c:359]: acc_db_init_child(): unable to connect to the database
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: ERROR: acc
[acc_mod.c:689]: child_init(): could not open database connection
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: ERROR: acc
[acc_mod.c:689]: child_init(): could not open database connection
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: ERROR: <core>
[sr_module.c:896]: init_mod_child(): init_mod_child(): Error while
initializing module acc (/usr/local/lib64/kamailio/modules/acc.so)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: ERROR: <core>
[sr_module.c:896]: init_mod_child(): init_mod_child(): Error while
initializing module acc (/usr/local/lib64/kamailio/modules/acc.so)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: ERROR: <core>
[pt.c:350]: fork_process(): ERROR: fork_process(): init_child failed for
process 3, pid 10303, "udp receiver child=2 sock=A.B.C.4:5060"
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: ERROR: <core>
[pt.c:350]: fork_process(): ERROR: fork_process(): init_child failed for
process 6, pid 10306, "udp receiver child=5 sock=A.B.C.4:5060"
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10303]: : <core>
[main.c:1630]: main_loop(): main_loop: Cannot fork
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10306]: : <core>
[main.c:1630]: main_loop(): main_loop: Cannot fork
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: ERROR: db_mysql
[km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to
MySQL server on '192.168.2.6' (4)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: ERROR: acc
[acc.c:359]: acc_db_init_child(): unable to connect to the database
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: ERROR: acc
[acc_mod.c:689]: child_init(): could not open database connection
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: ERROR: <core>
[sr_module.c:896]: init_mod_child(): init_mod_child(): Error while
initializing module acc (/usr/local/lib64/kamailio/modules/acc.so)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: ERROR: <core>
[pt.c:350]: fork_process(): ERROR: fork_process(): init_child failed for
process 4, pid 10304, "udp receiver child=3 sock=A.B.C.4:5060"
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10304]: : <core>
[main.c:1630]: main_loop(): main_loop: Cannot fork
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: ERROR: db_mysql
[km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to
MySQL server on '192.168.2.6' (4)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: ERROR: acc
[acc.c:359]: acc_db_init_child(): unable to connect to the database
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: ERROR: acc
[acc_mod.c:689]: child_init(): could not open database connection
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: ERROR: <core>
[sr_module.c:896]: init_mod_child(): init_mod_child(): Error while
initializing module acc (/usr/local/lib64/kamailio/modules/acc.so)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: ERROR: <core>
[pt.c:350]: fork_process(): ERROR: fork_process(): init_child failed for
process 5, pid 10305, "udp receiver child=4 sock=A.B.C.4:5060"
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10305]: : <core>
[main.c:1630]: main_loop(): main_loop: Cannot fork
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: ERROR: db_mysql
[km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to
MySQL server on '192.168.2.6' (4)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: ERROR: acc
[acc.c:359]: acc_db_init_child(): unable to connect to the database
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: ERROR: acc
[acc_mod.c:689]: child_init(): could not open database connection
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: ERROR: <core>
[sr_module.c:896]: init_mod_child(): init_mod_child(): Error while
initializing module acc (/usr/local/lib64/kamailio/modules/acc.so)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: ERROR: <core>
[pt.c:350]: fork_process(): ERROR: fork_process(): init_child failed for
process 9, pid 10309, "udp receiver child=8 sock=A.B.C.4:5060"
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10309]: : <core>
[main.c:1630]: main_loop(): main_loop: Cannot fork
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10300]: ERROR: db_mysql
[km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to
MySQL server on '192.168.2.6' (4)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10308]: ERROR: db_mysql
[km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to
MySQL server on '192.168.2.6' (4)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10300]: ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10300]: ERROR: usrloc
[ul_mod.c:437]: child_init(): child(0): failed to connect to database
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10308]: ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10300]: ERROR: <core>
[sr_module.c:896]: init_mod_child(): init_mod_child(): Error while
initializing module usrloc (/usr/local/lib64/kamailio/modules/usrloc.so)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10308]: ERROR: acc
[acc.c:359]: acc_db_init_child(): unable to connect to the database
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10308]: ERROR: acc
[acc_mod.c:689]: child_init(): could not open database connection
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10300]: ERROR: <core>
[main.c:1716]: main_loop(): ERROR: main: error in init_child
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10307]: ERROR: db_mysql
[km_my_con.c:109]: db_mysql_new_connection(): driver error: Can't connect to
MySQL server on '192.168.2.6' (4)
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10307]: ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool
Oct 11 16:29:40 localhost /usr/local/sbin/kamailio[10330]: INFO: <core>
[main.c:854]: sig_usr(): INFO: signal 15 received
[...]
Many thanks for your help.
Regards,
Igor.
Hi All,
We are trying to install media proxy and we are able to install but when we
run using ./media-dispatcher --no-fork we are getting below error. I kindly
request to help us.
Traceback (most recent call last):
File "./media-dispatcher", line 63, in <module>
from mediaproxy.dispatcher import Dispatcher
File "/usr/local/lib/python2.7/site-packages/mediaproxy/dispatcher.py",
line 36, in <module>
from mediaproxy.tls import X509Credentials, X509NameValidator
File "/usr/local/lib/python2.7/site-packages/mediaproxy/tls.py", line 12,
in <module>
from gnutls import crypto
File "/usr/local/lib/python2.7/site-packages/gnutls/crypto.py", line 11,
in <module>
from gnutls.validators import method_args, one_of
File "/usr/local/lib/python2.7/site-packages/gnutls/validators.py", line
9, in <module>
from gnutls.constants import *
File "/usr/local/lib/python2.7/site-packages/gnutls/constants.py", line
38, in <module>
from gnutls.library import constants
File "/usr/local/lib/python2.7/site-packages/gnutls/library/__init__.py",
line 129, in <module>
from gnutls.library import errors
File "/usr/local/lib/python2.7/site-packages/gnutls/library/errors.py",
line 15, in <module>
from gnutls.library.functions import gnutls_strerror, gnutls_alert_get
File "/usr/local/lib/python2.7/site-packages/gnutls/library/functions.py",
line 124, in <module>
gnutls_certificate_get_x509_cas =
libgnutls.gnutls_certificate_get_x509_cas
File "/usr/local/lib/python2.7/ctypes/__init__.py", line 378, in
__getattr__
func = self.__getitem__(name)
File "/usr/local/lib/python2.7/ctypes/__init__.py", line 383, in
__getitem__
func = self._FuncPtr((name_or_ordinal, self))
AttributeError: /usr/lib/libgnutls.so.26: undefined symbol:
gnutls_certificate_get_x509_cas
Thanks,
Prem Chandiran M
Hi folks,
i have a problem with call_control module. I get a following log from
kamailio
kamailio[15066]: WARNING: call_control [call_control.c:1159]:
postprocess_request(): dialog to trace controlled call was not created.
discarding callcontrol.
and following log from call_control python application
Call id <call-id> of 1000(a)domain.com to sip:0033000000@domain.com canceled
by user
As far as I can see the call_control module runs a postprocess_request()
function which checks whether the dialog was created by checking
FL_USE_CALL_CONTROL variable.
This variable is set at the time of the registration of call_controll to
the dialog module DLGCB_CREATED.
Therefore if I call the call_control() function in kamailio after the
dlg_manage, the FL_USE_CALL_CONTROL cannot be set and the call_control
won't work.
In my configuration I would like to call the dlg_manage at the beginning of
the script for example because of uac_replace_from as I have AUTO_RESTORE
mode ON.
I have kamailio 4.0.2 and call_control 2.0.15.
Is there anything I can fix in a script or configuration or this is an
implementation problem?
Thanks for the reply
Efelin
