Last updated: November 14, 2006
This section is only applicable to the lab application.
Each calling party has three states in the Call Waiting test, they are defined as follows:
Idle - There is no voice call between MS and the calling party.
Waiting - The voice call from one calling party is waiting for an answer from MS while MS is already in a voice call with another calling party.
Active - There is a voice call established between MS and the calling party.
These states can be observed from the
Call Waiting Information
window or queried with
CALL:SSERvice:WAITing:CPNumber[1]:STATus[:STATe]?
and
CALL:SSERvice:WAITing:CPNumber2:STATus[:STATe]?
.
Many events can make calling parties to transfer states. All possible state transitions and the events cause them are described below. You can click on the blue letters for the detailed descriptions of the events.
MS initiates a voice call and establishes a connection with calling party 1.
Execute "
Originate Call
" from the test set and establish a connection with MS.
Execute "
Connect Calling Party 1
" from the test set when the call with calling party 2 is already active, notify MS that calling party 1 is waiting.
Execute "
Connect Calling Party 2
" from the test set when the first call with calling party 1 is already active, notify MS that calling party 2 is waiting.
Execute "
Disconnect Calling Party 1
" from the test set when it is waiting, notify MS that calling party 1 is no longer waiting.
Execute "
Disconnect Calling Party 1
" from the test set when calling party 1 is active and calling party 2 is waiting, mute the voice path since there is no active calling party.
Execute "
Disconnect Calling Party 2
" from the test set when it is waiting, notify MS that calling party 2 is no longer waiting.
Execute "
Disconnect Calling Party 2
" from the test set when calling party 2 is active and calling party 1 is waiting, mute the voice path since there is no active calling party.