29 Sep
2004
29 Sep
'04
1:02 p.m.
Brilliant ... worked first time .... been spending ages on that :)
Call is quite breaky at first then within a few seconds it gets better. Is this usual?
Also I get these errors in the messages file when making the call:
Sep 29 10:56:50 testsip2 /sbin/ser[4043]: record_route(): Double attempt to record-route
Sep 29 10:56:52 testsip2 /sbin/ser[4048]: ERROR: extract_body: message body has lenght
zero
Sep 29 10:56:52 testsip2 /sbin/ser[4048]: ERROR: force_rtp_proxy2: can't extract body
from the message
Sep 29 10:56:52 testsip2 /sbin/ser[4048]: ERROR: on_reply processing failed
Sep 29 10:56:52 testsip2 /sbin/ser[4049]: ERROR: extract_body: message body has lenght
zero
Sep 29 10:56:52 testsip2 /sbin/ser[4049]: ERROR: force_rtp_proxy2: can't extract body
from the message
Sep 29 10:56:52 testsip2 /sbin/ser[4049]: ERROR: on_reply processing failed
What would this point to I wonder?
My ser.cfg is already in this thread if that helps.
Many Thanks.
Dave
On Tuesday 28 September 2004 21:02, Andrei Pelinescu-Onciul wrote:
On Sep 28, 2004 at 16:11, David Simmons
<iptel(a)davidsimmons.co.uk> wrote:
Hi,
Having tremendous trouble with SER + RTPProxy.
Running Fedora Core 1.
Have made RTPProxy using: make -f Makefile.gnu
Then run it fine by using: ./rtpproxy
[...]
Sep 28 16:03:46 testsip2 /sbin/ser[2582]: ERROR:
send_rtpp_command: can't
read reply from a RTP proxy
You're probably not running the latest rtpproxy version.
You can get the latest version only from cvs:
cvs -d:pserver:anonymous@cvs.ser.berlios.de:/cvsroot/ser co rtpproxy
Andrei