Cisco BTS 10200 Guía de instalación Pagina 31

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 60
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 30
CISCO CONFIDENTIAL
31
Cisco BTS 10200 Softswitch — Release Notes for Release 3.3 V04
OL-1835-04
Caveats
CSCdy37084 Sendevent does not show up in FMG.log Symptom: Sendevent.sh -s 2 -l 2 -i 2 was typed and nothing
appeared in the file FMG.log
Impact: Events do not show up on FMG.log file.
Conditions: Running of test case Event_Management_
NA_SNG_00016 did not work.
Workaround: Issue the command “CLI> subscribe event-report
type=all; severity=all”, then any events issued (either through
normal operation or sendevent.sh) can be seen.
CSCdy46844 “Cannot receive SIP messages from
network” alarm does not clear
Symptom: BTS 10200 software version 3.3 does not properly
clear “Cannot receive SIP messages from network” alarms.
Impact: If the alarm remains on after the port conflict has been
resolved and the process that issued the alarm has been
successfully restarted, there is no direct service impact.
Conditions: This alarm is issued when the a process using the
SIP stack cannot open the port it is configured to use. This can
happen if the BTS is not configured properly, or if some other
program running on the BTS is using the port that the process is
configured to use.
If a process that uses the SIP stack cannot open the port it is
configured to receive messages on, it will issue this alarm and
exit. In order to get the system to work properly, the port conflict
must be resolved and the process must be restarted.
Workaround: Follow the steps described in the alarm
description to remove any port conflicts.
Before restarting the call agent, use the CLI to manually clear
the alarm. Then restart the call agent and verify the alarm is not
issued again.
The current alarm description does not tell the operator to clear
the alarm.
CSCdy47391 Unable to display all sub /trunk
termination status via COBRA interface
Symptom: When user inputs ID for all subscribers id=*@mgw,
EPOM came up with error: java.lang.NullPointerException
Impact: Cannot view all subscribers using EPOM.
Conditions: Current EPOM is able to display individual CIC for
a specified trunk group when the user selects to view
trunk-termination status. However, it failed to display for all
CICs in a trunk group.
Workaround: Use CLI command to view all subscribers,
Table 2 Open Caveats (continued)
DDTS ID Description Workaround
Vista de pagina 30
1 2 ... 26 27 28 29 30 31 32 33 34 35 36 ... 59 60

Comentarios a estos manuales

Sin comentarios