Valid8.com/ACATS VoIP H.323 Conformance Test Suite, for use with H.323 Signaling Tester
TEST SUITE OVERVIEW
References
Archive/Project h323_ts
Version19171599
Date23 Feb 2010
Number of Scenarios984
Number of Groups95
Average per Group10
GROUP/SCENARIOTEST PURPOSE
H225
H225/
RAS
H225/
RAS/
RAS_TE_GDR
RAS_TE_GDR_00Tx GRQ message
Ensure that the IUT, to discover a Gatekeeper, sends a GRQ message.
User Action: Invite the IUT to send in unicast mode a GRQ message
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.1[2] subclause 7.8[3]
RAS_TE_GDR_01Rx GCF message successfully
Ensure that the IUT having sent a GRQ message in unicast mode, with the
gatekeeper Identifier set to a value other than NULL, on receipt of a GCF
message considers to have completed the GKDiscovery procedure successfully.
User Action: Invite the IUT to send in unicast mode a GRQ message
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.1[2] subclause 7.8[3]
RAS_TE_GDR_02Rx GCF message successfully
Ensure that the IUT having sent a GRQ message in multicast mode to the
well-known Discovery Multicast Address and gatekeeperIdentifier missing or set
to NULL, on receipt of a GCF message, considers to have completed its GKDiscovery
procedure successfully.
User Action: Invite the IUT to send in multicast mode a GRQ message
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.1[2] subclause 7.8[3]
RAS_TE_GDR_03Rx multiple GCF message successfully with one gatekeeper
Ensure that the IUT having sent a GRQ message in multicast mode to the
well-known Discovery Multicast Address and with gatekeeperIdentifier missing
or set to NULL, on receipt of multiple GCF message from different gatekeepers,
considers to have completed its GKDiscovery procedure successfully with one of
them.
User Action: Invite the IUT to send in multicast mode a GRQ message
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.1[2] subclause 7.8[3]
RAS_TE_GDR_04Rx GRJ message(rejectreason field) unsuccessfully
Ensure that the IUT having sent a GRQ message, on receipt of a GRJ message with a value in
the rejectreason field, does not consider to have completed its GKDiscovery procedure successfully.
User Action: Invite the IUT to send in unicast mode a GRQ message
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.1[2] subclause 7.8[3]
RAS_TE_GDR_05Tx same GRQ message again
Ensure that the IUT having sent a GRQ message, upon the first expiry of
default timer for GRQ message, re-sends the same GRQ message.
User Action: Invite the IUT to send in unicast mode a GRQ message
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.1[2], subclause 7.8[3] and 7.19[3]
RAS_TE_GDR_06Rx GCF message before timer successfully
Ensure that the IUT having sent a GRQ message for the second time,on receipt
of GCF message before the expiry of timer for a GRQ message, considers to
have completed its GKDiscovery procedure successfully.
User Action: Invite the IUT to send in unicast mode a GRQ message
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.1[2] subclause 7.8[3] and 7.19 [3]
RAS_TE_GDR_07Not Tx same GRQ message again
Ensure that the IUT having already sent a GRQ message for two times,
on the expiry of timer for a GRQ message, does not send the same GRQ again.
User Action: Invite the IUT to send in unicast mode a GRQ message
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.1[2], subclause 7.8[3] and 7.19 [3]
H225/
RAS/
RAS_TE_REG
RAS_TE_REG_01Tx RRQ message
Ensure that the IUT before attempting a call, sends a RRQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[2] subclause 7.2.2[2] subclause 7.9[3]
RAS_TE_REG_02Rx RCF message successfully
Ensure that the IUT having sent a RRQ message, on receipt of a RCF message,
considers to have completed its Registration procedure successfully.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.2 [2] subclause 7.2.2[2] subclause 7.9[3]
RAS_TE_REG_03Rx RRJ and restart gatekeeper discovery procedure
Ensure that the IUT having sent a valid RRQ message on receipt of a RRJ
message, restarts a gatekeeper discovery procedure.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[2] subclause 7.2.1[2] subclause 7.2.2[2] and subclause 7.9[3]
RAS_TE_REG_04Tx lightweight RRQ message(KeepAlive field = TRUE)
Ensure that the IUT having previously registered successfully, to keep the
registration alive, sends a lightweight RRQ message with the KeepAlive field set to TRUE.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[2] subclause 7.2.1[2] subclause 7.9[3]
RAS_TE_REG_05Tx RRQ message again
Ensure that the IUT having sent a RRQ message, upon the first expiry of timer
for a RRQ message, re-sends the same RRQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[2] subclause 7.2.2[2] subclause 7.9[3] and subclause 7.19 [3]
RAS_TE_REG_06Rx RCF message successfully
Ensure that the IUT having sent a RRQ message for the second time, on receipt
of RCF message before the expiry of timer for a RRQ message considers to have
completed its Registration procedure successfully.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[2] subclause 7.2.2[2] subclause 7.9[3] and subclause 7.19 [3]
RAS_TE_REG_07Not Tx RRQ message
Ensure that the IUT having already sent a RRQ message for two times, upon the
second expiry of timer for a RRQ message, does not re-send the same RRQ message again.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[2] subclause 7.2.2[2] subclause 7.9[3] and subclause 7.19 [3]
H225/
RAS/
RAS_TE_ADM
RAS_TE_ADM_01Tx valid ARQ
Ensure that the IUT, when it is registered with the gatekeeper, sends a valid
ARQ before attempting a call.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[3] subclause 7.2.4[2] subclause 8 [2] and subclause 7.11 [3]
RAS_TE_ADM_02Tx valid ARQ
Ensure that the IUT, when it is registered with the gatekeeper, on receipt of
a SETUP message, sends a valid ARQ.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[3] subclause 7.2.4[2] subclause 8 [2] and subclause 7.11 [3]]
RAS_TE_ADM_03Rx ACF and proceed with call
Ensure that the IUT, when it is registered with the gatekeeper having sent an
ARQ message in response to a SETUP message, on receipt of an ACF, proceeds
with the call.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[3] subclause 7.2.4[2] subclause 8 [2] and subclause 7.11 [3]
RAS_TE_ADM_04on Rx of ARJ, release call
Ensure that the IUT, when it is registered with the gatekeeper, on receipt of
a SETUP message, having sent an ARQ message, on receipt of an ARJ, releases
the call.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[3] subclause 7.2.4[2] subclause 8 [2] and subclause 7.11 [3]
RAS_TE_ADM_05on Rx of ACF, proceed with call and Tx IRR message
Ensure that the IUT, when it is registered with the gatekeeper on receipt of a
SETUP message, having sent an ARQ message, on receipt of an ACF with the
irrFrequency proceeds with the call and sends a IRR message in the requested
frequency.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[3] subclause 7.2.4[2] subclause 7.11[3]
RAS_TE_ADM_06Tx same ARQ message
Ensure that the IUT, when it is registered with the gatekeeper, on receipt of
a SETUP message, having sent an ARQ message, upon the first expiry of default
timer for a ARQ message, re-sends the same ARQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[3] subclause 7.2.4[2] subclause 7.11[3]
RAS_TE_ADM_07on Rx of ACF message, proceed with call
Ensure that the IUT, when it is registered with the gatekeeper, on receipt of
a SETUP message, having sent an ARQ message for the second time, on receipt of
an ACF message before the second expiry of timer for an ARQ message, proceeds
with the call.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[3] subclause 7.2.4[2] subclause 7.11[3]]
RAS_TE_ADM_08Not Tx same ARQ message again
Ensure that the IUT, when it is registered with the gatekeeper, on receipt of
a SETUP message, having already sent an ARQ message for two times, upon the
expiry of timer for an ARQ message, does not re-send the same ARQ message
again.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[3] subclause 7.2.4[2] subclause 7.11[3]
RAS_TE_ADM_09Tx ARQ to gatekeeperIdentifier
Ensure that the IUT, when it is registered with the gatekeeper, on receipt of
a SETUP message, having sent an ARQ message on receipt of an ARJ with the
field altGKInfo, sends an ARQ to a gatekeeperIdentifier from altGKInfo
received in the ARJ.
with the call.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[3] subclause 7.2.4[2] subclause 7.11[3]
RAS_TE_ADM_10On Rx of ACF, proceed with call
Ensure that the IUT, when it is registered with the gatekeeper, on receipt of
a SETUP message, having sent an ARQ message on receipt of an ARJ with the
field altGKInfo, after sending an ARQ to a gatekeeperIdentifier from altGKInfo
received in the ARJ on receipt of an ACF, proceeds with the call.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[3] subclause 7.2.4[2] subclause 7.11[3]
H225/
RAS/
RAS_TE_LOC
RAS_TE_LOC_01Rx LCF message successfully
Ensure that the IUT having sent a valid LRQ message in unicast mode, on
receipt of a LCF message, considers to have completed the Location procedure
successfully.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[4] subclause 7.2.3[2] subclause 7.13[3]
RAS_TE_LOC_02Rx LCF message successfully
Ensure that the IUT having sent a valid LRQ message in multicast mode, on
receipt of a LCF message, considers to have completed the Location procedure
successfully.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[4] subclause 7.2.3[2] subclause 7.13[3]
RAS_TE_LOC_03Rx LCF message unsuccessfully
Ensure that the IUT having sent a valid LRQ message, on receipt of a LRJ
message, considers to have not completed the Location procedure successfully.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[4] subclause 7.2.3[2] subclause 7.13[3]
RAS_TE_LOC_04Tx same LRQ message
Ensure that the IUT having sent a LRQ message, upon the first expiry of
default timer for a LRQ message, re-sends the same LRQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[4] subclause 7.2.3[2] subclause 7.13[3] subclause 7.13[3]
RAS_TE_LOC_05Rx LCF message successfully
Ensure that the IUT having sent a LRQ message for the second time, on receipt
of LCF message before the second expiry of timer for a LRQ message, considers
to have completed the Location procedure successfully.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[4] subclause 7.2.3[2] subclause 7.13[3] subclause 7.13[3]
RAS_TE_LOC_06Not Tx same LRQ message again
Ensure that the IUT having already sent a LRQ message for two times, upon the
second expiry of timer for a LRQ message, does not re-send the same LRQ
message again.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[4] subclause 7.2.3[2] subclause 7.13[3] subclause 7.13[3]
H225/
RAS/
RAS_TE_BND
RAS_TE_BND_01On Rx of BCF, consider request granted
Ensure that the IUT during a call, having sent a valid BRQ message to raise
its allowed bandwidth on receipt of a BCF from the Gatekeeper, considers that
its request has been granted.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[5] subclause 7.2.4[2] subclause 7.12[3]
RAS_TE_BND_02On Rx of BRJ message(rejectreason, insufficient resources, allowed bandwidth) considers request granted
Ensure that the IUT during a call having sent a BRQ message to raise its
allowed bandwidth on receipt of a BRJ message with the rejectreason
insufficient resources and allowed bandwidth, considers that its request has
been rejected.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[5] subclause 7.2.4[2] subclause 8.4.1[2] and subclause 7.12[3]
RAS_TE_BND_03Tx same BRQ message
Ensure that the IUT having sent a BRQ message, upon the first expiry of timer
for a BRQ message, re-sends the same BRQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[5] subclause 7.2.4[2] subclause 8.4.1[2] subclause 7.12[3] and subclause 7.19[3]
RAS_TE_BND_04On Rx of BCF message, consider request granted
Ensure that the IUT during a call having sent a BRQ message for the second
time, on receipt of a BCF message before the second expiry of timer for a BRQ
message, considers that its request has been granted.
User Action:
Config: A
SUT: Terminal
Status: -ubc
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[5] subclause 7.2.4[2] subclause 8.4.1[2] subclause 7.12[3] and subclause 7.19[3]
RAS_TE_BND_05Not Tx same BRQ message again
Ensure that the IUT during a call having sent a BRQ message for two times,
upon the second expiry of timer for a BRQ message, does not re-send the same
BRQ message again.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[5] subclause 7.2.4[2] subclause 8.4.1[2] subclause 7.12[3] and subclause 7.19[3]
RAS_TE_BND_06Tx BCF message
Ensure that the IUT during a call, on receipt of a valid BRQ message to raise
its allowed bandwidth, sends a BCF message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[5] subclause 7.2.4[2] subclause 7.12[3]
RAS_TE_BND_07Tx BCF message
Ensure that the IUT during a call, on receipt of a valid BRQ message to lower
its allowed bandwidth, sends a BCF message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[5] subclause 7.2.4[2] subclause 7.12[3]
RAS_TE_BND_08Tx BRJ message(rejectReason, insufficient resources, allowed bandwidth)
Ensure that the IUT during a call on receipt of a BRQ message to raise its
allowed bandwidth, when the requested bandwith is not available, sends a BRJ
message with the rejectReason insufficient resources and allowed bandwidth.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[5] subclause 7.2.4[2] subclause 8.4.1 [2] and subclause 7.12[3]]
H225/
RAS/
RAS_TE_URG
RAS_TE_URG_01Tx URQ message
Ensure that the IUT having sent a valid URQ message on receipt of an UCF,
considers to be unregistered.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1.6 subclause 7.2.2[2] subclause 7.10[3]
RAS_TE_URG_02On Rx of UCF, consider unregistered
Ensure that the IUT having sent a valid URQ message on receipt of an UCF,
considers to be unregistered.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1.6 subclause 7.2.2[2] subclause 7.10[3]
RAS_TE_URG_03Tx UCF message Rx URJ
Ensure that the IUT which is not registered, on receipt of a valid URQ message,
sends an URJ with the reason for rejection in the reject reason field as notCurrentlyRegistered
User Action:
Config: A
SUT: Terminal
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1.6 subclause 7.2.2[2] subclause 7.10[3]
RAS_TE_URG_04Not Tx URJ message again and consider unregistered
Ensure that the IUT, when the call is active, on receipt of a valid URQ message,
sends an URJ with the reason for rejection in the reject reason as callInProgress.
User Action:
Config: A
SUT: Terminal
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.2 [2] and 7.10 [3]
RAS_TE_URG_05Tx same URQ message again
Ensure that the IUT having sent a valid URQ message, upon the first expiry of the timer for a URQ message,
re-sends the same URQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1.6 subclause 7.2.2[2] subclause 7.10[3]
RAS_TE_URG_06On Rx of UCF message, consider unregistered
Ensure that the IUT having sent a valid URQ message for the second time, on receipt of an UCF message before the
expiry of the timer for a URQ message,
considers to be unregistered.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1.6 subclause 7.2.2[2] subclause 7.10[3] and subclause 7.19[3]
RAS_TE_URG_07Not Tx same URQ message again
Ensure that the IUT having sent an URQ message for two times, upon the expiry
of the timer for an URQ message, does not re-send the same URQ message again.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.1.6 clauses 7.2.2[2], 7.10[3] and 7.19[3]
H225/
RAS/
RAS_TE_DIS
RAS_TE_DIS_01Tx valid DRQ
Ensure that the IUT having sent a Release Complete message, sends a valid DRQ
message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[7] subclause 7.2.4[2] subclause 8.5[2] and subclause 7.14[3]
RAS_TE_DIS_02Tx valid DRQ message
Ensure that the IUT on receipt of a Release Complete message, sends a valid
DRQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[7] subclause 7.2.4[2] subclause 8.5[2] and subclause 7.14[3]
RAS_TE_DIS_03On Rx of DCF message, consider call terminated
Ensure that the IUT having sent a DRQ message to the Gatekeeper, on receipt of
a DCF message considers the call to be terminated.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[7] subclause 7.2.4[2] subclause 8.5[2] and subclause 7.14[3]
RAS_TE_DIS_04Tx Release complete message
Ensure that the IUT on receipt of a valid DRQ message, sends a Release
complete message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[7] subclause 7.2.4[2] subclause 8.5[2] and subclause 7.14[3]
RAS_TE_DIS_05Tx DCF message
Ensure that the IUT on receipt of a valid DRQ message, sends a DCF.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[7] subclause 7.2.4[2] subclause 8.5[2] and subclause 7.14[3]
RAS_TE_DIS_06On Rx of DRJ from gatekeeper, do not consider call terminated
Ensure that the IUT having sent a valid DRQ, on receipt of a DRJ from the
Gatekeeper, does not consider the call to be terminated.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[7] subclause 7.2.4[2] subclause 8.5[2] and subclause 7.14[3]
RAS_TE_DIS_07Tx same DRQ message
Ensure that the IUT having sent a DRQ message, upon the first expiry of timer
for a DRQ message, re-sends the same DRQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[7] subclause 7.2.4[2] subclause 8.5[2] and subclause 7.19[3]
RAS_TE_DIS_08On Rx of DCF message, consider call terminated
Ensure that the IUT during a call having sent a DRQ message for the second
time, on receipt of a DCF message before the second expiry of timer for a DRQ
message, considers the call to be terminated.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[7] subclause 7.2.4[2] subclause 8.5[2] and subclause 7.19[3]
RAS_TE_DIS_09Not Tx same DRQ message again
Ensure that the IUT during a call having sent a DRQ message for two times,
upon the second expiry of timer for a DRQ message, does not re-send the same
DRQ message again.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[7] subclause 7.2.4[2] subclause 8.5[2] and subclause 7.19[3]
H225/
RAS/
RAS_TE_STA
RAS_TE_STA_01Tx IRR message
Ensure that the IUT after establishing a call, on receipt of a valid IRQ
message with the Call reference value of an active call, sends an IRR message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[8] subclause 8.4.2[2] subclause 7.15[3]
RAS_TE_STA_02Tx IRR message for each call IUT active
Ensure that the IUT on receipt of a valid IRQ message with the Call reference
value as NULL, sends an IRR message for each call the IUT is active.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[8] subclause 8.4.2[2] subclause 7.15[3]
RAS_TE_STA_03Tx IRR message
Ensure that the IUT on receipt of a valid IRQ message when there is no active
call, sends an IRR message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[8] subclause 8.4.2[2] subclause 7.15[3]
RAS_TE_STA_04Tx same IRR message
Ensure that the IUT having sent an IRR message for the first time, upon the
expiry of timer for an IRR message, re-sends the same IRR message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[8] subclause 8.4.2[2] subclause 7.15[3] and subclause 7.19[3]
RAS_TE_STA_05Not Tx same IRR message
Ensure that the IUT having sent an IRR message, on receipt of IACK since the willRespondtoIRR was TRUE in
RCF/ACF message, before the expiry of the timer for an IRR message,
does not re-send the same IRR message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[8] subclause 8.4.2[2] subclause 7.15[3] and subclause 7.19[3]
RAS_TE_STA_06Not Tx same IRR message again
Ensure that the IUT having already sent an IRR message for two times, since
the willRespondtoIRR was TRUE in RCF/ACF message, does not re-send the same
IRR message again.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[8] subclause 8.4.2[2] subclause 7.15[3] and subclause 7.19[3]
RAS_TE_STA_07Not Tx same IRR message
Ensure that the IUT having sent an IRR message to the Gatekeeper, since the willRespondtoIRR was TRUE in
RCF/ACF message, on receipt of an INAK from the Gatekeeper
does not re-send the IRR message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[8] subclause 8.4.2[2] subclause 7.15[3]
H225/
RAS/
RAS_TE_RIP
RAS_TE_RIP_01On Rx of RIP message, restart timer and counter for GRQ message
Ensure that the IUT having sent a valid GRQ message in multicast mode, on receipt of a RIP message
restarts the timer and counter for the GRQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_02Tx GRQ message and restart timer
EEnsure that the IUT having sent a valid GRQ message in multicast mode and then received a RIP message, upon the
expiry of the RIP delay,
re-sends the GRQ message and restarts the timer.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_03On Rx of GCF message, consider GKDiscovery procedure successfull
Ensure that the IUT having sent a valid GRQ message in multicast mode and then received a RIP message, on receipt of
the GCF message before the expiry of the RIP delay,
considers to have completed the GKDiscovery procedure successfully.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_04On Rx of RIP message, restart timer and counter for RRQ message
Ensure that the IUT having sent a valid RRQ message, on receipt of a RIP
message restarts the timer and counter for the RRQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_05Tx RRQ message again and restart timer
Ensure that the IUT having sent a valid RRQ message and then received a RIP message, upon the expiry of the RIP
delay,
re-sends the RRQ message and restarts the timer.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_06On Rx of RCF message, consider Registration procedure successfull
Ensure that the IUT having sent a valid RRQ message and then received a RIP message, on receipt of the RCF message
before the expiry of the RIP delay,
considers to have completed the Registration procedure successfully.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_07On Rx of RIP message, restart timer and counter for ARQ message
Ensure that the IUT having sent a valid ARQ message, on receipt of a RIP
message restarts the timer and counter for the ARQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_08Tx ARQ message and restart timer
Ensure that the IUT having sent a valid ARQ message and then received a RIP
message, upon the expiry of the RIP delay, re-sends the ARQ message and
restarts the timer.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_09Rx ACF message and proceed with call
Ensure that the IUT having sent a valid ARQ message and then received a RIP
message, on receipt of the ACF message before the expiry of the RIP delay,
proceeds with the call.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_10Ensure that the IUT having sent a valid LRQ message, on receipt of a RIP
message restarts the timer and counter for the LRQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_11Tx LRQ message and restart timer
Ensure that the IUT having sent a valid LRQ message and then received a RIP
message, upon the expiry of the RIP delay,
re-sends the LRQ message and restarts the timer.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_12Tx LRQ message RX RIP and TX LCF
Ensure that the IUT having sent a valid LRQ message and then received a RIP message, on receipt of the LCF message
before the expiry of the RIP delay,
proceeds with the call.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_13Rx RIP message, restart timer and counter for BRQ message
Ensure that the IUT having sent a valid BRQ message, on receipt of a RIP
message restarts the timer and counter for the BRQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_14Tx BRQ message and restart timer
Ensure that the IUT having sent a valid BRQ message and then received a RIP message, upon the expiry of the RIP
delay,
re-sends the BRQ message and restarts the timer.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_15Rx BCF message, consider request granted
Ensure that the IUT having sent a valid BRQ message and then received a RIP message, on receipt of the BCF message
before the expiry of the RIP delay,
considers that its request has been granted.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_16Rx RIP message, restart timer and counter
Ensure that the IUT having sent a valid URQ message, on receipt of a RIP
message restarts the timer and counter for the URQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_17Tx URQ message, restart timer
Ensure that the IUT having sent a valid URQ message and then received a RIP message, upon the expiry of the RIP
delay,
re-sends the URQ message and restarts the timer.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_18Rx UCF message, consider unregistered
Ensure that the IUT having sent a valid URQ message and then received a RIP message, on receipt of the UCF message
before the expiry of the RIP delay,
considers to be unregistered.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_19Rx RIP message, restart timer and counter
Ensure that the IUT having sent a valid DRQ message, on receipt of a RIP
message restarts the timer and counter for the DRQ message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_20Tx DRQ message, restart timer
Ensure that the IUT having sent a valid DRQ message and then received a RIP message, upon the expiry of the RIP
delay,
re-sends the DRQ message and restarts the timer.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_21Rx DCF message, terminate call
Ensure that the IUT having sent a valid DRQ message and then received a RIP message, on receipt of the DCF message
before the expiry of the RIP delay,
terminates the call.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_22Rx RIP message, restart timer and counter
Ensure that the IUT having sent a valid IRR message, on receipt of a RIP
message restarts the timer and counter for the IRR message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_23Tx IRR message, restart timer
Ensure that the IUT having sent a valid IRR message and then received a RIP message, upon the expiry of the RIP
delay,
re-sends the IRR message and restarts the timer.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RAS_TE_RIP_24Rx INACK message, proceed with call
Ensure that the IUT having sent a valid IRR message and then received a RIP message, on receipt of the INACK
message before the expiry of the RIP delay,
proceeds with the call.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
H225/
RAS/
RAS_GK_GDR
RAS_GK_GDR_01Tx GCF message
Ensure that the IUT on receipt of a GRQ message in unicast mode, with the
gatekeeper Identifier set to a value other than NULL, when it wants this
endpoint to register with it sends a GCF message.
User Action:
Config: B1
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.1 subclause 7.2.1[2] subclause 7.8[3]
RAS_GK_GDR_02Tx GCF message
Ensure that the IUT on receipt of a GRQ message in multicast mode to the
well-known Discovery Multicast Address and gatekeeperIdentifier missing or set
to NULL, when it wants this endpoint to register with it, sends a GCF message.
User Action:
Config: B1
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.1 subclause 7.2.1[2] subclause 7.8[3]
RAS_GK_GDR_03Tx GRJ message
Ensure that the IUT on receipt of a GRQ message in unicast mode, when it does
not want this endpoint to register with it, sends a GRJ message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.1 subclause 7.2.1[2] subclause 7.8[3]
RAS_GK_GDR_04Rx GRQ message, do not send answer
Ensure that the IUT on receipt of a GRQ message in multicast mode, when it
does not want this endpoint to register with it, sends no answer.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.1 subclause 7.2.1[2] subclause 7.8[3]
RAS_GK_GDR_05Tx GCF message
Ensure that the IUT on receipt of a GRQ message concerning an endpoint having
already discovered it, sends a GCF message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.1 subclause 7.2.1[2] subclause 7.8[3]
RAS_GK_GDR_06Tx GCF message
Ensure that the IUT on receipt of a GRQ message concerning an endpoint having
already registered, sends a GCF message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.1 subclause 7.2.1[2] subclause 7.8[3]
H225/
RAS/
RAS_GK_REG
RAS_GK_REG_01Tx RCF message for registration
Ensure that the IUT on receipt of a RRQ message, when it wants this endpoint
to register with it sends a RCF message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.2 subclause 7.2.2[2] subclause 7.9[3]
RAS_GK_REG_02Tx RRJ for no regristration
Ensure that the IUT on receipt of a RRQ message, when it does not want this
endpoint to register with it, sends a RRJ message
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.2 subclause 7.2.2[2] subclause 7.9[3]
RAS_GK_REG_03Tx RCF message on Rx of RRQ message
Ensure that the IUT on receipt of a RRQ message with the discovery element set to TRUE immediately after
completing GKDiscovery procedure,
sends a RCF message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.2 subclause 7.2.2[2] subclause 7.9[3]
RAS_GK_REG_04Tx RCF without timetoLive value
Ensure that the IUT on receipt of a RRQ message, sends a RCF message without
the timetoLive value indicating that the Gatekeeper does not support KeepAlive
mechanism .
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.2 subclause 7.2.2[2] subclause 7.9[3]
RAS_GK_REG_05Tx RCF(timetoLive)
Ensure that the IUT on receipt of a RRQ message, sends a RCF message with the
timetoLive value indicating that the Gatekeeper supports KeepAlive mechanism
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.2 subclause 7.2.2[2] subclause 7.9[3]
RAS_GK_REG_06Tx RCF message on Rx of RRQ message
Ensure that the IUT on receipt of a RRQ message from the Endpoint which is already registered to this gatekeeper with
the KeepAlive element set to TRUE before the expiry of the timetolive timer,
sends a RCF message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.2 subclause 7.2.2[2] subclause 7.9[3]
RAS_GK_REG_07Tx RRJ(discoveryRequired)
Ensure that the IUT which has not already discovered the Gatekeeper, on
receipt of a RRQ message with the discovery element set to FALSE, sends a RRJ
message with the reason code of discoveryRequired.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.2 subclause 7.2.2[2] subclause 7.9[3]
RAS_GK_REG_08Rx RRQ message, reset time to live timer
Ensure that the IUT, on receipt of a lightweight RRQ message before the
expiration of the time-to live, reset the time to live timer.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.2 subclause 7.2.2[2] subclause 7.9[3]
RAS_GK_REG_09Rx RRQ message, Tx RCF message
Ensure that the IUT, on receipt of a full RRQ message after the expiry of the
timetolive, sends a RCF message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.2 subclause 7.2.2[2] subclause 7.9[3]
RAS_GK_REG_10Tx RRJ(fullRegistrationRequired or discoveryRequired)
Ensure that the IUT on receipt of a lightweight RRQ message after the time-to-live has expired,
sends a RRJ message with the reason code fullRegistrationRequired or discoveryRequired.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.2 subclause 7.2.2[2] subclause 7.9[3]
RAS_GK_REG_11Tx ARJ(callerNotRegistered or CalledPartyNotRegistered)
Ensure that the IUT on receipt of an ARQ message after the time-to-live has
expired, sends an ARJ message with the reject reason callerNotRegistered or
CalledPartyNotRegistered.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.2 subclause 7.2.2[2] subclause 7.9[3]
RAS_GK_REG_12Rx RRQ, Tx RRJ
Ensure that the on receipt of a RRQ message with the alias address of an endpoint which is already registered with a
different transport address,
sends a RRJ message.
User Action:
Config: 2 Links to same Gatekeeper
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.2 subclause 7.2.2[2] subclause 7.9[3]
H225/
RAS/
RAS_GK_ADM
RAS_GK_ADM_01Rx ARQ, Tx ACF
Ensure that the IUT on receipt of a valid ARQ message, concerning an endpoint
registered to it, sends an ACF message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.3 subclause 7.2.4[2] subclause 7.11[3]
RAS_GK_ADM_02Rx ARQ, Tx ARJ
Ensure that the IUT on receipt of a valid ARQ message, concerning an endpoint
that is not registered to it, sends an ARJ message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.3 subclause 7.2.4[2] subclause 7.11[3]
H225/
RAS/
RAS_GK_LOC
RAS_GK_LOC_01Tx LCF(call signalling channel, RAS channel addresses)
Ensure that the IUT on receipt of a valid LRQ message in unicast mode
concerning an endpoint registered to it, sends to the replyAddress a LCF
message including call signalling channel and RAS channel addresses.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.4 subclause 7.2.3[2] subclause 7.13[3]
RAS_GK_LOC_02Tx LCF(call signalling channel, RAS channel addresses)
Ensure that the IUT on receipt of a valid LRQ message in multicast mode
concerning an endpoint registered to it, sends to the replyAddress a LCF
message including call signalling channel and RAS channel addresses.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.4 subclause 7.2.3[2] subclause 7.13[3]
RAS_GK_LOC_03Rx LRQ, Tx LRJ
Ensure that the IUT on receipt of a valid LRQ message in unicast mode with
which the requested endpoint is not registered, sends a LRJ message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.4 subclause 7.2.3[2] subclause 7.13[3]
RAS_GK_LOC_04Rx LRQ, do not send answer
Ensure that the IUT on receipt of a valid LRQ message in multicast mode with
which the requested endpoint is not registered, sends no answer.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.4 subclause 7.2.3[2] subclause 7.13[3]
RAS_GK_LOC_05Rx LCF, consider Location procedure successful
Ensure that the IUT having sent a valid LRQ message, on receipt of a LCF message,
considers to have completed the Location procedure successfully.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.4 subclause 7.2.3[2] subclause 7.13[3]
RAS_GK_LOC_06Tx same LRQ upon expiry of default timer
Ensure that the IUT having sent a LRQ message, upon the first expiry of default timer for a LRQ message,
re-sends the same LRQ message.
Selection: IUT supports LRQ timer, PICS G_TI9
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.4 subclause 7.2.3[2] subclause 7.13[3] and subclause 7.19[3]
RAS_GK_LOC_07Rx LCF, consider Location procedure successful
Ensure that the IUT having sent a LRQ message for the second time, on receipt of LCF message before the second
expiry of timer for a LRQ message, considers to have completed the Location procedure successfully.
Selection: IUT supports LRQ timer, PICS G_TI9
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.4 clauses 7.2.3 [2], 7.13 [3] and 7.19 [3]
RAS_GK_LOC_08Do not Tx same LRQ again
Ensure that the IUT having already sent a LRQ message for two times, upon the second expiry of timer for
a LRQ message, does not re-send the same LRQ message again.
Selection: IUT supports LRQ timer, PICS G_TI9
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.4 clauses 7.2.3 [2], 7.13 [3] and 7.19 [3]
RAS_GK_LOC_09Rx LRJ, do not consider Location procedure successful
Ensure that the IUT having sent a valid LRQ message, on receipt of a LRJ message,
does not consider to have completed the Location procedure successfully.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.4 clauses 7.2.3 [2] and 7.13 [3]
H225/
RAS/
RAS_GK_BND
RAS_GK_BND_01Rx BRQ, Tx BCF
Ensure that the IUT, on receipt of a valid BRQ message to raise the allowed
bandwidth when the request is acceptable, sends a BCF message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.5 clauses 7.2.4 [2], 8.4.1 [2] and 7.12 [3]
RAS_GK_BND_02Rx BRQ, Tx BRJ
Ensure that the IUT on receipt of an valid BRQ message, when the request is
not acceptable sends a BRJ.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.5 clauses 7.2.4 [2], 8.4.1 [2] and 7.12 [3]
RAS_GK_BND_03Rx BCF, consider request granted
Ensure that the IUT having sent a valid BRQ message, on receipt of a BCF
message, considers that its request has been granted.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.5 clauses 7.2.3 [2], 8.4.1 [2] and 7.13 [3]
RAS_GK_BND_04Tx same BRQ upon first expiry of default timer
Ensure that the IUT having sent a BRQ message, upon the first expiry of
default timer for a BRQ message, re-sends the same BRQ message
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.5 clauses 7.2.3 [2], 7.13 [3] and 7.19 [3]
RAS_GK_BND_05Rx BCF, consider request granted
Ensure that the IUT having sent a BRQ message for the second time, on receipt
of BCF message before the second expiry of timer for a BRQ message, considers
that its request has been granted.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.5 clauses 7.2.3 [2], 7.13 [3] and 7.19 [3]
RAS_GK_BND_06Do not Tx same BRQ
Ensure that the IUT having already sent a BRQ message for two times, upon the
second expiry of timer for a BRQ message, does not re-send the same BRQ
message again.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.5 clauses 7.2.3 [2], 7.13 [3] and 7.19 [3]
RAS_GK_BND_07Rx BRJ, consider request rejected
Ensure that the IUT having sent a valid BRQ message, on receipt of a BRJ
message, considers that its request has been rejected.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.5 clauses 7.2.3 [2] and 7.13 [3]
H225/
RAS/
RAS_GK_URG
RAS_GK_URG_01Rx URQ, Tx UCF
Ensure that the IUT on receipt of a valid URQ message, sends an UCF.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.6 clauses 7.2.2 [2] and 7.10 [3]
RAS_GK_URG_02Rx URQ, Tx URJ
Ensure that the IUT on receipt of a URQ message from a Endpoint which is not
registered, sends an URJ.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.6 clauses 7.2.2 [2] and 7.10 [3]
RAS_GK_URG_03Rx URQ, Tx URJ(callInProgress)
Ensure that the IUT on receipt of an URQ message when the call is active,
sends a URJ with the reason for rejection in the reject reason as
callInProgress.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.6 clauses 7.2.2 [2] and 7.10 [3]
RAS_GK_URG_04Rx UCF, consider terminal not registered any more
Ensure that the IUT having sent an URQ message to the Endpoint on receipt of a
UCF message, considers that the terminal is not registered any more.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.6 clauses 7.2.2 [2] and 7.10 [3]
RAS_GK_URG_05Tx same URQ upon first expiry of default timer
Ensure that the IUT having sent a URQ message, upon the first expiry of
default timer for a URQ message, re-sends the same URQ message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.6 clauses 7.2.3 [2], 7.13 [3] and 7.19 [3]
RAS_GK_URG_06Rx UCF, consider terminal not registered any more
Ensure that the IUT having sent a URQ message for the second time, on receipt
of UCF message before the second expiry of timer for a URQ message, considers
that the terminal is not registered any more.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.6 clauses 7.2.3 [2], 7.13 [3] and 7.19 [3]
RAS_GK_URG_07Do not Tx same URQ
Ensure that the IUT having already sent a URQ message for two times, upon the
second expiry of timer for a URQ message, does not re-send the same URQ
message again.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.6 clauses 7.2.3 [2], 7.13 [3] and 7.19 [3]
H225/
RAS/
RAS_GK_DIS
RAS_GK_DIS_01Rx DRQ, Tx DCF
Ensure that the IUT on receipt of a valid DRQ message for an admitted call,
sends a DCF message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.7 clauses 7.2.4 [2] and 7.14 [3]
RAS_GK_DIS_02Rx DRQ, Tx DRJ
Ensure that the IUT on receipt of a valid DRQ message for a terminal, which is
unregistered, sends a DRJ message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.7 clauses 7.2.4 [2] and 7.14 [3]
RAS_GK_DIS_03Rx DCF, terminate call
Ensure that the IUT having sent an DRQ message, on receipt of a DCF message,
terminates the call.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.7 clauses 7.2.4 [2] and 7.14 [3]
RAS_GK_DIS_04Tx same DRQ upon expiry of default timer
Ensure that the IUT having sent a DRQ message, upon the first expiry of
default timer for a DRQ message, re-sends the same DRQ message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.7 clauses 7.2.4 [2] and 7.14 [3]
RAS_GK_DIS_05Rx DCF, terminate call
Ensure that the IUT having sent a DRQ message for the second time, on receipt
of DCF message before the second expiry of timer for a DRQ message, terminates
the call.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.7 clauses 7.2.4 [2] and 7.14 [3]
RAS_GK_DIS_06Do not Tx same DRQ
Ensure that the IUT having already sent a DRQ message for two times, upon the
second expiry of timer for a DRQ message, does not re-send the same DRQ
message again.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.7 clauses 7.2.3 [2], 7.13 [3] and 7.19 [3]
H225/
RAS/
RAS_GK_STA
RAS_GK_STA_01Rx IRR
Ensure that the IUT having sent a valid IRQ message, accepts an IRR message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.8 clauses 8.4.2 [2] and 7.15 [3]
RAS_GK_STA_02Tx IACK(willRespondtoIRR)
Ensure that the IUT on receipt of an unsolicited IRR message with needResponse
field set to TRUE, sends an IACK message depending of the willRespondtoIRR in
RCF/ACF message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.8 clauses 8.4.2 [2] and 7.15 [3]
RAS_GK_STA_03Rx unsolicited IRR, do not send response
Ensure that the IUT on receipt of an unsolicited IRR message with needResponse
field set to FALSE, sends no response.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.8 clauses 8.4.2 [2] and 7.15 [3]
RAS_GK_STA_04Tx INAK(nakreason = notRegistered)
Ensure that the IUT on receipt of an IRR message from a Terminal which is not
registered, sends an INAK with nakReason as notRegistered.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.8 clauses 8.4.2 [2] and 7.15 [3]
H225/
RAS/
RAS_GK_RIP
RAS_GK_RIP_01Rx RIP, restart timer and counter
Ensure that the IUT having sent a valid BRQ message, on receipt of a RIP
message restarts the timer and counter for the BRQ message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.9 clauses 7.2 [2] and 7.19 [3]
RAS_GK_RIP_02Tx BRQ and restart timer
Ensure that the IUT having sent a valid BRQ message and then received a RIP
message, upon the expiry of the RIP delay , re-sends the BRQ message and
restarts the timer.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.9 clauses 7.2 [2] and 7.19 [3]
RAS_GK_RIP_03Rx BCF, proceed with call
Ensure that the IUT having sent a valid BRQ message and then received a RIP
message, on receipt of the BCF message before the expiry of the RIP delay,
proceeds with the call.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.9 clauses 7.2 [2] and 7.19 [3]
RAS_GK_RIP_04Rx RIP, restart timer and counter
Ensure that the IUT having sent a valid URQ message, on receipt of a RIP
message restarts the timer and counter for the URQ message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.9 clauses 7.2 [2] and 7.19 [3]
RAS_GK_RIP_05Tx URQ, restart timer
Ensure that the IUT having sent a valid URQ message and then received a RIP
message, upon the expiry of the RIP delay, re-sends the URQ message and
restarts the timer.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.9 clauses 7.2 [2] and 7.19 [3]
RAS_GK_RIP_06Rx UCF, consider terminal not registered any more
Ensure that the IUT having sent a valid URQ message and then received a RIP
message, on receipt of the UCF message before the expiry of the RIP delay,
considers that the terminal is not registered any more.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.9 clauses 7.2 [2] and 7.19 [3]
RAS_GK_RIP_07Rx RIP, restart timer and counter
Ensure that the IUT having sent a valid DRQ message, on receipt of a RIP
message restarts the timer and counter for the DRQ message.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.9 clauses 7.2 [2] and 7.19 [3]
RAS_GK_RIP_08Tx DRQ, restart timer
Ensure that the IUT having sent a valid DRQ message and then received a RIP
message, upon the expiry of the RIP delay , re-sends the DRQ message and
restarts the timer.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.9 clauses 7.2 [2] and 7.19 [3]
RAS_GK_RIP_09Rx DCF, terminate call
Ensure that the IUT having sent a valid DRQ message and then received a RIP
message, on receipt of the DCF message before the expiry of the RIP delay,
terminates the call.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.1.2.9 clauses 7.2 [2] and 7.19 [3]
H225/
BCC
H225/
BCC/
Endpoint
H225/
BCC/
Endpoint/
PHA
BCC_TE_PHA_01Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP containing
a User-to-user information element including the sourceAddress field with an E.164
type AliasAddress, sends any of a CALL PROCEEDING, ALERTING or CONNECT message and
enters the relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
Note: FastStart only.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_02Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP
containing an User-to-user information element including the sourceAddress
field with a H323-ID type AliasAddress,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
Note: FastStart only.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_03Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP
containing an User-to-user information element including the sourceAddress
field with an URL-ID type AliasAddress,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_04Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP
containing an User-to-user information element including the sourceAddress
field with a transportID type AliasAddress,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_05Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP
containing an User-to-user information element including the sourceAddress
field with an email-ID type AliasAddress,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_06Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP
containing an User-to-user information element including the sourceAddress
field with a partyNumber type AliasAddress,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_07Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP
containing an User-to-user information element including the
destinationAddress field with an E.164 type AliasAddress,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_08Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP
containing an User-to-user information element including the
destinationAddress field with a H323-ID type AliasAddress,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_09Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP
containing an User-to-user information element including the
destinationAddress field with an URL-ID type AliasAddress,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_10Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP
containing an User-to-user information element including the
destinationAddress field with a transportID type AliasAddress,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
Note: FastStart only.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_11Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP
containing an User-to-user information element including the
destinationAddress field with an email-ID type AliasAddress,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_12Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP
containing an User-to-user information element including the
destinationAddress field with a partyNumber type AliasAddress,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_13Tx CALL PROCEEDING, ALERTING, or CONNECT and enter Incoming Call Proceeding U9, Call Recieved U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message
containing the called party number information element including a valid
Numbering plan identification other than 1001,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10.
User Action: Let Terminal ring briefly, test-case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_14Tx SETUP, enter Call Initiated state U1
Ensure that the IUT in the Null call state U0, to establish a call,
sends a SETUP message and enters the Call Initiated call state U1.
User Action: Make a call from the Terminal IUT. Test case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_TE_PHA_15Tx no message, enter Outgoing Call Proceeding state U3
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING, sends no message and enters the Outgoing Call Proceeding call state U3.
Note: FastStart only.
User Action: Make a call from the Terminal IUT. Test case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.3.2 [3]
BCC_TE_PHA_16Tx no message, enter Call delivered call state U4
Ensure that the IUT in the Call Initiated call state U1, on receipt of an
ALERTING message, sends no message and enters the Call delivered call state U4.
Note: FastStart only.
User Action: Make a call from the Terminal IUT. Test case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.3.2 [3]
BCC_TE_PHA_17Tx no message, enter Active call state U10
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
CONNECT message, sends no message and enters the Active call state U10.
Note: FastStart only.
User Action: Make a call from the Terminal IUT. Test case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.3.3 [3]
BCC_TE_PHA_18Tx SETUP, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on the first expiry
of the timer T303, sends a SETUP message and remains in the Call Initiated call state U1.
Note: FastStart only.
User Action: Make a call from the Terminal IUT. Test case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.5 [3]
BCC_TE_PHA_19Tx RELEASE COMPLETE(Cause or User-to-user), enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on the second expiry
of the timer T303, sends a RELEASE COMPLETE message containing either a Cause information element
indicating the cause value 102 "recovery on timer expiry"; or an User-to-user
information element including the reason field indicating why the call was
released and enters the Null call state U0
Note: FastStart only.
User Action: Make a call from the Terminal IUT. Test case will tear down call automatically.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.5 [3]
BCC_TE_PHA_20Tx no message, enter Outgoing Call Proceeding call state U3
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a CALL
PROCEEDING message, sends no message and enters the Outgoing Call Proceeding call state U3.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.3.2 [3]
BCC_TE_PHA_21Tx no message, enter Call Delivered call state U4
Ensure that the IUT in the Overlap Sending call state U2, on receipt of an
ALERTING message, sends no message and enters the Call Delivered call state U4.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.3.1 [3]
BCC_TE_PHA_22Tx no message, enter Active call state U10
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a
CONNECT message, sends no message and enters the Active call state U10.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.3.3 [3]
BCC_TE_PHA_23Tx no message, enter Call delivered call state U4
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a ALERTING message, sends no message and enters the Call delivered call state U4.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.3.1 [3]
BCC_TE_PHA_24Tx no message, enter Active call state U10
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a CONNECT message, sends no message and enters the Active call state U10.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.3.3 [3]
BCC_TE_PHA_25Tx no message, enter Active call state U10
Ensure that the IUT in the Call delivered call state U4, on receipt of a
CONNECT message, sends no message and enters the Active call state U10.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clauses 8.1 [2], clause 7.3.10 [3]
BCC_TE_PHA_26Tx RELEASE COMPLETE(Cause or User-to-user), enter Null call state U0
Ensure that the IUT in the Call Delivered call state U4, on the expiry of the
timer T301, sends a RELEASE COMPLETE message containing either a Cause information element
indicating the cause value 102 "recovery on timer expiry"; or an User-to-user
information element including the reason field indicating why the call was
released and enters the Null call state U0.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 clauses 8.1 [2], clauses 7.5 [3]
BCC_TE_PHA_27Tx STATUS, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
STATUS ENQUIRY message,sends a STATUS message containing a Cause information element indicating the
cause value 30 and Call state information
element indicating the Call Initiated call state and remains in the Call
Initiated call state U1.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 table 4, clauses 7.3.12 and 7.3.13 [3]
BCC_TE_PHA_28Tx STATUS, remain in Overlap Sending call state U2
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a
STATUS ENQUIRY message, sends a STATUS message containing a Cause information element indicating the
cause value 30 and Call state information element
indicating the Overlap Sending Call State and remains in the Overlap Sending
call state U2.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 table 4, clauses 7.3.12 and 7.3.13 [3]
BCC_TE_PHA_29Tx STATUS, remain in Outgoing Call Proceeding state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a STATUS ENQUIRY message, sends a STATUS message containing a Cause information element indicating the
cause value 30 , and a Call State information
element indicating the Outgoing Call Proceeding call state and remains in the
Outgoing Call Proceeding call state U3.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 table 4, clauses 7.3.12 and 7.3.13 [3]
BCC_TE_PHA_30Tx STATUS, remain in Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
STATUS ENQUIRY message, sends a STATUS message containing a Cause information element indicating the
cause value 30 and a Call State information
element indicating the Call Delivered call state and remains in the Call
Delivered call state U4.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 table 4, clauses 7.3.12 and 7.3.13 [3]
BCC_TE_PHA_31Tx STATUS, remain in Call Received call state U7
Ensure that the IUT in the Call Received call state U7, on receipt of a STATUS
ENQUIRY message, sends a STATUS message containing a Cause information element indicating the
cause value 30 and a Call state information
element indicating the Call Received call state and remains in the Call
Received call state U7.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 table 4, clauses 7.3.12 and 7.3.13 [3]
BCC_TE_PHA_32Tx STATUS, remain in Active Call state U10
Ensure that the IUT in the Active Call State U10, on receipt of a STATUS
ENQUIRY message, sends a STATUS message containing a Cause information element indicating the
cause value 30 and a Call State information
element indicating tha Active call state and remains in the Active Call state
U10.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.1 table 4, clauses 7.3.12 and 7.3.13 [3]
H225/
BCC/
Endpoint/
PHE
BCC_TE_PHE_01Close call signalling channel, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE
COMPLETE message, closes call signalling channel and enters the Null call state U0.
Note: FastStart only.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.2 clauses 8.5 [2] and 7.1 [3]
BCC_TE_PHE_02Tx RELEASE COMPLETE, close call signalling channel, enter Null call state U0
Ensure that the IUT in the Active call state U10, to release the call;
sends a RELEASE COMPLETE message, closes call signalling channel and enters
the Null call state U0.
Note: FastStart only.
User Action: Off-hook phone when it rings. On-hook phone when asked.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.2 clauses 8.5 [2] and 7.1 [3]
H225/
BCC/
Endpoint/
Inopportune
H225/
BCC/
Endpoint/
Inopportune/
U0
BCC_TE_I_U00_01Tx STATUS, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a message
containing an unknown message type information element,
sends a STATUS message and remains in the Null call state U0.
Note: FastStart only.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.1 clause 5.8.4 [4]
BCC_TE_I_U00_02Tx STATUS, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a RESUME message
(out of context of the base specification), sends a STATUS message and remains in the Null call state U0.
Note: FastStart only.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.1 table 4 [3] and clause 5.8.4 [4]
BCC_TE_I_U00_03Tx STATUS, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a STATUS ENQUIRY
message, sends a STATUS message containing a Cause information element indicating the
cause value 30 and a Call State information
element indicating the Null call state and remains in the Null call state U0.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.1 clauses 5.8.3.2 h) and 5.8.10 [4]
BCC_TE_I_U00_04Tx RELEASE COMPLETE, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a STATUS message
containing a Call state information element indicating a call state other than
the Null call state, sends a RELEASE COMPLETE message containing a Cause information element
indicating the cause value 101 and
remains in the Null call state U0.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.1 clauses 5.8.3.2 g) and 5.8.11 [4]
BCC_TE_I_U00_05Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a STATUS message
containing a Call state information element indicating the Null call state,
sends no message and remains in the Null call state U0.
Note: FastStart only.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.1 clauses 5.8.3.2 g) and 5.8.11 [4]
H225/
BCC/
Endpoint/
Inopportune/
U1
BCC_TE_I_U01_01Close call signalling channel, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
RELEASE COMPLETE message closes call signalling channel and enters the Null
call state U0.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.2 clause 5.8.4 [4]
BCC_TE_I_U01_02Close call signalling channel, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
STATUS message containing a Call state information element indicating the Null
call state, closes call signalling channel and enters the Null call state U0.
Note: FastStart only.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.2 clause 5.8.11 [4]
BCC_TE_I_U01_03Tx STATUS, remain in Call Initiated state U1
Ensure that the IUT in the Call Initiated state U1, on receipt of a message
containing an unknown message type information element,
sends a STATUS message and remains in the Call Initiated state U1.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.2 clause 5.8.4 [4]
BCC_TE_I_U01_04Tx STATUS, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
RELEASE message (out of the contexte of the base specification),
sends a STATUS message and remains in the Call Initiated call state U1.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.2 table 4 [3] and clause 5.8.4 [4]
H225/
BCC/
Endpoint/
Inopportune/
U2
BCC_TE_I_U02_01Close call signalling channel, enter Null call state U0
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a
RELEASE COMPLETE message, closes call signalling channel and enters the Null call state U0.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.3 clause 5.8.4 [4]
BCC_TE_I_U02_02Close call signalling channel, enter Null call state U0
Ensure that the IUT in theOverlap Sending call state U2, on receipt of a
STATUS message containing a Call state information element indicating the Null
call state, closes call signalling channel and enters the Null call state U0.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.3 clause 5.8.11 [4]
BCC_TE_I_U02_03Tx STATUS, remain in Overlap Sending call state U2
Ensure that the IUT in the Overlap Sending state U2, on receipt of a message
containing an unknown message type information element,
sends a STATUS message and remains in the Overlap Sending call state U2.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.3 clause 5.8.4 [4]
BCC_TE_I_U02_04Tx STATUS, remain in Overlap Sending call state U2
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a
RELEASE message (out of the contexte of the base specification),
sends a STATUS message and remains in the Overlap Sending call state U2.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.3 table 4 [3] and clause 5.8.4 [4]
H225/
BCC/
Endpoint/
Inopportune/
U3
BCC_TE_I_U03_01Close call signalling channel, enter Null call state U0
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a RELEASE COMPLETE message, closes call signalling channel and enters the
Null call state U0.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.4 clause 5.8.4 [4]
BCC_TE_I_U03_02Close call signalling channel, enter Null call state U0
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a STATUS message containing a Call state information element indicating the
Null call state, closes call signalling channel and enters the Null call state
U0.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.4 clause 5.8.11 [4]
BCC_TE_I_U03_03Tx STATUS, remain in Outgoing Call Proceeding call state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a message containing an unknown message type information element,
sends a STATUS message and remains in the Outgoing Call Proceeding call state U3.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.4 clause 5.8.4 [4]
BCC_TE_I_U03_04Tx STATUS, remain in Outgoing Call Proceeding call state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a DISCONNECT message (out of the contexte of the base specification),
sends a STATUS message and remains in the Outgoing Call Proceeding call state U3.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.4 table 4 [3] and clause 5.8.4 [4]
H225/
BCC/
Endpoint/
Inopportune/
U4
BCC_TE_I_U04_01Close call signalling channel, enter Null call state U0
Ensure that the IUT in the Call delivered call state U4, on receipt of a
RELEASE COMPLETE message, closes call signalling channel and enters the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.5 clause 5.8.4 [4]
BCC_TE_I_U04_02Close call signalling channel, enter Null call state U0
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
STATUS message containing a Call state information element indicating the Null
call state, closes call signalling channel and enters the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.5 clause 5.8.11 [5]
BCC_TE_I_U04_03Tx STATUS, remain in Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
message containing an unknown message type information element,
sends a STATUS message and remains in the Call Delivered call state U4.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.5 clause 5.8.4 [4]
BCC_TE_I_U04_04Tx STATUS, remain in Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
DISCONNECT message (out of the contexte of the base specification),
sends a STATUS message and remains in the Call Delivered call state U4.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.5 table 4 [3] and clause 5.8.4 [4]
H225/
BCC/
Endpoint/
Inopportune/
U7
BCC_TE_I_U07_01Close call signalling channel, enter Null call state U0
Ensure that the IUT in the Call Received call state U7, on receipt of a
RELEASE COMPLETE message, closes call signalling channel and enters the Null
call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.6 clause 5.8.4 [4]
BCC_TE_I_U07_02Close call signalling channel, enter Null call state U0
Ensure that the IUT in the Call Received call state U7, on receipt of a
STATUS message containing a Call state information element indicating the Null
call state, closes call signalling channel and enters the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.6 clause 5.8.11 [4]
BCC_TE_I_U07_03Tx STATUS, remain in Call Received state state U7
Ensure that the IUT in the Call Received call state U7, on receipt of a
message containing an unknown message type information element,
sends a STATUS message and remains in the Call Received call state U7.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.6 clause 5.8.4 [4]
BCC_TE_I_U07_04Tx STATUS, remain in Call Received call state U7
Ensure that the IUT in the Call Received call state U7, on receipt of a RELEASE message (out of the context of the
base specification),
sends a STATUS message and remains in the Call Received call state U7.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.6 table 4 [3] and clause 5.8.4 [4]
H225/
BCC/
Endpoint/
Inopportune/
U10
BCC_TE_I_U10_01Close call signalling channel, enter Null call state U0
Ensure that the IUT in the Active Call call state U10, on receipt of a STATUS
message containing a Call state information element indicating the Null call
state, closes call signalling channel and enters the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.7 clause 5.8.4 [4]
BCC_TE_I_U10_02Tx STATUS, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a message
containing an unknown message type information element,
sends a STATUS message and remains in the Active call state U10.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.7 clause 5.8.4 [4]
BCC_TE_I_U10_03Tx STATUS, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a CONNECT
ACKNOWLEDGE message (out of the contexte of the base specification),
sends a STATUS message and remains in the Active call state U10.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.3.7 table 4 [3] and clause 5.8.4 [4]
H225/
BCC/
Endpoint/
SyntacticallyInvalid
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U00
BCC_TE_S_U00_01Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message
containing an erroneous protocol discriminator information element, coded
other than 08, sends no message and remains in the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.1 clause 5.8.1 [4]
BCC_TE_S_U00_02Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a message which
is too short to contain a complete message type information element,
sends no message and remains in the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.1 clause 5.8.2 [4]
BCC_TE_S_U00_03Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message
containing an invalid call reference information element format (octet 1, bits
8 - 5 != 0000), sends no message and remains in the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.1 clause 5.8.3.1 [4]
BCC_TE_S_U00_04Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message
containing an invalid call reference information element format (octet 1, bits
1 to 4, length too high), sends no message and remains in the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.1 clause 5.8.3.1 [4]
BCC_TE_S_U00_05Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message
containing the dummy call reference, sends no message and remains in the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.1 clause 5.8.3.1 [4]
BCC_TE_S_U00_06Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message
containing a call reference flag bit set to 1, sends no message and remains in
the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.1 clause 5.8.3.2 d) [4]
BCC_TE_S_U00_07Tx RELEASE COMPLETE, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message
with a mandatory information element missing, sends a RELEASE COMPLETE message
containing a Cause information element indicating the cause value 96
information element missing> and remains in the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.1 clause 5.8.6.1 [4]
BCC_TE_S_U00_08Tx RELEASE COMPLETE, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message
containing a mandatory information element with content error,
sends a RELEASE COMPLETE message containing a Cause information element
indicating the cause value 100 and
remains in the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.1 clause 5.8.6.2 [4]
BCC_TE_S_U00_09Tx CALL PROCEEDING, ALERTING, or CONNECT, enter Incoming Call Proceeding U9, Call Received U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message
containing an information element, which is not within the context of the base
specification, sends any of a CALL PROCEEDING, ALERTING or CONNECT message and
enters the relevant call state Incoming Call Proceeding U9, Call Received U7
or Active call state U10
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.1 clause 5.8.7.1 [4]
BCC_TE_S_U00_10Tx CALL PROCEEDING, ALERTING, or CONNECT, enter Incoming Call Proceeding U9, Call Received U7, or Active call state U10
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message
containing a non-mandatory information element with content error,
sends any of a CALL PROCEEDING, ALERTING or CONNECT message and enters the
relevant call state Incoming Call Proceeding U9, Call Received U7 or Active
call state U10
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.1 clause 5.8.7.2 [4]
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U01
BCC_TE_S_U01_01Tx no message, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a SETUP ACKNOWLEDGE message containing an
erroneous protocol discriminator information element, coded other than `08`H,
sends no message and remains in the Call Initiated call state U1.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.1 [4]
BCC_TE_S_U01_02Tx no message, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
message which is too short to contain a complete message type information
element, sends no message and remains in the Call Initiated call state U1.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.2 [4]
BCC_TE_S_U01_03Tx no message, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message containing an invalid call reference information element
format (octet 1, bits 8 - 5 != 000), sends no message and remains in the
Call Initiated call state U1.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.3.1 [4]
BCC_TE_S_U01_04Tx no message, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of an
ALERTING message containing an invalid call reference information element
format (octet 1, bits 1 to 4, length too high), sends no message and remains
in the Call Initiated call state U1.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.3.1 [4]
BCC_TE_S_U01_05Tx no message, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message containing the dummy call reference, sends no message and
remains in the Call Initiated call state U1.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.3.1 [4]
BCC_TE_S_U01_06Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a SETUP
ACKNOWLEDGE message with a mandatory information element missing, sends a
RELEASE COMPLETE message containing a Cause information element indicating the
cause value 96 and enters the Null
call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.6.1 [4]
BCC_TE_S_U01_07Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message with a mandatory information element missing, sends a
RELEASE COMPLETE message containing a Cause information element indicating the
cause value 96 and enters the Null
call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.6.1 [4]
BCC_TE_S_U01_08Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
ALERTING message with a mandatory information element missing, sends a RELEASE
COMPLETE message containing a Cause information element indicating the cause
value 96 and enters the Null call
state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.6.1 [4]
BCC_TE_S_U01_09Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a SETUP
ACKNOWLEDGE message containing a mandatory information element with content
error, sends a RELEASE COMPLETE message containing a Cause information element
indicating the cause value 100 and enters the
Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.6.2 [4]
BCC_TE_S_U01_10Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message containing a mandatory information element with content
error, sends a RELEASE COMPLETE message containing a Cause information element
indicating the cause value 100 and enters the
Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.6.2 [4]
BCC_TE_S_U01_11Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of an
ALERTING message containing a mandatory information element with content
error, sends a RELEASE COMPLETE message containing a Cause information element
indicating the cause value 100 and enters the
Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.6.2 [4]
BCC_TE_S_U01_12Tx no message, enter Overlap Sending state U2
Ensure that the IUT in the Call Initiated call state U1, on receipt of a SETUP
ACKNOWLEDGE message containing a information element which is not within the
context of the base specification, sends no message and enters the Overlap
Sending state U2.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.7.1 [4]
BCC_TE_S_U01_13Tx no message, enter Outgoing Call Proceeding state U3
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message containing a information element which is not within the
context of the base specification, sends no message and enters the Outgoing
Call Proceeding state U3.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.7.1 [4]
BCC_TE_S_U01_14Tx no message, enter Call Delivered state U4
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
ALERTING message containing a information element which is not within the
context of the base specification, sends no message and enters the Call
Delivered state U4.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.7.1 [4]
BCC_TE_S_U01_15Tx no message, enter Overlap Sending state U2
Ensure that the IUT in the Call Initiated call state U1, on receipt of a SETUP
ACKNOWLEDGE message containing a non-mandatory information element with
content error, sends no message and enters the Overlap Sending state U2.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.7.2 [4]
BCC_TE_S_U01_16Tx no message, enter Outgoing Call Proceeding state U3
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message containing a non-mandatory information element with content
error, sends no message and enters the Outgoing Call Proceeding state U3.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.7.2 [4]
BCC_TE_S_U01_17Tx no message, enter Call Delivered state U4
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
ALERTING message containing a non-mandatory information element with content
error, sends no message and enters the Call Delivered state U4.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.2 clause 5.8.7.2 [4]
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U02
BCC_TE_S_U02_01Tx no message, remain in Overlap Sending call state U2
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a CALL
PROCEEDING message containing an erroneous protocol discriminator information
element, coded other than 08, sends no message and remains in the Overlap
Sending call state U2.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.1 [4]
BCC_TE_S_U02_02Tx no message, remain in Overlap Sending call state U2
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a
message which is too short to contain a complete message type information
element, sends no message and remains in the Overlap Sending call state U2.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.2 [4]
BCC_TE_S_U02_03Tx no message, remain in Overlap Sending call state U2
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a
ALERTING message containing an invalid call reference information element
format (octet 1, bits 8 - 5 != ’0000’B), sends no message and remains in
the Overlap Sending call state U2.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.3.1 [4]
BCC_TE_S_U02_04Tx no message, remain in Overlap Sending call state U2
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a CALL
PROCEEDING message containing an invalid call reference information element
format (octet 1, bits 1 to 4, length too high), sends no message and remains
in the Overlap Sending call state U2.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.3.1 [4]
BCC_TE_S_U02_05Tx no message, remain in Overlap Sending call state U2
Ensure that the IUT in the Overlap Sending call state U2, on receipt of an
ALERTING message containing the dummy call reference, sends no message and
remains in the Overlap Sending call state U2.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.3.1 [4]
BCC_TE_S_U02_06Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a CALL
PROCEEDING message with a mandatory information element missing, sends a
RELEASE COMPLETE message containing either a Cause information element
indicating the cause value 96 and
enters the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.6.1 [4]
BCC_TE_S_U02_07Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Overlap Sending call state U2, on receipt of an
ALERTING message with a mandatory information element missing, sends a RELEASE
COMPLETE message containing a Cause information element indicating the cause
value 96 and enters the Null call
state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.6.1 [4]
BCC_TE_S_U02_08Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a CALL
PROCEEDING message containing a mandatory information element with content
error, sends a RELEASE COMPLETE message containing a Cause information element
indicating the cause value 100 and enters the
Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.6.2 [4]
BCC_TE_S_U02_09Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Overlap Sending call state U2, on receipt of an
ALERTING message containing a mandatory information element with content
error, sends a RELEASE COMPLETE message containing a Cause information element
indicating the cause value 100 and enters the
Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.6.2 [4]
BCC_TE_S_U02_10Tx no message, enter Outgoing Call Proceeding call state U3
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a CALL
PROCEEDING message containing an information element, which is not within the
context of the base specification, sends no message and enters the Outgoing
Call Proceeding call state U3.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.7.1 [4]
BCC_TE_S_U02_11Tx no message, enter Call Delivered call state U4
Ensure that the IUT in the Overlap Sending call state U2, on receipt of an
ALERTING message containing an information element, which is not within the
context of the base specification, sends no message and enters the Call
Delivered call state U4.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.7.1 [4]
BCC_TE_S_U02_12Tx no message, enter Outgoing Call Proceeding call state U3
Ensure that the IUT in the Overlap Sending call state U2, on receipt of a CALL
PROCEEDING message containing a non-mandatory information element with content
error,sends no message and enters the Outgoing Call Proceeding call state U3.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.7.2 [4]
BCC_TE_S_U02_13Tx no message, enter Call Delivered call state U4
Ensure that the IUT in the Overlap Sending call state U2, on receipt of an
ALERTING message containing a non-mandatory information element with content
error, sends no message and enters the Call Delivered call state U4.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.3 clause 5.8.7.2 [4]
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U03
BCC_TE_S_U03_01Tx no message, remain Outgoing Call Proceeding call state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a ALERTING message containing an erroneous protocol discriminator
information element, coded other than’08’H, sends no message and remains in
the Outgoing Call Proceeding call state U3.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.4 clause 5.8.1 [4]
BCC_TE_S_U03_02Tx no message, remain in Outgoing Call Proceeding call state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a message which is too short to contain a complete message type information
element, sends no message and remains in the Outgoing Call Proceeding call state U3.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.4 clause 5.8.2 [4]
BCC_TE_S_U03_03Tx no message, remain in Outgoing Call Proceeding call state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of an ALERTING message containing an invalid call reference information
element format (octet 1, bits 8 - 5 != ’0000’B), sends no message and remains
in theOutgoing Call Proceeding call state U3.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.4 clause 5.8.3.1 [4]
BCC_TE_S_U03_04Tx no message, remain in Outgoing Call Proceeding call state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of an ALERTING message containing an invalid call reference information
element format (octet 1, bits 1 to 4, length too high), sends no message and
remains in the Outgoing Call Proceeding call state U3.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.4 clause 5.8.3.1 [4]
BCC_TE_S_U03_05Tx no message, remain in Outgoing Call Proceeding call state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of an ALERTING message containing the dummy call reference, sends no message
and remains in the Outgoing Call Proceeding call state U3.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.4 clause 5.8.3.1 [4]
BCC_TE_S_U03_06Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of an ALERTING message with a mandatory information element missing, sends a
RELEASE COMPLETE message containing a Cause information element indicating the
cause value 96 and enters the Null
call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.4 clause 5.8.6.1 [4]
BCC_TE_S_U03_07Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of an ALERTING containing a mandatory information element with content error,
sends a RELEASE COMPLETE message containing a Cause information element
indicating the cause value 100 and enters the
Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.4 clause 5.8.6.2 [4]
BCC_TE_S_U03_08Tx no message, enter Call Delivered call state U4
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of an ALERTING message containing an information element, which is not within
the context of the base specification, sends no message and enters the Call
Delivered call state U4.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.4 clause 5.8.7.1 [4]
BCC_TE_S_U03_09Tx no message, enter Call Delivered call state U4
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of an ALERTING message containing a non-mandatory information element with
content error, sends no message and enters the Call Delivered call state U4.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.4 clause 5.8.7.2 [4]
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U04
BCC_TE_S_U04_01Tx no message, remain in Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
CONNECT message containing an erroneous protocol discriminator information
element, coded other than 08, sends no message and remains in the Call
Delivered call state U4.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.5 clause 5.8.1 [4]
BCC_TE_S_U04_02Tx no message, remain in Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
message which is too short to contain a complete message type information
element, sends no message and remains in the Call Delivered call state U4.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.5 clause 5.8.2 [4]
BCC_TE_S_U04_03Tx no message, remain in Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
CONNECT message containing an invalid call reference information element
format (octet 1, bits 8 - 5 != ’0000’B), sends no message and remains in
the Call Delivered call state U4.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.5 clause 5.8.3.1 [4]
BCC_TE_S_U04_04Tx no message, remain in Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
CONNECT message containing an invalid call reference information element
format (octet 1, bits 1 to 4, length too high), sends no message and
remains in the Call Delivered call state U4.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.5 clause 5.8.3.1 [4]
BCC_TE_S_U04_05Tx no message, remain in Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
CONNECT message containing the dummy call reference, sends no message and
remains in the Call Delivered call state U4.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.5 clause 5.8.3.1 [4]
BCC_TE_S_U04_06Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
CONNECT message with a mandatory information element missing, sends a RELEASE
COMPLETE message containing a Cause information element indicating the cause
value 96 and enters the Null call
state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.5 clause 5.8.6.1 [4]
BCC_TE_S_U04_07Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
CONNECT message containing a mandatory information element with content error,
sends a RELEASE COMPLETE message with a Cause information element indicating
the cause value 100 and enters the Null call
state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.5 clause 5.8.6.2 [4]
BCC_TE_S_U04_08Tx no message, enter Active call state U10
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
CONNECT message containing an information element, which is not within the
context of the base specification, sends no message and enters the Active call state U10.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.5 clause 5.8.7.1 [4]
BCC_TE_S_U04_09Tx no message, enter Active call state U10
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
CONNECT message containing a non-mandatory information element with content
error, sends no message and enters the Active call state U10.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.5 clause 5.8.7.2 [4]
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U07
BCC_TE_S_U07_01Tx no message, remain in Call Received call state U7
Ensure that the IUT in the Call Received call state U7, on receipt of a
RELEASE COMPLETE message containing an erroneous protocol discriminator
information element, coded other than ’08’H, sends no message and remains
in the Call Received call state U7.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.6 clause 5.8.1 [4]
BCC_TE_S_U07_02Tx no message, remain in Call Received call state U7
Ensure that the IUT in the Call Received call state U7, on receipt of a
message which is too short to contain a complete message type information
element, sends no message and remains in the Call Received call state U7.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.6 clause 5.8.2 [4]
BCC_TE_S_U07_03Tx no message, remain in Call Received call state U7
Ensure that the IUT in the Call Received call state U7, on receipt of a
RELEASE COMPLETE message containing an invalid call reference information
element format (octet 1, bits 8 - 5 != ’0000’B), sends no message and remains
in the Call Received call state U7.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.6 clause 5.8.3.1 [4]
BCC_TE_S_U07_04Tx no message, remain in Call Received call state U7
Ensure that the IUT in the Call Received call state U7, on receipt of a
RELEASE COMPLETE message containing an invalid call reference information
element format (octet 1, bits 1 to 4, length too high),
sends no message and remains in the Call Received call state U7.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.6 clause 5.8.3.1 [4]
BCC_TE_S_U07_05Tx no message, remain in Call Received call state U7
Ensure that the IUT in the Call Received call state U7, on receipt of a
RELEASE COMPLETE message containing the dummy call reference, sends no message
and remains in the Call Received call state U7.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.6 clause 5.8.3.1 [4]
BCC_TE_S_U07_06Tx no message, enter Null call state U0
Ensure that the IUT in the Call Received call state U7, on receipt of a
RELEASE COMPLETE message with a mandatory information element missing, sends
no message and enters the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.6 clause 5.8.6.1 [4]
BCC_TE_S_U07_07Tx no message, enter Null call state U0
Ensure that the IUT in the Call Received call state U7, on receipt of a
RELEASE COMPLETE message containing a mandatory information element with
content error, sends no message and enters the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.6 clause 5.8.6.2 [4]
BCC_TE_S_U07_08Tx no message, enter Null call state U0
Ensure that the IUT in the Call Received call state U7, on receipt of a
RELEASE COMPLETE message containing a information element which is not within
the context of the base specification, sends no message and enters the Null
call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.6 clause 5.8.7.1 [4]
BCC_TE_S_U07_09Tx no message, enter Null call state U0
Ensure that the IUT in the Call Received call state U7, on receipt of a
RELEASE COMPLETE message containing a non-mandatory information element with
content error, sends no message and enters the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.6 clause 5.8.7.2 [4]
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U10
BCC_TE_S_U10_01Tx no message, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE
COMPLETE message containing an erroneous protocol discriminator information
element, coded other than ’08’H, sends no message and remains in the Active
call state U10.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.7 clause 5.8.1 [4]
BCC_TE_S_U10_02Tx no message, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a message
which is too short to contain a complete message type information element,
sends no message and remains in the Active call state U10.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.7 clause 5.8.2 [4]
BCC_TE_S_U10_03Tx no message, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE
COMPLETE message containing an invalid call reference information element
format (octet 1, bits 8 - 5 != 0000), sends no message and remains in
the Active call state U10.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.7 clause 5.8.3.1 [4]
BCC_TE_S_U10_04Tx no message, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE
COMPLETE message containing an invalid call reference information element
format (octet 1, bits 4 to 1, length too high), sends no message and remains
in the Active call state U10.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.7 clause 5.8.3.1 [4]
BCC_TE_S_U10_05Tx no message, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE
COMPLETE message containing the dummy call reference, sends no message and
remains in the Active call state U10.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 5.2.2.1.4.7 clause 5.8.3.1 [4]
BCC_TE_S_U10_06Tx no message, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE
COMPLETE message with a mandatory information element missing,
sends no message and enters the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.7 clause 5.8.6.1 [4]
BCC_TE_S_U10_07Tx no message, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE
COMPLETE message containing a mandatory information element with content
error, sends no message and enters the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.7 clause 5.8.6.2 [4]
BCC_TE_S_U10_08Tx no message, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE
COMPLETE message containing a information element which is not within the
context of the base specification, sends no message and enters the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.7 clause 5.8.7.1 [4]
BCC_TE_S_U10_09Tx no message, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE
COMPLETE message containing a non-mandatory information element with content
error, sends no message and enters the Null call state U0.
Note: FastStart only.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.1.4.7 clause 5.8.7.2 [4]
H225/
BCC/
Gatekeeper
H225/
BCC/
Gatekeeper/
BCC_GK_PHA
BCC_GK_PHA_01Tx CALL PROCEEDING, enter Incoming Call Proceeding call state U9, Tx SETUP, enter Call Initiated call state U1
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message,
from the calling endpoint, containing an User-to-user information element
including the destinationAddress field with an E.164 type AliasAddress,
sends a CALL PROCEEDING message and enters the Incoming Call Proceeding call
state U9 in the interface with the calling endpoint and
sends a SETUP message, to the Destination Gatekeeper and enters the Call
Initiated call state U1 in the interface with the destination Gatekeeper.
User Action: Make a call from the Terminal IUT.
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 clause 8.1 [2], clauses 7.1 and 7.3.10 [3]
BCC_GK_PHA_02Tx CALL PROCEEDING, enter Incoming Call Proceeding call state U9, Tx SETUP, enter Call Initiated call state U1
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message,
from the calling endpoint, containing an User-to-user information element
including the destinationAddress field with an H323-ID type AliasAddress,
sends a CALL PROCEEDING message and enters the Incoming Call Proceeding call
state U9 in the interface with the calling endpoint and
sends a SETUP message, to the Destination Gatekeeper and enters the Call
Initiated call state U1 in the interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 clause 8.1 [2], clauses 7.1 and 7.3.10 [3]
BCC_GK_PHA_03Tx CALL PROCEEDING, enter Incoming Call Proceeding call state U9, Tx SETUP, enter Call Initiated call state U1
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message,
from the calling endpoint, containing an User-to-user information element
including the destinationAddress field with an URL-ID type AliasAddress,
sends a CALL PROCEEDING message and enters the Incoming Call Proceeding call
state U9 in the interface with the calling endpoint and
sends a SETUP message, to the Destination Gatekeeper and enters the Call
Initiated call state U1 in the interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 clause 8.1 [2], clauses 7.1 and 7.3.10 [3]
BCC_GK_PHA_04Tx CALL PROCEEDING, enter Incoming Call Proceeding call state U9, Tx SETUP, enter Call Initiated call state U1
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message,
from the calling endpoint, containing an User-to-user information element
including the destinationAddress field with an tranportID type AliasAddress,
sends a CALL PROCEEDING message and enters the Incoming Call Proceeding call
state U9 in the interface with the calling endpoint and
sends a SETUP message, to the Destination Gatekeeper and enters the Call
Initiated call state U1 in the interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 clause 8.1 [2], clauses 7.1 and 7.3.10 [3]
BCC_GK_PHA_05Tx CALL PROCEEDING, enter Incoming Call Proceeding call state U9, Tx SETUP, enter Call Initiated call state U1
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message,
from the calling endpoint, containing an User-to-user information element
including the destinationAddress field with an email-ID type AliasAddress,
sends a CALL PROCEEDING message and enters the Incoming Call Proceeding call
state U9 in the interface with the calling endpoint and
sends a SETUP message, to the Destination Gatekeeper and enters the Call
Initiated call state U1 in the interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 clause 8.1 [2], clauses 7.1 and 7.3.10 [3]
BCC_GK_PHA_06Tx CALL PROCEEDING, enter Incoming Call Proceeding call state U9, Tx SETUP, enter Call Initiated call state U1
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message,
from the calling endpoint, containing an User-to-user information element
including the destinationAddress field with an partyNumber type AliasAddress,
sends a CALL PROCEEDING message and enters the Incoming Call Proceeding call
state U9 in the interface with the calling endpoint and
sends a SETUP message, to the Destination Gatekeepe and enters the Call
Initiated call state U1 in the interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 clause 8.1 [2], clauses 7.1 and 7.3.10 [3]
BCC_GK_PHA_07Tx CALL PROCEEDING, enter Incoming Call Proceeding call state U9, Tx SETUP, enter Call Initiated call state U1
Ensure that the IUT in the Null call state U0, from the calling endpoint,
containing the called party number information element including a valid
Numbering plan identification other than ’1001’,
sends a CALL PROCEEDING message and enters the Incoming Call Proceeding call
state U9 in the interface with the calling endpoint and
sends a SETUP message, to the Destination Gatekeeper and enters the Call
Initiated call state U1 in the interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 clause 8.1 [2], clauses 7.1 and 7.3.10 [3]
BCC_GK_PHA_08Tx no message, remain in Incoming Call Proceeding call state U9, Tx no message, enter Outgoing Call Proceeding call state U3
Ensure that the IUT in the Call Initiated call state U9, on receipt of a CALL
PROCEEDING message from the destination Gatekeeper,
sends no message and remains in the Incoming Call Proceeding call state U9 in
the interface with the calling endpoint
and sends no message and enters the Outgoing Call Proceeding call state U3 in the
interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 clauses 8.1 [2] and 7.3.2 [3]
BCC_GK_PHA_09enter Call Delivered call state U4, Tx ALERTING, enter Call Received call state U7
Ensure that the IUT in the Outgoing Call Proceeding call state U9, on receipt
of an ALERTING message from the destination Gatekeeper,
enters the Call Delivered call state U4 in the interface with the destination
Gatekeeper and sends an ALERTING message to the calling endpoint and enters the Call Received
call state U7 in the interface with the calling endpoint.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 clauses 8.1 [2] and 7.3.1 [3]
BCC_GK_PHA_10enter Active call state U10, Tx CONNECT, enter Active call state U10
Ensure that the IUT in the Outgoing Call Proceeding call state U7, on receipt
of a CONNECT message from the destination Gatekeeper,
enters the Active call state U10 in the interface with the destination
Gatekeeper and sends a CONNECT message to the calling endpoint and enters the Active call
state U10 in the interface with the calling endpoint.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 clauses 8.1 [2] and 7.3.3 [3]
BCC_GK_PHA_11Tx no message, enter Active call state U10, Tx CONNECT, enter Active call state U10, Tx CONNECT, enter Active call state U10
Ensure that the IUT in the Call Delivered call state U9, on receipt of a
CONNECT message, from the destination Gatekeeper,
sends no message and enters the Active call state U10 in the interface with
the destination Gatekeeper
and sends a CONNECT message to the calling endpoint and enters the Active call
state U10 in the interface with the calling endpoint.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 clauses 8.1 [2] and 7.3.3 [3]
BCC_GK_PHA_12Tx STATUS, remain in Call Proceeding call state U9
Ensure that the IUT in the Call Proceeding call state U9, on receipt of a
STATUS ENQUIRY message from the calling endpoint,
sends a STATUS message containing a Cause information element indicating the
cause value 30 "response to STATUS ENQUIRY" and a Call state information
element indicating the Call Proceeding call state and remains in the Call
Proceeding call state U9.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 table 4, clauses 7.3.12 and 7.3.13 [3]
BCC_GK_PHA_13Tx STATUS, remain in Call Received call state U7
Ensure that the IUT in the Call Received call state U7, on receipt of a STATUS
ENQUIRY message from the calling endpoint,
sends a STATUS message containing a Cause information element indicating the
cause value 30 "response to STATUS ENQUIRY" and a Call state information
element indicating the Call Received call state and remains in the Call
Received call state U7.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 table 4, clauses 7.3.12 and 7.3.13 [3]
BCC_GK_PHA_14Tx STATUS, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a STATUS
ENQUIRY message from the calling endpoint,
sends a STATUS message containing a Cause information element indicating the
cause value 30 "response to STATUS ENQUIRY" and a Call state information
element indicating the Active call state and remains in the Active call state U10.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 table 4, clauses 7.3.12 and 7.3.13 [3]
H225/
BCC/
Gatekeeper/
BCC_GK_PHE
BCC_GK_PHE_01enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE
COMPLETE message from the calling endpoint,
enters the Null call state U0 in the interface with the calling endpoint
and sends a RELEASE COMPLETE message to the destination Gatekeeper and enters in
the Null call state U0 in the interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.2 clauses 8.5 [2] and 7.1 [3]
BCC_GK_PHE_02enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message
from the destination gatekeeper, enters the Null call state U0 in the interface with the destination gatekeeper;
and sends a RELEASE COMPLETE message to the calling endpoint and enters in the Null call state U0 in the interface with the calling endpoint.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.2 clauses 8.5 [2] and 7.1 [3]
H225/
BCC/
Gatekeeper/
InnoportuneBehavior
H225/
BCC/
Gatekeeper/
InnoportuneBehavior/
U00
BCC_GK_I_U00_01Tx STATUS, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a message containing an unknown
message type information element, sends a STATUS message to the calling endpoint and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.1 clause 5.8.4 [4]
BCC_GK_I_U00_02Tx STATUS, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a RESUME message
(out of the context of the base specification), sends a STATUS message to the calling endpoint and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.1 table 4 [3] and clause 5.8.4 [4]
BCC_GK_I_U00_03Tx STATUS, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a STATUS ENQUIRY message,
sends a STATUS message containing a Cause information element indicating the cause value 30 "response to
STATUS ENQUIRY" and a Call state information element indicating the Null call state and remains in the Null call
state U0.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.1 clauses 5.8.3.2 h) and 5.8.10 [4]
BCC_GK_I_U00_04Tx RELEASE COMPLETE, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a STATUS message
containing a Call state information element indicating a call state other than the Null call state,
sends a RELEASE COMPLETE message containing a Cause information element indicating the cause value 101
"message not compatible with call state" and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.1 clauses 5.8.3.2 g) and 5.8.11 [4]
BCC_GK_I_U00_05Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a STATUS message
containing a Call state information element indicating the Null call state, sends no message and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.1 clauses 5.8.3.2 g) and 5.8.11 [4]
H225/
BCC/
Gatekeeper/
InnoportuneBehavior/
U07
BCC_GK_I_U07_01Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Received call state U7, on receipt of a
RELEASE COMPLETE message, closes call signalling channel and enters the Null call state U0 in the interface with the calling endpoint
and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the
interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.2 clause 5.8.4 [4]
BCC_GK_I_U07_02Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Received call state U7, on receipt of a STATUS message containing a Call state
information element indicating the Null call state,
closes call signalling channel and enters the Null call state U0 in the interface with the calling endpoint
and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the
interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.2 clause 5.8.11 [4]
BCC_GK_I_U07_03Tx STATUS, remain in Call Received call state U7
Ensure that the IUT in the Call Received call state U7, on receipt of a message containing an unknown message type
information element, sends a STATUS message to the calling endpoint and remains in the Call Received call state U7.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.2 clause 5.8.11 [4]
BCC_GK_I_U07_04Tx STATUS, remain in Call Received call state U7
Ensure that the IUT in the Call Received call state U7, on receipt of a DISCONNECT
message (out of the context of the base specification), sends a STATUS message to the calling endpoint and remains in the Call Received
call state U7.
5.2.2.2.3.3 Call Proceeding call state U9
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.2 table 4 [3] and clause 5.8.4 [4]
H225/
BCC/
Gatekeeper/
InnoportuneBehavior/
U09
BCC_GK_I_U09_01Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Proceeding call state U9, on receipt of a RELEASE COMPLETE message,
closes call signalling channel and enters the Null call state U0 in the interface with the calling endpoint
and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the
interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.3 clause 5.8.4 [4]
BCC_GK_I_U09_02Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Proceeding call state U9, on receipt of a STATUS message containing a Call state
information element indicating the Null call state,
closes call signalling channel and enters the Null call state U0 in the interface with the calling endpoint
and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the
interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.3 clause 5.8.11 [4]
BCC_GK_I_U09_03Tx STATUS, remain in Call Proceeding call state U9
Ensure that the IUT in the Call Proceeding call state U9, on receipt of a message containing an unknown message type
information element, sends a STATUS message to the calling endpoint and remains in the Call Proceeding call state U9.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.3 clause 5.8.4 [4]
BCC_GK_I_U09_04Tx STATUS, remain in Call Proceeding call state U9
Ensure that the IUT in the Call Proceeding call state U9, on receipt of a RELEASE message (out of the context of the base specification),
sends a STATUS message to the calling endpoint and remains in the Call Proceeding call state U9.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.3 table 4 [3] and clause 5.8.4 [4]
H225/
BCC/
Gatekeeper/
InnoportuneBehavior/
U10
BCC_GK_I_U10_01Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call stateU0
Ensure that the IUT in the Active call state U10, on receipt of a STATUS message containing a Call state information
element indicating the Null call state, closes call signalling channel and enters the Null call state U0 in the interface with the calling endpoint
and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the
interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.4 clause 5.8.11 [4]
BCC_GK_I_U10_02Tx STATUS, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a message containing an unknown message type
information element, sends a STATUS message to the calling endpoint and remains in the Active call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.4 clause 5.8.11 [4]
BCC_GK_I_U10_03Tx STATUS, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a SUSPEND message (out of the context of the base
specification), sends a STATUS message to the calling endpoint and remains in the Active call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.3.4 table 4 [3] and clause 5.8.4 [4]
H225/
BCC/
Gatekeeper/
SyntacticallyInvalid
H225/
BCC/
Gatekeeper/
SyntacticallyInvalid/
U00
BCC_GK_S_U00_01Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message containing an erroneous protocol
discriminator information element, coded other than 08H, sends no message and remains in the Null call state U0.
Note: FastStart only.
User Action: None
Config: B
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.1 clause 5.8.1 [4]
BCC_GK_S_U00_02Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a message which is too short to contain a complete message
type information element, sends no message and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.1 clause 5.8.2 [4]
BCC_GK_S_U00_03Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message containing an invalid call reference
information element format (octet 1, bits 8 to 5 != 0000B), sends no message and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.1 clause 5.8.3.1 [4]
BCC_GK_S_U00_04Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message containing an invalid call reference
information element format (octet 1, bits 4 to 1, length too high), sends no message and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.1 clause 5.8.3.1 [4]
BCC_GK_S_U00_05Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message containing the dummy call reference,
sends no message and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.1 clause 5.8.3.1 [4]
BCC_GK_S_U00_06Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message containing a call reference flag bit set
to 1, sends no message and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.1 clause 5.8.3.1 [4]
BCC_GK_S_U00_07Tx RELEASE COMPLETE, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message with a mandatory information element
missing, sends a RELEASE COMPLETE message containing a Cause information element indicating the cause value 96
"mandatory information element missing" and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.1 clause 5.8.6.1 [4]
BCC_GK_S_U00_08Tx RELEASE COMPLETE, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message containing a mandatory information
element with content error, sends a RELEASE COMPLETE message containing a Cause information element indicating the cause value 100
"invalid information element" and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.1 clause 5.8.6.2 [4]
BCC_GK_S_U00_09Tx CALL PROCEEDING, enter Incoming Call Proceeding call state U9, Tx SETUP, enter Call Initiated call state U1
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message containing an information element, which
is not within the context of the base specification, sends a CALL PROCEEDING message and enters the Incoming Call Proceeding call state U9 in the interface with
the calling endpoint and sends a SETUP message, to the Destination Gatekeeper and enters the Call Initiated call state U1 in the interface
with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.1 clause 5.8.7.1 [4]
BCC_GK_S_U00_10Tx CALL PROCEEDING, enter Incoming Call Proceeding call state U9, Tx SETUP, enter Call Initiated call state U1
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message containing a non-mandatory information
element with content error, sends a CALL PROCEEDING message and enters the Incoming Call Proceeding call state U9 in the interface with
the calling endpoint and sends a SETUP message, to the Destination Gatekeeper and enters the Call Initiated call state U1 in the interface
with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.1 clause 5.8.7.2 [4]
H225/
BCC/
Gatekeeper/
SyntacticallyInvalid/
U07
BCC_GK_S_U07_01Tx no message, remain in Call Received call state U7
Ensure that the IUT in the Call Delivered call state U7, on receipt of a RELEASE COMPLETE
message containing an erroneous protocol discriminator information element, coded other than 08H, sends no message and remains in the Call
Delivered call state U7.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.2 clause 5.8.1 [4]
BCC_GK_S_U07_02Tx no message, remain in Call Received state U7
Ensure that the IUT in the Call Delivered call state U7, on receipt of a message
which is too short to contain a complete message type information element, sends no message and remains in the Call Delivered call state U7.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.2 clause 5.8.2 [4]
BCC_GK_S_U07_03Tx no message, remain in Call Received call state U7
Ensure that the IUT in the Call Delivered call state U7, on receipt of a RELEASE COMPLETE
message containing an invalid call reference information element format (octet 1, bits 8 to 5 != 0000B), sends no message and remains in the
Call Delivered call state U7.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.2 clause 5.8.3.1 [4]
BCC_GK_S_U07_04Tx no message, remain in Call Received call state U7
Ensure that the IUT in the Call Delivered call state U7, on receipt of a RELEASE COMPLETE
message containing an invalid call reference information element format (octet 1, bits 4 to 1, length too high), sends no message and remains
in the Call Delivered call state U7.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.2 clause 5.8.3.1 [4]
BCC_GK_S_U07_05Tx no message, remain in Call Received call state U7
Ensure that the IUT in the Call Delivered call state U7, on receipt of a RELEASE COMPLETE
message containing the dummy call reference, sends no message and remains in the Call Delivered call state U7.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.2 clause 5.8.3.1 [4]
BCC_GK_S_U07_06enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Delivered call state U7, on receipt of a RELEASE COMPLETE
message with a mandatory information element missing, enters the Null call state U0 in the interface with the calling endpoint and sends a
RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the interface with the destination
Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-3 V2.1.1 (2004-11) 5.2.2.2.4.2 clause 5.8.6.1 [4]
BCC_GK_S_U07_07enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Delivered call state U7, on receipt of a RELEASE COMPLETE
message containing a mandatory information element with content error, enters the Null call state U0 in the interface with the calling endpoint
and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters the Null call state U0 in the interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.2 clause 5.8.6.2 [4]
BCC_GK_S_U07_08enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Delivered call state U7, on receipt of a RELEASE COMPLETE
message containing an information element, which is not within the context of the base specification, enters the Null call state U0
in the interface with the calling endpoint and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null
call state U0 in the interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.2 clause 5.8.7.1 [4]
BCC_GK_S_U07_09enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Delivered call state U7, on receipt of a RELEASE COMPLETE
message containing a non-mandatory information element with content error, enters in the Null call state U0 in the interface with the calling
endpoint and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the interface with the
destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.2 clause 5.8.7.2 [4]
H225/
BCC/
Gatekeeper/
SyntacticallyInvalid/
U09
BCC_GK_S_U09_01Tx no message, remain in Incoming Call Proceeding call state U9
Ensure that the IUT in the Incoming Call Proceeding call state U9, on receipt of a
RELEASE COMPLETE message containing an erroneous protocol discriminator information element, coded other than ’08’H,
sends no message and remains in the Incoming Call Proceeding call state U9.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.3 clause 5.8.1 [4]
BCC_GK_S_U09_02Tx no message, remain in Incoming Call Proceeding call state U9
Ensure that the IUT in the Incoming Call Proceeding call state U9, on receipt of a message
which is too short to contain a complete message type information element,
sends no message and remains in the Incoming Call Proceeding call state U9.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.3 clause 5.8.2 [4]
BCC_GK_S_U09_03Tx no message, remain in Incoming Call Proceeding call state U9
Ensure that the IUT in the Incoming Call Proceeding call state U9, on receipt of a
RELEASE COMPLETE message containing an invalid call reference information element format (octet 1, bits 8 to 5 != ’0000’B),
sends no message and remains in the Incoming Call Proceeding call state U9.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.3 clause 5.8.3.1 [4]
BCC_GK_S_U09_04Tx no message, remain in Incoming Call Proceeding call state U9
Ensure that the IUT in the Incoming Call Proceeding call state U9, on receipt of a
RELEASE COMPLETE message containing an invalid call reference information element format (octet 1, bits 4 to 1, length too high),
sends no message and remains in the Incoming Call Proceeding call state U9.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.3 clause 5.8.3.1 [4]
BCC_GK_S_U09_05Tx no message, remain in Incoming Call Proceeding call state U9
Ensure that the IUT in the Incoming Call Proceeding call state U9, on receipt of a
RELEASE COMPLETE message containing the dummy call reference, sends no message and remains in the Incoming Call Proceeding call state U9.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.3 clause 5.8.3.1 [4]
BCC_GK_S_U09_06enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Incoming Call Proceeding call state U9, on receipt of a
RELEASE COMPLETE message with a mandatory information element missing, enters the Null call state U0 in the interface with the calling
endpoint and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the interface with
the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.3 clause 5.8.6.1 [4]
BCC_GK_S_U09_07enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Incoming Call Proceeding call state U9, on receipt of a
RELEASE COMPLETE message containing a mandatory information element with content error, enters the Null call state U0 in the interface
with the calling endpoint and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the
interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.3 clause 5.8.6.2 [4]
BCC_GK_S_U09_08enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Incoming Call Proceeding call state U9, on receipt of a
RELEASE COMPLETE message containing an information element, which is not within the context of the base specification, enters the Null
call state U0 in the interface with the calling endpoint and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters
in the Null call state U0 in the interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.3 clause 5.8.7.1 [4]
BCC_GK_S_U09_09enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Incoming Call Proceeding call state U9, on receipt of a
RELEASE COMPLETE message containing a non-mandatory information element with content error, enters the Null call state U0 in the interface
with the calling endpoint and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the
interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.3 clause 5.8.7.2 [4]
H225/
BCC/
Gatekeeper/
SyntacticallyInvalid/
U10
BCC_GK_S_U10_01Tx no message, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message containing an
erroneous protocol discriminator information element, coded other than ’08’H,
sends no message and remains in the Active call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.4 clause 5.8.1 [4]
BCC_GK_S_U10_02Tx no message, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a message which is too short to contain a complete
message type information element,
sends no message and remains in the Active call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.4 clause 5.8.2 [4]
BCC_GK_S_U10_03Tx no message, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message containing an invalid
call reference information element format (octet 1, bits 8 to 5 != ’0000’B),
sends no message and remains in the Active call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.4 clause 5.8.3.1 [4]
BCC_GK_S_U10_04Tx no message, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message containing an invalid
call reference information element format (octet 1, bits 4 to 1, length too high),
sends no message and remains in the Active call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.4 clause 5.8.3.1 [4]
BCC_GK_S_U10_05Tx no message, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message containing the
dummy call reference,
sends no message and remains in the Active call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.4 clause 5.8.3.1 [4]
BCC_GK_S_U10_06enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message
with a mandatory information element missing, enters the Null call state U0 in the interface with the calling endpoint and sends the
RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.4 clause 5.8.6.1 [4]
BCC_GK_S_U10_07enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE
message containing a mandatory information element with content error, enters the Null call state U0 in the interface with the calling
endpoint and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the
interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.4 clause 5.8.6.2 [4]
BCC_GK_S_U10_08enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE
message containing an information element, which is not within the context of the base specification, enters the Null call state U0 in
the interface with the calling endpoint and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call
state U0 in the interface with the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.4 clause 5.8.7.1 [4]
BCC_GK_S_U10_09enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE
message containing a nonmandatory information element with content error, enters the Null call state U0 in the interface with the calling
endpoint and sends the RELEASE COMPLETE message to the destination Gatekeeper and enters in the Null call state U0 in the interface with
the destination Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.4.4 clause 5.8.7.2 [4]
H225/
BCC/
DestinationGatekeeper
H225/
BCC/
DestinationGatekeeper/
PHA
BCC_DGK_PHA_01Tx CALL PROCEEDING, enter Incoming Call Proceeding call state U9, Tx SETUP, enter Call Initiated call state U1
Ensure that the IUT in the Null call state U0, on receipt of a SETUP message,
from the calling Gatekeeper, sends a CALL PROCEEDING message and enters the Incoming Call Proceeding call
state U9 in the interface with the calling Gatekeeper and sends a SETUP message, to the called endpoint, and enters the Call Initiated
call state U1 in the interface with the called endpoint.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 clauses 8.1 [2], clauses 7.1 and 7.3.10 [3]
BCC_DGK_PHA_02Tx no message, enter Outgoing Call Proceeding call state U3, Tx no message, remains in Incoming Call Proceeding call state U9
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message, from the called endpoint, sends no message and enters the Outgoing Call Proceeding call state U3 in the
interface with the called endpoint and sends no message and remains in the Incoming Call Proceeding call state U9 in
the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 clauses 8.1 [2] and 7.3.2 [3]
BCC_DGK_PHA_03Tx no message, enter Call Delivered call state U4, Tx ALERTING, enter Call Received call state U7
Ensure that the IUT in the Call Initiated call state U1, on receipt of an
ALERTING message from the called endpoint, sends no message and enters the Call Delivered call state U4 in the interface
with the called endpoint and sends an ALERTING message to the calling Gatekeeper and enters the Call
Received call state U7 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 clauses 8.1 [2] and 7.3.1 [3]
BCC_DGK_PHA_04Tx no message, enter Active call state U10, Tx CONNECT, enter Active call state U10
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
CONNECT message from the called endpoint, sends no message and enters the Active call state U10 in the interface with
the called endpoint and sends a CONNECT message to the calling Gatekeeper and enters the Active call
state U10 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 clauses 8.1 [2] and 7.3.3 [3]
BCC_DGK_PHA_05Tx SETUP, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on the first expiry
of the timer T303, sends a SETUP message and remains in the Call Initiated call state U1.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 clauses 8.1 [2] and 7.5 [3]
BCC_DGK_PHA_06Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on the second expiry
of the timer T303, sends a RELEASE COMPLETE message containing either a Cause information element indicating the cause value
102 "recovery on timer expiry" or a User-to-user information element including the reason field indicating why the call was released
to the called endpoint and enters the Null call state U0 in the interface with the called endpoint and sends a RELEASE COMPLETE message
to the calling Gatekeeper and enters the Null call state U0 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 clauses 8.1 [2] and 7.5 [3]
BCC_DGK_PHA_07Tx no message, enter Call delivered call state U4, Tx ALERTING, enter Call received call state U7
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of an ALERTING message from the called endpoint, sends no message and enters the Call delivered call state U4 in the interface
with the called endpoint and sends an ALERTING message to the calling Gatekeeper and enters the Call received call state U7 in the
interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 clauses 8.1 [2] and 7.5 [3]
BCC_DGK_PHA_08Tx no message, enter Active call state U10, Tx CONNECT, enter Active call state U10
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a CONNECT message from the called endpoint, sends no message and enters the Active call state U10 in the interface with
the called endpoint and sends a CONNECT message to the calling Gatekeeper and enters the Active call state U10 in the interface
with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 clauses 8.1 [2] and 7.3.3 [3]
BCC_DGK_PHA_09Tx no message, enter Active call state U10, Tx CONNECT, enter Active call state U10
Ensure that the IUT in the Call delivered call state U4, on receipt of a
CONNECT message from the called endpoint, sends no message and enters the Active call state U10 in the interface with
the called endpoint and sends a CONNECT message to the calling Gatekeeper and enters the Active call state U10 in the interface
with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 clauses 8.1 [2] and 7.3.3 [3]
BCC_DGK_PHA_10Tx STATUS, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
STATUS ENQUIRY message from the called endpoint, sends a STATUS message containing a Cause information element indicating the
cause value 30 "response to STATUS ENQUIRY" and a Call state information element indicating the Call Initiated call state and
remains in the Call Initiated call state U1.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 table 4, clauses 7.3.12 and 7.3.13 [3]
BCC_DGK_PHA_11Tx STATUS, remain in Outgoing Call Proceeding call state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a STATUS ENQUIRY message from the called endpoint, sends a STATUS message containing a Cause information element indicating the
cause value 30 "response to STATUS ENQUIRY" and a Call state information element indicating the Outgoing Call Proceeding call state
and remains in the Outgoing Call Proceeding call state U3.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 table 4, clauses 7.3.12 and 7.3.13 [3]
BCC_DGK_PHA_12Tx STATUS, remain in Call delivered call state U4
Ensure that the IUT in the Call delivered call state U4, on receipt of a STATUS ENQUIRY message from the called
endpoint,
sends a STATUS message containing a Cause information element indicating the cause value 30 "response to
STATUS ENQUIRY" and a Call state information element indicating the Call delivered call state and remains in
the Call delivered call state U4.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 table 4, clauses 7.3.12 and 7.3.13 [3]
BCC_DGK_PHA_13Tx STATUS, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a STATUS ENQUIRY message from the called endpoint,
sends a STATUS message containing a Cause information element indicating the cause value 30 "response to
STATUS ENQUIRY" and a Call state information element indicating the Active call state and remains in the Active
call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.3.1 table 4, clauses 7.3.12 and 7.3.13 [3]
H225/
BCC/
DestinationGatekeeper/
PHE
BCC_DGK_PHE_01Tx enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message,
from the calling Gatekeeper, enters the Null call state U0 in the interface with the calling Gatekeeper and
sends a RELEASE COMPLETE to the called endpoint, and enters the Null
call state U0 in the interface with the called endpoint.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 6.4, 8.1.5, 8.1.6, 8.1.8 [2]; subclause 7.1, 7.3.10 [3]
BCC_DGK_PHE_02Tx enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message,
from the called endpoint, enters the Null call state U0 in the interface with the called endpoint and
sends a RELEASE COMPLETE to the calling Gatekeeper, and enters the Null
call state U0 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 6.4, 8.1.5, 8.1.6, 8.1.8 [2]; subclause 7.1, 7.3.10 [3]
H225/
BCC/
DestinationGatekeeper/
Inopportune
H225/
BCC/
DestinationGatekeeper/
Inopportune/
U00
BCC_DGK_I_U00_01Tx STATUS, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a message
containing an unknown message type information element, from the called endpoint, sends a STATUS message to the called
endpoint and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 6.4, 8.1.5, 8.1.6, 8.1.8 [2]; subclause 7.1 [3]
BCC_DGK_I_U00_02Tx STATUS, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a RESUME message
(out of the context of the base specification), sends a STATUS message to the called endpoint and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 6.4, 8.1.5, 8.1.6, 8.1.8 [2]; subclause 7.1[3]; figure A.3 annex A [4]
BCC_DGK_I_U00_03Tx STATUS, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a STATUS ENQUIRY
message, sends a STATUS message containing a Cause information element indicating the
cause value 30 "response to STATUS ENQUIRY" and a Call state information
element indicating the Null call state and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 6.4, 8.1.5, 8.1.6, 8.1.8 [2]; subclause 7.1[3]; subclause 5.8.3.2 h), 5.8.10 [4]
BCC_DGK_I_U00_04Tx RELEASE COMPLETE, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a STATUS message containing a Call state information
element indicating a call state other than the Null call state, sends a RELEASE COMPLETE message containing a Cause information element
indicating the cause value 101 "message not compatible with call state" and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 6.4, 8.1.5, 8.1.6, 8.1.8 [2]; subclause 7.1[3]; subclause 5.8.3.2 g), 5.8.11 [4]
BCC_DGK_I_U00_05Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a STATUS message
containing a Call state information element indicating the Null call state, sends no message and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) ssubclause 6.4, 8.1.5, 8.1.6, 8.1.8 [2]; subclause 7.1[3]; subclause 5.8.3.2 g), 5.8.11 [4]
H225/
BCC/
DestinationGatekeeper/
Inopportune/
U01
BCC_DGK_I_U01_01Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
RELEASE COMPLETE message, closes call signalling channel and enters the Null call state U0 in the
interface with the called endpoint and sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3]
BCC_DGK_I_U01_02Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
STATUS message containing a Call state information element indicating the Null
call state, closes call signalling channel and enters the Null call state U0 in the interface with the called endpoint
and sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3]
BCC_DGK_I_U01_03Tx STATUS, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
message containing an unknown message type information element,
sends a STATUS message to the calling endpoint and remains in the Call
Initiated call state U1.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3]
BCC_DGK_I_U01_04Tx STATUS, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
RELEASE message (out of the context of the base specification),
sends a STATUS message to the calling endpoint and remains in the Call
Initiated call state U1.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3]
H225/
BCC/
DestinationGatekeeper/
Inopportune/
U03
BCC_DGK_I_U03_01Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a RELEASE COMPLETE message, closes call signalling channel and enters the Null call state U0 in the interface with the called
endpoint and sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3]
BCC_DGK_I_U03_02Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a STATUS message containing a Call state information element indicating the
Null call state, closes call signalling channel and enters the Null call state U0 in the
interface with the called endpoint and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3]
BCC_DGK_I_U03_03Tx STATUS, remain in Outgoing Call Proceeding call state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a message containing an unknown message type information element,
sends a STATUS message to the calling endpoint and remains in the Outgoing
Call Proceeding call state U3.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3]
BCC_DGK_I_U03_04Rx DISCONNECT, Tx STATUS, remain in Outgoing Call Proceeding call state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt of a DISCONNECT message (out of the
context of the base specification),
sends a STATUS message to the calling endpoint and remains in the Outgoing Call Proceeding call state U3.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3]
H225/
BCC/
DestinationGatekeeper/
Inopportune/
U04
BCC_DGK_I_U04_01Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
RELEASE COMPLETE message,
closes call signalling channel and enters the Null call state U0 in the
interface with the called endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3]
BCC_DGK_I_U04_02Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
STATUS message containing a Call state information element indicating the Null
call state,
closes call signalling channel and enters the Null call state U0 in the
interface with the called endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3]
BCC_DGK_I_U04_03Tx STATUS, remain in Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
message containing an unknown message type information element, sends a STATUS message to the calling endpoint and remains in
the Call Delivered call state U4.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3]
BCC_DGK_I_U04_04Tx STATUS, remain in Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a
RELEASE message (out of the context of the base specification),sends a STATUS message to the calling endpoint and remains in
the Call Delivered call state U4.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3]
H225/
BCC/
DestinationGatekeeper/
Inopportune/
U10
BCC_DGK_I_U10_01Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a STATUS
message containing a Call state information element indicating the Null call state,
closes call signalling channel and enters the Null call state U0 in the interface with the called endpoint and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1[3], 5.8.11 [5]
BCC_DGK_I_U10_02Tx STATUS, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a message
containing an unknown message type information element,
sends a STATUS message to the calling endpoint and remains in the Active call
state U10.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1 [3]
BCC_DGK_I_U10_03Tx STATUS, remain in Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a CONNECT
ACKNOWLEDGE message (out of the context of the base specification),
sends a STATUS message to the calling endpoint and remains in the Active call
state U10.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clause 7.1 [3]
H225/
BCC/
DestinationGatekeeper/
SyntacticallyInvalid
H225/
BCC/
DestinationGatekeeper/
SyntacticallyInvalid/
U00
BCC_DGK_S_U00_01Tx no message, remain in Null call state U0
Ensure that the IUT in the Null call state U0, on receipt of a message which
is too short to contain a complete message type information element,
sends no message and remains in the Null call state U0.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 5.8.2 [5]
H225/
BCC/
DestinationGatekeeper/
SyntacticallyInvalid/
U01
BCC_DGK_S_U01_01Tx no message, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message containing an erroneous protocol discriminator information
element, coded other than 08H,
sends no message and remains in the Call Initiated call state U1.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.1.2 [3]; subclause 5.8.1 [5]
BCC_DGK_S_U01_02Tx no message, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
message which is too short to contain a complete message type information
element,
sends no message and remains in the Call Initiated call state U1.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 5.8.2 [5]
BCC_DGK_S_U01_03Tx no message, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of an
ALERTING message containing an invalid call reference information element
format (octet 1, bits 8 - 5 != 0000B),
sends no message and remains in the Call Initiated call state U1.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.1.2 [3]; subclause 5.8.3.1 [5]
BCC_DGK_S_U01_04Tx no message, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
CONNECT message containing an invalid call reference information element
format (octet 1, bits 4 to 1, length too high),
sends no message and remains in the Call Initiated call state U1.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.1.2 [3]; subclause 5.8.3.1 [5]
BCC_DGK_S_U01_05Tx no message, remain in Call Initiated call state U1
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message containing the dummy call reference,
sends no message and remains in the Call Initiated call state U1.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2.1.2 [3]; subclause 5.8.3.1 [5]
BCC_DGK_S_U01_06Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message with a mandatory information element missing,
sends a RELEASE COMPLETE message with a Cause information element indicating
the cause value 96 "mandatory information element missing" to the Called
endpoint and enters the Null call state U0 in the interface with the called
endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 6.1.1 [4]; subclause 5.8.6.1 [5]
BCC_DGK_S_U01_07Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of an
ALERTING message with a mandatory information element missing,
sends a RELEASE COMPLETE message with a Cause information element indicating
the cause value 96 "mandatory information element missing" to the Called
endpoint and enters the Null call state U0 in the interface with the called
endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 6.1.1 [4]; subclause 5.8.6.1 [5]
BCC_DGK_S_U01_08Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
CONNECT message with a mandatory information element missing,
sends a RELEASE COMPLETE message with a Cause information element indicating
the cause value 96 "mandatory information element missing" to the Called
endpoint and enters the Null call state U0 in the interface with the called
endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 6.1.1 [4]; subclause 5.8.6.1 [5]
BCC_DGK_S_U01_09Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message containing a mandatory information element with content
error,
sends a RELEASE COMPLETE message with a Cause information element indicating
the cause value 100 "invalid information element" to the Called endpoint and
enters the Null call state U0 in the interface with the called endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 6.1.1 [4]; subclause 5.8.6.1 [5]
BCC_DGK_S_U01_10Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of an
ALERTING message containing a mandatory information element with content
error,
sends a RELEASE COMPLETE message with a Cause information element indicating
the cause value 100 "invalid information element" to the Called endpoint and
enters the Null call state U0 in the interface with the called endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 6.1.1 [4]; subclause 5.8.6.1 [5]
BCC_DGK_S_U01_11Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Initiated call state U1, on receipt of a
CONNECT message containing a mandatory information element with content error,
sends a RELEASE COMPLETE message with a Cause information element indicating
the cause value 100 invalid information element to the Called endpoint and
enters the Null call state U0 in the interface with the called endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the
Null call state U0 interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 6.1.1 [4]; subclause 5.8.6.1 [5]
BCC_DGK_S_U01_12Tx no message, enter Outgoing Call Proceeding call state U3, Tx no message, remain in Incoming Call Proceeding call state U9
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message containing an information element, which is not within the
context of the base specification,
sends no message and enters the Outgoing Call Proceeding call state U3 in the
interface with the called endpoint
and
sends no message and remains in the incoming Call Proceeding call state U9 in
the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 6.1.1 [4]
BCC_DGK_S_U01_13Tx no message, enter Call Delivered call state U4, Tx ALERTING, enter Call Received call state U7
Ensure that the IUT in the Call Initiated call state U1, on receipt of an
ALERTING message containing an information element, which is not within the
context of the base specification,
sends no message and enters the Call Delivered call state U4 in the interface
with the called endpoint
and
sends an ALERTING message to the Calling Gatekeeper and enters the Call
Received call state U7 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 6.1.1 [4]
BCC_DGK_S_U01_14Tx no message, enter Active call state U10, Tx CONNECT, enter Active call state U10
Ensure that the IUT in the Call Initiated call state U1, on receipt of an
CONNECT message containing an information element, which is not within the
context of the base specification,
sends no message and enters the Active call state U10 in the interface with
the called endpoint
and
sends a CONNECT message to the calling Gatekeeper and enters the Active call
state U10 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 6.1.1 [4]
BCC_DGK_S_U01_15 Tx no message, enter Outgoing Call Proceeding state U3, Tx no message, remain in incoming Call Proceeding state U9
Ensure that the IUT in the Call Initiated call state U1, on receipt of a CALL
PROCEEDING message containing a non-mandatory information element with content
error,
sends no message and enters the Outgoing Call Proceeding call state U3 in the
interface with the called endpoint
and
sends no message and remains in the incoming Call Proceeding call state U9 in
the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 6.1.1 [4]
BCC_DGK_S_U01_16Tx no message, enter Call Delivered state U4, Tx ALERTING message, enter Call Received state U7
Ensure that the IUT in the Call Initiated call state U1, on receipt of an
ALERTING message containing a non-mandatory information element with content
error,
sends no message and enters the Call Delivered call state U4 in the interface
with the called endpoint
and
sends an ALERTING message to the Calling Gatekeeper and enters the Call
Received call state U7 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 6.1.1 [4]
BCC_DGK_S_U01_17Tx no message, enter Active call state U10, Tx CONNECT message, enter Active call state U10
Ensure that the IUT in the Call Initiated call state U1, on receipt of an
CONNECT message containing a non-mandatory information element with content
error,
sends no message and enters the Active call state U10 in the interface with
the called endpoint
and
sends a CONNECT message to the calling Gatekeeper and enters the Active call
state U10 in the interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.1 [3]; subclause 6.1.1 [4]
H225/
BCC/
DestinationGatekeeper/
SyntacticallyInvalid/
U03
BCC_DGK_S_U03_01Tx no message, remain in Outgoing Call Proceeding state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of an ALERTING message containing an erroneous protocol discriminator
information element, coded other than’08’H,
sends no message and remains in the Outgoing Call Proceeding call state U3.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.1 [4]
BCC_DGK_S_U03_02Tx no message, remain in Outgoing Call Proceeding state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a message which is too short to contain a complete message type information
element,
sends no message and remains in the Outgoing Call Proceeding call state U3.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.2 [4]
BCC_DGK_S_U03_03Tx no message, remain in Outgoing Call Proceeding state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt
of a CONNECT message containing an invalid call reference information element
format (octet 1, bits 8 - 5 != ’0000’B),
sends no message and remains in the Outgoing Call Proceeding call state U3.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.3.1 [4]
BCC_DGK_S_U03_04Tx no message, remain in Outgoing Call Proceeding state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt of an ALERTING message containing an
invalid call reference information element format (octet 1, bits 4 to 1, length too high),
sends no message and remains in the Outgoing Call Proceeding call state U3.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.3.1 [4]
BCC_DGK_S_U03_05Tx no message, remain in Outgoing Call Proceeding state U3
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt of a CONNECT message containing the
dummy call reference,
sends no message and remains in the Outgoing Call Proceeding call state U3.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.3.1 [4]
BCC_DGK_S_U03_06Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt of an ALERTING message with a
mandatory information element missing,
sends a RELEASE COMPLETE message containing a Cause information element indicating the cause value 96
"mandatory information element missing" to the called endpoint and enters the Null call state U0 in the interface
with the called endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the Null call state U0 in the
interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.6.1 [4]
BCC_DGK_S_U03_07Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt of a CONNECT message with a
mandatory information element missing,
sends a RELEASE COMPLETE message containing a Cause information element indicating the cause value 96
"mandatory information element missing" to the called endpoint and enters the Null call state U0 in the interface
with the called endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the Null call state U0 in the
interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.6.1 [4]
BCC_DGK_S_U03_08Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt of an ALERTING message containing a
mandatory information element with content error,
sends a RELEASE COMPLETE message containing a Cause information element indicating the cause value 100
"invalid information element" to the called endpoint and enters the Null call state U0 in the interface with the called
endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the Null call state U0 in the
interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.6.2 [4]
BCC_DGK_S_U03_09Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt of a CONNECT message containing a
mandatory information element with content error,
sends a RELEASE COMPLETE message containing a Cause information element indicating the cause value 100
"invalid information element" to the called endpoint and enters the Null call state U0 in the interface with the called
endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the Null call state U0 in the
interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.6.2 [4]
BCC_DGK_S_U03_10 Tx no message, enters Call Delivered state U4
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt of an ALERTING message containing an
information element, which is not within the context of the base specification,
sends no message and enters the Call Delivered call state U4 in the interface with the called endpoint
and
sends an ALERTING message to the calling Gatekeeper and enters the Call Received call state U7 in the interface
with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.7.1 [4]
BCC_DGK_S_U03_11Tx no message, enters the Active call state U10
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt of a CONNECT message containing an
information element, which is not within the context of the base specification,
sends no message and enters the Active call state U10 in the interface with the called endpoint
and
sends a CONNECT message to the calling Gatekeeper and enters the Active call state U10 in the interface with the
calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.7.1 [4]
BCC_DGK_S_U03_12Tx no message, enter Call Delivered call state U4, Tx ALERTING, enter Call Received call state U7
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt of an ALERTING message containing a
non-mandatory information element with content error,
sends no message and enters the Call Delivered call state U4 in the interface with the called endpoint
and
sends an ALERTING message to the calling Gatekeeper and enters the Call Received call state U7 in the interface
with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.7.2 [4]
BCC_DGK_S_U03_13Tx no message, enter Active call state U10, Tx CONNECT, enter Active call state U10
Ensure that the IUT in the Outgoing Call Proceeding call state U3, on receipt of a CONNECT message containing a
non-mandatory information element with content error,
sends no message and enters the Active call state U10 in the interface with the called endpoint
and
sends a CONNECT message to the calling Gatekeeper and enters the Active call state U10 in the interface with the
calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.7.2 [4]
H225/
BCC/
DestinationGatekeeper/
SyntacticallyInvalid/
U04
BCC_DGK_S_U04_01Tx no message, remain in the Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a CONNECT message containing an erroneous
protocol discriminator information element, coded other than 08H,
sends no message and remains in the Call Delivered call state U4.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.1 [4]
BCC_DGK_S_U04_02Tx no message, remain in the Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a message which is too short to contain a complete
message type information element,
sends no message and remains in the Call Delivered call state U4.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.2 [4]
BCC_DGK_S_U04_03Tx no message, remain in the Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of an CONNECT message containing an invalid call
reference information element format (octet 1, bits 8 to 5 != 0000B),
sends no message and remains in the Call Delivered call state U4.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.3.1 [4]
BCC_DGK_S_U04_04Tx no message, remain in the Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a CONNECT message containing an invalid call
reference information element format (octet 1, bits 4 to 1, length too high),
sends no message and remains in the Call Delivered call state U4.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.3.1 [4]
BCC_DGK_S_U04_05Tx no message, remain in the Call Delivered call state U4
Ensure that the IUT in the Call Delivered call state U4, on receipt of a CONNECT message containing the dummy call
reference,
sends no message and remains in the Call Delivered call state U4.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.3.1 [4]
BCC_DGK_S_U04_06Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Delivered call state U4, on receipt of a CONNECT message with a mandatory
information element missing,
sends a RELEASE COMPLETE message containing a Cause information element indicating the cause value 96
"mandatory information element missing" to the called endpoint and enters the Null call state U0 in the interface
with the called endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the Null call state U0 in the
interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.6.1 [4]
BCC_DGK_S_U04_07Tx RELEASE COMPLETE, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Call Delivered call state U4, on receipt of a CONNECT message containing a mandatory
information element with content error,
sends a RELEASE COMPLETE message containing a Cause information element indicating the cause value 100
"invalid information element" to the called endpoint and enters the Null call state U0 in the interface with the called
endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the Null call state U0 in the
interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.6.2 [4]
BCC_DGK_S_U04_08Tx no message, enter Active call state U10, Tx CONNECT, enter Active call state U10
Ensure that the IUT in the Call Delivered call state U4, on receipt of a CONNECT message containing an information
element, which is not within the context of the base specification,
sends no message and enters the Active call state U10 in the interface with the called endpoint
and
sends a CONNECT message to the calling Gatekeeper and enters the Active call state U10 in the interface with the
calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.7.1 [4]
BCC_DGK_S_U04_09Tx no message, enter Active call state U10, Tx CONNECT, enter Active call state U10
Ensure that the IUT in the Call Delivered call state U4, on receipt of a CONNECT message containing a non-mandatory
information element with content error,
sends no message and enters the Active call state U10 in the interface with the called endpoint
and
sends a CONNECT message to the calling Gatekeeper and enters the Active call state U10 in the interface with the
calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.7.2 [4]
H225/
BCC/
DestinationGatekeeper/
SyntacticallyInvalid/
U10
BCC_DGK_S_U10_01Tx no message, enter Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message containing an
erroneous protocol discriminator information element, coded other than 08H,
sends no message and remains in the Active call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.1 [4]
BCC_DGK_S_U10_02Tx no message, enter Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a message which is too short to contain a complete
message type information element,
sends no message and remains in the Active call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.2 [4]
BCC_DGK_S_U10_03Tx no message, enter Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message containing an invalid
call reference information element format (octet 1, bits 8 to 5 != 0000B),
sends no message and remains in the Active call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.3.1 [4]
BCC_DGK_S_U10_04Tx no message, enter Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message containing an invalid
call reference information element format (octet 1, bits 4 to 1, length too high),
sends no message and remains in the Active call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.3.1 [4]
BCC_DGK_S_U10_05Tx no message, enter Active call state U10
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message containing the
dummy call reference,
sends no message and remains in the Active call state U10.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.3.1 [4]
BCC_DGK_S_U10_06Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message with a mandatory
information element missing,
enters the Null call state U0 in the interface with the called endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the Null call state U0 in the
interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.6.1 [4]
BCC_DGK_S_U10_07Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message containing a
mandatory information element with content error,
enters the Null call state U0 in the interface with the called endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the Null call state U0 in the
interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.6.2 [4]
BCC_DGK_S_U10_08Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message containing an
information element, which is not within the context of the base specification,
enters the Null call state U0 in the interface with the called endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the Null call state U0 in the
interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.7.1 [4]
BCC_DGK_S_U10_09Close call signalling channel, enter Null call state U0, Tx RELEASE COMPLETE, enter Null call state U0
Ensure that the IUT in the Active call state U10, on receipt of a RELEASE COMPLETE message containing a nonmandatory
information element with content error,
enters the Null call state U0 in the interface with the called endpoint
and
sends the RELEASE COMPLETE message to the calling Gatekeeper and enters in the Null call state U0 in the
interface with the calling Gatekeeper.
User Action:
Config: A
SUT: Gatekeeper
Status:
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.8.7.1 [4]
H225/
MISC
RAS_TE_URQ_REJ_1Tx URQ with info Rx from URJ
Ensure that the IUT receive URJ with alternate GK.
receipt URJ from GK with altGKInfo, it should send another URQ to
a gatekeeperIdentifier from altGKInfo that rx from the URJ.
ref:CSCed90966
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[1] subclause 7.2.2[2] subclause 7.9[3]
RAS_TE_REG_0xTx RRQ
Ensure that the IUT before attempting a call, sends a RRQ message.
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 5.2.1.1[1] subclause 7.2.2[2] subclause 7.9[3]
CS_TE_Out_FastStart_01Outgoing faststart call to SUT
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
CS_TE_Out_H245_Video_02Outgoing slow-start H.245 video call to SUT
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
CS_TE_Out_H245_Video_TC97_2_aOutgoing slow-start H.245 video call to SUT. Check when CCM is Master side, it should
return OpenLogicalChannelReject with InvalidSessionID when receives SessionID=2 before it sends OLC.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
CS_TE_Out_H245_Video_TC97_2_bOutgoing slow-start H.245 video call to SUT. Check when CCM is Master side, it should
return OpenLogicalChannelReject with InvalidSessionID when receive undefined session ID,
e.g. sessionID = 4.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
BCC_FastStart_In_01Faststart IUT originated call
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_FastStart_In_Facility_collisionFaststart IUT originated call, and FACILITY/starth245 collision
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
BCC_FastStart_In_Facility_collision_2Faststart IUT originated call, and FACILITY/starth245 collision
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
SETUP_QSIG_01Sends SETUP with QSIG content to SUT
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
Send_STATUS_ENQSend STATUS_ENQ
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
Send_STATUSSend STATUS
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
Send_FACILITYSend FACILITY
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
Send_NOTIFYSend NOTIFY
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
Send_RELCOMPSend RELCOMP
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) clauses 8.1 [2], clauses 7.1, 7.3.10 [3]
Send_RELCOMP_NoCauseSend RELCOMP with No Cause
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11)
Test_1Del me
Del me
CS_TE_Out_H245_Audio_01Outgoing slow-start H.245 audio call to SUT
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
IPIPGW_V_01IPIPGW Call flow
Note: FastStart only.
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
IPIPGW_V_02IPIPGW H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
IPIPGW_V_03Responder for IPIPGW H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
Raw_01Demonstrate how to use H323 Raw message
User Action:
Config: A
SUT: Terminal
Status: -
Ref:
BCC_TE_EXAMPLE_PROGRESS_INDSend ALERTING and CALL PROCEEDING with Progess Indicator

User Action: Make a call from the Terminal IUT.
Config: A
SUT: Terminal
Status: -
Ref: -
H245
H245/
OE
H245/
OE/
TC_OE_CEP_BV
TC_OE_CEP_BV_01Start timer T101, enter outgoing CESE state 1
Ensure that the IUT, having sent a valid TerminalCapabilitySet message, starts timer T101 and enters outgoing CESE state 1: Awaiting Response.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_CEP_BV_02Reset timer T101, enter outgoing CESE state 0
Ensure that the IUT, on receipt of a TerminalCapabilitySetAck message and if the sequence number field is set to the variable out_SQ, resets timer T101 enters outgoing CESE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_CEP_BV_03Remain in the outgoing CESE state 1
Ensure that the IUT, on receipt of a TerminalCapabilitySetAck message and if the sequence number field is not set to the variable out_SQ, remains in the outgoing CESE state 1: Awaiting Response
User Action: Off-hook phone when it rings
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_CEP_BV_04Reset timer T101 enters outgoing CESE state 0
Ensure that the IUT, on receipt of a TerminalCapabilitySetReject message and if the sequence number field is set to the variable out_SQ, resets timer T101 enters outgoing CESE state 0: Idle
User Action: Off-hook phone when it rings
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_CEP_BV_05Remain in the outgoing CESE state 1
Ensure that the IUT, on receipt of a TerminalCapabilitySetReject message and if the sequence number field is not set to the variable out_SQ, remains in the outgoing CESE state 1
User Action: Off-hook phone when it rings
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_CEP_BV_06Tx a TerminalCapabilitySetRelease message, enter outgoing CESE state 0
Ensure that the IUT, upon the expiry of timer T101, sends a TerminalCapabilitySetRelease message, and enters outgoing CESE state 0: Idle.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
OE/
TC_OE_CEP_BO
TC_OE_CEP_BO_01Remain in outgoing CESE state 0
Ensure that the IUT on receipt of a TerminalCapabilitySetAck message remains in outgoing CESE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_CEP_BO_02Remain in outgoing CESE state 0
Ensure that the IUT on receipt of a TerminalCapabilitySetReject message remains in outgoing CESE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
OE/
TC_OE_MSD_BV
TC_OE_MSD_BV_01Start timer T106, enter MSDSE state 1
Ensure that the IUT, having sent a valid MasterSlaveDetermination message, starts timer T106 and enters MSDSE state 1: Outgoing Awaiting Response
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MSD_BV_02Reset timer T106, enter MSDSE state 0
Ensure that the IUT, on receipt of a MasterSlaveDeterminationAck message, resets timer T106 and enters MSDSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MSD_BV_03Reset timer T106, enter MSDE state 0
Ensure that the IUT, on receipt of a MasterSlaveDeterminationReject message, resets timer T106 and if the state variable sv_NCOUNT is greater than or equal to N100, enters MSDSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MSD_BV_04Tx MasterSlaveDetermination, set timer T106 and remain in the same state
Ensure that the IUT, on receipt of a MasterSlaveDeterminationReject message, if the state variable sv_NCOUNT is not greater than or equal to N100 sends a MasterSlaveDetermination message, sets timer T106 and remains in the same state
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MSD_BV_05Start timer T103, enter outgoing LCSE state 1
Ensure that the IUT, having sent a valid OpenLogicalChannel message, starts timer T103 and enters outgoing LCSE state 1: Awaiting Establishment.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MSD_BV_05_OLDStart timer T103 and enters outgoing LCSE state 1
Ensure that the IUT, having sent a valid OpenLogicalChannel message, starts timer T103 and enters outgoing LCSE state 1: Awaiting Establishment.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MSD_BV_06Sends a MasterSlaveDeterminationRelease message, and enters MSDSE state 0
Ensure that the IUT, upon the expiry of timer T106, sends a MasterSlaveDeterminationRelease message, and enters MSDSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MSD_BV_07Sends a MasterSlaveDeterminationRelease message, and enters MSDSE state 0
Ensure that the IUT, upon the expiry of timer T106, sends a MasterSlaveDeterminationRelease message, and enters MSDSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MSD_BV_08Resets timer T106 and enters the Idle state
Ensure that the IUT, on receipt of a MasterSlaveDetermination message, if the variable sv_STATUS set to indeterminate and if the variable sv_NCOUNT is greater than or equal to N100, resets timer T106 and enters the Idle state
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MSD_BV_09Resets timer T106 and enters the Idle state
Ensure that the IUT, on receipt of a MasterSlaveDetermination message, if the variable sv_STATUS set to indeterminate and if the variable sv_NCOUNT is greater than or equal to N100, resets timer T106 and enters the Idle state
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
OE/
TC_OE_MSD_BO
TC_OE_MSD_BO_01Remains in MSDSE state 0
Ensure that the IUT on receipt of a MasterSlaveDeterminationAck message remains in MSDSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MSD_BO_02Sends a MasterSlaveDetermination message, sets timer T106 and remains in the same state
Ensure that the IUT, on receipt of a MasterSlaveDeterminationReject message, if the state variable sv_NCOUNT is not greater than or equal to N100 sends a MasterSlaveDetermination message, sets timer T106 and remains in the same state
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MSD_BO_03Remains in MSDSE state 0
Ensure that the IUT on receipt of a MasterSlaveDeterminationRelease message remains in MSDSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
OE/
TC_OE_LCS_BV
TC_OE_LCS_BV_01Starts timer T103 and enters outgoing LCSE state 1
Ensure that the IUT, having sent a valid OpenLogicalChannel message, starts timer T103 and enters outgoing LCSE state 1: Awaiting Establishment.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_02Resets timer T103 enters outgoing LCSE state 2
Ensure that the IUT, on receipt of an OpenLogicalChannelAck message, resets timer T103 enters outgoing LCSE state 2: Established
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_02_V2Resets timer T103 enters outgoing LCSE state 2
Ensure that the IUT, on receipt of an OpenLogicalChannelAck message, resets timer T103 enters outgoing LCSE state 2: Established.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_03Resets timer T103 enters outgoing LCSE state 0
Ensure that the IUT, on receipt of an OpenLogicalChannelReject message, resets timer T103 enters outgoing LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_04Remains in the outgoing LCSE state 1
Ensure that the IUT, on receipt of a CloseLogicalChannelAck message, remains in the outgoing LCSE state 1: Awaiting Establishment
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_05Restarts timer T103, sends CloseLogicalChannel message and enters outgoing LCSE state 3
Ensure that the IUT, on receipt of a RELEASE_REQUEST from its upper layer, restarts timer T103, sends CloseLogicalChannel message and enters outgoing LCSE state 3: Awaiting Release
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_06Sends CloseLogicalChannel message and enters in the outgoing LCSE state 0
Ensure that the IUT, upon the expiry of timer T103, sends CloseLogicalChannel message and enters in the outgoing LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_07Sets timer T103, sends CloseLogicalChannel message and enters outgoing LCSE state 3
Ensure that the IUT, on receipt of a RELEASE_REQUEST from its upper layer, sets timer T103, sends CloseLogicalChannel message and enters outgoing LCSE state 3: Awaiting Release
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_08Enters in outgoing LCSE state 0
Ensure that the IUT on receipt of an OpenLogicalChannelReject message enters in outgoing LCSE state 0: Released.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_09Enters in outgoing LCSE state 0
Ensure that the IUT on receipt of a CloseLogicalChannelAck message enters in outgoing LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_10Reset timer T103, enter LCSE state 0
Ensure that the IUT, on receipt of a CloseLogicalChannelAck message, resets timer T103 enters outgoing LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_11Resets timer T103 enters outgoing LCSE state 0
Ensure that the IUT, on receipt of an OpenLogicalChannelReject message, resets timer T103 enters outgoing LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_12Remains in the outgoing LCSE state 3
Ensure that the IUT, on receipt of an OpenLogicalChannelAck message remains in the outgoing LCSE state 3: Awaiting Release.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_13Enters in the outgoing LCSE state 0
Ensure that the IUT, upon the expiry of timer T103 enters in the outgoing LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_14Resets timer T103,sends OpenLogicalChannel message and enters outgoing LCSE state 1
Ensure that the IUT, on receipt of a RELEASE_REQUEST from its upper layer, resets timer T103,
sends OpenLogicalChannel message and enters outgoing LCSE state 1: Awaiting Establishment.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BV_NKResets timer T103 enters outgoing LCSE state 2
Ensure that the IUT, on receipt of an OpenLogicalChannelAck message, resets timer T103 enters outgoing LCSE state 2: Established.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
OE/
TC_OE_LCS_BO
TC_OE_LCS_BO_01Remains in outgoing LCSE state 0
Ensure that the IUT on receipt of an OpenLogicalChannelAck message remains in outgoing LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BO_02Remains in outgoing LCSE state 0
Ensure that the IUT on receipt of an OpenLogicalChannelReject message remains in outgoing LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BO_03Message remains in outgoing LCSE state 0
Ensure that the IUT on receipt of a CloseLogicalChannelAck message remains in outgoing LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_LCS_BO_04Remains in outgoing LCSE state 2
Ensure that the IUT on receipt of an OpenLogicalChannelAck message remains in outgoing LCSE state 2: Established.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
OE/
TC_OE_CLC_BV
TC_OE_BLC_BV_01Starts timer T103 and enters outgoing B-LCSE state 1
Ensure that the IUT, having sent a valid OpenLogicalChannel message, starts timer T103 and enters outgoing B-LCSE state 1: Awaiting Establishment.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_02Resets timer T103 enters outgoing B-LCSE state 2
Ensure that the IUT, on receipt of an OpenLogicalChannelAck message, resets timer T103 enters outgoing B-LCSE state 2: Established
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_03Resets timer T103 enters outgoing B-LCSE state 0
Ensure that the IUT, on receipt of an OpenLogicalChannelReject message, resets timer T103 enters outgoing B-LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_04Remains in the outgoing B-LCSE state 1
Ensure that the IUT, on receipt of a CloseLogicalChannelAck message, remains in the outgoing B-LCSE state 1: Awaiting Establishment
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_05Restarts timer T103, sends CloseLogicalChannel message and enters outgoing B-LCSE state 3
Ensure that the IUT, on receipt of a RELEASE_REQUEST from its upper layer, restarts timer T103, sends CloseLogicalChannel message and enters outgoing B-LCSE state 3: Awaiting Release
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_06Sends CloseLogicalChannel message and enters in the outgoing B-LCSE state 0
Ensure that the IUT, upon the expiry of timer T103, sends CloseLogicalChannel message and enters in the outgoing B-LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_07Sets timer T103, sends CloseLogicalChannel message and enters outgoing B-LCSE state 3
Ensure that the IUT, on receipt of a RELEASE_REQUEST from its upper layer, sets timer T103, sends CloseLogicalChannel message and enters outgoing B-LCSE state 3: Awaiting Release
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_08Enters in outgoing B-LCSE state 0
Ensure that the IUT on receipt of an OpenLogicalChannelReject message enters in outgoing B-LCSE state 0: Released.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_09Enters in outgoing B-LCSE state 0
Ensure that the IUT on receipt of a CloseLogicalChannelAck message enters in outgoing B-LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_10Resets timer T103 enters outgoing B-LCSE state 0
Ensure that the IUT, on receipt of a CloseLogicalChannelAck message, resets timer T103 enters outgoing B-LCSE state 0: Released
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_11Resets timer T103 enters outgoing B-LCSE state 0
Ensure that the IUT, on receipt of a OpenLogicalChannelReject message, resets timer T103 enters outgoing B-LCSE state 0: Released.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_12Remains in the outgoing B-LCSE state 3
Ensure that the IUT, on receipt of an OpenLogicalChannelAck message remains in the outgoing B-LCSE state 3: Awaiting Release.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_13Enters in the outgoing B-LCSE state 0
Ensure that the IUT, upon the expiry of timer T103 enters in the outgoing B-LCSE state 0: Released.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BV_14Sends OpenLogicalChannel message and enters outgoing B-LCSE state 1
Ensure that the IUT, on receipt of a RELEASE_REQUEST from its upper layer, resets timer T103, sends OpenLogicalChannel message and enters outgoing B-LCSE state 1: Awaiting Establishment.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
OE/
TC_OE_BLC_BO
TC_OE_BLC_BO_01Remains in outgoing B-LCSE state 0
Ensure that the IUT on receipt of an OpenLogicalChannelAck message remains in outgoing B-LCSE state 0: Released.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BO_02Remains in outgoing B-LCSE state 0
Ensure that the IUT on receipt of an OpenLogicalChannelReject message remains in outgoing B-LCSE state 0: Released.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_BO_03Remains in outgoing B-LCSE state 0
Ensure that the IUT on receipt of a CloseLogicalChannelAck message remains in outgoing B-LCSE state 0: Released.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_BLC_B0_04Remains in outgoing B-LCSE state 2
Ensure that the IUT on receipt of an OpenLogicalChannelAck message remains in outgoing B-LCSE state 2: Established.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
OE/
TC_OE_CLC_BV
TC_OE_CLC_BV_01Starts timer T108 and enters outgoing CLCSE state 1
Ensure that the IUT, having sent a valid RequestChannelClose message, starts timer T108 and enters outgoing CLCSE state 1: Awaiting Response.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_CLC_BV_02Resets timer T108 enters outgoing CLCSE state 0
Ensure that the IUT, on receipt of a RequestChannelCloseAck message, resets timer T108 enters outgoing CLCSE state 0: Idle.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_CLC_BV_03Resets timer T108 enters outgoing CLCSE state 0
Ensure that the IUT, on receipt of a RequestChannelCloseAck message, resets timer T108 enters outgoing CLCSE state 0: Idle.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_CLC_BV_04Enters in the outgoing CLCSE state 0
Ensure that the IUT, upon the expiry of timer T108, enters in the outgoing CLCSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
OE/
TC_OE_CLC_BO
TC_OE_CLC_BO_01Remains in outgoing CLCSE state 0
Ensure that the IUT on receipt of a RequestChannelCloseAck message remains in outgoing CLCSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_CLC_BO_02Remains in outgoing CLCSE state 0
Ensure that the IUT on receipt of a RequestChannelCloseReject message remains in outgoing CLCSE state 0: Idle.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
OE/
TC_OE_MRS_BV
TC_OE_MRS_BV_01Starts timer T109 and enters outgoing MRSE state 1
Ensure that the IUT, having sent a valid RequestMode message, starts timer T109 and enters outgoing MRSE state 1: Awaiting Response.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MRS_BV_02Starts timer T109 and enters outgoing MRSE state 1
Ensure that the IUT, having sent a valid RequestMode message, starts timer T109 and enters outgoing MRSE state 1: Awaiting Response.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MRS_BV_03Remains in the outgoing MRSE state 1
Ensure that the IUT, on receipt of a RequestModeAck message and if the sequence number field is not set to the variable out_SQ, remains in the outgoing MRSE state 1: Awaiting Response.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MRS_BV_04Resets timer T109 enters outgoing MRSE state 0
Ensure that the IUT, on receipt of a RequestModeReject message and if the sequence number field is set to the variable out_SQ, resets timer T109 enters outgoing MRSE state 0: Idle.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MRS_BV_05Remains in the outgoing MRSE state 1
Ensure that the IUT, on receipt of a RequestModeReject message and if the sequence number field is not set to the variable out_SQ, remains in the outgoing MRSE state 1: Awaiting Response.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MRS_BV_06Restarts timer T109, sends a RequestMode message and remains in the outgoing MRSE state 1
Ensure that the IUT, on receipt of a TRANSFER_REQUEST from its upper layer, restarts timer T109, sends a RequestMode message and remains in the outgoing MRSE state 1: Awaiting Response.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MRS_BV_07Sends a RequestModeRelease message, and enters outgoing MRSE state 0
Ensure that the IUT, upon the expiry of timer T109, sends a RequestModeRelease message, and enters outgoing MRSE state 0: Idle.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
OE/
TC_OE_MRS_BO
TC_OE_MRS_BO_01Message remains in outgoing MRSE state 0
Ensure that the IUT on receipt of a RequestModeAck message remains in outgoing MRSE state 0: Idle.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_OE_MRS_BO_02Message remains in outgoing MRSE state 0
Ensure that the IUT on receipt of a RequestModeReject message remains in outgoing MRSE state 0: Idle.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
TE
H245/
TE/
TC_TE_CEP_BV
TC_TE_CEP_BV_01Enters the incoming CESE state 1
Ensure that the IUT, on receipt of a TerminalCapabilitySet message, enters the incoming CESE state 1: Awaiting Response
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_CEP_BV_02Sends a TerminalCapabilitySetAck message and enters the incoming CESE state 0
Ensure that the IUT, on receipt of a TRANSFER_RESPONSE from its upper layer, sends a TerminalCapabilitySetAck message and enters the incoming CESE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_CEP_BV_03Sends a TerminalCapabilitySetReject message and enters the incoming CESE state 0
Ensure that the IUT, on receipt of a REJECT_REQUEST from its upper layer, sends a TerminalCapabilitySetReject message and enters the incoming CESE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
TE/
TC_TE_CEP_BO
TC_TE_CEP_BO_01Sends a TerminalCapabilitySetAck message and enters the incoming CESE state 0
Ensure that the IUT, on receipt of a TRANSFER_RESPONSE from its upper layer, sends a TerminalCapabilitySetAck message and enters the incoming CESE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_CEP_BO_02Remains in the incoming CESE state 1
Ensure that the IUT, on receipt of a TerminalCapabilitySet message, remains in the incoming CESE state 1: Awaiting Response.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
TE/
TC_TE_MSD_BV
TC_TE_MSD_BV_01Sends a MasterSlaveReject message and remains in MSDSE state 0
Ensure that the IUT, on receipt of a MasterSlaveDetermination message and if the variable sv_STATUS is set to indeterminate, sends a MasterSlaveReject message and remains in MSDSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MSD_BV_02Sends a MasterSlaveDeterminationAck message, sets timer T106 and enters MSDSE state 2
Ensure that the IUT, on receipt of a MasterSlaveDetermination message and if the variable sv_STATUS is set to master/slave, sends a MasterSlaveDeterminationAck message, sets timer T106 and enters MSDSE state 2: Incoming Awaiting Response.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MSD_BV_03Resets timer T106 and enters MSDSE state 0
Ensure that the IUT, on receipt of a MasterSlaveDeterminationAck message, resets timer T106 and enters MSDSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MSD_BV_04Resets timer T106 and enters MSDSE state 0
Ensure that the IUT, on receipt of a MasterSlaveDetermination message, resets timer T106 and enters MSDSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MSD_BV_05Resets timer T106 and enters MSDSE state 0
Ensure that the IUT, on receipt of a MasterSlaveDeterminationReject message, resets timer T106 and enters MSDSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MSD_BV_06Resets timer T106 and enters MSDSE state 0
Ensure that the IUT, on receipt of a MasterSlaveDeterminationRelease message, resets timer T106 and enters MSDSE state 0: Idle
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MSD_BV_07Resets timer T106 and enters MSDSE state 0
Ensure that the IUT, upon the expiry of timer T106, resets timer T106 and enters MSDSE state 0: Idle.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
TE/
TC_TE_MSD_BO
TC_TE_MSD_BO_01Remains in MSDSE state 0
Ensure that the IUT on receipt of a MasterSlaveDeterminationAck message remains in MSDSE state 0: Idle.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MSD_BO_02Remains in MSDSE state 0
Ensure that the IUT on receipt of a MasterSlaveDeterminationReject message remains in MSDSE state 0: Idle.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MSD_BO_03Remains in MSDSE state 0
Ensure that the IUT on receipt of a MasterSlaveDeterminationRel message remains in MSDSE state 0: Idle.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
TE/
TC_TE_LCS_BV
TC_TE_LCS_BV_01Enters the incoming LCSE state 1
Ensure that the IUT, on receipt of an OpenLogicalChannel message, enters the incoming LCSE state 1: Awaiting Establishment.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_LCS_BV_02Sends an OpenLogicalChannelAck message and enters the incoming LCSE state 2
Ensure that the IUT, on receipt of an OpenLogicalChannel message, sends an OpenLogicalChannelAck message and enters the incoming LCSE state 2: Established.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_LCS_BV_03Sends an OpenLogicalChannelReject message and enters the incoming LCSE state 0
Ensure that the IUT, on receipt of a RELEASE_REQUEST from its upper layer, sends an OpenLogicalChannelReject message and enters the incoming LCSE state 0: Released.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_LCS_BV_04Sends a CloseLogicalChannelAck message, and enters the incoming LCSE state 0
Ensure that the IUT, on receipt of a CloseLogicalChannel message, sends a CloseLogicalChannelAck message, and enters the incoming LCSE state 0: Released.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_LCS_BV_05Sends a CloseLogicalChannelAck message, and enters the incoming LCSE state 0
Ensure that the IUT, on receipt of a CloseLogicalChannel message, sends a CloseLogicalChannelAck message, and enters the incoming LCSE state 0: Released.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_LCS_BV_06Enters the incoming LCSE state 1
Ensure that the IUT, on receipt of an OpenLogicalChannel message, enters the incoming LCSE state 1: Awaiting Establishment.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
TE/
TC_TE_LCS_B0
TC_TE_LCS_B0_01Sends a CloseLogicalChannelAck message and remains in the incoming LCSE State 0
Ensure that the IUT, on receipt of a CloseLogicalChannel message, sends a CloseLogicalChannelAck message and remains in the incoming LCSE State 0: Released.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_LCS_B0_02Remains in the incoming LCSE state 1
Ensure that the IUT, on receipt of an OpenLogicalChannel message, remains in the incoming LCSE state 1: Awaiting Establishment.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
TE/
TC_TE_BLC_BV
TC_TE_BLC_BV_01Enters the incoming B-LCSE state 1
Ensure that the IUT, on receipt of an OpenLogicalChannel message, enters the incoming B-LCSE state 1: Awaiting Establishment.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_BV_02Sends an OpenLogicalChannelAck message, sets the timer T103 and enters the incoming B-LCSE state 2
Ensure that the IUT, on receipt of a ESTABLISH_RESPONSE from its upper layer, sends an OpenLogicalChannelAck message, sets the timer T103 and enters the incoming B-LCSE state 2:
Awaiting Confirmation.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_BV_03Sends an OpenLogicalChannelReject message, and enters the incoming B-LCSE State 0
Ensure that the IUT, on receipt of a RELEASE_REQUEST from its upper layer, sends an OpenLogicalChannelReject message, and enters the incoming B-LCSE State 0: Released.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_BV_04Sends a CloseLogicalChannelAck message, and enters the incoming B-LCSE State 0
Ensure that the IUT, on receipt of a CloseLogicalChannel message, sends a CloseLogicalChannelAck message, and enters the incoming B-LCSE State 0: Released.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_BV_05Enters the incoming B-LCSE State 0
Ensure that the IUT, upon the expiry of timer T103, enters the incoming B-LCSE State 0: Released.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_BV_06Resets timer T103 and enters the incoming B-LCSE State 3
Ensure that the IUT, on receipt of an OpenLogicalChannelConfirm message, resets timer T103 and enters the incoming B-LCSE State 3: Established.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_BV_07Resets timer T103, sends a CloseLogicalChannelAck message and enters the incoming B-LCSE State 0
Ensure that the IUT, on receipt of a CloseLogicalChannel message, resets timer T103, sends a CloseLogicalChannelAck message and enters the incoming B-LCSE State 0: Released.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_BV_08Resets timer T103 and enters the incoming B-LCSE State 1
Ensure that the IUT, on receipt of an OpenLogicalChannel message, resets timer T103 and enters the incoming B-LCSE State 1: Awaiting Establishment.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_BV_09Enters the incoming B-LCSE State 1
Ensure that the IUT, on receipt of an OpenLogicalChannel message, enters the incoming B-LCSE State 1: Awaiting Establishment
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_BV_10Sends a CloseLogicalChannelAck message and enters the incoming B-LCSE State 0
Ensure that the IUT, on receipt of a CloseLogicalChannel message, sends a CloseLogicalChannelAck message and enters the incoming B-LCSE State 0: Released.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
TE/
TC_TE_BLC_BO
TC_TE_BLC_B0_01Remains in the incoming B-LCSE State 0
Ensure that the IUT, on receipt of a OpenLogicalChannelConfirm message, remains in the incoming B-LCSE State 0: Released.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_B0_02Sends a CloseLogicalChannelAck message and remains in the incoming B-LCSE State 0
Ensure that the IUT, on receipt of a CloseLogicalChannel message, sends a CloseLogicalChannelAck message and remains in the incoming B-LCSE State 0: Released.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_B0_03Remains in the incoming B-LCSE state 1
Ensure that the IUT, on receipt of an OpenLogicalChannel message, remains in the incoming B-LCSE state 1: Awaiting Establishment.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_B0_04Enters the incoming B-LCSE State 0
Ensure that the IUT, on receipt of an OpenLogicalChannelConfirm message, enters the incoming B-LCSE State 0: Released.
User Action: Off-hook phone when it rings.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_BLC_B0_05Remains in the incoming B-LCSE state 3
Ensure that the IUT, on receipt of an OpenLogicalChannelConfirm message, remains in the incoming B-LCSE state 3: Established.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
TE/
TC_TE_CLC_BV
TC_TE_CLC_BV_01Enters the incoming CLCSE state 1
Ensure that the IUT, on receipt of a RequestChannelClose message, enters the incoming CLCSE state 1: Awaiting Response.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_CLC_BV_02Sends a RequestChannelCloseAck message, and enters the incoming CLCSE state 0
Ensure that the IUT, on receipt of a CLOSE_RESPONSE from its upper layer, sends a RequestChannelCloseAck message, and enters the incoming CLCSE state 0: Idle.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_CLC_BV_03Sends a RequestChannelCloseReject message, and enters the incoming CLCSE state 0
Ensure that the IUT, on receipt of a REJECT_REQUEST from its upper layer, sends a RequestChannelCloseReject message, and enters the incoming CLCSE state 0: Idle.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_CLC_BV_04Enters the incoming CLCSE state 0
Ensure that the IUT, on receipt of a RequestChannelCloseRelease message, enters the incoming CLCSE state 0: Idle.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
TE/
TC_CLC_BO
TC_TE_CLC_B0_01Enters the incoming CLCSE state 0
Ensure that the IUT, on receipt of a RequestChannelCloseRelease message, enters the incoming CLCSE state 0: Idle.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_CLC_B0_02Remains in incoming CLCSE state 1
Ensure that the IUT, on receipt of a RequestChannelClose message remains in incoming CLCSE state 1: Awaiting Response.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
H245/
TE/
TC_TE_MRS_BV
TC_TE_MRS_BV_01Enters the incoming MRSE state 1
Ensure that the IUT, on receipt of a RequestMode message, enters the incoming MRSE state 1: Awaiting Response.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MRS_BV_02Sends a RequestModeAck message, enters the incoming MRSE state 0
Ensure that the IUT, on receipt of a TRANSFER_RESPONSE from its upper layer, sends a RequestModeAck message, enters the incoming MRSE state 0: Idle.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MRS_BV_03Sends a RequestModeReject message, enters the incoming MRSE state 0
Ensure that the IUT, on receipt of a REJECT_REQUEST from its upper layer, sends a RequestModeReject message, enters the incoming MRSE state 0: Idle.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MRS_BV_04Enters the incoming MRSE state 0
Ensure that the IUT, on receipt of a RequestModeRelease message, enters the incoming MRSE state 0: Idle.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MRS_BO_01Remains in the incoming MRSE state 0
Ensure that the IUT on receipt of a RequestModeRelease message remains in the incoming MRSE state 0: Idle.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
TC_TE_MRS_BO_02Remains in the incoming MRSE state 1
Ensure that the IUT on receipt of a RequestMode message remains in the incoming MRSE state 1: Awaiting Response.
User Action: Off-hook phone when it rings. Hangup when prompted.
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
Choctaw_TSTest ECS Call Flows for Supplementary features
Choctaw_FS_1test fast Start Call
Choctaw_FS_2test fast Start Call
CH_IN_SS_1Incoming Slow Start Call
Incoming Slow Start Call
CH_IN_SS_LCL_ECS_1Incoming Slow Start Call
Incoming Slow Start Call
CH_IN_SS_LCL_ECS_2Incoming Slow Start Call - with ECS Call flow
CH_IN_FS_LCL_ECS_3Incoming Fast Start Call - with ECS Call flow (Connect with tunneling false and no h245 address)
CH_IN_FS_LCL_ECS_6Incoming Fast Start Call - with ECS Call flow (Connect with tunneling true
and no h245 address)
CH_IN_FS_LCL_ECS_7Incoming Fast Start Call - with tunneled messages
CH_IN_FS_LCL_ECS_4Incoming Fast Start Call - with ECS Call flow - h245 address in connect
CH_IN_FS_LCL_ECS_5Incoming Fast Start Call - with ECS Call flow - h245 address in connect and tunneling true
Choctaw_TS_C1Test ECS Call Flows for Supplementary features
DSP_IS_REPRDIncoming Fast Start Call -
CH_OG_SS_11Outgoing slow-start H.245audio call to SUT
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
Choctaw_FS_1_C1test fast Start Call
Choctaw_FS_2_C1test fast Start Call
CH_IN_SS_1_C1Incoming Slow Start Call
Incoming Slow Start Call
CH_OG_SS_1Outgoingslowstart call - h245 address in setup
Outgoingslowstart call - h245 address in setup
CH_IN_SS_LCL_ECS_1_C1Incoming Slow Start Call
Incoming Slow Start Call
CH_IN_SS_LCL_ECS_2_C1Incoming Slow Start Call - with ECS Call flow
CH_IN_SS_NOMSDSCK_ECS_2Incoming Slow Start Call - with ECS Call flow
CH_IN_SS_REQCLOSE_ECS_10Incoming Slow Start Call - with ECS Call flow. request close logical channel
CH_IN_FS_LCL_ECS_3_C1Incoming Fast Start Call - with ECS Call flow (Connect with tunneling false and no h245 address)
CH_IN_FSTUNN_LCL_ECS_1Incoming Fast Start Call - with ECS Call flow (Connect with tunneling false and no h245 address)
CH_IN_FS_LCL_ECS_6_C1Incoming Fast Start Call - with ECS Call flow (Connect with tunneling true
and no h245 address)
CH_IN_FS_1Incoming Fast Start Call
CH_IN_FS_LCL_ECS_7_C1Incoming Fast Start Call - with tunneled messages
CH_IN_FS_LCL_ECS_4_C1Incoming Fast Start Call - with ECS Call flow - h245 address in connect
CH_IN_FS_LCL_ECS_5_C1Incoming Fast Start Call - with ECS Call flow - h245 address in connect and tunneling true
CH_IN_SS_LCL_NOCLC_8Incoming Slow Start Call - do not respond with CLC for a ECS
CH_IN_SS_LCL_NOCLCACK_8Incoming Slow Start Call - Do not send CLC ACK
Choctaw_TS_C1/
ECS_STATEMACHINE		All Test cases related to ECS State Machine
CH_IN_FS_H323_72_1Incoming Fast Start Call - with ECS Call flow and MSD Not acknowledged
CH_IN_FS_H323_9Delayed ECS Response - Incoming Fast start Call - Tested OK
CH_IN_FS_H323_99Multiple ECS Ack received - Tested OK
CH_IN_FS_H323_72_1TIncoming Fast Start Call - with ECS Call flow and MSD Not acknowledged - h245 tunnel enabled
CH_IN_SS_h323_75_1Incoming Slow Start Call - with ECS Call flow. OLC No Response
CH_IN_SS_h323_75_1TIncoming Fast Start Call - with ECS Call flow. OLC No Response- H245 Tunnel enabled
CH_IN_SS_h323_74_1Incoming Slow Start Call - with ECS Call flow. OLC Reject
CH_IN_SS_h323_74_1TIncoming Fast Start Call - with ECS Call flow. OLC Reject Tunnel enabled
CH_IN_SS_h323_71_2Incoming Slow Start Call - with ECS Call flow. ECSReject is send
CH_IN_FS_h323_71_2Incoming Fast Start Call - with ECS Call flow. ECSReject is send
CH_IN_FS_h323_71_2TIncoming Fast Start Call - with ECS Call flow. ECSReject is send, tunnel enabled
CH_IN_SS_h323_71_1Incoming Slow Start Call - with ECS Call flow. ECS is not acknowledged
CH_IN_FS_h323_71_1Incoming FAST Start Call - with ECS Call flow. ECS is not acknowledged
CH_IN_FS_h323_71_1TIncoming FAST Start Call - with ECS Call flow. ECS is not acknowledged, Tunnel enabled
CH_IN_FS_h323_76_1Incoming FAST Start Call - with ECS Call flow
CH_IN_SS_h323_72_2Incoming Slow Start Call - with ECS Call flow. MSDRejected
CH_IN_FS_h323_72_2IncomingFast Start Call - with ECS Call flow. MSDRejected
CH_IN_FS_h323_72_2TIncomingFast Start Call - with ECS Call flow. MSDRejected-tunnelenabled
CH_IN_SS_h323_72_1Incoming Slow Start Call - with ECS Call flow. MSD Not acknowledged
CH_IN_FS_h323_78Incoming FAST Start Call - Remote ECS; After Call proceeding
CH_IN_FS_h323_78_1Incoming FAST Start Call - Remote ECS; After Call proceeding with FS
CH_IN_FS_h323_78_1TIncoming FAST Start Call - Remote ECS; After Call proceeding with FS-Tunnel enabled
CH_IN_FS_h323_79_1Incoming FAST Start Call - Remote ECS; After Alerting without FS
CH_IN_FS_h323_79_1TIncoming FAST Start Call - Remote ECS; After Alerting without FS-Tunneled
CH_IN_FS_h323_79_2Incoming FAST Start Call - Remote ECS; After Alerting with FS
CH_IN_FS_h323_79_2TIncoming FAST Start Call - Remote ECS; After Alerting with FS With tunnelled message
CH_IN_FS_h323_79_3Incoming FAST Start Call - Remote ECS; After call proceeding with FS
CH_IN_FS_h323_79_3TIncoming FAST Start Call - Remote ECS; After call proceeding with FS.With tunneled h245
CH_IN_FS_h323_80_1Incoming FAST Start Call - Remote ECS; After Connect without FS
CH_IN_FS_h323_80_1TIncoming FAST Start Call - Remote ECS; After Connect without FS Tunnel enabled
CH_IN_FS_h323_80_2Incoming FAST Start Call - Remote ECS; After Alerting with FS and connect:TESTED OK
CH_IN_FS_h323_80_2TIncoming FAST Start Call - Remote ECS; After Alerting with FS and connect:TESTED OKTunneledmessage
CH_IN_FS_h323_80_3Incoming FAST Start Call - Remote ECS; After call proceeding with FS and alert followed by connect:TestedOK
CH_IN_FS_h323_80_3TIncoming FAST Start Call - Remote ECS; After call proceeding with FS and alert followed by connect:
tunneled
CH_IN_FS_h323_80_4Incoming FAST Start Call - Remote ECS; After call proceeding and alert followed by connect with FS:TestedOK
CH_IN_FS_h323_80_4TIncoming FAST Start Call - Remote ECS; After call proceeding and alert followed by connect with FS:TestedOK
CH_IN_FS_h323_80Incoming FAST Start Call - Remote ECS; After alerting
CH_IN_FS_h323_77_2Incoming FAST Start Call - Remote ECS on recpetion of incoming setup without call proceeding
CH_IN_FS_h323_77_2TIncoming FAST Start Call - Remote ECS on recpetion of incoming setup without call proceeding
CH_IN_FS_h323_82Outgoing FAST Start Call - Remote ECS after sending Call Proceeding without fast start
CH_IN_FS_h323_82Toutgoing FAST Start Call - Remote ECS after sending Call Proceeding without fast start
CH_OG_FS_h323_82outgoing
FAST Start Call - Remote ECS after Recieving CallProceeding - Not work as alerting comes immediately
CH_OG_FS_h323_82_1Toutgoing FAST Start Call - Remote ECS after Recieving CallProceeding
CH_OG_FS_h323_83outgoing
FAST Start Call - Remote ECS after Recieving Alerting
CH_OG_FS_h323_83_1Toutgoing FAST Start Call - Remote ECS after Recieving Alerting
CH_OG_FS_h323_84Outgoing FAST Start Call - Remote ECS after Recieving Connect
CH_OG_FS_h323_84_1Toutgoing FAST Start Call - Remote ECS after Recieving Connect
CH_OG_FS_h323_85Outgoing FAST Start Call - Local ECS after Recieving Connect
CH_OG_FS_h323_85_1Outgoing FAST Start Call - Local ECS after Recieving Connect-H245tunnel
CH_IN_FS_h323_87Incoming FAST Start Call - with ECS Call flow- endsession command
dtmftest
dtmfOutgoing FAST Start Call - Remote ECS after Recieving Connect
RTP
CS_TE_Out_H245_RTPOutgoing slow-start H.245 video call to SUT
Config: A
SUT: Terminal
Status: -
Ref: ACATS H323v2.1
ASNV13Testcase Block to test sanitization function
BasicFastStartTunnelIPIPGW Fast Start Call flow and Tunneling Call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_100_TunnelSending a new choice field in terminalCapabilitySetReject response
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_55_TunnelSending a new choice of field of mediaMode in RequestMode in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_56_TunnelSending a new choice of field of RedundancyEncodingDTMode in RequestMode in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_57_TunnelSending a new choice of field of adaptationLayerType in H223ModeParameters of RequestMode in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_58_TunnelSending a new choice of field of v76ModeParameters in RequestMode in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_59_TunnelSending a new choice of field of secondaryEncoding in H2250ModeParameters field of RequestMode in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_60_TunnelSending a new choice field of VideoMode in RedundancyEncodingDTMode field of RequestMode in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_61_TunnelSending a new choice field of profileAndLevel in H262VideoMode field of RequestMode in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_62_TunnelSending a new choice field of Resolution in H263VideoMode field of RequestMode in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_63_TunnelSending a new choice field of AudioMode in type field of RequestMode in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_64_TunnelSending a new choice field of Application in DataMode field of RequestMode in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_65_TunnelSending a new choice field of in EncryptionMode in RequestMode in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_66_TunnelSending a new choice field in maintenanceLoopRequest in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_67_TunnelSending a new choice field of type in ConferenceRequest in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_68_TunnelSending a new choice field of type in RemoteMCRequest in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_70_TunnelSending a new choice field of newRequestType in maximumHeaderInterval field of MultilinkRequest in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_73_TunnelSending a new choice field of encryptionCommand in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_74_TunnelSending a new choice field of sendTerminalCapabilitySet in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_75_TunnelSending a new choice field of endSessionCommand in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_78_TunnelSending a new choice field of conferenceCommand in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_79_TunnelSending a new choice field of miscellaneousCommand in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_84_TunnelSending a new choice field of miscellaneousIndication in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_85_TunnelSending a new choice field of newATMVCCommand in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_86_TunnelSending a new choice field of newATMVCCommand in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_87_TunnelSending a new choice field of newATMVCCommand in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_88_TunnelSending a new choice field of newATMVCCommand in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_89_TunnelSending a new choice field of newATMVCCommand in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_96_TunnelSending a new choice field of userInput in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_97_TunnelSending a new choice field of userInputSupportIndication in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_103_TunnelSending a new choice field of requestChannelClose in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_54_TunnelSending a new choice of field of modeElementType in RequestMode in a tunnel call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_6_TunnelSending a new type of MuxCap in TCS message after receiving Connect
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_7_TunnelSending a new type of Capability in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_8_TunnelSending a new type of DataApplicationCapability in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_9_TunnelSending a new type of DataProtocolCapability in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_10_TunnelSending a new type of v76WCompression in DataProtocolCapability in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_11_TunnelSending a new type of CompressionType pdu in DataProtocolCapability in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_12_TunnelSending a new type of T38FaxRateManagement pdu in DataApplicationCapability in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_13_TunnelSending a new type of T38FaxUdpEc pdu in t38FaxProfile field in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_14_TunnelSending a new type of CapabilityIdentifier pdu in GenericCapability field in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_15_TunnelSending a new type of ParameterIdentifier pdu in GenericParameter field in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_16_TunnelSending a new type of ParameterValue pdu in GenericParameter field in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_19_TunnelSending a new type of RedundancyEncodingMethod pdu in RedundancyEncodingCapability field in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_20_TunnelSending a new type of VideoCapability pdu in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_21_TunnelSending a new type of VideoBackChannelSend pdu in RefPictureSelection field in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_22_TunnelSending a new type of PixelAspectInfo pdu in CustomPictureFormat field in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_23_TunnelSending a new type of AudioCapability pdu in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_24_TunnelSending a new type of mediaEncryptionAlgorightm pdu in EncryptionCapability field in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_25_TunnelSending a new type of UserCapability pdu in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_26_TunnelSending a new type of MultiplexFormat pdu in MultiplexedStreamCapability field in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_27_TunnelSending a new type of DepFecCapability pdu in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_28_TunnelSending a new type of FrameToThreadMapping pdu in RTPH263VideoRedundancyEncoding in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_29_TunnelSending a new type of CapabilityIdentifier pdu in GenericCapabilityField in TCS message for Tunneled call
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_OG_SS_1_C1Outgoing slowstart call - h245 address in setup
Outgoing slowstart call - h245 address in setup
ASN_IN_SS_1_C1Incoming Slow Start Call
Incoming Slow Start Call
ASNV13_SLOWSTARTTestcases related to slow start
Basic_CallFlowIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
Basic_CallFlow_FSIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
ASN_TC_1Sending a new H.245 message type
Sending a new H.245 message type
ASN_TC_2Sending a new H.245 request message
Sending a new H.245 request message
ASN_TC_3Sending a new H.245 response message
Sending a new H.245 response message
ASN_TC_4Sending a new H.245 command message
Sending a new H.245 command message
ASN_TC_5Sending a new H.245 indication message
Sending a new H.245 indication message
ASN_TC_6Sending a new type of MuxCap in TCS message imm after receiving Connect
Sending a new type of MuxCap in TCS message imm after receiving Connect
ASN_TC_7Sending a new type of capability pdu in TCS message
Sending a new type of capability pdu in TCS message
ASN_TC_8Sending a new type of DataApplicationCapability in TCS message imm after receiving Connect
Sending a new type of DataApplicationCapability in TCS message imm after receiving Connect
ASN_TC_9Sending a new type of DataProtocolCapability in TCS message imm after receiving Connect
Sending a new type of DataProtocolCapability in TCS message imm after receiving Connect
ASN_TC_10Sending a new type of v76WCompression pdu in DataProtocolCapability in TCS message imm after receiving Connect
Sending a new type of v76WCompression pdu in DataProtocolCapability in TCS message imm after receiving Connect
ASN_TC_11Sending a new type of CompressionType pdu in DataProtocolCapability in TCS message imm after receiving Connect
Sending a new type of CompressionType pdu in DataProtocolCapability in TCS message imm after receiving Connect
ASN_TC_12Sending a new type of T38FaxRateManagement pdu in DataApplicationCapability field in TCS message imm after receiving Connect
Sending a new type of T38FaxRateManagement pdu in DataApplicationCapability field in TCS message imm after receiving Connect
ASN_TC_13Sending a new type of t38faxUdpEC pdu in t38FaxProfile field of TCS message imm after receiving Connect
Sending a new type of t38faxUdpEC pdu in t38FaxProfile field of TCS message imm after receiving Connect
ASN_TC_14Sending a new type of CapabilityIdentifier pdu in GenericCapability field in TCS message imm after receiving Connect
Sending a new type of CapabilityIdentifier pdu in GenericCapability field in TCS message imm after receiving Connect
ASN_TC_15Sending a new type of ParameterIdentifier pdu in GenericParameter field in TCS message imm after receiving Connect
Sending a new type of ParameterIdentifier pdu in GenericParameter field in TCS message imm after receiving Connect
ASN_TC_16Sending a new type of ParameterValue pdu in GenericParameter field in TCS message imm after receiving Connect
Sending a new type of ParameterValue pdu in GenericParameter field in TCS message imm after receiving Connect
ASN_TC_17Sending a new type of payloadDescriptor in RTPPayloadType field in OLC message
Sending a new type of payloadDescriptor in RTPPayloadType field in OLC message
ASN_TC_18Sending a new type of mediaTransportType in transportCapabilityType field in OLC message
Sending a new type of mediaTransportType in transportCapabilityType field in OLC message
ASN_TC_19Sending a new type of RedundancyEncodingMethod pdu in RedundancyEncodingCapability field in TCS message imm after receiving Connect
Sending a new type of RedundancyEncodingMethod pdu in RedundancyEncodingCapability field in TCS message imm after receiving Connect
ASN_TC_20Sending a new type of VideoCapability pdu in TCS message imm after receiving Connect
Sending a new type of VideoCapability pdu in TCS message imm after receiving Connect
ASN_TC_21Sending a new type of videoBackChannelSend pdu in RefPictureSelection field in the TCS message imm after receiving Connect
Sending a new type of videoBackChannelSend pdu in RefPictureSelection field in the TCS message imm after receiving Connect
ASN_TC_22Sending a new type of pixelAspectInfo pdu in CustomPictureFormat field in the TCS message imm after receiving Connect
Sending a new type of pixelAspectInfo pdu in CustomPictureFormat field in the TCS message imm after receiving Connect
ASN_TC_23Sending a new type of AudioCapability pdu in TCS message imm after receiving Connect
Sending a new type of AudioCapability pdu in TCS message imm after receiving Connect
ASN_TC_24Sending a new type of mediaEncryptionAlgorithm pdu in EncryptionCapability field in the TCS message imm after receiving Connect
Sending a new type of mediaEncryptionAlgorithm pdu in EncryptionCapability field in the TCS message imm after receiving Connect
ASN_TC_25Sending a new type of UserInputCapability pdu in TCS message imm after receiving Connect
Sending a new type of UserInputCapability pdu in TCS message imm after receiving Connect
ASN_TC_26Sending a new type of MultiplexFormat pdu in MultiplexedStreamCapability field of TCS message imm after receiving Connect
Sending a new type of MultiplexFormat pdu in MultiplexedStreamCapability field of TCS message imm after receiving Connect
ASN_TC_27Sending a new type of DepFecCapability pdu in TCS message imm after receiving Connect
Sending a new type of DepFecCapability pdu in TCS message imm after receiving Connect
ASN_TC_28Sending a new type of FrameToThreadMapping pdu in RTPH263VideoRedundancyEncoding field in TCS message imm after receiving Connect
Sending a new type of FrameToThreadMapping pdu in RTPH263VideoRedundancyEncoding field in TCS message imm after receiving Connect
ASN_TC_29Sending a new type of CapabilityIdentifier pdu in GenericCapability field in TCS message imm after receiving Connect
Sending a new type of CapabilityIdentifier pdu in GenericCapability field in TCS message imm after receiving Connect
ASN_TC_30Sending a new type of QOSMode in TransportCapability field in OLC message
Sending a new type of QOSMode in TransportCapability field in OLC message
ASN_TC_31Sending a new type of newDistribution in NetworkAccessParamters field in OLC message
Sending a new type of newDistribution in NetworkAccessParamters field in OLC message
ASN_TC_32Sending a new type of newNetworkAddress in NetworkAccessParamters field in OLC message
Sending a new type of newNetworkAddress in NetworkAccessParamters field in OLC message
ASN_TC_33Sending a new type of t120SetupProcedure in NetworkAccessParamters field in OLC message
Sending a new type of t120SetupProcedure in NetworkAccessParamters field in OLC message
ASN_TC_34Sending a new type of Q2931Address in NetworkAccessParamters field in OLC message
Sending a new type of Q2931Address in NetworkAccessParamters field in OLC message
ASN_TC_35Sending a new DataType in OLC message
Sending a new DataType in OLC message
ASN_TC_36Sending a new type of AdaptationLayerType in H223LogicalChannelParamters field in OLC message
Sending a new type of AdaptationLayerType in H223LogicalChannelParamters field in OLC message
ASN_TC_37Sending a new type of TransferMode in H223AL1MParamters of H223LogicalChannelParamters field in OLC message
Sending a new type of TransferMode in H223AL1MParamters of H223LogicalChannelParamters field in OLC message
ASN_TC_38Sending a new type of HeaderFEC in H223AL1MParamters of H223LogicalChannelParamters field in OLC message
Sending a new type of HeaderFEC in H223AL1MParamters of H223LogicalChannelParamters field in OLC message
ASN_TC_39Sending a new type of CRCLength in H223AL1MParamters of H223LogicalChannelParamters field in OLC message
Sending a new type of CRCLength in H223AL1MParamters of H223LogicalChannelParamters field in OLC message
ASN_TC_40Sending a new type of ARQType in H223AL1MParamters of H223LogicalChannelParamters field in OLC message
Sending a new type of ARQType in H223AL1MParamters of H223LogicalChannelParamters field in OLC message
ASN_TC_41Sending a new type of HeaderFEC in H223AL2MParamters of H223LogicalChannelParamters field in OLC message
Sending a new type of HeaderFEC in H223AL2MParamters of H223LogicalChannelParamters field in OLC message
ASN_TC_42Sending a new type of HeaderFormat in H223AL3MParamters of H223LogicalChannelParamters field in OLC message
Sending a new type of HeaderFormat in H223AL3MParamters of H223LogicalChannelParamters field in OLC message
ASN_TC_43Sending a new type of CRCLength in H223AL3MParamters of H223LogicalChannelParamters field in OLC message
Sending a new type of CRCLength in H223AL3MParamters of H223LogicalChannelParamters field in OLC message
ASN_TC_44Sending a new type of ARQType in H223AL3MParamters of H223LogicalChannelParamters field in OLC message
Sending a new type of ARQType in H223AL3MParamters of H223LogicalChannelParamters field in OLC message
ASN_TC_45Sending a new choice field of numberofRetransmissions in H223AnnexCArqParamters of H223AL3MParamters of H223LogicalChannelParamters field in OLC message
Sending a new choice field of numberofRetransmissions in H223AnnexCArqParamters of H223AL3MParamters of H223LogicalChannelParamters field in OLC message
ASN_TC_46Sending a new choice field of suspendResume in V76LogicalChannelParameters field in OLC message
Sending a new choice field of suspendResume in V76LogicalChannelParameters field in OLC message
ASN_TC_47Sending a new choice field of Mode in V76LogicalChannelParameters field in OLC message
Sending a new choice field of Mode in V76LogicalChannelParameters field in OLC message
ASN_TC_48Sending a new choice field of Recovery in eRM field of V76LogicalChannelParameters field in OLC message
Sending a new choice field of Recovery in eRM field of V76LogicalChannelParameters field in OLC message
ASN_TC_49Sending a new choice field of crcLength in V76HDLCParamters field of V76LogicalChannelParameters field in OLC message
Sending a new choice field of crcLength in V76HDLCParamters field of V76LogicalChannelParameters field in OLC message
ASN_TC_50Sending a new type of MediaPacketization in H2250LogicalChannelPAramters field in OLC message
Sending a new type of MediaPacketization in H2250LogicalChannelPAramters field in OLC message
ASN_TC_51Sending a new type of newTransportAddress in NetworkAccessParamters field in OLC message
Sending a new type of newTransportAddress in NetworkAccessParamters field in OLC message
ASN_TC_52Sending a new type of newUnicastAddress field of NetworkAccessParamters field in OLC message
Sending a new type of newUnicastAddress field of NetworkAccessParamters field in OLC message
ASN_TC_53Sending a new type of newMulticastAddress field of NetworkAccessParameters field in OLC message
Sending a new type of newMulticastAddress field of NetworkAccessParameters field in OLC message
ASN_TC_54Sending a new choice field of modeElementType in RequestMode message
Sending a new choice field of modeElementType in RequestMode message
ASN_TC_55Sending a new choice field of mediaMode in H235Mode of RequestMode message
Sending a new choice field of mediaMode in H235Mode of RequestMode message
ASN_TC_56Sending a new choice field of Type in primary field of RedundancyEncodingDTMode of RequestMode message
Sending a new choice field of Type in primary field of RedundancyEncodingDTMode of RequestMode message
ASN_TC_57Sending a new choice field of adapatationLayerType in H223ModeParameters of RequestMode message
Sending a new choice field of adapatationLayerType in H223ModeParameters of RequestMode message
ASN_TC_58Sending a new choice field of v76ModeParameters in RequestMode message
Sending a new choice field of v76ModeParameters in RequestMode message
ASN_TC_59Sending a new choice field of secondaryEncoding in H2250ModeParameters field of RequestMode message
Sending a new choice field of secondaryEncoding in H2250ModeParameters field of RequestMode message
ASN_TC_60Sending a new choice field of VideoMode in RedundancyEncodingDTMode field of RequestMode message
Sending a new choice field of VideoMode in RedundancyEncodingDTMode field of RequestMode message
ASN_TC_61Sending a new choice field of profileAndLevel in H262VideoMode field of RequestMode message
Sending a new choice field of profileAndLevel in H262VideoMode field of RequestMode message
ASN_TC_62Sending a new choice field of Resolution in H263VideoMode field of RequestMode message
Sending a new choice field of Resolution in H263VideoMode field of RequestMode message
ASN_TC_63Sending a new choice field of AudioMode in type field of RequestMode message
Sending a new choice field of AudioMode in type field of RequestMode message
ASN_TC_64Sending a new choice field of Application in DataMode field of RequestMode message
Sending a new choice field of Application in DataMode field of RequestMode message
ASN_TC_65Sending a new choice field of EncryptionMode in RequestMode message
Sending a new choice field of EncryptionMode in RequestMode message
ASN_TC_66Sending a new choice field of type in MaintenanceLoopRequest message
Sending a new choice field of type in MaintenanceLoopRequest message
ASN_TC_67Sending a new choice field of type in ConferenceRequest message
Sending a new choice field of type in ConferenceRequest message
ASN_TC_68Sending a new choice field of type in RemoteMCRequest message
Sending a new choice field of type in RemoteMCRequest message
ASN_TC_69Sending a new choice field of type MultilinkRequest message
Sending a new choice field of type MultilinkRequest message
ASN_TC_70Sending a new choice field of newRequestType in the maximumHeaderInterval field of MultilinkRequest message
Sending a new choice field of newRequestType in the maximumHeaderInterval field of MultilinkRequest message
ASN_TC_71Sending a new choice field of dialingInfo in the addConnection field of MultilinkRequest message
Sending a new choice field of dialingInfo in the addConnection field of MultilinkRequest message
ASN_TC_72Sending a new choice field of dialingInfoNWType in the addConnection field of MultilinkRequest message
Sending a new choice field of dialingInfoNWType in the addConnection field of MultilinkRequest message
ASN_TC_73Sending a new choice field of EncryptionCommand message
Sending a new choice field of EncryptionCommand message
ASN_TC_74Sending a new choice field of SendTCS message
Sending a new choice field of SendTCS message
ASN_TC_75Sending a new choice field of EndSessionCommand message
Sending a new choice field of EndSessionCommand message
ASN_TC_76Sending a new choice field of gstnOptions in EndSessionCommand message
Sending a new choice field of gstnOptions in EndSessionCommand message
ASN_TC_77Sending a new choice field of isdnOptions in EndSessionCommand message
Sending a new choice field of isdnOptions in EndSessionCommand message
ASN_TC_78Sending a new choice field of ConferenceCommand message
Sending a new choice field of ConferenceCommand message
ASN_TC_79Sending a new choice field of encryptionUpdateDirection field in MiscellaneousCommand message
Sending a new choice field of encryptionUpdateDirection field in MiscellaneousCommand message
ASN_TC_80Sending a new choice field of MobileMultilinkReconfigurationCommand message
Sending a new choice field of MobileMultilinkReconfigurationCommand message
ASN_TC_81Sending a new choice field of MiscellaneousCommand message
Sending a new choice field of MiscellaneousCommand message
ASN_TC_82Sending a new choice field of repeatCount in MiscellaneousCommand message
Sending a new choice field of repeatCount in MiscellaneousCommand message
ASN_TC_83Sending a new choice field of pictureReference in LostPartialPicture in MiscellaneousCommand message
Sending a new choice field of pictureReference in LostPartialPicture in MiscellaneousCommand message
ASN_TC_84Sending a new choice field of MiscellaneousIndication message
Sending a new choice field of MiscellaneousIndication message
ASN_TC_85Sending a new choice field of clockRecovery in ATMVCCommand message
Sending a new choice field of clockRecovery in ATMVCCommand message
ASN_TC_86Sending a new choice field of errorCorrection in aal1 field of ATMVCCommand message
Sending a new choice field of errorCorrection in aal1 field of ATMVCCommand message
ASN_TC_87Sending a new choice field of aal in ATMVCCommand message
Sending a new choice field of aal in ATMVCCommand message
ASN_TC_88Sending a new choice field of multiplex in ATMVCCommand message
Sending a new choice field of multiplex in ATMVCCommand message
ASN_TC_89Sending a new choice field of multiplex in reverse paramters of ATMVCCommand message
Sending a new choice field of multiplex in reverse paramters of ATMVCCommand message
ASN_TC_90Sending a new choice field of clockRecovery in ATMVCIndication message
Sending a new choice field of clockRecovery in ATMVCIndication message
ASN_TC_91Sending a new choice field of errorCorrection in ATMVCIndication message
Sending a new choice field of errorCorrection in ATMVCIndication message
ASN_TC_92Sending a new choice field of aal in ATMVCIndication message
Sending a new choice field of aal in ATMVCIndication message
ASN_TC_93Sending a new choice field of multiplex in ATMVCIndication message
Sending a new choice field of multiplex in ATMVCIndication message
ASN_TC_94Sending a new choice field of multiplex in reverseParameters of ATMVCIndication message
Sending a new choice field of multiplex in reverseParameters of ATMVCIndication message
ASN_TC_95Sending a new choice field of multiplex in forward and reverseParameters of ATMVCIndication message
Sending a new choice field of multiplex in forward and reverseParameters of ATMVCIndication message
ASN_TC_96Sending a new choice field of UserInputIndication message
Sending a new choice field of UserInputIndication message
ASN_TC_97Sending a new choice field of userinputsupported in UserInputIndication message
Sending a new choice field of userinputsupported in UserInputIndication message
ASN_TC_98Sending a new choice field of ConferenceIndication message
Sending a new choice field of ConferenceIndication message
ASN_TC_99Sending a new choice field in CloseLogicalChannel message
Sending a new choice field in CloseLogicalChannel message
ASN_TC_100Sending a new choice field in TCSReject message
Sending a new choice field in TCSReject message
ASN_TC_101Sending a new choice field in OLCAck message
Sending a new choice field in OLCAck message
ASN_TC_102Sending a new choice field in OLCReject message
Sending a new choice field in OLCReject message
ASN_TC_103Sending a new choice field in RCC message
Sending a new choice field in RCC message
ASN_TC_104Sending a new choice field in RCCReject message
Sending a new choice field in RCCReject message
ASN_TC_105Sending a new choice field in RMAck message
Sending a new choice field in RMAck message
ASN_TC_106testing of cyclic redundancy capability - VBDCapability
testing of cyclic redundancy capability - VBDCapability
ASN_TC_107Sending a new choice field of RequestModeAck message
Sending a new choice field of RequestModeAck message
ASN_TC_108Testing cyclic redundancy in VBDMode of RequestMode message
Testing cyclic redundancy in VBDMode of RequestMode message
ASN_TC_109Testing of cyclic redundancy - Redundancy Encoding field in the Datatype field of OLC message
Testing of cyclic redundancy - Redundancy Encoding field in the Datatype field of OLC message
ASN_TC_110Testing of cyclic redundancy - Redundancy Encoding field in the H235Media field of Datatype field of OLC message
Testing of cyclic redundancy - Redundancy Encoding field in the H235Media field of Datatype field of OLC message
ASN_TC_111Testing of cyclic redundancy - Redundancy Encoding field in the Datatype field of OLC message-redundancy encoding field again
Testing of cyclic redundancy - Redundancy Encoding field in the Datatype field of OLC message-redundancy encoding field again
ASN_TC_112Testing of cyclic redundancy - Redundancy Encoding field in the H235Media field of Datatype field of OLC message-H235media again
Testing of cyclic redundancy - Redundancy Encoding field in the H235Media field of Datatype field of OLC message-H235media again
ASN_TC_113Testing of redundancy encoding - ModeElementType in RM message
Testing of redundancy encoding - ModeElementType in RM message
ASN_TC_114Sending a new cause field in MultiplexEntrySendReject message
Sending a new cause field in MultiplexEntrySendReject message
ASN_TC_115Sending a new cause field in RequestMultiplexEntrySendReject message
Sending a new cause field in RequestMultiplexEntrySendReject message
ASN_TC_116Sending a new choice field in MaintenanceLoopAck message
Sending a new choice field in MaintenanceLoopAck message
ASN_TC_117Sending a new choice field of type_ in MaintenanceLoopReject message
Sending a new choice field of type_ in MaintenanceLoopReject message
ASN_TC_118Sending a new choice field of cause in MaintenanceLoopReject message
Sending a new choice field of cause in MaintenanceLoopReject message
ASN_TC_119Sending a new choice field of makeMeChairResponse in ConferenceResponse message
Sending a new choice field of makeMeChairResponse in ConferenceResponse message
ASN_TC_120Sending a new choice field in ConferenceResponse message
Sending a new choice field in ConferenceResponse message
ASN_TC_121Sending a new choice field of BroadcastMyLCResponse in ConferenceResponse message
Sending a new choice field of BroadcastMyLCResponse in ConferenceResponse message
ASN_TC_122Sending a new choice field of MakeMeTerminalBroadcasterResp in ConferenceResponse message
Sending a new choice field of MakeMeTerminalBroadcasterResp in ConferenceResponse message
ASN_TC_123Sending a new choice field of SendThisSourceResponse in ConferenceResponse message
Sending a new choice field of SendThisSourceResponse in ConferenceResponse message
ASN_TC_124Sending a new choice field in CommunicationModeResponse message
Sending a new choice field in CommunicationModeResponse message
ASN_TC_125Sending a new choice field of DataType in CommunicationModeResponse message
Sending a new choice field of DataType in CommunicationModeResponse message
ASN_TC_126Sending a new choice field in RemoteMCResponse message
Sending a new choice field in RemoteMCResponse message
ASN_TC_127Sending a new choice field of responseCode in MultilinkResponse message
Sending a new choice field of responseCode in MultilinkResponse message
ASN_TC_128Sending a new choice field of rejected field in the responseCode field of MultilinkResponse message
Sending a new choice field of rejected field in the responseCode field of MultilinkResponse message
ASN_TC_129Sending a new choice field of MultilinkResponse message
Sending a new choice field of MultilinkResponse message
ASN_TC_130Sending a new choice field of rejectReason in LogicalChannelRateRejectResponse message
Sending a new choice field of rejectReason in LogicalChannelRateRejectResponse message
ASN_TC_131Sending a new choice field of h223ModeChange in H223MultiplexReconfiguration message
Sending a new choice field of h223ModeChange in H223MultiplexReconfiguration message
ASN_TC_132Sending a new choice field of h223AnnexADoubleFlag in H223MultiplexReconfiguration message
Sending a new choice field of h223AnnexADoubleFlag in H223MultiplexReconfiguration message
ASN_TC_133Sending a new choice field of FunctionNotSupported message
Sending a new choice field of FunctionNotSupported message
ASN_TC_134Testing of redundancy encoding - MultiplePayloadStreamElementMode in RM message
Testing of redundancy encoding - MultiplePayloadStreamElementMode in RM message
ASN_TC_135Testing of cyclic redundancy - Redundancy Encoding field in the Datatype field of OLC message-using redundancyEncodingElement field this time
Testing of cyclic redundancy - Redundancy Encoding field in the Datatype field of OLC message-using redundancyEncodingElement field this time
ASN_TC_136Testing of redundancy encoding - FECMode in RM message
Testing of redundancy encoding - FECMode in RM message
ASN_TC_137Sending a new mode in DepFECData in DataType field of OLC message
Sending a new mode in DepFECData in DataType field of OLC message
ASN_TC_138Sending a new seperateStream field in DepFECData pdu in DataType field of OLC message
Sending a new seperateStream field in DepFECData pdu in DataType field of OLC message
ASN_TC_139Sending a new choice field of Mode in depFECMode field of RequestMode message
Sending a new choice field of Mode in depFECMode field of RequestMode message
ASN_TC_140Sending a new choice field of depFECMode field of RequestMode message
Sending a new choice field of depFECMode field of RequestMode message
ASN_TC_141Sending a new choice field of seperateStream in depFECMode field of RequestMode message
Sending a new choice field of seperateStream in depFECMode field of RequestMode message
Generic_CapsGeneric Caps
Basic_CallFlow_Gen_Caps_mainIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GDB_TC_1_AudioIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GDB_TC_1_tmp_AudioIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_2_AudioIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_3_AudioIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_4_AudioIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_5_AudioIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_6_AudioIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_7_AudioIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_8_AudioIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_9_AVIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_10_AVIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_11_VideoIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_12_VideoIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_13_VideoIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_14_VideoIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_15_VideoIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_16_VideoIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_17_VAIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_18_VAIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_19_VVIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_20_VVIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_21_AAIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
GCB_TC_22_AAIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
DTMFThis scennario block is for various DTMF related cases
Basic_CallFlow_DTMFIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
Basic_CallFlow_DTMF_SignalIPIPGW H.225 and H.245 Call flow
Note:
User Action: None
Config:
SUT: IPIPGW
Status: -
Ref:
DTMF_1Sending a signal in UserInputIndication msg
Sending a signal in UserInputIndication msg
DTMF_2Sending a signal in UserInputIndication msg
Sending a signal in UserInputIndication msg
teacat_dtmf_1Outgoing FAST Start Call - Remote ECS after Recieving Connect
ARQ_TESTThis scennario block is for various ARQ related cases
ARQ_GK_REG_01Ensure that the IUT on receipt of a RRQ message, when it wants this endpoint
to register with it sends a RCF message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_baseEnsure that the IUT on receipt of a RRQ message, when it wants this endpoint
to register with it sends a RCF message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_full_callEnsure that the IUT on receipt of a RRQ message, when it wants this endpoint
to register with it sends a RCF message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_1Send ARQ requesting bandwidth more than the configured session bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_2Send ARQ requesting bandwidth less than the configured session bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_3Send ARQ requesting bandwidth equal to the configured session bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_4Send ARQ requesting bandwidth more than the configured total bandwidth with return available configured
User Action: NEED TO FIX THIS ROUTINE
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_5Send ARQ requesting bandwidth less than the configured total bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_6Send ARQ requesting bandwidth equal to the configured total bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_7Send ARQ requesting bandwidth more than the configured interzone bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_8Send ARQ requesting bandwidth less than the configured interzone bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_9Send ARQ requesting bandwidth equal to the configured interzone bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_10Send ARQ requesting bandwidth more than the configured session bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_11Send ARQ requesting bandwidth less than the configured session bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_12Send ARQ requesting bandwidth equal to the configured session bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_13Send ARQ requesting bandwidth more than the configured total bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_14Send ARQ requesting bandwidth less than the configured total bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_15Send ARQ requesting bandwidth equal to the configured total bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_16Send ARQ requesting bandwidth more than the configured interzone bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_17Send ARQ requesting bandwidth less than the configured interzone bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_18Send ARQ requesting bandwidth equal to the configured interzone bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_TC_ShanthaSend ARQ requesting bandwidth more than the configured session bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
GK_SecurityThis scennario block is for various GK Security related cases
ARQ_GK_SEC_REG_01Ensure that the IUT on receipt of a RRQ message, when it wants this endpoint
to register with it sends a RCF message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_baseEnsure that the IUT on receipt of a RRQ message, when it wants this endpoint
to register with it sends a RCF message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_full_callEnsure that the IUT on receipt of a RRQ message, when it wants this endpoint
to register with it sends a RCF message.
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_1Send ARQ requesting bandwidth more than the configured session bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_2Send ARQ requesting bandwidth less than the configured session bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_3Send ARQ requesting bandwidth equal to the configured session bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_4Send ARQ requesting bandwidth more than the configured total bandwidth with return available configured
User Action: NEED TO FIX THIS ROUTINE
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_5Send ARQ requesting bandwidth less than the configured total bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_6Send ARQ requesting bandwidth equal to the configured total bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_7Send ARQ requesting bandwidth more than the configured interzone bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_8Send ARQ requesting bandwidth less than the configured interzone bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_9Send ARQ requesting bandwidth equal to the configured interzone bandwidth with return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_10Send ARQ requesting bandwidth more than the configured session bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_11Send ARQ requesting bandwidth less than the configured session bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_12Send ARQ requesting bandwidth equal to the configured session bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_13Send ARQ requesting bandwidth more than the configured total bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_14Send ARQ requesting bandwidth less than the configured total bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_15Send ARQ requesting bandwidth equal to the configured total bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_16Send ARQ requesting bandwidth more than the configured interzone bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_17Send ARQ requesting bandwidth less than the configured interzone bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
ARQ_SEC_TC_18Send ARQ requesting bandwidth equal to the configured interzone bandwidth without return available configured
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RRQ_TC_1Send RRQ with call signaling addr, RAS and source addr are same and receive RRQ
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RRQ_TC_2Send RRQ with call signaling set as 0.0.0.0 IP addr and no change in RAS and source addr and receive RRJ security denial
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
RRQ_TC_3Send RRQ with call signaling set as 9.13.25.21 (other than its own) and no change in RAS and source addr and receive RRJ security denial
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) subclause 7.2[2] subclause 7.19[3]
MISC
CALL_PROC_RAWTx sending raw uuie in Call Proceeding
Send raw uuie in call proceeding
User Action:
Config: A
SUT: Gatekeeper
Status: -
Ref: ETSI TS 101 804-2 V2.1.1 (2004-11) 5.2.2.2.1 clauses 8.1 [2] and 7.3.2 [3]
MISC/
MISC_GK
GK_Accept_CallReceive call;
User Action:
Config: A
SUT: Terminal
Status: -
Ref: ETSI TS 10
Test_GK_Accept_CallTests GK_Accept_Call
User Action:
Config: A
SUT: Terminal
Status: -
Ref:
GK_Send_CallMake a call;
User Action:
Config: A
SUT: Terminal
Status: -
Ref:
Test_GK_Send_CallTests GK_Accept_Call
User Action:
Config: A
SUT: Terminal
Status: -
Ref:
MISC/
TWO_PCS
STOP_A
SUT:
STOP_B
SUT:
Status:
H323_01ASlow-start Basic Call Setup between two EP and no GK. Make call. H.323 data flowing in both directions.
Send and receive RTP data.
Config: Link 1
SUT: Terminal
Status: -
Ref:
H323_01BSlow-start Basic Call Setup between two EP and no GK. Receive call. Receive and send RTP DTMF
User Action:
Config: Link 1
SUT: Terminal
Status: -
Ref:
H323_02ABasic Call Setup between two EP and no GK (timeout) - Send SETUP and get no answer
Config: Link 1
SUT: Terminal
Status: -
Ref:
H323_02BBasic Call Setup between two EP and no GK (timeout) - Receive SETUP and send no answer
User Action:
Config: Link 1
SUT: Terminal
Status: -
Ref:
H323_03AOutgoing FAST Start Call - Two EP(EndPoint) using the same GK, direct call signaling and control
User Action:
Config: Link 1
SUT: Terminal
Status: -
Ref:
H323_03BIncoming Fast Start Call - Two EP(EndPoint) using the same GK, direct call signaling and control
User Action:
Config: Link 1
SUT: Terminal
Status: -
Ref:
H323_04ASlow-start Two EP using the same GK. GK routed signaling and direct call control. This scenario makes the call
Config: TESTER Link 1 and Link 2 same IP Address; SUT Link 1 and Link 2 different IP Addresses
SUT: Terminal
Status: -
Ref:
H323_04BSlow-start Two EP using the same GK. GK routed signaling and direct call control. This scenario receives the call
Config: TESTER Link 1 and Link 2 different IP Addresses; SUT Link 1 and Link 2 same IP Address
SUT: Terminal
Status: -
Ref:
H323_05ATwo EP using the same GK, GK routed signaling, and GK routed call control. This scenario makes the call
Config: TESTER Link 1 and Link 2 same IP Address; SUT Link 1 and Link 2 different IP Addresses
SUT: Terminal
Status: -
Ref:
H323_05BSlow-start Two EP using the same GK, GK routed signaling, and GK routed call control. This scenario receives the call
Config: TESTER Link 1 and Link 2 same IP Address; SUT Link 1 and Link 2 different IP Addresses
SUT: Terminal
Status: -
Ref:
H323_09AOutgoing FAST Start Call - Remote ECS after Recieving Connect
H323_09BIncoming Fast Start Call - with tunneled messages
H323_13ASlow-start Make call. H.323 data flowing in both directions. Send and receive RTP data
Config: A
SUT: Terminal
Status: -
Ref:
H323_13BSlow-start Receive call. Receive and send RTP DTMF.
Slow-start Receive call. Receive and send RTP DTMF.
H323_14ASlow-start Make call. Send RTP DTMF
Config: A
SUT: Terminal
Status: -
Ref:
H323_14BSlow-start Receive call. Receive RTP DTMF.
Slow-start Receive call. Receive RTP DTMF.
H323_15ASlow-start Make call. Receive RTP DTMF
Config: A
SUT: Terminal
Status: -
Ref:
H323_15BSlow-start Receive call. Send RTP DTMF.
Slow-start Receive call. Send RTP DTMF.
H323_16AH323 that contains an H.225.0 Call Signaling SETUP message, but no metadata (no CGPN and no NDPN)
Slow-start Make Call. Send then receive RTP DTMF.
Config: A
SUT: Terminal
Status: -
Ref:
H323_16BH323 that contains an H.225.0 Call Signaling SETUP message, but no metadata (no CGPN and no NDPN)
Slow-start Receive Call. Receive then send RTP DTMF.
H323_17AH323 that contains an H.225.0 Call Signaling SETUP message, with user metadata (both called and calling party)
Slow-start Make Call. Send then receive RTP DTMF.
Config: A
SUT: Terminal
Status: -
Ref:
H323_17BH323 that contains an H.225.0 Call Signaling SETUP message, with user metadata (both called and calling party)
Slow-start Receive Call. Receive then send RTP DTMF.
H323_18AH323 that contains an H.225.0 Call Signaling SETUP message, with user metadata (both called and calling party),
but no subsequent H.245 message.
Slow-start Make Call.
Config: A
SUT: Terminal
Status: -
Ref:
H323_18BH323 that contains an H.225.0 Call Signaling SETUP message, with user metadata (both called and calling party),
but no subsequent H.245 message.
Slow-start Receive Call.
H323_19AH323 that contains an H.225.0 Call Signaling SETUP message, with user metadata (both called and calling party),
H.245 message, but no RTCP.
Slow-start Make Call.
Config: A
SUT: Terminal
Status: -
Ref:
H323_19BH323 that contains an H.225.0 Call Signaling SETUP message, with user metadata (both called and calling party),
H.245 message, but no RTCP.
Slow-start Receive Call.
H323_20AH323 that contains an H.225.0 Call Signaling SETUP message, with user metadata (both called and calling party),
H.245 message, RTCP message, but no RTP data.
Slow-start Make Call.
Config: A
SUT: Terminal
Status: -
Ref:
H323_20BH323 that contains an H.225.0 Call Signaling SETUP message, with user metadata (both called and calling party),
H.245 message, RTCP message, but no RTP data.
Slow-start Receive Call.
H323_21ASlow-start H.323 that contains all signaling protocols required to start a cut. Make call. Send and receive RTP data
Config: A
SUT: Terminal
Status: -
Ref:
H323_21BSlow-start H.323 that contains all signaling protocols required to start a cut. Receive call. Receive and send RTP DTMF.
Slow-start H.323 that contains all signaling protocols required to start a cut. Receive call. Receive and send RTP DTMF.
H323_22ASlow-start Make call. RTP running for a long time, tests ability to end cut when maximum cut size is reached. Send and receive RTP data
Config: A
SUT: Terminal
Status: -
Ref:
H323_22BSlow-start Receive call. RTP running for a long time, tests ability to end cut when maximum cut size is reached. Receive and send RTP DTMF.
Slow-start Receive call. RTP running for a long time, tests ability to end cut when maximum cut size is reached. Receive and send RTP DTMF.
MISC/
MISC_VIDEO
H323_Aethra_Vega_x7_Call_AAethra Vega x7 outgoing call
Config: A
SUT: Terminal
Status: -
Ref:
H323_Aethra_Vega_x7_Call_BAethra Vega x7 incoming call.
Aethra Vega x7 incoming call.
H323_RTP_Outgoing_CallOutgoing call
Config: A
SUT: Terminal
Status: -
Ref:
H323_RTP_Incoming_CallIncoming call.
Incoming call.

VariableDefault ValueDescription
H323_PX_IP_Address_TESTER_Text"9.13.46.200" IP Address of TESTER Link 1
H323_PX_IP_Address_TESTER_Text_2"9.13.46.201" IP Address of TESTER Link 2
H323_PX_IP_Address_TESTER_Text_3"9.13.46.202" IP Address of TESTER Link 3
H323_PX_IP_Address_TESTER_Text_4"9.13.46.203" IP Address of TESTER Link 4
H323_PX_IP_Address_TESTER_Text_5"9.13.46.204" IP Address of TESTER Link 5 - not used in test scenario
H323_PX_IP_Port_TESTER_CS1720 Port Address of TESTER for H.225 dialogue (e.g. SETUP, CONNECT, etc.)
H323_PX_IP_Port_TESTER_RAS1719 Port Address of TESTER for RAS dialogue (e.g. GRQ, GCF, etc.)
H323_PX_IP_Port_TESTER_MMSC1721 Port Address of TESTER for H.245 dialogue (e.g. MSDET, OLC, etc. )
H323_PX_IP_Address_IUT_Text"9.13.32.10" IP Address of IUT Link 1
H323_PX_IP_Address_IUT_Text_2"9.13.32.11" IP Address of IUT Link 2
H323_PX_IP_Address_IUT_Text_3"9.13.32.12" IP Address of IUT Link 3
H323_PX_IP_Address_IUT_Text_4"9.13.32.13" IP Address of IUT Link 4
H323_PX_IP_Address_IUT_Text_5"9.13.32.14" IP Address of IUT Link 5 - not used in test scenario
H323_PX_IP_Port_IUT_CS1720 Port Address of IUT for H.225 dialogue (e.g. SETUP, etc.)
H323_PX_IP_Port_IUT_RAS1719 Port Address of IUT for RAS dialogue (e.g. GRQ, GCF, etc.)
H323_PX_IP_Port_IUT_MMSC1721 Port Address of IUT for H.245 dialogue (e.g. MSDET, OLC, etc. )
H323_PX_IP_Address_TESTER_RTP_TEXT"192.168.1.67" IP Address of TESTER for RTP Link 1
H323_PX_IP_Address_TESTER_RTP_TEXT_2"192.168.1.68" IP Address of TESTER for RTP Link 2
H323_PX_IP_Address_TESTER_RTP_TEXT_3"192.168.1.69" IP Address of TESTER for RTP Link 3
H323_PX_IP_Address_TESTER_RTP_TEXT_4"192.168.1.70" IP Address of TESTER for RTP Link 4
H323_PX_IP_Address_TESTER_RTP_TEXT_5"192.168.1.71" IP Address of TESTER for RTP Link 5
H323_PX_IP_Port_TESTER_RTP9900 IP Port Address of TESTER for RTP Link 1
H323_PX_IP_Port_TESTER_RTP_29902 IP Port Address of TESTER for RTP Link 2
H323_PX_IP_Port_TESTER_RTP_39904 IP Port Address of TESTER for RTP Link 3
H323_PX_IP_Port_TESTER_RTP_49906 IP Port Address of TESTER for RTP Link 4
H323_PX_IP_Port_TESTER_RTP_59908 IP Port Address of TESTER for RTP Link 5
H323_PX_BCC_GK_Phone1"56941000" Gatekeeper E.164 address for Link 1
H323_PX_BCC_GK_Phone2"56941001" Gatekeeper E.164 address for Link 2
H323_PX_BCC_GK_Phone3"56941002" Gatekeeper E.164 address for Link 2 - scenarios RAS_GK_LOC_01-04
H323_PX_BCC_GK_Unknown"56941003" Gatekeeper E.164 address unknown scenario RAS_GK_LOC_03
H323_PX_BCC_GK_ID1"Phone1" Gatekeeper H.323-ID address for Link 1
H323_PX_BCC_GK_ID2"Phone2" Gatekeeper H.323-ID address for Link 2
H323_PX_BCC_GK_URL1"h323:phone1@testhost.aaa" Gatekeeper URL-ID address for Link 1
H323_PX_BCC_GK_URL2"h323:phone2@testhost.aaa" Gatekeeper URL-ID address for Link 2
H323_PX_BCC_GK_email1"phone1@testhost.aaa" Gatekeeper email address for Link 1
H323_PX_BCC_GK_email2"phone2@testhost.aaa" Gatekeeper email address for Link 2
H323_PX_BCC_GK_PartyNumber1"56941000" Gatekeeper E.164 address for Link 1
H323_PX_BCC_GK_PartyNumber2"56941001" Gatekeeper E.164 address for Link 2
H323_PX_RAS_GK2_ID"GK2" Gatekeeper 2 ID for DGK scenarios
H323_PX_Q931_CDPN"56941000" Destination phone number (Called Party Number)
H323_PX_Q931_CGPN"26682000" Source phone number (Calling Party Number)
H323_H245_FastStartFALSE RFU
H323_PX_IUT_Needs_MSReqTRUE Flag to indicate whether TESTER should send MS Determination message. TRUE - YES; FALSE - No
H323_PX_ProtocolID'0008914A0006'H Test case H323 Protocol Identifier
H323_PX_ConferenceID'8CF3B8172274F742853B420D310B6... Test case H323 Conference Identifier
H323_PX_CallIdentifier_GUID'75594AC19341AD4188663328BC017... Test case H323 Call Identifier
H323_PX_ActiveMCFALSE activeMC parameter in SETUP message
H323_PX_MediaWaitForConnectFALSE mediaWaitForConnect parameter in SETUP message
H323_PX_CanOverlapSendFALSE canOverlapSend parameter in SETUP message
H323_PX_FastStart0'0000000D4002800A040001008638E... Test case H323 FastStart param used in SETUP
H323_PX_FastStart1'0000010C203B800A040001008638E... Test case H323 FastStart param used in SETUP
H323_PX_FastStart2'0000020C603B800A040001008638E... Test case H323 FastStart param used in SETUP
H323_PX_FastStart3'401299060401004D4002801114000... Test case H323 FastStart param used in SETUP
H323_PX_FastStart4'401299060401004C203B801114000... Test case H323 FastStart param used in SETUP
H323_PX_FastStart5'401299060401004C603B801114000... Test case H323 FastStart param used in SETUP
H323_PX_G729_Priority_Level1 Used in ASN scenarios to specify set of FastStart Parameter values
H323_PX_BCAP_Entry_1'881886A5'H Bearer Capability entry 1 - Test case H323 FastStart param
H323_PX_BCAP_Entry_2'8090A2'H Bearer Capability entry 2
H323_PX_BCAP_Entry_3'80C0A5'H Bearer Capability entry 3
H323_PX_BCAP_Entry_4'9090A3'H Bearer Capability entry 4
H323_PX_BCAP_Entry_Num_To_Use1 Bearer Capability (BCAP) entry to use. Defaults to 1
H323_PX_Display"Valid8.com TESTER" Display name on SETUP
H323_LC_Audio_forwardChanNum258 OLC Forward Logical Channel Number
H323_LC_Video_forwardChanNum257 OLC Forward Logical Channel Number
H323_PX_T_AC20000 General purpose timer used to wait for a response from IUT
H323_PX_T_T10920000 Timer T109 used in H.245 scenarios
H323_PX_T_T10320000 Timer T103 used in H.245 scenarios for how long to wait for response (e.g. OLCACK ot OLC)
H323_PX_T_301MIN10000 Min value for Timer T301. Scenario (BCC_TE_PHA_26) expects message after MIN and before Max
H323_PX_T_301MAX20000 Max value for Timer T301. Scemario (BCC_TE_PHA_26) expects message after MIN and before Max
H323_PX_T_303MIN10000 Min value for Timer T303. Scenario expects message after MIN and before Max
H323_PX_T_303MAX20000 Max value for Timer T303. Scemario expects message after MIN and before Max
H323_PX_T_SYNC20000 Timer for how long to wait for ACF response to ARQ
H323_PX_T_NOAC1000 Timer for how long to wait for RAS Confirm message (e.g. GCF for GRQ, LCF for LRQ)
H323_PX_T_ACTIVE10000 Timer used after receiving CONNECT to wait for next message
H323_PX_T_WAIT_ARQ30000 How long to wait for a ARQ message
H323_PX_T_WAIT_BRQ30000 How long to wait for a BRQ message
H323_PX_T_WAIT_DRQ30000 How long to wait for a DRQ message
H323_PX_T_WAIT_GRQ30000 How long to wait for a GRQ message
H323_PX_T_WAIT_IRQ65000 How long to wait for an IRQ message
H323_PX_T_WAIT_LRQ2000 How long to wait for an LRQ message
H323_PX_T_WAIT_RRQ30000 How long to wait for an RRQ message
H323_PX_T_WAIT_URQ30000 How long to wait for a URQ message
H323_PX_T_REPEAT_ARQ500 How long to wait for an ARQ message to be repeated
H323_PX_T_REPEAT_BRQ500 How long to wait for a BRQ message to be repeated
H323_PX_T_REPEAT_DRQ500 How long to wait for a DRQ message to be repeated
H323_PX_T_REPEAT_GRQ500 Delay value to put into RIP message after receiving GRQ (scenario RAS_TE_RIP_02 and 03)
H323_PX_T_REPEAT_IRR500 How long to wait for an IRR message to be repeated
H323_PX_T_REPEAT_LRQ10000 Delay value to put into RIP message after receiving LRQ (scenario RAS_TE_RIP_11)
H323_PX_T_REPEAT_RRQ500 Delay value to put into RIP message after receiving RRQ (scenario RAS_TE_RIP_05)
H323_PX_T_REPEAT_URQ10000 Timer (in ms) for how long to wait between URQ messages
H323_PX_RAS_SEND_GRQTRUESend GRQ during preamble before RRQ. TRUE = Yes; FALSE = No
H323_PX_RAS_SEND_RRQ_WITH_ALIASFALSESend RRQ with TerminalAlias and Terminal undefinedNode to FALSE. TRUE = Yes FALSE = No
H323_PX_RAS_SEND_URQ_WITH_EPIDFALSESend URQ with Endpoint Identification. TRUE - Yes FALSE = No
H323_PX_RAS_SEND_DRQ_WITH_RCFALSESend DRQ with RELEASE COMPLETE. TRUE = YES; FALSE = NO
H323_PX_RAS_USE_RAND_SEQNOFALSEUse a random number as the starting sequence number. TRUE = Yes; FALSE = No (start at seqno 1)
H323_PX_RAS_ADD_OPT_TO_SETUPFALSEInclude sourceCallSignalAddress in SETUP Message. TRUE = YES; FALSE = NO
H323_PX_RAS_ADD_TRANSPORT_TO_CONNECTFALSEInclude H245 transport address in CONNECT Message. TRUE = YES; FALSE = NO
H323_PX_RAS_ACCEPT_STATUS_MSGFALSEAccept STATUS message when no message is expected. Used in GK scenarios. TRUE = YES; FALSE = NO
H323_PX_RAS_VERIFY_CALL_STATEFALSEVerify Call state in DGK scenarios. TRUE = YES; FALSE = NO
H323_PX_RAS_SEND_ALTERNATE_SETUPFALSESend alternate setup without FastStart and Terminal. TRUE = YES; FALSE = NO
H323_PX_RAS_DONT_TIMEOUT_ON_CONNECTFALSEStart a timer waiting for a CONNECT. TRUE = Dont Start Timer; FALSE = Start Timer (RAS TE scenarios)
H323_PX_RAS_USE_TERMINAL_ON_SETUPTRUEUse terminal on SETUP message. TRUE = Yes; FALSE = No use gateway (BCC_TE_PHA or BCC_GK_PHA scenarios)
H323_PX_RAS_USE_ALT_PH_ON_LOCTRUEUse alternate Phone number on ras_gk_loc_01-04 TRUE=yes (H323_PX_BCC_GK_Phone3) FALSE=no (H323_PX_BCC_GK_Phone2)
H323_PX_RAS_UNICAST_LRQTRUE RFU
H323_PX_RAS_OPERATOR_SEND_FOR_BRQTRUE RFU
H323_PX_RAS_OPERATOR_SEND_FOR_GRQTRUE RFU
H323_PX_RAS_OPERATOR_SEND_FOR_IRQTRUE RFU
H323_PX_RAS_OPERATOR_SEND_FOR_LRQTRUE RFU
H323_PX_RAS_OPERATOR_SEND_FOR_URQTRUEOperator sends URQ. TRUE - Operator send URQ; FALSE - Power off to send URQ
H323_PX_RAS_WAIT_TO_SEND_SETUPFALSEWait to send SETUP message after RCF is complete. TRUE - YES; FALSE - NO (RAS_TE scenarios)
H323_PX_RAS_WAIT_FOR_ARQFALSEWait for ARQ after SETUP message. TRUE - YES; FALSE - NO (RAS_TE scenarios)
H323_PX_RAS_WAIT_TO_DISCONNECT_CALLFALSEWait for timer before sending DRQ. TRUE - YES; FALSE - NO
H323_PX_RAS_MANUAL_GKDiscoveryTRUEWait for GRQ. TRUE - Do not wait for GRQ; FALSE - Wait for GRQ. Used in RAS_TE_ tests
H323_PX_RAS_IMMEDIATE_RRQTRUE RFU
H323_PX_RAS_TESTER_MULTICAST_PORT1718Multicast IP Port for scenario RAS_TE_GDR_02
H323_PX_RAS_TESTER_MULTICAST_IPADDR_Text"224.0.1.41"Multicast IP Address for scenario RAS_TE_GDR_02
H323_PX_RAS_Broadcast_ModeBroadcast_Disabled Broadcast mode for scenario RAS_TE_GDR_02
H323_PX_RAS_IUT_MULTICAST_PORT1718 Multicast Porrt Address used in scenario (RAS_TE_GDR_02)
H323_PX_RAS_IUT_MULTICAST_IPADDR_Text"224.0.1.41" Multicast IP Address used in scenario (RAS_TE_GDR_02)
H323_PX_RAS_ETS_IRRFrequency500RFU
H323_PX_RAS_WAIT_CALL_PROCEEDINGTRUEWhether to wait for CALL PROCEEDING message for IUT - TRUE means wait
H323_PX_RAS_CALL_REFERENCE_VALUE2RAS CallReferenceValue
H323_PX_RAS_DELAY_TO_ESTABLISH_A_CALL2000Time to live in RCF message or time to wait for CONNECT message after ACF
H323_RequestSeqNum1000Sequence Number used in some H.245 messages
H323_PX_RAS_RAISE_BANDWITH3200Used in RAS scenarios (gk_BND_01, 02, & te_BND_06) to raise allowed bandwidth
H323_PX_RAS_LOW_BANDWITH0Used in scenario RAS_TE_BND_07 to lower allowed bandwidth
H245_SentOpenLCTRUE RFU
H323_PD_Error15 Protocol Discriminator Error to send (0 - 255). Used in GK and DGK scenarios
T_LENGTH_TO_SEND5000 Length of time to send RTP DTMF. Used in MISC scenarios
T_RETRY_TIMEOUT60000 Length of time to retry. Used in MISC scenarios
T_CALL_HOLD_VAL30000 Length of time to hold call. Used in MISC_GK scenarios
T_ANSWER_DELAY_VAL0 Length of time to wait before answering incoming call. Used in MISC_GK scenarios
T_CALL_WAIT_DELAY_VAL0 Length of time to wait from receiving RRQ before sending SETUP. Used in MISC_GK scenarios
T_WAIT_TIME_TO_DISCONNECT0Time to wait(in ms) before sending DRQ. H323_PX_RAS_WAIT_TO_DISCONNECT_CALL must be set to TRUE
PROGRESS_IND'1E028088'HProgress indicator field for Alerting and Call Proceeding
TSC_BND_LOW_VALUE0(null)

Copyright © ACATS Forum 2008 on behalf of the test suite author. All rights reserved. Specifications may change subject to requirements.

23 Feb 2010Produced by SAFIRE V20.05.14.01
www.SAFIRE-World.com		 Test Suite Overview