KAMAILIO 4.2 - RTPPROXY config confirmation - error message from systemctl status kamailio.service -l (ERROR: <script>: NATMANAGE coee)
20 Nov
2018
20 Nov
'18
10:41 p.m.
Dear All,
I am still using Kamailio 4.2 with Debian Jessie without any issues.
RTPPROXY - CONFIG
# Defaults for rtpproxy
# The control socket.
#CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock"
# To listen on an UDP socket, uncomment this line:
CONTROL_SOCK=udp:127.0.0.1:7722
# Additional options that are passed to the daemon.
# log in /var/log/kamailio.log
EXTRA_OPTS="-l ip_public/192.168.40.101 -m 11000 -M 12000 -d DBUG:LOG_LOCAL0"
WHEN I MAKE AN INVITE FROM 801 TO 803, I HAVE THIS ERROR MESSAGE :
KAMAILIO SERVICE (ERROR: <SCRIPT>: NATMANAGE COEE)
root@sipsecure:~# systemctl status kamailio.service -l
● kamailio.service - LSB: Start the Kamailio SIP proxy server
Loaded: loaded (/etc/init.d/kamailio)
Active: active (running) since Tue 2018-11-20 22:34:31 CET; 40s ago
Process: 1820 ExecStop=/etc/init.d/kamailio stop (code=exited,
status=0/SUCCESS)
Process: 1830 ExecStart=/etc/init.d/kamailio start (code=exited,
status=0/SUCCESS)
CGroup: /system.slice/kamailio.service
├─1846 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1848 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1849 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1850 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1851 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1852 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1853 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1854 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1855 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1856 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1858 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1860 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1863 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1865 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1867 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1869 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1871 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1873 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
└─1875 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1853]: ERROR: <script>:
NATMANAGE coee
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1854]: ERROR: <script>:
NATMANAGE M=INVITE OU=<null> RURI=<null> RD=<null>
F=sip:801@192.168.40.101;transport=UDP
T=sip:803@192.168.40.101;transport=UDP NH=<null> IP=192.168.0.207
ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1854]: ERROR: <script>:
NATMANAGE coee
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1855]: ERROR: <script>:
NATMANAGE M=INVITE OU=<null> RURI=<null> RD=<null>
F=sip:801@192.168.40.101;transport=UDP
T=sip:803@192.168.40.101;transport=UDP NH=<null> IP=192.168.0.207
ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1855]: ERROR: <script>:
NATMANAGE coee
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1852]: ERROR: <script>:
NATMANAGE M=INVITE OU=<null> RURI=<null> RD=<null>
F=sip:801@192.168.40.101;transport=UDP
T=sip:803@192.168.40.101;transport=UDP NH=<null> IP=192.168.0.207
ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1852]: ERROR: <script>:
NATMANAGE coee
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1852]: NOTICE: acc
[acc.c:317]: acc_log_request(): ACC: transaction answered:
timestamp=1542749703;method=INVITE;from_tag=4d488551;to_tag=2006d156;call_id=fjpUwRGm0u--3RvvB4fZ7Q..;code=200;reason=OK;src_user=801;src_domain=192.168.40.101;src_ip=192.168.0.229;dst_ouser=803;dst_user=803;dst_domain=192.168.0.207;user_agent=Z
5.2.19 rv2.8.99
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1853]: ERROR: <script>:
NATMANAGE M=ACK OU=sip:803@192.168.0.207:5060;alias=192.168.0.207:5060~1
RURI=sip:803@192.168.0.207:5060 RD=192.168.0.207
F=sip:801@192.168.40.101;transport=UDP
T=sip:803@192.168.40.101;transport=UDP NH=192.168.0.207 IP=192.168.0.229
ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1853]: ERROR: <script>:
NATMANAGE coee
Don't understand why the error???
RTPPROXY SERVICE : (RTPPROXY IS DOING HIS JOB PERFECTLY AND GET AUDIO ON
BOTH DIRECTION)
root@sipsecure:~# systemctl status rtpproxy.service -l
● rtpproxy.service - LSB: RTP Proxy
Loaded: loaded (/etc/init.d/rtpproxy)
Active: active (running) since Tue 2018-11-20 22:13:58 CET; 22min ago
Process: 443 ExecStart=/etc/init.d/rtpproxy start (code=exited,
status=0/SUCCESS)
CGroup: /system.slice/rtpproxy.service
└─1137 /usr/bin/rtpproxy -s udp:127.0.0.1 7722 -u rtpproxy rtpproxy -p
/var/run/rtpproxy/rtpproxy.pid -l 212.76.231.102 192.168.40.101 -m 11000
-M 12000 -d DBUG LOG_LOCAL0
Nov 20 22:34:31 sipsecure rtpproxy[1137]: DBUG:doreply: sending reply
"1875_11 1
"
Nov 20 22:35:00 sipsecure rtpproxy[1137]: DBUG:handle_command: received
command "1853_8 USEEc106,9,3,111,0,8,97,110,112,98,101,100,99,102
fjpUwRGm0u--3RvvB4fZ7Q.. 192.168.0.229 11000 4d488551;1"
Nov 20 22:35:00 sipsecure rtpproxy[1137]: INFO:handle_command: new
session fjpUwRGm0u--3RvvB4fZ7Q.., tag 4d488551;1 requested, type strong
Nov 20 22:35:00 sipsecure rtpproxy[1137]: INFO:handle_command: new
session on a port 11496 created, tag 4d488551;1
Nov 20 22:35:00 sipsecure rtpproxy[1137]: INFO:handle_command:
pre-filling caller's address with 192.168.0.229:11000
Nov 20 22:35:00 sipsecure rtpproxy[1137]: DBUG:doreply: sending reply
"1853_8 11496 192.168.40.101
"
Nov 20 22:35:03 sipsecure rtpproxy[1137]: DBUG:handle_command: received
command "1852_8 LSEEc106,9,3,111,0,8,97,110,112,102,98,101,100,99
fjpUwRGm0u--3RvvB4fZ7Q.. 192.168.0.207 11112 4d488551;1 2006d156;1"
Nov 20 22:35:03 sipsecure rtpproxy[1137]: INFO:handle_command: lookup on
ports 11496/11402, session timer restarted
Nov 20 22:35:03 sipsecure rtpproxy[1137]: INFO:handle_command:
pre-filling callee's address with 192.168.0.207:11112
Nov 20 22:35:03 sipsecure rtpproxy[1137]: DBUG:doreply: sending reply
"1852_8 11402 192.168.40.101
"
??? Question : for rtpproxy config, do I need to add the natted ip
address (NAT 1:1) or the real public address (where ip phone needs to
assign as domain)? I am confused.
Thanks a lot in advance
Best Regards,
Youssef
21 Nov
21 Nov
10:31 a.m.
On Tue, Nov 20, 2018 at 10:41:51PM +0100, yboujraf(a)by-research.be wrote:
WHEN I MAKE AN INVITE FROM 801 TO 803, I HAVE THIS ERROR MESSAGE :
KAMAILIO SERVICE (ERROR: <SCRIPT>: NATMANAGE COEE)
check you config and search for COEE. it this a xlog?
if so see the way you can call xlog and what facility is used by
default:
https://www.kamailio.org/docs/modules/5.1.x/modules/xlog.html#xlog.f.xlog
6:24 p.m.
New subject: KAMAILIO 4.2 - RTPPROXY config confirmation - error message from systemctl status kamailio.service -l (ERROR: <script>: NATMANAGE coee)
Dear,
I checked in the /etc/kamailio/kamailio.cfg the COEE.
This is the default code not updated by us :
# RTPProxy control
route[NATMANAGE] {
#!ifdef WITH_NAT
if (is_request()) {
if(has_totag()) {
if(check_route_param("nat=yes")) {
setbflag(FLB_NATB);
}
}
}
if (!(isflagset(FLT_NATS) || isbflagset(FLB_NATB)))
return;
xlog("NATMANAGE M=$rm OU=$ou RURI=$ru RD=$rd F=$fu T=$tu NH=$nh(d)
IP=$si ID=$ci\n");
if(dst_ip == _ip_public_address_) {
if(is_ipv4($nh(d)) && is_in_subnet($nh(d), PRIVATE_NET)) {
xlog("NATMANAGE coei\n");
rtpproxy_manage("cowei");
} else {
xlog("NATMANAGE coee\n");
rtpproxy_manage("cowee");
}
} else {
if(is_ipv4($nh(d)) && is_in_subnet($nh(d), PRIVATE_NET)) {
xlog("NATMANAGE coii\n");
rtpproxy_manage("cowii");
} else {
xlog("NATMANAGE coie\n");
rtpproxy_manage("cowie");
}
}
if (is_request()) {
if (!has_totag()) {
if(t_is_branch_route()) {
add_rr_param(";nat=yes");
}
}
}
if (is_reply()) {
if(isbflagset(FLB_NATB)) {
if(is_first_hop())
set_contact_alias();
}
}
#!endif
return;
}
Is it an issue with the public ip address configured in the rtpproxy
(/etc/default/rtpproxy)?
# Defaults for rtpproxy
# The control socket.
#CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock"
# To listen on an UDP socket, uncomment this line:
CONTROL_SOCK=udp:127.0.0.1:7722
# Additional options that are passed to the daemon.
# log in /var/log/kamailio.log
EXTRA_OPTS="-l _ip_public_address_/192.168.40.101 -m 11000 -M 12000 -d
DBUG:LOG_LOCAL0"
Thanks in advance
Best Regards,
Youssef
-----Original Message-----
From: Daniel Tryba <d.tryba(a)pocos.nl>
Sent: Wednesday, 21 November 2018 10:31
To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org>
Subject: Re: [SR-Users] KAMAILIO 4.2 - RTPPROXY config confirmation - error
message from systemctl status kamailio.service -l (ERROR: <script>:
NATMANAGE coee)
On Tue, Nov 20, 2018 at 10:41:51PM +0100, yboujraf(a)by-research.be wrote:
WHEN I MAKE AN INVITE FROM 801 TO 803, I HAVE THIS ERROR MESSAGE :
KAMAILIO SERVICE (ERROR: <SCRIPT>: NATMANAGE COEE)
check you config and search for COEE. it this a xlog?
if so see the way you can call xlog and what facility is used by
default:
https://www.kamailio.org/docs/modules/5.1.x/modules/xlog.html#xlog.f.xlog
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
22 Nov
22 Nov
11:59 a.m.
On Wed, Nov 21, 2018 at 06:24:22PM +0100, yboujraf(a)by-research.be wrote:
...
xlog("NATMANAGE coei\n");
...
Is it an issue with the public ip address configured
in the rtpproxy
(/etc/default/rtpproxy)?
There is no issue. Please take a look at
https://www.kamailio.org/docs/modules/5.1.x/modules/xlog.html#xlog.f.xlog
xlog logs strings to some log file, the default level/severity is error.
Combine that with a retarted launcher like systemd and you might get the
impression there is something wrong where there isn't.
27 Nov
27 Nov
10:26 p.m.
New subject: KAMAILIO 4.2 - RTPPROXY config confirmation - error message from systemctl status kamailio.service -l (ERROR: <script>: NATMANAGE coee)
Dear,
Any help to figure out my issue?
Best Regards,
Youssef
From: yboujraf(a)by-research.be <yboujraf(a)by-research.be>
Sent: Tuesday, 20 November 2018 22:42
To: sr-users(a)lists.kamailio.org
Subject: [SR-Users] KAMAILIO 4.2 - RTPPROXY config confirmation - error message from
systemctl status kamailio.service -l (ERROR: <script>: NATMANAGE coee)
Dear All,
I am still using Kamailio 4.2 with Debian Jessie without any issues.
RTPPROXY - config
# Defaults for rtpproxy
# The control socket.
#CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock"
# To listen on an UDP socket, uncomment this line:
CONTROL_SOCK=udp:127.0.0.1:7722
# Additional options that are passed to the daemon.
# log in /var/log/kamailio.log
EXTRA_OPTS="-l ip_public/192.168.40.101 -m 11000 -M 12000 -d DBUG:LOG_LOCAL0"
When I MAKE an INVITE from 801 to 803, I have this error message :
kamailio service (ERROR: <script>: NATMANAGE coee)
root@sipsecure:~# systemctl status kamailio.service -l
● kamailio.service - LSB: Start the Kamailio SIP proxy server
Loaded: loaded (/etc/init.d/kamailio)
Active: active (running) since Tue 2018-11-20 22:34:31 CET; 40s ago
Process: 1820 ExecStop=/etc/init.d/kamailio stop (code=exited, status=0/SUCCESS)
Process: 1830 ExecStart=/etc/init.d/kamailio start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/kamailio.service
├─1846 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1848 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1849 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1850 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1851 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1852 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1853 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1854 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1855 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1856 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1858 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1860 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1863 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1865 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1867 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1869 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1871 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1873 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
└─1875 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1853]: ERROR: <script>: NATMANAGE coee
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1854]: ERROR: <script>: NATMANAGE
M=INVITE OU=<null> RURI=<null> RD=<null>
F=sip:801@192.168.40.101;transport=UDP T=sip:803@192.168.40.101;transport=UDP
NH=<null> IP=192.168.0.207 ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1854]: ERROR: <script>: NATMANAGE coee
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1855]: ERROR: <script>: NATMANAGE
M=INVITE OU=<null> RURI=<null> RD=<null>
F=sip:801@192.168.40.101;transport=UDP T=sip:803@192.168.40.101;transport=UDP
NH=<null> IP=192.168.0.207 ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1855]: ERROR: <script>: NATMANAGE coee
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1852]: ERROR: <script>: NATMANAGE
M=INVITE OU=<null> RURI=<null> RD=<null>
F=sip:801@192.168.40.101;transport=UDP T=sip:803@192.168.40.101;transport=UDP
NH=<null> IP=192.168.0.207 ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1852]: ERROR: <script>: NATMANAGE coee
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1852]: NOTICE: acc [acc.c:317]:
acc_log_request(): ACC: transaction answered:
timestamp=1542749703;method=INVITE;from_tag=4d488551;to_tag=2006d156;call_id=fjpUwRGm0u--3RvvB4fZ7Q..;code=200;reason=OK;src_user=801;src_domain=192.168.40.101;src_ip=192.168.0.229;dst_ouser=803;dst_user=803;dst_domain=192.168.0.207;user_agent=Z
5.2.19 rv2.8.99
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1853]: ERROR: <script>: NATMANAGE M=ACK
OU=sip:803@192.168.0.207:5060;alias=192.168.0.207:5060~1 RURI=sip:803@192.168.0.207:5060
RD=192.168.0.207 F=sip:801@192.168.40.101;transport=UDP
T=sip:803@192.168.40.101;transport=UDP NH=192.168.0.207 IP=192.168.0.229
ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1853]: ERROR: <script>: NATMANAGE coee
Don't understand why the error???
rtpproxy service : (rtpproxy is doing his job perfectly and get audio on both direction)
root@sipsecure:~# systemctl status rtpproxy.service -l
● rtpproxy.service - LSB: RTP Proxy
Loaded: loaded (/etc/init.d/rtpproxy)
Active: active (running) since Tue 2018-11-20 22:13:58 CET; 22min ago
Process: 443 ExecStart=/etc/init.d/rtpproxy start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/rtpproxy.service
└─1137 /usr/bin/rtpproxy -s udp:127.0.0.1 7722 -u rtpproxy rtpproxy -p
/var/run/rtpproxy/rtpproxy.pid -l 212.76.231.102 192.168.40.101 -m 11000 -M 12000 -d DBUG
LOG_LOCAL0
Nov 20 22:34:31 sipsecure rtpproxy[1137]: DBUG:doreply: sending reply "1875_11 1
"
Nov 20 22:35:00 sipsecure rtpproxy[1137]: DBUG:handle_command: received command
"1853_8 USEEc106,9,3,111,0,8,97,110,112,98,101,100,99,102 fjpUwRGm0u--3RvvB4fZ7Q..
192.168.0.229 11000 4d488551;1"
Nov 20 22:35:00 sipsecure rtpproxy[1137]: INFO:handle_command: new session
fjpUwRGm0u--3RvvB4fZ7Q.., tag 4d488551;1 requested, type strong
Nov 20 22:35:00 sipsecure rtpproxy[1137]: INFO:handle_command: new session on a port 11496
created, tag 4d488551;1
Nov 20 22:35:00 sipsecure rtpproxy[1137]: INFO:handle_command: pre-filling caller's
address with 192.168.0.229:11000
Nov 20 22:35:00 sipsecure rtpproxy[1137]: DBUG:doreply: sending reply "1853_8 11496
192.168.40.101
"
Nov 20 22:35:03 sipsecure rtpproxy[1137]: DBUG:handle_command: received command
"1852_8 LSEEc106,9,3,111,0,8,97,110,112,102,98,101,100,99 fjpUwRGm0u--3RvvB4fZ7Q..
192.168.0.207 11112 4d488551;1 2006d156;1"
Nov 20 22:35:03 sipsecure rtpproxy[1137]: INFO:handle_command: lookup on ports
11496/11402, session timer restarted
Nov 20 22:35:03 sipsecure rtpproxy[1137]: INFO:handle_command: pre-filling callee's
address with 192.168.0.207:11112
Nov 20 22:35:03 sipsecure rtpproxy[1137]: DBUG:doreply: sending reply "1852_8 11402
192.168.40.101
"
??? Question : for rtpproxy config, do I need to add the natted ip address (NAT 1:1) or
the real public address (where ip phone needs to assign as domain)? I am confused.
Thanks a lot in advance
Best Regards,
Youssef
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
28 Nov
28 Nov
1:25 p.m.
Hello,
you already got some replies, those ERROR messages are because you have
some xlog() statements (or other functions from xlog modules) in your
configuration file. They are not errors from inside the code of Kamailio.
Those error messages are printed because the person that wrote the
kamailio.cfg decided to print some log messages to ERROR level.
So, either you ignore them or remove the use of xlog() functions from
kamailio.cfg.
Cheers,
Daniel
On 27.11.18 22:26, yboujraf(a)by-research.be wrote:
Dear,
Any help to figure out my issue?
Best Regards,
Youssef
*From:*yboujraf@by-research.be <yboujraf(a)by-research.be>
*Sent:* Tuesday, 20 November 2018 22:42
*To:* sr-users(a)lists.kamailio.org
*Subject:* [SR-Users] KAMAILIO 4.2 - RTPPROXY config confirmation -
error message from systemctl status kamailio.service -l (ERROR:
<script>: NATMANAGE coee)
Dear All,
I am still using Kamailio 4.2 with Debian Jessie without any issues.
*_RTPPROXY - config_*
# Defaults for rtpproxy
# The control socket.
#CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock"
# To listen on an UDP socket, uncomment this line:
CONTROL_SOCK=udp:127.0.0.1:7722
# Additional options that are passed to the daemon.
# log in /var/log/kamailio.log
EXTRA_OPTS="-l ip_public/192.168.40.101 -m 11000 -M 12000 -d
DBUG:LOG_LOCAL0"
*_When I MAKE an INVITE from 801 to 803, I have this error message :_*
*_kamailio service (ERROR: <script>: NATMANAGE coee)_*
root@sipsecure:~# systemctl status kamailio.service -l
● kamailio.service - LSB: Start the Kamailio SIP proxy server
Loaded: loaded (/etc/init.d/kamailio)
Active: active (running) since Tue 2018-11-20 22:34:31 CET; 40s ago
Process: 1820 ExecStop=/etc/init.d/kamailio stop (code=exited,
status=0/SUCCESS)
Process: 1830 ExecStart=/etc/init.d/kamailio start (code=exited,
status=0/SUCCESS)
CGroup: /system.slice/kamailio.service
├─1846 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1848 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1849 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1850 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1851 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1852 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1853 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1854 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1855 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1856 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1858 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1860 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1863 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1865 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1867 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1869 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1871 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
├─1873 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
└─1875 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P
/var/run/kamailio/kamailio.pid -m 64 -M 8 -u kamailio -g kamailio
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1853]: ERROR: <script>:
NATMANAGE coee
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1854]: ERROR: <script>:
NATMANAGE M=INVITE OU=<null> RURI=<null> RD=<null>
F=sip:801@192.168.40.101;transport=UDP
T=sip:803@192.168.40.101;transport=UDP NH=<null> IP=192.168.0.207
ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1854]: ERROR: <script>:
NATMANAGE coee
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1855]: ERROR: <script>:
NATMANAGE M=INVITE OU=<null> RURI=<null> RD=<null>
F=sip:801@192.168.40.101;transport=UDP
T=sip:803@192.168.40.101;transport=UDP NH=<null> IP=192.168.0.207
ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1855]: ERROR: <script>:
NATMANAGE coee
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1852]: ERROR: <script>:
NATMANAGE M=INVITE OU=<null> RURI=<null> RD=<null>
F=sip:801@192.168.40.101;transport=UDP
T=sip:803@192.168.40.101;transport=UDP NH=<null> IP=192.168.0.207
ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1852]: ERROR: <script>:
NATMANAGE coee
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1852]: NOTICE: acc
[acc.c:317]: acc_log_request(): ACC: transaction answered:
timestamp=1542749703;method=INVITE;from_tag=4d488551;to_tag=2006d156;call_id=fjpUwRGm0u--3RvvB4fZ7Q..;code=200;reason=OK;src_user=801;src_domain=192.168.40.101;src_ip=192.168.0.229;dst_ouser=803;dst_user=803;dst_domain=192.168.0.207;user_agent=Z
5.2.19 rv2.8.99
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1853]: ERROR: <script>:
NATMANAGE M=ACK
OU=sip:803@192.168.0.207:5060;alias=192.168.0.207:5060~1
RURI=sip:803@192.168.0.207:5060 RD=192.168.0.207
F=sip:801@192.168.40.101;transport=UDP
T=sip:803@192.168.40.101;transport=UDP NH=192.168.0.207
IP=192.168.0.229 ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1853]: ERROR: <script>:
NATMANAGE coee
Don't understand why the error???
*_rtpproxy service : (rtpproxy is doing his job perfectly and get
audio on both direction)_*
root@sipsecure:~# systemctl status rtpproxy.service -l
● rtpproxy.service - LSB: RTP Proxy
Loaded: loaded (/etc/init.d/rtpproxy)
Active: active (running) since Tue 2018-11-20 22:13:58 CET; 22min ago
Process: 443 ExecStart=/etc/init.d/rtpproxy start (code=exited,
status=0/SUCCESS)
CGroup: /system.slice/rtpproxy.service
└─1137 /usr/bin/rtpproxy -s udp:127.0.0.1 7722 -u rtpproxy rtpproxy -p
/var/run/rtpproxy/rtpproxy.pid -l 212.76.231.102 192.168.40.101 -m
11000 -M 12000 -d DBUG LOG_LOCAL0
Nov 20 22:34:31 sipsecure rtpproxy[1137]: DBUG:doreply: sending reply
"1875_11 1
"
Nov 20 22:35:00 sipsecure rtpproxy[1137]: DBUG:handle_command:
received command "1853_8
USEEc106,9,3,111,0,8,97,110,112,98,101,100,99,102
fjpUwRGm0u--3RvvB4fZ7Q.. 192.168.0.229 11000 4d488551;1"
Nov 20 22:35:00 sipsecure rtpproxy[1137]: INFO:handle_command: new
session fjpUwRGm0u--3RvvB4fZ7Q.., tag 4d488551;1 requested, type strong
Nov 20 22:35:00 sipsecure rtpproxy[1137]: INFO:handle_command: new
session on a port 11496 created, tag 4d488551;1
Nov 20 22:35:00 sipsecure rtpproxy[1137]: INFO:handle_command:
pre-filling caller's address with 192.168.0.229:11000
Nov 20 22:35:00 sipsecure rtpproxy[1137]: DBUG:doreply: sending reply
"1853_8 11496 192.168.40.101
"
Nov 20 22:35:03 sipsecure rtpproxy[1137]: DBUG:handle_command:
received command "1852_8
LSEEc106,9,3,111,0,8,97,110,112,102,98,101,100,99
fjpUwRGm0u--3RvvB4fZ7Q.. 192.168.0.207 11112 4d488551;1 2006d156;1"
Nov 20 22:35:03 sipsecure rtpproxy[1137]: INFO:handle_command: lookup
on ports 11496/11402, session timer restarted
Nov 20 22:35:03 sipsecure rtpproxy[1137]: INFO:handle_command:
pre-filling callee's address with 192.168.0.207:11112
Nov 20 22:35:03 sipsecure rtpproxy[1137]: DBUG:doreply: sending reply
"1852_8 11402 192.168.40.101
"
??? Question : for rtpproxy config, do I need to add the natted ip
address (NAT 1:1) or the real public address (where ip phone needs to
assign as domain)? I am confused.
Thanks a lot in advance
Best Regards,
Youssef
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Virus-free. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference -- www.kamailioworld.com
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
3:27 p.m.
New subject: KAMAILIO 4.2 - RTPPROXY config confirmation - error message from systemctl status kamailio.service -l (ERROR: <script>: NATMANAGE coee)
Dear Daniel,
Thank you for your answer, the only files we have modified is :
* Rtpproxy /etc/default/rtpproxy
RTPPROXY - config
# Defaults for rtpproxy
# The control socket.
#CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock"
# To listen on an UDP socket, uncomment this line:
CONTROL_SOCK=udp:127.0.0.1:7722
# Additional options that are passed to the daemon.
# log in /var/log/kamailio.log
EXTRA_OPTS="-l ip_public/ip_to_be_natted -m 11000 -M 12000 -d DBUG:LOG_LOCAL0"
??? Question :
To be confirmed : ip_public : is the ip address used by softphone to reach kamailio
Ip_to_be_natted : is the private ip address of kamailio in the DMZ network.
Thanks again,
Best Regards,
Youssef
From: Daniel-Constantin Mierla <miconda(a)gmail.com>
Sent: Wednesday, 28 November 2018 13:25
To: yboujraf(a)by-research.be; Kamailio (SER) - Users Mailing List
<sr-users(a)lists.kamailio.org>
Subject: Re: [SR-Users] KAMAILIO 4.2 - RTPPROXY config confirmation - error message from
systemctl status kamailio.service -l (ERROR: <script>: NATMANAGE coee)
Hello,
you already got some replies, those ERROR messages are because you have some xlog()
statements (or other functions from xlog modules) in your configuration file. They are not
errors from inside the code of Kamailio.
Those error messages are printed because the person that wrote the kamailio.cfg decided to
print some log messages to ERROR level.
So, either you ignore them or remove the use of xlog() functions from kamailio.cfg.
Cheers,
Daniel
On 27.11.18 22:26, yboujraf(a)by-research.be <mailto:yboujraf@by-research.be> wrote:
Dear,
Any help to figure out my issue?
Best Regards,
Youssef
From: yboujraf(a)by-research.be <mailto:yboujraf@by-research.be>
<mailto:yboujraf@by-research.be> <yboujraf(a)by-research.be>
Sent: Tuesday, 20 November 2018 22:42
To: sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org>
Subject: [SR-Users] KAMAILIO 4.2 - RTPPROXY config confirmation - error message from
systemctl status kamailio.service -l (ERROR: <script>: NATMANAGE coee)
Dear All,
I am still using Kamailio 4.2 with Debian Jessie without any issues.
RTPPROXY - config
# Defaults for rtpproxy
# The control socket.
#CONTROL_SOCK="unix:/var/run/rtpproxy/rtpproxy.sock"
# To listen on an UDP socket, uncomment this line:
CONTROL_SOCK=udp:127.0.0.1:7722
# Additional options that are passed to the daemon.
# log in /var/log/kamailio.log
EXTRA_OPTS="-l ip_public/192.168.40.101 -m 11000 -M 12000 -d DBUG:LOG_LOCAL0"
When I MAKE an INVITE from 801 to 803, I have this error message :
kamailio service (ERROR: <script>: NATMANAGE coee)
root@sipsecure:~# systemctl status kamailio.service -l
● kamailio.service - LSB: Start the Kamailio SIP proxy server
Loaded: loaded (/etc/init.d/kamailio)
Active: active (running) since Tue 2018-11-20 22:34:31 CET; 40s ago
Process: 1820 ExecStop=/etc/init.d/kamailio stop (code=exited, status=0/SUCCESS)
Process: 1830 ExecStart=/etc/init.d/kamailio start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/kamailio.service
├─1846 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1848 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1849 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1850 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1851 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1852 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1853 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1854 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1855 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1856 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1858 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1860 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1863 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1865 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1867 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1869 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1871 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
├─1873 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
└─1875 /usr/sbin/kamailio -f /etc/kamailio/kamailio.cfg -P /var/run/kamailio/kamailio.pid
-m 64 -M 8 -u kamailio -g kamailio
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1853]: ERROR: <script>: NATMANAGE coee
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1854]: ERROR: <script>: NATMANAGE
M=INVITE OU=<null> RURI=<null> RD=<null>
F=sip:801@192.168.40.101;transport=UDP T=sip:803@192.168.40.101;transport=UDP
NH=<null> IP=192.168.0.207 ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1854]: ERROR: <script>: NATMANAGE coee
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1855]: ERROR: <script>: NATMANAGE
M=INVITE OU=<null> RURI=<null> RD=<null>
F=sip:801@192.168.40.101;transport=UDP T=sip:803@192.168.40.101;transport=UDP
NH=<null> IP=192.168.0.207 ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:00 sipsecure /usr/sbin/kamailio[1855]: ERROR: <script>: NATMANAGE coee
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1852]: ERROR: <script>: NATMANAGE
M=INVITE OU=<null> RURI=<null> RD=<null>
F=sip:801@192.168.40.101;transport=UDP T=sip:803@192.168.40.101;transport=UDP
NH=<null> IP=192.168.0.207 ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1852]: ERROR: <script>: NATMANAGE coee
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1852]: NOTICE: acc [acc.c:317]:
acc_log_request(): ACC: transaction answered:
timestamp=1542749703;method=INVITE;from_tag=4d488551;to_tag=2006d156;call_id=fjpUwRGm0u--3RvvB4fZ7Q..;code=200;reason=OK;src_user=801;src_domain=192.168.40.101;src_ip=192.168.0.229;dst_ouser=803;dst_user=803;dst_domain=192.168.0.207;user_agent=Z
5.2.19 rv2.8.99
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1853]: ERROR: <script>: NATMANAGE M=ACK
OU=sip:803@192.168.0.207:5060;alias=192.168.0.207:5060~1 RURI=sip:803@192.168.0.207:5060
RD=192.168.0.207 F=sip:801@192.168.40.101;transport=UDP
T=sip:803@192.168.40.101;transport=UDP NH=192.168.0.207 IP=192.168.0.229
ID=fjpUwRGm0u--3RvvB4fZ7Q..
Nov 20 22:35:03 sipsecure /usr/sbin/kamailio[1853]: ERROR: <script>: NATMANAGE coee
Don't understand why the error???
rtpproxy service : (rtpproxy is doing his job perfectly and get audio on both direction)
root@sipsecure:~# systemctl status rtpproxy.service -l
● rtpproxy.service - LSB: RTP Proxy
Loaded: loaded (/etc/init.d/rtpproxy)
Active: active (running) since Tue 2018-11-20 22:13:58 CET; 22min ago
Process: 443 ExecStart=/etc/init.d/rtpproxy start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/rtpproxy.service
└─1137 /usr/bin/rtpproxy -s udp:127.0.0.1 7722 -u rtpproxy rtpproxy -p
/var/run/rtpproxy/rtpproxy.pid -l 212.76.231.102 192.168.40.101 -m 11000 -M 12000 -d DBUG
LOG_LOCAL0
Nov 20 22:34:31 sipsecure rtpproxy[1137]: DBUG:doreply: sending reply "1875_11 1
"
Nov 20 22:35:00 sipsecure rtpproxy[1137]: DBUG:handle_command: received command
"1853_8 USEEc106,9,3,111,0,8,97,110,112,98,101,100,99,102 fjpUwRGm0u--3RvvB4fZ7Q..
192.168.0.229 11000 4d488551;1"
Nov 20 22:35:00 sipsecure rtpproxy[1137]: INFO:handle_command: new session
fjpUwRGm0u--3RvvB4fZ7Q.., tag 4d488551;1 requested, type strong
Nov 20 22:35:00 sipsecure rtpproxy[1137]: INFO:handle_command: new session on a port 11496
created, tag 4d488551;1
Nov 20 22:35:00 sipsecure rtpproxy[1137]: INFO:handle_command: pre-filling caller's
address with 192.168.0.229:11000
Nov 20 22:35:00 sipsecure rtpproxy[1137]: DBUG:doreply: sending reply "1853_8 11496
192.168.40.101
"
Nov 20 22:35:03 sipsecure rtpproxy[1137]: DBUG:handle_command: received command
"1852_8 LSEEc106,9,3,111,0,8,97,110,112,102,98,101,100,99 fjpUwRGm0u--3RvvB4fZ7Q..
192.168.0.207 11112 4d488551;1 2006d156;1"
Nov 20 22:35:03 sipsecure rtpproxy[1137]: INFO:handle_command: lookup on ports
11496/11402, session timer restarted
Nov 20 22:35:03 sipsecure rtpproxy[1137]: INFO:handle_command: pre-filling callee's
address with 192.168.0.207:11112
Nov 20 22:35:03 sipsecure rtpproxy[1137]: DBUG:doreply: sending reply "1852_8 11402
192.168.40.101
"
??? Question : for rtpproxy config, do I need to add the natted ip address (NAT 1:1) or
the real public address (where ip phone needs to assign as domain)? I am confused.
Thanks a lot in advance
Best Regards,
Youssef
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Virus-free.
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
www.avast.com
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com <http://www.asipto.com>
www.twitter.com/miconda <http://www.twitter.com/miconda> --
www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda>
Kamailio World Conference -- www.kamailioworld.com <http://www.kamailioworld.com>
Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com
<http://www.asipto.com>
---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
1988
days inactive
1996
days old
6 comments
3 participants
participants (3)
-
Daniel Tryba -
Daniel-Constantin Mierla -
yboujraf＠by-research.be