28 Mar
2005
28 Mar
'05
4:49 a.m.
Take a look at README.remote in rtpproxy directory. There is one thing need
to watch out, do not use "udp:" as it mentioned in README.remote, example
"rtpproxy -s <interface ip>:<port>". Unfortunately, it can't
do both unix
sock and ip address and port in the same server.
Raymond
-----Original Message-----
From: serusers-bounces(a)iptel.org [mailto:serusers-bounces@lists.iptel.org] On
Behalf Of szj
Sent: Monday, March 28, 2005 9:05 AM
To: Maxim Sobolev; serusers(a)lists.iptel.org
Subject: Re: [Serusers] rtpproxy usage??
Maxim Sobolev wrote:
szj wrote:
Thanks for your immediate reply and instructions. I think
when both ser and rtpproxy run on the same machine, it would
works as you described. But I want them to run on the different
device. I think the SER must know which port the rtpproxy listens.
Or still through the /var/run???
Thansk again.
Best Regards
Sun Zongjun
It's greate that rtpproxy support multiple
stream. Thanks
Maxim for his great work.
Now I want to test the rtpprxy+SER, But after starting the
rtpproxy, I can't find which ports the rtpproxy listens.
I don't understand the arguments of rtpproxy all well.
Is it a must the rtpproxy runs on machine with multiple network
adapters?? How to start it with the appropriate arguments?
Thanks for your kind help and advance.
Unless there is a session in progress the rtpproxy doesn't listen at
any ports. Usually you only don't need to pass any arguments to it.
Please don't forget to run it as root, since it needs to create unix
domain socket in /var/run.
-Maxim
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers