Nortel Networks Telephone NN10033-111 Manual de usuario Pagina 29

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 42
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 28
Configuration Management 29
Copyright © 2003, Nortel Networks MCP Interworking Basics
Nortel Networks Confidential
When the SIP Application Module is deployed from the management
server, the service node name is defined in one of two places,
depending on whether or not the SIP Application Module is configured
in an N+M cluster.
Non-N+M node name configuration
In a non-N+M cluster configuration, the service node name is added to
the "Server Properties" tab in the System Management Console. In a
non-N+M configuration, the service node name can be the node name
of the SIP Application Module platform. For more information on
configuring the SIP Application Module service node name in a
non-N+M configuration, please refer to the Configuration chapter in the
MCP SIP Application Module Basics document.
Once the service node name information is configured in the “Server
Properties” tab of the System Management Console, this information
must then be datafilled on the CS 2000 (table MGCINV).
N+M node name configuration
In an N+M configuration, the service node name has to be assigned to
the service instance so, unlike the non-N+M configuration, the service
node name can not be the node name of the SIP Application Module
platform. Each service instance is defined as a service parameter in
each Network Service Description (NSD) in the “Transport
Management” tab. Each NSD has to define a unique service name.
This is done by adding a service name of "Service_Node_Name" in the
label field and the desired node name in the Value part. For more
information on configuring the SIP Application Module service node
name in a N+M configuration, please refer to the Configuration chapter
in the MCP SIP Application Module Basics document.
Once the service node name information is configured in the “Transport
Management” tab of the System Management Console, this
information must then be datafilled on the CS 2000 (table MGCINV).
CS 2000 node authorization
The SIP Application Module allows only authorized network nodes to
send a SIP request to it with out requiring the request to be
authenticated. The SIP PRI Gateway is an example of an authorized
network node; the SIP Application Module does not challenge incoming
call requests from the SIP PRI Gateway. The CS 2000 node must be
added to list of authorized nodes so that it can send SIP-T messaging
to the SIP Application Module. This is achieved by adding the IP
address of the CS 2000 to the Authorized SIP Nodes field in the
“Authentication” tab of the System Manage Console. For more
information on configuring the SIP Application Module service node
Vista de pagina 28
1 2 ... 24 25 26 27 28 29 30 31 32 33 34 ... 41 42

Comentarios a estos manuales

Sin comentarios