[Serusers] send_rtpp_command error in nat configuration

[Ashling O'Driscoll]

Hello,

This is partially linked to my post this morning regarding having no
audio between clients on different nats. I have spent the whole day
trying different configurations and at this stage I think the reason
its not working is coming down to the rtp errors (ERROR:
send_rtpp_command etc). My problem as such is exactly the same
detailed in the below thread (see below) which I found in the
archives. However whilst suggestions were made regarding this
problems (check that the versions are up to date and that you have
sufficient permissions to rtp.sock etc)...no actual definitive
solution was given. I have tried all the recommendations and none
work. My deadline is looming so if someone (anybody) who has
experience this problem and solved it, or just someone who has ideas,
could give me pointers, I would be VERY appreciative.

Kindest Regards,
Aisling.


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:

textops - initializing
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
 5(2195)  4(2194)  2(2192)  1(2191) ERROR:
send_rtpp_command: can't read reply from a RTP proxy
ERROR: send_rtpp_command: can't read reply from a RTP
proxy 13(2203) 14(2204) 15(2205) 16(2206) 17(2207) 
ERROR: send_rtpp_command: can't read reply from a RTP
proxy 3(2193) 
ERROR: send_rtpp_command: can't read reply from a RTP
proxy 5(2195)  4(2194)
ERROR: send_rtpp_command: can't connect to RTP proxy
<rest of errors removed; more of the same>

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?

Regards,
Allan 


-------------------Legal  Disclaimer---------------------------------------

The above electronic mail transmission is confidential and intended only for the person to whom it is addressed. Its contents may be protected by legal and/or professional privilege. Should it be received by you in error please contact the sender at the above quoted email address. Any unauthorised form of reproduction of this message is strictly prohibited. The Institute does not guarantee the security of any information electronically transmitted and is not liable if the information contained in this communication is not a proper and complete record of the message as transmitted by the sender nor for any delay in its receipt.