Avaya Administering Aura Session Manager Release 6.1 Manual de usuario Pagina 287

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 532
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 286
that exists in the same import operation as the SIP Entity. SIP Entity of type “ASM” <Avaya
Session Manager> cannot contain an adaptation entry.
<adaptationName> contains the adaptation module name and parameters separated by
spaces <examples below>.
Listen ports (<listenports>) are only relevant for SIP Entity of type “ASM”. Do not include
these entries for any other type of SIP Entity.
• Multiple listen ports entries (<listenports>) can be configured for one ASM SIP Entity.
- <sipdomainName> must refer to an existing domain with the exact same name. It
must either appear in the System Manager database or in an import file that exists
in the same import operation as the SIP Entity.
- The values in <transportprotocol> must appear exactly same (being case sensitive)
as they appear in the System Manager user interface.
The values of <timezoneName> should be same (being case sensitive) as that of the field
“Time Zone” in the SIP Entity user interface in System Manager.
• The field <userfc3263> corresponds to the “Override Port & Transport with DNS SRV”
check box in the SIP entity form.
The value of <entitytype> must contain one of the following values exactly as they appear
below being case sensitive.
- CM — communication manager (CM in the user interface)
- ASM — Session Manager in the user interface
- Modular Messaging — Session Manager in the user interface
- VP — Voice Portal in the user interface
- Gateway — Gateway in the user interface
- SIP Trunk — SIP Trunk in the user interface
- OTHER — Other in the user interface.
• The values in <cdrSetting> must appear exactly same being case sensitive, as they
appear in the System Manager user interface.
The field <do_monitoring> corresponds to the field “SIP Link Monitoring” in the SIP Entity
details form. The relation is as follows:
- In order to enable SIP Link monitoring, <do_monitoring> value must be “yes”
- In order to enable SIP Link monitoring, <do_monitoring> value must be “no”
- In order to use the Session Manager configuration, the <do_monitoring> tag must
be completely omitted.
Example:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<sipentityFullTOList>
<SipentityFullTO>
<notes>this is a test</notes>
SIP Entities
Administering Avaya Aura
®
Session Manager November 2010 287
Vista de pagina 286
1 2 ... 282 283 284 285 286 287 288 289 290 291 292 ... 531 532

Comentarios a estos manuales

Sin comentarios