Le vendredi 16 février 2007 à 19:29 +0100, Karel Kulhavy a écrit : > On Fri, Feb 16, 2007 at 12:09:17PM +0100, Damien Sandras wrote: > > Le vendredi 16 février 2007 ?? 10:02 +0100, Karel Kulhavy a écrit : > > > On Thu, Feb 15, 2007 at 09:48:08PM -0800, George Boyd wrote: > > > > The problem I believe,is when reviewers test and compare software (in > > > > this case the article you mentioned), is that the reviewers are not > > > > fully aware of the potential or features of the software they are > > > > writing about. Reviewers should know the programs completely before they > > > > try to write comparison articles. > > > > > > Reviewers are writing reviews for ordinary users, and ordinary users > > > typically > > > have only superficial knowledge of software. In today's world, where you > > > are > > > using many pieces of software concurrently, learning each one in depth > > > would > > > require too much time. > > > > > > I think it's OK when a reviewer writes a review from position of someone > > > who doesn't know the software completely. > > > > > > > Probably, but there is a saying : compare what is actually comparable. > > > > Flexibility has a price. > > > > Perhaps Wengo has some features Ekiga doesn't have. But the opposite is > > also true. > > I tried about 5 different phones on OpenBSD incl. Wengo and Ekiga and all > failed (didn't even compile). Then I tried x-ten x-lite on Windows and it > didn't work. Sent internal address in SDP so it couldn't get the RTP data. > Even > when I fiddled with all the NAT settings and even made a port forwarding. Then > I managed to install Ekiga on Windows (website instructions worked) and that > worked :) > > Now I am trying to make our hardware SIP implementation call in to Ekiga. > Maybe blows up on the "Contact:". The RFC says " The Contact header field > provides a SIP or SIPS URI that can be used to contact that specific > instance of the UA for subsequent requests." - that doesn't explicitly say > that > 5060 cannot be used anymore, so I am continuing to send the ACK to 5060 and > Ekiga shows "connected", but doesn't send any RTP and doesn't play anything > (even when the RTP is coming to her and contains sound). Ekiga sends a > 2xx with Contact:<192.168.2.68:5067>. Does the RFC > actually mean "provides a SIP or SIPS URI that must be used to contact that > specific instance of the UA for subsequent requests"? >
I think so. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:[EMAIL PROTECTED] _______________________________________________ ekiga-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/ekiga-list
