[Serusers] RTPPROY error messages

[samuel]

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 <acruz at 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:
> 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 at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20060710/eec8b09b/attachment.htm>