Links

GitHub

Open HUB

Quick Links

Download

STREAMS

SIGTRAN

SS7

Hardware

SCTP

Related

Package

Manual

Status

FAQ

ISUP

ETSI ISUP PICS

SS7 Stack

ISUP

BSSAP

TCAP

SCCP

MTP Level 3

SS7 Stack Manager

Conformance

Applications

SS7 Stack

ISDN Stack

SIGTRAN Stack

VoIP Stack

MG Stack

SS7/ISDN Devices

IP Transport

Embedded Systems

Operating System

Documentation

FAQ

SIGTRAN

Design

Conformance

Performance

References

Man Pages

Manuals

Papers

Home

Overview

Status

Documentation

Resources

About

News

ETSI ETS 300 356-31 Annex A

Description: OpenSS7 SS7 ISUP PICS Proforma.

Annex A (normative): PICS proforma

Notwithstanding the provisions of the copyright clause related to the text of this ETS, ETSI grands that users of this ETS may freely reproduce the PICS proforma in this annex so that it can be used for its intended purposes and may further publish the completed PICS.


A.1  Instructions for completing the PICS proforma

The supplier of the implementation shall complete the PICS profroma in each of the spaces provided. If necessar the supplier may provide additional comments separately.

More detailed instructions are given at the beginning of the different subclauses of the PICS proforma.

A.1.1  Purpose and structure

The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in ISDN User Part (ISUP) '97 reference specification [1] may provide information about the implementation in a standardized manner.

The PICS proforma is subdivided into subclauses for the following categories of information:

  • instructions for completing the PICS proforma;
  • identification of the implementation;
  • identification of the protocol specification;
  • POCS proforma tables (containing the global statement of conformance).

A.1.2  Abbreviations and conventions

The PICS proforma contained in this annex is comprised of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [14].

Item column

It contains a number which identifies the item in the table.

Item description column

It describes each respective item (e.g., parameters, timers, etc.)

Reference column

It gives reference to ISUP '97 specification [1], except where explicitly stated otherwise.

Status column

The following notations, defined in ISO/IEC 9646-7 [14], are used for the status column:

m mandatory - the capability is required to be supported
n/a not applicable - in the given context, it is impossible to use the capability
o optional - the capability may be supported or not
o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies a unique group of related optional items and the logic of their selection which is defined immediately following the table
ci conditional - the requirement on the capability ("m", "o" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying an unique conditional status expression which is defined immediately following the table
Support column

The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [4], are used for the support column:

Y or y supported by the implementation
N or n not supported by the implementation
N/A, n/a or - no answer required (allowed only if the status is n/a, directly or after evaluation of a conditional status)
NOTE:

Support of a capbility means that the capability is implemented in conformance to the ISUP '97 specification [1].

Values allowed column

This column contains the values or the ranges of values allowed.

Values supported column

The values supported column shall be filed in by the supplier of the implementation. In this column, the values or the ranges of values supported by the implementation shall be indicated.

Reference to items

For each possible item answer (answer in the support column) within the PICS proforma a unique reference exists, used, for example, in the conditional expressions. It is defined as the table identifier, followed by a solidus character "/", followed by the item number in the table. If there is more than one support column in a table, the columns are discriminated by letters (a, b, etc.), respectively.

EXAMPLE 1:

A.5/4 is the reference to the answer of item 4 in table 5 of annex A.

EXAMPLE 2:

A.6/3b is the reference to the second answer (i.e. in the second support column) of item 3 in table 6 of annex A.


A.2  Identification of the Implementation

Identification of the Implementation Under Test (IUT) and the system in which it resides - the System Under Test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options.

The product supplier information and client information should both be filled in if they are different.

A person who can answer queries regarding information supplied in the ICS should be named as the contact person.

A.2.1  Date of the statement

Date of the statement:   September 1, 2002

A.2.2  Implementation Under Test (IUT) identification

IUT name:   OpenSS7 Stack
IUT version:   0.8.6 Release

A.2.3  System Under Test (SUT) identification

SUT name:   PC
Hardware configuration:   E400P-SS7
Operating system:   Linux 2.4.18

A.2.4  Product supplier

Name:   OpenSS7 Corporation
Address:   1469 Jeffreys Crescent, Edmonton AB, Canada T6L 6T1
Telephone number:   +1-780-490-1141
Facsimile number:   +1-780-490-1241
E-mail address:   info@openss7.com
Additional information:  

A.2.5  Client

Name:   Intermedia AG
Address:  
Telephone number:  
Facsimile number:  
E-mail address:  
Additional information:  

A.2.6  ICS contact person

Name:   Brian Bidulock
Address:   1469 Jeffreys Crescent, Edmonton AB, Canada T6L 6T1
Telephone number:   +1-780-490-1141
Facsimile number:   +1-780-490-1241
E-mail address:   biduock@openss7.org
Additional information:  

A.3  Identification of the reference specification

This PICS proforma applies to the following standard:

ETSI EN 300 356-1 (V3.2): "Intergrated Services Digital Network (ISDN); Signalling System No. 7; ISDN User Part (ISUP); ISDN User Part (ISUP) version 3 for the international interface; Part 1: Basic services [ITU-T Recommendation Q.761 to Q.764 (1997) modified]".


A.4  PICS proforma tables

A.4.1  Global statement of conformance

  (Yes/No)
Are all mandatory capabilities implemented? Yes
NOTE:

Answering "No" to this question indicates non-conformance to the protocol specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming.

All references are to ITU-T Recommendation Q.764 [8], unless explicitly stated otherwise.

A.4.2  Roles

Table A.1: Roles
Item Is the implementation an ... Reference Status Support
1 OLE - Originating local exchange 2.1.1.1 o.1 Y
2 NTE - National transit exchange 2.1.1.2 o.1 N
3 OutIE - Outgoing international exchange 2.1.1.3 o.1 N
4 IncIE - Incoming international exchange 2.1.1.4 o.1 N
5 ITE - International transit exchange 2.1.1.5 o.1 N
6 DLE - Destination local exchange 2.1.1.6 o.1 Y
o.1:   It is mandatory to support at least one of these items

Comments:

Intermediate exchange operation may be supported at a later date.

A.4.3  Capabilities

The following matrix is an abbreviation guide for roles:

OLE NTE OutIE ITE IncIE DLE
TypeA TypeB TypeA TypeB TypeA TypeA
Local Transit Gateway Transit Gateway Local
  IntermE IntermE IntermE IntermE  
CntrlE CntrlE CntrlE      
  IWorkE IWorkE IWorkE IWorkE  

 

Table A.2: Connection types
Item Is the exchange able to ... Reference Status Support
1 support the connection type "Speech"? 2.1.1.1
.1.2.1
o.2 Y
2 support the connection type "3,1 kHz audio"? 2.1.1.1
.1.2.1
o.2 N
3 support the connection type "64 kbit/s unrestricted"? 2.1.1.1
.1.2.1
o.2 Y
4 support the connection type "64 kbit/s unrestricted preferred"? 2.1.1.1
.1.2.1
o Y
5 support multirate connection types? 2.1.1.1
.1.2.1
o N
6 support the connection type "2 x 64 kbit/s unrestrictred"? 2.1.1.1
.1.2.1
o N
7 support the connection type "384 kbit/s unrestricted"? 2.1.1.1
.1.2.1
o N
8 support the connection type "1,536 kbit/s unrestricted"? 2.1.1.1
.1.2.1
o N
9 support the connection type "1,920 kbit/s unrestricted"? 2.1.1.1
.1.2.1
o N
10 support the connection type "N x 64 kbit/s unrestricted"? 2.1.13 o N
o.2:   It is mandatory to support at least one of these items.

Comments:

Table A.3: Forward address signalling
Item Is the exchange [role] able to ... Reference Status Support
1 [OLE] use the en bloc operation in the forward address signalling (sending)? 2.1.1.1 o.3 Y
2 [OLE] use the overlap operation in the forward address signalling (sending)? 2.1.2.1 o.3 Y
3 [IntermE] use the en bloc operation in the forward address signalling (receiving)? 2.1.1.2-5 m  
4 [IntermE] use the overlap operation in the forward address signalling (receiving)? 2.1.2.2-5 m  
5 [IntermE] use the en bloc operation in the forward address signalling (sending)? 2.1.1.2-5 o.4  
6 [IntermE] use the overlap operation in the forward address signalling (sending)? 2.1.2.2-5 o.4  
7 [DLE] use the en bloc operation in the forward address signalling (receiving)? 2.1.1.6 m Y
8 [DLE] use the overlap operation in the forward address signalling (receiving)? 2.1.2.6 m Y
o.2:   It is mandatory to support at least one of these items.
o.4:   It is mandatory to support at least one of these items.

Comments:

Table A.4: OLE capabilities
Item Is the exchange able to ... Reference Status Support
1 send the end-of-pulsing signal (ST)? 2.1.1.1 b)
.1.2.1 b)
o Y
2 through-connect the transmission path also in the forward direction immediately after sending IAM for "Speech" or "3.1 kHz audio" calls? 2.1.1.1 d)
.1.2.1 d)
o Y
3 through-connect in the backward direction immediately after IAM in case of overlap signalling? 2.1.2.1 d) i) o.5 Y
4 through-connect in the backward direction when Called party number complete (digit analysis, timer T10, receive of ACM) in case of overlap signalling? 2.1.2.1 d) ii) o.5 Y
5 handle (generate and route according to) the Transit network selection received from the access? 2.1.11 o N
o.5:   It is mandatory to support at least one of these items.

Comments:

Table A.5: NTE capabilities
Item Is the exchange able to ... Reference Status Support
1 route calls using only the connection type in the Transmission medium requirement? 2.1.1.2 a)
.1.2.2 a)
o.6  
2 route calls using not only the connection type in the Transmission medium requirement? 2.1.1.2 a)
.1.2.2 a)
o.6  
3 route calls by examining the Bearer capability in the User service information and/or the High layer capability in the User teleserice information? 2.1.1.2 a)
.1.2.2 a)
c51  
4 support awaiting answer timer T9 if it is a controlling exchange (CntrlE)? 2.1.4.2 o  
o.6:   It is mandatory to support at least one of these items.
c51:   IF A.5/2 THEN o ELSE n/a.

Comments:

The NTE role is not supported at this time.

Table A.6: OutIE capabilities
Item Is the exchange able to ... Reference Status Support
1 route calls using only the connection type in the Transmission mediium requirement? 2.1.1.2 a)
.1.2.3 a)
o.7  
2 route calls using not only the connection type in the Transmission medium requirement? 2.1.1.2 a)
.1.2.3 a)
o.7  
3 route calls by examining the Bearer capability in the User service information and/or the High layer capability in the User teleservice information? 2.1.1.2 a)
.1.2.3 a)
c61  
4 ammend or omit the most significant digits in the called party number (country code)? 2.1.1.3 b) o  
5 send the end-of-pusling signal (ST)? 2.1.1.2 b)
.1.2.3 b)
o  
6 support u-law to A-law conversion? 2.1.1.2 b)
.1.2.3 b)
n/a  
o.7:   It is mandatory to support at least one of these items.
c61:   IF A.6/2 THEN o ELSE n/a.

Comments:

The OutIE role is not supported at this time.

Table A.7: ITE capabilities
Item Is the exchange able to ... Reference Status Support
1 ammend or omit the most significant digits in the called party number (country code)? 2.1.1.4 b) o  

Comments:

The ITE role is not supported at this time.

Table A.8: IncIE capabilities
Item Is the exchange able to ... Reference Status Support
1 support A-law to u-law convestion? 2.1.1.5 b)
.1.2.5 b)
n/a  

Comments:

The IncIE role is not supported at this time.

Table A.9: DLE capabilities
Item Is the exchange able to ... Reference Status Support
1 send a network initiated Suspend on receipt of an on-hook condition? 2.4.1 o Y
2 send a network initiated Resume on receipt of an off-hook condition? 2.4.2 c91 Y
c91:   IF A.9/1 THEN m ELSE n/a

Comments:

Table A.10: IntermE capabilities
Item Is the exchange able to ... Reference Status Support
1 route accodring to the Transit network selection? 2.1.11 o  
2 generate Call history information if it is missing? 2.6.1.5 c101  
c101:   IF A.13/11 THEN o ELSE n/a.

Comments:

The IntermE role is not supported at this time.

Table A.11: IworkE capabilities
Item Is the exchange able to ... Reference Status Support
1 send a network initiated Suspend on receipt of a clear back signal? 2.4.1 o  
2 send a network initiated Resume on receipt of a re-answer indication? 2.4.2 c111  
c111:   IF A.11/1 THEN m ELSE n/a.

Comments:

The IworkE role is not supported at this time.

Table A.12: Gateway capabilities
Item Is the exchange able to ... Reference Status Support
1 perform policing of information for re-segmentation? 2.1.12 d) o  
2 re-segment without discarding unrecognized parameters that have to be passed on according to the compatibility procedure? 2.1.12 h) o  

Comments:

The Gateway role is not supported at this time.

Table A.12a: Role independent capabilities
Item Is the exchange able to ... Reference Status Support
1 support calls to testing and measuring devices (sending)? 2.1.1.8
.1.2.8
o Y
2 support calls to testing and measuring devices (receiving)? 2.1.1.8
.1.2.8
o Y
3 support the Continuity check procedures? 2.1.8 o Y
4 use Continuity-check request message to test for proper CIC-alignment? 2.1.8
nnex G.3 b)
o Y
5 do continuity checking for multirate type calls? 2.1.8 o (note 1)
6 support FOT? 2.1.10 o N
7 support the Simple segmentation procedure? 2.1.12 o Y
8 support in-band tones and announcements? 2.2.4 m Y
9 support Cause in the ACM and CPG? 2.2.4 m Y
10 support signalling procedure for connection type allowing fallback? 2.5 o N
11 support the propagation delay determination procedures? 2.6 c121 Y
12 support the simple (Q.767) echo control procedures? Q.767/D.2.8 o.8 Y
13 support the dynamic echo control procedures? 2.7 o.8 Y
14 handle circuits on more than one PCM-system in one CGB/CGBA and CGU/CGUA? 2.8 o Y
15 support method 1 as preventive action of dual seizure? 2.9.1.3 o.9 Y
16 support method 2 as preventive action of dual seizure? 2.9.1.3 o.9 Y
17 support a proprietary method as preventative action of dual seizure? 2.9.1.3 o.9 N
18 handle circuits on more than one PCM-system in one GRS/GRA? 2.9.3 o Y
19 support the compatibility procedure? 2.9.5 m Y
20 discard an unknown parameter without Parameter compatibility information? 2.9.5.3.2 i) b)
.9.5.3.2 ii) b)
o.10 N
21 pass on an unknown parameter without Parameter compatibility information? 2.9.5.3.2 i) b)
.9.5.3.2 ii) b)
o.10 Y
22 support of ISDN User Part signalling congestion control? 2.10 o Y
23 support of automatic congestion control? 2.11 o Y
24 support the ISDN User Part availability control? 2.13 o Y
25 support interaction with MTP Pause and Resume? 2.14 m Y
26 support of temporary alternative routing (TAR) 2.16 o Y
27 support of hop counter procedure 2.17 o Y
28 support of call collect request procedure 2.18 o N
o.8:   It is mandatory to support at least one of these items.
o.9:   It is mandatory to support at least one of these items.
o.10:   It is mandatory to support at least one of these items.

Comments:

Note 1:
The implementation does not support multirate type calls, so item A.12a/5 is not applicable.
Table A.13: Timers
Item User of ... Reference Status Support Values in seconds
allowed supported
1T1Table A.1/Q.764mY15 - 6015 - 60
2T2Table A.1/Q.764mY180180
3T3Table A.1/Q.764oY120120
4T4Table A.1/Q.764oY300 - 900300 - 900
5T5Table A.1/Q.764mY300 - 900300 - 900
6T6Table A.1/Q.764
.3.2/Q.118
mY60 - 12060 - 120
7T7Table A.1/Q.764mY20 - 3020 - 30
8T8Table A.1/Q.764mY10 - 1510 - 15
9T9Table A.1/Q.764
.3.2/Q.118
mY90 - 12090 - 120
10T10Table A.1/Q.764mY4 - 64 - 6
11T11Table A.1/Q.764mY15 - 2015 - 20
12T12Table A.1/Q.764mY15 - 6015 - 60
13T13Table A.1/Q.764mY300 - 900300 - 900
14T14Table A.1/Q.764mY15 - 6015 - 60
15T15Table A.1/Q.764mY300 - 900300 - 900
16T16Table A.1/Q.764mY15 - 6015 - 60
17T17Table A.1/Q.764mY300 - 900300 - 900
18T18Table A.1/Q.764mY15 - 6015 - 60
19T19Table A.1/Q.764mY300 - 900300 - 900
20T20Table A.1/Q.764mY15 - 6015 - 60
21T21Table A.1/Q.764mY300 - 900300 - 900
22T22Table A.1/Q.764mY15 - 6015 - 60
23T23Table A.1/Q.764mY300 - 900300 - 900
24T24Table A.1/Q.764mY0 - 20.010 - 2 (note 1)
25T25Table A.1/Q.764mY1 - 101 - 10
26T26Table A.1/Q.764mY60 - 18060 - 180
27T27Table A.1/Q.764mY240240
28T28Table A.1/Q.764oY1010
29T29Table A.1/Q.764oY0.3 - 0.60.3 - 0.6
30T30Table A.1/Q.764oY5 - 105 - 10
31T31Table A.1/Q.764oY>360360.010 - (note 2)
32T32Table A.1/Q.764oY3 - 53 - 5
33T33Table A.1/Q.764oY12 - 1512 - 15
34T34Table A.1/Q.764c131Y2 - 42 - 4
35T35Table A.1/Q.764mY15 - 2015 - 20
36T36Table A.1/Q.764mY10 - 1510 - 15
37T37Table A.1/Q.764c132Y2 - 42 - 4
38T38Table A.1/Q.764
.3.2/Q.118
mY60 - 12060 - 120
39T39Table A.1/Q.764
.9/Q.731.7
oY4 - 154 - 15
c131:   IF A.13/7 THEN m ELSE o.
c132:   IF A.13/13 THEN m ELSE o.

Comments:

Note 1:
The minimum allowed setting for a timer is 0.010 seconds.
Note 2:
The maximum allowed setting for a timer is 2147483 seconds.

Timers are only accurate to a granularity of 10 milliseconds. Timer response may be delayed up to 100 milliseconds.

Last modified: Sun, 05 Mar 2006 08:34:15 GMT  
Copyright © 2014 OpenSS7 Corporation All Rights Reserved.