On Jul 10, 2004 at 15:03, Karunakar Chemudugunta voicexml@gmail.com wrote:
Andrei, Thanks for your answers and still I am getting same problem.
Do you think, it is version problem ? I am using ser from cvs branch and laterst rtpproxy.
No, if you are using latest rtpproxy from cvs and nathelper from unstable.
Please send me the output of: head -1 sip_router/modules/nathelper/nathelper.c and grep Id: rtpproxy/main.c
It might also be a false alarm, e.g. you start first ser and then rtpproxy => you'll get some rtpproxy not found errors on startup, but once rtpproxy is started + 1 minute it should start to work.
If it still does not work, send me also the output of: netstat -axep |grep rtpproxy
Nope, I have down loaded latest rtpproxy and compiled on linux and running rtpproxy without any parameters on same machine of SER.
Andrei> Try to see after you start rtpproxy, if /var/run/rtpproxy.sock is created and is writtable by the user under which ser runs.
Karun> Both processes are running under root user and it has both read and write problems. /var/run/rtpproxy.sock has both read and write permissions.
ls -al command for rtpproxy.sock
[root@engcasip002 run]# ls -al rtpproxy.sock srwxr-xr-x 1 root root 0 Jul 10 14:46 rtpproxy.sock
Do I need to pass any parameters for rtpproxy ??? Andrei> No, unless you want to use a non-default socket or udp mode.
Karun> What is UDP mode ?
The unstable nathelper & rtpproxy can use UDP instead of unix sockets for communicating between them. This means you can have ser+nathelper on one machine and rtpproxy on another one.
Andrei