Meridian Link Services presents no information
Meridian Link Services presents no information on incoming calls that are not
answered and forwarded to a CDN. However, if the call is answered manually, a
status change message of active is presented, followed by a connected message.
Call progress messages not delivered
If a non-AST controlled telephone is called as the consultation leg of a manually
initiated (from the telephone and not a TAPI application) conference call, certain
call progress messages are not delivered to the application.
For example, consider three telephones: A, B and C. Both A and B are under
AST-control, but C is not. The agent on telephone A establishes a call to the agent
on telephone B. Using the conference key and the key pad on A, agent A places a
consultation call to the agent on telephone C. Because no Meridian Link Services
messages are sent when C answers the call, Symposium TAPI SP cannot
determine if agent C answered. In this scenario, Symposium TAPI SP registers the
call events as follows:
•
Agent A establishes a call to agent B — CallHandle1 = CONNECTED.
•
Agent A places a consultation call to agent C resulting in the following:
— CallHandle1 = CONFERENCED
— CallHandle2 = DIALTONE
— CallHandle3 = ONHOLDPENDING-CONF
Note: CallHandle2 is the consultation leg of the call and CallHandle3 is
the conference call.
•
Agent C answers the consultation call and all call handles remain the same.
•
Agent A completes the conference call resulting in the following:
— CallHandle1 = CONFERENCED
— CallHandle2 = CONFERENCED
— CallHandle3 = CONNECTED
Network Managers Guide for Symposium TAPI Service Provider for Succession, release 3.0
Chapter 8 Troubleshooting
183