ANSI SCTE 165-17-2019 pdf free download – IPCablecom 1.5 Part 17: Audio Server Protocol.
5TECHNICAL OVERVIEW
The IPCablecom Audio Server Specification defines a suite of signaling protocols for providing announcement andmedia services in an IPCablecom network.This section of the document:
.Defines the architectural requirements for providing IPCablecom announcement and media services,
Defines and categorizes announcement and media types,
Defines the components and their roles in the IPCablecom Audio Server Architecture, as described in theIPCablecom Architecture Technical Report [5], and
.Describes the signaling and media inter faces in the IPCablecom Audio Server Specification.5.1Architectural Requirements
The architectural requirements and assumptions for providing Audio and Media Services for an IPCablecom
Network are listed below. These requirements are based upon the specifications and technical reports that define theIPCablecom architecture.
5.1.1 Call Destination
The Audio Server Specification must define how announcements are provided for IPCablecom on-net to off-net andon-net to on-net calls1.
5.1.2 Media Formats
A Media Player must be able to generate the required announcements in any of the code formats required by theIPCablecom Codlecs specification [3].
5.1.3Security
Audio MUST be signaled and played in a secure manner. Media Player Controllers and Media Players MUSTsupport the security protocols defined in the IPCablecom Security specification [4].
5.1.4Operational Support Systems
Media Player Controllers MUST support the IPCablecom billing and event message protocols as defined in [7], asapplicable to the applications they support. No requirement has been identified for support of event reporting by theMedia Player.
5.2Announcement Definitions
Announcements can be divided into four distinct categories: tones, fixed-content, variable content, and interactiveannouncements.
5.2.1 Tones
Includes tones such as reorder, busy, and ringback. See [1] and [6] for details.
5.2.2 Fixed-content Announcements
Fixed-content Announcements consist of audio messages with fixed-content that require no user interaction.Forexample, “Your call did not go through. Please hang up and try your call again.”
5.2.3Variable Content Announcements
Variable Content Announcements are messages that contain a customizing parameter(s) yet require no userinteraction. For example, “The number you have dialed,321-9876, has been changed. The new number is 321-6789.”
5.2.4lnteractive Announcements
Interactive Announcements are announcements that require user interaction, DTMF(Dual Tone Multi-Frequency) orIVR.For example, “The number you have dialed, 541-321-9876, has been changed. The new number is 541-32i-6789.To be connected to the new number, at a cost of thirty-five cents, please press 1.”
5.2.5 Naming Conventions for Endpoint ldentifiers
A flat name space for endpoints is used, with audio ports indicated by the prefix aud and the port number, e.g.，aud/’12@audio-server-3.whatever.net. Wildcards ($, *) may be used in place of the port numbers in accordance withstandard NCS rules for wild card use.
Systems that support announcements only (i.e., no digit collection, no recording, and no spech recognition ability)may use the prefix ann instead of aud.
Some systems may use one additional level in the naming scheme to support the identification of specific cards. Inthis case the naming would look like aud<card number>/<port number>@audio-server-3.whatever.net
5.3 Interfaces
The IPCablecom Audio Server Specification defines a set of interfaces between the components responsible forproviding audio services. The following figure illustrates the interfaces between these components. Only where aninterface is exposed is it expected to meet IPCablecom specification requirements.ANSI SCTE 165-17 pdf download.