search for: cionoiu

...: User (0) < Ext: 1 Cause: No route to destination (3), class = Normal Event (0) ] I have try to make calls in just one way with computer, and i still have alot of noise on the line. This systems are production, so, i can't test alot. Any idee will be apreciated. Diana Cionoiu

Hello I think I finally understood the issue/solution, but I'd like to make sure I'm correct: - In Diana Cionoiu's famous article on Freshmeat (http://freshmeat.net/articles/nat-traversal-for-the-sip-protocol), regardless of whether SIP end-points use a public IP or are behind a NAT, RTP packets flow directly between the two SIP end-points because the SIP server only acts... as an SIP server, meaning it o...

Diana Cionoiu a ?crit : > Hi Jean-Marc, > > 1. Why CELT versus Speex? There's nearly no overlap between Speex and CELT. CELT is much higher quality, very low latency, and of course, higher bit-rate than Speex. So it really depends on the application. > 2. What's the RTP payload for CELT, s...

Use Jingle, anyway Jingle kicks SIP on almost every aspect. Especially on the way the standards are made. Diana David Hogan wrote: >> I understand, but CELT would be useless for SIP if one can't >> > read/guess > >> correctly decoder configuration from the RTP data. >> >> One possible way to cope with this would be to have several CELT >>

Hi all, i want to use authentication in h323.conf. How can i use it ? In the h323.conf is writed : "If you wish to use Authentication you need to set the appropriate auth keyword above" Where and how i have to set this keyword ??? I've tried "auth=yes",but it does not work. Thanks for Help, Thomas.

Hi everyone, I'm happy to announce CELT version 0.5.0. This release includes simplifications to the bit allocation code and includes a new low-complexity mode that can be enabled (without breaking compatibility) on the encoder side. There are several other optimisations and bug fixes included. The API has also been slightly modified, so code using CELT will have to be updated (only minor

Hi everyone, I'm happy to announce CELT version 0.5.0. This release includes simplifications to the bit allocation code and includes a new low-complexity mode that can be enabled (without breaking compatibility) on the encoder side. There are several other optimisations and bug fixes included. The API has also been slightly modified, so code using CELT will have to be updated (only minor

Hi Jean-Marc, 1. Why CELT versus Speex? 2. What's the RTP payload for CELT, so we can add it in Yate? 3. What are the SDP declaration parameters? Diana Jean-Marc Valin wrote: > Hi everyone, > > I'm happy to announce CELT version 0.5.0. This release includes > simplifications to the bit allocation code and includes a new > low-complexity mode that can be enabled (without

On Tue, 14 Oct 2008, Jean-Marc Valin wrote: > Diana Cionoiu a ?crit : >> Hi Jean-Marc, >> >> 1. Why CELT versus Speex? > > There's nearly no overlap between Speex and CELT. CELT is much higher > quality, very low latency, and of course, higher bit-rate than Speex. So > it really depends on the application. > >> 2....

Hi Farhan, What is the purpose of the protocol? Just to be a binary form a SIP? I mean conferencing, PTT, chat we have in h.323, sip, jingle, iax? What is the reason for a new one? The NAT traversal has been fixed for a while for all those protocols also. Diana farhan@phonestack.com wrote: > Dear All, > > I have finished documenting my Lightweight Telephony Protocol. It is > now