Media Application Server configuration
37
Error or unusual scenario behavior
The following table describes various error or unusual ringback or treatment
service behaviors.
Table 4
Error or unusual ringback or treatment service behaviors
Error
Description or Solution
MAS not
available or
misprovisioned
The ringback service attempts to send an INVITE to the MAS to trigger
ringback. If the routing to the MAS itself (pooled entity not defined) is not
present, an internal 404 message is generated and the service does not
activate. The transferred endpoint continues to hear silence and does not
have ringback applied.
If the MAS itself is unavailable due to maintenance or network issues, a four
second sanity timer runs on the Session Manager. Upon expiration, an internal
error is generated and the service does not activate. This same mechanism is
currently in use for other media services, such as branding or Music-on-hold.
Transfer-to
party simrings
(forking)
In a forked call scenario, the Session Manager strips all SDPs that may
be received from the far end device so as to avoid an unpredictable user
experience. This means that the service always applies and provides audible
ringback where the destination is reached by means of a forked call; there be
no cut-through of any far end provided media.
Transfer-to party
sequentially
advances
On a sequential advance scenario, the user experience behaves as described
in
"SIP protocol considerations" (page 34)
; that is, the network-based audible
ringback service is applied when no SDP is provided by the currently-alerted
terminator. Far end media is cut-through, however, if that is available
(indicated by the presence of an SDP in the 18x message).
Media Application Server configuration
This section contains information for configuring MAS for the various
services.
Configuring ringback service
There is no special configuration for the MAS for the ringback service. The
ringback files are provided by the base MAS installer for the announcement
service that must be present for this feature.
Configuring announcement files on the MAS
Note: You must place the announcement files on the D drive of the
Media Application Server. There is no room on the C drive.
For detailed information about configuring announcement files on the MAS,
see MAS Announcements Fundamentals (NN42020-130).
Nortel Media Application Server
Media Application Server Planning and Engineering
NN42020-201
01.04
Standard
4.0
27 July 2007
Copyright © 2007, Nortel Networks
.
