Nortel Networks NN44470-100 - Manual (Page 18)

- 18 -
MAS commissioning
Nortel Media Application Server 6.0 for AS 5300
Fundamentals
NN44470-100 01.01 Standard
Release 6.0 03 June 2008
Copyright © 2008, Nortel Networks
The platform has an internal domain called the wildcard domain, which is
represented with an asterisk and is the default domain if no matching domain
is found.
SIP accounts
SIP accounts are used for application registration in the SIP network. The
MAS registers all accounts against the registrar servers. For information about
the servers, see
SIP registrar servers (page 19) . You can view, add, and
delete SIP accounts.
SIP trusted nodes
MAS processes SIP traffic from trusted nodes only (for example, proxies and
gateways). Any requests from a nontrusted node are rejected. You can view,
add, and delete trusted nodes.
Attention: If you add or delete a trusted node, you must restart the platform
for the change to take effect.
SIP routes
Use SIP routes to define all proxy and registrar servers with which a MAS
node communicates. You can configure up to 32 routes for each domain.
SIP proxy servers
A SIP proxy server accepts MAS requests and queries the SIP registrar server
to obtain the recipient addressing information. The proxy server then forwards
the request directly to the recipient if the recipient is in the same domain or to
another proxy server if the recipient is in a different domain.
The MAS platform uses proxy server routes to route outbound SIP requests
to the appropriate proxy server for outbound traffic load sharing and failover.
Routes are selected based on the domain (or subdomain) lookup. If no
matching domain is configured, the default wildcard (*) route is used. For
example, if an outbound call is made to [email protected], the routes
associated with the techtrial.com domain are selected.
On the first routing attempt, the MAS platform selects active routes that are
online based on the lowest priority only. The weight is used to select routes
within the same priority level. Route selection from the next priority level is
chosen automatically only if the lower priority routes are either offline or fail to
respond.
For load sharing configurations, you can define multiple routes with the same
priority. For failover configurations, configure the primary routes with
priority = 0 and weight = 10 and configure the secondary routes with
priority = 1 and weight = 10.