22
Introduction
Treatment (cause) reason
Message
number
TEMPORARILY_UNAVAILABLE
480
CALL_LEG_TRANSACTION_DOES_NOT_EXIST
481
LOOP_DETECTED
482
TOO_MANY_HOPS
483
ADDRESS_INCOMPLETE
484
AMBIGUOUS
485
BUSY_HERE
486
REQUEST_TERMINATED
487
NOT_ACCEPTATBLE_HERE
488
EVENT_NOT_SUPPORTED
489
REQUEST_PENDING
491
SERVER_INTERNAL_ERROR
500
NOT_IMPLEMENTED
501
BAD_GATEWAY
501
SERVICE_UNAVAILABLE
503
GATEWAY_TIMEOUT
504
VERSION_NOT_SUPPORTED
505
BUSY_EVERYWHERE
600
DECLINE
603
DOES_NOT_EXIST_ANYWHERE
604
NOT_ACCEPTABLE
606
If a call fails due to one of the reasons listed in
Table 1 "Treatment (cause)
group reasons" (page 21)
, the Session Manager checks if it is the home
server for the originator. If the Session Manager is not the home server for
the originator, it proxies the failure cause. If the Session Manager is the
home server for the originator, it checks if the reason is provisioned in one
of the treatment groups under the subdomain of the originating party.
If the Session Manager cannot find a reason in the subdomain treatment
groups, it looks in the groups under the parent domain. If the Session
Manager finds a reason in one of the treatment groups, it checks the
language preference of the called party. The language parameter is needed
to let the Media Application Server know which file to play for the user (file
name and locale parameters are both needed).
Nortel Media Application Server
Media Application Server Planning and Engineering
NN42020-201
01.04
Standard
4.0
27 July 2007
Copyright © 2007, Nortel Networks
.