ETSI TS 101 553-2 V4.1.1 (2016-09)

TECHNICAL SPECIFICATION
Core Network and Interoperability Testing (INT);
Testing of the IBCF requirements;
(3GPP Release 12);
Part 2: Test Suite Structure and Test Purposes (TSS&TP)

2 ETSI TS 101 553-2 V4.1.1 (2016-09)

Reference
RTS/INT-00133-2
Keywords
IBCF, SIP, testing, TSS&TP
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2016.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 101 553-2 V4.1.1 (2016-09)
Contents
Intellectual Property Rights . 4
Foreword. 4
Modal verbs terminology . 4
1 Scope . 5
2 References . 5
2.1 Normative references . 5
2.2 Informative references . 6
3 Definitions, symbols and abbreviations . 7
3.1 Definitions . 7
3.2 Symbols . 7
3.3 Abbreviations . 7
4 Test Suite Structure (TSS) . 7
5 Test Purposes (TP) . 8
5.1 Naming convention and strategy . 8
5.1.0 Introduction . 8
5.1.1 TP naming convention . 8
5.1.2 Test strategy . 8
6 Test purposes IBCF test . 8
6.1 IBCF as an exit point . 8
6.1.1 Registration . 8
6.1.2 Basic call . 12
6.1.3 Screening of SIP signalling . 28
6.1.3.1 Basic call requirements . 28
6.1.3.2 Simulation services . 133
6.1.3.2.1 Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) . 133
6.1.3.2.2 Terminating Identification Presentation (TIP) and Terminating Presentation Restriction (TIR) . 134
6.1.3.2.3 Communication Diversion service . 136
6.1.3.2.4 Other Simulation services . 138
6.1.4 Network configuration hiding . 161
6.1.4.1 Registration. 161
6.1.4.2 Basic call requirements . 163
6.1.5 Application level gateway . 170
6.1.5.1 Treatment of SIP signalling . 170
6.1.5.2 Treatment of session and media description . 196
6.2 IBCF as an entry point . 204
6.2.1 Registration . 204
6.2.2 Basic call . 207
6.2.3 Screening of SIP signalling . 222
6.2.3.1 Basic call requirements . 222
6.2.3.2 Simulation services . 327
6.2.3.2.1 Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) . 327
6.2.3.2.2 Terminating Identification Presentation (TIP) and Terminating Presentation Restriction (TIR) . 328
6.2.3.2.3 Communication Diversion service . 333
6.2.3.2.4 Other Simulation services . 339
6.2.4 Network configuration hiding . 361
6.2.4.1 Registration. 361
6.2.4.2 Basic call requirements . 362
6.2.5 Application level gateway . 364
6.2.5.1 Treatment of SIP signalling . 364
6.2.5.2 Treatment of session and media description . 389
Annex A (informative): Bibliography . 397
History . 398

ETSI
4 ETSI TS 101 553-2 V4.1.1 (2016-09)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (https://ipr.etsi.org/).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI Technical Committee Core Network and Interoperability
Testing (INT).
The present document is part 2 of a multi-part deliverable covering the Testing of the IBCF requirements, as identified
below:
Part 1: "Protocol Implementation Conformance Statement (PICS)";
Part 2: "Test Suite Structure and Test Purposes (TSS&TP)".
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
5 ETSI TS 101 553-2 V4.1.1 (2016-09)
1 Scope
The present document specifies the test suite structure and test purposes of testing of the IBCF requirements. The focus
is the Ic interface as the interconnection point between two network operators.
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI TS 124 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session
Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3
(3GPP TS 24.229 Release 9)".
[2] ETSI TS 129 165: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Inter-IMS Network to Network Interface (NNI)
(3GPP TS 29.165 Release 9)".
[3] ETSI TS 101 553-1: "Core Network and Interoperability Testing (INT); Testing of the IBCF
requirements; (3GPP Release 9); Part 1: Protocol Implementation Conformance Statement
(PICS)".
[4] ETSI TS 124 407: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services;
Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR);
Protocol specification (3GPP TS 24.407 Release 8)".
[5] ETSI TS 124 508: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; PSTN/ISDN simulation services Terminating
Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol
specification (3GPP TS 24.508 Release 8)".
[6] ETSI TS 124 505: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services:
Conference (CONF); Protocol specification (3GPP TS 24.505 Release 8)".
[7] ETSI TS 124 406: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services; Message
Waiting Indication (MWI): Protocol specification (3GPP TS 24.406 Release 8)".
[8] ETSI TS 124 410: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; NGN Signalling Control Protocol;
Communication HOLD (HOLD) PSTN/ISDN simulation services; Protocol specification
(3GPP TS 24.410 Release 8)".
ETSI
6 ETSI TS 101 553-2 V4.1.1 (2016-09)
[9] ETSI TS 124 411: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services:
Anonymous Communication Rejection (ACR) and Communication Barring (CB); Protocol
specification (3GPP TS 24.411 Release 8)".
[10] ETSI TS 124 516: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services;
Malicious Communication Identification (MCID); Protocol specification
(3GPP TS 24.516 Release 8)".
[11] ETSI TS 124 529: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services: Explicit
Communication Transfer (ECT); Protocol specification (3GPP TS 24.529 Release 8)".
[12] ETSI TS 124 454: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services; Protocol
specification Closed User Group (CUG) (3GPP TS 24.454 Release 8)".
[13] ETSI TS 123 002: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Network architecture (3GPP TS 23.002 Release 9)".
[14] ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS); Stage 2
(3GPP TS 23.228 Release 9)".
[15] IETF RFC 7044: "An Extension to the Session Initiation Protocol (SIP) for Request History
Information".
[16] IETF RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Asserted Identity
within Trusted Networks".
[17] ETSI TS 129 162: "Digital cellular telecommunications system (Phase 2+); Universal Mobile
Telecommunications System (UMTS); LTE; Interworking between the IM CN subsystem and IP
networks (3GPP TS 29.162)".
[18] IETF RFC 2663: "IP Network Address Translator (NAT) Terminology and Considerations".
[19] IETF RFC 3261: "SIP: Session Initiation Protocol".
[20] IETF RFC 4028: "Session Timers in the Session Initiation Protocol (SIP)".
[21] IETF RFC 4412: "Communications Resource Priority for the Session Initiation Protocol (SIP)".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] IEEE 802.11a-1999: "IEEE Standard for Telecommunications and Information Exchange Between
Systems - LAN/MAN Specific Requirements - Part 11: Wireless Medium Access Control (MAC)
and physical layer (PHY) specifications: High Speed Physical Layer in the 5 GHz band".
ETSI
7 ETSI TS 101 553-2 V4.1.1 (2016-09)
3 Definitions, symbols and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in [1] to [19] apply.
NOTE: This may contain additional information.
3.2 Symbols
For the purposes of the present document, the symbols given in [1] to [19] apply.
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in [1] to [19] apply.
4 Test Suite Structure (TSS)
The Test Suite Structure is in close alignment with clause 5.10, ETSI TS 124 229 [1].
Exit_Point
reg IBCF_101_xxx
bcall IBCF_102_xxx
scr bcall IBCF_103_xxx
ss oip-oir IBCF_104_xxx
ss/tip-tir IBCF_105_xxx
cdiv IBCF_106_xxx
other IBCF_107_xxx
nch reg IBCF_108_xxx
bcall IBCF_109_xxx
alg sip IBCF_110_xxx
sdp IBCF_111_xxx
Entry_Point
reg IBCF_201_xxx
bcall IBCF_202_xxx
scr bcall IBCF_203_xxx
oip-oir IBCF_204_xxx
tip-tir IBCF_205_xxx
cdiv IBCF_206_xxx
other IBCF_207_xxx
nch reg IBCF_208_xxx
bcall IBCF_209_xxx
alg sip IBCF_210_xxx
sdp IBCF_211_xxx
ETSI
8 ETSI TS 101 553-2 V4.1.1 (2016-09)
5 Test Purposes (TP)
5.1 Naming convention and strategy
5.1.0 Introduction
For each requirement in ETSI TS 124 229 [1] a TP is defined.
5.1.1 TP naming convention
TPs are numbered, starting at 001, within each group. Groups are organized according to the TSS. Additional references
are added to identify the actual test suite and whether it applies to the network or the user (see table 5.1.1-1).
Table 5.1.1-1: TP identifier naming convention scheme
Identifier: IBCF__
= group 3 digit field representing group reference according to TSS
= TP number 3 digit sequential number (001-999)

5.1.2 Test strategy
As the base standard ETSI TS 124 229 [1] contains no explicit requirements for testing, the TPs were generated as a
result of an analysis of the base standard and the PICS specification ETSI TS 101 553-1 [3]. The criteria applied include
the following:
 whether or not a test case can be built from the TP is not considered.
6 Test purposes IBCF test
6.1 IBCF as an exit point
6.1.1 Registration
TP number IBCF_101_001 Reference 5.10.2.1 3) [1]
TSS reference Exit_Point/reg
Selection criteria PICS 7.2.1/1
Test Purpose name
WWW-Authenticate header is passed unchanged
Test Purpose
When an IBCF receives a REGISTER request from the visited network it shall forward this
request to the other home network. If the IBCF receives the 401 Unauthorized final
response from the other home network the WWW-Authenticate header is unchanged in the
forwarded SIP response.
SIP Parameter values 401 1: WWW-Authenticate
401 2: WWW-Authenticate
Comments
Message flows Mx SUT Ic
REGISTER   REGISTER
401 Unauthorized 2   401 Unauthorized 1
Apply post test routine
ETSI
9 ETSI TS 101 553-2 V4.1.1 (2016-09)
TP number IBCF_101_002 Reference 5.10.2.1 3) [1]
TSS reference Exit_Point/reg
Selection criteria PICS 7.2.1/1 AND PICS 7.1.1/2
Test Purpose name The Authorization header is passed unchanged
Test Purpose
When an IBCF receives a REGISTER request from the visited network it shall forward this
request to the other home network. The Authorization header remains unchanged in the
forwarded SIP request.
SIP Parameter values REGISTER 1: Authorization
Path
Require: path
P-Charging-Vector: icid; orig-ioi
REGISTER 2: Authorization
Path
Require: path
P-Charging-Vector: icid; orig-ioi
Comments
Message flows Mx SUT Ic
REGISTER 1   REGISTER 2
200 OK REGISTER   200 OK REGISTER
Apply post test routine
TP number IBCF_101_003 Reference 5.10.2.1 3) [1]
TSS reference Exit_Point/reg
Selection criteria PICS 7.2.1/1 AND PICS 7.1.1/2
Test Purpose name The P-Associated-URI, Path, Service-Route and P-Charging-Vector headers are passed
unchanged
Test Purpose When an IBCF receives a 200 OK REGISTER request from the other (home) network it
shall forward this request to the own (visited) network. The P-Associated-URI, Path,
Service-Route, P-Charging-Vector headers remain unchanged in the forwarded SIP
response.
SIP Parameter values 200 OK 1: P-Associated-URI
Path
Service-Route
P-Charging-Vector: term-ioi
Contact
200 OK 2: P-Associated-URI
Path
Service-Route
P-Charging-Vector: term-ioi
Contact
Comments
Message flows Mx SUT Ic
REGISTER 1   REGISTER 2
200 OK REGISTER   200 OK REGISTER
Apply post test routine
ETSI
10 ETSI TS 101 553-2 V4.1.1 (2016-09)
TP number IBCF_101_004 Reference 5.10.2.1 3) [1]
TSS reference Exit_Point/reg
Selection criteria PICS 7.2.1/1
Test Purpose name The Event and Expires header are passed unchanged
Test Purpose
When an IBCF receives a SUBSCRIBE request from the visited network it shall forward
this request to the other home network. The Event header and the Expires header remain
unchanged in the request.
SIP Parameter values SUBSCRIBE 1: Event: reg
P-Charging-Vector: icid
Expires: 600 000
SUBSCRIBE 2: Event: reg
P-Charging-Vector: icid
Expires: 600 000
Comments
Message flows Mx SUT Ic
The registration procedure was successful
 
SUBSCRIBE 1 SUBSCRIBE 2
 
200 OK SUBSCRIBE 200 OK SUBSCRIBE
Apply post test routine
TP number IBCF_101_005 Reference 5.10.2.1 3) [1]
TSS reference Exit_Point/reg
Selection criteria
PICS 7.2.1/1
Test Purpose name The 'reginfo' body is passed unchanged
Test Purpose When an IBCF receives a NOTIFY request from the visited network it shall forward this
request to the other home network. The Event header and the XML body remain
unchanged in the request.
SIP Parameter values NOTIFY 1: Event: reg
Content-Type: application/reginfo+xml




duration-registered="0">
sip:[any value]



NOTIFY 2: Event: reg
Content-Type: application/reginfo+xml




duration-registered="0">
sip:[any value]



Comments
Message flows Mx SUT Ic
The registration procedure was successful
 
NOTIFY 1 NOTIFY 2
 
200 OK NOTIFY 200 OK NOTIFY
Apply post test routine
ETSI
11 ETSI TS 101 553-2 V4.1.1 (2016-09)
TP number IBCF_101_006 Reference 5.10.2.1 3) [1]
TSS reference Exit_Point/reg
Selection criteria PICS 7.2.1/1 AND PICS 7.2.1/4
Test Purpose name The IBCF selects an alternative entry point to the other network if a 3xx was received
Test Purpose
When an IBCF receives a SIP 3xx (Redirection) response from another (home) network
entry point to a previously forwarded SIP REGISTER request, it shall resend the Register
request to another entry point to which it has not previously forwarded the same request.
SIP Parameter values
Comments IUT configured with two entry points to home network
Message flows Mx SUT Ic 1 Ic 2
 
REGISTER REGISTER
 3xx
 REGISTER
200 OK REGISTER    200 OK REGISTER
Apply post test routine
TP number IBCF_101_007 Reference 5.10.2.1 3) [1]
TSS reference Exit_Point/reg
Selection criteria PICS 7.2.1/1 AND PICS 7.2.1/4
Test Purpose name
The IBCF selects an alternative entry point to the other network if a 480 was received
Test Purpose
When an IBCF receives SIP 480 (Temporarily Unavailable) response from a home network
entry point to a previously forwarded SIP REGISTER request, it shall forward the Register
request to another home network entry point to which it has not previously forwarded the
same request.
SIP Parameter values
Comments IUT configured with two entry points to home network
Message flows Mx SUT Ic 1 Ic 2
REGISTER   REGISTER

480 Temporarily
Unavailable
 REGISTER
200 OK REGISTER    200 OK REGISTER
Apply post test routine
TP number IBCF_101_008 Reference 5.10.2.1 3) [1]
TSS reference Exit_Point/reg
Selection criteria PICS 7.2.1/1 AND PICS 7.2.1/4
Test Purpose name The IBCF selects an alternative entry point to the other network if no response was
received
Test Purpose When an IBCF receives no response from a home network entry point to a previously
forwarded SIP REGISTER request, it shall forward the Register request to another home
network entry point to which it has not previously forwarded the same request.
SIP Parameter values
Comments
IUT configured with two entry points to home network
Message flows Mx SUT Ic 1 Ic 2
REGISTER   REGISTER
 REGISTER
No response
200 OK REGISTER    200 OK REGISTER
Apply post test routine
ETSI
12 ETSI TS 101 553-2 V4.1.1 (2016-09)
TP number IBCF_101_009 Reference 5.10.2.1 3) [1]
TSS reference Exit_Point/reg
Selection criteria PICS 7.2.1/1
Test Purpose name The IBCF sends a 504 if a 3xx to a REGISTER request was received
Test Purpose
If an IBCF receives a SIP 3xx (Redirection) response to a SIP REGISTER request from
all entry points in the registering user s home network, it shall send a SIP 504 (Server
Time-Out) response to the P-CSCF.
SIP Parameter values
Comments IUT configured with one entry points to home network
Message flows Mx SUT Ic

REGISTER  REGISTER
 3xx
504 Server Time-Out 
Apply post test routine
TP number IBCF_101_010 Reference 5.10.2.1 3) [1]
TSS reference Exit_Point/reg
Selection criteria PICS 7.2.1/1
Test Purpose name
The IBCF sends a 504 if a 480 to a REGISTER request was received
Test Purpose
If an IBCF receives a SIP 480 (Temporarily Unavailable) response to a SIP REGISTER
request from all entry points in the registering user s home network, it shall send a SIP
504 (Server Time-Out) response to the P-CSCF.
SIP Parameter values
Comments IUT configured with one entry points to home network
Message flows Mx SUT Ic

REGISTER  REGISTER
 480 Temporarily
Unavailable
504 Server Time-Out 
Apply post test routine
TP number IBCF_101_011 Reference 5.10.2.1 3) [1]
TSS reference Exit_Point/reg
Selection criteria PICS 7.2.1/1
Test Purpose name
The IBCF sends a 504 if no response to a REGISTER request was received
Test Purpose If an IBCF receives no response to a SIP REGISTER request from all entry points in the
registering user s home network, it shall send a SIP 504 Server Time-Out response to the
P-CSCF.
SIP Parameter values
Comments IUT configured with one entry points to home network
Message flows Mx SUT Ic
REGISTER  REGISTER

No response
504 Server Time-Out 
Apply post test routine
6.1.2 Basic call
TP number IBCF_102_001 Reference 5.10.2.2 1) [1]
TSS reference Exit_Point/bcall
Selection criteria
Test Purpose name
The SUT responds with a 100 Trying after an INVITE was received
Test Purpose
When the IBCF receives an INVITE request, the SUT responds with a 100 Trying
SIP Parameter values
Comments
Message flows Mx SUT Ic
INVITE   INVITE

100 Trying
Apply post test routine
ETSI
13 ETSI TS 101 553-2 V4.1.1 (2016-09)
TP number IBCF_102_002 Reference 5.10.2.2 2B) [1]
TSS reference Exit_Point/bcall
Selection criteria PICS 7.2.2/73
Test Purpose name The IBCF performs the Record-Route procedure
Test Purpose
When the IBCF sends an INVITE request to the other network a Record-Route header
field value is added to the request identifying the IBCF itself.
SIP Parameter values
Comments
Message flows Mx SUT Ic
INVITE   INVITE
100 Trying 
Apply post test routine
TP number IBCF_102_003 Reference 5.10.2.2, 7) [1]
TSS reference Exit_Point/bcall
Selection criteria
PICS 7.2.2/1
Test Purpose name
The P-Charging-Vector header is supported unchanged
Test Purpose When the IBCF sends an INVITE request to the other network, the P-Charging-Vector
present as received from the own network.
SIP Parameter values
INVITE1: P-Charging-Vector: icid-value; orig-ioi

INVITE2: P-Charging-Vector: icid-value; orig-ioi
Comments
Message flows Mx SUT Ic
 
INVITE1 INVITE2

100 Trying
Apply post test routine
TP number IBCF_102_004 Reference 5.10.2.2, 7) [1]
TSS reference Exit_Point/bcall
Selection criteria PICS 7.2.2/2
Test Purpose name Some values of the P-Charging-Vector are not present
Test Purpose
When the IBCF sends an INVITE request to the other network, some values of the
P-Charging-Vector are not present.
SIP Parameter values INVITE1: P-Charging-Vector: icid-value; orig-ioi

INVITE2: P-Charging-Vector header some values not present
Comments
Message flows Mx SUT Ic
INVITE1   INVITE2
100 Trying 
Apply post test routine
TP number IBCF_102_005 Reference 5.10.2.2, 7) [1]
TSS reference
Exit_Point/bcall
Selection criteria PICS 7.2.2/3
Test Purpose name The P-Charging-Vector is not present
Test Purpose When the IBCF sends an INVITE request to the other network, the P-Charging-Vector is
not present.
SIP Parameter values INVITE1: P-Charging-Vector: icid-value; orig-ioi

INVITE2:
Comments
Message flows Mx SUT Ic
 
INVITE1 INVITE2
100 Trying 
Apply post test routine
ETSI
14 ETSI TS 101 553-2 V4.1.1 (2016-09)
TP number IBCF_102_006_A Reference 5.10.2.2, 8) [1]
TSS reference Exit_Point/bcall
Selection criteria PICS 7.2.2/59
Test Purpose name P-Charging-Function-Addresses header present in INVITE request
Test Purpose
The IBCF receives an INVITE request from the own network containing an
P-Charging-Function-Addresses header, When the IBCF sends an INVITE request to the
other network, the P-Charging-Function-Addresses header is present as received from
the own network.
SIP Parameter values INVITE: P-Charging-Function-Addresses: ccf="aaa//etsi.com"
Comments
Message flows Mx SUT Ic
INVITE   INVITE
100 Trying 
Apply post test routine
TP number Reference 5.10.2.2, 8) [1]
IBCF_102_006_B
TSS reference Exit_Point/bcall
Selection criteria NOT PICS 7.2.2/59
Test Purpose name P-Charging-Function-Addresses header is not present in INVITE request
Test Purpose The IBCF receives an INVITE request from the own network containing an
P-Charging-Function-Addresses header, When the IBCF sends an INVITE request to the
other network, the P-Charging-Function-Addresses header is not present.
SIP Parameter values
INVITE2: P-Charging-Function-Addresses header is not present
Comments
Message flows Mx SUT Ic
INVITE1   INVITE2
100 Trying 
Apply post test routine
TP number Reference 5.10.2.2, 10) [1],
IBCF_102_007_A
IETF RFC 4028 [20]
TSS reference Exit_Point/bcall
Selection criteria PICS 7.2.2/59
Test Purpose name
P-Charging-Function-Addresses header is present in 200 OK
Test Purpose The IBCF receives a 200 OK INVITE response from the other network containing an
P-Charging-Function-Addresses header, When the IBCF sends a 200 OK INVITE
response to the own network, the P-Charging-Function-Addresses header is present as
received from the other network.
SIP Parameter values 200 OK: P-Charging-Function-Addresses: ccf="aaa//etsi.com"
Comments
Message flows Mx SUT Ic
INVITE   INVITE
180 Ringing   180 Ringing
200 OK   200 OK
ACK   ACK
Apply post test routine
ETSI
15 ETSI TS 101 553-2 V4.1.1 (2016-09)
TP number IBCF_102_007_B Reference 5.10.2.2, 10) [1],
IETF RFC 4028 [20]
TSS reference Exit_Point/bcall
Selection criteria NOT PICS 7.2.2/59
Test Purpose name P-Charging-Function-Addresses header is not supported in 200 OK
Test Purpose The IBCF receives a 200 OK INVITE response from the other network containing an
P-Charging-Function-Addresses header, When the IBCF sends a 200 OK INVITE
response to the own network, the P-Charging-Function-Addresses header is not present.
SIP Parameter values 200 OK1: P-Charging-Function-Addresses: ccf="aaa//etsi.com"
200 OK2:
Comments
Message flows Mx SUT Ic
INVITE   INVITE
180 Ringing   180 Ringing
200 OK2   200 OK1
ACK   ACK
Apply post test routine
TP number Reference 4.4.6 [1],
IBCF_102_008
IETF RFC 4412 [21]
TSS reference Exit_Point/bcall
Selection criteria PICS 7.2.2/22 AND PICS 5.2.2/23 NOT PICS 7.2.1/2
Test Purpose name
A Resource-Priority header field is passed to a trusted network option tag in Require
header
Test Purpose When an IBCF receives an initial SIP INVITE request from within its own network and a
Resource-Priority header field is present, it leaves the Resource-Priority header field
header fields in the SIP requests if the other network is trusted or the request is rejected
with a 420 response if not supported.
SIP Parameter values
INVITE1: Require: resource-priority
Resource-Priority: q735.0
INVITE2: Resource-Priority: q735.0
Comments
Message flows Mx SUT Ic
INVITE 

100 Trying
CASE A
 INVITE
CASE B
420 Bad Extension 
ACK 
Apply post test routine
TP number Reference 4.4.6 [1],
IBCF_102_008A
IETF RFC 4412 [21]
TSS reference Exit_Point/bcall
Selection criteria
PICS 7.2.2/22 AND PICS 7.2.2/93 AND NOT PICS 7.2.1/2
Test Purpose name A Resource-Priority header field is passed to a trusted network option tag in Supported
header
Test Purpose
When an IBCF receives an initial SIP INVITE request from its own network and a
Resource-Priority header field is present, it leaves the Resource-Priority header field
header fields in the SIP requests if the other network is trusted.
SIP Parameter values INVITE1: Supported: resource-priority
Resource-Priority: q735.0
INVITE2: Resource-Priority: q735.0
Comments
Message flows Mx SUT Ic
INVITE   INVITE
100 Trying 
Apply post test routine
ETSI
16 ETSI TS 101 553-2 V4.1.1 (2016-09)
TP number IBCF_102_009 Reference 4.4.6 [1],
IETF RFC 4412 [21]
TSS reference Exit_Point/bcall
Selection criteria PICS 7.2.1/2
Test Purpose name A Resource-Priority header field is removed from the INVITE
Test Purpose When an IBCF receives an initial SIP INVITE request from within its own network and a
Resource-Priority header field is present, it removes the Resource-Priority header field
header fields from the SIP requests if the other network is untrusted.
SIP Parameter values INVITE1: Require: resource-priority
Resource-Priority: q735.0
INVITE2:
Comments
Message flows Mx SUT Ic
 
INVITE INVITE

100 Trying
Apply post test routine
TP number IBCF_102_010 Reference 4.4.7 [1]
TSS reference Exit_Point/bcall
Selection criteria PICS 7.2.2/71
Test Purpose name A Reason header is passed in a SIP response
Test Purpose When an IBCF receives a SIP response from the other network and a Reason header
field is present as indicated in table 6.1.2-1, this header field is passed in the forwarded
response to the own network.
SIP Parameter values SIP_response 1: Reason: Q.850;cause=Response_cause
SIP_response 2: Reason: Q.850;cause=Response_cause
Comments
Message flows Mx SUT Ic
INVITE   INVITE
VA_response 2   SIP_response 1
ACK   ACK
Table 6.1.2-1: Receipt of the Reason header in response
Response_cause SIP_response
Status code
Reason header
VA_01 404 Not Found
Reason: Q.850; cause=1 (unallocated (unassigned) number)
VA_02 500 Server Internal error
Reason: Q.850; cause=2 (no route to network)
VA_03 500 Server Internal error
Reason: Q.850; cause=3 (no route to destination)
VA_04 500 Server Internal error
Reason: Q.850; cause=4 (Send special information tone)
VA_05 404 Not Found
Reason: Q.850; cause=5 (Misdialled trunk prefix)
VA_06 486 Busy Here
Reason: Q.850; cause=17 (user busy)
VA_07 480 Temporarily unavailable
Reason: Q.850; cause=18 (no user responding)
VA_08 480 Temporarily unavailable
Reason: Q.850; cause=19 (no answer from the user)
VA_09 480 Temporarily unavailable
Reason: Q.850; cause=20 (subscriber absent)
VA_10 603 Decline
Reason: Q.850; cause=21 (call rejected)
VA_11 480Temporarily unavailable
Reason: Q.850; cause=21 (call rejected)
VA_12 410 Gone
Reason: Q.850; cause=22 (number changed)
VA_13 433 Anonymity Disallowed
Reason: Q.850; cause=24 (call rejected due to ACR supplementary
service)
ETSI
17 ETSI TS 101 553-2 V4.1.1 (2016-09)
Response_cause SIP_response
Status code
Reason header
VA_14 483 Too many hops
Reason: Q.850; cause=25 (Exchange routing error)
VA_15 480 Temporarily unavailable
Reason: Q.850; cause=26 (Non-selected user clearing)
VA_16 502 Bad Gateway
Reason: Q.850; cause=27 (destination out of order)
VA_17 484 Address Incomplete
Reason: Q.850; cause=28 invalid number format (address incomplete)
VA_18 500 Server Internal error
Reason: Q.850; cause=29 (facility rejected)
VA_19 480 Temporarily unavailable
Reason: Q.850; cause=31 (normal unspecified)
VA_20 486 Busy here
Reason: Q.850; cause=34 (No circuit/channel available)
VA_21 480 Temporarily unavailable
Reason: Q.850; cause=34 (No circuit/channel available)
VA_22 500 Server Internal error
Reason: Q.850; cause=41 (Temporary failure)
VA_23 500 Server Internal error
Reason: Q.850; cause=50 (requested facility no subscribed)
VA_24 603 Decline
Reason: Q.850; cause=55 (Incoming class barred within Closed User
Group)
VA_25 403 Forbidden
Reason: Q.850; cause=57 (bearer capability not authorized)
VA_26 500 Server Internal error
Reason: Q.850; cause=58 (bearer capability not presently)
VA_27 500 Server Internal error
Reason: Q.850; cause=63 (service option not available, unspecified)
VA_28 500 Server Internal error
Reason: Q.850; cause=65 (Bearer capability not implemented)
VA_29 403 Forbidden
Reason: Q.850; cause=87 (User not member of Closed User Group)
VA_30 500 Server Internal error
Cause value No 88 (incompatible destination)
VA_31 403 Forbidden
Reason: Q.850; cause=90 (Non existing Closed User Group)
VA_32 500 Server Internal error
Reason: Q.850; cause=91 (invalid transit network selection)
VA_33 500 Server Internal error
Reason: Q.850; cause=95 (invalid message)
VA_34 501 Not Implemented
Reason: Q.850; cause=97 (Message type non-existent or not
implemented)
VA_35 501 Not Implemented
Reason: Q.850; cause=99 (information element/parameter non-existent
or not implemented))
VA_36 480 Temporarily unavailable
Reason: Q.850; cause=102 (recovery on timer expiry)
VA_37 501 Not Implemented
Reason: Q.850; cause=110 (Message with unrecognized Parameter,
discarded)
VA_38 500 Server Internal error
Reason: Q.850; cause=111 (protocol error, unspecified)
VA_39 500 Server Internal error
Reason: Q.850; cause=127 (interworking unspecified)

ETSI
18 ETSI TS 101 553-2 V4.1.1 (2016-09)
TP number IBCF_102_011 Reference 4.4.8 [1]
TSS reference Exit_Point/bcall
Selection criteria NOT PICS 7.2.1/2 AND NOT PICS 7.2.2/4
Test Purpose name The P-Profile-Key header is forwarded to the trusted network
Test Purpose
When an IBCF receives an initial SIP INVITE request from its own network and a
P-Profile-Key header field is present, it leaves the P-Profile-Key header field header fields
in the SIP requests if the other network is trusted.
SIP Parameter values INVITE1: P-Profile-Key:
INVITE2: P-Profile-Key:
Comments
Message flows Mx SUT Ic
INVITE1   INVITE2
100 Trying 
Apply post test routine
TP number Reference 4.4.8 [1]
IBCF_102_012
TSS reference Exit_Point/bcall
Selection criteria NOT PICS 7.2.1/2 AND NOT PICS 7.2.2/4
Test Purpose name The P-Profile-Key header is not forwarded to the trusted network
Test Purpose When an IBCF receives an initial SIP INVITE request from its own network and a
P-Profile-Key header field is present, it removes the P-Profile-Key header field header
fields from the SIP requests if the other network is trusted.
SIP Parameter values INVITE1: P-Profile-Key:
INVITE2:
Comments
Message flows Mx SUT Ic
 
INVITE1 INVITE2
100 Trying 
Apply post test routine
TP number IBCF_102_013 Reference 4.4.8 [1]
TSS reference Exit_Point/bcall
Selection criteria PICS 7.2.1/2
Test Purpose name
The P-Profile-Key header is not forwarded to the untrusted network
Test Purpose When an IBCF receives an initial SIP INVITE request from within its own network and a
P-Profile-Key header field is present, it removes the P-Profile-Key header field header
fields from the SIP requests if the other network is untrusted.
SIP Parameter values INVITE1: P-Profile-Key:
INVITE2:
Comments
Message flows Mx SUT Ic
INVITE1   INVITE2

100 Trying
Apply post test routine
TP number IBCF_102_014 Reference 4.4.9 [1]
TSS reference Exit_Point/bcall
Selection criteria NOT PICS 7.2.1/2 AND NOT PICS 7.2.2/5
Test Purpose name The P-Served-User header is forwarded to the trusted network
Test Purpose When an IBCF receives an initial SIP INVITE request from its own network and a
...