I installed Kamailio 4.2 and the latest rtpproxy. When starting Kamailio I see these lines:
Oct 27 21:54:26 ip-10-0-2-68 kamailio: DEBUG: <core> [sr_module.c:590]: load_module(): load_module: trying to load </usr/local
Oct 27 21:54:26 ip-10-0-2-68 kamailio: DEBUG: <core> [sr_module.c:357]: register_module(): register PV from: rtpproxy
Oct 27 21:54:26 ip-10-0-2-68 kamailio: DEBUG: <core> [cfg.lex:1724]: pp_define(): defining id: MOD_rtpproxy
Oct 27 21:54:32 ip-10-0-2-68 ./…
[View More]kamailio[3887]: ERROR: rtpproxy [rtpproxy.c:1707]: send_rtpp_command(): timeout waiting reply f
Oct 27 21:54:32 ip-10-0-2-68 ./kamailio[3887]: ERROR: rtpproxy [rtpproxy.c:1716]: send_rtpp_command(): proxy <udp:10.0.2.68:77
Oct 27 21:54:32 ip-10-0-2-68 ./kamailio[3887]: WARNING: rtpproxy [rtpproxy.c:1573]: rtpp_test(): can't get version of the RTP
Oct 27 21:54:32 ip-10-0-2-68 ./kamailio[3887]: WARNING: rtpproxy [rtpproxy.c:1610]: rtpp_test(): support for RTP proxy <udp:10
Oct 27 21:54:37 ip-10-0-2-68 ./kamailio[3898]: ERROR: rtpproxy [rtpproxy.c:1707]: send_rtpp_command(): timeout waiting reply f
Oct 27 21:54:37 ip-10-0-2-68 ./kamailio[3898]: ERROR: rtpproxy [rtpproxy.c:1716]: send_rtpp_command(): proxy <udp:10.0.2.68:77
Oct 27 21:54:37 ip-10-0-2-68 ./kamailio[3898]: WARNING: rtpproxy [rtpproxy.c:1573]: rtpp_test(): can't get version of the RTP
I run rtpproxy like this:
/usr/local/rtpproxy-install-dir/bin/rtpproxy -l <public ip here> -s udp:10.0.2.68:7722 -F -d DBUG:LOG_LOCAL3
I have these linee in the kamailio.cfg file
loadmodule "rtpproxy.so"
# ----- rtpproxy params -----
modparam("rtpproxy", "rtpproxy_sock", "udp:10.0.2.68:7722")
I have tried with localhost, with 127.0.0.1 and get the same results ( I mean configure kamailio to contact rttpproxy with localhost instead of ip and at the same time running rtpproxy with the same reference.
I can see the rtpproxy running/listening
[root@ip-10-0-2-68 sbin]# netstat -lnp | grep rtpproxy
udp 0 0 10.0.2.68:7722 0.0.0.0:* 3608/rtpproxy
I can also see these lines:
[root@ip-10-0-2-68 sbin]# netstat -np | grep 7722
udp 0 0 10.0.2.68:49772 10.0.2.68:7722 ESTABLISHED 3928/./kamailio
udp 0 0 10.0.2.68:36097 10.0.2.68:7722 ESTABLISHED 3897/./kamailio
udp 0 0 10.0.2.68:49158 10.0.2.68:7722 ESTABLISHED 3906/./kamailio
udp 0 0 10.0.2.68:37129 10.0.2.68:7722 ESTABLISHED 3904/./kamailio
udp 0 0 10.0.2.68:39052 10.0.2.68:7722 ESTABLISHED 3926/./kamailio
udp 0 0 10.0.2.68:38161 10.0.2.68:7722 ESTABLISHED 3919/./kamailio
udp 0 0 10.0.2.68:53144 10.0.2.68:7722 ESTABLISHED 3887/./kamailio
udp 0 0 10.0.2.68:39721 10.0.2.68:7722 ESTABLISHED 3905/./kamailio
udp 0 0 10.0.2.68:59563 10.0.2.68:7722 ESTABLISHED 3909/./kamailio
udp 0 0 10.0.2.68:51884 10.0.2.68:7722 ESTABLISHED 3921/./kamailio
udp 0 0 10.0.2.68:46902 10.0.2.68:7722 ESTABLISHED 3930/./kamailio
udp 0 0 10.0.2.68:33981 10.0.2.68:7722 ESTABLISHED 3931/./kamailio
udp 0 0 10.0.2.68:60221 10.0.2.68:7722 ESTABLISHED 3898/./kamailio
udp 0 0 10.0.2.68:35651 10.0.2.68:7722 ESTABLISHED 3900/./kamailio
udp 0 0 10.0.2.68:33105 10.0.2.68:7722 ESTABLISHED 3927/./kamailio
udp 0 0 10.0.2.68:43349 10.0.2.68:7722 ESTABLISHED 3887/./kamailio
udp 0 0 10.0.2.68:39259 10.0.2.68:7722 ESTABLISHED 3899/./kamailio
udp 0 0 10.0.2.68:35170 10.0.2.68:7722 ESTABLISHED 3907/./kamailio
udp 0 0 10.0.2.68:38760 10.0.2.68:7722 ESTABLISHED 3908/./kamailio
In the rtpproxy I see that it is sent data and it replies too, I even got a wireshark capture showing that as well:
Oct 27 21:54:41 ip-10-0-2-68 rtpproxy[3608]: DBUG:get_command: received command "3931_2 V"
Oct 27 21:54:41 ip-10-0-2-68 rtpproxy[3608]: DBUG:rtpc_doreply: sending reply "20040107#012"
Oct 27 21:54:41 ip-10-0-2-68 rtpproxy[3608]: DBUG:get_command: received command "3927_2 V"
Oct 27 21:54:41 ip-10-0-2-68 rtpproxy[3608]: DBUG:rtpc_doreply: sending reply "20040107#012"
Oct 27 21:54:41 ip-10-0-2-68 rtpproxy[3608]: DBUG:get_command: received command "3926_2 V"
Oct 27 21:54:41 ip-10-0-2-68 rtpproxy[3608]: DBUG:rtpc_doreply: sending reply "20040107#012"
Oct 27 21:54:41 ip-10-0-2-68 rtpproxy[3608]: DBUG:get_command: received command "3928_2 V"
Oct 27 21:54:41 ip-10-0-2-68 rtpproxy[3608]: DBUG:rtpc_doreply: sending reply "20040107#012"
But somehow kamailio does not see it:
[root@ip-10-0-2-68 sbin]# ./kamctl fifo nh_show_rtpp
which: no greadlink in (/sbin:/bin:/usr/sbin:/usr/bin:/)
which: no gdb in (/sbin:/bin:/usr/sbin:/usr/bin:/)
udp:10.0.2.68:7722:: set=0
index:: 0
disabled:: 1
weight:: 1
recheck_ticks:: 53253287
I even when to the kamailio code and saw something that may have something to do with it but havent tried it yet:, in the implementation of the function "send_rtpp_command" I see that the socket created is using TCP. But I tried configuring kamailio/rtpproxy to use tcp instead but I also got the same results, kamailio seems to fail to acknoledgwe the replies from rtpproxy.
I also have SELINUX disabled and the iptables are not running.
I dont know what else to check, if somebody can shed some light into this I'd appreciate it.
jp2014
[View Less]
Hello. I use kamailio with last rtpengine and
I have 5-7 Seconds voice delay. This happened only for from webphone. But
it is not client issue as i see. Wireshark at client side shows that RTP
starts as soon I pick up call. So rtp leaves rtpengine and goes to the
destination with delay... I use WSS and think that problem at handshake.
There are some statisticcs after call finished (as example). You may see
that one of streams created after 5 seconds delay.
Oct 26 22:15:31 Kamailio2 …
[View More]rtpengine[35466]: [
28ed5c035d4b8a1c5383360e4d3677af@10.0.1.6:5060] --- Tag 'rsik48leli',
created 1:12 ago, in dialogue with 'as7b4cb593'
Oct 26 22:15:31 Kamailio2 rtpengine[35466]: [
28ed5c035d4b8a1c5383360e4d3677af@10.0.1.6:5060] ------ Media #1, port 34178
<> 8.2.10.25:52463, 340 p, 58032 b, 0 e
Oct 26 22:15:31 Kamailio2 rtpengine[35466]: [
28ed5c035d4b8a1c5383360e4d3677af@10.0.1.6:5060] ------ Media #1, port 34179
<> 8.2.10.25:52468 (RTCP), 10 p, 960 b, 0 e
Oct 26 22:15:31 Kamailio2 rtpengine[35466]: [
28ed5c035d4b8a1c5383360e4d3677af@10.0.1.6:5060] --- Tag 'as7b4cb593',
created 1:12 ago, in dialogue with 'rsik48leli'
Oct 26 22:15:31 Kamailio2 rtpengine[35466]: [
28ed5c035d4b8a1c5383360e4d3677af@10.0.1.6:5060] ------ Media #1, port 34194
<> 10.0.1.6:16376, 201 p, 36582 b, 0 e
Oct 26 22:15:31 Kamailio2 rtpengine[35466]: [
28ed5c035d4b8a1c5383360e4d3677af@10.0.1.6:5060] ------ Media #1, port 34195
<> 10.0.1.6:16377 (RTCP), 1 p, 78 b, 0 e
Oct 26 22:15:31 Kamailio2 rtpengine[35466]: [iunge05ber6sqlc7qs6b] Final
packet stats:
Oct 26 22:15:31 Kamailio2 rtpengine[35466]: [iunge05ber6sqlc7qs6b] --- Tag
'as3af30098', created 1:17 ago, in dialogue with 'bqinihbhsf'
Oct 26 22:15:31 Kamailio2 rtpengine[35466]: [iunge05ber6sqlc7qs6b] ------
Media #1, port 34142 <> 10.0.1.6:17258, 200 p, 35200 b, 0 e
Oct 26 22:15:31 Kamailio2 rtpengine[35466]: [iunge05ber6sqlc7qs6b] ------
Media #1, port 34143 <> 10.0.1.6:17259 (RTCP), 1 p, 78 b, 0 e
Oct 26 22:15:31 Kamailio2 rtpengine[35466]: [iunge05ber6sqlc7qs6b] --- Tag
'bqinihbhsf', created 1:12 ago, in dialogue with 'as3af30098'
Oct 26 22:15:31 Kamailio2 rtpengine[35466]: [iunge05ber6sqlc7qs6b] ------
Media #1, port 34162 <> 8.2.10.25:52453, 216 p, 36768 b, 0 e
Oct 26 22:15:31 Kamailio2 rtpengine[35466]: [iunge05ber6sqlc7qs6b] ------
Media #1, port 34163 <> 8.2.10.25:52453 (RTCP),
[View Less]
Hi There,
since 4.2 we had the problem that kamailio did not start after a reboot.
A "/etc/init.d/kamailio restart" fixxed it. The problem is quite obvious:
kamailio-loglile => Kamailio can't connect to mysqlDB 13:33:44
Oct 29 13:33:44 kamailio-test /usr/sbin/kamailio[1063]: DEBUG: db_mysql
[km_my_con.c:94]: db_mysql_new_connection(): opening connection:
mysql://xxxx:xxxx@localhost/routing
Oct 29 13:33:44 kamailio-test /usr/sbin/kamailio[1063]: ERROR: db_mysql
[km_my_con.c:109]: …
[View More]db_mysql_new_connection(): driver error: Can't
connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock' (2)
Oct 29 13:33:44 kamailio-test /usr/sbin/kamailio[1063]: ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool
mysql-logfile => ready for connections 13:33:45
141029 13:33:45 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.40-0ubuntu0.12.04.1' socket:
'/var/run/mysqld/mysqld.sock' port: 3306 (Ubuntu)
So simply mysql is not ready for connnections when kamailio is ready.
I "fixxed" this with a "sleep 5;" in the initfile. But this is not what
I call a clean solution.
Anyone else had the same problem and fixxed it a little cleaner? Maybe
converted the init- to a upstart-script?
regards,
moritz
--
Moritz Graf, M.Sc.
Betrieb NGN-Plattform
[View Less]
Hello,
I'm working with rtpproxy module for managing calls to a particular route.
The thing is that for some calls, the "Connection information" is not
rewritten properly whereas another calls, less than 1 second before or
after, are properly rewritten.
When "cr_route" defines that the call must be route to this carrier, I go to
a route in order to make some change:
- Keep only PCMA, PCMU, G729a and telephone-event
- Depends on the R-URI:
o If the uri contains …
[View More]IP addresses or domain name of the carrier:
rtpproxy_manage("iefrcoz20","<CARRIER_IP_ADDRESS");
o else : rtpproxy_manage("eifrcoz20");
Kamailio listens on <CARRIER_IP_ADDRESS> and also on an internal one.
A dedicated instance of RTPProxy runs with the following option: "-l
<INTERNAL_IP_ADDRESS>/<CARRIER_IP_ADDRESS>".
The idea is to tell to my customers to send their RTP to the internal IP
address, and to tell to the carrier to send the RTP to the IP address that
they have attributed to me.
For hundred and hundred calls, this mechanism is working fine. But
sometimes, no, the SDP remains as the original one.
I don't know how to diagnose this. Could it be a saturation of RTPProxy?
Regards,
Igor.
[View Less]
hi all,
kamailio 4.2.x has been released, And I used two endpoint to test kamailio server. I install kamailio 4.2.x on centos 6.5 via 'yum'.
One endpoint failed to call another, I captured packets via wireshark, and found that invite method is recognized as error sip signal because of content-length' mismatch.
I examined the invite packets, and calculated content-length in invite signal. There is no mistake for the value of content-length. I guess it may be a bug in kamailio 4.2.x. But …
[View More]I don't know what causes kamailio to report the mismatch response. who can give me help?
I have uploaded the captured packets as an attachment. Below are two snapshots from the captured packets.
B.R.
andrew
[View Less]
hi,
I install kamailio 4.2.x on centos 6.5 via 'yum'. One endpoint called another, where one dialog is created, and caller and callee can talk with each other. But when the caller hangup the phone(i.e. send bye to the callee), the callee can't receive the bye message, and the dialog can't be terminated normally.
I have captured the packets via wireshark, and uploaded kamailio.cfg and the captured files as attachment.
In the captured file, PRACK and BYE message can be sent to kamailio …
[View More]server successfully, but kamailio server doesn't forward the two messages to the callee.
Why PRACK and BYE message can't be sent to the callee?
Looking forward to your help!
B.R.
Andrew
[View Less]
Hi All
I have followed link http://nil.uniza.sk/book/export/html/617 to install
P-CSCF/I-CSCF/S-CSCF.
Though I have some doubts in configuration , still I have put the
configuration to best of my knowledge.
When I execute SCSCF, I get below errors.
I see some database related errors.
As per the followed link, I find some DB configurations and I did
accordingly.
I do not see any DB configurations for SCSCF, still I see two below lines
# Connection URL for the database:
#!define DB_URL "…
[View More]con1=>mysql://scscf:secret@localhost/scscf"
#!define DB_URL2 "con2=>mysql://scscf:secret@localhost/scscf"
in file scscf.cfg
Is this really required, or can I comment these two lines.
*root@Kamal-E5430:/etc/kamailio/scscf#
root@Kamal-E5430:/etc/kamailio/scscf# root@Kamal-E5430:/etc/kamailio/scscf#
./scscf -f kamailio.cfg -Eloading modules under config path:
/usr/local/lib64/kamailio/modules/Listening on udp:
192.168.1.114 [192.168.1.114]:4080 tcp: 192.168.1.114
[192.168.1.114]:4080Aliases: *:
scscf.group4-imslab11.in:* 0(25982) INFO: <core> [tcp_main.c:4745]:
init_tcp(): using epoll_lt as the io watch method (auto detected) 0(25984)
INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import
bind_ob 0(25984) INFO: rr [rr_mod.c:160]: mod_init(): outbound module not
available 0(25984) ERROR: db_mysql [km_my_con.c:109]:
db_mysql_new_connection(): driver error: Access denied for user
'scscf'@'localhost' (using password: YES) 0(25984) ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool 0(25984)
WARNING: db_cluster [dbcl_data.c:456]: dbcl_init_connections(): cannot
connect to database - connection [con2] 0(25984) ERROR: db_mysql
[km_my_con.c:109]: db_mysql_new_connection(): driver error: Access denied
for user 'scscf'@'localhost' (using password: YES) 0(25984) ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool 0(25984)
WARNING: db_cluster [dbcl_data.c:473]: dbcl_init_connections(): cannot
connect to database - connection [con2] 0(25984) ERROR: db_mysql
[km_my_con.c:109]: db_mysql_new_connection(): driver error: Access denied
for user 'scscf'@'localhost' (using password: YES) 0(25984) ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool 0(25984)
WARNING: db_cluster [dbcl_data.c:456]: dbcl_init_connections(): cannot
connect to database - connection [con1] 0(25984) ERROR: db_mysql
[km_my_con.c:109]: db_mysql_new_connection(): driver error: Access denied
for user 'scscf'@'localhost' (using password: YES) 0(25984) ERROR: <core>
[db.c:322]: db_do_init2(): could not add connection to the pool 0(25984)
WARNING: db_cluster [dbcl_data.c:473]: dbcl_init_connections(): cannot
connect to database - connection [con1] 0(25984) ERROR: <core> [db.c:401]:
db_table_version(): error in db_query 0(25984) ERROR: <core> [db.c:440]:
db_check_table_version(): querying version for table presentity 0(25984)
ERROR: presence [presence.c:322]: mod_init(): error during table version
check 0(25984) ERROR: <core> [sr_module.c:968]: init_mod(): Error while
initializing module presence
(/usr/local/lib64/kamailio/modules/presence.so)ERROR: error while
initializing modules 0(25984) INFO: cdp [mod.c:257]: cdp_exit():
CDiameterPeer child stopping ... 0(25982) ERROR: <core> [daemonize.c:315]:
daemonize(): Main process exited before writing to
piperoot@Kamal-E5430:/etc/kamailio/scscf#
root@Kamal-E5430:/etc/kamailio/scscf# *
Best Regards
Kamal
[View Less]
Hi All
I am in process of setting up of P-CSCF using Kamailio 4.2.0.
I wanted to disable WITH_ANTIFLOOD (as I am not sure what shall be the
content of dispatcher.list file for me, as it is juts a local setup).
When I disable WITH_ANTIFLOOD, and try to execute I get below errors.
Wherever *ds_is_from_list* is referred in Kamailio.cfg, I am getting error
in those places.
Can somebody pls suggest a work around when we disable macro WITH_ANTIFLOOD
*root@Kamal-E5430:/etc/…
[View More]kamailio/pcscf# kamailio -f kamailio.cfg -Eloading
modules under config path: /usr/local/lib64/kamailio/modules/ 0(25255)
ERROR: <core> [cfg.y:3299]: yyparse(): cfg. parser: failed to find command
ds_is_from_list (params 0) 0(25255) : <core> [cfg.y:3439]: yyerror_at():
parse error in config file /etc/kamailio/pcscf/kamailio.cfg, line 486,
column 23: unknown command, missing loadmodule? 0(25255) ERROR: <core>
[cfg.y:3299]: yyparse(): cfg. parser: failed to find command
ds_is_from_list (params 0) 0(25255) : <core> [cfg.y:3439]: yyerror_at():
parse error in config file /etc/kamailio/pcscf/kamailio.cfg, line 658,
column 45: unknown command, missing loadmodule? 0(25255) ERROR: <core>
[cfg.y:3299]: yyparse(): cfg. parser: failed to find command
ds_is_from_list (params 0) 0(25255) : <core> [cfg.y:3439]: yyerror_at():
parse error in config file /etc/kamailio/pcscf/kamailio.cfg, line 672,
column 23: unknown command, missing loadmodule? 0(25255) ERROR: <core>
[cfg.y:3299]: yyparse(): cfg. parser: failed to find command
ds_is_from_list (params 0) 0(25255) : <core> [cfg.y:3439]: yyerror_at():
parse error in config file /etc/kamailio/pcscf/kamailio.cfg, line 706,
column 37: unknown command, missing loadmodule? 0(25255) ERROR: <core>
[cfg.y:3299]: yyparse(): cfg. parser: failed to find command ds_select_dst
(params 2) 0(25255) : <core> [cfg.y:3439]: yyerror_at(): parse error in
config file /etc/kamailio/pcscf/kamailio.cfg, line 846, column 29: unknown
command, missing loadmodule? 0(25255) ERROR: <core> [cfg.y:3299]:
yyparse(): cfg. parser: failed to find command ds_select_dst (params
2) 0(25255) : <core> [cfg.y:3439]: yyerror_at(): parse error in config file
/etc/kamailio/pcscf/kamailio.cfg, line 993, column 29: unknown command,
missing loadmodule?ERROR: bad config file (6 errors)*
Thanks
Kamal
[View Less]
I was giving the htable iterator a go , but I can't get it to work.
My relevant config would is:
modparam("htable", "htable", "testhtable=>size=4;")
in the request route I have this:
sht_iterator_start("i1", "testhtable");
while(sht_iterator_next("i1")) {
xlog("L_INFO"," $shtitkey(i1) is: $shtitval(i1)\n");
}
sht_iterator_end("i1");
I added some values to my testhtable:
$ kamcmd htable.dump testhtable
{
entry: 0
size: 2
slot: {
…
[View More] item: {
name: x[0]
value: 1
}
item: {
name: x[1]
value: 1
}
}
}
But when I have something route over that part I get:
Oct 27 15:33:36 kamailio[18828]: INFO: <script>: <null> is: <null>
Oct 27 15:33:36 kamailio[18828]: INFO: <script>: <null> is: <null>
So it is correct to find 2 items in the htable, but for both the key and
value are not found.
Tried it on both 4.2 and master.
Thx!
[View Less]