Cisco DPA 7610 Voice Mail Gateway Version 1.1(1) Release Notes

CSCdr83003

The FTP server does not require a username or a password.

The DPA 7610 does not require user names and ships without a set or enabled password. Once you set a password, however, the DPA 7610 requires that you use it.

If you are able to access FTP without entering a password, then no password has been set. To set the password, complete the following procedure: From the main menu, select Configure > Passwords, select Login password, then enter the new password.

Refer to the section "Configuring Passwords" on page 4-10 in the Cisco DPA 7630/7610 Voice Mail Gateways Administration Guide for more details.

CSCdr83478

The console locks up and requires a power cycle to resume functioning.

In rare circumstances, a terminal program connected to the console port of the DPA 7610 might lock up. The DPA 7610 itself continues to function correctly.

To work around the problem, restart the terminal program.

CSCdr87999

Fax messaging fails to work across a G.711 inter-cluster trunk.

Under certain circumstances, fax messaging across a G.711 inter-cluster trunk can fail.

Be aware that fax messaging will not work if any part of the system through which you are sending the fax is operating in G.729 mode. Verify that your inter-cluster trunk, or H.323-analog gateway, is registered as a G.711 in the Cisco CallManager.

CSCdr88571

The Message Waiting Indicator (MWI) feature does not travel across an inter-cluster trunk.

MWI commands are not propagated across inter-cluster links. Therefore, the DPA 7610 can set MWIs only for those extensions located on the same Cisco CallManager cluster as the DPA 7610 itself.

CSCdr90825

Sending a file to the DPA 7610 takes considerably longer than receiving the same file from the DPA 7610.

This is expected behavior. It takes longer to write to the Flash-based filing system used by the DPA 7610 than to read from it.

CSCdr93073

Only two simultaneous Telnet sessions are supported by the DPA 7610 at any given time.

This is expected behavior. The DPA 7610 does not accept more than two simultaneous Telnet sessions.

CSCdr93980

Attempting an unsupervised transfer from an Octel Voice Mail System to a non-existent or busy Cisco CallManager extension results in the caller being disconnected.

Do not allow extensions that do not have a "forward when busy" number assigned to them to be the target of unsupervised transfers. If this is unavoidable, all extensions should forward on busy to a device that is always be available, such as the DPA 7610.

CSCds08331

Time stamps and delta times in the event log are out of order or expressed as negative numbers.

The DPA 7610 maintains time by periodically synchronizing with a network time source (an NTP server) and by relying on its own internal timer between network updates. Because this internal timer can differ slightly from the NTP server's time source, a gradual divergence between the two clocks can occur, requiring adjustments upon the next synchronization. These adjustments can cause time stamps and delta times in the event log to appear out of order.

CSCds25389

Voice mail hunt groups containing more than 13 extensions can cause voice mail access to fail with an error tone.

By default, Cisco CallManager supports a maximum of 12 forwarding hops, leading to a maximum of 13 extensions in any one hunt group.

To work around the problem, do one of the following steps:

• Set the "ForwardMaximumHopCount" System Parameter to more than 12. (Refer to the section "Setting the Hop Count" on page 3-12 of the Cisco DPA 7630/7610 Voice Mail Gateways Administration Guide for instructions on setting this parameter.)

• Divide the DPA 7610 into several hunt groups (possibly all in the same forwarding chain) to improve load balance.

CSCds25783

Transfers using the Octel 200 Voice Mail System fail if the caller presses phone keys while on hold.

Octel-supervised transfers fail if keys are pressed while the call is on hold. This is expected behavior caused by operational differences between Meridian 1 PBX systems and the Cisco CallManager.

CSCds34595

When set to perform supervised transfers, an Octel 250 Voice Mail System sometimes inaccurately reports that an extension is busy.

The Octel system sometimes identifies as busy an extension that is actually unavailable. This occurs when the Octel system is set to perform supervised transfers to an extension, and when that extension is configured to forward all calls to voice mail. Under these circumstances, the Octel system cannot correctly identify why a call is forwarded to voice mail.

CSCds38975

Using the Cisco IP Phone 7960 in speakerphone mode at a high volume and in conjunction with the DPA 7610 can cause some dual tone multi-frequency (DTMF) digits to be sent twice.

Some DTMF digits are sent both in-band (caused by acoustic coupling between the speaker and the microphone) and out-of-band. As a result, the Octel Voice Mail System receives the digit twice.

To work around this problem, ensure that the Cisco IP Phone operates with a firmware version of P003D301 or later.

CSCds39732

MWIs (message waiting indicators) fail to turn off and the Octel 250 Voice Mail System disables its MWI ports.

For MWIs to function properly, the Message Waiting Timeout feature in menu 6.2 of the Octel system must be set to the "positive acknowledgement" setting.

The "negative acknowledgement" setting directs the Octel system to interpret the lack of a confirmation tone as an error indication. The DPA 7610 requires that the "positive acknowledgement" option be used.

To work around this problem, set the Octel system's Message Waiting Timeout feature in menu 6.2 to "positive acknowledgement."

CSCds40475

Transfers from a Cisco IP Phone to a PBX phone via the DPA 7610 are routed directly to voice mail.

The DPA 7610 functions properly in a Hybrid configuration only if the Cisco CallManager has a route plan that allows the Octel Voice Mail System to make calls to a PBX system via the Cisco CallManager.

For example:

• PBX directory numbers are 5XXX

• Cisco CallManager route plan is 8.XXXXX

In this case, you must create a route plan for the Cisco CallManager that accepts the PBX pattern of 5XXX and allows the DPA 7610 to route the calls over the digital link.

CSCds59539

You cannot manually add a static route to the DPA 7610.

The DPA 7610 can receive Internet Control Message Protocol (ICMP) redirects from the gateway and update its routing tables accordingly.

CSCds73942

When resetting a DPA port from Cisco Call Manager, the port status screen on the DPA 7610 does not always show the port being reset.

The port status screen is refreshed periodically. Sometimes, the port completes the reset cycle and comes back up in between the screen refresh.

CSCds76719

If the event log levels on the DPA 7610 are set to "trace" for all ports, then functionality is impaired.

You should only enable trace if instructed to do so by a Cisco technical representative.

CSCds91358

On an Octel 250/350, the DPA 7610 may cause the "loopback test" from the port test menu to fail, giving as the reason "NO AV A RESP."

This does not indicate an error with the Octel system. Regular port testing should be disabled on ports connected to a DPA 7610 to avoid generating errors on the Octel.

CSCdt04499

Calls going through the DPA 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 7610 until all the ports on the DPA 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 7610 appear disabled, but they are enabled in the Meridian 1 PBX.

The DPA 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 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 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 7610 needs to be restarted after a change to the Ethernet speed or duplex setting.

This is as designed.

CSCdt45372

The DPA 7610 might exhibit problems if the Ethernet interface is set to auto-negotiation and the switch is set to fixed speed or duplex, or vice-versa.

This is not a supported configuration. The DPA 7610 requires that both connections are either configured to auto-negotiaton or set to the same combination of speed and duplex.

CSCdt49576

Reprogramming the boot loader while the DPA 7610 is busy causes other activity on the DPA 7610 to be suspended or stopped.

You should only update the boot loader when the DPA 7610 is otherwise idle.

Caution   Only upgrade the boot loader if you are instructed to do so by a Cisco technical representative. If you encounter difficulties during this upgrade, such as a loss of power, the DPA 7610 might not be able to start up.