Re: AW: [Serusers] RTPPROY error messages

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