search for: schulzrinn

[thread moved from -dev due to non-dev content] At 6:40 PM +0200 on 8/13/05, Andreas Sikkema wrote: >On Sat, 2005-08-13 at 12:44 +0800, Steve Underwood wrote: > >> He doesn't seem to really understand the strengths and weaknesses of >> IAX. IAX has drawbacks, but none of the problems he lists actually exist. > >OK, I'll bite ;-) > >How would IAX2 solve

[moved from -dev list due to non-dev topic content] At 12:44 PM +0800 on 8/13/05, Steve Underwood wrote: >Mike Taht wrote: > >>but hey, maybe the folk on this list understand where he's coming >>from and can explain why sip is better.... > >He is one of originators of RTP and the main guy behind SIP. Of >course he thinks they are wonderful. The reality is they

All, We are using a SIP provider that is expecting 0-15 response for fmtp. Our CVS Head asterisk server is sending 0-16, I looked up an rfc and it stated: RTP Payloads for Telephone Signal Events RFC 2833 Henning Schulzrinne, Scott Petrack. May 2000 Implementation notes: * Implementations can support events 0 through 15 (DTMF) by simply ignoring the packets, but MUST declare all event numbers that are meaningful to it in the fmtp parameter, including 0 through 15 Any ideas? Thanks!

Hello, Is there someody who can explain me the meaning of these sentence. "Sip is philosophically horizontal and H.323/MGCP are vertical" Thank U (if you have some links to share about this protocols, share it :) ) Ignace

We asked Henning Schulzrinne (the author of RTP and currently the RTP/AVG maintainer) about getting a static RTP payload type code assigned for Speex, since we meet the criteria in rfc1890. He said no. Here is his answer: On Fri, 22 Nov 2002, Henning Schulzrinne wrote: > Sorry, this is not going to happen, regardless o...

..."Becase" -> "Because" 8 References: Your reference to RFC2119 of 1 Introduction got lost. [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", RFC 2119, BCP 14, March 1997. [1] in 6 Security Considerations will then be [2]: [2] Schulzrinne, H., Casner, S., Frederick, R., and V. Jacobson, "RTP: A transport protocol for real-time applications," RFC 1889, January 1996. Add this one: [3] Handley, M. "Guidelines for Writers of RTP Payload Format Specifications" RFC 2736, December 1999. Che...

...Thanks to Kevin P. Flemming and the guys on Asterisk Dev for creating a thread on this. Dan York for getting some to pay attention. PSIRT at Cisco for looking into this, Tim Donahue for his perl pointers, vgersh99 (aka vlad) for nawk foo pointers, PHV, Annihilannic, p5wizard (segment!), and Henning Schulzrinne for taking a look at the tool during his seminars at Columbia. Also thanks to Anthony LaMantia, Tzafir Cohen, and the others on the dev list for tolerating my posts. Public apologies to Jay R. Ashworth for my mis-reading of the "(Missed)Trust in Caller ID" thread on VOIPSA ;) Coming 10...

...ication may be used to discard packets from undesired sources, but the processing cost of the authentication itself may be too high. <p>8. Normative References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. 3. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies",...

...reamComm for his assistance in developing > the proposed standard for Speex use in H.323 applications. > > The authors would also like to thank the following members of the > Speex and AVT communities for their input: Ross Finlayson, Federico > Montesino Pouzols, Henning Schulzrinne, Magnus Westerlund. > > Thanks to former authors of this document; Simon Morlat, Roger > Hardiman, Phil Kerr. > > > > > > > > > > > > > > > > > > > > > > > > > > > > >...

...@streamcomm.com> of StreamComm for his assistance in developing the proposed standard for Speex use in H.323 applications. The authors would also like to thank the following members of the Speex and AVT communities for their input: Ross Finlayson, Federico Montesino Pouzols, Henning Schulzrinne, Magnus Westerlund. Thanks to former authors of this document; Simon Morlat, Roger Hardiman, Phil Kerr. Herlein, et al. Expires November 30, 2007 [Page 17] Internet-Draft Speex May 2007 9....

Do not forget to add the "Copying conditions" to the RFC. Check http://wiki.debian.org/NonFreeIETFDocuments That page contains a section titled "Template for RFC authors to release additional rights". To follow that guideline a section like the following should be added: x. Copying conditions The author(s) agree to grant third parties the irrevocable right to

...ication may be used to discard packets from undesired sources, but the processing cost of the authentication itself may be too high. <p>8. Normative References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. 3. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies",...

...kets from undesired sources, but the processing cost of > the authentication itself may be too high. > > > 8. Normative References > > 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP > 9, RFC 2026, October 1996. > > 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: > A Transport Protocol for real-time applications", RFC 1889, > January 1996. > > 3. Freed, N. and N. Borenstein, "Multipurpose Internet Mail > Extensions (MIME) Part One: Format of Intern...

...@streamcomm.com> of StreamComm for his assistance in developing the proposed standard for Speex use in H.323 applications. The authors would also like to thank the following members of the Speex and AVT communities for their input: Ross Finlayson, Federico Montesino Pouzols, Henning Schulzrinne, Magnus Westerlund. Thanks to former authors of this document; Simon Morlat, Roger Hardiman, Phil Kerr. Herlein, et al. Expires December 7, 2007 [Page 17] Internet-Draft Speex June 2007 9....

...@streamcomm.com> of StreamComm for his assistance in developing the proposed standard for Speex use in H.323 applications. The authors would also like to thank the following members of the Speex and AVT communities for their input: Ross Finlayson, Federico Montesino Pouzols, Henning Schulzrinne, Magnus Westerlund. Thanks to former authors of this document; Simon Morlat, Roger Hardiman, Phil Kerr Herlein, et al. Expires October 24, 2007 [Page 15] Internet-Draft Speex April 2007 8....

...ceiver to select which sources are allowed to reach it. 7. References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. ITU-T Recommendation G.722.1, available online from the ITU bookstore at http://www.itu.int. 3. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. (Updated by a Work in Progress.) 4. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of I...

...o select which sources are allowed to reach it. <p>7. References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. ITU-T Recommendation G.722.1, available online from the ITU bookstore at http://www.itu.int. 3. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. (Updated by a Work in Progress.) 4. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of I...

...Network-layer authentication may be used to discard packets from undesired sources, but the processing cost of the authentication itself may be too high. 7. References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. (Updated by a Work in Progress.) 3. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of I...

...Network-layer authentication may be used to discard packets from undesired sources, but the processing cost of the authentication itself may be too high. 8. References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. (Updated by a Work in Progress.) 3. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of I...

...Network-layer authentication may be used to discard packets from undesired sources, but the processing cost of the authentication itself may be too high. 8. References 1. Bradner, S., "The Internet Standards Process -- Revision 3", BCP 9, RFC 2026, October 1996. 2. Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: A Transport Protocol for real-time applications", RFC 1889, January 1996. (Updated by a Work in Progress.) 3. Freed, N. and N. Borenstein, "Multipurpose Internet Mail Extensions (MIME) Part One: Format of I...