Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario Pagina 82

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 306
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 81
Avaya Media Processing Server Series System Reference Manual
Page 82 # P0602477 Ver: 3.1.11
Call Control Manager (CCM/CCMA)
Startup parameters for CCM can be specified as command line options in the
MPSHOME/mpsN/etc/vos.cfg file for the component CCM controls (see The
vos.cfg File on page 143). These options apply to the current instance of CCM, and
cannot be overridden directly from a command/shell line. If the parameters to CCM
need to be changed, the system must be stopped, the vos.cfg file edited, and the
system restarted. Configuration options available to CCM and CCMA are contained in
The ccm_phoneline.cfg File on page 151 and The ccm_admin.cfg File on
page 155, respectively.
The command line options for CCM are shown below:
The -d option should only be used to enable debugging of errors that happen before
the system is up (i.e., before being able to enable debugging via vsh). The -d option
is typically used for debugging administrative application bind issues in CCM.
ccm
[-c <class>] [-d <debug_obj>]
[-s <num_list>]
-c <class> Specifies whether CCM provides administrative (admin) or
Telephony & Media Service (tms) services. The default for this
option is tms.
-d
<debug_obj>
Enables debugging from startup. All debugging is written to the
default file $MPSHOME/common/log/ccm.dlog. The following
debug objects are supported: LINE, ERROR, STARTUP, ALL.
-s <num_list>
Specifies the service IDs/lines that CCM controls. This option is
only required when the class is tms; it is ignored for admin class.
This option has no default.
Vista de pagina 81
1 2 ... 77 78 79 80 81 82 83 84 85 86 87 ... 305 306

Comentarios a estos manuales

Sin comentarios