ANSI SCTE 24-2-2016 pdf free download – IPCablecom 1.0 Part 2: Audio Codec Requirements for the Provision of Bi-directional Audio Service over Cable Television Networks Using Cable Modems.
The legal/regulatory classification of IP-based voice communications provided over cable networks and otherwise, and the legal/regulatory obligations, if any, borne by providers of such voice communications, are not yet fully defined by appropriate legal and regulatory authorities. Nothing in this specification is addressed to, or intended to affect, those issues. In particular, while this document uses standard terms such as “call,” “call signaling,” “telephony,” etc., it will be evident from this document that while an IPCablecom network performs activities analogous to these PSTN functions, the manner by which it does so differs considerably from the manner in which they are performed in the PSTN by telecommunications carriers. These differences may be significant for legal/regulatory purposes.
1.4 Phasing of Requirements The codec requirements contained in this specification cover both audio and video Multimedia Terminals (MTAs) and Trunking Gateways (Media Gateway). The term MTA-2 is used to define a terminal supporting video. In the initial phase of IPCablecom, MTAs are not required to support the MTA-2 requirements as defined in Section 8 of this specification. MTAs MUST support the requirements for audio terminals as defined in Sections 2, 6, 7, and 9. All MTA-2s MUST support the requirements defined in Section 8.
2REFERENCES
The following documents contain provisions which, through reference in this text, constitute provisions of thisstandard.At the time of Subcommittee approval, the editions indicated were valid. All documents are subject torevision, and while parties to agreement based on this standard are encouraged to investigate the possibility ofapplying the most recent editions of the documents listed below, they are reminded that newer editions of thosedocuments might not be compatible with the referenced version.
2.1 Normative References
In order to claim compliance with this standard, it is necessary to conform to the following standards and otherworks as indicated, in addition to the other requirements of this standard. Intellectual property rights may berequired to implement these references.
[]ANSISCTE 24-01 2016,IPCablecom 1.0 Part 1:Architecture Framework for the Delivery of Time-CriticalServices over Cable Television Networks Using Cable Modems.
[2]ANSISCTE24-04 2016, IPCablecom 1.0 Part 4: Dynamic Quality of Service for the Provision of Real-Time Services over Cable Television Networks Using Data Modems.
[3]ANSISCTE 24-03 2016,IPCablecom 1.0 Part 3: Network Call Signaling Protocol for the Delivery of Time-Critical Services over Cable Television Using Data Modems.
[4]ANSI T1.521-1999,A Packet Loss Concealment Technique for Use with ITU-T Recommendation G.711.[5]IMTC Voice-Over-IP Forum Service Interoperability Implementation Agreement 1.0, dated December 1,1997,
[6]”Current Methods of Speech Coding.” R.V.Cox. Ilnternational Journal of High Speed Electronics & Systems,Vol 8, No 1 (1997) pp 13-68.
[7]IETF RFC 1890,RTP Profile for Audio and Video Conferences with Minimal Control, Audio-Video Transport Working Group, H. Schulzrinne.January 1996.
[8]IETF RFC 2327,SDP: Session Description Protocol.M.Handley,V.Jacobson.April 1998.[]IETF RFC0821, Simple Mail Transfer Protocol.J.Postel.Aug-01-1982.
[10] IETF RFC 2104,HMAC: Keyed-Hashing for Message Authentication.H. Krawczyk,M. Bellare,R. Canetti.February 1997.
[11]IETF RFC 1945,Hypertext Transfer Protocol –HTTP/1.0.T.Berners-Lee,R.Fielding,H. Frystyk.May 1996.
[12] IETF RFC 2068,Hypertext Transfer Protocol –HTTP/1.1.R. Fielding,J. Gelys, J.Mogul,H.Frystyk, T.Berners-Lee.January 1997.
[13] IETF RFC 2705,Media Gateway Control Protocol (MGCP) Version 1.0.M. Arango, A. Dugan,I.Elliot,C.Huitema, S. Pickett.October 1999.
[14] IETF RFC 2138,Remote Authentication Dial n User Service (RADIUS).C.Rigney,A. Rubens,W.Simpson, S. Willens.April 1997.
[15] IETFRFC 2139,RADIUS Accounting.C. Rigney.April 1997.
[16] IETF RFC 1889,RTP: A Transport Protocol for Real-Time Applications. Audio-Video Transport Working Group, H. Schulzrinne, S. Casner, R.Frederick, V. Jacobson. January 1996.ANSI SCTE 24-2 pdf download