
Known Issues
14
Known Issues
78-12814-03
CSCdt04499 Calls going through the
DPA 7630/7610 immediately
after a port has registered with
Cisco CallManager might not be
answered by the Octel system.
This is caused by Octel ports not being
completely ready to accept incoming calls until
some time after they are initialized.
To work around this, do not make calls through
the DPA 7630/7610 until all the ports on the
DPA 7630/7610 have been initialized.
CSCdt12455 The Octel 200 appears to take a
while to initialize its ports when
connected to the DPA 7610.
The ports appear as initialized on the DPA port
status screen, but using the “pstat” command on
the Octel 200, the ports appear to be in “err” state.
Calls made through the DPA 7610 while it is
initializing might be unanswered by the voice
mail system.
To avoid this problem, allow more time for all the
Octel ports to initialize before making calls
through the DPA 7610.
CSCdt15035 The PBX ports on the DPA
7630/7610 appear disabled, but
they are enabled in the Meridian 1
PBX.
The DPA 7630/7610 requires all ports connected
to the Meridian 1 PBX to have key 6 configured as
a MSB key. If they do not have this, the
DPA 7630/7610 cannot determine that the PBX
ports are active. Therefore, the ports appear to be
disabled, and MWIs will not work on PBX
phones.
The DPA 7630/7610 requires the all of the
following keys on ports connected to the PBX:
• 06 MSB (Make Set Busy)
• 13 MIK (Message Indication Key)
• 14 MCK (Message Cancel Key)
CSCdt44142 The DPA 7630/7610 needs to be
restarted after a change to the
Ethernet speed or duplex setting.
This is as designed.
Table 3 DPA 7630/7610 Known Issues (continued)
Bug ID Summary Explanation
Comentarios a estos manuales