[GnomeMeeting-devel-list] I GOT THE PROBLEM! :) :) :)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I got the problem. It seems to be such an trivial "\r\n" error like we
had already before!!!!

The opal OpalTransportIP::Read(buffer, length) call in
OpalTransportUDP::Read(void * buffer, PINDEX length) spit's out the
following text ( that's void * buffer ):

 helloE sip:03419899434 195 158 171 101:5061;user=phone SIP/2.0
From: <sip:anonymous 213 148 136 2;user=phone>;tag=d97c9bd5
To: <sip:03419899434 195 158 171 101;user=phone>
CSeq: 1 INVITE
Call-ID: 4fb4059922d7f33d301a2760d3044543 sx3000
Via: SIP/2.0/UDP 213.148.136.2:5060;branch=z9hG4bK15ee99e1d
Allow:
INVITE,ACK,CANCEL,OPTIONS,BYE,REGISTER,PRACK,INFO,UPDATE,SUBSCRIBE,NOTIFY,MESSAGE,REFER
Max-Forwards: 16
Supported: 100rel
Contact: <sip:anonymous 213 148 136 2:5060;user=phone>
Privacy: user
Content-Length: 316
Content-Type: application/sdp

v=0
o=HuaweiSoftX3000 89350 89350 IN IP4 213.148.135.2
s=Sip Call
c=IN IP4 213.148.136.2
t=0 0
m=audio 58446 RTP/AVP 18 8 0 4 97 96
a=rtpmap:18 G729/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:4 G723/8000
a=rtpmap:97 telephone-event/8000
a=rtpmap:96 red/8000
a=fmtp:97 0-15
a=fmtp:96 97/97

Because of this transport.good() failes.

Our "hello" - Connection keeper message is received together with the
INVITE nessage in one packet. They are seperated with an "\r\n". We need
to seperate both, and handle each one: Ignore the "hello" message and
handle the invite correctly!!

Je l'aime! Moi cher Gnomemeeting! ( cont complain, that's a google
translation ) :D

Greetings,
Jan Schiefer!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCXjLHzC00UKXFdVcRAuioAJ0Ufy9JfhOEtvZY5Uy9fufjnVkOdgCfXxm8
lwLjSprdw8kdyB25xsbsTLs=
=unKP
-----END PGP SIGNATURE-----




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]