10 Jul
2006
10 Jul
'06
10:25 a.m.
Alberto Cruz wrote:
I tried but I'm still receiving the same
messages:
Jul 9 17:51:58 sermex02 /usr/sbin/ser[3902]: DEBUG: init_mod_child
(-4): nathelper
Jul 9 17:51:58 sermex02 /usr/sbin/ser[3902]: ERROR:
send_rtpp_command: can't connect to RTP proxy
Jul 9 17:51:58 sermex02 /usr/sbin/ser[3902]: WARNING: rtpp_test:
can't get version of the RTP proxy
Jul 9 17:51:58 sermex02 /usr/sbin/ser[3902]: WARNING: rtpp_test:
support for RTP proxy has been disabled temporarily
Does anybody else have seen this behavior?
Yes, that happens when the nathelper module is unable to contact the
rtppoxy either because it is not running or it is an old version and is
incompatible with your nathelper.
Regards
Alberto Cruz
Andres wrote:
--
Andres
Technical Support
http://www.telesip.net
Alberto Cruz wrote:
I have checked and the RTPProxy is running and
listening:
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node Path
unix 2 [ ACC ] STREAM LISTENING 3121
/tmp/.gdm_socket
unix 2 [ ACC ] STREAM LISTENING 1765
/var/run/dirmngr/socket
unix 2 [ ACC ] STREAM LISTENING 20376
/var/run/rtpproxy.sock
unix 2 [ ACC ] STREAM LISTENING 2029
/var/run/mysqld/mysqld.sock
And the rtpproxy socket configuration at ser.cfg is ok too:
# -- nathelper params --
modparam("nathelper", "natping_interval", 30)
modparam("nathelper", "ping_nated_only", 1)
modparam("nathelper", "rtpproxy_sock",
"unix:/var/run/rtpproxy.sock")
Try this instead:
modparam("nathelper", "rtpproxy_sock",
"/var/run/rtpproxy.sock")