Ujjval Karihaloo wrote: > T38 rfc does not detail the sequence of t30 negotiations.. > Like v21 preamble, nsf, Dsi, what the correct sequence of t30 > negotiation. Is.
T.38 is not an RFC, it's an ITU recommendation, as is T.30. The T.30 and T.38 specifications (along with T.4 and a few others) fully specify the FAX protocol, as they are the actual protocol specifications for FAX. The recommendations can be found here: http://www.itu.int/rec/T-REC-T/recommendation.asp?lang=en&parent=T-REC-T.4 http://www.itu.int/rec/T-REC-T/recommendation.asp?lang=en&parent=T-REC-T.30 http://www.itu.int/rec/T-REC-T/recommendation.asp?lang=en&parent=T-REC-T.38 -- Kevin P. Fleming Digium, Inc. | Director of Software Technologies 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA skype: kpfleming | jabber: [email protected] Check us out at www.digium.com & www.asterisk.org _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2009 - October 13 - 15 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
