[Serusers] send_rtpp_command error in nat configuration

[Emilio Panighetti]

I have the same issue. I got the latest stable version of RTPProxy from 
Portaone, and SER 0.8.14

I originally had SER running as user nobody, but now I commented out 
that on ser.cfg and it seems to be doing the same.

Any ideas?

On Oct 4, 2004, at 12:11 PM, Allan wrote:

> Thanks for the reply,
>
> The permission for rtpproxy.sock is:
> srwxr-xr-x   1 root  wheel        0 Oct  4 11:07
> rtpproxy.sock
>
> I added the patch and now see the following output:
>
> sip# ser
> Listening on
>               10.5.5.83 [10.5.5.83]:5060
>               127.0.0.1 [127.0.0.1]:5060
> Aliases: localhost:5060 localhost.infosat.com:5060
> sip:5060
> textops - initializing
> sip# stateless - initializing
> Maxfwd module- initializing
>  0(0) INFO: udp_init: SO_RCVBUF is initially 42080
>  0(0) INFO: udp_init: SO_RCVBUF is finally 231808
>  0(0) INFO: udp_init: SO_RCVBUF is initially 42080
>  0(0) INFO: udp_init: SO_RCVBUF is finally 231808
> 10(162) 11(163) 12(164) 13(165) 14(166) 15(167)
> 16(168) 17(169)  2(154) ERROR: send_rtpp_command:
> can't connect to RTP proxy: Connection refused [61]
>
> <snip>
>
> I also see further down:
>
> INFO: fifo process starting: 169
>  1(153)  3(155) ERROR: send_rtpp_command: can't read
> reply from a RTP proxy: No buffer space available [55]
>
>
> Regards,
> Alan
>
>
>
>  --- Andrei Pelinescu-Onciul
> <pelinescu-onciul at fokus.fraunhofer.de> wrote:
>> On Sep 30, 2004 at 18:42, Allan
>> <voip_tango at yahoo.ca> wrote:
>>> Hello,
>>>
>>> I am have having difficulty getting rtpproxy and
>> ser
>>> to work together correctly.  Each time I start ser
>>> (after first starting rtpproxy) I get the
>> following
>>> errors:
>>>
>> [...]
>>> send_rtpp_command: can't read reply from a RTP
>> proxy
>>> ERROR: send_rtpp_command: can't read reply from a
>> RTP
>> [...]
>>>
>>> Looking through the list I thought it was an
>> incorrect
>>> rtpproxy version and downloaded and installed the
>>> stable 0.8.14 ser version and latest rtpproxy from
>>> CVS.  But I still see the same errors.  I can see
>> the
>>> rtpproxy process running and rtpproxy.sock is
>> present.
>>>
>>>
>>> Currently I have ser 0.8.14 and rtpproxy 1.21
>>> 2004/08/13  running on freebsd 4.10.  Aside from
>> these
>>> errors the calls set up fine but with no audio.
>>>
>>> I have been searching through the list and google
>> for
>>> a couple of days but still seem to be missing
>>> something.
>>>
>>> Any thoughts on what I should try next?
>>
>> Check your permissions on rtpproxy.sock (if you're
>> not running ser as
>> root).
>>
>> Try also the attached nathelper patch, which should
>> give a little more
>> information on the errors above.
>>
>> Andrei
>>> diff -u -r1.63 nathelper.c
>> --- nathelper.c	9 Sep 2004 10:38:00 -0000	1.63
>> +++ nathelper.c	1 Oct 2004 18:19:10 -0000
>> @@ -1152,7 +1152,8 @@
>>  		}
>>  		if (connect(fd, (struct sockaddr *) &addr,
>> sizeof(addr)) < 0) {
>>  			close(fd);
>> -			LOG(L_ERR, "ERROR: send_rtpp_command: can't
>> connect to RTP proxy\n");
>> +			LOG(L_ERR, "ERROR: send_rtpp_command: can't
>> connect to RTP"
>> +					" proxy: %s [%d]\n", strerror(errno), errno);
>>  			return NULL;
>>  		}
>>
>> @@ -1169,7 +1170,8 @@
>>  		} while (len == -1 && errno == EINTR);
>>  		close(fd);
>>  		if (len <= 0) {
>> -			LOG(L_ERR, "ERROR: send_rtpp_command: can't read
>> reply from a RTP proxy\n");
>> +			LOG(L_ERR, "ERROR: send_rtpp_command: can't read
>> reply from a "
>> +					"RTP proxy: %s [%d]\n", strerror(errno),
>> errno);
>>  			return NULL;
>>  		}
>>  	} else {
>>
>
> ______________________________________________________________________
> Post your free ad now! http://personals.yahoo.ca
>
> _______________________________________________
> Serusers mailing list
> serusers at lists.iptel.org
> http://lists.iptel.org/mailman/listinfo/serusers