Dropping The Original Call During Consultation Transfer; Transferring Number Not Displayed; Caller Id Not Reported; Call Status Messages Sent By Meridian Link Services - Nortel TAPI User Manual

Chapter 8 Troubleshooting 185

Dropping the original call during consultation transfer

If the original call is dropped while the consultation call is ringing, Symposium
TAPI SP fails.

Transferring number not displayed

When transferring a call, Meridian Link Services supplies only the DN of the
party performing the transfer if the destination party DN is AST-controlled.

Caller ID not reported

Meridian Link Services does not transfer the CLID to the called party in a
conference call if the receiving DN is not AST-controlled. The CLID of the party
initiating the conference displays as unknown.

Call status messages sent by Meridian Link Services

Meridian Link Services still sends call status messages, even if you select
outbound call processing only in the configuration application. It is normal
practice to select inbound call processing as well.

Called number not displayed when routed to a CDN

Meridian Link Services presents the calling number, but not the called number,
when the incoming call is transferred or forwarded to a CDN. For example, 2495
calls 2491, 2491 forwards the call to a CDN (2121). The route request message
shows the calling number (2495) but not the called number (2491).

Call parking not supported

Meridian Link Services does not support call parking. There are no park or unpark
status change messages. When a call park is performed manually at the telephone
set, the call is reported as on hold and does not go off hold. If the call is not picked
up, a new call is presented in addition to the onhold call, with the same CLID as
the CLID of the held call.
Network Managers Guide for Symposium TAPI Service Provider for Succession, release 3.0