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.
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 ?
Thanks, Karun On Sat, 10 Jul 2004 21:40:24 +0200, Andrei Pelinescu-Onciul pelinescu-onciul@fokus.fraunhofer.de wrote:
On Jul 09, 2004 at 09:47, Karunakar Chemudugunta voicexml@gmail.com wrote:
Nope, I have down loaded latest rtpproxy and compiled on linux and running rtpproxy without any parameters on same machine of SER.
Try to see after you start rtpproxy, if /var/run/rtpproxy.sock is created and is writtable by the user under which ser runs.
How to enable debug on rtpproxy ?
You can't, it doesn't really have a debugging mode.
Do I need to pass any parameters for rtpproxy ???
No, unless you want to use a non-default socket or udp mode.
Do I need to set any info regarding rtp proxy in ser.cfg file ?
Please find my attached ser.cfg which is usedfor this test.
Andrei