Announcements service
23
When the Media Application Server receives a request to play an
announcement, the server looks for the file name and checks if it has a file
for the language requested. If no file is found, the Media Application Server
returns a Not Found indication to the Session Manager, that proceeds as if
no announcement was to be played (in other words, forwards the original
failure cause to the originator). The Media Application Server pegs an
operational measurement (OM) and creates a log if a treatment file is not
found or if the license count was exhausted, and the Session Manager
creates a log if it receives a File Not Found or Temporarily Unavailable
indication from the Media Application Server.
Branding announcements
You can use Branding announcements to play prerecorded marketing
messages to people who use your network. A branding announcement
plays before the call is routed to the called number.
Branding announcements consist of one or more audio messages that you
(the administrator) can chain together, and for which you can specify a
playback order. Additionally, you can configure these messages to loop
indefinitely, or for a specified duration.
The Announcement service is service package independent, which means
branding announcements are also service package independent. If the
following conditions are met, the caller hears a branding announcement
before the call is answered:
•
you configured branding announcements for a domain (and optionally a
subdomain)
•
you placed the necessary audio files on the MAS
Note: The branding announcement that plays to the originator of a call
is based on the domain or subdomain of the called party.
During call set up, the Session Manager determines if the originating and
called parties are within
•
the same subdomain (of a parent domain)
•
different subdomains (of a parent domain)
After the Session Manager determines the relationship of the originator
and called parties within the domain or subdomain hierarchy, the Session
Manager uses the rules found in
Table 2 "Branding for calls between users
within subdomains of a domain" (page 24)
to determine whether to play a
branding announcement to the originating party.
Note: In the example
Table 2 "Branding for calls between users within
subdomains of a domain" (page 24)
, there is a parent domain (xyz.com),
and two subdomains (a.xyz.com and b.xyz.com). A value of True under
Nortel Media Application Server
Media Application Server Planning and Engineering
NN42020-201
01.04
Standard
4.0
27 July 2007
Copyright © 2007, Nortel Networks
.
