Valid8.com/ACATS VoIP H.323 Conformance Test Suite, for use with H.323 Signaling Tester
TEST SUITE OVERVIEW
References
Archive/Projectvoip/h323_fts
Version19171710
Date25 Jan 2010
Number of Scenarios10
Number of Groups1
Average per Group10
GROUP/SCENARIOTEST PURPOSE
H225
H225/
RAS
H225/
RAS/
RAS_TE_GDR
H225/
RAS/
RAS_TE_REG
H225/
RAS/
RAS_TE_ADM
H225/
RAS/
RAS_TE_LOC
H225/
RAS/
RAS_TE_BND
H225/
RAS/
RAS_TE_URG
H225/
RAS/
RAS_TE_DIS
H225/
RAS/
RAS_TE_STA
H225/
RAS/
RAS_TE_RIP
H225/
RAS/
RAS_GK_GDR
H225/
RAS/
RAS_GK_REG
H225/
RAS/
RAS_GK_ADM
H225/
RAS/
RAS_GK_LOC
H225/
RAS/
RAS_GK_BND
H225/
RAS/
RAS_GK_URG
H225/
RAS/
RAS_GK_DIS
H225/
RAS/
RAS_GK_STA
H225/
RAS/
RAS_GK_RIP
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]
H225/
BCC/
Endpoint/
PHE
H225/
BCC/
Endpoint/
Inopportune
H225/
BCC/
Endpoint/
Inopportune/
U0
H225/
BCC/
Endpoint/
Inopportune/
U1
H225/
BCC/
Endpoint/
Inopportune/
U2
H225/
BCC/
Endpoint/
Inopportune/
U3
H225/
BCC/
Endpoint/
Inopportune/
U4
H225/
BCC/
Endpoint/
Inopportune/
U7
H225/
BCC/
Endpoint/
Inopportune/
U10
H225/
BCC/
Endpoint/
SyntacticallyInvalid
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U00
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U01
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U02
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U03
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U04
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U07
H225/
BCC/
Endpoint/
SyntacticallyInvalid/
U10
H225/
BCC/
Gatekeeper
H225/
BCC/
Gatekeeper/
BCC_GK_PHA
H225/
BCC/
Gatekeeper/
BCC_GK_PHE
H225/
BCC/
Gatekeeper/
InnoportuneBehavior
H225/
BCC/
Gatekeeper/
InnoportuneBehavior/
U00
H225/
BCC/
Gatekeeper/
InnoportuneBehavior/
U07
H225/
BCC/
Gatekeeper/
InnoportuneBehavior/
U09
H225/
BCC/
Gatekeeper/
InnoportuneBehavior/
U10
H225/
BCC/
Gatekeeper/
SyntacticallyInvalid
H225/
BCC/
Gatekeeper/
SyntacticallyInvalid/
U00
H225/
BCC/
Gatekeeper/
SyntacticallyInvalid/
U07
H225/
BCC/
Gatekeeper/
SyntacticallyInvalid/
U09
H225/
BCC/
Gatekeeper/
SyntacticallyInvalid/
U10
H225/
BCC/
DestinationGatekeeper
H225/
BCC/
DestinationGatekeeper/
PHA
H225/
BCC/
DestinationGatekeeper/
PHE
H225/
BCC/
DestinationGatekeeper/
Inopportune
H225/
BCC/
DestinationGatekeeper/
Inopportune/
U00
H225/
BCC/
DestinationGatekeeper/
Inopportune/
U01
H225/
BCC/
DestinationGatekeeper/
Inopportune/
U03
H225/
BCC/
DestinationGatekeeper/
Inopportune/
U04
H225/
BCC/
DestinationGatekeeper/
Inopportune/
U10
H225/
BCC/
DestinationGatekeeper/
SyntacticallyInvalid
H225/
BCC/
DestinationGatekeeper/
SyntacticallyInvalid/
U00
H225/
BCC/
DestinationGatekeeper/
SyntacticallyInvalid/
U01
H225/
BCC/
DestinationGatekeeper/
SyntacticallyInvalid/
U03
H225/
BCC/
DestinationGatekeeper/
SyntacticallyInvalid/
U04
H225/
BCC/
DestinationGatekeeper/
SyntacticallyInvalid/
U10
H225/
MISC
H245
H245/
OE
H245/
OE/
TC_OE_CEP_BV
H245/
OE/
TC_OE_CEP_BO
H245/
OE/
TC_OE_MSD_BV
H245/
OE/
TC_OE_MSD_BO
H245/
OE/
TC_OE_LCS_BV
H245/
OE/
TC_OE_LCS_BO
H245/
OE/
TC_OE_CLC_BV
H245/
OE/
TC_OE_BLC_BO
H245/
OE/
TC_OE_CLC_BV
H245/
OE/
TC_OE_CLC_BO
H245/
OE/
TC_OE_MRS_BV
H245/
OE/
TC_OE_MRS_BO
H245/
TE
H245/
TE/
TC_TE_CEP_BV
H245/
TE/
TC_TE_CEP_BO
H245/
TE/
TC_TE_MSD_BV
H245/
TE/
TC_TE_MSD_BO
H245/
TE/
TC_TE_LCS_BV
H245/
TE/
TC_TE_LCS_B0
H245/
TE/
TC_TE_BLC_BV
H245/
TE/
TC_TE_BLC_BO
H245/
TE/
TC_TE_CLC_BV
H245/
TE/
TC_CLC_BO
H245/
TE/
TC_TE_MRS_BV
Choctaw_TSTest ECS Call Flows for Supplementary features
Choctaw_TS_C1Test ECS Call Flows for Supplementary features
Choctaw_TS_C1/
ECS_STATEMACHINE		All Test cases related to ECS State Machine
dtmftest
RTP
ASNV13Testcase Block to test sanitization function
ASNV13_SLOWSTARTTestcases related to slow start
Generic_CapsGeneric Caps
DTMFThis scennario block is for various DTMF related cases
ARQ_TESTThis scennario block is for various ARQ related cases
GK_SecurityThis scennario block is for various GK Security related cases
MISC
MISC/
MISC_GK
MISC/
TWO_PCS
MISC/
MISC_VIDEO

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_05-09
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_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 = YESY; FALSE = NO
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 2010 on behalf of the test suite author. All rights reserved. Specifications may change subject to requirements.

01 Feb 2010Produced by SAFIRE V20.05.15.01
www.SAFIRE-World.com		 Test Suite Overview