SIST EN 301 060-5:2000

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.JUDGEDIntegrated Services Digital Network (ISDN); Digital Subscriber Signalling System No. one (DSS1) protocol; Basic call control; Enhancement at the b service entry point for Virtual Private Network (VPN) applications; Part 5: Test Suite Structure and Test Purposes (TSS&TP) specification for the network33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:EN 301 060-5 Version 1.1.3SIST EN 301 060-5:2000en01-december-2000SIST EN 301 060-5:2000SLOVENSKI
STANDARD
EN 301 060-5 V1.1.3 (1998-11)European Standard (Telecommunications series)Integrated Services Digital Network (ISDN);Digital Subscriber Signalling System No. one (DSS1) protocol;Basic call control;Enhancement at the "b" service entry point forVirtual Private Network (VPN) applications;Part 5: Test Suite Structure and Test Purposes (TSS&TP)specification for the networkSIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)2ReferenceDEN/SPS-05109-5 (9td90ie0.PDF)KeywordsISDN, DSS1, basic, VPN, TSS&TP, networkETSIPostal addressF-06921 Sophia Antipolis Cedex - FRANCEOffice address650 Route des Lucioles - Sophia AntipolisValbonne - FRANCETel.: +33 4 92 94 42 00
Fax: +33 4 93 65 47 16Siret N° 348 623 562 00017 - NAF 742 CAssociation à but non lucratif enregistrée à laSous-Préfecture de Grasse (06) N° 7803/88Internetsecretariat@etsi.frIndividual copies of this ETSI deliverablecan be downloaded fromhttp://www.etsi.orgCopyright NotificationNo part may be reproduced except as authorized by written permission.The copyright and the foregoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1998.All rights reserved.SIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)3ContentsIntellectual Property Rights.5Foreword.51Scope.62Normative references.63Definitions and abbreviations.73.1Definitions.73.1.1Definitions related to conformance testing.73.1.2Definitions related to EN 301 060-1.83.2Abbreviations.84Test Suite Structure (TSS).85Test Purposes (TP).105.1Introduction.105.1.1TP naming convention.105.1.2Source of TP definition.105.1.3TP structure.105.1.4Test strategy.115.1.5Test of call states.115.1.6Test of point-to-multipoint configurations.125.1.7Test of inopportune and syntactically invalid behaviour.125.2TPs for the basic call control VPN, layer 3, network.125.2.1Null call state N00.125.2.1.1Valid.125.2.1.1.1Outgoing call.125.2.1.1.2Incoming call - point-to-point configuration.175.2.1.2Inopportune.185.2.1.3Syntactically invalid.195.2.2Overlap sending call state N02.205.2.2.1Valid.205.2.2.2Inopportune.225.2.2.3Syntactically invalid.225.2.3Outgoing call proceeding call state N03.235.2.3.1Valid.235.2.3.2Inopportune.245.2.3.3Syntactically invalid.255.2.4Call delivered call state N04.265.2.4.1Valid.265.2.4.2Inopportune.275.2.4.3Syntactically invalid.275.2.5Call present call state N06.285.2.5.1Valid.285.2.5.1APoint-to-point configuration.285.2.5.2Inopportune.325.2.5.3Syntactically invalid.335.2.6Call received call state N07.345.2.6.1Valid.345.2.6.1APoint-to-point configuration.345.2.6.2Inopportune.355.2.6.3Syntactically invalid.365.2.7Incoming call proceeding call state N09.365.2.7.1Valid.365.2.7.1APoint-to-point configuration.365.2.7.2Inopportune.375.2.7.3Syntactically invalid.38SIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)45.2.8Active call state N10 (incoming call).395.2.8.1Valid.395.2.8.2Inopportune.405.2.8.3Syntactically invalid.415.2.9Active call state N10 (outgoing call).415.2.9.1Valid.415.2.9.2Inopportune.425.2.9.3Syntactically invalid.435.2.10Disconnect indication call state N12 (incoming call).445.2.10.1Valid.445.2.10.2Inopportune.445.2.10.3Syntactically invalid.455.2.11Disconnect indication call state N12 (outgoing call).465.2.11.1Valid.465.2.11.2Inopportune.465.2.11.3Syntactically invalid.475.2.12Release request call state N19 (incoming call).475.2.12.1Valid.475.2.12.2Inopportune.485.2.12.3Syntactically invalid.485.2.13Release request call state N19 (outgoing call).495.2.13.1Valid.495.2.13.2Inopportune.495.2.13.3Syntactically invalid.505.2.14Overlap receiving call state N25.515.2.14.1Valid.515.2.14.1APoint-to-point configuration.515.2.14.2Inopportune.515.2.14.3Syntactically invalid.525.2.15Restart null call state R00 (incoming call).535.2.15.1Valid.535.2.15.2Inopportune.545.2.15.3Syntactically invalid.545.2.16Restart null call state R00 (outgoing call).555.2.16.1Valid.555.2.16.2Inopportune.565.2.16.3Syntactically invalid.565.2.17Restart request call state R01.575.2.17.1Valid.575.2.17.2Inopportune.575.2.17.3Syntactically invalid.585.2.18Message segmentation procedure.595.2.18.1Valid.595.2.18.2Inopportune.595.2.18.3Syntactically invalid.596Compliance.607Requirements for a comprehensive testing service.60History.61SIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)5Intellectual Property RightsIPRs essential or potentially essential to the present document may have been declared to ETSI. The informationpertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be foundin SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respectof ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on theETSI Web server (http://www.etsi.org/ipr).Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaranteecan be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)which are, or may be, or may become, essential to the present document.ForewordThis European Standard (Telecommunications series) has been produced by ETSI Technical Committee SignallingProtocols and Switching (SPS).The present document is part 5 of a multi-part standard covering the Digital Subscriber Signalling System No. one(DSS1) protocol specification for the Integrated Services Digital Network (ISDN) basic call control extensions at the"b" service entry point for VPN applications, as described below:Part 1:"Protocol specification";Part 2:"Protocol Implementation Conformance Statement (PICS) proforma specification";Part 3:"Test Suite Structure and Test Purposes (TSS&TP) specification for the user";Part 4:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification for the user";Part 5:"Test Suite Structure and Test Purposes (TSS&TP) specification for the network";Part 6:"Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT)proforma specification for the network".National transposition datesDate of adoption of this EN:20 November 1998Date of latest announcement of this EN (doa):28 February 1999Date of latest publication of new National Standardor endorsement of this EN (dop/e):31 August 1999Date of withdrawal of any conflicting National Standard (dow):31 August 1999SIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)61ScopeThis fifth part of EN 301 060 is applicable to the basic call control extensions at the "b" service entry point for VirtualPrivate Network (VPN) applications for the pan-European Integrated Services Digital Network (ISDN) as provided byEuropean public telecommunications operators at the T reference point (as defined inITU-T Recommendation I.411 [13]) by means of the Digital Subscriber Signalling System No. one (DSS1) protocol.Stage three identifies the protocol procedures and switching functions needed to support a telecommunications service(see CCITT Recommendation I.130 [12]).The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for the network side for the ISDNDSS1 basic call control extensions at the "b" service entry point for VPN applications as specified in EN 301 060-1 [1]in compliance with the relevant requirements and in accordance with the relevant guidance given inISO/IEC 9646-7 [11].2Normative referencesReferences may be made to:a)specific versions of publications (identified by date of publication, edition number, version number, etc.), inwhich case, subsequent revisions to the referenced document do not apply; orb)all versions up to and including the identified version (identified by "up to and including" before the versionidentity); orc)all versions subsequent to and including the identified version (identified by "onwards" following the versionidentity); ord)publications without mention of a specific version, in which case the latest version applies.A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the samenumber.[1]EN 301 060-1 (V1.2): "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Basic call control; Enhancement at the "b" service entry pointfor Virtual Private Network (VPN) applications; Part 1: Protocol specification".[2]EN 301 060-2 (V.1.1): "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Basic call control; Enhancement at the "b" service entry pointfor Virtual Private Network (VPN) applications; Part 2: Protocol implementation ConformanceStatement (PICS) proforma specification".[3]EN 300 403-1: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 1: Protocol specification [ITU-T Recommendation Q.931 (1993), modified]".[4]ETS 300 403-2: "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 2: Specification and Description Language (SDL) diagrams".[5]EN 300 403-3: "Integrated Services Digital Network (ISDN); Digital Subscriber Signalling SystemNo. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 3: Protocol Implementation Conformance Statement (PICS) proforma specification".[6]ETS 300 403-5: "Integrated Services Digital Network (ISDN); Digital Subscriber SignallingSystem No. one (DSS1) protocol; Signalling network layer for circuit-mode basic call control;Part 5: Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information forTesting (PIXIT) proforma specification for the user".[7]ETS 300 406 (1995): "Methods for Testing and Specification (MTS); Protocol and profileconformance testing specifications; Standardization methodology".SIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)7[8]ISO/IEC 9646-1: "Information technology; Open systems interconnection; Conformance testingmethodology and framework; Part 1: General concepts".[9]ISO/IEC 9646-2: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 2: Abstract Test Suite specification".[10]ISO/IEC 9646-3: "Information technology; Open Systems Interconnection; Conformance testingmethodology and framework; Part 3: The Tree and Tabular Combined Notation (TTCN)".[11]ISO/IEC 9646-7: "Information technology; Open systems interconnection; Conformance testingmethodology and framework; Part 7: Implementation Conformance Statements".[12]CCITT Recommendation I.130 (1988): "Method for the characterization of telecommunicationservices supported by an ISDN and network capabilities of an ISDN".[13]ITU-T Recommendation I.411 (1993): "ISDN user-network interfaces - Reference configurations".3Definitions and abbreviations3.1DefinitionsFor the purposes of the present document, the following definitions apply:3.1.1Definitions related to conformance testingabstract test case: refer to ISO/IEC 9646-1 [8].Abstract Test Suite (ATS): refer to ISO/IEC 9646-1 [8].active test: a test case where the Implentation Under Test (IUT) is required to send a particular message, but not inreaction to a received message. This would usually involve the use of PIXIT information to see how this message can begenerated and quite often is specified in an ATS using an implicit send event.Implementation Under Test (IUT): refer to ISO/IEC 9646-1 [8].implicit send event: refer to ISO/IEC 9646-3 [10].lower tester: refer to ISO/IEC 9646-1 [8].passive test: a test case where the IUT is required to respond to a protocol event (e.g. received message) with anotherprotocol event (e.g. send message) which normally does not require any special operator intervention as associated withthe implicit send event.point of control and observation: refer to ISO/IEC 9646-1 [8].Protocol Implementation Conformance Statement (PICS): refer to ISO/IEC 9646-1 [8].PICS proforma: refer to ISO/IEC 9646-1 [8].Protocol Implementation eXtra Information for Testing (PIXIT): refer to ISO/IEC 9646-1 [8].PIXIT proforma: refer to ISO/IEC 9646-1 [8].system under test: refer to ISO/IEC 9646-1 [8].Test Purpose (TP): refer to ISO/IEC 9646-1 [8].SIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)83.1.2Definitions related to EN 301 060-1dummy call reference: see EN 300 403-1 [3], subclause 4.3.Integrated Services Digital Network (ISDN): see ITU-T Recommendation I.112 [9], definition 308.ISDN number: a number conforming to the numbering and structure specified in CCITT Recommendation E.164 [10].service; telecommunication service: see ITU-T Recommendation I.112 [9], definition 201.supplementary service: see ITU-T Recommendation I.210 [11], subclause 2.4.T: the DSS1 protocol entity at the User side of the user-network interface where a T reference point applies (User is aPrivate ISDN).3.2AbbreviationsFor the purposes of the present document, the following abbreviations apply:ATSAbstract Test SuiteISDNIntegrated Services Digital NetworkIUTImplementation Under TestPICSProtocol Implementation Conformance StatementPIXITProtocol Implementation eXtra Information for TestingTPTest PurposeTSSTest Suite StructureVPNVirtual Private Network4Test Suite Structure (TSS)· Null call state N00· Valid· Outgoing call· Incoming call - point-to-point configuration· Inopportune· Syntactically invalid· Overlap Sending call state N02· Valid· Inopportune· Syntactically invalid· Outgoing Call Proceeding call state N03· Valid· Inopportune· Syntactically invalid· Call Delivered call state N04· Valid· Inopportune· Syntactically invalid· Call Present call state N06· Valid· Point-to-point configuration· Inopportune· Syntactically invalidSIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)9· Call Received call state N07· Valid· Point-to-point configuration· Inopportune· Syntactically invalid· Incoming Call Proceeding call state N09· Valid· Point-to-point configuration· Inopportune· Syntactically invalid· Active call state N10 (Incoming call)· Valid· Inopportune· Syntactically invalid· Active call state N10 (Outgoing call)· Valid· Inopportune· Syntactically invalid· Disconnect Indication call state N12 (Incoming call)· Valid· Inopportune· Syntactically invalid· Disconnect Indication call state N12 (Outgoing call)· Valid· Inopportune· Syntactically invalid· Release Request call state N19 (Incoming call)· Valid· Inopportune· Syntactically invalid· Release Request call state N19 (Outgoing call)· Valid· Inopportune· Syntactically invalid· Call Abort call state N22· Overlap Receiving call state N25· Valid· Point-to-point configuration· Inopportune· Syntactically invalid· Restart Null call state R00 (Incoming call)· Valid· Inopportune· Syntactically invalid· Restart Null call state R00 (Outgoing call)· Valid· Inopportune· Syntactically invalid· Restart Request call state R01· Valid· Inopportune· Syntactically invalid· Message segmentation procedure· Valid· Inopportune· Syntactically invalidSIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)105Test Purposes (TP)5.1IntroductionFor each test requirement, a TP is defined.5.1.1TP naming conventionTPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional referencesare added to identify the actual test suite and whether it applies to the network or the user (see table 1).Table 1: TP identifier naming convention schemeIdentifier:___=layer + type of IUT:e.g. "L3N" for layer 3, IUT = network=call state:e.g. N10 for Active call state=group:one character field representing the group referenceaccording to TSSV:Valid stimulusI: Inopportune stimulusS:Syntactically invalid stimulus=sequential number:(001-999)5.1.2Source of TP definitionThe TPs are based on EN 300 403-1 [3] and ETS 300 403-2 [4].5.1.3TP structureEach TP has been written in a manner which is consistent with all other TPs. The intention of this is to make the TPsmore readable and checkable. A particular structure has been used which is illustrated in table 2. This table should beread in conjunction with any TP, i.e. please use a TP as an example to facilitate the full comprehension of table 2.SIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)11Table 2: Structure of a single TPTP partTextExampleHeader tabsee table 1subclause 2.3.4, subclause 9.3.1.1 [3](see note 3) VPNxxx (see note 4)StimulusEnsure that the IUT in theN00, N10, etc. see below for message structureon receipt of a XXXX message(see note 2)or to request a .Reactionsends, saves, does, etc.using en bloc sending, etc.if the action is sending see below for message structure, etc.and remains in the same stateor and enters state MessagestructuremessageSETUP, FACILITY, CONNECT, etc.(see note 2)a) with a information elementb) indicating in the and back to a) or b)Bearer capability, Facility, etc.NOTE 1:Text in italics will not appear in TPs and text between <> is filled in for each TP and may differ from oneTP to the next.NOTE 2:All messages shall be considered as "valid and compatible" unless otherwise specified in the testpurpose.NOTE 3:The subclause indicated there refers directly to the EN 300 403-1 [3] unless otherwise specified, i.e.subclause 9.3.1.1 [6] refers directly to EN 301 060-1 [1].NOTE 4:VPNxxx indicates the origin of the test purpose.VPNMOD: indicates that the test purpose was taken from ETS 300 403-5 [6] and modified in accordancewith the VPN context.VPNNEW: indicates that the test purpose did not exist in ETS 300 403-5 [6] and was created to cover aVPN specific procedure.No indication is used when the test purposes was directly taken from ETS 300 403-5 [6] withoutmodification.5.1.4Test strategyAs the base standard EN 300 403-1 [3] contains no explicit requirements for testing, the TPs were generated as a resultof an analysis of the base standard and the PICS specification EN 300 403-3 [5].The TPs are only based on conformance requirements related to the externally observable behaviour of the IUT, and arelimited to conceivable situations to which a real implementation is likely to be faced (ETS 300 406 [7]).5.1.5Test of call statesMany TPs include a reference to the IUT's final call state after the realization of the TP. In these cases the TP includesthe requirement to ensure that the IUT has entered this particular final call state. Ensuring that the IUT is in a particularcall state shall be realized by following the procedures described in subclause 5.8.10 of EN 300 403-1 [3]. According tothese procedures, the IUT on receipt of a STATUS ENQUIRY message, shall respond with a STATUS messageindicating, in the third octet of the Call state information element, the current call state of the IUT. This exchange ofmessages is not mentioned explicitly in each TP but is considered to be implicit in the reference to the final call state.This way of phrasing the TPs has been used to avoid over-complicating the text and structure of the TPs and to improvethe readability.The call state being reached by the IUT in the following test purpose is intended for a call in a VPN context.SIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)125.1.6Test of point-to-multipoint configurationsThere is no configuration point-to-multipoint in the VPN context.5.1.7Test of inopportune and syntactically invalid behaviourIn the test groups for inopportune and syntactically invalid behaviour the procedures as described in subclause 5.8 ofEN 300 403-1 [3] are tested. This is done in each call state with one message for each of the described error cases.Messages have been chosen that are, if they are received without the inopportune or erroneous coding, expectedmessages in the call states under test.Test purposes for inopportune behaviour that is described outside the subclause 5.8 of EN 300 403-1 [3] are found inthe valid test groups. This was done, as these procedures are seen more as a part of the basic call procedures than as apart of the error handling procedures.5.2TPs for the basic call control VPN, layer 3, networkAll PICS items referred to in this subclause are as specified in ETS 301 060-2 [2] unless indicated otherwise by anothernumbered reference.5.2.1Null call state N005.2.1.1Valid5.2.1.1.1Outgoing callL3N_N00_V_001subclause 5.1.1VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context during an all channelsbusy condition, sends a RELEASE COMPLETE message with a Cause information element indicating the cause value34 "no circuit / channel available" and remains in the Null call state N00.L3N_N00_V_002subclauses 5.1.2 a), 5.1.3VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context without Called partynumber and Sending complete information element and with the Channel identification information element indicating aB-channel that is available and indicating in the preferred / exclusive bit "exclusive: only the indicated channel isacceptable", sends SETUP ACKNOWLEDGE message with the Channel identification information element indicatingthe requested B-channel and indicating in the preferred / exclusive bit "exclusive: only the indicated channel isacceptable" and enters the Overlap Sending call state N02.L3N_N00_V_003subclauses 5.1.2 a), 5.1.5.1VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context with a Called partynumber information element providing the complete called party information, with a Sending complete informationelement and with the Channel identification information element indicating a B-channel that is available and indicatingin the preferred / exclusive bit "exclusive: only the indicated channel is acceptable", sends CALL PROCEEDINGmessage with the Channel identification information element indicating the requested B-channel and indicating in thepreferred / exclusive bit "exclusive: only the indicated channel is acceptable" and enters the Outgoing Call Proceedingcall state N03.L3N_N00_V_004subclause 5.1.2 a)VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context with the Channelidentification information element indicating a B-channel that is not available and indicating in the preferred / exclusivebit "exclusive: only the indicated channel is acceptable", sends a RELEASE COMPLETE message with a Causeinformation element indicating the cause value 34 "no circuit / channel available" or 44 "requested circuit / channel notavailable" and remains in the Null call state.L3N_N00_V_005subclause 5.1.2 a)VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context with the Channelidentification information element indicating a B-channel that is not subscribed and indicating in thepreferred / exclusive bit "exclusive: only the indicated channel is acceptable", sends a RELEASE COMPLETE messagewith a Cause information element indicating the cause value 82 "identified channel does not exist" and remains in theNull call state.Selection:IUT is a primary rate access. PICS: R 6.2.SIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)13L3N_N00_V_006subclauses 5.1.2 b), 5.1.3 VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context without Called partynumber and Sending complete information element and with the Channel identification information element indicating aB-channel that is available and indicating in the preferred / exclusive bit "indicated channel is preferred", sends aSETUP ACKNOWLEDGE message with the Channel identification information element indicating the requested B-channel and indicating in the preferred / exclusive bit "exclusive: only the indicated channel is acceptable" and entersthe Overlap Sending call state N02.L3N_N00_V_007subclauses 5.1.2 b), 5.1.3VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context without Called partynumber and Sending complete information element and with the Channel identification information element indicating aB-channel that is not available and indicating in the preferred / exclusive bit "indicated channel is preferred", sends aSETUP ACKNOWLEDGE message with the Channel identification information element indicating a B-channel that isavailable and indicating in the preferred / exclusive bit "exclusive: only the indicated channel is acceptable" and entersthe Overlap Sending call state N02.L3N_N00_V_008subclauses 5.1.2 b), 5.1.5.1VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context with a Called partynumber information element providing the complete called party information, with a Sending complete informationelement and with the Channel identification information element indicating a B-channel that is available and indicatingin the preferred / exclusive bit "indicated channel is preferred", sends CALL PROCEEDING message with the Channelidentification information element indicating the requested B-channel and indicating in the preferred / exclusive bit"exclusive: only the indicated channel is acceptable" and enters the Outgoing Call Proceeding call state N03.L3N_N00_V_009subclauses 5.1.2 b), 5.1.5.1VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context with a Called partynumber information element providing the complete called party information, with a Sending complete informationelement and with the Channel identification information element indicating a B-channel that is not available andindicating in the preferred / exclusive bit "indicated channel is preferred", sends CALL PROCEEDING message withthe Channel identification information element indicating a B-channel that is available and indicating in thepreferred / exclusive bit "exclusive: only the indicated channel is acceptable" and enters the Outgoing Call Proceedingcall state N03.L3N_N00_V_010subclause 5.1.2 b)VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context with the Channelidentification information element indicating a B-channel and indicating in the preferred / exclusive bit "indicatedchannel is preferred", when there is no channel available, sends a RELEASE COMPLETE message with a Causeinformation element indicating the cause value 34 "no circuit / channel available" or 44 "requested circuit / channel notavailable" and remains in the Null call state.L3N_N00_V_011subclauses 5.1.2 c), 5.1.3VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context without Called partynumber and Sending complete information element and with the Channel identification information element indicatingin the Info channel selection "any channel", sends a SETUP ACKNOWLEDGE message with the Channel identificationinformation element indicating a B-channel that is available and indicating in the preferred / exclusive bit "exclusive:only the indicated channel is acceptable" and enters the Overlap Sending call state N02.L3N_N00_V_012subclauses 5.1.2 c), 5.1.3VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context without Called partynumber and Sending complete information element and without the Channel identification information element, sends aSETUP ACKNOWLEDGE message with the Channel identification information element indicating a B-channel that isavailable and indicating in the preferred / exclusive bit "exclusive: only the indicated channel is acceptable" and entersthe Overlap Sending call state N02.L3N_N00_V_013subclauses 5.1.2 c), 5.1.5.1VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context with a Called partynumber information element providing the complete called party information, with a Sending complete informationelement and with the Channel identification information element indicating in the Info channel selection "any channel",sends CALL PROCEEDING message with the Channel identification information element indicating a B-channel that isavailable and indicating in the preferred / exclusive bit "exclusive: only the indicated channel is acceptable" and entersthe Outgoing Call Proceeding call state N03.SIST EN 301 060-5:2000

ETSIEN 301 060-5 V1.1.3 (1998-11)14L3N_N00_V_014subclauses 5.1.2 c), 5.1.5.1VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context with a Called partynumber information element providing the complete called party information, with a Sending complete informationelement and without the Channel identification information element, sends CALL PROCEEDING message with theChannel identification information element indicating a B-channel that is available and indicating in thepreferred / exclusive bit "exclusive: only the indicated channel is acceptable" and enters the Outgoing Call Proceedingcall state N03.L3N_N00_V_015subclause 5.1.2 c)VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context with the Channelidentification information element indicating in the Info channel selection "any channel", when there is no channelavailable, sends a RELEASE COMPLETE message with a Cause information element indicating the cause value 34"no circuit / channel available" or 44 "requested circuit / channel not available" and remains in the Null call state.L3N_N00_V_016subclause 5.1.2 c)VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context without the Channelidentification information element, when there is no channel available, sends a RELEASE COMPLETE message with aCause information element indicating the cause value 34 "no circuit / channel available" or 44 "requestedcircuit / channel not available" and remains in the Null call state.L3N_N00_V_017subclause 5.1.3 a)VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context without Called partynumber and without Sending complete information element, sends a SETUP ACKNOWLEDGE message and enters theOverlap Sending call state N02.L3N_N00_V_018subclauses 5.1.3 b), c)VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context with a Called partynumber information element indicating incomplete number information and without a Sending complete informationelement, sends a SETUP ACKNOWLEDGE message and enters the Overlap Sending call state N02.L3N_N00_V_019subclauses 5.1.1, 5.1.4VPNMODEnsure that the IUT in the Null call state N00, on receipt of a SETUP message in a VPN context with a Called partynumber information element indicating incomplete number information and with a Sending complete informationelement, either sends a RELEASE COMPLETE message indicating in the Cause information element one of the causevalues 1 "unassigned (unallocated) number", 3 "no route to destination", 22 "number changed" or 28 "invalid numberformat (incomplete number)" and remains in the Null call state N00;
...