Because phantom calls can be directed anywhere, you must properly configure the application and Communication Manager to ensure that the vector commands that are executed for the calls make sense. For more information, see Communication Manager CallVisor ASAI Technical Reference.
Communication Manager does not block phantom calls from executing any vector commands because phantom calls follow the same vector processing as regular voice calls. However, do not allow phantom calls to enter certain vector steps such as the following.
Steps |
Description |
Announcements |
Because there is nobody listening to an announcement that is made to a phantom call, there is no sense in playing one. |
Collect steps |
In a phantom call, the collect step fails because the step cannot connect a tone receiver to a station Administration Without Hardware (AWOH). The step times out because there is nobody to enter the expected digits. The busy step provides a busy signal to the caller. In a phantom call, the busy step disconnects the call because Communication Manager clears a phantom call when the call cannot terminate at a specific local destination. |
