Your RTPproxy is not running I guess. Ladislav Alberto Cruz wrote: _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Hello, Your RTPproxy might be running, but not where your SER expects it. Check out SER configuration and see if your RTPproxy can be reached on the port it listens, from SER machine. "can't connect to RTP proxy" is fairly explicit. Moreover, check that RTPproxy listens on the right interface... WL. Alberto Cruz wrote:

gI'm running the RTPproxy from the stable debian distro so It is running with the default values using unix socket. It is working since we are placing calls at ser without problem but I'm watching this messages errors at the syslog file. And BTW the message error that I'm concerned about mainly are: "WARNING: rtpp_test: can't get version of the RTPproxy" and "WARNING: rtpp_test: support for RTP proxy has been disabled temporarily" Regards Alberto Cruz Weiter Leiter wrote: >Hello, > >Your RTPproxy might be running, but not where your SER expects it. Check >out SER configuration and see if your RTPproxy can be reached on the >port it listens, from SER machine. "can't connect to RTP proxy" is >fairly explicit. Moreover, check that RTPproxy listens on the right >interface... > >WL. > >Alberto Cruz wrote: > > >>No, the message appears when RTPROXY is running. >> >>As I have read at nathelper README there are some exported parameters >>to control the time-out and retries from SER to communicate to RTPPROXY. >>I don't know if the "WARNING: rtpp_test: can't get version of the RTP >>proxy" and "WARNING: rtpp_test: support for RTP proxy has been >>disabled temporarily" are related to it. >> >>Could it be? >> >>Regards >> >>Alberto Cruz >> >>Ladislav Andel wrote: >> >> >> >>>Your RTPproxy is not running I guess. >>> >>>Ladislav >>> >>>Alberto Cruz wrote: >>> >>> >>> >>>>Hi everybody! >>>> >>>>Have somebody seen the following error messages at syslog? >>>>Jul 8 12:21:04 localhost /usr/sbin/ser[29329]: ERROR: >>>>unforce_rtp_proxy: support for RTP proxy is disabled >>>>Jul 8 12:21:04 localhost /usr/sbin/ser[29336]: ERROR: >>>>force_rtp_proxy2: support for RTP proxy is disabled >>>>Jul 8 12:21:04 localhost /usr/sbin/ser[29335]: Successethod - STOP >>>>ACCOUNTING >>>>Jul 8 12:21:04 localhost /usr/sbin/ser[29335]: ERROR: >>>>send_rtpp_command: can't connect to RTP proxy >>>>Jul 8 12:21:04 localhost /usr/sbin/ser[29335]: WARNING: rtpp_test: >>>>can't get version of the RTP proxy >>>>Jul 8 12:21:04 localhost /usr/sbin/ser[29335]: WARNING: rtpp_test: >>>>support for RTP proxy has been disabled temporarily >>>>Jul 8 12:21:04 localhost /usr/sbin/ser[29335]: ERROR: >>>>unforce_rtp_proxy: support for RTP proxy is disabled >>>>Jul 8 12:21:05 localhost /usr/sbin/ser[29341]: ERROR: >>>>force_rtp_proxy2: support for RTP proxy is disabled >>>>Jul 8 12:21:05 localhost /usr/sbin/ser[29329]: ERROR: >>>>force_rtp_proxy2: support for RTP proxy is disabled >>>> >>>>Are this normal? >>>> >>>>Regards >>>> >>>>Alberto Cruz >>>> >>>>_______________________________________________ >>>>Serusers mailing list >>>>Serusers(a)lists.iptel.org >>>>http://lists.iptel.org/mailman/listinfo/serusers >>>> >>>> >>>> >>>> >>>_______________________________________________ >>>Serusers mailing list >>>Serusers(a)lists.iptel.org >>>http://lists.iptel.org/mailman/listinfo/serusers >>> >>> >>> >>_______________________________________________ >>Serusers mailing list >>Serusers(a)lists.iptel.org >>http://lists.iptel.org/mailman/listinfo/serusers >> >> >> > > > >

Hi, maybe active firewall settings are blocking the ports? Michael ------------------------------------------------------------------------ Von: serusers-bounces(a)lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] Im Auftrag von Alberto Cruz Gesendet: Sonntag, 9. Juli 2006 09:53 An: serusers(a)iptel.org Betreff: Re: [Serusers] RTPPROY error messages Wichtigkeit: Hoch 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") So why am I getting this messages at syslog file? Jul 9 02:50:19 sermex02 /usr/sbin/ser[2347]: ERROR: send_rtpp_command: can't connect to RTP proxy Jul 9 02:50:19 sermex02 /usr/sbin/ser[2347]: WARNING: rtpp_test: can't get version of the RTP proxy Jul 9 02:50:19 sermex02 /usr/sbin/ser[2347]: WARNING: rtpp_test: support for RTP proxy has been disabled temporarily Regards Alberto Cruz Alberto Cruz wrote: gI'm running the RTPproxy from the stable debian distro so It is running with the default values using unix socket. It is working since we are placing calls at ser without problem but I'm watching this messages errors at the syslog file. And BTW the message error that I'm concerned about mainly are: "WARNING: rtpp_test: can't get version of the RTPproxy" and "WARNING: rtpp_test: support for RTP proxy has been disabled temporarily" Regards Alberto Cruz Weiter Leiter wrote: Hello, Your RTPproxy might be running, but not where your SER expects it. Check out SER configuration and see if your RTPproxy can be reached on the port it listens, from SER machine. "can't connect to RTP proxy" is fairly explicit. Moreover, check that RTPproxy listens on the right interface... WL. Alberto Cruz wrote: ------------------------------------------------------------------------ _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Alberto Cruz wrote: Try this instead: modparam("nathelper", "rtpproxy_sock", "/var/run/rtpproxy.sock")

Alberto Cruz wrote: 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.

Maybe something's wrong with the socket permissions.... which are the owner/group which SER and rtproxy are running?? Check wether SER user has permissions wnough to access the rtproxy socket. Hope it helps, Samuel. 2006/7/10, Alberto Cruz &lt;acruz(a)tekbrain.com <mailto:acruz@tekbrain.com>>: Hi Jan and Maxim: Maybe you can help me with this. I'm using Debian sarge r3.0 and SER apt packages (0.9.6) I was looking at the CVS Repository if there was something related to this behavior with RTPPROXY and I found the following annotation for ser/rtpproxy/main.c on July 4: Since we are now opening control socket in non-blocking mode, there is race condition between accepting stream connection on unix domain socket and availability of data on the socket. Patch it by doing read() in a loop until we actually get the data. While I am here, allow V command to take extra argument, which we don't process but put into the log file. This allows to pass some extra information from the client (SER in this case) such as PID number for example. Does it have something to do with my problem? BTW I found a bug posted too at the lists.debian.org <http://lists.debian.org>: Bug#356721: ITP: rtpproxy -- RTP proxy for SER <http://url?sa=U&start=3&q=http://lists.debian.org/debian-devel/2006/03/msg00561.html&e=14905&ei=caixRPnxNJbMwQL-jbXTCQ> Am I doing something wrong with my installation/configuration or is it a bug? Regards Alberto Cruz Andres wrote: _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org <mailto:Serusers@lists.iptel.org> http://lists.iptel.org/mailman/listinfo/serusers

I found the problem. As Samuel have said the problem is with socket permissions. When the RTPProxy is already running and I modified the permissions or owner to the rtpproxy.sock file it works but as soon as I restart the deamon the permissions go back again to the original permissions. This is something to do with how the rtproxy is creating the .socket file at the time it starts and it defines the permissions to srwxr-xr-x for the user and group equal to root. So as I have been running SER with user and group as ser, SER can't talk to the socket. I need to modify the way like RTPROXY runs in other to start the daemon with another user or with different permissions for the socket file. In the meantime I applied the "umask 000" command at the "/etc/init.d/rtproxy" file and it works but it modifies the .pid file too. Is there a way to tell rtpproxy daemon to run with a different user for example user ser ? Regards Alberto Cruz Alberto Cruz wrote: ------------------------------------------------------------------------ _______________________________________________ Serusers mailing list Serusers(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers

Hi I don't know how to use the setuid command. I were trying to find some documentation or tutorial and BTW I red the manual information for the setuid function. I tried to add the following line at the rtpproxy init script but I only got an error: setuid ser Could anybody give me a hand? Regards Alberto Cruz Greger V. Teigre wrote: > Alberto, > Typically, you will run rtpproxy with the same user (or at least > group) as ser or you can change permission on the socket file after > starting rtpproxy in your init script (chmod to be more targeted). > g-) > > Alberto Cruz wrote: >> I found the problem. As Samuel have said the problem is with socket >> permissions. >> >> When the RTPProxy is already running and I modified the permissions >> or owner to the rtpproxy.sock file it works but as soon as I restart >> the deamon the permissions >> go back again to the original permissions. >> >> This is something to do with how the rtproxy is creating the .socket >> file at the time it starts and it defines the permissions to >> srwxr-xr-x for the user and group equal to root. >> >> So as I have been running SER with user and group as ser, SER can't >> talk to the socket. >> >> I need to modify the way like RTPROXY runs in other to start the >> daemon with another user or with different permissions for the >> socket file. >> >> In the meantime I applied the "umask 000" command at the >> "/etc/init.d/rtproxy" file and it works but it modifies the .pid >> file too. >> >> Is there a way to tell rtpproxy daemon to run with a different user >> for example user ser ? >> >> Regards >> >> Alberto Cruz >> >> Alberto Cruz wrote: >>> RTPROXY is running as it default: >>> root 2332 1 0 Jul09 ? 00:00:00 /usr/sbin/rtpproxy >>> >>> And SER is running as follow: >>> ser 4612 4575 0 Jul09 ? 00:00:00 /usr/sbin/ser -P >>> /var/run/ser/ser.pid -u ser -g ser >>> >>> And the socket File is like this: >>> -rw-r--r-- 1 root root 5 2006-07-09 02:45 >>> rtpproxy.pid >>> srwxr-xr-x 1 root root 0 2006-07-09 02:45 >>> rtpproxy.sock >>> >>> I already tried changing the owner and group for the rtpproxy.sock >>> but it didn't work >>> >>> Regards >>> >>> Acruz >>> samuel wrote: >>>> Maybe something's wrong with the socket permissions.... which are >>>> the owner/group which SER and rtproxy are running?? >>>> >>>> Check wether SER user has permissions wnough to access the rtproxy >>>> socket. >>>> >>>> Hope it helps, >>>> Samuel. >>>> >>>> >>>> 2006/7/10, Alberto Cruz &lt;acruz(a)tekbrain.com >>>> <mailto:acruz@tekbrain.com>>: >>>> >>>> Hi Jan and Maxim: >>>> Maybe you can help me with this. >>>> I'm using Debian sarge r3.0 and SER apt packages (0.9.6) >>>> >>>> I was looking at the CVS Repository if there was something >>>> related to this behavior with RTPPROXY and I found the >>>> following annotation for ser/rtpproxy/main.c on July 4: >>>> >>>> Since we are now opening control socket in non-blocking mode, there is race condition between accepting stream connection on unix domain socket and availability of data on the socket. Patch it by doing read() in a loop until we actually get the data. While I am here, allow V command to take extra argument, which we don't process but put into the log file. This allows to pass some extra information from the client (SER in this case) such as PID number for example. >>>> >>>> >>>> Does it have something to do with my problem? BTW I found a >>>> bug posted too at the lists.debian.org <http://lists.debian.org>: >>>> Bug#356721: ITP: *rtpproxy* -- RTP proxy for SER >>>> <http://url?sa=U&start=3&q=http://lists.debian.org/debian-devel/2006/03/msg00561.html&e=14905&ei=caixRPnxNJbMwQL-jbXTCQ> >>>> >>>> Am I doing something wrong with my installation/configuration >>>> or is it a bug? >>>> >>>> >>>> Regards >>>> >>>> Alberto Cruz >>>> >>>> Andres wrote: >>>>> 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: >>>>>> >>>>>>> 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") >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Serusers mailing list >>>> Serusers(a)lists.iptel.org <mailto:Serusers@lists.iptel.org> >>>> http://lists.iptel.org/mailman/listinfo/serusers >>>> >>>> >>>> >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Serusers mailing list >> Serusers(a)lists.iptel.org >> http://lists.iptel.org/mailman/listinfo/serusers >>