ETSI Plugtests 2007 Test Cases Description 06-SEPT-2007 Release 4

Transcription

1 ETSI Plugtests 2007 Test Cases Description 06-SEPT-2007 Release 4 Plugtests 2007 Test Cases page 1 of 53

2 Table of contents 1 Introduction Scope of the tests Test Environment and Setup Equipment list Implementation details for TS v Implementation details for TS v Test cases: Handover interface for the lawful interception of telecommunications traffic - TS Basic Test Cases Tests Cases: Service-specific details for services for IMAP - TS Tests cases: Service-specific details for IP Multimedia Services - TS Basic Test Cases Tests cases: Service-specific details for PSTN/ISDN Services - TS Basic Test Cases History...53 Plugtests 2007 Test Cases page 2 of 53

3 1 Introduction EVENT DESCRIPTION This event follows upon LI 2006 Plugtests that took place in ETSI headquarters (Sophia Antipolis). Lawful interception (LI) plays a crucial role in helping law enforcement agencies to combat criminal activity. Lawful interception of public telecommunications systems in each country is based on national legislation in that country. The purpose of standardization of lawful interception in ETSI is to facilitate the economic realization of lawful interception that complies with the national and international conventions and legislation. The Technical Committee on Lawful Interception (TC LI) is the leading body for lawful interception standardization within ETSI. LI Plugtests' objective is to validate the work made by ETSI TC LI. As the specifications produced by this committee describe the handover interface between Mediation function and LEMF, the Plugtests event will be focused on this interface. WHAT'S NEW THIS YEAR? In 2007, the event is expanding with the integration of Plugtests concerning VoIP service, and service (for IMAP protocol only). Tests on Internet service (DHCP, PPPoE ) and other protocols (SMTP, POP3) will not be kept this year. To integrate these evolutions, here are the new features added to the test infrastructure: 1 SIP proxy server open source (for tests based on TS part 05) 1 H.323 GK open source (for tests based on TS part 05) 1 PSTN captive network (for tests based on TS part 06 and TS ). This network gives the opportunity to : o Make VoIP-PSTN calls, o Allow PSTN delivery between MD and LEMF. A PRI access (or BRI) on each LI Platform (Mediation and LEMF) will be put in place. 1 IMAP server (for tests based on TS part 02) You will find below the test infrastructure, and the list of the different equipments. ORGANIZATION ETSI intervenes as the organizer of the event, and France Telecom R&D will ensure a role of technical support to ETSI. FTR&D will supply the whole network infrastructure, and will coordinate the technical organization of the event. Plugtests 2007 Test Cases page 3 of 53

4 COMPANIES INVITED TO THE EVENT MEDIATION DEVICE MANUFACTURERS LEMF DEVICE MANUFACTURERS OTHER COMPANIES WHICH PRODUCTS FOLLOW THE SPECIFICATIONS TESTED. For all these companies, the ETSI LI Plugtests will be a measure to test adherence of their product to standards and interoperability. It's a good way for them to get confidence in their solution' strengths as they get feedback from worldwide experts. 1.1 Scope of the tests TS : Handover Interface and Service-Specific Details (SSD) Part 02 : Service-specific details for services. o Objective : to intercept IMAP traffic, and to deliver it on ETSI format (compliant to TS part 01) toward LEMF device. IMAP Interception probe will be provided by the vendors. Part 05 : Service-specific details for IP Multimedia Services o Objective : to intercept VoIP call, and to deliver it on ETSI format (compliant to TS part 01) toward LEMF device. VoIP Interception probe will be provided by the vendors. Part 06 : Service-specific details for PSTN/ISDN services o Objective : a target analog phone places a call to a VoIP subscriber. The call is intercept by the VoIP probe, and is then deliver on ETSI format (compliant to TS part 01) toward LEMF device. VoIP Interception probe will be provided by the vendors. TS : Handover interface for the lawful interception of telecommunications traffic. o Objective : to intercept VoIP call, and to deliver it on ETSI format (compliant to TS ) toward LEMF device. VoIP Interception probe (H.323 and SIP) will be provided by the vendors. 1.2 Test Environment and Setup Plugtests 2007 Test Cases page 4 of 53

5 Figure 1 : Test architecture Plugtests 2007 Test Cases page 5 of 53

6 1.3 Equipment list EQUIPMENTS N Station with VoIP clients (ACT for SIP and SJphone for H.323), and IMAP client (Mozilla Thunderbird) PROVIDED BY FTR&D Target N Analog phone (DECT) FTR&D Vendors solutions N Mediation function N LEMF Platform N SIP Interception probe N IMAP Interception probe Vendors Vendors Vendors Vendors 1 IMAP server Open Source (Dovecot) FTR&D 1 Open IMS (based on Poen SER) FTR&D servers 1 GK H.323 Open Source FTR&D 1 Aggregation router (CISCO 7200) FTR&D 2 Switch 10/100 BaseT Ethernet for VLAN segmentation (CISCO 3560) FTR&D Test Infrastucture 1 MGW IP/PSTN CISCO AS 5350 (SIP and H.323) FTR&D 4 Hub 10/100 BaseT Ethernet FTR&D Cabling FTR&D PSTN captive network FTR&D WiFi HotSpots for Internet access FTR&D N E1 connections to PSTN FTR&D Test tool SILEA (developped by France Telecom) FTR&D 1.4 Implementation details for TS v This chapter proposes "standard" options of TS implementation which could be chosen like basic set-up for the Plugtests 1- Two possible methods for delivery of IRI to the LEMF can be implemented: a) ROSE (TS clause C.1); b) FTP (TS clause C.2). 2- Correlation information will be send on HI3 interface using: a) UUS or b) Called party subaddress 3- For IRIs description, the test plan is defined in accordance with TS v Plugtests 2007 Test Cases page 6 of 53

7 However, for IRI delivery on SIP platform, Annex H of this document can apply, and only IRIs reports are sent to LEMF. 4- Codecs supported for CC delivery are G711 alaw and mulaw, G723-1 and G Implementation details for TS v2.2.1 This chapter proposes "standard" options of TS implementation which could be chosen like basic set-up for the Plugtests 5 Headers 5.1 General The enveloping process must always append the LI header to the start of the envelope Authorization Country Code A two-letter code must be defined for this field. Aqsacom proposes Authorization Country Code = FR Communication Identifier The operator identifier must specify the legally registered name of the service provider. Operator identifier= FTRD The network element identifier must specify the logical name assigned to the network element by the service provider. What should be the network element identifier for a probe? Aqsacom proposes: network element identifier = IP address of the probe Payload direction The payload direction must be specified for CC Interception Point identifier The interception point identifier must specify an 8-character logical name assigned to the interception point by the service provider. Aqsacom proposes: Interception Point identifier = Aqsa 6 Data Exchange General PDU distribution should be achieved through selection of a DF for the PDU on the basis of its LIID i.e. a separate DF must be configured for each LEA and all intercepts for a specific LEA will be distributed through the designated DF for that LEA Aggregation of payloads Payload aggregation shall not be used Sending a large block of application-level data Segmentation shall be applied for application-level data in accordance with this section Padding data Data padding shall not be used Buffering Buffering shall not be used Keep-alives TIME1=120s TIME2=30s TIME3=60s Acknowledging data Data is to be considered as successfully sent once TCP-acknowledgements have been received. Plugtests 2007 Test Cases page 7 of 53

8 7 Delivery Networks Private networks Out of the Plugtests scope: it depends of national law Public networks with strict control Out of the Plugtests scope: it depends of national law Public networks with loose control Out of the Plugtests scope: it depends of national law Confidentiality and Authentication Out of the Plugtests scope: it depends of national law Integrity Out of the Plugtests scope: it depends of national law Test data Test-PDU shall not be used Timeliness Out of the Plugtests scope: it depends of national law. Plugtests 2007 Test Cases page 8 of 53

9 2 Test cases: Handover interface for the lawful interception of telecommunications traffic - TS Basic Test Cases These test cases reflect the basic communication scenarios defined for telecommunications traffic in ETSI TS v ( ) Types of IRI records Event first event of a communication attempt at any time during a communication or communication attempt within the IRI transaction at the end of a communication or communication attempt used in general for non-communication related events iritype BEGIN CONTINUE END REPORT Summary Test case Description P01 Established call : IP (Target) calling IP called P02 Established call : IP calling IP (target) called P03 Called busy: IP (Target) calling IP called is busy (no voic activated) P04 Called no reply, CF on voic IP (Target) calling IP called no reply, voic activated P05 Established call: IP (Target) calling PSTN user called P06 Call hold (CH): IP (Target ) calling other IP user called, PSTN user calls IP Target Target activates CH (Target in a call with PSTN user Target hangs up the call after 30 seconds P07 Established call : IP (Target) calling IP (Target) called P08 Established call: IP (Target) calling IP called PSTN called 3PTY Test Case P01: Successful IP (Target) IP call IP users on SIP platform The target is calling user Action Make a call between target dialling E164 number and another IP client. Calling hangs up the call after 30 seconds. Three records containing the same 'Communication Identity Number' Plugtests 2007 Test Cases page 9 of 53

10 IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0001' 2- HI3 CC record LIID = '0001' Direction Network Identifier LEMF Address 3- HI2 End record LIID = '0001' Ringing duration (optional) Conversation duration (optional) (optional) Release cause of intercepted call (optional) Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P02: Successful IP IP (Target) call IP users on SIP platform The target is called user Action Make a call between a IP client dialling E164 number of the target. Calling hangs up the call after 30 seconds. Plugtests 2007 Test Cases page 10 of 53

11 Three records containing the same 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0002' 2- HI3 CC record LIID = '0002' Direction Network Identifier LEMF Address 3- HI2 End record LIID = '0002' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P03: Successful IP (Target) IP, Callee busy, no voic IP users on SIP platform The target is calling user Action Plugtests 2007 Test Cases page 11 of 53

12 Try to make a call between target dialling E164 number and another IP client. Called is busy, no call established with called user Two records containing the same 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0003' 2- no HI3 CC record no media streams 3- HI2 End record LIID = '0003' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P04: Successful IP (Target) IP call: Callee no reply, voic activated IP users on SIP platform The target is calling user Action Try to make a call between target dialling E164 number and another IP client. Called no answer, voic activate, Plugtests 2007 Test Cases page 12 of 53

13 Three records containing the same 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0004' 2- HI3 CC record LIID = '0004' Direction Network Identifier LEMF Address 3- HI2 End record LIID = '0004' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P05: Successful IP (Target) PSTN call IP users on SIP platform The target is calling user Action Plugtests 2007 Test Cases page 13 of 53

14 Make a call between target dialling E164 number and another IP client. Called hangs up the call after 30 seconds. Three records containing the same 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0005' 2- HI3 CC record LIID = '0005' Direction Network Identifier LEMF Address 3- HI2 End record LIID = '0005' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P06: Call Hold (CH): IP (Target ) calling other IP user called, PSTN user calls IP Target Target activates Call Hold A = IP target Plugtests 2007 Test Cases page 14 of 53

15 B = another IP client C = PSTN user Action Make a call between A (dialling E164 number) and B. C calls A. A activates CH (Established call between A and C) A hangs up the call after 30 seconds. A activates CH and establishes the call with B. After 30 seconds of call, B hangs up the call. Records of the first call containing the same 'Communication Identity Number' Records of the second call containing another 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0006' 2- HI3 CC record LIID = '0006' Direction Network Identifier LEMF Address 3- HI2 Begin record LIID = '0006' CIN = 'value1' Call hold indication Plugtests 2007 Test Cases page 15 of 53

16 Or 3bis- HI2 Continue record IRIType='Continue' LIID = '0006' Call hold indication 4- HI3 CC record LIID = '0006' CIN = 'value1' or 'value' Direction Network Identifier LEMF Address 5- HI2 End record LIID = '0006' CIN = 'value1' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) 6- HI2 End record LIID = '0006' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) Plugtests 2007 Test Cases page 16 of 53

17 Remarks If an IRI Continue has been generated, it should imply that only one IRI End would be generated The CIN 'value' must be the same for all the sequence of IRI The CIN 'value1' must be the same for all the sequence of IRI Test Case P07: Successful IP (Target) IP (Target) IP users on SIP platform Calling user and called user are targets Action Make a call between calling target dialling E164 number and another IP client (called target). Calling hangs up the call after 30 seconds. Six records containing the same 'Communication Identity Number' and two different LIID IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0007' 2- HI2 Begin record IRIType = 'Begin' LIID = '0017' 3- HI3 CC record LIID = '0007' Direction Plugtests 2007 Test Cases page 17 of 53

18 Network Identifier LEMF Address 4- HI3 CC record LIID = '0017' Direction Network Identifier LEMF Address 5- HI2 End record LIID = '0017' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) 6- HI2 End record LIID = '0007' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P08: Established call: IP (Target) calling IP called PSTN called 3PTY A = IP target Plugtests 2007 Test Cases page 18 of 53

19 B = another IP client C = PSTN user Action Make a call between A (dialling E164 number) and B. A activates CH and establishes call with C A activates CONF and establishes the call with B and C. After 30 seconds of call, A hangs up the call. Records of the first call containing the same 'Communication Identity Number' Records of the second call containing another 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0008' 2- HI3 CC record LIID = '0008' Direction Network Identifier LEMF Address 3- HI2 Begin record LIID = '0008' CIN = 'value1' or 3bis- HI2 Continue record Plugtests 2007 Test Cases page 19 of 53

20 IRIType='Continue' LIID = ' HI3 CC record LIID = '0008' CIN = 'value1' Direction Network Identifier LEMF Address 5- HI2 Continue record IRIType='Continue' LIID = '0008 or 'value1' 6- HI2 End record LIID = '0018' CIN = 'value1' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) 7- HI2 End record LIID = '0008' Ringing duration (optional) Conversation duration (optional) Plugtests 2007 Test Cases page 20 of 53

21 Release cause of intercepted call (optional) Remarks The CIN 'value' must be the same for all the sequence of IRI The CIN 'value1' must be the same for all the sequence of IRI Plugtests 2007 Test Cases page 21 of 53

22 3 Tests Cases: Service-specific details for services for IMAP - TS In the test cases description, some points appear underlined in yellow. This is because TS is not clear on these specific points, and will certainly need clarifications. Two drafts of Change Request against TS have been written by France Telecom R&D in order to use IMAP4 in ASN.1 description. They are minor changes in protocol-id and event-type fields and can be found on Plugtests website (CR008 and CR009). As next LI attendance is in Berlin in October, they might be approved there. For most of the tests, Mozilla Thunderbird will be used as IMAP4 client. Some "php" scripts will be created for some specific tests. These test cases reflect the basic communication scenarios defined for IMAP4 in Table C.1 and C.2 in TS Version UID FETCH do COPY, FETCH or STORE on part of message(s) based on specified UID, instead of message sequence number Table C.1: IMAP4 and related LI events IMAP4 Command Description ASN.1 -Event iritype LOGIN login client using -logon Begin cleartext username+password AUTHENTICATE authenticate client -logon Begin according to RFC 2222 [16] SASL FETCH Retrieve message(s) -download Report according to specified criteria FETCH Retrieve parts of -partialdownload Report message(s) according to specified criteria APPEND append argument as -upload Report last mail in mailbox UID FETCH do COPY, FETCH or STORE on message(s) based on specified UID, instead of message sequence number -download Report -partialdownload LOGOUT close session -logoff End Report Table C.2: Mapping of IMAP4 response and ASN.1 -Status field IMAP 4 Response Value of ASN.1 -Status OK Successful NO Failed Remark: According to C.1 table of TS , IRI Begin can be started on reception of Login or Authenticate message. Login option will be firstly selected Plugtests 2007 Test Cases page 22 of 53

23 Test Case P01: Successful Log On / Log Off Environment and setup as specified in section 1.2. Action Client connects to the IMAP4 server, logs on successfully as target, and logs off immediately. First case: used the Thunderbird client. Second case: used the script TestCaseP01.php (Entry your IMAP login in file config_imap.inc.php3). Four records containing the same 'Communication Identity Number' 1- HI2 Begin record with protocol-id = 'imap4' (3) eventtype = -logon (5) status = successful (3) client-address, server-address, client-port and server-port as specified in [2], section B HI3 CC record with authentication data -format = 'ip-packet' (1) or 'application' (2) content containing authentication data in string format (login name, password, server answer) 3- HI2 End record with protocol-id = 'imap4' (3) eventtype = -logoff (7) status = successful (3) client-address, server-address, client-port and server-port as specified in [2], section B HI3 CC record -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (logout, server answer) Remarks Test Case P02: Unsuccessful Log On Environment and setup as specified in section 1.2. Plugtests 2007 Test Cases page 23 of 53

24 This transaction can only be captured if the target login id was correct (so that the target may be identified) and the password was incorrect. If the login id itself is incorrect, the transaction will not be captured because the target will not match any capture rule. Action Client connects to the IMAP4 server and tries to log in as "target", but using a wrong password. The IMAP4 server will thus deny access. First case (authenticate method): used the Thunderbird client. Second case (login method): used the script TestCaseP01.php (Entry your IMAP login and a bad password in file config_imap.inc.php3). Two records containing the same 'Communication Identity Number' 1- HI2 Report record with protocol-id = 'imap4' (3) eventtype = -logon (5) status = operation-failed (2) client-address, server-address, client-port and server-port, 2- HI3 CC record -format = 'ip-packet' (1) or 'application' (2) content containing authentication data in string format (login name, password, server answer) Remarks Test Case P03: Successful Logon / Mail Download / Logoff Environment and setup as specified in section 1.2. An has been sent to the target and one additional address. Except for this the target's mailbox should be empty. Action Client connects to the IMAP4 server, logs in as "target" and downloads the unread message and logs off. Used the script TestCaseP03.php (Enter your MAP login in file config_imap.inc.php3). Seven records containing the same 'communication Identity Number' 1- HI2 Begin record with protocol-id = 'imap4' (3) Plugtests 2007 Test Cases page 24 of 53

25 eventtype = -logon (5) status = successful (3) client-address, server-address, client-port and server-port. 2- HI3 CC record with authentication data -format = 'ip-packet' (1) or 'application' (2) content containing authentication data in string format (login name, password, server answer) 3- HI3 CC record with SEEN/UNSEEN message data protocol-id = 'imap4' (3) -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (EXIST, FLAGS, RECENT, server answer) 4- HI2 Report* record with protocol-id = 'imap4' (3) eventtype** = -partial-download (8) status = successful (3) client-address, server-address, client-port and server-port as specified. * see remark 5- HI3 CC record with data -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (sequence number msg, RFC822 message) 6- HI2 End record with protocol-id = 'imap4' (3) eventtype = -logoff (7) status = successful (3) client-address, server-address, client-port and server-port 7- HI3 CC record -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (logout, server answer) Remarks *: IRI report may be IRI Continue **: eventtype may be -download if all message information are received Test Case P04: Successful Log On \ Header Download \ Log Off Plugtests 2007 Test Cases page 25 of 53

26 Environment and setup as specified in section 1.2. An with at least 20 lines of content has been sent to the target. The target's mailbox should be empty otherwise. Action Client connects to the IMAP4 server and logs in as "target". The client then issues a UID FETCH command to download the header of the new message. Client finally logs off. Used the Thunderbird client. Seven records containing the same 'Communication Identity Number' 1- HI2 Begin record with protocol-id = 'imap4' (3) eventtype = -logon (5) status = successful (3) client-address, server-address, client-port and server-port. 2- HI3 CC record with authentication data -format = 'ip-packet' (1) or 'application' (2) content containing authentication data in string format (login name, password, server answer) 3- HI3 CC record with SEEN/UNSEEN message data -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (EXIST, FLAGS, RECENT, server answer) 4- HI2 Report* record with protocol-id = 'imap4' (3) eventtype** = -partial-download (8) status = successful (3) client-address, server-address, client-port and server-port. 5- HI3 CC record with data -format = 'ip-packet' (1) or 'application' (2) content containing data in string format 6- HI2 End record with protocol-id = 'imap4' (3) eventtype = -logoff (7) status = successful (3) client-address, server-address, client-port and server-port. Plugtests 2007 Test Cases page 26 of 53

27 7- HI3 CC record -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (logout, server answer) Remarks *: IRI report may be IRI Continue **: eventtype may be -download if all message information are received Test Case P05: Successful Log On \ Unsuccessful Download \ Log Off Environment and setup as specified in section 1.2. Action Client connects to the IMAP4 server and logs in as target. Use the php script provided "TestCaseP05.php". (This script consults the message with ID 9999). The client then issues a FETCH command to download an . However the message number specified (9999) does not exist on the server. The command will thus fail. Used the script TestCaseP05.php (Enter your IMAP login in file config_imap.inc.php3). Seven records containing the same Communication Identity Number. 1- HI2 Begin record with protocol-id = 'imap4' (3) eventtype = -logon (5) status = successful (3) client-address, server-address, client-port and server-port 2- HI3 CC record with authentication data -format = 'ip-packet' (1) or 'application' (2) content containing authentication data in string format (login name, password, server answer) 3- HI3 CC record with SEEN/UNSEEN message data -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (EXIST, FLAGS, RECENT, server answer) 4- HI2 Report* record with protocol-id = 'imap4' (3) eventtype** = -partial-download (8) status = operation-failed (2) client-address, server-address, client-port and server-port Plugtests 2007 Test Cases page 27 of 53

28 5- HI3 CC record with data -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (server answer (NO) ) 6- HI2 End record with protocol-id = 'imap4' (3) eventtype = -logoff (7) status = successful (3) client-address, server-address, client-port and server-port 7- HI3 CC record -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (logout, server answer) Remarks *: IRI report may be IRI Continue **: eventtype may be -download if all message information are received Test Case P06: Successful Logon / Mail Download (UID FETCH) / Logoff Environment and setup as specified in section 1.2. Action Client connects to the IMAP4 server, logs in as "target" and downloads the unread UID message and logs off. Used the Thunderbird client open an unread message. Seven records containing the same 'communication Identity Number' 1- HI2 Begin record with protocol-id = 'imap4' (3) eventtype = -logon (5) status = successful (3) client-address, server-address, client-port and server-port 2- HI3 CC record with authentication data -format = 'ip-packet' (1) or 'application' (2) content containing authentication data in string format (login name, password, server answer) Plugtests 2007 Test Cases page 28 of 53

29 3- HI3 CC record with SEEN/UNSEEN message data -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (EXIST, FLAGS, RECENT, server answer) 4- HI2 Report* record with protocol-id = 'imap4' (3) eventtype** = -partial-download (8) status = successful (3) client-address, server-address, client-port and server-port 5- HI3 CC record with data -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (UID msg, RFC822 message) 6- HI2 End record with protocol-id = 'imap4' (3) eventtype = -logoff (7) status = successful (3) client-address, server-address, client-port and server-port 7- HI3 CC record -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (logout, server answer) Remarks *: IRI report may be IRI Continue **: eventtype may be -download if all message information are received Test Case P07: Successful Logon / APPEND / Logoff Environment and setup as specified in section 1.2. Action Client connects to the IMAP4 server, logs in as "target" and creates new message and logs off. Used the Thunderbird client, creates new draft message. Seven records containing the same 'communication Identity Number' Plugtests 2007 Test Cases page 29 of 53

30 1- HI2 Begin record with protocol-id = 'imap4' (3) eventtype = -logon (5) status = successful (3) client-address, server-address, client-port and server-port 2- HI3 CC record with authentication data -format = 'ip-packet' (1) or 'application' (2) content containing authentication data in string format (login name, password, server answer) 3- HI3 CC record with SEEN/UNSEEN message data -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (EXIST, FLAGS, RECENT, server answer) 4- HI2 Report* record with protocol-id = 'imap4' (3) eventtype = -upload (9) status = successful (3) client-address, server-address, client-port and server-port 5- HI3 CC record with data -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (server answer) 6- HI2 End record with protocol-id = 'imap4' (3) eventtype = -logoff (7) status = successful (3) client-address, server-address, client-port and server-port 7- HI3 CC record -format = 'ip-packet' (1) or 'application' (2) content containing data in string format (logout, server answer) Remarks *: IRI report may be IRI Continue Plugtests 2007 Test Cases page 30 of 53

31 4 Tests cases: Service-specific details for IP Multimedia Services - TS Basic Test Cases These test cases reflect the basic communication scenarios defined for IP multimedia services in ETSI TS V2.1.1 ( ) Table 1: Mapping between IP MM Events and HI2 Records Type Event At assignment of a new CIN value All intermediate signalling, other than the last event The last event related to a communication session Delayed IRI events related to an already ended session Events that are not mapped iritype BEGIN CONTINUE END REPORT REPORT NOTE: Not mapped events could for example be encapsulated SIP messages. Summary Test case Description P01 Established call : IP (Target) calling IP called P02 Established call : IP calling IP (target) called P03 Called busy: IP (Target) calling IP called is busy (no voic activated) P04 Called no reply, CF on voic IP (Target) calling IP called no reply, voic activated P05 Established call: IP (Target) calling PSTN user called P06 Call hold (CH): IP (Target ) calling other IP user called, PSTN user calls IP Target Target activates CH (Target in a call with PSTN user Target hangs up the call after 30 seconds P07 Established call : IP (Target) calling IP (Target) called P08 Established call: IP (Target) calling IP called PSTN called 3PTY Test Case P01: Successful IP (Target) IP call IP users on SIP platform The target is calling user Action Make a call between target dialling E164 number and another IP client. Calling hangs up the call after 30 seconds. Three records containing the same 'Communication Identity Number' Plugtests 2007 Test Cases page 31 of 53

32 IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0001' ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent 2- HI3 CC record LIID = '0001' rtpcccontents = copy of the media streams 3- HI2 End record LIID = '0001' ipiricontents= 'sipmessage' (1) SipMessage contains ipsourceadress, ipdestinationadress, sipcontent Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P02: Successful IP IP (Target) call IP users on SIP platform The target is called user Action Make a call between a IP client dialling E164 number of the target. Calling hangs up the call after 30 seconds. Three records containing the same 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0002' Plugtests 2007 Test Cases page 32 of 53

33 ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent 2- HI3 CC record LIID = '0002' rtpcccontents = copy of the media streams 3- HI2 End record LIID = '0002' ipiricontents= 'sipmessage' (1) SipMessage contains ipsourceadress, ipdestinationadress, sipcontent Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P03: Successful IP (Target) IP, Callee busy, no voic IP users on SIP platform The target is calling user Action Try to make a call between target dialling E164 number and another IP client. Called is busy, no call established with called user Two records containing the same 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0003' ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent 2- no HI3 CC record Plugtests 2007 Test Cases page 33 of 53

34 no media streams 3- HI2 End record LIID = '0003' ipiricontents= 'sipmessage' (1) SipMessage contains ipsourceadress, ipdestinationadress, sipcontent Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P04: Successful IP (Target) IP call: Callee no reply, voic activated IP users on SIP platform The target is calling user Action Try to make a call between target dialling E164 number and another IP client. Called no answer, voic activate, Three records containing the same 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0004' ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent 2- HI3 CC record LIID = '0004' rtpcccontents = copy of the media streams 3- HI2 End record LIID = '0004' Plugtests 2007 Test Cases page 34 of 53

35 ipiricontents= 'sipmessage' (1) SipMessage contains ipsourceadress, ipdestinationadress, sipcontent Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P05: Successful IP (Target) PSTN call IP users on SIP platform The target is calling user Action Make a call between target dialling E164 number and another IP client. Called hangs up the call after 30 seconds. Three records containing the same 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0005' ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent 2- HI3 CC record LIID = '0005' rtpcccontents = copy of the media streams 3- HI2 End record LIID = '0005' ipiricontents= 'sipmessage' (1) SipMessage contains ipsourceadress, ipdestinationadress, sipcontent Remarks The CIN 'value' must be the same for all the sequence of IRI Plugtests 2007 Test Cases page 35 of 53

36 Test Case P06: Call hold (CH): IP (Target ) calling other IP user called, PSTN user calls IP Target Target activates CH A = IP target B = another IP client C = PSTN user Action Make a call between A (dialling E164 number) and B. C calls A. A activates CH (Established call between A and C) A hangs up the call after 30 seconds. A activates CH and establishes the call with B. After 30 seconds of call, B hangs up the call. Records of the first call containing the same 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0006' CIN = '000001' ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent 2- HI3 CC record LIID = '0006' rtpcccontents = copy of the media streams 3- HI2 Begin record LIID = '0006'. ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent, Call hold indication or Plugtests 2007 Test Cases page 36 of 53

37 3bis- HI2 Continue record IRIType='Continue' LIID = '00006' ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent, Call hold indication 4- HI3 CC record LIID = '0006' rtpcccontents = copy of the media streams 5- HI2 End record LIID = '00006' ipiricontents= 'sipmessage' (1) SipMessage contains ipsourceadress, ipdestinationadress, sipcontent 7- HI2 End record LIID = '0006' ipiricontents= 'sipmessage' (1) SipMessage contains ipsourceadress, ipdestinationadress, sipcontent Remarks If an IRI Continue has been generated, it should imply that only one IRI End would be generated The CIN 'value' must be the same for all the sequence of IRI Test Case P07: Successful IP (Target) IP (Target) IP users on SIP platform Calling user and called user are targets Plugtests 2007 Test Cases page 37 of 53

38 Action Make a call between calling target dialling E164 number and another IP client (called target). Calling hangs up the call after 30 seconds. Six records containing the same 'Communication Identity Number' and two different LIID IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0007' ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent 2- HI2 Begin record LIID = '0017' ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent 3- HI3 CC record LIID = '0007' rtpcccontents = copy of the media streams 4- HI3 CC record LIID = '0017' rtpcccontents = copy of the media streams 5- HI2 End record LIID = '0007' ipiricontents= 'sipmessage' (1) SipMessage contains ipsourceadress, ipdestinationadress, sipcontent 6- HI2 End record Plugtests 2007 Test Cases page 38 of 53

39 LIID = '0017' ipiricontents= 'sipmessage' (1) SipMessage contains ipsourceadress, ipdestinationadress, sipcontent Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P08: Established call: IP (Target) calling IP called PSTN called 3PTY A = IP target B = another IP client C = PSTN user Action Make a call between A (dialling E164 number) and B. A activates CH and establishes call with C A activates CONF and establishes the call with B and C. After 30 seconds of call, A hangs up the call. Seven records containing CIN IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0008' ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent 2- HI13 CC record LIID = '0008' rtpcccontents = copy of the media streams Plugtests 2007 Test Cases page 39 of 53

40 3- HI2 Begin record LIID = '0008' CIN = 'value1' ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent 3bis- HI2 Continue record IRIType='Continue' LIID = '0008' ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent 4- HI3 CC record LIID = '0018' CIN = 'value1' rtpcccontents = copy of the media streams 5- HI2 Continue record IRIType='Continue' LIID = '0008' ipiricontents= 'sipmessage' (1) sipmessage contains ipsourceadress, ipdestinationadress, sipcontent 6- HI2 End record LIID = '0008' ipiricontents= 'sipmessage' (1) SipMessage contains ipsourceadress, ipdestinationadress, sipcontent 7- HI2 End record LIID = '0018' CIN = 'value1' ipiricontents= 'sipmessage' (1) SipMessage contains ipsourceadress, ipdestinationadress, sipconten Plugtests 2007 Test Cases page 40 of 53

41 Remarks The CIN 'value' must be the same for all the sequence of IRI The CIN 'value1' must be the same for all the sequence of IRI Plugtests 2007 Test Cases page 41 of 53

42 5 Tests cases: Service-specific details for PSTN/ISDN Services - TS Basic Test Cases These test cases reflect the basic communication scenarios defined for PSTN/ISDN services in ETSI TS V2.2.1 (2007-5) Type of IRI record (Defined as per TS ) Event first event of a communication attempt at any time during a communication or communication attempt within the IRI transaction at the end of a communication or communication attempt used in general for non-communication related events iritype BEGIN CONTINUE END REPORT Summary Test case Description P01 Established call: PSTN (Target) calling IP user called P02 Called busy: PSTN (Target) calling IP called is busy (no voic activated) P03 Called no reply, CF on voic PSTN (Target) calling IP called no reply, voic activated P04 Call hold (CH): PSTN (Target ) calling other IP user called, PSTN user calls IP Target Target activates CH (Target in a call with PSTN user Target hangs up the call after 30 seconds P05 Established call : PSTN (Target) calling IP (Target) called P06 Established call: PSTN (Target) calling IP called PSTN called 3PTY Test Case P01: Successful PSTN (Target) IP call IP user on SIP platform The target is calling user Action Make a call between target dialling E164 number and another IP client. Called hangs up the call after 30 seconds. Three records containing the same 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) Plugtests 2007 Test Cases page 42 of 53

43 1- HI2 Begin record LIID = '0003' 2- HI3 CC record LIID = '0003' Direction Network Identifier LEMF Address 3- HI2 End record LIID = '0003' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P02: Successful PSTN (Target) IP, Callee busy, no voic IP user on SIP platform The target is calling user Action Try to make a call between target dialling E164 number and another IP client. Called is busy, no call established with called user Plugtests 2007 Test Cases page 43 of 53

44 Two records containing the same 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0004' 2- no HI3 CC record no media streams 3- HI2 End record LIID = '0004' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P03: Successful PSTN (Target) IP call: Callee no reply, voic activated IP user on SIP platform The target is calling user Action Try to make a call between target dialling E164 number and another IP client. Called no answer, voic activate, Three records containing the same 'Communication Identity Number' Plugtests 2007 Test Cases page 44 of 53

45 IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0005' 2- HI3 CC record LIID = '0005' Direction Network Identifier LEMF Address 3- HI2 End record LIID = '0005' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P04: Call hold (CH): PSTN (Target ) calling other IP user called, PSTN user calls IP Target Target activates CH A = IP target B = another IP client C = PSTN user Plugtests 2007 Test Cases page 45 of 53

46 Action Make a call between A (dialling E164 number) and B. C calls A. A activates CH (Established call between A and C) A hangs up the call after 30 seconds. A activates CH and establishes the call with B. After 30 seconds of call, B hangs up the call. Records of the first call containing the same 'Communication Identity Number' Records of the second call containing another 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0006' 2- HI3 CC record LIID = '0016' Direction Network Identifier LEMF Address 3- HI2 Begin record LIID = '0016' Call hold indication Or Plugtests 2007 Test Cases page 46 of 53

47 3Bis- HI2 Continue record IRIType='Continue' LIID = '0006' Call hold indication 4- HI3 CC record LIID = '0016' CIN = 'value1' or 'value'' Direction Network Identifier LEMF Address 5- HI2 End record LIID = '00016' CIN = 'value1' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) 6- HI2 End record LIID = '0006' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) Plugtests 2007 Test Cases page 47 of 53

48 Remarks If an IRI Continue has been generated, it should imply that only one IRI End would be generated The CIN 'value' must be the same for all the sequence of IRI The CIN 'value1' must be the same for all the sequence of IRI Test Case P05: Successful PSTN (Target) IP (Target) IP user on SIP platform Calling user and called user are targets Action Make a call between calling target dialling E164 number and another IP client (called target). Calling hangs up the call after 30 seconds. Six records containing the same 'Communication Identity Number' and two different LIID IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0007' 2- HI2 IRIType='Begin' LIID = '0017' 3- HI3 CC record LIID = '0007' Direction Network Identifier LEMF Address Plugtests 2007 Test Cases page 48 of 53

49 4- HI3 CC record LIID = '0017' rtpcccontents = copy of the media streams 5- HI2 End record LIID = '0007' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) 6- HI2 End record LIID = '00017' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) Remarks The CIN 'value' must be the same for all the sequence of IRI Test Case P06: Established call: PSTN (Target) calling IP called PSTN called 3PTY A = IP target B = another IP client C = PSTN user Plugtests 2007 Test Cases page 49 of 53

50 Action Make a call between A (dialling E164 number) and B. A activates CH and establishes call with C A activates CONF and establishes the call with B and C. After 30 seconds of call, A hangs up the call. Seven records containing the same 'Communication Identity Number' IRIs Continue can be also generated during the call to indicate some events (e g: called response) 1- HI2 Begin record LIID = '0008' 2- HI3 CC record LIID = '0008' Direction Network Identifier LEMF Address 3- HI2 Begin record LIID = '0088' CIN = 'value1' or 3Bis- HI2 Continue record LIID = '0008' Plugtests 2007 Test Cases page 50 of 53

51 4- HI3 CC record LIID = '0018' CIN = 'value1' Direction Network Identifier LEMF Address 5- HI2 Continue record IRIType='Continue' LIID = '0008' or 'value1' 6- HI2 End record LIID = '0018' CIN = 'value1' Ringing duration (optional) Conversation duration (optional) Release cause of intercepted call (optional) 7- HI2 End record LIID = '0008' Ringing duration (optional) Conversation duration (optional) Plugtests 2007 Test Cases page 51 of 53

52 Release cause of intercepted call (optional) Remarks The CIN 'value' must be the same for all the sequence of IRI The CIN 'value1' must be the same for all the sequence of IRI Plugtests 2007 Test Cases page 52 of 53

53 6 History 11-JUL-2007 FTR&D: Initial tests cases for services, PSTN/ISDN services, Telecommunications traffic Release 2 18-JUL-2007 FTR&D: For taking into account remarks of Aqsacom and correction of some errors of release 1 Release 3 Release 4 06-SEPT-2007 FTR&D: clarification on the IMAP part 12-SEPT-2007 FTR&D: clarification on the IMAP part for the test methodology Plugtests 2007 Test Cases page 53 of 53