Dialogic SS7 Call Flow

Dialogic Global Call SS7
Technology Guide
November 2008
05-2274-006
Copyright and Legal Notice

Copyright 2000-2008, Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission in
writing from Dialogic Corporation at the address provided below.
All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a commitment on
the part of Dialogic Corporation or its subsidiaries (Dialogic). Reasonable effort is made to ensure the accuracy of the information contained in the
document. However, Dialogic does not warrant the accuracy of this information and cannot accept responsibility for errors, inaccuracies or omissions
that may be contained in this document.
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY
ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A
SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY
EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES
RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY
RIGHT OF A THIRD PARTY.
Dialogic products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications.
Due to differing national regulations and approval requirements, certain Dialogic products may be suitable for use only in specific countries, and thus
may not function properly in other countries. You are responsible for ensuring that your use of such products occurs only in the countries where such
use is suitable. For information on specific products, contact Dialogic Corporation at the address indicated below or on the web at www.dialogic.com.
It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this document, in marketing collateral
produced by or on web pages maintained by Dialogic may infringe one or more patents or other intellectual property rights owned by third parties.
Dialogic does not provide any intellectual property licenses with the sale of Dialogic products other than a license to use such product in accordance
with intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a signed agreement with
Dialogic. More detailed information about such intellectual property is available from Dialogics legal department at 9800 Cavendish Blvd., 5th Floor,
Montreal, Quebec, Canada H4M 2V9. Dialogic encourages all users of its products to procure all necessary intellectual property licenses
required to implement any concepts or applications and does not condone or encourage any intellectual property infringement and
disclaims any responsibility related thereto. These intellectual property licenses may differ from country to country and it is the
responsibility of those who develop the concepts or applications to be aware of and comply with different national license requirements.
Dialogic, Dialogic Pro, Brooktrout, Cantata, SnowShore, Eicon, Eicon Networks, Eiconcard, Diva, SIPcontrol, Diva ISDN, TruFax, Realblocs,
Realcomm 100, NetAccess, Instant ISDN, TRXStream, Exnet, Exnet Connect, EXS, ExchangePlus VSE, Switchkit, N20, Powering The ServiceReady Network, Vantage, Making Innovation Thrive, Connecting People to Information, Connecting to Growth and Shiva, among others as well as
related logos, are either registered trademarks or trademarks of Dialogic Corporation or its subsidiaries. Dialogic's trademarks may be used publicly
only with permission from Dialogic. Such permission may only be granted by Dialogics legal department at 9800 Cavendish Blvd., 5th Floor, Montreal,
Quebec, Canada H4M 2V9. Any authorized use of Dialogic's trademarks will be subject to full respect of the trademark guidelines published by
Dialogic from time to time and any use of Dialogics trademarks requires proper acknowledgement.
Windows is a registered trademark of Microsoft Corporation in the United States and/or other countries. Other names of actual companies and
product mentioned herein are the trademarks of their respective owners.
This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible for your decision to use open
source in connection with Dialogic products (including without limitation those referred to herein), nor is Dialogic responsible for any present or future
effects such usage might have, including without limitation effects on your products, your business, or your intellectual property rights.
Publication Date: November 2008
Document Number: 05-2274-006
Dialogic Global Call SS7 Technology Guide November 2008
Contents
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1
SS7 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.1
1.2
17
19
20
20
Dialogic Global Call Architecture for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

2.1
2.2
2.3
2.4
2.5
3
SS7 and Computer Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SS7 Protocol Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Lower Stack Layers for SS7 over a Circuit-Switched Network . . . . . . . . . . . . . . .
1.2.2 Upper Stack Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Dialogic Global Call Software with SS7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.1 Dialogic SS7 Interface Boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.2 Dialogic Signal Interface Unit (SIU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1.3 SS7 Protocol Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Architecture Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dialogic SS7 Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dialogic Global Call SS7 Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SS7 Protocol Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
24
28
31
32
34
34
35
Configuration and Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
3.10
SS7 System Environment Configuration (system.txt) . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SS7 Protocol Stack Configuration (config.txt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.1 Trunk Name Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.2 TDM Bus Configuration of Dialogic SS7 Boards . . . . . . . . . . . . . . . . . . . . . . . .
3.2.3 MTP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.4 ISUP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.5 TUP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2.6 BICC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dialogic Global Call SS7 Software Configuration (gcss7.cfg) . . . . . . . . . . . . . . . . . . . . .
3.3.1 System Configuration Type Parameter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2 Dialogic Global Call SS7 Call Control Library Parameters . . . . . . . . . . . . . . . . .
3.3.3 SS7 Service/Daemon Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.4 Dialogic SS7 Board Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.5 SIU Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.6 Dual-Resilient SIU Configuration Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.7 config.txt Related Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Viewing Parameter Values with the Dialogic Configuration Manager . . . . . . . . . . . . . . .
3.4.1 SS7 Board Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2 SIU Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring a Dialogic SS7 Board as a TDM Bus Master . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Dialogic Boards for SIGTRAN Signaling Support. . . . . . . . . . . . . . . . . . . . .
Configuring Dialogic SS7 Boards for Clear Channel Mode . . . . . . . . . . . . . . . . . . . . . . .
Starting a Dialogic SS7 Board System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Starting an SIU-Based System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dialogic Corporation
37
39
39
40
40
41
43
43
44
44
44
44
45
46
47
48
49
49
49
50
52
53
54
55
55
Contents
3.11
SS7 Call Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

4.1
4.2
4.3
4.4
4.5
4.6
3.10.1 Proving the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

3.10.2 Common Problems and Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Sample Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.11.1 Sample gcss7.cfg Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.11.2 Sample system.txt File for a System with a Dialogic SS7SPCI4 Board . . . . . . . 64
3.11.3 Sample config.txt File for a System with Circuits and Signaling on a Dialogic
SS7SPCI4 Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.11.4 Sample config.txt File for a System with Circuits and Signaling on DTI Trunks . . 66
3.11.5 Sample system.txt File for a System with a Dialogic SS7HDP Board . . . . . . . . . 67
3.11.6 Sample config.txt File for a System with Dialogic SS7HDP Board for Circuits and
Signaling on DTI Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
3.11.7 Sample system.txt File for a Single-SIU and Dual-SIU System. . . . . . . . . . . . . . . 69
3.11.8 Sample config.txt File for a Single-SIU System with One Host . . . . . . . . . . . . . . . 70
3.11.9 Sample config.txt File for a Single-SIU System with Two Hosts . . . . . . . . . . . . . . 71
3.11.10 Sample config.txt File for SIU A in a Dual-Resilient SIU System with a Single Host.
72
3.11.11 Sample config.txt File for SIU B in a Dual-Resilient SIU System with a Single Host.
73
3.11.12 Sample system.txt File for M3UA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3.11.13 Sample config.txt File for M3UA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.11.14 Sample system.txt File for M2PA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.11.15 Sample config.txt File for M2PA Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3.11.16 Sample system.txt File for Clear Channel Operation. . . . . . . . . . . . . . . . . . . . . . . 77
3.11.17 Sample config.txt File for Clear Channel Operation . . . . . . . . . . . . . . . . . . . . . . . 78
3.11.18 Sample system.txt File for a Mixed Configuration (SS7 Signaling and Clear Channel)
78
3.11.19 Sample config.txt File for a Mixed Configuration (SS7 Signaling and Clear Channel)
80
3.11.20 Sample system.txt File for a Mixed Configuration (Call Control and Transaction
Based) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
3.11.21 Sample config.txt File for a Mixed Configuration (Call Control and Transaction
Based) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
3.11.22 Sample system.txt File for Multiple Dialogic SS7 Boards in a System . . . . . . . . 83
3.11.23 Sample config.txt File for Multiple Dialogic SS7 Boards in a System . . . . . . . . . 84
Scenario Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Opening a Device Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Application-Initiated Outbound Call Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.3.1 Common Outbound Call Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.3.2 ITU-T Alternative Outbound Call Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
4.3.3 Outbound Call Where ACM Has No Indication Scenario. . . . . . . . . . . . . . . . . . . . 89
Network-Initiated Inbound Call Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.4.1 Common Inbound Call Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
4.4.2 Alternative Inbound Call Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Disconnect Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.5.1 Application-Initiated Disconnect Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4.5.2 Network-Initiated Disconnect Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.5.3 Server-Initiated Disconnect with Application Informed Scenario . . . . . . . . . . . . . . 91
4.5.4 Server-Initiated Disconnect with Application Not Informed Scenario. . . . . . . . . . . 92
Call Collision Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Contents
4.7
SS7-Specific Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
105
106
106
107
109
111
111
111
112
112
113
113
114
115
115
116
118
119
119
121
121
Header Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Required Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Required System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Debugging Dialogic Global Call SS7 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

7.1
7.2
Handling of Glare Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Controlling Priority in Circuit Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dynamically Adding and Deleting SS7 Circuit Groups . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.1 Adding a Circuit Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.3.2 Deleting a Circuit Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCbus or CT Bus Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.1 Routing Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4.2 Time Slot Assignment for Dialogic SS7 Boards . . . . . . . . . . . . . . . . . . . . . . . .
5.4.3 Using Time Slot 16 on Dialogic E1 Network Interface Boards . . . . . . . . . . . . .
Connecting Multiple Hosts to SIUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Dual Resilient SIU Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Overlap Send and Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Suspending and Resuming Calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performing Continuity Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.9.1 Inbound Continuity Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.9.2 Outbound Continuity Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Sending and Receiving ISUP/TUP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Handling Layer 1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.11.1 GCAMS Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.11.2 Supported Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.11.3 SS7-Specific Event Cause Codes for Layer 1 Alarms . . . . . . . . . . . . . . . . . . . .
Building Dialogic Global Call SS7 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

6.1
6.2
6.3
4.6.1 Glare Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

4.6.2 Inbound Call Received before Call Clearing Completion Scenario. . . . . . . . . . . . 93
4.6.3 SRL Queue-Related Call Collision Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.6.4 MQ Queue-Related Call Collision Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.6.5 GCT Queue-Related Call Collision with Application Informed Scenario. . . . . . . . 95
4.6.6 GCT Queue-Related Call Collision with Application Not Informed Scenario . . . . 95
Continuity Testing Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.7.1 Successful Outbound Out-of-Call Continuity Test Scenario . . . . . . . . . . . . . . . . . 96
4.7.2 Successful Inbound Out-of-Call Continuity Test Scenario . . . . . . . . . . . . . . . . . . 97
4.7.3 Outbound Out-of-Call Continuity Test with One Failure Scenario . . . . . . . . . . . . 97
4.7.4 Inbound Out-of-Call Continuity Test with One Failure Scenario . . . . . . . . . . . . . . 98
4.7.5 Successful Outbound In-Call Continuity Test Scenario . . . . . . . . . . . . . . . . . . . . 99
4.7.6 Successful Inbound In-Call Continuity Test Scenario . . . . . . . . . . . . . . . . . . . . . 100
4.7.7 Outbound In-Call Continuity Test with One Failure Scenario (Old Method) . . . . 100
4.7.8 Outbound In-Call Continuity Test with One Failure Scenario (New Method) . . . 101
4.7.9 Inbound In-Call Continuity Test with One Failure Scenario . . . . . . . . . . . . . . . . 102
SS7 Call Control Library Trace File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

SS7 Server Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
SS7-Specific Function Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

8.1
Dialogic Global Call Functions Supported by SS7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Contents
8.2
Dialogic Global Call Function Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

8.2.1 gc_AcceptCall( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
8.2.2 gc_AnswerCall( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
8.2.3 gc_CallAck( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
8.2.4 gc_DropCall( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
8.2.5 gc_ErrorValue( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
8.2.6 gc_Extension( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
8.2.7 gc_GetCallInfo( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
8.2.8 gc_GetDNIS( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
8.2.9 gc_GetNetworkH( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
8.2.10 gc_GetParm( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
8.2.11 gc_GetSigInfo( ) Variances for SS7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
8.2.12 gc_HoldCall( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
8.2.13 gc_MakeCall( ) Variances for SS7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
8.2.14 gc_OpenEx( ) Variances for SS7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
8.2.15 gc_ResetLineDev( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
8.2.16 gc_ResultValue( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
8.2.17 gc_RetrieveCall( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
8.2.18 gc_SetBilling( ) Variances for SS7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
8.2.19 gc_SetChanState( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
8.2.20 gc_SetConfigData( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
8.2.21 gc_SetInfoElem( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
8.2.22 gc_SetParm( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
8.2.23 gc_SndMsg( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
8.2.24 gc_StartTrace( ) Variances for SS7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
8.2.25 gc_StopTrace( ) Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
SS7-Specific Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

GCSS7_ISUP_CFG_CCTGRP configures an ISUP circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
GCSS7_TRUNK_CFG configures a trunk device in a circuit group . . . . . . . . . . . . . . . . . . . . . 150
S7_IE describes an ISUP message parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
S7_IE_BLK contains ISUP message parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
S7_MAKECALL_BLK holds SS7-specific parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
S7_SIGINFO_BLK contains ISUP message information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
10
SS7-Specific Error Codes and Event Cause Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

10.1
10.2
11
SS7-Specific Error Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

SS7-Specific Event Cause Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Supplementary Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

Contents
Figures
1
2
3
4
5
6
7
8
9
10
11
12
Signaling and Information Transfer Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

SS7 Protocol Stack Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dialogic SS7 Board Example Configuration 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
TDM-to-IP Gateway Using Dialogic SS7 and HMP DNI Boards . . . . . . . . . . . . . . . . . . . . . . .
SIU Example Configuration 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dialogic Global Call Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dialogic Global Call SS7 Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dialogic Global Call SS7 SIGTRAN Configuration Using Dialogic HMP DNI Boards . . . . . .

18
19
25
26
27
27
29
30
31
32
33
52
Contents
Tables
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Dialogic SS7 Board Example Configurations - Features and Benefits. . . . . . . . . . . . . . . . . . . 25

Capacity of Dialogic SIUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
SIU Example Configurations - Features and Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
CT Bus Clock Configuration for Dialogic SS7 PCI and CompactPCI Boards. . . . . . . . . . . . . . 40
Error Codes for SS7 Server Start Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Opening a Device Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Common Outbound Call Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Alternative Outbound Call Scenario for ITU-T Operation Only . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Outbound Call Where ACM Has No Indication Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Common Inbound Call Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Alternative Inbound Call Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Application-Initiated Disconnect Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Network-Initiated Disconnect Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Server-Initiated Disconnect with Application Informed Scenario . . . . . . . . . . . . . . . . . . . . . . . . 92
Server-Initiated Disconnect with Application Not Informed Scenario . . . . . . . . . . . . . . . . . . . . . 92
Glare Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Inbound Call before Completion of Call Clearing Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Disconnect Collision on SRL Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Disconnect Collision on MQ Queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Disconnect Collision on GCT Queue with Application Informed. . . . . . . . . . . . . . . . . . . . . . . . . 95
Disconnect Collision on GCT Queue with Application Not Informed . . . . . . . . . . . . . . . . . . . . . 96
Successful Outbound Out-of-Call Continuity Test Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Successful Inbound Out-of-Call Continuity Test Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Outbound Out-of-Call Continuity Test with One Failure Scenario . . . . . . . . . . . . . . . . . . . . . . . 98
Inbound Out-of-Call Continuity Test with One Failure Scenario . . . . . . . . . . . . . . . . . . . . . . . . . 98
Successful Outbound In-Call Continuity Test Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Successful Inbound In-Call Continuity Test Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Outbound In-Call Continuity Test with One Failure Scenario (Old Method) . . . . . . . . . . . . . . . 101
Outbound In-Call Continuity Test with One Failure Scenario (New Method) . . . . . . . . . . . . . . 102
Inbound In-Call Continuity Test with One Failure Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Revision History
This revision history summarizes the changes made in each published version of this document.
Document No.
Publication Date
Description of Revisions
05-2274-006
November 2008
Configuration and Startup chapter : In the Dialogic Global Call SS7 Software
Configuration (gcss7.cfg) section, added a new parameter, SIU.FTP_Type,
under SIU Configuration Parameters.
SS7-Specific Operations chapter : Under Using Dual Resilient SIU Configurations,
corrected the information about what happens when circuit groups are restored
to their preferred SIU when the SIU comes back after a failure.
SS7-Specific Function Information chapter : Under gc_OpenEx( ) Variances for SS7,
deleted a note that said trunk devices may not be opened for SS7. (The note was
incorrect, trunk devices can be opened for SS7.)
05-2274-005
January 2008
Global changes: Made global changes to reflect Dialogic brand.

Removed references to older generation SIUs (SIU131, SIU231, SIU520) and
boards (PCCS6, SS7CPM8), which are no longer supported.
Dialogic Global Call Architecture for SS7 chapter : In the Using Dialogic Global Call
Software with SS7 section, added that BICC protocol is supported.
Indicated that SS7HDCN16 Boards are supported in clear channel mode only.
Updated the licensing information for SS7SPCI Boards and SIUs.
In the Dialogic SS7 Interface Boards section, revised the note to indicate that
multiple Dialogic SS7 Boards are supported in a system.
Added figure showing a Dialogic SS7 Board used with a Dialogic HMP DNI
Board.
In the Dialogic Signal Interface Unit (SIU) section, revised the information to
indicate that two SIUs can be configured to share up to four local point codes.
Configuration and Startup chapter : Under SS7 Protocol Stack Configuration
(config.txt), added sections about Trunk Name Assignment and BICC
Configuration.
In the Dialogic Global Call SS7 Software Configuration (gcss7.cfg) section,
made minor changes to the descriptions of the System.Configuration,
Service.GCTLOAD_Path, and SeptelCard.ConfigDir parameters.
Added UserPart as a valid value for System.Configuration in SIGTRAN
configurations.
Added description of the Service.WatchDogMaxTime parameter under SS7
Service/Daemon Parameters.
Added information about using virtual devices for trunk names (dumBx) under
config.txt Related Parameters.
Added new section, Configuring Dialogic Boards for SIGTRAN Signaling
Support.
Added new section, Configuring Dialogic SS7 Boards for Clear Channel Mode.

Revision History
Document No.
05-2274-005
(continued)
Publication Date
Configuration and Startup chapter (continued): Added section for Sample
Configuration Files (This information formerly appeared in the Supplementary
Reference Information chapter.) In this section, added sample configuration files
for:
- System with Dialogic SS7HDP Board for Circuits and Signaling on DTI Trunks
- M3UA Configuration
- M2PA Configuration
- Clear Channel Operation
- Mixed Configuration (SS7 Signaling and Clear Channel)
- Mixed Configuration (Call Control and Transaction Based)
- Multiple Dialogic SS7 Boards in a System
Revised the Sample gcss7.cfg Configuration File (deleted comment that said the
Service.WatchDogMaxTime parameter was not supported).
SS7-Specific Operations chapter : Added new section, Dynamically Adding and
Deleting SS7 Circuit Groups.
Added new section, Handling Layer 1 Alarms.
In the Inbound Continuity Check section, added information about the events
received if GCEV_DETECTED is enabled or not enabled.
SS7-Specific Function Information chapter : Under Dialogic Global Call Functions
Supported by SS7, indicated that the following functions are supported (these
are Global Call Alarm Management System (GCAMS) functions):
gc_AlarmName( ), gc_AlarmNumber( ), gc_AlarmNumberToName( ),
gc_AlarmSourceObjectID( ), gc_AlarmSourceObjectIDToName( ),
gc_AlarmSourceObjectName( ), gc_AlarmSourceObjectNameToID( ),
gc_GetAlarmConfiguration( ), gc_GetAlarmFlow( ), gc_GetAlarmParm( ),
gc_GetAlarmSourceObjectList( ), gc_GetAlarmSourceObjectNetworkID( ),
gc_SetAlarmConfiguration( ), gc_SetAlarmFlow( ),
gc_SetAlarmNotifyAll( ), gc_SetAlarmParm( )
Under gc_OpenEx( ) Variances for SS7, added information about virtual devices.
Under gc_SetConfigData( ) Variances for SS7, added that gc_SetConfigData( )
can be used for dynamically adding and deleting SS7 circuit groups at runtime.
SS7-Specific Data Structures chapter : Added GCSS7_ISUP_CFG_CCTGRP and
GCSS7_TRUNK_CFG data structures.
SS7-Specific Error Codes and Event Cause Codes chapter : Updated to show
support for cause codes that were formerly not supported. (The cause codes for
GCEV_BLOCKED and GCEV_UNBLOCKED events, and the cause code for
timeout are now supported.)
Added event cause codes S7RV_LOCAL_RESET and S7RV_REMOTE_RESET
for the GCEV_UNBLOCKED event.
Added event cause codes related to layer 1 alarms.
Supplementary Reference Information chapter : Updated the list of references.
Moved the sample configuration files from this chapter to the Configuration and
Startup chapter.
10

Revision History
Document No.
Publication Date
05-2274-004
July 2005
General: Updates to acknowledge Intel NetStructure as a registered trademark.

General: Replaced the term DCM with Intel Dialogic configuration manager.
General: Updates to indicate support for SS7G21 and SS7G22 Signaling Gateways
in SIU Mode.
Configuring an Intel NetStructure SS7 Board as a TDM Bus Master : Added text to
describe configuration in Linux systems.
ISUP Configuration: Added paragraph to indicate support for
CAL_MSG_HEARTBEAT ISUP messages.
Dual-Resilient SIU Configuration Parameters: Added the SIU.Dual.TolerateCallTime
parameter and description.
Global Call Functions Supported by SS7: Added new supported utility functions:
gc_util_copy_parm_blk( ), gc_util_find_parm_ex( ),
gc_util_insert_parm_ref_ex( ) and gc_util_next_parm_ex( ) and new
unsupported functions: gc_AcceptModifyCall( ), gc_SetAuthenticationInfo( ),
gc_RejectModifyCall( ) and gc_ReqModifyCall( ).
gc_GetSigInfo( ) Variances for SS7: Rephrased note.
gc_MakeCall( ) Variances for SS7: Rephrased the statement of support for the
timeout parameter.
05-2274-003
March 2005
General: Updates to indicate support for SS7HD Boards (both PCI and CompactPCI).
General: Changed board names as follows (excluding command names and book
titles):
- SPCI2S to SS7SPCI2S
- SPCI4 to SS7SPCI4
- CPM8 to SS7CPM8
05-2274-002
September 2004
SS7 Server Log File: Updated the location of the SS7 server log file under Windows.
gc_GetParm( ) Variances for SS7: Added new GCPR_IGNORE_BCI parameter.
gc_SetParm( ) Variances for SS7: Added new GCPR_IGNORE_BCI parameter.
Global Call SS7 Software Configuration (gcss7.cfg): Added the following
configuration parameters: Service.IgnoreBCI, Service.CleanCidBit15,
SIU.ConfigureRsiLinks.
Sample system.txt File for a System with SS7 Boards: Updated.
Sample config.txt File for a System with Circuits and Signaling on an SS7 Board:
Updated.
Sample config.txt File for a System with Circuits and Signaling on DTI Trunks:
Updated.
Sample system.txt File for a Single-SIU and Dual-SIU System: Updated.
Sample config.txt File for a Single SIU System with One Host: Updated.
Sample config.txt File for a Single-SIU System with Two Host: Updated.
Sample config.txt File for SIU A in a Dual-Resilient SIU System with a Single Host:
Updated.
Sample config.txt File for SIU B in a Dual-Resilient SIU System with a Single Host:
Updated.
Section 3.5, Configuring an Intel NetStructure SS7 Board as a TDM Bus Master:
New section added.
Section 5.6, Using Overlap Send and Receive: Updated to indicate: 1) limitations
when using gc_SendMoreInfo( ), 2) gc_SndMsg( ) can still be used to send
SAM.

11
Revision History
Document No.
Publication Date
05-2274-002-01
March 2004
Table 1, Intel NetStructure SS7 Board Configurations - Features and Benefits:

Removed reference to ISA in the caption and updated the first row to indicate
support for four signaling links, not three.
Section 3.8.1.2, SIU Systems: Updated the first code segment under step 3 to
reference RSICMD.EXE.
Table 6, Error Codes for SS7 Server Start Failure: Updated the error code
descriptions for 0x5001 and 0x5002.
Section 3.8.2.4, SIU does not Function Correctly After Modification of config.txt:
Updated the text for step 2 to better explain that 0x0d is equivalent to a carriage
return symbol.
Section 10.1, SS7-Specific Error Codes: Updated some descriptions and added
asterisks to identify codes not currently supported.
Section 10.2, SS7-Specific Event Cause Codes: Added new section.
Section 11.8, Sample config.txt File for a Single-SIU System with Two Host: Added
new section.
Section 11.6, Sample system.txt File for a Single-SIU and Dual-SIU System: Added
mandatory LOCAL and FORK_PROCESS commands.
Section 11.9, Sample system.txt File for a Dual-Resilient SIU System: Added
mandatory LOCAL and FORK_PROCESS commands.
Section 11.9, Sample config.txt File for SIU A in a Dual-Resilient SIU System with a
Single Host: Updated MTP_ROUTE commands.
Section 11.10, Sample config.txt File for SIU B in a Dual-Resilient SIU System with a
Single Host: Updated MTP_ROUTE commands.
05-2274-001
November 2003
Initial version of document. Much of the information contained in this document was
previously published in the Global Call SS7 Technology Users Guide for Windows
Operating Systems, document number 05-1380-006 and the Global Call SS7
Technology Users Guide for Linux Operating Systems, document number 05-1936001. Major changes since these document versions are listed below.
General: Updates to accommodate all Global Call SS7 Software configuration in a
single file called gcss7.cfg.
Integrated the Troubleshooting chapter into the Configuration and Startup
chapter.
Viewing Parameter Values With the Intel Dialogic Configuration Manager : Added
section to explain that it is only possible to view key parameters values in the
configuration manager (DCM). Configuration of parameters previously
configured using DCM is now done using the gcss7.cfg file.
SS7 Call Scenarios: Replaced existing scenarios with more up-to-date and
comprehensive scenarios.
Building Global Call SS7 Applications: Added as a new chapter.
gc_OpenEx( ) Variances for SS7: Removed :L_SS7 from the devicename string; no
longer required. (PT 30317)
S7_SIGINFO_BLK: Updated the length parameter description; 1 must be added for
the NULL character.
Supplementary Reference Information: Updated the sample configuration files.
12

About This Publication

The following topics provide information about this publication.
Purpose
Applicability
Intended Audience
How to Use This Publication
Related Information
Purpose
This guide is for users of the Dialogic Global Call API who choose to write applications that use
SS7 technology. This guide provides Global Call SS7-specific information only, and should be
used in conjunction with the Dialogic Global Call API Programming Guide and the Dialogic
Global Call API Library Reference, which describe the generic behavior of the Global Call API.
Applicability
This document version is applicable to Dialogic Host Media Processing (HMP) Software and to
Dialogic System Release Software for Linux and Windows operating systems.
Check the Release Guide for your software release to determine whether this document is
supported.
Intended Audience
This guide is intended for:
Distributors
System Integrators
Toolkit Developers
Independent Software Vendors (ISVs)
Value Added Resellers (VARs)
Original Equipment Manufacturers (OEMs)
This publication assumes that the audience is familiar with the Linux and Windows operating
systems and has experience using the C programming language.

13
How to Use This Publication

Refer to this guide if you have installed the system software that includes the Dialogic Global
Call Software.
This guide is divided into the following chapters:
Chapter 1, SS7 Overview gives a brief introduction to SS7 technology for novice users.
Chapter 2, Dialogic Global Call Architecture for SS7 describes how Global Call software
can be used with SS7 technology and provides an overview of the architecture.
Chapter 3, Configuration and Startup describes how to configure the Dialogic SS7
software environment and how to start a system that contains Dialogic SS7 boards. Sample
configuration files are included at the end of this chapter.
Chapter 4, SS7 Call Scenarios provides some call scenarios that are specific to SS7
technology.
Chapter 5, SS7-Specific Operations describes how to use the Global Call API to perform
SS7-specific operations, such using overlap send and receive, performing continuity checks,
etc.
Chapter 6, Building Dialogic Global Call SS7 Applications provides guidelines for
building Global Call Software applications that use SS7 technology.

Chapter 7, Debugging Dialogic Global Call SS7 Applications provides information for
debugging Global Call Software applications that use SS7 technology.

Chapter 8, SS7-Specific Function Information describes the additional functionality of
specific Global Call Software functions used with SS7 technology.

Chapter 9, SS7-Specific Data Structures provides a data structure reference for SS7-specific
data structures.
Chapter 10, SS7-Specific Error Codes and Event Cause Codes provides descriptions of SS7-
specific event cause codes.

Chapter 11, Supplementary Reference Information provides references to publications about
SS7 technology.
A Glossary and an Index can be found at the end of the document.
Related Information
Those who choose to develop Global Call Software applications that use SS7 technology can refer
to the following documents and web sites:
System7 ISUP Programmers Manual
System7 TUP Programmers Manual
System7 Software Environment Programmers Manual
Dialogic Global Call API Library Reference
Dialogic Global Call API Programming Guide
Release Guide and Release Update for your Dialogic software release
14

http://www.dialogic.com/support/ (for Dialogic technical support)

http://www.dialogic.com/ (for Dialogic product information)
Note:
The SS7 stack and system documentation are available for download at:
http://www.dialogic.com/support/helpweb/signaling/default.htm. You will need to register with the
support site to gain access to the documentation.

15
16

SS7 Overview
1.
This chapter provides a brief overview of Signaling System 7 (SS7) technology. It is a high-level
description of the technology and does not intend to provide details of any aspect of SS7
technology. Some references to where more detailed information can be obtained are provided.
Topics covered by this chapter include:
SS7 and Computer Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
SS7 Protocol Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.1
SS7 and Computer Telephony

Signaling System 7 (SS7) is a common-channel signaling (CCS) system that defines the procedures
and protocol by which network elements (signaling points) in the public switched telephone
network (PSTN) exchange information over a digital signaling network to facilitate wireline and
wireless (cellular) call setup, routing and control.
In an SS7 network, control messages (packets) are routed through the network to perform call
management (setup, maintenance, and termination) and network management functions. Therefore,
the common-channel signaling SS7 network is a packet-switched network, even though the
network being controlled can be a circuit-switched network (PSTN).
An SS7 network is comprised of network elements connected together using signaling links. Such
a network element that is capable of handling SS7 control messages is called a signaling point
(SP). All signaling points in an SS7 network are identified by a unique code known as a point code.
There are three different basic types of network elements:
Signal Transfer Point (STP) - A signaling point that is capable of routing control messages;
that is, a message received on one signaling link is transferred to another link.
Service Control Point (SCP) - Contains centralized network databases for providing
enhanced services. An SCP accepts queries from an SP and returns the requested information
to the originator of the query. For example, when an 800 call is initiated by a user, the
originating SP sends a query to an 800 database (at the SCP) requesting information on how to
route the call. The SCP returns the routing information to the SP originating the query and the
call proceeds.
Service Switching Point (SSP) - A signaling point in a switching office, either a local
exchange or a tandem office. An SSP has the capability to control voice circuits via a voice
switch. The SSP can either integrate the voice switch or can be an adjunct computer to the
voice switch.
Network elements are interconnected using signaling links. A signaling link is a bidirectional
transmission path for signaling, comprised of two data channels operating together in opposite
directions at the same data rate. The standard rate on a digital transmission channel is 56 or 64

17
SS7 Overview
kilobits per second (kbps), although the minimum signaling rate for call control applications is 4.8
kbps. Network management applications may use bit rates lower than 4.8 kbps.
Figure 1 shows an example of an SS7 network that carries signaling information for the underlying
PSTN network nodes.
Figure 1. Signaling and Information Transfer Networks
SCP
SCP
STP
STP
SP
User
LE
SP
User
LE
STP
STP
SP
SP
LE
LE
SP
TC
PSTN Nodes:
LE - Local Exchange
TC - Transfer Center
SP
LE
SP
TC
SS7 Nodes:
SP - Signaling Point
STP - Signal Transfer Point
The signaling network is independent of the circuit-switched network. Signaling links can be
physically located on trunks that carry voice circuits, but can also be completely independent, or
even use a different transmission medium (for example, serial V.35). SSPs are the bridges between
both networks.
To ensure reliable transfer of signaling information in an environment susceptible to transmission
disturbances or network failures, an SS7 network employs error detection and error correction on
each signaling link. An SS7 network is normally designed with redundant signaling links and
includes functions for the automatic diversion of signaling traffic to alternative paths in case of link
failures.
Another type of network element that appears in an Intelligent Network (IN) is the Intelligent
Peripheral (IP). An IN is a service-independent telecommunications network, that is, a network in
which intelligence is taken out of the switch and placed in computer nodes that are distributed
throughout the network. An IP is an SP that provides enhanced services to the SSP, usually under
18

SS7 Overview
control of an SCP. Those services range from providing user-input prompts and collecting digits to
providing a complete service application.
1.2
SS7 Protocol Stack

The hardware and software functions of the SS7 protocol are divided into functional abstractions
called levels. These levels map loosely to the Open Systems Interconnect (OSI) 7-layer reference
model defined by the International Standards Organization (ISO). This model describes the
structure for modeling the interconnection and exchange of information between users in a
communications system.
Figure 2 shows the layers of the SS7 protocol stack when transporting SS7 signaling over the
PSTN and how the layers relate to the layers of the OSI Model.
Figure 2. SS7 Protocol Stack Layers

SS7 Model
OSI Model
OMAP
ASEs
Application
TCAP
TUP
Presentation
ISUP
Session
Transport
SCCP
Network
MTP3
NSP
MTP
MTP2
Data Link
MTP1
Physical
Legend:
OMAP - Operations Maintenance Application Part
ASEs - Application Service Elements
TCAP - Transaction Capabilities Application Part
ISUP - ISDN User Part
TUP - Telephony User Part
SCCP - Signaling Connection Control Part
MTP - Message Transfer Part
NSP - Network Service Part

19
SS7 Overview
1.2.1
Lower Stack Layers for SS7 over a Circuit-Switched

Network
When transporting SS7 signaling over a circuit-switched network, the lowest three levels of the
SS7 stack, called the Message Transfer Part (MTP), provide a reliable but connectionless
(datagram or packet style) service for routing messages through the SS7 network. This service is
used by the various user parts described in Section 1.2.2, Upper Stack Layers, on page 20.
The MTP is subdivided into three parts as follows:
MTP1, also called the signaling data link layer, is concerned with the physical and electrical
characteristics of the signaling links. MTP1 corresponds to the physical layer of the OSI
model.
MTP2, also called the signaling link layer, is a data link control protocol that provides for the
reliable sequenced delivery of data across a signaling data link. MTP2 corresponds to the data
link layer of the OSI model.
MTP3, also called the signaling network layer, provides for routing data across multiple
STPs from control source to control destination. MTP3 corresponds to a part of the network
layer of the OSI model.
The connectionless nature of the MTP provides a low-overhead facility tailored to the requirements
of telephony. However, the MTP does not provide all the services of the corresponding OSI
network layer. To support Integrated Services Digital Network (ISDN) applications such as
network management that requires expanded addressing capability and reliable message transfer, a
separate module is provided:
Signaling Connection Control Part (SCCP), defines a wide variety of network-layer
services. SCCP corresponds to part of the network layer of the OSI model.
The MTP and the SCCP together form the Network Service Part (NSP). The resulting split in OSI
network functions between MTP and SCCP has the advantage that the higher-overhead SCCP
services can be used only when required, and the more efficient MTP services can be used in other
applications.
1.2.2
Upper Stack Layers

The upper parts of the SS7 protocol stack are concerned with the actual contents of the SS7
messages and are sometimes called application layers. These include:
ISDN User Part (ISUP), provides the signaling needed for basic ISDN circuit-mode bearer
services as well as ISDN supplementary services having end-to-end significance. ISUP is the
protocol that supports ISDN in the public switched telephone network. It corresponds to the
transport, session, presentation, application layers and part of the network layer of the OSI
model.
Telephony User Part (TUP), an ISUP predecessor in providing telephony signaling functions.
TUP has now been made obsolete by ISUP in most countries and in the international network.
The TUP corresponds to the transport, session, presentation, application layers and part of the
network layer of the OSI model.
20

SS7 Overview
Transaction Capabilities Application Part (TCAP), provides the mechanisms for
transaction-oriented (rather than connection-oriented) applications and functions. The TCAP

corresponds to the application layer in the OSI model. TCAP is often used for database access
by the SS7 switches but has many other applications through the network.
Operations and Maintenance Application Part (OMAP), specifies network management
functions and messages related to operations and maintenance. The OMAP corresponds to the
application layer in the OSI model.
Application Service Elements (ASEs), represent user parts that are highly application-
specific, for example:

Intelligent Network Application Part (INAP)
Mobile Application Part (MAP), provides the signaling functions necessary for the
mobile capabilities of voice and non-voice applications in a mobile network
IS41, an ANSI signaling standard used in cellular networks
For any application, all three MTP layers and at least one application layer are required. Typically,
the word user in modules such as ISUP, TUP and so on explicitly identifies the module as a user
of the transport mechanism MTP.
SS7 computer telephony applications that transport SS7 signaling over a circuit-switched network
can use the ISUP (on top of the MTP layers) to control voice circuits, and sometimes TCAP to
query for information or to receive commands from a SCP.

21
SS7 Overview
22

Dialogic Global Call Architecture

for SS7
2.
This chapter describes the Dialogic Global Call Software architecture when using SS7 technology
and provides a high-level description of how the Global Call API can be used to develop call
control applications that use SS7. Topics include:
Using Dialogic Global Call Software with SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Architecture Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Dialogic SS7 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Dialogic Global Call SS7 Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
SS7 Protocol Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Using Dialogic Global Call Software with SS7
2.1
The SS7 signaling system is a packet-switched data network that forms the backbone of the
international telecommunications network. SS7 plays an important role in both wireline and
wireless networks. SS7 provides two basic types of services:
Call Control - SS7 provides fast and reliable common channel or out-of-band signaling for
call control. At the heart of the SS7 call control function is a network of highly-reliable packet
switches called Signal Transfer Points (STPs).
Intelligent Network - The SS7 network enables the implementation of Intelligent Network
(IN) and Advanced Intelligent Network (AIN) services. SS7 messages traverse STPs and enlist
the use of Service Control Points (SCPs), Service Switching Points (SSPs), and Intelligent
Peripherals to deliver these services to the user.
Dialogic Global Call Software provides a common call control interface for applications,
regardless of the signaling protocol needed to connect to the local telephone network. This manual
describes the use of Global Call Software to perform call control functions in a network that
supports SS7 signaling.
For SS7 and other protocols, Global Call Software provides a higher level of abstraction for call
control, shielding application developers from the need to deal with the low-level details.
Note:
Global Call Software covers only the call control aspects of SS7. It does not provide an API for
other user parts such as TCAP and INAP.
Currently, Global Call SS7 Software supports the ISUP protocol (ANSI version T1.609,
ITU versions Q.761 to Q.764 and Q.767), TUP protocol, and BICC protocol.

23
Dialogic Global Call Architecture for SS7
Global Call Software supports the SS7 solutions implemented using Dialogic SS7 hardware and
software. Solutions are based on the following hardware and software components:
Note:
For up-to-date information on supported hardware, refer to the Release Guide and Release Update
for your Dialogic Software release.
SS7 Interface Boards: Dialogic SS7SPCI4, SS7SPCI2S, and SS7HDP (PCI), and
SS7HDCD16, SS7HDCQ16 and SS7HDCS8 (CompactPCI) Boards. SS7HDCN16 is

supported in clear channel (DTI) mode only. (For information about Dialogic SS7 Boards
operating in clear channel mode, see Section 3.7, Configuring Dialogic SS7 Boards for
Clear Channel Mode, on page 53.)
Signaling Interface Units: Dialogic SS7G2x (operating in SIU mode)
Dialogic SS7 Protocols
Note:
2.1.1
The Dialogic SS7SPCI4 and SS7SPCI2S (PCI) Boards can be licensed for 1024, 2048, or 4096
circuits. Dialogic SS7HDP (PCI), and Dialogic SS7HDCS8, SS7HDCD16, and SS7HDCQ16
(CompactPCI) Boards can be licensed for 8192 or 32,768 circuits. The Dialogic SIUs can be
licensed to handle up to 65,535 circuits. Contact Dialogic Support for information about licensing.
Dialogic SS7 Interface Boards

Dialogic SS7 Boards are intelligent SS7 signaling boards that combine on-board support for the
SS7 common channel signaling protocols, one, two, four, or eight interfaces depending on the
board type, and CT Bus local PCM time slots on a mezzanine bus. A dedicated on-board processor
ensures that performance is independent of the load on the host PC. Downloadable operating
software makes the board easy to upgrade when protocol specification changes are necessary.
Notes: 1. Multiple Dialogic SS7 Boards can be configured and used under Global Call SS7 Software
control. The SS7 Boards are supported for carrying SS7 links or for clear channel. When using
multiple SS7 Boards under Global Call Software for carrying SS7 links, the ISUP and MTP3
layers have to run on the host (versus running on the board).
2. To support multiple boards, the device naming convention used in previous versions of Global
Call SS7 Software has been changed, and the revised naming convention has an impact on
systems with Dialogic SS7SPCI2S Boards. For further information, see Section 3.2.1, Trunk
Name Assignment, on page 39.
The Dialogic SS7SPCI4 and SS7SPCI2S Boards are PCI boards that feature four E1/T1 or two
E1/T1 interfaces, an H.100 PCM Highway, two serial network interfaces, and four SS7 links.
The Dialogic SS7HDP is an SS7 PCI board that provides up to four E1/T1 interfaces, V.11 (V.35compatible) serial ports, an H.110 PCM Highway, and 64 SS7 links.
The Dialogic SS7HDCS8 is an SS7 CompactPCI board that provides up to eight E1/T1 interfaces,
V.11 (V.35-compatible) serial ports, an H.110 PCM Highway, and 32 SS7 links.
The Dialogic SS7HDCD16 is an SS7 CompactPCI board that provides up to 16 E1/T1 interfaces,
The Dialogic SS7HDCQ16 is an SS7 CompactPCI board that provides up to 16 E1/T1 interfaces,
24

Figure 3, Figure 4, and Figure 5 show some configurations that use a Dialogic SS7 Board in
conjunction with other Dialogic Boards in a single chassis that in each case supports up to 256
ports. Table 1 summarizes the features and benefits of each configuration.
Dialogic SS7 Boards can also be used in conjunction with Dialogic HMP Digital Network
Interface (DNI) Boards. Figure 6 shows an example of a TDM-to-IP gateway.
Table 1. Dialogic SS7 Board Example Configurations - Features and Benefits
Example
Configuration
Dialogic SS7
Board Configuration
1
Features
Benefits
E1/T1 line with SS7 signaling connected to the

Dialogic SS7 Board
Multiple signaling reliability

with up to four signaling links
Voice channels routed through the Dialogic SS7

Board via the CT Bus
SS7 E1/T1 managed by the Dialogic SS7 Board
Dialogic SS7
Board Configuration
2
SS7 link and bearer channels enter through Dialogic

Network Interface Board
CT Bus clocking managed via

Dialogic Boards
E1/T1 with SS7 signaling channel connects to a

Dialogic Voice Board
All voice and data resources

managed by Dialogic Boards
The SS7 signaling is routed to the Dialogic SS7

Board via the CT Bus
Dialogic SS7
Board Configuration
3
The SS7 link is connected via a synchronous V.35

connection
All E1/T1 trunks (bearing voice circuits) enter through
Dialogic Network Interface Boards
Separates the signaling

channel from the bandwidth
channels
All signaling controlled using
V.35 clocking via two V.11
connections on the Dialogic
SS7 Board
Figure 3. Dialogic SS7 Board Example Configuration 1

PC
Application
DM/V960-4T1
CT Bus
DM/V960-4T1
E1/T1
T1 *
Dialogic
DM/V2400A
Board
Dialogic
SS7 PCI or CompactPCI
Board
SS7
T1 *
Legend:
SS7 Signaling
Voice Channels
Note: * indicates that for E1 interfaces, the equivalent

boards with E1 interfaces must be used.

25
Notable features in this configuration include:

The E1/T1 line with the SS7 signaling is connected to the Dialogic SS7 Board
B-channels are routed through the Dialogic SS7 Board to voice resource via CT Bus
The SS7 E1/T1 is managed by the Dialogic SS7 Board
Other E1/T1 trunks are managed by Dialogic Network Interface Boards

PC
Application
DM/V960-4T1
CT Bus
DM/V960-4T1
Dialogic
DM/V960-4T1
Board
Dialogic
Board
T1 *
SS7
T1 *
T1 *
Legend:
SS7 Signaling
Voice Channels


SS7 link and bearer channels enter through Dialogic Network Interface Board
All voice and data resources managed by Dialogic Boards
E1/T1 with SS7 signaling connects to a Dialogic Voice Board
The SS7 signaling is routed to the Dialogic SS7 Board via the CT Bus
26


PC
Application
DM/V960-4T1
CT Bus
DM/V960-4T1
SS7
V.35 Link
T1 *
T1 *
Dialogic
DM/V2400A
Board
Dialogic
Board
Legend:
SS7 Signaling
Voice Channels


All E1/T1 trunks (bearing voice circuits) enter through Dialogic Network Interface Boards
The SS7 link is via a synchronous V.35 connection
Note:
The V.35 signaling is actually done via two V.11 ports using a using 26-pin D-type connector. See
the documentation accompanying the Dialogic SS7 Board for more detailed information.
Figure 6. TDM-to-IP Gateway Using Dialogic SS7 and HMP DNI Boards
TDM-to-IP Gateway
SIP-SS7 Application
(TDM-to-IP Gateway)
IP Network
3rd Party
SIP Stack
NIC
SIP
+
RTP
virtual board device

R4
APIs
IPML
HMP
Media
HMP
RTP
Global Call
SIP
Stack
H.323
Stack
GCSS7
CT Bus
ISUP + G.711
G.711
PSTN
(voice)
Dialogic
DNI1200TEPHMP Board
Dialogic
SS7 PCI Board
Legend:
Protocol

27
2.1.2
Dialogic Signal Interface Unit (SIU)

The Dialogic Signal Interface Unit (SIU) is a black-box SS7 signaling server. The models
available are the Dialogic SS7G21 and SS7G22. The capacity of each SIU type is shown in
Table 2.
Table 2. Capacity of Dialogic SIUs

Dialogic SS7G21
Dialogic SS7G22
Signaling cards
3**
Links
12
128 (max)
Linksets
12
64
Call rate
450 calls/sec*
4000 calls/sec*
* Call rates can depend on issues in the network such as the way in which
signaling is presented. The values should not be considered absolute.
** SS7HDP high-density SS7 Boards
SS7 signaling is extracted from the E1 or T1 trunks into the system, and the voice circuits can be
passed transparently to the outgoing E1 or T1 ports. Alternatively, signaling can be connected
using V.35 serial links. Signaling information is automatically distributed by the SIU, via TCP/IP,
to the host that controls the telephony circuits. Typically this is the system where the voice trunks
are terminated on Dialogic Interface Boards.
Two SIUs can be configured to share up to four local point codes, providing fully resilient
operation within up to four local point codes. In normal operation, signaling can be load-shared
across the two SIUs. Then, if one unit fails, the remaining unit handles all signaling. Multiple hosts
can be connected to a single SIU, or to a resilient SIU pair, allowing large systems to be built.
Figure 7, Figure 8, and Figure 9 show some configurations using the SIU in conjunction with
Dialogic Boards. (The SIU can also be used in conjunction with Dialogic HMP DNI Boards.)
Table 3 summarizes the features and benefits of each configuration.
Table 3. SIU Example Configurations - Features and Benefits
Example
Configuration
SIU
Configuration 1
Features
V.35 SS7 connection to SIU (SS7G21)
Additional E1/T1 B channels are connected to
voice resources on media servers
SS7 signaling terminated on an SIU
SIU distributes SS7 information to media servers
over TCP/IP
28
Benefits
Manage greater number of channels
than a single board
Reduced maintenance cost due to
smaller overhead relative to
management of more circuits

Table 3. SIU Example Configurations - Features and Benefits (Continued)

Example
Configuration
SIU
Configuration 2
Features
Benefits
SS7 E1/T1 connected to SIU (SS7G21 or

SS7G22)
SS7 signaling terminated on SIU
Additional E1/T1 B channels

available for voice resources on
media servers
Voice channels routed through SIU via drop and

insert E1/T1
SIU distributes SS7 information to media servers
over TCP/IP
SIU
Configuration 3
SS7 link interconnects SIUs to provide a reliable

management channel
Provides dual point code

management
Dual SS7 links to separate SIUs
Redundant SS7 links for back-up of

signaling connections
SS7 distributed through a single or separate

TCP/IP connection
Figure 7. SIU Example Configuration 1
Application
TCP/IP
SS7 over TCP/IP
SS7 V.35 Link
CT Bus
SIU
Dialogic
DM/V960-4T1
DM/V1200-4E1
E1/T1
E1/T1
E1/T1
(Bearer
Only)
Application
Platform
Application
CT Bus
E1/T1
E1/T1
E1/T1
Legend:
SS7 Signaling
Voice Channels
Dialogic
DM/V960-4T1
DM/V1200-4E1
(Bearer
Only)

V.35 SS7 connection to SIU (SS7G21)
E1/T1 voice channels are connected to voice resources on media servers
SS7 signaling terminated on an SIU
SIU distributes SS7 information to media servers over TCP/IP

29
TCP/IP
SS7
Signaling
E1/T1
Application
CT Bus
SS7 over TCP/IP
SIU
E1/T1
E1/T1
E1/T1
Dialogic
DM/V960-4T1
DM/V1200-4E1
E1/T1
Application
Platform
Application
CT Bus
Legend:
SS7 Signaling
Voice Channels
Dialogic
DM/V960-4T1
DM/V1200-4E1
E1/T1
E1/T1
E1/T1

SS7 connected with E1/T1 bearer channels to SIU (SS7G21 or SS7G22)
E1/T1 voice channels connected to voice resources on media servers
SS7 signaling terminated on SIU
B channels routed through SIU via drop and insert E1/T1
SIU distributes SS7 information to media servers over TCP/IP
30


SS7 over TCP/IP
Application
CT Bus
SS7 Link
SIU #1
E1/T1
E1/T1
Dialogic
DM/V960-4T1
DM/V1200-4E1
E1/T1
Application
Platform
Signaling via T1 or V.35compatible (V.11) ports

Application
CT Bus
SS7 Link
SIU #2
E1/T1
Dialogic
DM/V960-4T1
DM/V1200-4E1
E1/T1
E1/T1
Legend:
SS7 Channel
Voice Channels

SS7 link interconnects SIUs to provide a reliability management channel (for single point code
management)
Dual SS7 links to separate SIUs (for dual point-code management)
SS7 distributed through a single or separate TCP/IP connection
Note:
To arrange for this setup, you are using two E1 or T1 lines out of the SIU Boards. This means that
you are using one of the available slots of the SIU to pass the voice channels and signaling back out
from one SIU to the other. Therefore, depending on the amount of bandwidth being administered,
you might need additional daughterboards.
See the documentation accompanying the Dialogic SS7G21 or SS7G22 product for more detailed
information.
2.1.3
SS7 Protocol Stack

The protocol stack is the software that implements the various layers of the SS7 protocol. A suite of
SS7 protocols is available and includes:
Message Transfer Part (MTP)
ISDN User Part (ISUP)
Telephony User Part (TUP)

31
Signaling Connection Control Part (SCCP)

Transaction Capabilities Application Part (TCAP)
MTP is supplied with all SIUs. MTP is available as an option for the Dialogic SS7 Boards.
Multiple country and switch variants are also available.
Note:
MTP and ISUP or TUP run on the SIU.

Each of the user parts can run on the host. See the Dialogic SS7 product documentation at
http://www.dialogic.com/support/helpweb/signaling/default.htm for detailed information.
Dialogic Global Call SS7 Software currently supports the ISUP and TUP layers. However, noncall-control related user parts could be accessed using the lower-level SS7 system software
environment API.
2.2
Architecture Overview
Figure 10 is a high level view of the Dialogic Global Call Software architecture and shows how
Global Call Software is used to provide a common call control interface for a variety of network
interface technologies including E1 CAS, T1 robbed bit, analog, ISDN, R4 on DM3, and SS7.
Figure 10. Dialogic Global Call Architecture
Application
Dialogic Global Call API Layer (Libgc.dll)
CAS
Call Control
ISDN
Call Control
Dialogic Springware Boards
R4 on DM3
Call Control
SS7
Call Control
Dialogic
DM3 Boards
Dialogic
SS7 Hardware
Multiple interface technologies can be mixed within a single application, allowing, for example,
the connection to ISDN and SS7 trunks.
See the Dialogic Global Call API Programming Guide for more information about the overall
Global Call architecture.
32

For SS7, Global Call Software requires integration with the SS7 system environment software. The
environment software is based on a number of communicating modules. Each module is a separate
task, process, or program (depending on the operating system type) and has a unique identifier
called a module ID. Modules communicate with each other by sending and receiving messages.
Each module has a message queue for the reception of messages. This process is called Inter
Process Communication (IPC). See the SS7G2x SIU Mode User Manual for more information. See
also the SS7 Programmers Manual for SPCI4, SPCI2S and CPM8 or the SS7HD Programmers
Manual for more information on the software environment and the System7 Software Environment
Programmers Manual for more information on IPC. These manuals are accessible via
http://www.dialogic.com/support/helpweb/signaling/default.htm.
Global Call SS7 Software extends this architecture by providing a Dialogic SS7 server module
(with a configurable module ID, typically 0x4d) that can communicate with existing modules. This
assignment is automatically made by the SS7 server. An example of interaction of the Global Call
SS7 Software components is shown in Figure 11.
Figure 11. Dialogic Global Call SS7 Architecture
Application N
Application 1
Dialogic
Global Call API
Other Call
Control
Library
Dialogic
Voice API
Libgcs7
Libgcs7
...
Dialogic
Global Call API
Other Call
Control
Library
Dialogic
Voice API
Libgcs7
Libgcs7
MQ gcss7
Messages*
MQ gcss7
Messages*
Dialogic Global Call SS7 Server/Daemon
Messages
GCT Messaging Environment
Note: * indicates the IPC mechanism used internally by Global Call SS7
Software for communication between the library and the server.
The figure shows how multiple applications can simultaneously use Global Call SS7 Software,
provided they do not attempt to control the same line devices (circuits).
The Dialogic SS7 Call Control Library is called Libgcs7 and is responsible for the
communication with other SS7 components in the system. Consequently, an application using
Global Call SS7 Software does not have to care about any of the lower-level aspects and can be
written to the standard Global Call API irrespective of the interface to the SS7 stack, hardware, or
communication mechanisms being used. The integration with the actual SS7 stack software
environment and the hardware only requires attention during the configuration phase.
For SS7, a Global Call line device maps directly to a telephony circuit in the PSTN. Calls made or
received on a circuit are assigned a Call Reference Number (CRN) that is used between the

33
application and the Global Call Software to identify the call, just like any other Global Call
network interface technology.
2.3
Dialogic SS7 Server

The Dialogic SS7 Server is started with all other Dialogic system components and is responsible
for performing the following tasks:
Reading and analyzing the system configuration (reads the files or pulls the configuration from
SIU(s) via FTP when applicable)

Performing startup tasks, such as CT Bus transmit time slot assignments for Dialogic
SS7SPCI4, SS7SPCI2S, or SS7HDP (PCI) and Dialogic CMP8, SS7HDCS8, SS7HDCD16,

or SS7HDCQ16 (CompactPCI) Board systems
Taking care of all communications with the underlying SS7 stack
Handling of circuits (call control, blocking/reset, etc.), groups, SIU(s), and other state
machines, thus hiding SS7 environment complexity from the application

Automatic handling of dual resilient operations (circuit groups activation and transfer to
partner SIU)
Managing multiple application connections
The messages dispatched by the Dialogic SS7 Server are handled by Libgcs7, eventually
generating standard Global Call events to the application.
In Dialogic SS7 Board systems, time slots that are used for voice circuits on lines connected to
the SS7 Board are automatically assigned a transmit time slot on the CT Bus for Dialogic
SS7SPCI4, SS7SPCI2S, or SS7HDP (PCI) and Dialogic CMP8, SS7HDCS8, SS7HDCD16, or
SS7HDCQ16 (CompactPCI) Boards, allowing the application to perform routing of these time
slots by using the standard set of bus routing functions, without having to care about special aspects
of interconnecting Dialogic SS7 Boards with other Dialogic hardware in the system.
The SS7 signaling can be routed over the CT Bus and passed through a digital network interface
front end by the Dialogic SS7 Server as well.
2.4
Dialogic Global Call SS7 Library

The Dialogic Global Call SS7 library (Libgcs7) is responsible for performing the following tasks:
Executing Global Call API functions that are invoked by the application for SS7 line devices
Sending telephony events, such as call state transitions (for example, GCEV_OFFERED,
GCEV_DISCONNECTED, etc.), to the application

Communicating in both directions with the SS7 Server
See Chapter 8, SS7-Specific Function Information for a list of supported Global Call SS7 library
functions and how to use them in an SS7 environment.
34

2.5
SS7 Protocol Stack

The SS7 protocol stack, which consists of the ISUP/TUP layer and the MTP layers, manages the
transfer of signal units (some containing messages) between the various layers of the stack and the
network.

35
36

Configuration and Startup

3.
Configuration of the SS7 environment and the Dialogic Global Call SS7 Software for operation in
that environment is described in the following topics:
SS7 System Environment Configuration (system.txt) . . . . . . . . . . . . . . . . . . . . . . . . . . 37
SS7 Protocol Stack Configuration (config.txt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Dialogic Global Call SS7 Software Configuration (gcss7.cfg). . . . . . . . . . . . . . . . . . 44
Viewing Parameter Values with the Dialogic Configuration Manager . . . . . . . . . . . . 49
Configuring a Dialogic SS7 Board as a TDM Bus Master . . . . . . . . . . . . . . . . . . . . . 50
Configuring Dialogic Boards for SIGTRAN Signaling Support . . . . . . . . . . . . . . . . 52
Configuring Dialogic SS7 Boards for Clear Channel Mode. . . . . . . . . . . . . . . . . . . . 53
Starting a Dialogic SS7 Board System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Starting an SIU-Based System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Sample Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Note:
3.1
Circuit groups can also be added and deleted dynamically at runtime. For information, see
Section 5.3, Dynamically Adding and Deleting SS7 Circuit Groups, on page 106.
SS7 System Environment Configuration (system.txt)

The SS7 system environment configuration is defined by the system.txt file. This file is used by the
GCTLOAD program to create message queues and spawn appropriate child processes.
The SS7 system software uses the concept of modules that send messages to each other. Each
module has a unique module ID, which must be specified by other modules in order to exchange
messages with each other. The module IDs that exist on the host system must be defined using
LOCAL commands in the system.txt file. Many module IDs are predefined and the lines that
specify these modules in the system.txt file should be left unchanged.
The command types that are found in the system.txt file are:
LOCAL commands
These commands are used to define the IDs.
Note: Earlier versions of the Dialogic Global Call SS7 Software required the inclusion of
extra LOCAL commands in the system.txt file for each application to define the
Global Call SS7 application IDs, but these are no longer required. Only the GCSS7
service module ID (typically 0x4d) should be defined in the system.txt file.

37
REDIRECT commands
These commands force the SS7 runtime system environment to redirect messages intended for
a specific destination module to a different module. For example, in a Dialogic SS7 Board
system, this is used to redirect messages for the ISUP module to the module that interfaces
with the board (ISUP is running on the board and not on the host).
Besides normal redirections for proper operation of the SS7 system software environment (see
sample configuration files and the Dialogic SS7 product documentation), a system
configured for Global Call SS7 should redirect status and management messages to the SS7
server.
In a Dialogic SS7 Board system, this is done using the following lines (assuming the SS7
server uses module ID 0x4d, the default value):
REDIRECT 0xdf 0x4d
* LIU/MTP2 status messages
In an SIU-based system, the command is:

REDIRECT 0xcf 0x4d
* management messages
SS7 system environment trace messages can also be directed to the Global Call SS7 server.
This is convenient because it allows the synchronized logging of SS7 system environment
trace messages with ISUP, management, and other messages being logged in one log file. The
command to redirect SS7 system environment trace messages to the Global Call SS7 server is:
REDIRECT 0xef 0x4d
* trace messages
Note: Care must be taken to ensure that there is no s7_log module running with the 0xef
module ID, that is, there should not be a FORK_PROCESS ss7_log command left
uncommented in the system.txt file. There should never be more than one module
reading messages with the same module ID in the system. Failing to follow these
rules will result in unpredictable results or even unstable behavior in the system.
FORK_PROCESS commands
These commands tell the GCTLOAD program to spawn child processes. For example, with
Dialogic SS7 PCI and CompactPCI boards, this is used to start the SSDS module that
interfaces with the board, and to start the timer modules. On SIU host systems, it can be used
to launch the RSI module that is responsible for the TCP/IP communication with the SIU
units. A FORK_PROCESS command can also be used to automatically start S7_LOG, a
message logging tool that displays system status messages.
This tool is most useful when proving or debugging a configuration, because it provides a
visual indication of the PCM trunk status, the link status, and so on. However, when working
with the Dialogic Global Call SS7 Software, it can be easier to redirect all the trace messages
into the GCSS7 servers trace file and therefore have all the messages in one file with real
timestamps, avoiding the need to synchronize different logs for analysis. Care must be taken to
avoid having several modules reading messages for the same module ID; that is, when
redirecting 0xef to GCSS7 server, there should not be an S7_LOG utility running on the stem
reading messages for the same 0xef module ID. See Section 7.1, SS7 Call Control Library
Trace File, on page 125 for more information.
On SIU systems, FORK_PROCESS should only be used to start the RSI module. It should not
be used to issue the RSI link activation commands (RSICMD), because these are sent
automatically by the SS7 server.
Note: The Dialogic SS7 Software does not require any special FORK_PROCESS
commands.
38

It is possible to configure the SS7 server to launch the GCTLOAD program automatically. In
Dialogic SS7 Board systems, it is necessary to add the -i option to the S7_MGT program in order
to complete the startup sequence.
For example:
FORK PROCESS S7_MGT -i0x4d
Note:
3.2
* notify Dialogic SS7 service
The module ID specified in the example shown should be that of the SS7 server.
SS7 Protocol Stack Configuration (config.txt)

The SS7 protocol stack is typically configured based on the config.txt configuration file.
For Dialogic SS7 Board systems, this file is used by the S7_MGT program, normally spawned by
the GCTLOAD program. The S7_MGT program reads the config.txt file and sends corresponding
configuration messages to the protocol stack modules.
For SIU systems, configuration is done in two stages:
Selection of protocol modules and assignment as either SIUA or SIUB is achieved using the
CNSYS management console command.

Editing of SS7 protocol parameters in the config.txt file.
The following sections describe only aspects of the protocol stack configuration that are important
for operation with the Dialogic Global Call SS7 Software. See the Dialogic SS7 product
documentation at http://www.dialogic.com/support/helpweb/signaling/default.htm for detailed
explanations of all the commands in the config.txt file.
3.2.1
Trunk Name Assignment

To support multiple boards, the device naming convention used in previous versions of Global Call
SS7 Software has been changed: trunk names are assigned based on the LIU_CONFIG commands
found in the config.txt file. The board_id parameter of the LIU_CONFIG command is used as a
major index and the liu_id parameter is used as a minor index for sequentially assigning trunk
device names to configured LIUs. The first configured LIU (typically board_id=0 and liu_id=0) is
assigned the dkB1 trunk name and subsequent configured LIUs get the next trunk names in
sequence.
See Section 3.11, Sample Configuration Files, on page 61 for examples of LIU_CONFIG
commands in config.txt files.
Note:
This revised naming convention has an impact on systems with one Dialogic SS7SPCI2S Board.
Previous versions of Global Call SS7 Software would have assigned the dkB2 and dkB3
devices names to the trunks of an SS7SPCI2S Board. With the trunk names now assigned
sequentially based on the LIU_CONFIG commands, the trunks of an SS7SPCI2S Board are
assigned the dkB1 and dkB2 device names (assuming the board is the first and only board in
the system).

39
3.2.2
TDM Bus Configuration of Dialogic SS7 Boards

For Dialogic SS7 Board systems that use the CT Bus (to access voice circuits on a line connected
to a Dialogic SS7 Board, or for routing the SS7 signaling), the CT Bus clocking must be
configured.
A Dialogic SS7 Board can be configured to take its clock from the CT Bus, acting as a bus
slave, or to take it from one of its line interfaces and act as a bus master, providing the clock for
all other boards on the CT Bus.
For the Dialogic SS7 PCI and CompactPCI Boards, the SS7_BOARD command in the config.txt
file should have the flags argument set to one of the values indicated in Table 4.
Table 4. CT Bus Clock Configuration for Dialogic SS7 PCI and CompactPCI Boards
Configuration
CT Bus slave
Flags
0x00C2
CT Bus master - clock from one of the line interfaces

CT Bus master -
Dialogic
SS7 Board internal clock
0x0043
0x0042
Once the Dialogic SS7 Board has been configured, the Dialogic Configuration Manager can be
used to specify that the board is a TDM master. See Section 3.5, Configuring a Dialogic SS7
Board as a TDM Bus Master, on page 50 for more information.
3.2.3
MTP Configuration
When using a Dialogic SS7 PCI or CompactPCI Board that has links routed over the CT Bus, the
stream parameter should be set to 0x83, and the timeslot parameter should be set to 0 for the first
link, 1 for the second link, 2 for the third link, and 3 for the fourth link. The other parameters
should be set to the correct values for the link being configured.
MTP_LINK 0
MTP_LINK 1
0
1
0
0
0
0
0
0
0
1
0x83
0x83
0
1
0x06
0x06
For Dialogic SS7HD PCI or CompactPCI Boards, when the timeslot parameter is set to a nonzero value, the stream parameter is the logical identity of the E1/T1 LIU (liu_id) containing the
signaling link. It should be in the range 0 to one less than the number of LIUs. When connecting
signaling links to the CT Bus, the stream and timeslot parameters of the MTP_LINK command
are not required and should be set to 0.
MTP_LINK 0 0 2 2 0 1-4 0 0 0x0006
See Section 3.11, Sample Configuration Files, on page 61 for more information.
In the gcss7.cfg file, the corresponding links should be configured as well as providing the correct
Dialogic Board device names for every link being routed over the CT Bus. For example:
MtpLink <link_ID> <device_name>
40

where, <device_name> is the Dialogic DTI time slot device name (for example, dtiB1T1 or
dtiB1T31) on which the SS7 signaling link is present.
For E1 lines, physical time slot 16 on a network interface (DTI) board is usually reserved for
signaling, but is named dtiB1T31 (because physical time slot 17 is named dtiB1T16).
3.2.4
ISUP Configuration
There are two items that require special attention in the ISUP configuration for a system using
Dialogic Global Call SS7 Software.
The ISUP_CONFIG command must specify in its UserID argument that the module using the
ISUP component is the SS7 server. By default, the SS7 server uses module ID 0x4d.
Additionally, Global Call SS7 Software relies on a specific type of circuit release procedure in the
ISUP module. This is the procedure recommended, and it requires that bit 2 (ISPF_ACR) and bit 4
(ISPF_NAI) of the <options> argument of the ISUP_CONFIG command be set to 1. You must
also set bit 6 (ISPF_GSPS) to 1 for proper generation of GCEV_BLOCKED and
GCEV_UNBLOCKED events.
Consequently, a standard ISUP_CONFIG line for ITU operation looks like the following
(assuming Point Code 1 and a maximum of 2 circuit groups):
ISUP_CONFIG 1 0x08 0x4d 0x0474 2 64
Also, circuit groups are defined by the ISUP_CFG_CCTGRP command in the config.txt file. For
example:
* Configure ISUP circuit groups:
* ISUP_CFG_CCTGRP <gid> <dpc> <base_cic> <base_cid> <cic_mask> <options>
*
<user_inst> <user_id> <opc> <ssf> <variant> <options2>
ISUP_CFG_CCTGRP 0 2 0x01 0x01 0x3fffffff 0x001e 0 0x4d 1 0x8 0 0
ISUP_CFG_CCTGRP 2 2 0x21 0x41 0x7fff7fff 0x001e 0 0x4d 1 0x8 0 0
ISUP_CFG_CCTGRP 5 1 0x41 0xa1 0x7fffffff 0x001e 0 0x4d 2 0x8 0 0
Because an application that uses the Global Call API opens circuits by giving their device name
(for example, dtiB1T1 for the first circuit on the first Dialogic DTI Board), Global Call SS7
Software requires that circuit groups that are being used by GCSS7 are configured in the gcss7.cfg
file also. This is done using the following command for each circuit group:
CGrp <gid> <trunk_name> [<base_TS>[<Pref_SIU>]]
where,
<gid>
Specifies the circuit group ID, which must match the corresponding group ID configured in the
config.txt file.
<trunk_name>
Specifies the physical device where the circuits in the group are terminated. This can be a
reference to a Dialogic Digital Network Interface Board, in which case the name is of the

41
form dtiBx (for example, dtiB1, dtiB2, and so on) or one of the trunks on a Dialogic SS7
Board, in which case the name is dkB1 for the first trunk and dkB2 for the second trunk. The
same name is used as a basis by the application for the network device name when it opens a
Global Call SS7 device. See Section 8.2.14, gc_OpenEx( ) Variances for SS7, on page 141
for details.
The following parameters are optional:
<base_Ts>
Specifies the first time slot of the trunk that corresponds to the first circuit of the group. This
time slot number is a true physical time slot number (1-31, for E1). If omitted, the first time
slot (number 1) is assumed.
Note: The <base_Ts> parameter is especially useful when running ANSI ISUP over E1
trunks with, for example, two groups of 15 circuits on each E1 trunk; the second
circuit group would be configured with the same <trunk_name> as the first one, but
with <Base_Ts>=17.
<Pref_SIU>
Specifies the default SIU for the group, that is, the SIU on which the group should be
preferably active (for load-balancing). Possible values are SIUA or SIUB. This parameter is
only valid for dual-resilient SIU configurations.
Each circuit group configuration command in the gcss7.cfg file must correspond to a circuit group
configuration command line in the config.txt file, that is, the group ID <gid> parameters should
match. For example, if the config.txt file contains the following circuit group definition commands:
*
ISUP_CFG_CCTGRP 5 1 0x41 0xa1 0x7fffffff 0x001e 0 0x4d 2 0x8 0 0
The following commands are valid in the gcss7.cfg file:

# Circuit Group configuration, Group ID must match the value in config.txt.
# CGrp <gid> <"trunk_name"> [<base_TS> [<"Pref_SIU">]]
CGrp 0 dkB1 2
CGrp 1 dtiB2 2
CGrp 2 dkB2
CGrp 3 dtiB1
CGrp 4 dumB1
CGrp 5 dumB2
The Global Call SS7 Software also supports CAL_MSG_HEARTBEAT ISUP messages. For
details on how to configure the Detection of Failed Host Applications ISUP feature, see the ISUP
Programmers Manual. When using Global Call SS7 Software, it is recommended to use this
feature in multiple-host SIU-based systems only.
42

3.2.5
TUP Configuration
TUP configuration is achieved in much the same way as the ISUP configuration described in
Section 3.2.4, ISUP Configuration, on page 41, with the following differences:
In the system.txt file, there should be a REDIRECT command for the TUP module as follows:
REDIRECT
0x4A
0x20
*TUP Module
In the config.txt file, the appropriate binary should be downloaded and the corresponding
license applied. The following are some examples:

For a Dialogic SS7 PCI Board system:
SS7_BOARD 0 SS7HDP 0X0042 SS7.dc3 TUP-L
For a Dialogic SS7 CompactPCI Board system:

SS7_BOARD 0 SS7HDC 0X0042 SS7.dc3 TUP-L
See the Dialogic SS7 product documentation at

http://www.dialogic.com/support/helpweb/signaling/default.htm for more information.
TUP parameters must be configured. The TUP_CONFIG command is described in the
Programmers Manuals for the SS7 products. For example:

* TUP_CONFIG <reserved> <reserved> <user_id> <options> <num_grps> <num_ccts>
TUP_CONFIG 0 0 0x4d 0x8166 128 4096
The options parameter is a 16-bit value containing global run-time options for the operation of
the TUP module. The meaning of each bit is as defined for the options parameter in the TUP
Configuration Request message described in the TUP Programmers Manual. For Dialogic
Global Call SS7 Software to function correctly, the following bits in the options argument
must be set:
bit 5 (TUPF_GSPS)
bit 6 (TUPF_ACR)
bit 15 (TUPF_NAI)
Circuit groups are configured using the TUP_CFG_CCTGRP command (instead of the
ISUP_CFG_CCTGRP command for ISUP), and each corresponding circuit group used by
Global Call SS7 Software must also be configured in the gcss7.cfg file. See Section 3.2.4,
ISUP Configuration, on page 41 for an example.
3.2.6
BICC Configuration
For Bearer Independent Call Control (BICC) signaling protocol, configure the config.txt file as
follows:
MTP_ROUTE user_part_mask - enable bit 13
ISUP_CFG_CCTGRP variant - set to 0xd

43
3.3
Dialogic Global Call SS7 Software Configuration

(gcss7.cfg)
The Dialogic Global Call SS7 Software is configured by editing the gcss7.cfg file. The gcss7.cfg
file is organized in sections where each section contains the parameters for a specific functional
group. See Section 3.11.1, Sample gcss7.cfg Configuration File, on page 62 for more
information.
3.3.1
System Configuration Type Parameter

System.Configuration
Specifies the type of system operation. Allowed values are: None, Card, SIU,
DualSIU, and UserPart. (UserPart is the setting for SIGTRAN configurations; see
Section 3.6, Configuring Dialogic Boards for SIGTRAN Signaling Support, on page 52.)
The default value is None. That is, at startup, there will be no attempt to detect a board on
Windows (DCM) or to start the GCSS7 server (dlgcs7d on Linux systems, DlgcS7Srv.exe on
Windows systems) when downloading the Dialogic Boards.
3.3.2
Dialogic Global Call SS7 Call Control Library Parameters

Library.LogFile
Enables library logging to be activated on the first call to gc_OpenEx( ) on an SS7 circuit with
the trace file named as specified by the value of this parameter. The default trace file name is
ss7.log.
Library.LogLevels
Controls the generation of library logging information. If set to All, the library will produce a
log file that can be very useful in troubleshooting a system. The default value is All.
Library.LogMaxLines
Limits the maximum length of a library log file to the value specified in kilobytes. The default
value is 200.
3.3.3
SS7 Service/Daemon Parameters

Service.LogLevels
Controls the generation of SS7 server logging information. If set to All, the SS7 server will
produce a log file that can be very useful in troubleshooting a system. See Section 7.2, SS7
Server Log File, on page 126 for more on this topic. The default value is All.
Service.LogMaxSize
Limits the maximum length of an SS7 servers log file to the value specified in kilobytes. The
default value is 200.
44

Service.GCTLOAD_Control
Determines if the GCTLOAD program should run automatically at startup. If set to Yes, the
SS7 server will try to start the GCTLOAD program automatically. The default value is No.
Note: This option should only be used after you have adapted and fully tested your
configuration since the GCTLOAD window, which provides very useful
configuration debugging information, is no longer displayed when this option is
enabled.
Service.GCTLOAD_Path
Contains the path to the GCTLOAD program file. This field must be set if the GCTLOAD
Control parameter is set to Yes. The default value (c:\septel for Windows or /usr/septel for
Linux) is commented out by default in the gcss7.cfg file and must be uncommented and
modified to point to the proper location.
Service.ModuleID
Defines the module ID used by the SS7 server. This must be one of the module IDs declared
LOCAL in the system.txt file. The default value is 0x4d. See Section 3.1, SS7 System
Environment Configuration (system.txt), on page 37.
Service.WatchDogMaxTime
Defines the maximum timeout (in seconds) for Global Call SS7 server-application keep-alive
(heartbeat) mechanism. The default value is 7 seconds. If this timer expires, the Global Call
SS7 server will assume that the application has failed and will terminate the IPC with the
application and block all the circuits. A value of 0 means the keep-alive mechanism is off.
Service.GroupCommandTimer
Defines the time interval to accumulate circuit group supervision requests (for example, reset,
block or unblock) for a circuit group. The default value is 500. Units are in milliseconds.
Service.IgnoreBCI
Inhibits the Dialogic Global Call SS7 Software from analyzing the Backward Call Indicator
(BCI) in incoming ACM messages and alerting the application of the call only when the
Called partys status indicator fields are set to Subscriber Free. When this parameter is set
to 1, the Global Call SS7 Software ignores the BCI content and always sends the
GCEV_ALERTING event to the application in response to an incoming ACM ISUP message.
The parameter setting applies to all circuits that are being controlled by a specific host. The
value specified by this parameter can be considered the default for the GCPR_IGNORE_BCI
parameter that can be set using the gc_SetParm( ) function (see Section 8.2.22,
gc_SetParm( ) Variances for SS7, on page 144). The default value is 0.
Service.CleanCidBit15
Recent versions of ISUP and TUP support up to 65,535 circuits per module, which means that
a 16-bit wide CID is necessary to address all of the configured circuits. The default value of
this parameter supports a backward-compatibility mode when the most significant bit is
ignored by the GCSS7 service. The default value is 1.
3.3.4
Dialogic SS7 Board Configuration Parameters

SeptelCard.ConfigDir
The path to the config.txt file. The default value (c:\septel on Windows or /usr/septel on
Linux) is commented out by default in the gcss7.cfg file and must be uncommented and
modified to point to the proper location.

45
SeptelCard.Auto_Links_Activation
Determines if MTP links should be activated automatically. Possible values are All and None.
The default value is All.
Note:
3.3.5
The term septel in configuration files relates to Dialogic SS7 Boards.
SIU Configuration Parameters

SIU.HostID
The host ID of the machine. If there is only one host connected to the SIU(s), select ID 0. The
default value is 0.
SIU.A.IP_Address
Defines the IP address of SIU A. The format of the IP address is 111.112.113.114.
SIU.A.FTP_Account
Defines the account name to be used when connecting to SIU A via FTP. The default name is
ftp. For Dialogic SS7G21 and SS7G22, the default name should be set to siuftp.
SIU.A.FTP_Password
Defines the account password to be used when connecting to SIU A via FTP. The default value
is ftp. For Dialogic SS7G21 and SS7G22, the default password should be set to siuftp.
SIU.A.RemoteConfigDir
Defines the directory on SIU A in which the config.txt file is located. The default value is .
(the dot character).
SIU.InitTimeout
Defines the maximum time that the SS7 server will wait at startup for an SIU to come online
before considering it as being down. The default value is 10 seconds.
SIU.FTP_Timeout
Defines the maximum time to wait for a response from an SIU while getting the config.txt file
via FTP. The default value is 5 seconds.
Note: Currently, the SIU.FTP_Timeout parameter is not configurable for Linux systems.
The Dialogic Global Call SS7 Software relies on the default ftp client timeout value.
SIU.FTP_Retries
Defines the number of times the Dialogic SS7 Server will reattempt to get the config.txt file
from an SIU. The default value is 2 attempts.
Note: Currently, the SIU.FTP_Retries parameter is not configurable for Linux systems.
The Dialogic Global Call SS7 Software relies on the default ftp client retries value.
SIU.ConfigureRsiLinks
Enables/disables the generation of the RSI_MSG_CONFIG message by the GCSS7 service.
When set to 0, RSI_MSG_CONFIG messages from the GCSS7 service are disabled, allowing
other applications that need to receive RSI status messages to co-exist with the Dialogic
Global Call SS7 Software. The default value is 1 (enable).
Note: For the GCSS7 service to function correctly with another application, that application
must forward all RSI messages to the GCSS7 service, which typically has the 0x4d
module ID.
46

SIU.FTP_Type
Specifies the type of file transfer protocol used by the Dialogic Global Call SS7 server to
retrieve configuration files from the SIUs when boards are downloaded. Currently, ftp and
ssh ftp (sftp) are supported. By default, this parameter is commented out in the gcss7.cfg file,
and the Global Call SS7 server uses regular ftp. To use sftp, uncomment the parameter to set
SIU.FTP_Type = SFTP.
Note: For sftp functionality on Linux systems, make sure the OpenSSH and OpenSSL
software is installed and that lftp and sftp are functional. If the OpenSSH software
does not come with your Linux operating system, you can download it from
http://www.openssh.com/. If the OpenSSL software does not come with your Linux
operating system, you can download it from http://www.openssl.org/.
If you are using Red Hat Linux Version 3.0 or earlier, you must upgrade the lftp software for
sftp support. Here are some steps to guide you in upgrading the lftp software:
1. Uninstall the current lftp software. To find out the name of the lftp package, run:
rpm -qa | grep lftp
Then remove the lftp package, for example:

rpm -e lftp-2.6.3
2. Download the latest lftp src package (for example, lftp-3.7.3.tar.gz) from
http://lftp.yar.ru/get.html.
3. Untar the lftp source in an appropriate directory. Go to the lftp-3.7.3 to build and install
the lftp software. The instructions for building the lftp binaries are in the INSTALL text
file.
To compile this package:
cd to the directory containing the package's source code and type ./configure to
configure the package for your system. If you're using csh on an old version of
System V, you might need to type sh ./configure instead to prevent csh from trying
to execute configure itself. Running configure takes a while. While running, it
prints some messages telling which features it is checking for.
Type make to compile the package.
Optionally, type make check to run any self-tests that come with the package.
Type make install to install the programs and any data files and documentation.
4. Create a symbolic link to /usr/local/bin/lftp in the /usr/bin directory by running:
ln -s /usr/local/bin/lftp lftp
from the /usr/bin directory.

5. Logout and log back in. Run lftp to make sure it is in the path.
3.3.6
Dual-Resilient SIU Configuration Parameters

SIU.B.IP_Address
Defines the IP address of SIU B. The format of the IP address is 111.112.113.114.
SIU.B.FTP_Account
Defines the account name to be used when connecting to SIU B via FTP. The default name is
ftp. For Dialogic SS7G21 and SS7G22, the default name should be set to siuftp.
SIU.B.FTP_Password
Defines the account password to be used when connecting to SIU B via FTP. The default value
is ftp. For Dialogic SS7G21 and SS7G22, the default password should be set to siuftp.

47
SIU.B.RemoteConfigDir
Defines the directory on SIU B in which the config.txt file is located. The default value is .
(the dot character).
SIU.Dual.SiuCommandTimeout
Specifies the timeout value to use when waiting for group activation or deactivation command
responses from an SIU. The default value is 5 seconds.
SIU.Dual.SiuUpDebounceTime
Specifies the time to use when detecting SIU availability. This debounce avoids undertaking
unnecessary actions in case of intermittent TCP/IP connection failures. The default value is
8 seconds.
SIU.Dual.MaxCmdRetries
Specifies the maximum number of times the SS7 server reattempts sending a group
(de)activation command to an SIU before declaring failure. A resend is required when the SIU
is already performing a command for another host system. The default value is 5 attempts.
SIU.Dual.TolerateCallTime
This parameter specifies the maximum amount of time (in seconds) for which the service
keeps calls in speech after control of a circuit group is transferred to another unit due to SIU
and/or RSI failure or restoration. This feature allows the complete restoration of the systems
normal functionality after any failure event on unit(s) or RSI link(s). The functionality covers
all cases of glare where the GCSS7 service does not receive or process the REL message from
the stack caused by RSI or SIU failure and recovery. The format of this parameter is Integer.
The default value is 600 seconds; 0 means the feature is off.
Note:
3.3.7
All the parameters for a single-SIU configuration are applicable to a dual-resilient system also.
config.txt Related Parameters

MtpLink <link_id> <link_source>
Identifies the MTP link source and link ID and must match the corresponding information in
the config.txt file.
CGrp <gid> <trunk_name> [<base_TS> [<Pref_SIU>]]
Identifies circuit group configuration and group ID and must match the corresponding
information in the config.txt file.
<gid> - Specifies the circuit group ID.
<trunk_name> - Specifies the physical device where the circuits in the group are
terminated. This can be any of the following:
reference to a Dialogic Digital Network Interface Board (e.g., a Dialogic DM3 or
Springware Board), in which case the name is of the form dtiBx (for example, dtiB1,
dtiB2, and so on)
one of the trunks on a Dialogic SS7 Board, in which case the name is of the form dkBx
(for example, dkB1 for the first trunk and dkB2 for the second trunk)
a virtual device, not tied to any physical board, in which case the name is of the form
dumBx. Virtual devices can be useful for testing purposes; for example, if there are not
enough boards in the system, you can create virtual devices without the need for hardware
for these circuits.
48

The same name is used as a basis by the application for the network device name when it opens
a Dialogic Global Call SS7 device. See Section 8.2.14, gc_OpenEx( ) Variances for SS7,
on page 141 for details.
<base_Ts> - An optional parameter that specifies the first time slot of the trunk that
corresponds to the first circuit of the group. This time slot number is a true physical time slot
number (1-31, for E1). If omitted, the first time slot (number 1) is assumed.
Note: The <base_Ts> parameter is especially useful when running ANSI ISUP over E1
trunks with, for example, two groups of 15 circuits on each E1 trunk; the second
circuit group would be configured with the same <trunk_name> as the first one, but
with <Base_Ts>=17.
<Pref_SIU> - An optional parameter that specifies the default SIU for the group, that is, the
SIU on which the group should be preferably active (for load-balancing). Possible values are
SIUA or SIUB. This parameter is only valid for dual-resilient SIU configurations.
Viewing Parameter Values with the Dialogic

Configuration Manager
3.4
Caution:
Using the Dialogic Configuration Manager to set parameters for Dialogic SS7 Boards or SIUs is
not supported. However, the Dialogic Configuration Manager can be used to view the values of a
number of key configuration parameters, such as the path to the gcss7.cfg file and the IP addresses
for SIUs.
Note:
The Dialogic Configuration Manager cannot be used to manually add a Dialogic SS7 Board or
SIU. Always allow the Dialogic system service to detect devices automatically.
3.4.1
SS7 Board Parameters

In the Dialogic Configuration Manager main window, double-click on a Dialogic SS7 Board
device to open the property sheets for that device.
The System property sheet that is specific to SS7 Boards contains the following parameter:
ConfigFile
Displays the path to the gcss7.cfg file that contains configurable parameters.
3.4.2
SIU Parameters
In the Dialogic Configuration Manager main window, double-click on a Dialogic SIU device to
open the property sheets for that device. The property sheets window contains three property sheets
that are specific to SS7 SIUs.
The System property sheet contains the following parameter:
ConfigFile
Displays the path to the gcss7.cfg file that contains configurable parameters.

49
The SIU Server property sheet contains the following parameter:

SIU A IP Address
Defines the IP address of SIU A. The format of the IP address is 111.112.113.114.
The Dual Resilient property sheet contains the following parameter:
SIU B IP Address
Defines the IP address of SIU B. The format of the IP address is 111.112.113.114.
3.5
Configuring a Dialogic SS7 Board as a TDM Bus

Master
To configure a Dialogic SS7 Board as a TDM bus master, the config.txt file must be modified (see
Section 3.2.2, TDM Bus Configuration of Dialogic SS7 Boards, on page 40).
On Linux Systems
When using Dialogic System Release 6.1 for Linux (or later) to configure a Dialogic SS7 Board
as the primary TDM bus master, it is necessary to set the clock daemon mode to PASSIVE (by
default, the mode is set to ACTIVE). Proceed as follows:
1. Open the /usr/dialogic/cfg/dlgsys.cfg file.
2. Change the ClockDaemonMode field to PASSIVE.
The updated file should look like the following:
.
.
.
; The following parameters are
; ClockDaemonMode
;
ACTIVE
- Clock Daemon
;
PASSIVE
- Clock Daemon
;
DISABLED
- Clock Daemon
[TDMBus 0] {
;ClockDaemonMode
ClockDaemonMode
}
currently supported.
is started
is started in passive mode
is not started
: ACTIVE
: PASSIVE
The update above applies to all mixed system configurations when making a Dialogic SS7 Board
the primary TDM bus master. These include:
Dialogic SS7 and DM3 Boards in a mixed system configuration
Dialogic SS7 and Springware Boards in a mixed system configuration
Dialogic SS7, DM3, and Springware Boards in a mixed system configuration
50

The update also applies in systems where a third-party board is the TDM bus master, irrespective of
the mix of Dialogic SS7, DM3, and Springware Boards in the system.
Note:
When Dialogic Springware Boards are included in a mixed system, it is important to ensure that
all Springware Boards are configured in SLAVE clocking mode; otherwise, two boards will be
configured as TDM bus master in the system. For DM3 Boards, it is not as important to ensure that
all DM3 Boards are configured in SLAVE clocking mode, because the clocking daemon in
PASSIVE mode ensures that all DM3 Boards are in SLAVE clocking mode.
To ensure that each Springware Board is set in SLAVE clocking mode, check that the
PrimaryMaster field in the /usr/dialogic/cfg/dialogic.cfg configuration file is set to NONE for
each Springware Board.
If a DM3 or Springware Board is the primary TDM bus master, with the SS7 Board as a TDM
slave, the ClockDaemonMode parameter in the /usr/dialogic/cfg/dlgsys.cfg file must be set to
ACTIVE.
When configuring a system that includes Dialogic SS7 Boards with Dialogic DM3 and/or
Springware Boards, also make sure that the TDM bus encoding method is set to A-law or Mu-law
as appropriate (A-law for E1, Mu-law for T1). This is done with the Configuration Manager utility
on the TDM Bus Settings screen.
On Windows Systems
When the Dialogic Configuration Manager (DCM) is invoked, it is possible to set the Dialogic
SS7 Board as the primary master FRU. This is done as follows:
1. In DCM, double-click on Configured Devices.
2. Double-click on TDM Bus.
3. Double-click on Bus-0 to open the Properties window.
4. Scroll down and click on Primary Master FRU (User Defined).
5. In the Values field, choose the name of the Dialogic SS7 Board that you want to be the CT
Bus master.
6. Click OK, then close DCM.
Caution:
If a Dialogic SS7 Board is a CT Bus master and it is being removed from the DCM configuration
or the system, it is imperative to set another board as the CT Bus master before making the
configuration changes or removing the Dialogic SS7 Board from the system.
When configuring a system that includes Dialogic SS7 Boards with Dialogic DM3 and/or
Springware Boards, also make sure that the TDM bus encoding method is set to A-law or Mu-law
as appropriate (A-law for E1, Mu-law for T1). This is done with the Media Type (User Defined)
parameter on the TDM Bus Configuration property sheet in DCM.

51
3.6
Configuring Dialogic Boards for SIGTRAN

Signaling Support
Global Call SS7 Software supports SIGTRAN (IETF SS7 signaling over IP). Signaling links can
be physically located on M3UA and MTP3 User Adaptation Layers. The scope of this feature is
limited to the ISDN User Part (ISUP) and Telephony User Part (TUP) layers.
In a typical SIGTRAN configuration, the ISUP/TUP and SIGTRAN stacks run on the host system.
For Global Call Software applications with SIGTRAN support, an application server process
(ASP) connects to one or more signaling gateways (SGs). The bearer trunks may terminate in the
same system on Dialogic HMP DNI Boards; see Figure 12.
Third party transport systems (e.g., M3UA, MTP3) can be used.
Figure 12. Dialogic Global Call SS7 SIGTRAN Configuration Using Dialogic HMP DNI
Boards
TCP/IP
SS7 SIGTRAN
Signaling
Application
SIGTRAN over TCP/IP
IP
CT Bus
DNI601TEPHMP
DNI601TEPHMP
E1/T1
E1/T1
E1/T1
Application
Platform
Application
CT Bus
Legend:
SS7 Signaling
Voice Channels
DNI601TEPHMP
DNI601TEPHMP
E1/T1
E1/T1
E1/T1
There are two supported SIGTRAN configurations:

M3UA (MTP3 (Message Transfer Part 3) User Adaptation Layer)
This signaling network layer provides for routing data across multiple signal transfer points
(STPs) from control source to control destination. For this feature, the ISUP configuration
remains the same in the config.txt configuration file. While no LIU, board, or MTP
configuration is required, the application needs to add the necessary SIGTRAN related
configuration parameters. To enable M3UA signaling, the System.Configuration parameter in
the gcss7.cfg file must be set to UserPart.
52

MTP3 over M2PA (MTP2 (Message Transfer Part 2) Peer-to-Peer Adaptation Layer)
This ISUP and MTP configuration remains the same in the config.txt configuration file. While
no LIU or board configuration is required, the application needs to add the necessary
SIGTRAN related configuration parameters. To enable M2PA signaling, the
System.Configuration parameter in the gcss7.cfg file must be set to UserPart.
See the sample system.txt and config.txt files in Section 3.11, Sample Configuration Files, on
page 61 for more information.
Note:
For Linux only: If the gc_Open( ) function fails, check the DlgcS7.log file and check for the
following trace:
MQSmsgq::MQSmsgq() msgget(... IPC_CREAT|0766) failed, errno=28
This indicates that a message queue has to be created but the system limit for the maximum number
of message queues (MSGMNI) would be exceeded. To find out the maximum number of message
queues (MSGMNI) on your system, issue the following command:
cat /proc/sys/kernel/msgmni
To increase the MSGMNI on your system, issue the following command:

sysctl -w kernel.msgmni=n
where n is the maximum number of message queues (MSGMNI) that you want the system to allow.
For example:
sysctl -w kernel.msgmni=32
3.7
Configuring Dialogic SS7 Boards for Clear

Channel Mode
When used with Dialogic Global Call Software, Dialogic SS7HDP and SS7HDC Boards can
have trunks that are not configured for SS7 signaling (DTI mode); i.e., all the time slots on these
trunks operate in clear channel mode. The SS7 Boards are supported in a non-SS7 signaling
environment. This allows the application to use an SS7 Board in a clear channel mode to terminate
E1/T1 trunks and switch them over the CT bus.
To configure an SS7 Board for clear channel, modify the gcss7.cfg file to specify a ClearGrp
parameter that includes the following fields:
<trunk_name>
The virtual device name of the trunk (for example, dkB1).
Note: This specifies the physical device where the circuits in the group are terminated. The
<trunk_name> refers to one of the trunks on the SS7 Board, where dkB1 is the name
of the first trunk (first LIU defined in the config.txt file), dkB2 is the name of the
second trunk (second LIU defined in the config.txt file), and so on. The same name is
used as a basis by the application for the network device name when it opens a Global
Call SS7 device.
<ts_mask>
Specifies the time slots that are to be used as clear channels. Each bit in this mask corresponds
to a physical time slot on the trunk where a 1 indicates that the time slot is to be used in clear

53
channel mode. For example, 0x7fffffff for E1 or 0xffffff for T1 indicates that all time slots in
the trunk are to be used in clear channel mode.
For example:
# Clear Channel Group configuration.
# ClearGrp <"trunk_name"> <ts_mask>
ClearGrp dkB1 0x7fffffff
See the sample system.txt and config.txt configuration files in Section 3.11, Sample Configuration
Files, on page 61 for more information.
Notes: 1. The following APIs are supported in clear channel mode:
gc_Attach( )
gc_AttachResource( )
gc_Close( )
gc_Detach( )
gc_GetNetworkH( )
gc_GetResourceH( )
gc_GetVoiceH( )
gc_GetXmitSlot( )
gc_Listen( )
gc_OpenEx( )
gc_Start( )
gc_Stop( )
gc_UnListen( )
2. None of the call control related APIs are supported for clear channel trunks (DTI mode) (for
example, gc_MakeCall( ), gc_WaitCall( ), gc_AnswerCall( ), etc.).
3. For clear channel circuits, if a call control function is issued, an error message is generated
indicating that the API is not supported. The error value EGC_UNSUPPORTED is the value
returned by Global Call Software when the gc_ErrorInfo( ) function is used to retrieve the error
code.
3.8
Starting a Dialogic SS7 Board System

The Dialogic system service downloads the required firmware to Dialogic boards, starts all
Dialogic device drivers, and assigns CT Bus time slots.
54

Starting the system involves two steps:

1. Start the SS7 system environment. This involves starting the gctload program, which sets up
the IPC (Inter Process Communication) and messaging system.
The gctload program also launches the s7_mgt program that reads the config.txt, downloads
the specified firmware to the board, and configures the stack as specified in the config.txt file.
2. Start the Dialogic system service that automatically performs all initialization steps required
by the Dialogic Global Call SS7 system (excluding the preceding step 1).
Note:
3.9
Starting the gctload program can be done manually by launching the gctload program from the
/usr/septel directory on Linux systems or the c:\Septel directory on Windows systems. It can also
be started automatically during the Dialogic system service startup as controlled by the
GCTLOAD_Control setting in the gcss7.cfg file. See Section 3.3, Dialogic Global Call SS7
Software Configuration (gcss7.cfg), on page 44 for more information.
Starting an SIU-Based System

When you start an SIU-based system, the Dialogic system service downloads the required
firmware to Dialogic Boards, starts all Dialogic device drivers, and assigns time slots.
Caution:
At least one SIU must be up and running when you start the service. This is required because the
configuration is read from the SIU.
Starting the system involves two steps:
1. Start the SS7 system software environment. This involves starting the gctload program,
which sets up the IPC (Inter Process Communication) and messaging system.
If the system.txt file is correctly configured, the gctload program loads the RSI module
responsible for communicating with the server(s). However, the actual connection to the
server(s) is made by the Dialogic SS7 server.
2. Start the Dialogic system service that automatically performs all initialization steps required
by the Dialogic Global Call SS7 system.
Note:
3.10
Starting the gctload program can be done manually by launching the gctload program from the
/usr/septel directory in Linux systems or the c:\Septel directory in Windows systems. It can also
be started automatically during the Dialogic system service startup as controlled by the
GCTLOAD_Control setting in the gcss7.cfg file. See Section 3.3, Dialogic Global Call SS7
Software Configuration (gcss7.cfg), on page 44 for more information.
Troubleshooting
This section provides information on troubleshooting problems encountered when configuring and
starting up a system. Topics include:
Proving the Configuration

55
Common Problems and Solutions
3.10.1
Proving the Configuration

An important step in troubleshooting a Dialogic Global Call SS7 system is proving the SS7 stack
configuration and the SS7 network connection (links), independently of any Dialogic component.
3.10.1.1
Dialogic SS7 Board Systems

Verify a Dialogic SS7 Board system configuration as follows:
1. Add debug flags to the system.txt file. For Dialogic SS7 PCI and CompactPCI Board
systems, add debugging flags to the SSD and S7_MGT modules, and make sure S7_LOG is
launched:
FORK_PROCESS
FORK_PROCESS
FORK_PROCESS
FORK_PROCESS
FORK_PROCESS
.\SSDS.EXE -d
.\TIM_NT.EXE
.\TICK_NT.EXE
.\S7_MGT.EXE -d
.\S7_LOG.EXE -m0xef
2. Start GCTLOAD and watch out for any error messages (for example, Timeout waiting
for). The first part of the boot sequence should show messages similar to the following:
Reading from system configuration file: 'system.txt'
Created LOCAL module Id 0x20
Created LOCAL module Id 0x0
Created LOCAL module Id 0xcf
Created LOCAL module Id 0xef
Created LOCAL module Id 0x4d
Redirect module Id 0x81 to module Id 0x20
Redirect module Id 0xe1 to module Id 0x20
Redirect module Id 0xf1 to module Id 0x20
Redirect module Id 0x8e to module Id 0x20
Redirect module Id 0x4a to module Id 0x20
Redirect module Id 0xdf to module Id 0xef
(2788)gctload: Process (3180)'ssdh.exe' - forked by gctload
(2788)gctload: Process (2588)'tim_nt.exe' - forked by gctload
(2788)gctload: Process (2608)'tick_nt.exe' - forked by gctload
(2788)gctload: Process (1536)'s7_mgt.exe' - forked by gctload
(2788)gctload: Process (3992)'s7_log.exe' - forked by gctload
(2788)gctload: Initialisation complete
S7_MGT Tx: M-I0000-t7680-i0000-fcf-d20-s00-p(24)200000cf70637337332e646331000000
0000000000000010
ssdh: 16 boards
S7_MGT Rx: M-I0000-t3680-i0000-f20-dcf-s00-p(24)200000cf70637337332e646331000000
0000000000000010
S7_MGT Tx: M-I0000-t7681-i0000-fcf-d20-s00-p(26)0003000000007373372e646334000000
00000000000000000004
56

S7_log : mod ID=0xef, options=0xaf0d, max_param_len=320

ssdh[0]: open
ssdh[0]: reset requested
S7_MGT Rx: M-I0000-t3681-i0000-f20-dcf-s00-p(26)0003000000007373372e646334000000
00000000000000000004
SSDH Board Boot Parameters: board_id 0
Product Code: 1
Hardware revision: 1
RAM size: 32M byte
ADDR switch: 3
Number of SPs: 2
Firmware: V1.05
Electronic serial number : 080006009343dcf1
License serial number: 826328000030009c
Board serial number: ME001036
Driver: SubNum:0x5005 State:0xb002 CheckPoint:0x8130
ssdh[0]: code download requested
ssdh[0]: Section download started(00000000 ss7.dc4)
ssdh[0]: Section download complete(906248 bytes)
ssdh[0]: run requested
ssdh[0]: running
ssdh[0]: Checking for more sections
ssdh[0]: Section download started(0000010f ss7.dc4)
ssdh[0]: Section download started(0000020f ss7.dc4)
ssdh[0]: Download completed. Awaiting board active ack
For Dialogic PCI and CompactPCI Boards, there should be an SS7 device. In Windows
2000, right click on My Computer, then choose Manage to open the Computer
Management dialog. Select Device Manager, then choose Show hidden devices from the
View menu. There should be an SS7 device, and you can check if it has started or not.
Note: If an SS7 device does not appear in the list, type net start Septel at the
command line.
At this point, the last thing you should see on the console is S7_MGT Boot Complete as a
final S7_MGT message:
.
.
.
S7_MGT Tx: M-I0000-t7312-i0000-fcf-d22-s00-p(32)00000309000000000000002000000000
00000000000000000000000000000000
S7_MGT Rx: M-I0000-t3312-i0000-f22-dcf-s00-p(32)00000309000000000000002000000000
00000000000000000000000000000000
S7_MGT Tx: M-I0000-t7312-i0000-fcf-d22-s00-p(32)0000022b010000000000002000000000
00000000000000000000000000000000
S7_MGT Rx: M-I0000-t3312-i0000-f22-dcf-s00-p(32)0000022b010000000000002000000000
00000000000000000000000000000000
S7_MGT Tx: M-I0000-t7700-i0000-fcf-d23-s00-p(40)0474004d4d22004d0001000a00020040
011005ef0000000000000000000000000000000000000000
S7L:I0000 M t0e23 i0000 f10 ddf s01
S7_MGT Rx: M-I0000-t3700-i0000-f23-dcf-s00-p(40)0474004d4d22004d0001000a00020040
011005ef0000000000000000000000000000000000000000
S7_MGT Tx: M-I0000-t7701-i0000-fcf-d23-s00-p(64)0000022b00000309000100007fff7fff
071e00004d004d00000000004d008500000000000000000000000000000000000000000000000000
0000000000000000
S7_MGT Rx: M-I0000-t3701-i0000-f23-dcf-s00-p(64)0000022b00000309000100007fff7fff
071e00004d004d00000000004d008500000000000000000000000000000000000000000000000000
0000000000000000
S7_MGT Tx: M-I0000-t7701-i0001-fcf-d23-s00-p(64)000003090000022b000100207fff7fff
071e00004d004d00000000004d008500000000000000000000000000000000000000000000000000

57
0000000000000000
S7_MGT Rx: M-I0000-t3701-i0001-f23-dcf-s00-p(64)000003090000022b000100207fff7fff
071e00004d004d00000000004d008500000000000000000000000000000000000000000000000000
0000000000000000
S7_MGT Boot complete
S7L:I0000 M t0e23 i0000 f10 ddf s03
S7L:I0000 M t0e23 i0000 f10 ddf s05
S7L:I0000 LIU Status : id=0 PCM OK
S7L:I0000 LIU Status : id=0 IN SYNC
S7L:I0000 LIU Status : id=0 AIS CLEARED
S7L:I0000 LIU Status : id=0 REMOTE ALARM CLEARED
S7L:I0000 LIU Status : id=1 PCM OK
S7L:I0000 LIU Status : id=1 IN SYNC
S7L:I0000 LIU Status : id=1 AIS CLEARED
S7L:I0000 LIU Status : id=1 REMOTE ALARM CLEARED
S7L:I0000 M t0e23 i0000 f10 ddf s02
3. Check that all messages on this last screen have a status of 0, indicating success. The status is
indicated as -sXX in each message, where XX is a hexadecimal number.
4. If, instead of the S7_MGT Boot complete message, you receive an S7_MGT: Timeout
occurred message, check that the firmware you have specified in your config.txt file
corresponds to the license button installed on the board.
5. Activate the MTP link(s) using the MTPSL tool (assuming linkset id 0 and link 0):
MTPSL ACT 0 0
If the MTP link is configured properly and activated at the adjacent point code and your
system is properly clocked, you should see messages similar to the ones below. The important
thing to check for is the presence of Destination available.
S7L:I00 MTP Event : linkset_id/link_ref=0000 Changeback
S7L:I00 MTP Event : linkset_id=00 Link set recovered
S7L:I00 MTP Event : linkset_id=00 Adjacent SP accessible
S7L:I00 MTP Event : point code=00000002
Destination available
If no other message appears on the console after a couple of minutes, you can reasonably
assume that your configuration is correct.
3.10.1.2
SIU Systems
For proving the configuration of an SIU-based system, follow the steps described in this section.
This description assumes a single host system connected to a single SIU.
1. Check that your system.txt file on the host system contains all standard LOCAL module
definitions and the following FORK_PROCESS commands:
FORK_PROCESS
FORK_PROCESS
.\S7_LOG.EXE -m0xef
.\RSI.EXE -r.\RSI_LNK.EXE -l1
2. Run GCTLOAD and power up the SIU.

3. Establish the TCP/IP link with the SIU using the following command (where
<SIU_IP_Address> is the actual IP address assigned to the SIU):
58

RSICMD.EXE 0 0xef 0 <SIU_IP_Address> 9000
When the SIU is booted, you should see the following messages on the S7_LOG screen (where
GCTLOAD is running):
S7L:I00 RSI_MSG_LNK_STATUS : Link 0 now down
S7L:I00 RSI_MSG_LNK_STATUS : Link 0 now up
The second message indicates that the host system is able to communicate with the SIU. If the
link remains down, check that all LEDs on the SIU are lit. Also check the IP address of the
SIU by doing a ping to it. If not all the LEDs are lit before establishing the TCP/IP link, it may
indicate a mistake in the configuration of the SIU (config.txt or system settings) or a hardware
problem. See the documentation for the specific SIU model for more information on
diagnosing and solving such problems.
Once the TCP/IP link between the host system and the SIU is established, the SIU will start
activating its MTP links. Messages similar to the following ones should appear on the console:
S7L:I00
S7L:I00
S7L:I00
S7L:I00
S7L:I00
Level 2 State : id=0 INITIAL ALIGNMENT

Level 2 State : id=0 ALIGNED READY
Level 2 State : id=0 IN SERVICE
MTP Event : linkset_id/link_ref=0000 Changeback
MTP Resume, dpc=00000001
The last message indicates that the destination point code (00000001 in this example) is
reachable. If you do not see this and the link is activated at the adjacent point code, check the
config.txt file on the SIU. Start by checking the point codes, the Signaling Link Code (SLC)
and Sub-Service Field (SSF) parameters.
3.10.2
Common Problems and Solutions

The following paragraphs list mistakes that are often made while installing and configuring a
Dialogic Global Call SS7 system. The symptoms are described together with suggested approach
to fix the problem.
3.10.2.1
Dialogic SS7 Server Fails to Start

The Dialogic Global Call SS7 server returns a meaningful error code when it fails to start. The
relevant error codes in this context are given in Table 5.
Table 5. Error Codes for SS7 Server Start Failure

Error Code
Description
0x5001
Error reading configuration; phase A: SYSTEM (gcss7.cfg).
0x5002
Error reading configuration; phase B: SEPTEL (config.txt).
0x5003
Error starting the GCTLOAD program.
0x5007
Failed to attach to GCT messaging environment.
0x5009
Unable to initialize SIU(s) correctly.
0x500a
Error initializing CardController, phase A;

ReserveTimeSlotRange(m_numTS) if needed.

59
Table 5. Error Codes for SS7 Server Start Failure (Continued)

Error Code
0x500b
Description
Error initializing CardController, phase B;
Load DTI, activate links, route CT Bus etc.
0x500c
Failed to create QMsg messaging environment.
0x500d
Error creating final Init thread (Windows only).
0x500e
Timeout waiting for DSS (Dialogic services).
In Windows systems, view the system log using the NT Event Viewer. If there are several error
events, locate the one that happened first; it is likely to be the one with the more precise description
of the failure. Other error events are usually consequences of the first one.
Note:
3.10.2.2
It is always helpful to check the contents of the DlgcS7.log file in case the server fails to start.
Dialogic SS7 Server Consumes 100% of the CPU Cycles

Check that the module ID for the SS7 server is correctly defined as a LOCAL module ID in the
gcss7.cfg file.
3.10.2.3
Dialogic SS7 Server Hangs During Startup

During startup, the SS7 server retrieves the config.txt file from the SIU via ftp. Currently, the
Dialogic Global Call SS7 Software for Linux uses the systems default ftp-client timeout and
retries values. The timeout could be significant, up to three minutes. One of the possible reasons for
ftp to fail and consequently force the SS7 server to wait for a long time is an incorrect IP
configuration setting for the SIU.
If the SIU and the host are in different subnets and the subnet mask or a gateway is not set properly,
the host and the SIU will not be able to communicate with each other. The value of the subnet mask
and a gateway can easily be checked by using telnet to access the SIU and checking the SIUs
configuration. For example:
telnet 111.122.133.144 8100
>cnsyp;
In the resulting display, check that the SUBNET and the GATEWAY values are set correctly.
For details on configuring SIUs and all the MML commands, see the SS7G2x SIU Mode User
Manual, available for download via
http://www.dialogic.com/support/helpweb/signaling/default.htm.
3.10.2.4
SIU Does Not Function Correctly after Modification of config.txt

Proceed as follows:
1. Download the config.txt file from the SIU via ftp using binary file transfer mode.
60

2. Check that the file does not contain any 0x0d symbols, that is, carriage return (<cr>) symbols
that do not have a graphical representation in the ASCII table. If it does, remove all the 0x0d
symbols using a text editor.
3. Upload the corrected config.txt file back to the SIU and restart it.
3.10.2.5
Dialogic SS7 Server Freezes at Startup (Linux Only)

Using the ps -ef command lists the dlgcs7d process as <defunct>, /var/dialogic/log/DlgcS7.log
contains 0 bytes.
This can occur on some Linux builds due to incorrect behavior of the gettimeofday( ) system
function. This issue will be resolved in future releases of the Dialogic Global Call SS7 Software.
Check the time zone setting on your Linux machine as follows:
echo $TZ
If the variable is empty, set the appropriate value before starting the SS7 Server, for example:
export TZ=CST
3.11
Sample Configuration Files

This section contains sample configuration files for various scenarios:
Sample gcss7.cfg Configuration File
Sample system.txt File for a System with a Dialogic SS7SPCI4 Board
Sample config.txt File for a System with Circuits and Signaling on a Dialogic SS7SPCI4
Board
Sample config.txt File for a System with Circuits and Signaling on DTI Trunks
Sample system.txt File for a System with a Dialogic SS7HDP Board
Sample config.txt File for a System with Dialogic SS7HDP Board for Circuits and Signaling
on DTI Trunks
Sample system.txt File for a Single-SIU and Dual-SIU System
Sample config.txt File for a Single-SIU System with One Host
Sample config.txt File for a Single-SIU System with Two Hosts
Sample config.txt File for SIU A in a Dual-Resilient SIU System with a Single Host
Sample config.txt File for SIU B in a Dual-Resilient SIU System with a Single Host
Sample system.txt File for M3UA Configuration
Sample config.txt File for M3UA Configuration
Sample system.txt File for M2PA Configuration
Sample config.txt File for M2PA Configuration
Sample system.txt File for Clear Channel Operation

61
Sample config.txt File for Clear Channel Operation

Sample system.txt File for a Mixed Configuration (SS7 Signaling and Clear Channel)
Sample config.txt File for a Mixed Configuration (SS7 Signaling and Clear Channel)
Sample system.txt File for a Mixed Configuration (Call Control and Transaction Based)
Sample config.txt File for a Mixed Configuration (Call Control and Transaction Based)
Sample system.txt File for Multiple Dialogic SS7 Boards in a System
Sample config.txt File for Multiple Dialogic SS7 Boards in a System
3.11.1
Sample gcss7.cfg Configuration File

The following is an example of a gcss7.cfg file:
################################
# Type of System Configuration #
################################
# Leave commented out or set to "None" when not using Dialogic SS7.
# Depending on the value of this parameter, the sections below, that
# are specific to some configurations (SeptelCard, SIU, SIU.Dual, UserPart)
# will be used or not. The UserPart configuration is used for ISUP/TUP
# only configuration where lower layers are not of concern e.g. SIGTRAN
# configuration.
# Format: String - ["None", "Card", "SIU", "DualSIU", UserPart]
System.Configuration = "None"
##########################################################
# Parameters for the GlobalCall SS7 Call Control Library #
##########################################################
# If defined, this parameter will cause the library logging to be
# activated at the first gc_Open() of an SS7 ciruit and the trace
# file will have the specified name.
# Format: String
Library.LogFile = "ss7.log"
# Logging Level for the library
# Format: String - ["None", "Errors", "All"]
# Default: "Errors" (and Warnings)
Library.LogLevels = "All"
# Maximum size of the library log in kilobytes
# Format: Integer, Default: 200
#Library.LogMaxSize = 200
##################################################
# Parameters for the Dialogic SS7 service/deamon #
##################################################
# Logging Level for the service (DlgcS7.log)
# Format: String - ["None", "Errors", "All"]
# Default: "Errors" (and Warnings)
Service.LogLevels = "All"
# Maximum size of the service log in kilobytes
#Service.LogMaxSize = 200
# Does the service need to start GCTLOAD automatically?
# Format: String - ["Yes", "No"]
Service.GCTLOAD_Control = "No"
62

# Path to GCTLOAD (Used only if GCTLOAD_Control is set to "Yes")

# For Setpel Cards, the parameter defaults to the same path as ConfigDir
# Format: String
#Service.GCTLOAD_Path = "c:\septel"
# GCT-environment module id used by the service
# Format: Integer, Default: 0x4d
Service.ModuleID = 0x4d
# Maximum timeout (in seconds) for server-application keep-alive mechanisme
# Format: Integer; Default: 7; 0 means the mechanisme is off (recommended for Windows)
#Service.WatchDogMaxTime = 8
# Time (in ms) during which to accumulate Circuit Group Supervision Requests
# (reset, block, unblock) for a circuit group.
# Format: Integer - Default: 500
#Service.GroupCommandTimer = 500
#########################################
# Configuration for Septel Card Systems #
#########################################
# Path to the config.txt file
# Format: String
SeptelCard.ConfigDir = "c:\septel"
# Should MTP links be automatically activated ?
# Format: String - ["None", "All"]
SeptelCard.Auto_Links_Activation = "All"
#################################
# Configuration for SIU Systems #
#################################
# ID of this host - Use 0 if only one host accessing the SIU(s)
# Format: Integer
SIU.HostID = 0
# SIU A - IP Address
# Format: String
#SIU.A.IP_Address = "192.168.0.21"
# SIU A - Account to use to connect to SIU when using FTP
# Format: String
#SIU.A.FTP_Account = "ftp"
# SIU A - Password for the FTP account
# Format: String
#SIU.A.FTP_Password = "ftp"
# SIU A - Directory to which to change (in FTP session) in order to get config.txt
# Format: String
#SIU.A.RemoteConfigDir = "."
# Maximum time (in seconds) to wait at startup for an SIU to come on-line before
# considering it as being down.
#SIU.InitTimeout = 10
# Max time (in seconds) to wait for FTP connection while getting config.txt from SIU
# Format: Integer - Deault: 5
#SIU.FTP_Timeout = 5
# Max number of FTP retries while getting config.txt from SIU
#SIU.FTP_Retries = 2

63
############################################################
# Parameters specific to Dual-Resilient SIU Configurations #
############################################################
# SIU B Parameters - See the same parameters for SIU.A
#SIU.B.IP_Address = "192.168.0.22"
#SIU.B.FTP_Account = "ftp"
#SIU.B.FTP_Password = "ftp"
#SIU.B.RemoteConfigDir = "."
# Max time (in seconds) to wait for group (de)activation command
# responses from SIU.
#SIU.Dual.SiuCommandTimeout = 5
# Debounce time (in seconds) for SIU Down indications
#SIU.Dual.SiuUpDebounceTime = 8
# Maximum number of retries for SIU group (de)activation commands
#SIU.Dual.MaxCmdRetries = 5
#############################################
# Parameters that are related to config.txt #
#############################################
# MTP Link source, link ID must match the value in config.txt.
# MtpLink <link_id> <"link_source">
# Circuit Group configuration, Group ID must match the value in config.txt.
# CGrp <gid> <"trunk_name"> [<base_TS> [<"Pref_SIU">]]
#
# End of gcss7.cfg
#
3.11.2
Sample system.txt File for a System with a Dialogic

SS7SPCI4 Board
The following is an example of a system.txt file for a system that includes a Dialogic SS7 Board,
in this case, the Dialogic SS7SPCI4 Board:
*
* Sample system.txt for Dialogic GC/SS7 on SS7SPCI4 system
*
* Modules running on the host:
*
LOCAL 0x00 * Timer Task
LOCAL 0x20 * ssd - Board Interface task
LOCAL 0x4d * Global Call SS7 Service
LOCAL 0xcf * s7_mgt
LOCAL 0xef * s7_log
*
* Modules running on the board (all redirected via ssd):
*
REDIRECT 0x10 0x20 * PCM/SCbus/Clocking control module
REDIRECT 0x71 0x20 * MTP2 module
REDIRECT 0x22 0x20 * MTP3 module
REDIRECT 0x23 0x20 * ISUP module.
REDIRECT 0x4a 0x20 * TUP/NUP module
64

REDIRECT 0x8e 0x20 * On-board management task

*
* Redirection of status:
*
REDIRECT 0xdf 0x4d * LIU/MTP2 status messages to DlgcS7
*
* Now start-up all local tasks:
*
FORK_PROCESS .\SSDS.EXE -d
FORK_PROCESS .\TIM_NT.EXE
FORK_PROCESS .\TICK_NT.EXE
FORK_PROCESS .\S7_MGT.EXE -d
FORK_PROCESS .\S7_LOG.EXE -m0xef
*
* End of file
*
3.11.3
Sample config.txt File for a System with Circuits and

Signaling on a Dialogic SS7SPCI4 Board
The following is an example of a config.txt file for a system that terminates trunks containing SS7
links and ISUP circuits on a Dialogic SS7 Board, in this example, the Dialogic SS7SPCI4
Board:
*
* Sample SS7SPCI4 Protocol configuraiton file (config.txt)
* for Dialogic GC/SS7.
* - 1 SS7SPCI4 in CTBus master mode
* - 2 circuit groups on the first 2 SS7SPCI4 trunks.
* - one SS7 link on timeslot 16 of each trunk
*
*
* Configure individual boards:
* For SS7SPCI4 / SS7SPCI2S boards:
* SEPTELPCI_BOARD <board_id> <flags> <code_file> <run_mode>
SEPTELPCI_BOARD 0 0x0043 ss7.dc3 ISUP
*
*
* Configure individual E1/T1 interfaces:
* LIU_CONFIG <board_id> <liu_id> <liu_type> <line_code> <frame_format> <crc_mode>
LIU_CONFIG 0 0 5 1 1 1
*
*
* MTP Parameters :
* MTP_CONFIG <reserved> <reserved> <options>
MTP_CONFIG 0 0 0x00000000
*
* Define linksets :
* MTP_LINKSET <linkset_id> <adjacent_spc> <num_links> <flags> <local_spc> <ssf>
MTP_LINKSET 0 1 2 0x0000 2 0x8
*
* Define signaling links :
* MTP_LINK <link_id> <linkset_id> <link_ref> <slc> <board_id> <blink>
*
<stream> <timeslot> <flags>
MTP_LINK 0 0 0 0 0 0 0 16 0x0006
MTP_LINK 1 0 1 1 0 1 1 16 0x0006
*
* Define a route for each remote signaling point:
* MTP_ROUTE <dpc> <linkset_id> <user_part_mask>
MTP_ROUTE 1 0 0x0020
*
*

65
* ISUP Parameters:
*
* Configure ISUP module:
* ISUP_CONFIG <reserved> <reserved> <user_id> <options> <num_grps> <num_ccts>
ISUP_CONFIG 0 0 0x4d 0x0474 4 64
*
*
ISUP_CFG_CCTGRP 0 1 0x01 0x01 0x7fff7fff 0x001c 0 0x4d 2 0x8 0 0x00
*
* End of file
*
Note:
The accompanying gcss7.cfg file should contain lines that correspond to the ISUP_CFG_CCTGRP
commands above, for example:
CGrp 0 dkB1
CGrp 1 dkB2
3.11.4
Sample config.txt File for a System with Circuits and

Signaling on DTI Trunks
The following is an example of a config.txt file for a system that includes a Dialogic SS7 Board,
in this case the Dialogic SS7SPCI4 Board, and that terminates trunks containing SS7 signaling
and ISUP circuits on the DTI trunks of a Dialogic Digital Network Interface Board:
*
* Sample SS7SPCI4 Protocol configuraiton file (config.txt)
* for Dialogic GC/SS7.
* - 1 SS7SPCI4 in CTBus slave mode
* - 2 circuit groups on Dialogic DTI trunks (e.g. DM/V1200-E1-PCI)
* - 2 SS7 links routed over the CTBus from timeslot 16 of Dialogic DTI trunks
* (a clear channel load is required for this, e.g. ml1_qs_ts16.pcd)
*
*
* For SS7SPCI4 / SS7SPCI2S boards:
SEPTELPCI_BOARD 0 0x00c2 ss7.dc3 ISUP
*
*
* MTP Parameters :
*
* Define linksets :
*
* Define signaling links :
*
MTP_LINK 0 0 0 0 0 0 0x83 0 0x0006
MTP_LINK 1 0 1 1 0 1 0x83 1 0x0006
*
*
*
* ISUP Parameters:
66

*
*
*
*
* End of file
*
Note:
The accompanying gcss7.cfg file should contain lines that correspond to the MTP_LINK
MtpLink 0 dtiB1T31
MtpLink 1 dtiB2T31
and lines that correspond to the ISUP_CFG_CCTGRP commands above, for example:
CGrp 0 dtiB1
CGrp 1 dtiB2
3.11.5
Sample system.txt File for a System with a Dialogic

SS7HDP Board
The following is an example of a system.txt file for a system that includes a Dialogic SS7 Board,
in this case, the Dialogic SS7HDP Board:
********************************************************************
*
* Example System Configuration File (system.txt) for use with the
* Windows Development Package for SS7 Boards
*
* Edit this file to reflect your configuration.
*
********************************************************************
*
* Essential modules running on host:
*
LOCAL
0x20
* ssd/ssds/ssdh - Board interface task
LOCAL
0x00
* tim_nt - Timer task
*
* Optional modules running on the host:
*
LOCAL
0xcf
* s7_mgt - Management/config task
LOCAL
0xef
* s7_log - Display and logging utility
LOCAL
0x4d
* GCSS7
*
* Modules that optionally run on the host
*
*LOCAL
0x23
* ISUP module
*LOCAL
0x4a
* TUP module
*LOCAL
0x33
* SCCP module
*LOCAL
0x14
* TCAP module
*LOCAL
0x22
* MTP3 module
*
* Essential modules running on the board (all redirected via ssd):
*
*REDIRECT
0x71
0x20
* MTP2 module (except SS7HD boards)
REDIRECT
0x81
0x20
* MTP2 module_id for SP 0 (SS7HD boards only)
REDIRECT
0x91
0x20
REDIRECT
0xe1
0x20

67
REDIRECT
0xf1
0x20
REDIRECT
0x10
0x20
* CT bus/Clocking control module
REDIRECT
0x8e
0x20
* On-board management module
*
* Modules that optionally run on the board (all redirected via ssd):
*
REDIRECT
0x23
0x20
* ISUP module
REDIRECT
0x4a
0x20
* TUP module
REDIRECT
0x33
0x20
* SCCP module
REDIRECT
0x14
0x20
* TCAP module
REDIRECT
0x22
0x20
* MTP3 module
*
* Redirection of status indications:
*
REDIRECT
0xdf
0xef
* LIU/MTP2 status messages -> s7_log
*REDIRECT
0xdf
0x4d
* LIU/MTP2 status messages -> GCSS7
*REDIRECT
0xef
0x4d
* trace messages -> GCSS7
*
*
(For PCCS6 start-up use ssd.exe and ssd_poll.exe,
*
for SPCI4/SPCI2S/CPM8 start-up use ssds.exe and
*
for SS7HD boards use ssdh.exe)
*
* FORK_PROCESS ssd.exe
* FORK_PROCESS ssd_poll.exe
*FORK_PROCESS
ssds.exe -d
FORK_PROCESS
ssdh.exe -d
FORK_PROCESS
tim_nt.exe
FORK_PROCESS
tick_nt.exe
FORK_PROCESS
s7_mgt.exe -d -i0x4d
FORK_PROCESS
s7_log.exe
*
*
********************************************************************************
3.11.6
Sample config.txt File for a System with Dialogic SS7HDP

Board for Circuits and Signaling on DTI Trunks
The following is an example of a config.txt file for a system that includes a Dialogic SS7HDP
Board for circuits and signaling on Dialogic DMV Boards (DTI trunks):
********************************************************************************|
*
* For SPCI4 / SPCI2S boards:
*SEPTELPCI_BOARD 0 0x0042 ss7.dc3 MTP
*
* SEPTELCP_BOARD <board_id> <flags> <code_file>
SS7_BOARD 0 SS7HDP 0X0042 ss7.dc4 ISUP * Master, Clk from OSC
*
MTP_CONFIG 0 0 0x000040000
MTP_LINKSET 0 777 2 0x0000 555 0x08* loopback - Septel LIU ID 2
MTP_LINKSET 1 555 2 0x0000 777 0x08* loopback - Septel LIU ID 3
68

* (Note: For Septel ISA (PCCS6) boards the first LIU port is stream=16
* whilst for Septel cP / PCI boards the first LIU port is stream=0)
*
MTP_LINK 0 0 0 0 0 0-0 0x90
0
0x0006 * DM3 dtiB1 - to be routed over CT-Bus
MTP_LINK 1 1 0 0 0 1-0 0x90
0
0x0006 * DM3 dtiB2 - to be routed over CT-Bus
*MTP_ROUTE
222
0x0020
* ISUP_CONFIG <reserved> <reserved> <reserved> <options> <num_grps> <num_ccts>

ISUP_CONFIG 0 0 0x4d 0x0475 4 128
*
*
ISUP_CFG_CCTGRP 0 777 0x01 0 0x7fff7fff 0x071e 0 0x4d 555 0x8 0 0
ISUP_CFG_CCTGRP 1 555 0x01 31 0x7fff7fff 0x071e 0 0x4d 777 0x8 0 0
3.11.7
Sample system.txt File for a Single-SIU and Dual-SIU

System
The following is an example of a system.txt file for a single or a dual Dialogic SS7G21 SIU
system application host:
*
* Multiple application hosts can use the same system.txt file when connecting to a single
* SIU unit
* Module Id's running locally on the host machine:
*
LOCAL 0x00 * timer Module Id
LOCAL 0xb0 * rsi Module Id
*
* Redirect modules running on the SIU to RSI:
*
REDIRECT 0x20 0xb0 * SSD module Id
REDIRECT 0xdf 0xb0 * SIU_MGT module Id
REDIRECT 0x22 0xb0 * MTP3 module Id
REDIRECT 0x32 0xb0 * RMM module Id
REDIRECT 0x23 0xb0 * ISUP module Id
REDIRECT 0x4a 0xb0 * TUP/NUP module Id
*
REDIRECT 0xef 0x4d * s7_log to DlgcS7.log
*
* Now start-up the Host tasks ....
*
FORK_PROCESS tim_nt.exe
FORK_PROCESS tick_nt.exe
FORK_PROCESS .\rsi.exe -r.\rsi_lnk.exe -l1
*
* End of file
*

69
3.11.8
Sample config.txt File for a Single-SIU System with One

Host
The following is an example of a config.txt file for a single Dialogic SS7G21 SIU system with
one application host:
*
* SS7G21 SIU Protocol Configuration File (config.txt)
* Refer to the SS7G21 SIU Developer's Manual.
*
*
* SIU commands:
*
* Define the number of hosts that this SIU will connect to:
* SIU_HOSTS <num_hosts>
SIU_HOSTS 1
*
*
* Set physical Interface Parameters:
* SS7_BOARD <bpos> <board_type> <flags>
SS7_BOARD 1 SPCI2S 0x0041
*
* LIU_CONFIG <port_id> <pcm> <liu_type> <line_code> <frame_format> <crc_mode> <syncpri>
LIU_CONFIG 0 1-3 5 1 1 1 1
LIU_CONFIG 1 1-4 5 1 1 1 2
*
*
* MTP Parameters:
* MTP_CONFIG <reserved1> <reserved2> <options>
MTP_CONFIG 0x0 0x0 0x0000
*
* Define linksets:
*
* Define signaling links:
* MTP_LINK <link_id> <linkset_id> <link_ref> <slc> <bpos> <blink>
*
<bpos2> <stream> <timeslot> <flags>
MTP_LINK 0 0 0 0 1 0 1 2 16 0x0006
MTP_LINK 1 0 1 1 1 1 1 3 16 0x0006
*
* MTP_ROUTE <dpc> <linkset_id> <user_part_mask> [<flags> <second_ls> <pc_mask>]
*
*
* ISUP Parameters:
* ISUP_CONFIG <local_pc> <ssf> <user_id> <options> <num_grps> <num_ccts>
*
*
<host_id> <user_id> <opc> <ssf> <variant> <options2>
ISUP_CFG_CCTGRP 0 2 0x01 0x01 0x7fff7fff 0x0003 0 0x4d 1 0x08 0 0
*
* End of file
*
Note:
The accompanying gcss7.cfg file should contain lines corresponding to the ISUP_CFG_CCTGRP
CGrp 0 dtiB1
CGrp 1 dtiB2
70

3.11.9
Sample config.txt File for a Single-SIU System with Two

Hosts
The following is an example of a config.txt file for a single Dialogic SS7G221 SIU system with
two application hosts:
*
*
*
* SIU commands:
*
SIU_HOSTS 2
*
*
*
LIU_CONFIG 0 1-3 5 1 1 1 1
LIU_CONFIG 1 1-4 5 1 1 1 2
*
*
* MTP Parameters:
*
* Define linksets:
*
*
MTP_LINK 0 0 0 0 1 0 1 2 16 0x0006
MTP_LINK 1 0 1 1 1 1 1 3 16 0x0006
*
* MTP_ROUTE <dpc> <linkset_id> <user_part_mask> [<flags> <second_ls> [<pc_mask>]]
*
*
* ISUP Parameters:
*
*
*
* End of file
*
Note:
The accompanying gcss7.cfg file for host 0 should contain the following lines:
SIU.HostID = 0
CGrp 0 dtiB1

71
and the accompanying gcss7.cfg file for host 1 should contain the following lines:
SIU.HostID = 1
CGrp 1 dtiB1
3.11.10
Sample config.txt File for SIU A in a Dual-Resilient SIU

System with a Single Host
The following is an example of a config.txt file for SIU A in a dual-resilient Dialogic SS7G21
SIU system with a single host:
*
*
*
* SIU commands:
*
SIU_HOSTS 1
*
* Define the network address of the partner SIU (dual operation only):
* SIU_REM_ADDR <remote_address>
SIU_REM_ADDR 192.168.0.2
*
*
SS7_BOARD 1 SPCI4 0x0041
*
LIU_CONFIG 0 1-1 5 1 1 1 1
LIU_CONFIG 0 1-2 5 1 1 1 0
LIU_CONFIG 1 1-4 5 1 1 1 2
*
*
* MTP Parameters:
*
* Define linksets:
* Inter-SIU linkset:
*
*
MTP_LINK 0 0 0 0 1 0 1 0 16 0x0006
MTP_LINK 1 1 0 0 1 1 1 3 16 0x0006
*
MTP_ROUTE 2 0 0x0020 0x0001 1
*
*
* ISUP Parameters:
*
72


*
*
*
* Cross Connections (control the connection of voice channels through
* the SIU):
* STREAM_XCON <bpos> <stream_a> <stream_b> <mode>
*
<ts_mask> <pattern>
STREAM_XCON 1 0 1 3 0xfffefffe 0
*
* End of file
*
Note:
CGrp 0 dtiB1 1 SIUA
CGrp 1 dtiB2 1 SIUB
3.11.11
Sample config.txt File for SIU B in a Dual-Resilient SIU

System with a Single Host
The following is an example of a config.txt file for SIU B in a dual-resilient Dialogic SS7G21 SIU
system with a single host:
*
*
* SIU commands:
*
SIU_HOSTS 1
*
* Define the network address of the partner SIU (dual operation only):
* SIU_REM_ADDR <remote_address>
SIU_REM_ADDR 192.168.0.1
*
*
SS7_BOARD 1 SPCI4 0x0041
*
LIU_CONFIG 0 1-1 5 1 1 1 1
LIU_CONFIG 0 1-2 5 1 1 1 0
LIU_CONFIG 1 1-4 5 1 1 1 2
*
*
* MTP Parameters:
*
* Define linksets:
* Inter-SIU linkset:
*

73

*
MTP_LINK 0 0 0 1 1 0 1 0 16 0x0006
MTP_LINK 1 1 0 0 1 1 1 3 16 0x0006
*
MTP_ROUTE 2 0 0x0020 0x0001 1
*
*
* ISUP Parameters:
*
*
*
*
* Cross Connections (control the connection of voice channels through
* the SIU):
* STREAM_XCON <bpos> <stream_a> <stream_b> <mode>
*
<ts_mask> <pattern>
STREAM_XCON 1 0 1 3 0xfffefffe 0
*
* End of file
*
Note:
CGrp 0 dtiB1 1 SIUA
CGrp 1 dtiB2 1 SIUB
3.11.12
Sample system.txt File for M3UA Configuration

The following is an example of a system.txt file for an M3UA configuration:
*
* Essential Protocol modules running on the host:
*
LOCAL 0x00 * tim_nt - Timer task
LOCAL 0xcf * s7_mgt - Management/config task
LOCAL 0xc2 * mbm - Management task
LOCAL 0xd0 * SCTPD module
*
LOCAL 0xd1 * SCTP module
LOCAL 0xd2 * M3UA module
LOCAL 0x23 * ISUP
LOCAL 0x4d * GC SS7 Server application
*
*
LOCAL 0xef * s7_log module
*
REDIRECT 0x22 0xd2 * MTP3 -> M3UA
*
*
74

FORK_PROCESS sctpd.exe
FORK_PROCESS sctp.exe
*
FORK_PROCESS m3ua_nt.exe -t
FORK_PROCESS isp_nt.exe -t
FORK_PROCESS mbm.exe -d
FORK_PROCESS s7_log.exe -m0xef
FORK_PROCESS s7_mgt.exe -d
*
* End of file
3.11.13
Sample config.txt File for M3UA Configuration

The following is an example of a config.txt file for an M3UA configuration:
********************************************************************************
*
* Protocol Configuration File (config.txt) for use with
* SS7 Boards.
*
* File generated by SS7Cfg V1.00-01
*
********************************************************************************
*
*
*
CNSYS:IPADDR=172.28.148.248;
*
SNSLI:SNLINK=1,IPADDR=172.28.148.190,HPORT=2905,PPORT=2905,SNEND=S,SNTYPE=m3ua;
SNSLI:SNLINK=2,IPADDR=172.28.148.190,HPORT=2906,PPORT=2906,SNEND=S,SNTYPE=m3ua;
*
SNAPI:AS=1,OPC=101,RC=1,TRMD=LS;
SNAPI:AS=2,OPC=102,RC=2,TRMD=LS;
*
SNRAI:RAS=1,RC=1,DPC=1;
SNRAI:RAS=2,RC=2,DPC=2;
*
SNALI:SNAL=1,RAS=1,SNLINK=1;
SNALI:SNAL=2,RAS=2,SNLINK=2;
*
SNLBI:SNLB=1,AS=1,RAS=1;
SNLBI:SNLB=2,AS=2,RAS=2;
*
* ISUP parameters:
* Configure ISUP module
* ISUP_CONFIG <reserved> <reserved> <user_id> <options> <num_grps> <num_ccts> [<partner_id>]
ISUP_CONFIG 0 0 0x4d 0x0414 2 64 *$ num_grps_auto=y num_ccts_auto=y
*
*
ISUP_CFG_CCTGRP 0 1 0x01 0x01 0x7fff7fff 0x249001c 0 0x4d 101 0x8 0x01 0x00d0 *$ conform=ISUP
ISUP_CFG_CCTGRP 1 2 0x01 0x21 0x7fff7fff 0x249001c 0 0x4d 102 0x8 0x01 0x00d0 *$ conform=ISUP
*
ISUP_TRACE 0x3f 0x7f 0xffff
********************************************************************************
3.11.14
Sample system.txt File for M2PA Configuration

The following is an example of a system.txt file for an M2PA configuration:

75
********************************************************************************
*
* Example System Configuration File (system.txt) for use with
* the Linux Development Package for SS7 Boards
*
*
********************************************************************************
*
*
*LOCAL
0x20
LOCAL
0x00
* tim_xxx - Timer task
*
*
LOCAL
0xcf
LOCAL
0xc2
* mbm module
LOCAL
0xef
LOCAL
0x2d
* upe - Example user part task
LOCAL
0x4d
* GC SS7
*
* Modules that optionally run on the host:
*
LOCAL
0xd0
*SCTPD
LOCAL
0xd1
*SCTPD
LOCAL
0xc1
*M2PA
LOCAL
0x23
* ISUP module
LOCAL
0x22
* MTP3 module
*
*
REDIRECT
0xdf
0xef
*
*
(For PCCS6 start-up use ssd,
*
for SPCI4/SPCI2S/CPM8 start-up use ssds and
*
for SS7HD boards use ssdh)
*
FORK_PROCESS
tim_nt.exe
FORK_PROCESS
tick_nt.exe
FORK_PROCESS
sctpd.exe
FORK_PROCESS
sctp.exe
FORK_PROCESS
m2pa_nt.exe -t
FORK_PROCESS
mbm.exe
FORK_PROCESS
mtp_nt.exe -t
FORK_PROCESS
isp_nt.exe -t
FORK_PROCESS
s7_mgt.exe
FORK_PROCESS
s7_log.exe
*
*
********************************************************************************
3.11.15
Sample config.txt File for M2PA Configuration

The following is an example of a config.txt file for an M2PA configuration:
********************************************************************************
*
* Example Protocol Configuration File (config.txt) for use with
* SS7 Boards.
*
* This file needs to be modified to suit individual circumstances.
* Refer to the relevant Programmer's Manuals for further details.
76

*
********************************************************************************
*
cnsys:ipaddr=146.152.98.12,per=0;
snsli:snlink=1,ipaddr=146.152.98.15,snend=s,sntype=m2pa,m2pa=1,pport=3565;
*
* MTP parameters:
*
*
* Define linksets:
MTP_LINKSET 0 2 2 0x0000 1 0x08
*
*
* Note 1: For PCCS6 boards the first LIU port is stream=16 whilst for other
* boards the first LIU port is stream=0.
* Note 2: The SS7HD board requires a compound parameter for blink of the form
* sp_id-sp_channel.
*
MTP_LINK 0 0 0 0 0 1 0 0 0x80000006
*
* Define any user provided Layer 4 protocol:
* MTP_USER_PART <service_ind> <module_id>
*MTP_USER_PART 0x0a 0x2d
*
*
* ISUP parameters:
*
*
*
*
********************************************************************************
3.11.16
Sample system.txt File for Clear Channel Operation

The following is an example of the minimum configuration required in the system.txt file for clear
channel operation (i.e, when there is no SS7 signaling supported):
*
*
LOCAL
0x20
LOCAL
0x00
*
*
LOCAL
0xcf
LOCAL
0xef
LOCAL
0x4d
* GCSS7
*

77
*
*
REDIRECT
0x10
0x20
REDIRECT
0x8e
0x20
*
*
*
*REDIRECT
0xdf
0xef
*REDIRECT
0xdf
0x4d
*REDIRECT
0xef
0x4d
*
*
*
*
*
* FORK_PROCESS ssdh.exe
FORK_PROCESS
./ssds -d
FORK_PROCESS
./tim_lnx
FORK_PROCESS
./tick_lnx
FORK_PROCESS
./s7_mgt -d -i0x4d
FORK_PROCESS
./s7_log
* FORK_PROCESS upe.exe
3.11.17
Sample config.txt File for Clear Channel Operation

In clear channel mode, the minimum configuration required is the board and LIU configuration in
the config.txt file, as shown in the example below for a Dialogic SS7HDC Board:
* For SS7HD cP boards:
* SS7_BOARD <board_id> <board_type> <flags> <code_file> <run_mode>
SS7_BOARD 0 SS7HDC 0x00C2 ss7.dc4 dti
*
3.11.18
Sample system.txt File for a Mixed Configuration (SS7

Signaling and Clear Channel)
The following is an example of a system.txt file for a mixed configuration (SS7 signaling on a
Dialogic SS7HDCS8 Board and clear channel on a Dialogic SS7HDCN16 Board):
********************************************************************
*
*
*
********************************************************************
*
*
78

LOCAL
0x20
LOCAL
0x00
*
*
LOCAL
0xcf
LOCAL
0xef
*LOCAL
0x2d
* upe - Example user part task
LOCAL
0x4d
* GC SS7 Service
*
*
*LOCAL
0x23
* ISUP module
*LOCAL
0x4a
* TUP module
*LOCAL
0x33
* SCCP module
*LOCAL
0x14
* TCAP module
*LOCAL
0x22
* MTP3 module
*
*
REDIRECT
0x71
0x20
REDIRECT
0x81
0x20
* MTP2 module_id for SP 0 (SS7HD boards
REDIRECT
0x91
0x20
REDIRECT
0xe1
0x20
REDIRECT
0xf1
0x20
REDIRECT
0x10
0x20
REDIRECT
0x8e
0x20
*
*
only)
only)
only)
only)
REDIRECT
0x23
0x20
* ISUP module
* REDIRECT
0x4a
0x20
* TUP module
* REDIRECT
0x33
0x20
* SCCP module
* REDIRECT
0x14
0x20
* TCAP module
REDIRECT
0x22
0x20
* MTP3 module
*
*
REDIRECT
0xdf
0x4d
* REDIRECT
0xef
0x4d
* other/trace -> GCSS7
REDIRECT
0xdf
0xef
*
*
*
*
*
* FORK_PROCESS ssds.exe
FORK_PROCESS ssdh.exe -d
FORK_PROCESS s7_mgt.exe -d -i0x4d
FORK_PROCESS s7_log.exe
*
*
********************************************************************************

79
3.11.19
Sample config.txt File for a Mixed Configuration (SS7

Signaling and Clear Channel)
The following is an example of a config.txt file for a mixed configuration (SS7 signaling on a
Dialogic SS7HDCS8 Board and clear channel on a Dialogic SS7HDCN16 Board):
********************************************************************
* Example Protocol Configuration File (config.txt) for use with
* SS7 Boards.
*
* Boards supported are PCCS6, SPCI4, SPC2S, CPM8 and the SS7HD range.
* (note, not all boards are supported on all operating systems).
*
* This file needs to be modified to suit individual circumstances.
* Refer to the relevant Programmer's Manuals for further details.
*
********************************************************************************
* For SS7HD cP boards:
SS7_BOARD 0 SS7HDC 0x0042 ss7.dc4 ISUP * Master -- HDC
SS7_BOARD 1 SS7HDC 0x00C2 ss7.dc4 dti
* LIU_CONFIG <board_id> <liu_id> <liu_type> <line_code> <frame_format>
*
<crc_mode>
LIU_CONFIG 1 10 4 4 7 4
LIU_CONFIG 1 11 4 4 7 4
LIU_CONFIG 1 12 4 4 7 4
LIU_CONFIG 1 13 4 4 7 4
LIU_CONFIG 1 14 4 4 7 4
LIU_CONFIG 1 15 4 4 7 4
MTP_CONFIG 0 0 0x00040f00
MTP_LINKSET 0 777 1 0x0000 555 0x03 * Loopback - HDC 1
MTP_LINKSET 1 555 1 0x0000 777 0x03 * Loopback - HDC 2
*
* boards the first LIU port is stream=0.
* sp_id-sp_channel.
*
* For SS7HD boards:
MTP_LINK 0 0 0 0 0 0-0 0
24 0x0006 * LIU 0, signalling on TS 24, for loopback
MTP_LINK 1 1 0 0 0 0-1 1
24 0x0006 * LIU 1, signalling on TS 24, for loopback
*
80


MTP_ROUTE 777 0 0x0020 0x0000 0
MTP_ROUTE 555 1 0x0020 0x0000 0
*
* ISUP parameters:
*
*
*
ISUP_CFG_CCTGRP 0 777 0x01 0x00 0x7fffff 0x0000401c 0 0x4d 555 0x3 2
ISUP_CFG_CCTGRP 1 555 0x01 0x19 0x7fffff 0x0000401c 0 0x4d 777 0x3 2
3.11.20
0x00
0x00
Sample system.txt File for a Mixed Configuration (Call

Control and Transaction Based)
The following is an example of a system.txt file for a mixed ISUP (Global Call SS7) and transaction
based (SCCP/TCAP/INAP) configuration.
* Module Id's running locally on the host machine:
*
LOCAL 0x00 * timer Module Id
LOCAL 0xb0 * rsi Module Id
LOCAL 0x5d * INAP application
*
*Redirect modules running on the SIU to RSI:
*
REDIRECT 0x20 0xb0 * SSD module Id
REDIRECT 0xdf 0xb0 * SIU_MGT module Id
REDIRECT 0x22 0xb0 * MTP3 module Id
REDIRECT 0x32 0xb0 * RMM module Id
REDIRECT 0x23 0xb0 * ISUP module Id
REDIRECT 0x33 0xb0 * SCCP module Id
REDIRECT 0x14 0xb0 * TCAP module Id
REDIRECT 0x35 0xb0 * INAP module Id
REDIRECT 0x4a 0xb0 * TUP/NUP module Id
*
REDIRECT 0xef 0x4d * s7_log to DlgcS7.log
*
*Now start-up the Host tasks ....
*
FORK_PROCESS .\rsi.exe -r.\rsi_lnk.exe -l1
*
* End of file
*
3.11.21
Sample config.txt File for a Mixed Configuration (Call

Control and Transaction Based)
The following is an example of a config.txt file for a mixed ISUP (Global Call SS7) and transaction
based (SCCP/TCAP/INAP) configuration.

81
***
***
*
SIU_HOSTS <num_hosts> <backup_mode>
SIU_HOSTS
1
0
***
*
LIU_CONFIG 0 1-3 5 1 1 1 1
LIU_CONFIG 1 1-4 5 1 1 1 2
**
* MTP Parameters:
*
* Define linksets:
*
MTP_LINKSET [<nc_id>] <linkset_id> <adjacent_spc> <num_links> <flags> <local_spc> <ssf>
MTP_LINKSET NC0 0 2 2 0x0000 1 0x8
*
* <bpos2> <stream> <timeslot> <flags>
MTP_LINK 0 0 0 0 1 0 1 2 16 0x0006
MTP_LINK 1 0 1 1 1 1 1 3 16 0x0006
*
*MTP_ROUTE [<nc_id>] <route_id> <dpc> <linkset_id> <user_part_mask> <flags> <second_ls>
<reserved>
MTP_ROUTE NC0 0 2 0 0x0028 0 0 0
**
* ISUP Parameters:
*
* ISUP_CFG_CCTGRP [<nc_id>] <gid> <dpc> <base_cic> <base_cid> <cic_mask> <options>
* <host_id> <user_id> <opc> <ssf> <variant> <options2>
*
* SCCP_CONFIG <local_spc> <ssf> <options>
SCCP_CONFIG 1 0x8 0x0106
*
Define SCCP Remote Signaling Points
*
SCCP_SSR [<nc_id>] <ssr_id> RSP <remote_spc> <rsp_flags> [<pc_mask>]
SCCP_SSR
NC0
1
RSP
2
0
*
*
Define SCCP Local Sub-Systems
*
SCCP_SSR [<nc_id>] <ssr_id> LSS <local_ssn> <module_id> <lss_flags> <protocol>
*
SCCP_SSR
NC0
2
LSS
0xfc
0x5d
0
INAP
*
*
Define SCCP Remote Sub-Systems
*
SCCP_SSR [<nc_id>] <ssr_id> RSS <remote_spc> <remote_ssn> <rss_flags>
*
SCCP_SSR
NC0
3
RSS
2
0xfa
0
*
Configure TCAP
*
TCAP_CONFIG <base_ogdlg_id> <nog_dialogues> <base_icdlg_id> <nic_dialogues> <options>
<dlg_hunt> <addr format>
*
TCAP_CONFIG
0
2000
0x8000
2000
0
0
*
Configure INAP
*
INAP_CONFIG <options>
82

*
INAP_CONFIG
*
* End of file
*
3.11.22
0x0002
Sample system.txt File for Multiple Dialogic SS7 Boards in

a System
The following is an example of a system.txt file for two Dialogic SS7HDP Boards, each
supporting two link sets:
********************************************************************
*
*
*
********************************************************************
*
*
LOCAL
0x20
LOCAL
0x00
*
*
LOCAL
0xcf
LOCAL
0xef
LOCAL
0x4d
* GCSS7
*
*
LOCAL
0x23
* ISUP module
*LOCAL
0x4a
* TUP module
*LOCAL
0x33
* SCCP module
*LOCAL
0x14
* TCAP module
LOCAL
0x22
* MTP3 module
*
*
*REDIRECT
0x71
0x20
REDIRECT
0x81
0x20
REDIRECT
0x91
0x20
REDIRECT
0xe1
0x20
REDIRECT
0xf1
0x20
REDIRECT
0x10
0x20
REDIRECT
0x8e
0x20
*
*
*REDIRECT
0x23
0x20
* ISUP module
REDIRECT
0x4a
0x20
* TUP module
REDIRECT
0x33
0x20
* SCCP module
REDIRECT
0x14
0x20
* TCAP module
*REDIRECT
0x22
0x20
* MTP3 module
*
*
REDIRECT
0xdf
0xef
*REDIRECT
0xdf
0x4d
*REDIRECT
0xef
0x4d
*

83

*
*
*
*
* FORK_PROCESS ssds.exe -d
FORK_PROCESS
ssdh.exe
FORK_PROCESS
tim_nt.exe
FORK_PROCESS
tick_nt.exe
FORK_PROCESS
isp_nt.exe -t
FORK_PROCESS
mtp_nt.exe -t
FORK_PROCESS
s7_mgt.exe -d -i0x4d
FORK_PROCESS
s7_log.exe
*
*
********************************************************************************
3.11.23
Sample config.txt File for Multiple Dialogic SS7 Boards in

a System
The following is an example of a config.txt file for two Dialogic SS7HDP Boards, each
supporting two link sets:
********************************************************************************
*
* Protocol Configuration File (config.txt) for use with
* SS7 Boards.
*
* File generated by SS7Cfg V1.01
*
********************************************************************************
*
* For PCCS6 boards:
* PCCS6_BOARD <port_id> <board_id> <num_pcm> <flags> <code_file>
* For SPCI4, SPCI2S, CPM8, SS7HD PCI (SS7HDP) and SS7HD cP (SS7HDC) boards:
SS7_BOARD 0 SS7HDP 0x0042 ss7.dc4 MTP2 *$ hw_type=SS7HDP4TE
SS7_BOARD 1 SS7HDP 0x00c3 ss7.dc4 MTP2 *$ hw_type=SS7HDP4TE
*
* LIU_CONFIG <board_id> <liu_id> <liu_type> <line_code> <frame_format>
*
<crc_mode> [<build_out>]
*
*
* MTP parameters:
*
*
* Define linksets:
MTP_LINKSET 0 777 1 0x0000 555 0x8
84

MTP_LINKSET 1 555 1 0x0000 777 0x8

MTP_LINKSET 2 888 1 0x0000 666 0x8
MTP_LINKSET 3 666 1 0x0000 888 0x8
*
*
*
boards the first LIU port is stream=0.
*
sp_id-sp_channel.
MTP_LINK 0 0 0 0 0 0-0 0 16 0x0006
MTP_LINK 1 1 0 0 0 0-1 1 16 0x0006
MTP_LINK 2 2 0 0 1 0-0 0 16 0x0006
MTP_LINK 3 3 0 0 1 0-1 1 16 0x0006
*
* MTP_ROUTE <dpc> <norm_ls> <user_part_mask> <flags> <second_ls>
MTP_ROUTE 777 0 0x0020 0x0000 0
MTP_ROUTE 555 1 0x0020 0x0000 0
MTP_ROUTE 888 2 0x0020 0x0000 0
MTP_ROUTE 666 3 0x0020 0x0000 0
*
*
* ISUP parameters:
*
* Configure ISUP module
* ISUP_CONFIG <reserved> <reserved> <user_id> <options> <num_grps> <num_ccts> [<partner_id>]
ISUP_CONFIG 0 0 0x4d 0x0475 8 256
*
*
ISUP_CFG_CCTGRP 0 777 0x01 0x00 0x7fff7fff 0x249001c 0 0x4d 555 0x8 1 0x00d0 *$
conform=ETSI_V2_V3
conform=ETSI_V2_V3
conform=ETSI_V2_V3
conform=ETSI_V2_V3
conform=ETSI_V2_V3
ISUP_CFG_CCTGRP 5 888 0x21 0xa0 0x7fff7fff 0x249001c 0 0x4d 666 0x8 1 0x00d0 *$
conform=ETSI_V2_V3
ISUP_CFG_CCTGRP 6 666 0x01 0xc0 0x7fff7fff 0x249001c 0 0x4d 888 0x8 1 0x00d0 *$
conform=ETSI_V2_V3
ISUP_CFG_CCTGRP 7 666 0x21 0xe0 0x7fff7fff 0x249001c 0 0x4d 888 0x8 1 0x00d0 *$
conform=ETSI_V2_V3
*
********************************************************************************

85
86

SS7 Call Scenarios
4.
This chapter describes some common call setup and call release scenarios when using SS7
technology. The first topic below describes how the scenarios are presented in this chapter, and
subsequent topics describe each specific scenario:
Scenario Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Opening a Device Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Application-Initiated Outbound Call Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Network-Initiated Inbound Call Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Disconnect Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Call Collision Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Continuity Testing Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
4.1
Scenario Presentation
Each scenario is presented in tabular format. The tables provide the following information:
Application - Shows functions issued by the application (::>).
Libgcs7 - Shows SS7 call control library activities including Dialogic Global Call Software
events sent to the application (<::) and messages sent to the Dialogic Global Call SS7 server
(==>)
Server - Shows Dialogic Global Call SS7 server activities including messages sent to the
Dialogic Global Call SS7 library (<==) and messages sent to the SS7 stack (-->).
Stack - Shows SS7 stack activities including messages received from the SS7 stack (<--).
Notes: 1. All scenarios described in this chapter operate in asynchronous mode.

2. For simplicity, all tables use ISUP message type names instead of primitive names.
3. The term Stack in each table represents the interface to the ISUP module and does not identify
messages sent to or received from the network.
4.2
Opening a Device Scenario

Table 6 shows the scenario.

87
SS7 Call Scenarios
Table 6. Opening a Device Scenario

Application
Libgcs7
Server
Stack
gc_OpenEx( ) ::>
Open_REQ ==>
<== Open_CONF
4.3
Application-Initiated Outbound Call Scenarios

Details on the following scenarios are provided:
Common Outbound Call Scenario
ITU-T Alternative Outbound Call Scenario
Outbound Call Where ACM Has No Indication Scenario
4.3.1
Common Outbound Call Scenario

Table 7 shows a common application-initiated outbound call scenario.
Table 7. Common Outbound Call Scenario

Application
Libgcs7
Server
Stack
gc_MakeCall( ) ::>
MakeCall_REQ ==>
IAM -->
<-- ACM
<== Alerting_IND
<:: GCEV_ALERTING
<-- ANM
<== Connected_IND
<:: GCEV_CONNECTED
4.3.2
ITU-T Alternative Outbound Call Scenario

Table 8 shows an alternative application-initiated outbound scenario for ITU-T operation only.
Table 8. Alternative Outbound Call Scenario for ITU-T Operation Only

Application
Libgcs7
Server
Stack
gc_MakeCall( ) ::>
MakeCall_REQ ==>
88

SS7 Call Scenarios
Table 8. Alternative Outbound Call Scenario for ITU-T Operation Only (Continued)
Application
Libgcs7
Server
Stack
IAM -->
<-- CON
<== Connected_IND
<:: GCEV_CONNECTED
4.3.3
Outbound Call Where ACM Has No Indication Scenario

Table 9 shows an application-initiated outbound call scenario where the ACM has no indication.
Table 9. Outbound Call Where ACM Has No Indication Scenario

Application
Libgcs7
Server
Stack
gc_MakeCall( ) ::>
MakeCall_REQ ==>
IAM -->
<-- ACM
<-- CPG
<== Alerting_IND
<:: GCEV_ALERTING
<-- ANM
<== Connected_IND
<:: GCEV_CONNECTED
4.4
Network-Initiated Inbound Call Scenarios

Common Inbound Call Scenario
Alternative Inbound Call Scenario
4.4.1
Common Inbound Call Scenario

Table 10 shows a common network-initiated inbound call scenario.
Table 10. Common Inbound Call Scenario

Application
Libgcs7
Server
Stack
gc_WaitCall( ) ::>
WaitCall_REQ ==>

89
SS7 Call Scenarios
Table 10. Common Inbound Call Scenario (Continued)

Application
Libgcs7
Server
Stack
<-- IAM
<== Offered_IND
<:: GCEV_OFFERED
gc_AcceptCall( ) ::>
Accept_REQ ==>
<:: GCEV_ACCEPT
ACM -->
gc_AnswerCall( ) ::>
Answer_REQ ==>
<:: GCEV_ANSWERED
4.4.2
ANM -->
Alternative Inbound Call Scenario

Table 11 shows an alternative network-initiated inbound call scenario.
Table 11. Alternative Inbound Call Scenario

Application
Libgcs7
Server
Stack
gc_WaitCall( ) ::>
WaitCall_REQ ==>
<-- IAM
<== Offered_IND
<:: GCEV_OFFERED
gc_AnswerCall( ) ::>
Answer_REQ ==>
<:: GCEV_ANSWERED
4.5
CON -->
Disconnect Scenarios
Application-Initiated Disconnect Scenario
Network-Initiated Disconnect Scenario
Server-Initiated Disconnect with Application Informed Scenario
Server-Initiated Disconnect with Application Not Informed Scenario
4.5.1
Application-Initiated Disconnect Scenario

Table 12 shows an application-initiated disconnect scenario.
90

SS7 Call Scenarios
Table 12. Application-Initiated Disconnect Scenario

Application
Libgcs7
Server
Stack
gc_DropCall( ) ::>
DropCall_REQ ==>
REL -->
<-- RLC
<== DropCall_CONF
<:: GCEV_DROPCALL
gc_ReleaseCallEx( ) ::>
<:: GCEV_RELEASECALL
4.5.2
Network-Initiated Disconnect Scenario

Table 13 shows a network-initiated disconnect scenario.
Table 13. Network-Initiated Disconnect Scenario

Application
Libgcs7
Server
Stack
<-- REL
<== Disconnect_IND
<:: GCEV_DISCONNECTED
REL -->
gc_DropCall( ) ::>
DropCall_REQ ==>
RLC -->
<-- RLC
<== DropCall_CONF
<:: GCEV_DROPCALL
4.5.3
Server-Initiated Disconnect with Application Informed

Scenario
Table 14 shows a server-initiated disconnect scenario when the application is informed. This
scenario is commonly used in continuity check procedures.

91
SS7 Call Scenarios
Table 14. Server-Initiated Disconnect with Application Informed Scenario

Application
Libgcs7
Server
Stack
<== Disconnect_IND
gc_DropCall( ) ::>
DropCall_REQ ==>
REL -->
<-- RLC
<== DropCall_CONF
<:: GCEV_DROPCALL
4.5.4
Server-Initiated Disconnect with Application Not Informed

Scenario
Table 15 shows a server-initiated disconnect scenario when the application is not informed. This
scenario is commonly used when processing unsuccessful calls with overlap receive.
Table 15. Server-Initiated Disconnect with Application Not Informed Scenario

Application
Libgcs7
Server
Stack
<-- IAM
REL -->
<-- RLC
4.6
Call Collision Scenarios

Glare Scenario
Inbound Call Received before Call Clearing Completion Scenario
SRL Queue-Related Call Collision Scenario
MQ Queue-Related Call Collision Scenario
GCT Queue-Related Call Collision with Application Informed Scenario
GCT Queue-Related Call Collision with Application Not Informed Scenario
92

SS7 Call Scenarios
4.6.1
Glare Scenario
Table 12 shows a glare scenario.
Table 16. Glare Scenario

Application
Libgcs7
Server
Stack
gc_MakeCall(#1) ::>
MakeCall_REQ ==>
IAM -->
<-- IAM
<== Offered_IND
<:: GCEV_DISCONNECTED (#1)
<:: GCEV_OFFERED (#2)
gc_DropCall(#1) ::>
<:: GCEV_DROPCALL (#1)
gc_ReleaseCallEx(#1) ::>
<:: GCEV_RELEASECALL (#1)
Continue call setup (#2) ...
4.6.2
Inbound Call Received before Call Clearing Completion

Scenario
Table 17 shows a call collision scenario where an inbound call is received before the completion of
call clearing on an existing call.
Table 17. Inbound Call before Completion of Call Clearing Scenario

Application
Libgcs7
Server
Stack
<-- REL
<== Disconnect_IND
<:: GCEV_DISCONNECTED (#1)
REL -->
gc_DropCall(#1) ::>
DropCall_REQ ==>
RLC -->
<-- RLC
<== DropCall_CONF
<:: GCEV_DROPCALL (#1)
<-- IAM
<== Offered_IND
<:: GCEV_OFFERED (#2)

93
SS7 Call Scenarios
Table 17. Inbound Call before Completion of Call Clearing Scenario (Continued)
Application
Libgcs7
Server
Stack
gc_ReleaseCallEx(#1) ::>
<:: GCEV_RELEASECALL (#1)
Continue call setup (#2) ...
4.6.3
SRL Queue-Related Call Collision Scenario

Table 18 shows a call collision scenario related to the Dialogic Standard Runtime Library (SRL)
queue.
Table 18. Disconnect Collision on SRL Queue

Application
Libgcs7
Server
Stack
<-- REL
<:: GCEV_DISCONNECTED sent
<== Disconnect_IND
REL -->
gc_DropCall( ) ::>
Application must ignore
this event.
DropCall_REQ ==>
RLC -->
<-- RLC
<== DropCall_CONF
<:: GCEV_DROPCALL
Note: The two references to GCEV_DISCONNECTED in the table above represent one GCEV_DISCONNECTED event at
two different points in time; the first when the event is sent by the Libgcs7 library and the second when the event is received
by the application.
4.6.4
MQ Queue-Related Call Collision Scenario

Table 19 shows a call collision scenario related to the MQ queue. MQ is the abbreviation for the
Inter Process Communication (IPC) mechanism used internally by the Dialogic Global Call SS7
Software for communication between the library and the server.
Table 19. Disconnect Collision on MQ Queue

Application
Libgcs7
Server
gc_DropCall( ) ::>
<-- REL
DropCall_REQ ==>>
94
Stack
<== Disconnect_IND

SS7 Call Scenarios
Table 19. Disconnect Collision on MQ Queue (Continued)

Application
Libgcs7
Server
Stack
REL -->
Ignored Disconnect_IND <==
==> DropCall_REQ
RLC -->
<-- RLC
<== DropCall_CONF
<:: GCEV_DROPCALL
4.6.5
GCT Queue-Related Call Collision with Application

Informed Scenario
Table 20 shows a call collision scenario related to the GCT queue where the application is
informed.
Table 20. Disconnect Collision on GCT Queue with Application Informed

Application
Libgcs7
Server
Stack
gc_DropCall( ) ::>
DropCall_REQ ==>>
REL -->
<-- REL
RLC -->
<-- RLC
<== DropCall_CONF
<:: GCEV_DROPCALL
4.6.6
GCT Queue-Related Call Collision with Application Not

Informed Scenario
Table 21 shows a call collision scenario related to the GCT queue where the application is not
informed. This scenario is used for processing unsuccessful calls that use overlap receive.

95
SS7 Call Scenarios
Table 21. Disconnect Collision on GCT Queue with Application Not Informed
Application
Libgcs7
Server
Stack
<-- IAM
REL -->
<-- REL
RLC -->
<-- RLC
4.7
Continuity Testing Scenarios

Successful Outbound Out-of-Call Continuity Test Scenario
Successful Inbound Out-of-Call Continuity Test Scenario
Outbound Out-of-Call Continuity Test with One Failure Scenario
Inbound Out-of-Call Continuity Test with One Failure Scenario
Successful Outbound In-Call Continuity Test Scenario
Successful Inbound In-Call Continuity Test Scenario
Outbound In-Call Continuity Test with One Failure Scenario (Old Method)
Outbound In-Call Continuity Test with One Failure Scenario (New Method)
Inbound In-Call Continuity Test with One Failure Scenario
4.7.1
Successful Outbound Out-of-Call Continuity Test Scenario

Table 22 shows a successful outbound out-of-call continuity test scenario.
Table 22. Successful Outbound Out-of-Call Continuity Test Scenario

Application
Libgcs7
Server
Stack
gc_Extension( ) ::>
(ext_id =
REQUESTCONTCHECK)
COT_Outbound_REQ ==>
<:: GCEV_EXTENSION
(ext_id = CONTCHECK)
SZE -->
(ANSI only; do
nothing)
<-- LPA
gc_Extension( ) ::>
(ext_id =
SENDCONTCHECKRESULT)
COT_Result_REQ ==>
96

SS7 Call Scenarios
Table 22. Successful Outbound Out-of-Call Continuity Test Scenario (Continued)

Application
Libgcs7
Server
Stack
REL -->
<-- RLC
<== DropCall_CONF
<:: GCEV_EXTENSION
(CONTCHECK_END)
4.7.2
Successful Inbound Out-of-Call Continuity Test Scenario

Table 23 shows a successful inbound out-of-call continuity testing scenario.
Table 23. Successful Inbound Out-of-Call Continuity Test Scenario

Application
Libgcs7
Server
Stack
<-- SZE
<== Detected_IND
<:: GCEV_DETECTED
<== ApplyLoop_IND
ApplyLoopback( )
(Internal)
LPA -->
(shortcut if ANSI)
<-- REL
<== RemoveLoop_IND
RemoveLoopback( )
(internal)
<== Disconnect_IND
gc_DropCall( ) ::>
DropCall_REQ ==>
RLC -->
<-- RLC
<== DropCall_CONF
<:: GCEV_DROPCALL
4.7.3
Outbound Out-of-Call Continuity Test with One Failure

Scenario
Table 24 shows an outbound out-of-call continuity test scenario with one failure.

97
SS7 Call Scenarios
Table 24. Outbound Out-of-Call Continuity Test with One Failure Scenario
Application
Libgcs7
Server
Stack
gc_Extension( ) ::>
(ext_id =
REQUESTCONTCHECK)
<:: GCEV_EXTENSION
SZE -->
(ANSI only; do nothing)
<-- LPA
gc_Extension( ) ::>
(ext_id =
(failure)
COT_Result_REQ ==>
(failure)
COT -->
gc_Extension( ) ::>
(ext_id =
REQUESTCONTCHECK)
<:: GCEV_EXTENSION
SZE -->
<-- LPA
gc_Extension( ) ::>
(ext_id =
COT_Result_REQ ==>
REL -->
<-- RLC
<== DropCall_CONF
<:: GCEV_EXTENSION
(ext_id = CONTCHECK_END)
4.7.4
Inbound Out-of-Call Continuity Test with One Failure

Scenario
Table 25 shows an inbound out-of-call continuity test scenario with one failure.
Table 25. Inbound Out-of-Call Continuity Test with One Failure Scenario
Application
Libgcs7
Server
Stack
<-- SZE
<== Detected_IND
98

SS7 Call Scenarios
Table 25. Inbound Out-of-Call Continuity Test with One Failure Scenario (Continued)
Application
Libgcs7
Server
Stack
<:: GCEV_DETECTED
<== ApplyLoop_IND
ApplyLoopback( )
(internal)
LPA -->
(shortcut if ANSI)
failure
<-- COT
<-- REL
<== RemoveLoop_IND
RemoveLoopback( )
(internal)
RLC -->
<-- SZE
<== ApplyLoop_IND
ApplyLoopback( )
(internal)
LPA -->
(shortcut if ANSI)
<-- REL
<== RemoveLoop_IND
RemoveLoopback( )
(internal)
<== Disconnect_IND
gc_DropCall( ) ::>
DropCall_REQ ==>
RLC -->
<-- RLC
<== DropCall_CONF
<:: GCEV_DROPCALL
4.7.5
Successful Outbound In-Call Continuity Test Scenario

Table 26 shows a successful outbound in-call continuity test scenario.
Table 26. Successful Outbound In-Call Continuity Test Scenario

Application
gc_MakeCall( ) ::>
Libgcs7
Server
Stack
Continuity Check Required...

MakeCall_REQ ==>

Continuity Check
Required...
99
SS7 Call Scenarios
Table 26. Successful Outbound In-Call Continuity Test Scenario (Continued)

Application
Libgcs7
Server
Stack
<:: GCEV_EXTENSION( )
IAM -->
<-- LPA
gc_Extension( ) ::>
(ext_id =
COT_Result_REQ ==>
<:: GCEV_EXTENSION
COT -->
(success)
Continue normal call setup...
4.7.6
Successful Inbound In-Call Continuity Test Scenario

Table 27 shows a successful inbound in-call continuity test scenario.
Table 27. Successful Inbound In-Call Continuity Test Scenario

Application
Libgcs7
Server
Continuity Check
Required...
Stack
<-- IAM
<== Detected_IND
<:: GCEV_DETECTED
<== ApplyLoop_IND
ApplyLoopback( )
(internal)
LPA -->
(shortcut if ANSI)
<-- COT
(success)
<== RemoveLoop_IND
RemoveLoopback( )
(internal)
<== Offered_IND
<:: GCEV_OFFERED
Continue normal call setup...
4.7.7
Outbound In-Call Continuity Test with One Failure Scenario

(Old Method)
Table 28 shows an older variation of the outbound in-call continuity test with one failure scenario.
100

SS7 Call Scenarios
Table 28. Outbound In-Call Continuity Test with One Failure Scenario (Old Method)
Application
gc_MakeCall( ) ::>
Libgcs7
Server
Stack

MakeCall_REQ ==>
Continuity Check
Required...
<:: GCEV_EXTENSION
IAM -->
<-- LPA
gc_DropCall( ) ::>
(reason =
CONTCHECK_FAILED)
COT_Result_REQ ==>
(failure)
COT -->
gc_Extension( ) ::>
(ext_id =
REQUESTCONTCHECK)
<:: GCEV_EXTENSION
SZE -->
<-- LPA
gc_Extension( ) ::>
(ext_id =
COT_Result_REQ ==>
<:: GCEV_EXTENSION
REL -->
<-- RLC
<== AbortCall_IND
<:: GCEV_DROPCALL
<::GCEV_RELEASECALL
4.7.8
Outbound In-Call Continuity Test with One Failure Scenario

(New Method)
Table 29 shows a newer variation of the outbound in-call continuity test with one failure scenario.

101
SS7 Call Scenarios
Table 29. Outbound In-Call Continuity Test with One Failure Scenario (New Method)
Application
gc_MakeCall( ) ::>
Libgcs7
Server
Stack

MakeCall_REQ ==>
Continuity Check
Required...
<:: GCEV_EXTENSION
IAM -->
<-- LPA
gc_Extension( ) ::>
(ext_id =
(failure)
COT_Result_REQ ==>
(failure)
COT -->
gc_Extension( ) ::>
(ext_id =
REQUESTCONTCHECK)
<:: GCEV_EXTENSION
SZE -->
(ANSI only, do nothing)
<-- LPA
gc_Extension( ) ::>
(ext_id =
SENDCONCHECKRESULT)
COT_Result_REQ ==>
<:: GCEV_EXTENSION
REL -->
<-- RLC
<== AbortCall_IND
gc_DropCall( ) ::>
<:: GCEV_DROPCALL
4.7.9
Inbound In-Call Continuity Test with One Failure Scenario

Table 30 shows the inbound in-call continuity test with one failure scenario.
102

SS7 Call Scenarios
Table 30. Inbound In-Call Continuity Test with One Failure Scenario
Application
Libgcs7
Server
Stack
Continuity Check
Required...
<-- IAM
<== Detected_IND
<:: GCEV_DETECTED
<== ApplyLoop_IND
ApplyLoopback( )
(internal)
LPA -->
(shortcut if ANSI)
<-- COT
(failure)
<-- REL
<== RemoveLoop_IND
RemoveLoopback( )
(internal)
RLC -->
<-- SZE
<== ApplyLoop_IND
ApplyLoopback( )
(internal)
LPA -->
(shortcut if ANSI)
<-- REL
<== RemoveLoop_IND
RemoveLoopback( )
(internal)
<== Disconnect_IND
gc_DropCall( ) ::>
DropCall_REQ ==>
RLC -->
<-- RLC
<== DropCall_CONF
<:: GCEV_DROPCALL

103
SS7 Call Scenarios
104

SS7-Specific Operations
5.
This chapter describes how the Dialogic Global Call Software is used to perform certain SS7specific operations. These tasks include:
Handling of Glare Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Controlling Priority in Circuit Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Dynamically Adding and Deleting SS7 Circuit Groups . . . . . . . . . . . . . . . . . . . . . . . . 106
SCbus or CT Bus Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Connecting Multiple Hosts to SIUs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Using Dual Resilient SIU Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Using Overlap Send and Receive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Suspending and Resuming Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Performing Continuity Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Sending and Receiving ISUP/TUP Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Handling Layer 1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
5.1
Handling of Glare Conditions

A glare condition occurs when an outgoing call has been initiated (gc_MakeCall( ) succeeded) and
an incoming call is detected. Dialogic Global Call SS7 Software and the SS7 stack almost
completely hide this condition from the application that will see its outbound call fail and will then
be notified of the inbound call. See Section 4.6.1, Glare Scenario, on page 93 for an example.
However, in order to avoid adding delay to the handling of the inbound call, the SS7 call control
library does not wait for the failed outbound call to be released before it notifies the application of
the inbound call. This means that, in case of glare, the following type of scenario can be seen:
Application
Libgcs7
gc_MakeCall(crn1)
-->
GCEV_DISCONNECTED(crn1)
<-gc_DropCall(crn1)
-->
GCEV_OFFERED(crn2)
<--
This shows that an application running on bidirectional circuits should be ready to handle two
CRNs on a single line device. However, the application can be purely reactive with respect to the

105
failed call (crn1) and just respond to events using their associated CRN: simply perform a
gc_ReleaseCallEx( ) upon reception of any GCEV_DROPCALL, whether the CRN is the active
one or not. Using this procedure, the application only needs to store one CRN per line device.
Another case of glare condition is at disconnection. If the application calls gc_DropCall( ) while a
GCEV_DISCONNECTED has already been put in the Dialogic Standard Runtime Library (SRL)
event queue, the application will receive it after it does gc_DropCall( ) when it is waiting for
GCEV_DROPCALL. This late GCEV_DISCONNECTED event must be ignored by the
application. The call control library will send the GCEV_DROPCALL as usual when the call is
dropped. Other glare conditions at disconnection are all hidden from the application.
5.2
Controlling Priority in Circuit Groups

ISUP allows the setting of different priority schemes on a per circuit group basis:
Priority to incoming call on all circuits
Priority to outgoing call on all circuits
Highest point code has priority on even CICs (Circuit Identification Codes)
Highest point code has priority on odd CICs
The third scheme is the one recommended by the ITU (Q.764). With the SS7 stack, the priority
scheme can be selected in the <options> field of the ISUP_CFG_CCTGRP commands in the
config.txt file. Once priority has been given to one of the calls by the SS7 stack, upper software
layers (Dialogic Global Call SS7 Software and the application) must conform.
Because of the multiple layers of the software architecture and the asynchronous nature of the
communication between them, it is possible that collisions appear to exist even though there has
not been a true glare condition on the signaling link. For example, if the SS7 stack has posted an
IAM message for the Dialogic Global Call SS7 call control library but the application issues a
gc_MakeCall( ) before this message is received, the application will see the equivalent of a glare
condition: the outbound call will fail and the inbound call will be offered. This can happen
regardless of the configured priority scheme, even with priority given to outbound calls on all
circuits.
5.3
Dynamically Adding and Deleting SS7 Circuit

Groups
Dialogic Global Call SS7 Software applications can be programmed to add new circuit groups
dynamically at runtime. You can start with an initial number of trunks in the system, and then
enable more trunks gradually without restarting the system and application. You can also delete
circuit groups.
The Dialogic Boards in the new circuit groups may include the following:
Dialogic SS7HDPD4TE SS7 Interface Boards
Dialogic SS7HDCN16 SS7 Interface Boards
106

Dialogic SS7HDCS8 SS7 Interface Boards

Dialogic SS7HDCD16 SS7 Interface Boards
Dialogic SS7HDCQ16 SS7 Interface Boards
Dialogic DMT160TEC Digital Telephony Interface Boards
Dialogic DMV-B Media Boards
Dialogic DMV-A Media Boards
The ability to add and delete SS7 circuit groups dynamically at runtime is provided by the
gc_SetConfigData( ) function with set ID SS7SET_ADD_CCTGRP for adding a circuit group and
set ID SS7SET_DEL_CCTGRP for deleting a circuit group. More details are given in the
following sections.
5.3.1
Adding a Circuit Group

The set ID/parm IDs for adding a circuit group are:
SS7SET_ADD_CCTGRP
Parm IDs:
SS7PARM_GRP_ID Group ID (integer value)
SS7PARM_ISUP_CFG_GRP Provides the basic data required by
ISP_MSG_CNF_GRP message. Its value type is GCSS7_ISUP_CFG_CCTGRP data
structure.
SS7PARM_TRUNK_CFG Provides the data required by Global Call SS7 Software to
configure a trunk device. Its value type is GCSS7_TRUNK_CFG data structure.
Note: The GCSS7_ISUP_CFG_CCTGRP and GCSS7_TRUNK_CFG data structures are
described in Chapter 9, SS7-Specific Data Structures.
To add a circuit group, do the following:
1. Call gc_util_insert_parm_val( ) to insert {SS7SET_ADD_CCTGRP, SS7PARM_GRP_ID}
with integer value: GroupID.
2. Call gc_util_insert_parm_ref( ) to insert {SS7SET_ADD_CCTGRP,
SS7PARM_ISUP_CFG_GRP} with data structure: GCSS7_ISUP_CFG_CCTGRP.
3. Call gc_util_insert_parm_ref( ) to insert {SS7SET_ADD_CCTGRP,
SS7PARM_TRUNK_CFG} with data structure: GCSS7_TRUNK_CFG.
4. Call gc_SetConfigData( ) with arguments set as follows:
target_type = GCTGT_CCLIB_SYSTEM
target_id = GC_SS7_LIB or 5
target_datap = GC_PARM_BLKP parameter pointer, as constructed by the utility
function gc_util_insert_parm_ref( ) or gc_util_insert_parm_val( ) for configuration of

circuit groups
time_out = time interval (in seconds) during which the parameter value must be updated.
If the interval is exceeded, the update request is ignored. This parameter is supported in
synchronous mode only, and it is ignored when set to 0.
update_cond = ignored in Global Call SS7 Software

107
request_idp = pointer to the location for storing the request ID, output from Global Call
Software
mode = EV_SYNC for synchronous execution
Example
#include
#include
#include
#include
#include
<stdio.h>
<srllib.h>
<gclib.h>
<gcerr.h>
<Libgcs7.h>
int AddCircuitGrp(int a_GroupID, unsigned long a_DPC, unsigned long a_OPC,

unsigned short a_FirstCIC, unsigned short a_FirstCID,
char * a_TrunkName, long * a_pRequestID)
{
GC_PARM_BLK * t_pParmBlk = NULL;
GCSS7_ISUP_CFG_CCTGRP t_GrpCfg;
GCSS7_TRUNK_CFG t_TrunkCfg;
int t_result = 0;
*a_pRequestID = 0;
/* Initialize the GCSS7_ISUP_CFG_CCTGRP data structure */
memset(&t_GrpCfg, 0, sizeof(GCSS7_ISUP_CFG_CCTGRP));
t_GrpCfg.dpc = a_DPC;
t_GrpCfg.basic_cic = a_FirstCIC;
t_GrpCfg.basic_cid = a_FirstCID;
t_GrpCfg.cic_mask = 0x7fff7fff;
t_GrpCfg.options = 0x071e;
t_GrpCfg.user_inst = 0;
t_GrpCfg.user_id = 0x4d;
t_GrpCfg.opc = a_OPC;
t_GrpCfg.ssf = 0x8;
t_GrpCfg.variant = 0;
t_GrpCfg.options2 = 0;
/* Initialize the GCSS7_TRUNK_CFG data structure */
memset(&t_TrunkCfg, 0, sizeof(GCSS7_TRUNK_CFG));
strcpy( t_TrunkCfg.trunk_name, a_TrunkName );
t_TrunkCfg.base_ts = 1; /* Started from the first timeslot */
/* Insert the Group ID */
t_result = gc_util_insert_parm_val(&t_pParmBlk, SS7SET_ADD_CCTGRP, SS7PARM_GRP_ID,
sizeof(int), a_GroupID);
if (t_result)
{
/* Process error */
return t_result;
}
/* Insert the parameter SS7PARM_ISUP_CFG_GRP */
t_result = gc_util_insert_parm_ref(&t_pParmBlk, SS7SET_ADD_CCTGRP, SS7PARM_ISUP_CFG_GRP,
sizeof(GCSS7_ISUP_CFG_CCTGRP), &t_GrpCfg);
if (t_result)
{
/* Process error */
return t_result;
}
/* Insert the parameter SS7PARM_TRUNK_CFG */
t_result = gc_util_insert_parm_ref(&t_pParmBlk, SS7SET_ADD_CCTGRP, SS7PARM_TRUNK_CFG,
sizeof(GCSS7_TRUNK_CFG), &t_TrunkCfg);
if (t_result)
{
/* Process error */
return t_result;
108

}
/* Add a new circuit group with a_GroupID */
t_result = gc_SetConfigData(GCTGT_CCLIB_SYSTEM, GC_SS7_LIB, t_pParmBlk, 0,
GCUPDATE_IMMEDIATE, a_pRequestID, EV_SYNC);
if (t_result)
{
/* Process the error */
gc_util_delete_parm_blk(t_pParmBlk);
return t_result;
}
return t_result;
}
Guidelines for Adding a Circuit Group

The following guidelines apply when adding circuit groups at runtime:
The Dialogic Boards (SS7 or DM3) representing new circuit groups should be downloaded
successfully.
Each gc_SetConfigData( ) function call allows the application to add or delete one circuit
group at a time.
The total number of circuit groups or the total number of circuits in the SS7 Board system
(including static and dynamically allocated) cannot exceed <num_grps> or <num_ccts> of

ISUP_CONFIG defined in config.txt.
The maximum number of circuit groups (including both original and dynamically added) is 64
E1/T1 trunks.
The maximum number of circuits in a circuit group should not exceed 31 for E1 trunk or 24 for
T1 trunk.
All E1/T1 LIUs of SS7 Boards in the system to be used must be configured in config.txt (using
the LIU_CONFIG command).

All MPT links of the SS7 Board to be used must be configured in config.txt (using
MTP_LINKSET and MTP_LINK commands).

Modification of existing circuit groups is not supported, which includes adding (or disabling)
individual circuits.
Dynamic configuration of Global Call SS7 circuit groups is only supported in the SS7 Board
system, not the SIU system.

Dynamic configuration of circuit groups does not include updating the configuration files
(config.txt and gcss7.cfg).

Dynamic configuration of LIUs and SCbus route is not supported.
The configuration remains persistent as long as the SS7 service/daemon is running. If only the
Global Call SS7 application is stopped, the newly added or deleted circuit group still remains
configured.
5.3.2
Deleting a Circuit Group

The set ID/parm ID for deleting a circuit group are:
SS7SET_DEL_CCTGRP
Parm ID:

109
SS7PARM_GRP_ID Group ID (integer value). There is no other data required by
ISP_MSG_END_GRP message.
To delete a circuit group, do the following:
1. Call gc_util_insert_parm_val( ) to insert {SS7SET_DEL_CCTGRP, SS7PARM_GRP_ID}
with integer value: GroupID.
2. Call gc_SetConfigData( ) with arguments set as follows:
target_type = GCTGT_CCLIB_SYSTEM
target_id = GC_SS7_LIB or 5
target_datap = GC_PARM_BLKP parameter pointer, as constructed by the utility
function gc_util_insert_parm_ref( ) or gc_util_insert_parm_val( ) for configuration of

circuit groups
time_out = time interval (in seconds) during which the parameter value must be updated.
If the interval is exceeded, the update request is ignored. This parameter is supported in
synchronous mode only, and it is ignored when set to 0.
update_cond = ignored in Global Call SS7 Software
request_idp = pointer to the location for storing the request ID, output from Global Call
Software
mode = EV_ASYNC for asynchronous execution
Example
#include
#include
#include
#include
#include
<stdio.h>
<srllib.h>
<gclib.h>
<gcerr.h>
<Libgcs7.h>
int DeleteCircuitGrp(int a_GroupID, long * a_pRequestID)

{
GC_PARM_BLK * t_pParmBlk = NULL;
int t_result = 0;
*a_pRequestID = 0;
/* Insert the Group ID */
t_result = gc_util_insert_parm_val(&t_pParmBlk, SS7SET_DEL_CCTGRP, SS7PARM_GRP_ID,
sizeof(int), a_GroupID);
if (t_result)
{
/* Process error */
return t_result;
}
/* Delete a circuit group with a_GroupID */
t_result = gc_SetConfigData(GCTGT_CCLIB_SYSTEM, GC_SS7_LIB, t_pParmBlk, 0,
GCUPDATE_IMMEDIATE, a_pRequestID, EV_ASYNC);
if (t_result)
{
/* Process the error */
return t_result;
}
return t_result;
}
110

int main()
{
int t_RequestID = 0;
AddCircuitGrp(1, 555, 777, 1, 1,"dkB1", &t_RequestID);
DeleteCircuitGrp(1, &t_RequestID);
}
Guidelines for Deleting a Circuit Group

The following guidelines apply when deleting circuit groups at runtime:
The circuit group to be deleted has to exist in the system.
All line devices (including trunk device) on that circuit group must be closed by using
gc_Close( ) before the circuit group can be deleted.

See also the Guidelines for Adding a Circuit Group above.
5.4
SCbus or CT Bus Routing

Routing is described under the following topics:
Routing Functions
Time Slot Assignment for Dialogic SS7 Boards
Using Time Slot 16 on Dialogic E1 Network Interface Boards
5.4.1
Routing Functions
The Dialogic Global Call SS7 Call Control Library (Libgcs7) supports the Global Call Software
routing functions (gc_Listen( ), gc_UnListen( ), and gc_GetXmitSlot( )). These functions are
available to user applications for performing routing of SS7 circuits regardless of their physical
location (for example, on a Dialogic Network Interface (DTI) Board or on a Dialogic SS7
Board). This allows the application to use one single set of functions without having to know where
the circuit is located (that is, on a DTI Board or on an SS7 Board).
The following functions are provided:
int gc_Listen(LINEDEV linedev, SC_TSINFO *sctsinfo_p, mode)
int gc_UnListen(LINEDEV linedev, mode)
int gc_GetXmitSlot(LINEDEV linedev, SC_TSINFO *sctsinfo_p, mode)
5.4.2
Time Slot Assignment for Dialogic SS7 Boards

The SS7 server automatically assigns CT Bus transmit time slots for telephony circuits located on a
Dialogic SS7 Board. The SS7 server also performs the full-duplex routing required for the
signaling connection, when the signaling links are routed over the CT Bus between a Dialogic
SS7 Board and a Dialogic Network Interface (DTI) Board. The configuration required for this to
happen is described in Chapter 3, Configuration and Startup.

111
5.4.3
Using Time Slot 16 on Dialogic E1 Network Interface

Boards
Traditionally, E1 trunks reserve physical time slot 16 for signaling, which is designated as
dtiB#T31, where # is the logical number of the trunk. With SS7 however, signaling can be on a
different physical trunk than the telephony circuits. The signaling time slots can then be used for a
normal voice circuit.
With Dialogic E1 Network Interface Boards, setting time slot 16 to the clear channel mode
requires special ISDN firmware to be downloaded to the board and the ISDN D channel to be
disabled. For Dialogic Springware Boards, this can be done using the CTR4 (ISCTR4 v6.65)
firmware, for example, and by changing parameter 16 in the CTR4.PRM parameter file to 2. For
Dialogic DM3 Boards, the special _TS16 firmware can be used, but see the limitation below.
Similarly, if an SS7 link is routed from time slot 16 of a Dialogic E1 Network Interface Board to
a Dialogic SS7 Board, the Network Interface Board must leave time slot 16 in clear channel
mode, as described.
When using Dialogic DM3 Boards, due to some backward-incompatible changes to the
*_ts16.config and corresponding *_ts16.fcd files in recent releases, each appropriate *_ts16.config
file must be reconfigured, and the corresponding *_ts16.fcd file regenerated, to restore the correct
time slot assignment, that is, TS16 = dtiBxT31 and TS17 = dtiBxT16, etc., required for correct
operation of the Dialogic Global Call SS7 Software. This is achieved as follows:
1. In the Dialogic Configuration Manager, double-click on the board device to open the
property sheets, click on the Misc property sheet if not already selected, and check the name
next to the FCDFileName property.
2. Open the corresponding *_ts16.config file in a text editor.
3. Replace the lines that start with defineBSet with the following lines:
defineBSet=10,1,1,31,
0,0,0,1,20,1,
0,0,0,1,20,1,
0,0,0,1,20,1,
0,0,0,1,20,1,
1,1,3,15,
1,1,3,15,
1,1,3,15,
1,1,3,15,
16,17,3,15,
16,17,3,15,
16,17,3,15,
16,17,3,15,
31,16,3,1,
31,16,3,1,
31,16,3,1,
31,16,3,1,
0
0
0
0
Downloading the updated .config file generates the correct *_ts16.fcd file.
4. Start the Dialogic system service.
5.5
Connecting Multiple Hosts to SIUs

SIU systems may have multiple hosts connected to the same SIU or pair of SIUs. In this case, each
host is responsible for the telephony circuits that it terminates. This must be specified in the
config.txt file on the SIU(s). Each ISUP_CFG_CCTGRP command must specify in its <host_id>
field which host is responsible for the circuit group. Additionally, the config.txt file must also
specify, using the SIU_HOSTS command, the number of hosts that will be used.
On each host, the SIU.HostID parameter must be set to reflect which one is the local host. This
allows Dialogic Global Call SS7 Software to correctly identify the host when communicating
with the SIU(s) and to know which circuit groups are configured on the local host.
112

5.6
Using Dual Resilient SIU Configurations

A dual-resilient SIU configuration brings an additional level of fault tolerance to a Dialogic
Global Call SS7 System. It consists of two SIUs configured as a single point code in the SS7
network. Host systems are connected via TCP/IP to both servers.
Under normal circumstances (both SIUs up and running) the load is shared between both units (see
Section 3.2.4, ISUP Configuration, on page 41). If one unit fails - either the whole unit or its
communication with the hosts - the partner unit maintains MTP operation of the node. However,
telephony circuit groups that were active on the failing SIU need to be transferred to the partner
SIU in order to be restored. With Dialogic Global Call SS7 Software, this procedure is performed
automatically by the Dialogic SS7 Server. The application will only see that circuits are blocked
(GCEV_BLOCKED event is received) and then unblocked after they are successfully transferred
to the partner SIU. The application should handle this as any other case of blocked circuits.
Dialogic Global Call SS7 Software automatically handles the restoration of the circuit groups to
their preferred SIU when the SIU comes back up after a failure. This process is transparent to the
user application. No GCEV_BLOCKED or GCEV_UNBLOCKED events are generated during the
restoration process.
Configuration of Dual Resilient SIUs

Dual-resilient SIU systems must have two SIUs configured. This configuration is done in the
gcss7.cfg file. SIUs are configured as either SIU A or SIU B. The first SIU configured must be SIU
A, and the second SIU must be B.
For Dialogic Global Call SS7 Software to be able to automatically handle dual-resilient SIU
operations, the gcss7.cfg file must specify which is the preferred SIU for each circuit group. See
Section 3.11, Sample Configuration Files, on page 61.
5.7
Using Overlap Send and Receive

The S77 call control library supports overlap sending using the gc_SendMoreInfo( ) function.
When using gc_SendMoreInfo( ), the only info_id parameter value supported by the Dialogic
SS7 call control library is DESTINATION_ADDRESS (DNIS). See the Dialogic Global Call
API Library Reference for more information.
Note:
To use gc_SendMoreInfo( ) for overlap sending, the GCST_SENDMOREINFO call state must be
enabled using the gc_SetConfigData( ) function. See the section on Call State Configuration in
the Dialogic Global Call API Programming Guide.
An older method of overlap sending is also still supported, that is, using the gc_SndMsg( )
function to send a Subsequent Address Message (SAM). See Section 8.2.23, gc_SndMsg( )
Variances for SS7, on page 145 for more information.
Two methods of overlap receiving are supported, the preferred method, and an older method
maintained for backward compatibility reasons only. Both methods are described below.

113
The preferred method for implementing overlap receiving is as follows:

1. Issue gc_CallAck(GCACK_SERVICE_INFO) to determine if digits are available.
2. Receive a GCEV_MOREINFO event.
3. Use gc_ResultValue( ) to determine the status, which is one of the following:
GCRV_INFO_PRESENT_ALL - The requested digits are now available.
GCRV_INFO_PRESENT_MORE - The requested digits are now available.
More/additional digits are available.

GCRV_INFO_SOME_TIMEOUT - Only some digits are available due to a timeout.
GCRV_INFO_SOME_NOMORE - Only some digits are available, no more digits will be
received.
GCRV_INFO_NONE_TIMEOUT - No digits are available due to a timeout.
GCRV_INFO_NONE_NOMORE - No more digits are available.
4. Issue gc_GetCallInfo(DESTINATION_ADDRESS) to retrieve the digits.

5. If the status returned via GCEV_MOREINFO in step 3 indicates that more digits are available,
the application can do the following:
Issue gc_ReqMoreInfo( ) to request the additional digits.
Receive a GCEV_MOREINFO event with a status as indicated in step 3 above.
Issue gc_GetCallInfo(DESTINATION_ADDRESS) to retrieve the additional digits.
6. Repeat step 5 until all information has been retrieved.

The following method of overlap receiving continues to be supported for backward compatibility
reasons only:
1. Issue gc_CallAck(GCACK_SERVICE_DNIS) identifying the number of digits to retrieve
(dnis.accept) in the GC_CALLACK_BLK structure pointed to by the callack_blkp function
parameter.
2. Receive a GCEV_MOREDIGITS event.
3. Issue gc_GetDNIS( ) to retrieve the digits.
Note:
To retrieve a certain number of digits at a time, specify that number in the dnis.accept field and
repeat steps 1, 2 and 3 above until all information has been retrieved.
See the Dialogic Global Call API Programming Guide for more detailed information on overlap
sending and receiving in general and the Dialogic Global Call API Library Reference for more
information about the functions mentioned above.
5.8
Suspending and Resuming Calls

Call suspend and resume features are supported using the gc_HoldCall( ) and gc_RetrieveCall( )
functions. A call can be suspended by the application or by the network.
When a call is in the Connected state, the application can issue gc_HoldCall( ) on the CRN of the
current call to put the call in the suspended state. The application receives a GCEV_HOLDACK
event indicating that the call has entered the suspended state. The call remains in the suspended
114

state until a gc_RetrieveCall( ) is issued on the CRN for the call. The application receives a
GCEV_RETRIEVEACK event when this occurs.
If the action of suspending a call is initiated by the network (with an SS7 SUS message), the
application receives a GCEV_HOLDCALL event. When the network resumes the call, the
application receives a GCEV_RETRIEVECALL event. If the network decides to drop the call or
the call remains in the suspended state for too long, the application will not receive the
GCEV_RETRIEVECALL event but instead receives a GCEV_DROPCALL event. While a call is
in the suspended state, it can be dropped or released by the application.
Notes: 1. The call state, as returned by gc_GetCallState( ), for a suspended call is GCST_ONHOLD.
2. A suspended call can only be resumed by the side that originally put the call in the suspended
state. If a call has been placed in the suspended state by the network, the application cannot
resume the call using the gc_RetrieveCall( ) function. The gc_RetrieveCall( ) function will fail
if this is attempted. Similarly, if a call has been placed in the suspended state by the application,
an SS7 RES message from the network will not resume the call.
5.9
Performing Continuity Checks

The continuity check feature is implemented using the gc_Extension( ) function and the associated
GCEV_EXTENSION event.
The structure associated with the GCEV_EXTENSION event (METAEVENT structure) contains
the extevtdatap field, which is a pointer to an EXTENSIONEVTBLK structure. The value of the
ext_id field in the EXTENSIONEVTBLK structure can be:
S7_EXT_CONTCHECK to indicate the beginning of a continuity check process
S7_EXT_CONTCHECK_END to signal the end of a continuity check process
The parmblk field in the EXTENSIONEVTBLK structure contains additional information. The
parmblk field, which is of type GC_PARM_BLK, contains only one element of parameter data of
type GC_PARM_DATA. The set ID of this parameter is S7SET_CONTCHECK and the parameter
ID is S7PARM_CONTCHECK_TYPE. The parm_data_size is sizeof(int).
Note:
In earlier releases of the Dialogic Global Call SS7 Software, S7SET_ parameter sets and
S7PARM_ parameter IDs were defined with values that are different than the current release. An
application that uses the S7SET_ and S7PARM_ defines must be recompiled with the correct
header file from the current release.
In this feature, the gc_Extension( ) function does not require any GC_PARM_BLK data, except
when sending continuity check result and the outcome of the test must be sent. Also, the
gc_Extension( ) function does not return anything via the retblkp parameter.
5.9.1
Inbound Continuity Check

When a continuity check request is received from the network, the call control library does the
following:
1. Saves, if necessary, the current time slot assignment of the current line.

115
2. Sends a GCEV_DETECTED event to the application to prevent attempts to make outbound

calls.
Note: The application should first enable the GCEV_DETECTED event. Enabling the
GCEV_DETECTED event is not required for correct operation of the inbound
continuity check, but it is recommended in order to minimize the possiblity of call
collisions.
3. Puts the line in loopback for the continuity test.
When the continuity check completes:
1. The Dialogic Global Call SS7 Software removes the loopback and restores the previous
CT Bus routing.
Note: For CT Bus routing to be restored correctly, it is important that any routing be done
using Dialogic Global Call API routing functions and not using other available
routing options, such as using the dt_* functions or the nr_* CT Bus routing
functions, or the sending of CT Bus routing messages directly to the board.
2. The application receives a GCEV_OFFERED event (for an in-call continuity check) or a
GCEV_DISCONNECTED event (for an out-of-call continuity check).
3. The application should continue processing the call in the normal way.
Note the difference in events received if GCEV_DETECTED is enabled or not enabled:
If the application enables the generation of the GCEV_DETECTED event and a call
disconnects while in the Detected state, a GCEV_DISCONNECTED event is received.

If the application did not enable the generation of the GCEV_DETECTED event and a call
disconnects while it is in the Detected state (that is, before the call enters the Offered state), the
application receives a GCEV_OFFERED event with a result value of
GCRV_CALLABANDONED, then a GCEV_DISCONNECTED event.
5.9.2
Outbound Continuity Check

As for the inbound continuity check, the outbound continuity check can be done outside of any call
(Out-of-Call) or as part of an outgoing call (In-Call). However, in the outbound case, since the
check is initiated by the application, the procedures for both types of check differ.
5.9.2.1
Outbound Out-of-Call Continuity Check

When requesting an outbound out-of-call continuity check on a circuit, the line device must be in
the Idle state, that is, the circuit must be unblocked and cannot have any active calls. The
application can then use the gc_Extension( ) function with an ext_id of
S7_EXT_REQUESTCONTCHECK to send an SS7 CCR message to the network.
The application receives a GCEV_EXTENSION event with an ext_id of S7_EXT_CONTCHECK
and with a parameter value of S7RV_CC_OUTBOUND to indicate that it can begin the continuity
check by connecting the test equipment to the line.
When the continuity check is completed and the result analyzed, the application must call
gc_Extension( ) with an ext_id of S7_EXT_SENDCONTCHECKRESULT to communicate the
116

results of the check to the remote party. To achieve this, the application must build a
GC_PARM_BLK structure. The set_ID must be S7SET_CONTCHECK, the parm_ID must be
S7PARM_CONTCHECK_RESULT, and the parameter value must be either CONTI_SUCCESS or
CONTI_FAILURE.
If the function is called with CONTI_SUCCESS, the continuity check process is finished and the
application is notified by a GCEV_EXTENSION event with an ext_id of
S7_EXT_CONTCHECK_END and with a parameter value of S7RV_CCEND_OUTBOUND.
When the application receives this event, the line can be used for making or receiving calls.
If the function is called with CONTI_FAILURE, the remote side is waiting for a re-check, and
therefore the application does not receive a GCEV_EXTENSION event with an ext_id of
S7_EXT_CONTCHECK_END.
5.9.2.2
Outbound In-Call Continuity Check

To request an in-call continuity check, the application must call gc_MakeCall( ) with the
continuity_check_indicator field in the S7_MAKECALL_BLK structure set to
CCI_CC_REQUIRED, so that the Dialogic Global Call library sends an SS7 IAM message, with
continuity check requested, to the network.
The application receives a GCEV_EXTENSION event with an ext_id of S7_EXT_CONTCHECK
and with a parameter value of S7RV_CC_OUTBOUND to indicate that it can begin the continuity
check by connecting the test equipment to the line.
If the continuity check is successful, the application indicates the success to the remote side by
calling gc_Extension( ) with an ext_id of S7_EXT_SENDCONTCHECKRESULT and a
parameter value of CONTI_SUCCESS. Since the continuity check process is now finished, the
application receives a GCEV_EXTENSION event with an ext_id of
S7_EXT_CONTCHECK_END with a parameter value of S7RV_CCEND_OUTBOUND. When
the application receives this event, the call proceeds in the normal way.
If the continuity check fails, to indicate the failure to the remote side, the application must call
either gc_Extension( ) with an ext_id of S7_EXT_SENDCONTCHECKRESULT and a parameter
value of CONTI_FAILURE or the gc_DropCall( ) function with a cause value of
CONTCHECK_FAILED. The call is cleared internally by Global Call Software and the other side
will have no knowledge of the call. The other side only recognizes a failed continuity check test
and waits for a re-check.
Caution:
If a failure result is sent to the other side, the other side will expect a re-check on the circuit.
Therefore, another call to gc_Extension( ) with an ext_id of S7_EXT_REQUESTCONTCHECK
should be issued by the application, until the continuity check succeeds. Alternatively, the
application could reset the circuit using gc_ResetLineDev( ) on the corresponding line device. In
this case, the application does not receive a GCEV_EXTENSION event, but receives a
GCEV_RESETLINEDEV event corresponding to the gc_ResetLineDev( ) function call.

117
The GCEV_EXTENSION event with an ext_id of S7_EXT_CONTCHECK_END may be received

in two other cases:
If the parameter value is S7RV_CCEND_OUTBOUND_ERROR, an error occurred during the
continuity check, for example, if the time waiting for the SS7 REL message at the remote side
expires.
If the parameter value is S7RV_CCEND_OUTBOUND_GLARE, a glare condition occurred,
for example, while seizing the line for a continuity check, an SS7 IAM message was received.
Caution:
5.10
In both cases of the GCEV_EXTENSION event with ext_id of EXT_CONTCHECK_END above,

the continuity check process is abandoned by the Dialogic Global Call library. The application
should not try to perform the physical continuity test again or try to send any continuity check
results because the remote side is not ready to receive the results and the send operation will fail.
Sending and Receiving ISUP/TUP Messages

The gc_SndMsg( ) function can be used to send any ISUP/TUP message (for example, facility)
that does not alter the call state or circuit state. See Section 8.2.23, gc_SndMsg( ) Variances for
SS7, on page 145 for more information.
Incoming ISUP/TUP messages that trigger Dialogic Global Call events can be retrieved using the
gc_GetSigInfo( ) function. See Section 8.2.11, gc_GetSigInfo( ) Variances for SS7, on page 139
for more information.
Dialogic Global Call Software can also be used to configure a line device to receive ISUP/TUP
messages processed by the underlying stack but not recognized by the SS7 call control library. To
configure a line device to receive these ISUP/TUP messages, use the gc_SetParm( ) function as
follows:
GC_PARM t_gcparm;
t_gcparm.intvalue = true;
gc_SetParm(ldev, GCPR_UNKNOWN_ISUP_MSGS, t_gcparm);
When an ISUP/TUP message is received on the line device, a GCEV_EXTENSION event with an
ext_id of S7_EXT_ISUP_EVENT is generated. The application can retrieve the message
parameters using code similar to the following:
void getextevtdata(METAEVENT* a_me_p) {
int ext_id = ((EXTENSIONEVTBLK*)(a_me_p->extevtdatap))->ext_id;
if (S7_EXT_ISUP_EVENT == ext_id) {
GC_PARM_BLKP t_parmblk_p =
&(((EXTENSIONEVTBLK*)a_me_p->extevtdatap)->parmblk);
GC_PARM_DATAP t_parm_p =
gc_util_find_parm(t_parmblk_p, S7SET_ISUP_EVENT,
S7PARM_ISUP_EVENT_PARM);
if (t_parm_p) {
printf(" parm size=%d. 0x...", t_parm_p->value_size);
for (int i=0; i < t_parm_p->value_size; ++i) {
printf(" %02x", t_parm_p->value_buf[i]);
}
}
}
}
118

For a GCEV_EXTENSION event that was caused by an unprocessed ISUP message, the
gc_GetSigInfo( ) function can be used instead of parsing the EXTENSIONEVTBLK data
structure, assuming that the GCPR_RECEIVE_INFO_BUF parameter has been set (by the
gc_SetParm( ) function) to enable the retrieval of the messages. See Section 8.2.11,
gc_GetSigInfo( ) Variances for SS7, on page 139 for more information.
5.11
Handling Layer 1 Alarms

The application is notified whenever a MVD_MSG_LIU_STATUS message is received for
Dialogic SS7HDP and SS7HDC Boards. This message provides specific layer 1 status indications
(for example, Pulse Code Modulation (PCM) Loss of Signal of Signal (LOS), Alarm Indication
Signal (AIS), etc.) for dkBx trunk devices. This notification to the application is sent for each
circuit associated with the trunk in the conventional Global Call Software method using
GCEV_ALARM events. With alarm notification, applications are able to better determine which
devices are available for making and receiving calls, or enabling/disabling voice activity.
Alarm handling is described under the following topics:
GCAMS Support
Supported Alarms
SS7-Specific Event Cause Codes for Layer 1 Alarms
5.11.1
GCAMS Support
The GCSS7 Library supports the Global Call Alarm Management System (GCAMS). This
provides applications with notification when layer 1 alarms are present and when the alarms have
cleared via GCEV_ALARM events. Applications have the ability to control the following:
Which alarms are blocking and non-blocking
Alarm flow (for example, notification of when the first alarm occurred and the last alarm
cleared) via gc_SetAlarmFlow( ) API

A GCSS7 Alarm Source Object (ASO), which is a module in GCAMS that handles the SS7 layer 1
alarms, supports this functionality. The GCSS7 ASO resides in the GCSS7 Call Control Library for
the SS7 Boards and pertains to SS7 layer 1 alarms only. The ASO handles the Line Interface Unit
(LIU) indications from the underlying stack and the alarm notification.
When using SS7 Boards, alarms are recognized on a span (trunk) basis. Once an alarm is detected,
all open channels on that span receive a GCEV_BLOCKED event. When the alarm is cleared, open
channels receive a GCEV_UNBLOCKED event. Alarm notification (GCEV_ALARM event) is
disabled by default and must be enabled via gc_SetAlarmConfiguration( ). When alarm
notification is enabled, alarms (GCEV_ALARM events) are generated for each time slot on the
affected span. See the Dialogic Global Call API Programming Guide for more information.
Notes: 1. Using GCAMS, the application has the ability to set which alarms are blocking and nonblocking
as described in the Dialogic Global Call API Programming Guide. However, this capability
applies on a span basis only. Changing which alarms are blocking and non-blocking for one time
slot results in changing which alarms are blocking and non-blocking for all time slots on the

119
span. This is because all the time slots on the span use the same ASO, and once you change the
ASO configuration it affects all the time slots.
2. For SS7 technology, the gc_TransmitAlarms( ) and gc_StopTransmitAlarms( ) functions are
not supported on SS7 Boards since there are no interfaces in the underlying stack to support
transmission of layer 1 alarms.
3. Using the gc_GetAlarmParm( ) and gc_SetAlarmParm( ) functions to retrieve and set specific
alarm parameters, for example alarm triggers, is not supported.
The following code examples show how to enable reception of the GCEV_ALARM event and
process the GCEV_ALARM event.
Enable Reception of GCEV_ALARM Event

int EnableAlarmEvent()
{
int rc = gc_OpenEx();
if(rc != GC_SUCCESS) {
cout << "failed to open device" << endl;
return GC_ERROR;
} else {
Cout << "gc_OpenEx() called - device successfully opened" << endl;
}
rc = gc_SetAlarmNotifyAll();
if(rc != GC_SUCCESS) {
cout << "failed to enable reception of GCEV_ALARM event" << endl;
return GC_ERROR;
} else {
Cout << "gc_SetAlarmNotifyAll() called - successfully enabled reception of
GCEV_ALARM event" << endl;
}
return 0;
}
Processing of GCEV_ALARM Event

int ProcessGCEvent(METAEVENT *metaeventp)
{
Char alarm_name[30];
switch (metaeventp->evttype)
{
:
case GCEV_ALARM:
gc_AlarmNumberToName(ALARM_SOURCE_ID_SS7, alarm_number,
&alarm_name);
cout << "Received GCEV_ALARM because of " << alarm_name << endl;
break;
:
}
return 0;
}
120

5.11.2
Supported Alarms
The following list shows the alarms that are supported for SS7 Boards. The dagger symbol () next
to an alarm name indicates that the alarm is blocking by default. (The default can be changed using
the gc_SetAlarmConfiguration( ) function.)
SS7_FRAME_SYNC_LOSS (0xa)
Frame Sync Loss has been detected
SS7_FRAME_SYNC_OK (0xb)
Frame Sync has been cleared
SS7_AIS_DETECTED (0xc)
Alarm Indication Signal (AIS) has been detected
SS7_AIS_CLEARED (0xd)
AIS has been cleared
SS7_REMOTE_ALARM_DETECTED (0xe)
Remote Alarm has been detected
SS7_REMOTE_ALARM_CLEARED (0xf)
Remote Alarm has been cleared
SS7_PCM_LOSS (0x14)
Pulse Code Modulation (PCM) Loss has been detected
SS7_PCM_OK (0x15)
PCM Loss has been cleared
SS7_FRAME_SLIP (0x16)
Frame Slip has been detected
SS7_BER5 (0x19)
Bit Error Rate (BER) > 1 in 100,000 has been detected
SS7_BER5_CLEARED (0x1a)
BER5 has been cleared
SS7_BER3 (0x1b)
BER > 1 in 1,000 has been detected
SS7_BER3_CLEARED (0x1c)
BER3 has been cleared
5.11.3
SS7-Specific Event Cause Codes for Layer 1 Alarms

When an event is received, the gc_ResultInfo( ) function, or the gc_ResultValue( ) function
(deprecated), can be used to retrieve event cause code information.
When the gc_ResultInfo( ) function is used, the a_Info parameter is a pointer to a GC_INFO
structure that contains both the standard Global Call Software event cause code (gcValue
field), and an SS7-specific event cause code (ccValue field).
When the gc_ResultValue( ) function is used, function parameters point to a standard Global
Call Software event cause code (gc_resultp function parameter), and an SS7-specific event
cause code (cclib_resultp function parameter).

121
The SS7-specific event cause codes related to layer 1 alarms are listed and described in
Section 10.2, SS7-Specific Event Cause Codes, on page 162.
122

Building Dialogic Global Call

SS7 Applications
6.
This chapter describes the SS7-specific header files and libraries required when building
applications. Topics include:
Header Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Required Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Required System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
6.1
Header Files
When compiling Dialogic Global Call Software applications for the SS7 technology, it is
necessary to include the following header files in addition to the standard Global Call header files,
which are listed in the Dialogic Global Call API Library Reference and Dialogic Global Call
API Programming Guide:
Libgcs7.h
Contains defines and definitions specific to using the Dialogic Global Call SS7 Software.
Note:
6.2
The Libgcs7.h file has an include statement for the cc_s7.h file that contains many of the definitions
used by the Global Call SS7 Software. The cc_s7.h file should not be included directly when
developing Global Call SS7 applications.
Required Libraries
When building Dialogic Global Call Software applications for SS7 technology, it is not necessary
to link any libraries other than the standard Global Call library, libgc.lib.
6.3
Required System Software

The Dialogic System Software must be installed on the development system. See the Software
Installation Guide for your Dialogic software release for more information.

123
Building Dialogic Global Call SS7 Applications
124

Debugging Dialogic Global Call

SS7 Applications
7.
This chapter describes the tools available for testing and debugging SS7 applications. Topics
include:
SS7 Call Control Library Trace File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
SS7 Server Log File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
7.1
SS7 Call Control Library Trace File

When the library trace is enabled by the Library.LogFile and Library.LogLevels parameters in
the gcss7.cfg file or by calling the gc_StartTrace( ) function, a binary trace file is generated. The
trace file includes the following information:
Call control requests from the application
Events sent to the application
Messages sent to the SS7 Server
Messages received from the SS7 Server
Call state changes
Error conditions
The file includes real time stamps to mark when the events took place. Where applicable, the
concerned circuit and call are contained in the logged data. Trace entries contain time stamps in
milliseconds.
The trace file is in a binary format, as opposed to plain readable text, in order to improve system
performance and minimize the file size. Use the ss7trace utility to generate a readable text file
equivalent.
The following is a short extract from a library trace file:
24.03.2003 12:48
12:48 00.688 LocalConfigFile::Open(AutoTest.cfg) SUCCEEDED
12:48 00.809 GCDK product version: 3,0,0,3
12:48 01.119 ::>
s7_OpenEx(:N_dkB1T1:P_SS7:V_dxxxB1C1)
12:48 01.119
==> MT_CONFIG_REQ
size=2

125
Debugging Dialogic Global Call SS7 Applications
The following is a guide to the format of the text file that is generated from the binary library trace
file:
______ messages or calls to/from the application
| _____ Library
| | ____ messages to/from Server
| | |
v v v
<== Received from Server
<== [CID] Received from Server for LineDevice
==> [CID] Sent to Server by LineDevice
==> Sent to Server
::>
User's application call
::>
[CID] User's application call to LineDevice
<::
[CID] Message sent to the User's application by LineDevice
<::
Message sent to the User's application
<*** Received from MQ
Any other internal message
Note:
All error messages are prefixed with an ERROR: label and all warning messages are prefixed with
a WARNING: label.
For additional help analyzing the contents of the trace file, contact Dialogic Customer Support.
7.2
SS7 Server Log File

By default, logging is enabled, but it can be disabled by editing the Service.LogLevels parameter
in the gcss7.cfg file.
The Dialogic SS7 server writes logging information to the %DLGCROOT%\log\DlgcS7.log
(Windows) or the ${DLGCROOT}/log/DlgcS7.log (Linux) file. This binary file contains status
messages received from the SS7 stack, SIU failure indications, and circuit groups activation
information with real time stamps of when the information occurred.
The trace file is in a binary format, as opposed to plain readable text, in order to optimize system
performance and minimize the file size. Use the ss7trace utility to generate a readable text file
equivalent.
The following is a guide to the format of the text file that is generated from the binary SS7 server
log file:
______ messages to/from the library
| _____ Server
| | ____ messages to/from DK stack
| | |
v v v
<-- Received from DK stack
<-- [CID] Received from DK stack by Circuit
<-- <GID> Received from DK stack by Group
--> Sent to DK stack
--> [CID] Sent to DK stack by Circuit
--> <GID> Sent to DK stack by Group
==>
(d) Received from Application id number d
126

==>
<==
<==
***>
Note:
[CID] (d) Received by Circuit from Application id number d

[CID] (d) Sent by Circuit to Application id number d
(d) Sent to Application id number d
Received from MQ
Any other internal message
All error messages are prefixed with an ERROR: label and all warning messages are prefixed with
a WARNING: label.
For additional help analyzing the contents of the SS7 server log file, contact Dialogic Customer
Support.
Note:
It is possible to redirect all SS7 system environment trace messages to the Dialogic Global Call
SS7 server trace file so that all logging information is in one file. This is achieved using a
REDIRECT command in the system.txt file. See Section 3.1, SS7 System Environment
Configuration (system.txt), on page 37 for more information.

127
128

SS7-Specific Function
Information
8.
This chapter describes the Dialogic Global Call API functions that have additional functionality
or perform differently when used with SS7 technology. The function descriptions are presented
alphabetically and contain information that is specific to SS7 applications. Generic function
description information (that is, information that is not technology-specific) is provided in the
Dialogic Global Call API Library Reference.
Dialogic Global Call Functions Supported by SS7. . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Dialogic Global Call Function Variances for SS7. . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Dialogic Global Call Functions Supported by SS7
8.1
The following is a list of all functions in the Dialogic Global Call API library. The description
under each function indicates whether the function is supported, not supported, or supported with
variances.
Note:
For functions supported by Dialogic SS7 Boards in clear channel mode, see Section 3.7,
Configuring Dialogic SS7 Boards for Clear Channel Mode, on page 53.
gc_AcceptCall( )
Supported with variances described in Section 8.2.1, gc_AcceptCall( ) Variances for SS7, on
page 136.
gc_AcceptInitXfer( )
Not supported.
gc_AcceptModifyCall( )
Not supported.
gc_AcceptXfer( )
Not supported.
gc_AlarmName( )
Supported.
gc_AlarmNumber( )
Supported.
gc_AlarmNumberToName( )
Supported.
gc_AlarmSourceObjectID( )
Supported.
gc_AlarmSourceObjectIDToName( )
Supported.

129
SS7-Specific Function Information
gc_AlarmSourceObjectName( )
Supported.
gc_AlarmSourceObjectNameToID( )
Supported.
gc_AnswerCall( )
Supported with variances described in Section 8.2.2, gc_AnswerCall( ) Variances for SS7,
on page 136.
gc_Attach( ) (deprecated)
Supported.
gc_AttachResource( )
Not supported.
gc_BlindTransfer( )
Not supported.
gc_CallAck( )
Supported with variances described in Section 8.2.3, gc_CallAck( ) Variances for SS7, on
page 137.
gc_CallProgress( )
Not supported.
gc_CCLibIDToName( )
Supported.
gc_CCLibNameToID( )
Supported.
gc_CCLibStatus( ) (deprecated)
Supported.
gc_CCLibStatusAll( ) (deprecated)
Supported.
gc_CCLibStatusEx( )
Supported.
gc_Close( )
Supported.
gc_CompleteTransfer( )
Not supported.
gc_CRN2LineDev( )
Supported.
gc_Detach( )
Supported.
gc_DropCall( )
Supported with variances described in Section 8.2.4, gc_DropCall( ) Variances for SS7, on
page 137.
gc_ErrorInfo( )
Supported.
130

gc_ErrorValue( ) (deprecated)
Supported with variances described in Section 8.2.5, gc_ErrorValue( ) Variances for SS7, on
page 137.
gc_Extension( )
Supported with variances described in Section 8.2.6, gc_Extension( ) Variances for SS7, on
page 137.
gc_GetAlarmConfiguration( )
Supported.
gc_GetAlarmFlow( )
Supported.
gc_GetAlarmParm( )
Supported.
gc_GetAlarmSourceObjectList( )
Supported.
gc_GetAlarmSourceObjectNetworkID( )
Supported.
gc_GetANI( ) (deprecated)
Supported.
gc_GetBilling( )
Not supported.
gc_GetCallInfo( )
Supported with variances described in Section 8.2.7, gc_GetCallInfo( ) Variances for SS7,
on page 138.
gc_GetCallProgressParm( )
Not supported.
gc_GetCallState( )
Supported.
gc_GetConfigData( )
Not supported.
gc_GetCRN( )
Supported.
gc_GetCTInfo( )
Not supported.
gc_GetDNIS( ) (deprecated)
Supported with variances described in Section 8.2.8, gc_GetDNIS( ) Variances for SS7, on
page 138.
gc_GetFrame( ) (deprecated)
Not supported.
gc_GetInfoElem( ) (deprecated)
Not supported.

131
gc_GetLineDev( )
Supported.
gc_GetLinedevState( )
Supported.
gc_GetMetaEvent( )
Supported.
gc_GetMetaEventEx( ) (Windows extended asynchronous model only)
Supported.
gc_GetNetCRV( ) (deprecated)
Not supported.
gc_GetNetworkH( ) (deprecated)
Supported with variances described in Section 8.2.9, gc_GetNetworkH( ) Variances for SS7,
on page 139.
gc_GetParm( )
Supported with variances described in Section 8.2.10, gc_GetParm( ) Variances for SS7, on
page 139.
gc_GetResourceH( )
Supported.
gc_GetSigInfo( )
Supported with variances described in Section 8.2.11, gc_GetSigInfo( ) Variances for SS7,
on page 139.
gc_GetUserInfo( )
Not supported.
gc_GetUsrAttr( )
Supported.
gc_GetVer( )
Supported.
gc_GetVoiceH( ) (deprecated)
Supported.
gc_GetXmitSlot( )
Supported.
gc_HoldACK( )
Not supported.
gc_HoldCall( )
Supported with variances described in Section 8.2.12, gc_HoldCall( ) Variances for SS7, on
page 140.
gc_HoldRej( )
Not supported.
gc_InitXfer( )
Not supported.
132

gc_InvokeXfer( )
Not supported.
gc_LinedevToCCLIBID( )
Supported.
gc_Listen( )
Supported.
gc_LoadDxParm( )
Not supported.
gc_MakeCall( )
Supported with variances described in Section 8.2.13, gc_MakeCall( ) Variances for SS7, on
page 140.
gc_Open( ) (deprecated)
Supported.
gc_OpenEx( )
Supported with variances described in Section 8.2.14, gc_OpenEx( ) Variances for SS7, on
page 141.
gc_QueryConfigData( )
Not supported.
gc_RejectInitXfer( )
Not supported.
gc_RejectModifyCall( )
Not supported.
gc_RejectXfer( )
Not supported.
gc_ReleaseCall( ) (deprecated)
Supported.
gc_ReleaseCallEx( )
Supported.
gc_ReqANI( )
Not supported.
gc_ReqModifyCall( )
Not supported.
gc_ReqMoreInfo( )
Supported.
gc_ReqService( )
Not supported.
gc_ResetLineDev( )
Supported with variances described in Section 8.2.15, gc_ResetLineDev( ) Variances for
SS7, on page 142.
gc_RespService( )
Not supported.

133
gc_ResultInfo( )
Supported.
gc_ResultMsg( ) (deprecated)
Supported.
gc_ResultValue( ) (deprecated)
Supported with variances described in Section 8.2.16, gc_ResultValue( ) Variances for SS7,
on page 143.
gc_RetrieveAck( )
Not supported.
gc_RetrieveCall( )
Supported with variances described in Section 8.2.17, gc_RetrieveCall( ) Variances for SS7,
on page 143.
gc_RetrieveRej( )
Not supported.
gc_SendMoreInfo( )
Supported.
gc_SetAlarmConfiguration( )
Supported.
gc_SetAlarmFlow( )
Supported.
gc_SetAlarmNotifyAll( )
Supported.
gc_SetAlarmParm( )
Supported.
gc_SetAuthenticationInfo( )
Not supported.
gc_SetBilling( )
Supported with variances described in Section 8.2.18, gc_SetBilling( ) Variances for SS7, on
page 143.
gc_SetCallingNum( ) (deprecated)
Supported.
gc_SetCallProgressParm( )
Not supported.
gc_SetChanState( )
Supported with variances described in Section 8.2.19, gc_SetChanState( ) Variances for
SS7, on page 143.
gc_SetConfigData( )
Supported with variances described in Section 8.2.20, gc_SetConfigData( ) Variances for
SS7, on page 143.
gc_SetEvtMsk( ) (deprecated)
Supported.
134

gc_SetInfoElem( ) (deprecated)
Supported with variances described in Section 8.2.21, gc_SetInfoElem( ) Variances for SS7,
on page 144.
gc_SetParm( )
Supported with variances described in Section 8.2.22, gc_SetParm( ) Variances for SS7, on
page 144.
gc_SetupTransfer( )
Not supported.
gc_SetUserInfo( )
Not supported.
gc_SetUsrAttr( )
Supported.
gc_SipAck( )
Not supported.
gc_SndFrame( ) (deprecated)
Not supported.
gc_SndMsg( ) (deprecated)
Supported with variances described in Section 8.2.23, gc_SndMsg( ) Variances for SS7, on
page 145.
gc_Start( )
Supported.
gc_StartTrace( )
Supported with variances described in Section 8.2.24, gc_StartTrace( ) Variances for SS7,
on page 145.
gc_Stop( )
Supported.
gc_StopTrace( )
Supported with variances described in Section 8.2.25, gc_StopTrace( ) Variances for SS7,
on page 146.
gc_StopTransmitAlarms( )
Not supported.
gc_SwapHold( )
Not supported.
gc_TransmitAlarms( )
Not supported.
gc_UnListen( )
Supported.
gc_util_copy_parm_blk( )
Supported.
gc_util_delete_parm_blk( )
Supported.

135
gc_util_find_parm( )
Supported.
gc_util_find_parm_ex( )
Supported.
gc_util_insert_parm_ref( )
Supported.
gc_util_insert_parm_ref_ex( )
Supported.
gc_util_insert_parm_val( )
Supported.
gc_util_next_parm( )
Supported.
gc_util_next_parm_ex( )
Supported.
gc_WaitCall( )
Supported.
Dialogic Global Call Function Variances for SS7
8.2
The Dialogic Global Call function variances that apply when using SS7 technology are described
in the following sections. See the Dialogic Global Call API Library Reference for generic
(technology-independent) descriptions of the Global Call API functions.
Notes: 1. For SS7, all the Global Call API functions that have a mode argument must be used in
asynchronous mode, except the routing functions (gc_Listen( ), gc_UnListen( ), and
gc_GetXmitSlot( )), which must be used in synchronous mode.
2. The SS7 specific constants and data structures are defined in the Libgcs7.h and cc_s7.h header
files. An application should only include Libgcs7.h (cc_s7.h being included by the latter).
8.2.1
gc_AcceptCall( ) Variances for SS7

The gc_AcceptCall( ) function is used to send an Address Complete Message (ACM). The rings
parameter is ignored.
8.2.2
gc_AnswerCall( ) Variances for SS7

The gc_AnswerCall( ) function is used to send an Answer Message (ANM). In the case of ITU-T
operation, if no ACM message has been sent, the gc_AnswerCall( ) function sends a Connect
message (CON) instead of an ANM message. The rings parameter is ignored.
136

8.2.3
gc_CallAck( ) Variances for SS7

The GCST_GETMOREINFO and GCST_SENDMOREINFO states must be enabled by issuing
the gc_SetConfigData( ) function with a target_type of GCTGT_GCLIB_CHAN and a
target_ID of a line device, and passing the GCSET_CALLSTATE_MSK set ID and the
GCACT_ADDMSK parameter ID with one of the following values:
GCMSK_GETMOREINFO_STATE
GCMSK_SENDMOREINFO_STATE
See the gc_SetConfigData( ) function description in the Dialogic Global Call API Library
Reference and the section on Call State Configuration in the Dialogic Global Call API
Programming Guide for more information.
8.2.4
gc_DropCall( ) Variances for SS7

The gc_DropCall( ) function sends a Release message (REL) to the SS7 stack if the active call has
not been released by the other side. The REL message contains an SS7 cause translated from a
Global Call cause specified as an argument to the gc_DropCall( ) function. Otherwise, the
gc_DropCall( ) function sends a Release Complete message (RLC).
Bits 8 to 11 from the gc_DropCall( ) parameter are transparently packed into the location field of
the cause value. See the Cause Indicators section in ITU-T Recommendation Q.763, Signaling
System No. 7 - ISDN User Part Formats and Codes for more information.
8.2.5
gc_ErrorValue( ) Variances for SS7

The SS7 call control library provides both standard Global Call Software error codes and
SS7-specific error codes (cclib_errorp argument), which are useful when diagnosing function
failures. See Chapter 10, SS7-Specific Error Codes and Event Cause Codes for more
information. The error codes are also listed in the cc_s7.h header file, which is included by
including the Libgcs7.h file when compiling and building applications.
Note:
8.2.6
The gc_ErrorValue( ) function is deprecated. The preferred alternative is gc_ErrorInfo( ).
gc_Extension( ) Variances for SS7

The gc_Extension( ) function and corresponding GCEV_EXTENSION event are used to support
the Continuity Check feature.
For the GCEV_EXTENSION event, the extevtdatap field of the METAEVENT structure is a
pointer to an EXTENSIONEVTBLK structure. The ext_id member of EXTENSIONEVTBLK can
be:
S7_EXT_CONTCHECK - Indicating the beginning of a Continuity Check
S7_EXT_CONTCHECK_END - Indicating the end of a Continuity Check

137
The parmblk field of the EXTENSIONEVTBLK structure contains additional information. The
parmblk field is of type GC_PARM_BLK and contains only a GC_PARM_DATA structure. The
set_ID of GC_PARM_DATA is S7SET_CONTCHECK, and the parm_ID is
S7PARM_CONTCHECK_TYPE. The parm_data_size is sizeof(int).
Note:
In earlier releases of the Dialogic Global Call SS7 Software, S7SET_ parameter sets and
S7PARM_ parameter IDs were defined with values that are different than the current release. An
application that uses the S7SET_ and S7PARM_ defines must be recompiled with the correct
header file from the current release.
For an outbound, out-of-call Continuity Check request, the application can use the gc_Extension( )
function with an ext_id of S7_EXT_REQUESTCONTCHECK. See Section 5.9.2, Outbound
Continuity Check, on page 116 for more information.
For an outbound, in-call Continuity Check request, the application must use the gc_MakeCall( )
function. See Section 8.2.13, gc_MakeCall( ) Variances for SS7, on page 140 for more
information.
8.2.7
gc_GetCallInfo( ) Variances for SS7

The gc_GetCallInfo( ) function can retrieve the following information:
CATEGORY_DIGIT
The calling party category for the call.
DESTINATION_ADDRESS
The destination address. This method of retrieving the destination address is preferred over the
equivalent gc_GetDNIS( ) function.
ORIGINATION_ADDRESS
The origination address. This method of retrieving the origination address is preferred over the
equivalent gc_GetANI( ) function.
PRESENT_RESTRICT
The calling party presentation restriction.
REDIRECTING_NUMBER
The destination address before the last redirection (forward or diversion).
Other info_id values are not currently supported for SS7. The functionality of the U_IES
(Unformatted Information Elements) info_id can be obtained by using the more appropriate
gc_GetSigInfo( ) function that associates messages with Global Call events. See Section 8.2.11,
gc_GetSigInfo( ) Variances for SS7, on page 139 for more details.
8.2.8
gc_GetDNIS( ) Variances for SS7

The gc_GetDNIS( ) function returns the full DNIS string available, including any digits received in
overlap mode after the Initial Address Message (IAM).
Note:
138
The gc_GetDNIS( ) function is deprecated; use gc_GetCallInfo( ).

8.2.9
gc_GetNetworkH( ) Variances for SS7

The gc_GetNetworkH( ) function is supported for backward compatibility only. The function can
be used to retrieve the network device handle associated with the line device. For circuits located
on a Dialogic Network Interface Board, the returned handle can then be used when invoking
Dialogic DTI functions. For circuits located on a Dialogic SS7 Board, the returned handle will
be the same as the specified line device. This handle cannot be used with DTI functions.
Typical usage of this function was to perform routing of a Global Call line device (dt_listen( ),
dt_getxmitslot( )). However, this call control library supports the Global Call API routing
functions (gc_Listen( ), gc_GetXmitSlot( )) that can be used regardless of the type of network
interface device (DTI or SS7) and allow correct operation of a loopback in a circuit for inbound
continuity checks. See Section 5.9.1, Inbound Continuity Check, on page 115 for more
information. Therefore, for routing of SS7 line devices, it is strongly recommended to always use
the Global Call API functions instead of the DTI functions. This makes the network device type
transparent to the application.
See Section 5.4, SCbus or CT Bus Routing, on page 111 for more on routing.
Note:
8.2.10
The gc_GetNetworkH( ) function is deprecated. The preferred alternative is

gc_GetResourceH( ).
gc_GetParm( ) Variances for SS7

The gc_GetParm( ) function can be used to retrieve the following parameters:
GCPR_CALLINGPARTY
Default calling party address.
GCPR_IGNORE_BCI
Inhibits the Dialogic Global Call SS7 Software from analyzing the Backward Call Indicator
(BCI) in incoming ACM messages and alerting the application of the call only when the
Called partys status indicator fields are set to Subscriber Free. When this parameter is set
to 1, the Global Call SS7 Software ignores the BCI content and always sends the
GCEV_ALERTING event to the application in response to an incoming ACM ISUP message.
By default, this parameter is set to 0.
GCPR_MINDIGITS
The minimum number of digits to collect before reporting an OFFERED call.
GCPR_RECEIVE_INFO_BUF
The size, that is, the number of messages that can be stored in the cyclic buffer. Messages can
be retrieved using the gc_GetSigInfo( ) function. See Section 8.2.11, gc_GetSigInfo( )
Variances for SS7, on page 139 for details.
8.2.11
gc_GetSigInfo( ) Variances for SS7

The gc_GetSigInfo( ) function enables an application to retrieve the content of the message that
triggered an event. This can be used if the application requires access to some SS7 specific message
parameter that is not directly accessible using another Dialogic Global Call function. It is then up
to the application to parse the message and extract the information it requires.

139
Since events are delivered to the application using an asynchronous mechanism (Dialogic
Standard Runtime Library (SRL) event queue), it is possible that a subsequent message may
already be received and other events may already be put in the queue by the time the application
calls the gc_GetSigInfo( ) function. Therefore, the SS7 call control library stores messages in a
cyclic buffer so that the application can retrieve a message associated with a particular event. The
event for which the application wishes to retrieve the associated message is specified by passing the
Global Call metaevent to the function.
The maximum number of messages that can be stored in the cyclic buffer is configurable by using
the gc_SetParm( ) function and specifying the GCPR_RECEIVE_INFO_BUF parameter. There
is one cyclic buffer for each circuit. Since, by default, the cyclic buffer is configured to store
0 (zero) messages, an application that wishes to use the gc_GetSigInfo( ) function must set the
GCPR_RECEIVE_INFO_BUF parameter for each line device. For most practical uses of this
mechanism, a cyclic buffer depth of 8 messages should be sufficient, although the Global Call SS7
library limits this number to 777 in order to prevent extremely inefficient memory use. See
Section 8.2.22, gc_SetParm( ) Variances for SS7, on page 144 for more information.
Note:
The third parameter in the gc_GetSigInfo( ) function signature, info_id, is currently not used by
the SS7 call control library. It must be set to zero unless otherwise specified.
The returned messages contain 2 bytes indicating the length at the beginning of the buffer followed
by the message data that is encoded as specified in the Application Message - User Data Format
section in the SS7 Protocols ISUP Programmers Manual (Issue 12).
The following code demonstrates the use of gc_GetSigInfo( ):
METAEVENT metaevt;
gc_GetMetaEvent(&metaevt);
char buffer[322]; // max size of message + length
if (GC_SUCCESS == gc_GetSigInfo(m_ldid, buffer, 0, &metaevt)) {
S7_IE_BLK *blk_p = (S7_IE_BLK *)buffer;
// further parsing of an obtained message
} else {
// process error here
}
Notes: 1. The cc_s7.h file mistakenly defines S7_MAXLEN_IEDATA as 254. The correct value is 320.
2. The S7_SIGINFO_BLK and S7_IE structures defined in the cc_s7.h file can be used for parsing
of received messages, but should never be used for allocation of buffers.
8.2.12
gc_HoldCall( ) Variances for SS7

At any time after a call is in the Connected state, the application can call the gc_HoldCall( )
function to put the call in the Suspended state. The application receives a GCEV_HOLDACK event
indicating that the call has entered the Suspended state. The call remains in the Suspended state
until the gc_RetrieveCall( ) function is called with the same CRN to resume the call. See
Section 8.2.17, gc_RetrieveCall( ) Variances for SS7, on page 143 for related information.
8.2.13
gc_MakeCall( ) Variances for SS7

The SS7 call control library supports the timeout parameter regardless of the fact that the
gc_MakeCall( ) function can be used in ASYNC mode only.
140

The GC_MAKECALL_BLK data structure contains a cclib field. When the cclib field is set to
zero, default values are used for all call setup parameters. When the cclib field is set to a pointer to
an S7_MAKECALL_BLK data structure that contains parameters usually set in an Initial Address
Message (IAM), the specified fields overwrite the default values in the IAM.
The S7_MAKECALL_BLK structure contains the following IAM parameters:
destination_number_type
destination_number_plan
internal_network_number
origination_phone_number
origination_number_type
oringination_number_plan
calling_party_category
origination_present_restrict
origination_screening
forward_call_indicators
trans_medium_req
satellite_indicator
echo_device_indicator
continuity_check_indicator
user_to_user_indicators
Notes: 1. The fields in the S7_MAKECALL_BLK structure that are not used must be set to 0 (zero) before
calling the gc_MakeCall( ) function.
2. Other parameters can be added using the gc_SetInfoElem( ) function. See Section 8.2.21,
gc_SetInfoElem( ) Variances for SS7, on page 144 for more information.
3. It is the responsibility of the application to ensure that the parameters that are being added via the
S7_MAKECALL_BLK data structure are not duplicated in gc_SetInfoElem( ) calls for use with
the same gc_MakeCall( ). Otherwise, it is not possible to guarantee which parameter value will
be processed by the underlying stack.
The gc_MakeCall( ) function can be used to request an in-call continuity check. The
continuity_check_indicator in the S7_MAKECALL_BLK structure must be set to
CCI_CC_REQUIRED so that Global Call Software will send an SS7 IAM message with continuity
check to the network. See Section 5.9.2, Outbound Continuity Check, on page 116 for more
information.
8.2.14
gc_OpenEx( ) Variances for SS7

Dialogic Global Call Software device naming conventions apply to SS7 telephony devices. The
protocol name to use is SS7. A voice device name may be specified, in which case this device will
be opened and its handle will be available through the gc_GetVoiceH( ) function. An application
should use the following device name format:

141
N_network_device_name:P_SS7:V_voice_device_name
See the Dialogic Global Call API Library Reference for more on the device name format.
The result of specifying a voice device name in the Global Call device name given to
gc_OpenEx( ) is equivalent to opening the voice device separately, using dx_open( ), performing a
gc_Attach( ), then routing the network and the voice devices together. A voice device opened as
part of a Global Call line device can later be detached from the line device using gc_Detach( ). A
voice device that has been opened together with a Global Call line device but that has later been
detached from it is not closed during the corresponding gc_Close( ).
The network device that is specified is the physical time slot where the voice circuit is located. This
is completely independent of the signaling path. The latter need only be specified in the
configuration of the system. The circuit time slot can reside on a Dialogic Board that includes
network interfaces (for example, a Dialogic DM/V960-4T1 or a DM/V1200-4E1) or on a
Dialogic SS7 Board. It is also possible to specify virtual devices, not tied to any physical board.
For a Dialogic DM3 or Springware Board with network interfaces, the standard device names
are used: dtiBxTy where x is the logical board number and y is the logical circuit number
(from 1 to the number of circuit on the trunk, no gaps are left for unused time slots or time
slots used for signaling).
For Dialogic SS7 Boards, the device names used are: dkBxTy where x is 1 for the first trunk
of the board and 2 for the second trunk (if present) and y is the logical circuit number (same as
for Dialogic DTI Boards).
For virtual devices, the device names used are: dumBxTy where x and y are virtual trunk and
circuit numbers.
Note:
When a voice device is specified in the devicename string, a full duplex routing is established
between the network interface device and the voice resource. The full duplex routing is performed
regardless of whether the network device name is a DTI device (dtiBxTy, on a Dialogic Network
Interface Board) or an SS7 device (dkBxTy, on a Dialogic SS7 Board).
As part of executing gc_OpenEx( ), Dialogic Global Call SS7 Software will start initializing the
circuit. The application must wait for a GCEV_UNBLOCKED event to be received before it can
start using the opened line device.
8.2.15
gc_ResetLineDev( ) Variances for SS7

The gc_ResetLineDev( ) function releases any resource allocated to the circuit and any of its
associated calls and performs a reset of the telephony circuit.
This function also cancels gc_WaitCall( ) and sets the channel state to GCLS_INSERVICE. See
Section 8.2.19, gc_SetChanState( ) Variances for SS7, on page 143 for more information.
A GCEV_RESETLINEDEV event indicates successful completion of the function. Upon reception
of this event, the application may issue a new gc_WaitCall() in order to start receiving calls again.
142

8.2.16
gc_ResultValue( ) Variances for SS7

The call control library-specific result value will indicate the actual SS7 network cause value, if
available.
Note:
8.2.17
The gc_ResultValue( ) function is deprecated. The preferred alternative is gc_ResultInfo( ).
gc_RetrieveCall( ) Variances for SS7

An application can use the gc_RetrieveCall( ) function to resume a call previously placed in the
Suspended state by using the gc_HoldCall( ) function. The application receives a
GCEV_RETRIEVEACK event if the call is resumed successfully. If the network has placed the
call in the Suspended state, a call to gc_RetrieveCall( ) to resume the call will fail. See
Section 8.2.12, gc_HoldCall( ) Variances for SS7, on page 140 for related information.
8.2.18
gc_SetBilling( ) Variances for SS7

The gc_SetBilling( ) function may be used before calling gc_AcceptCall( ) or gc_AnswerCall( )
to control charging (charge or no-charge). After the gc_SetBilling( ) function is called, Dialogic
Global Call Software sets accordingly the BCI (Backward Call Indicator) parameter in each ACM
or CON message that it sends.
If the specified rate type is any value other than GCR_NOCHARGE, the charge indicator of
the BCI is set to charge.

If the specified rate type is GCR_NOCHARGE, the charge indicator of the BCI is set to no
charge.
The charge indicator is left in the default value in case the gc_SetBilling( ) function is not called by
the application.
8.2.19
gc_SetChanState( ) Variances for SS7

The gc_SetChanState( ) function allows an application to block a circuit. This release of
Dialogic Global Call SS7 Software will always perform maintenance blocking, whether the
specified state is GCLS_MAINTENANCE or GCLS_OUT_OF_SERVICE. Consequently, any
active call on the circuit will always proceed unaffected, but further calls will be blocked. Setting
the channel state to GCLS_INSERVICE unblocks the circuit.
8.2.20
gc_SetConfigData( ) Variances for SS7

The gc_SetConfigData( ) function is supported only for the following uses:
Enabling call states. For example, the gc_SetConfigData( ) function can be used to enable the
GCST_GETMOREINFO and GCST_SENDMOREINFO states that are used for overlap send
and receive. See Section 8.2.3, gc_CallAck( ) Variances for SS7, on page 137 and
Section 5.7, Using Overlap Send and Receive, on page 113 for more information.
Dynamically adding and deleting SS7 circuit groups at runtime. See Section 5.3,
Dynamically Adding and Deleting SS7 Circuit Groups, on page 106 for more information.

143
8.2.21
gc_SetInfoElem( ) Variances for SS7

The gc_SetInfoElem( ) function allows the application to add ISUP message parameters (that is,
information elements) to outgoing messages sent by the SS7 call control library while executing a
Dialogic Global Call call control function. The format of the information elements is typically
identical to the ISUP format, with the exception that all parameters are formatted as optional
parameter (parameter name, length, and contents). It is possible to add multiple information
elements in one gc_SetInfoElem( ) function call. The parameters must be put in an S7_IE_BLK
structure, a pointer to which is set in the cclib field of the GC_IE_BLK specified as argument to the
function. The following code fragment illustrates the use of the function:
/* Add User-to-user information to Initial Address Message */
S7_IE_BLK ie_blk;
GC_IE_BLK gc_ie_blk;
ie_blk.length = 5;
ie_blk.data[0] = 0x20;
ie_blk.data[2] = 'A';
ie_blk.data[3] = 'B';
ie_blk.data[4] = 'C';
/*
/*
/*
/*
/*
Parameter
Parameter
Parameter
Parameter
Parameter
name - User-to-user info */

length - 3 bytes */
value - 1st byte */
value - 2nd byte */
value - 3rd byte */
gc_ie_blk.gclib = NULL;
gc_ie_blk.cclib = &ie_blk;
if (gc_SetInfoElem(linedev, &gc_ie_blk) != GC_SUCCESS) /* Process error */
if (gc_MakeCall(linedev, &crn, "7124311", NULL, 15, EV_ASYNC) != GC_SUCCESS)
/* Process error */
Note:
8.2.22
Parameter values (such as 0x20 in the example above, which corresponds to the User-to-User
Information parameter) should correspond to parameter values from the ISUP/TUP specifications.
gc_SetParm( ) Variances for SS7

The gc_SetParm( ) function can be used to configure the following line device parameters:
GCPR_CALLINGPARTY
The default calling party address for the circuit. This parameter is overwritten by the one in the
S7_MAKECALL_BLK if specified. Use the paddress field of the GC_PARM union.
GCPR_IGNORE_BCI
This parameter inhibits the Dialogic Global Call SS7 Software from analyzing the Backward
Call Indicator (BCI) in incoming ACM messages and alerting the application of the call only
when the Called partys status indicator fields are set to Subscriber Free. When this
parameter is set to 1, the Global Call SS7 Software ignores the BCI content and always sends
the GCEV_ALERTING event to the application in response to an incoming ACM ISUP
message. Use the intvalue field of the GC_PARM union. By default, this parameter is set to 0.
GCPR_MINDIGITS
The minimum number of digits to collect before reporting an OFFERED call. An overlap
receive procedure is used in case the initial number of digits does not reach the minimum
number set using this function. Use the intvalue field of the GC_PARM union.
GCPR_RECEIVE_INFO_BUF
The depth of the cyclic IE buffer. Sets the number of messages that can be stored in the cyclic
buffer. The recommended number of messages is 8. Messages can be retrieved using the
144

gc_GetSigInfo( ) function. See Section 8.2.11, gc_GetSigInfo( ) Variances for SS7, on

page 139 for details. Use the intvalue field of the GC_PARM union.
GCPR_UNKNOWN_ISUP_MSGS
Enables the configuration of a line device to receive ISUP messages not recognized by the SS7
call control library. See Section 5.10, Sending and Receiving ISUP/TUP Messages, on
page 118 for more information.
8.2.23
gc_SndMsg( ) Variances for SS7

The gc_SndMsg( ) function enables sending of application-ISUP messages, as long as they do not
alter the call state or circuit state.
Messages must be formatted as required by the SS7 stack. This format is very similar to the ISUP
format with the exception that all message parameters are coded as optional parameters (parameter
name, length, and contents).
The ISUP message type (also know as primitive) is specified in the msg_type argument. The
message parameters are specified in the S7_IE_BLK pointed to by the cclib field of the
GC_IE_BLK given as an argument to this function. Multiple parameters can be put one after the
other in the data field of the S7_IE_BLK structure. The total length of the parameters section must
be set in the length field of the structure.
The following code fragment illustrates the use of gc_SndMsg( ) for SS7:
/* Send a Subsequent Address Message
* (SAM) with digits 234 (overlap sending)
*/
S7_IE_BLK ie_blk;
GC_IE_BLK gc_ie_blk;
ie_blk.length = 5;
/*
/*
/*
/*
/*
Parameter
Parameter
Parameter
Parameter
Parameter
1
1
1
1
1
name - Subsequent Number */

length - 3 bytes */
value - odd number of digits */
value - digits '2' and '3' */
value - digit '4' */
gc_ie_blk.gclib = NULL;
gc_ie_blk.cclib = &ie_blk;
ret = gc_SndMsg(linedev, crn, 0x02 /* SAM */, &gc_ie_blk);
Note:
8.2.24
Parameter values (for example, 0x05 which corresponds to the Subsequent Number parameter)
should correspond to parameter values from the ISUP/TUP specifications. Similarly, message type
values (for example, 0x02 in the gc_SndMsg( ) function call above) should correspond to message
type values from the ISUP/TUP specification.
gc_StartTrace( ) Variances for SS7

The gc_StartTrace( ) function starts SS7 call control library tracing. See Section 7.1, SS7 Call
Control Library Trace File, on page 125 for more information. Starting a trace on one channel
starts a process-wide tracing, that is, tracing on all circuits opened within the process in which
gc_StartTrace( ) was called. The function must be called on a circuit line device.

145
8.2.25
gc_StopTrace( ) Variances for SS7

The gc_StopTrace( ) function stops the process-wide tracing associated with a specific channel.
See Section 7.1, SS7 Call Control Library Trace File, on page 125. The function must be called
on a circuit line device.
146

SS7-Specific Data Structures

9.
This chapter describes the data structures that are specific to SS7 technology.
Note:
These data structures are defined in the cc_s7.h header file, but are included by including the
Libgcs7.h header file when compiling and linking applications. The cc_s7.h file should not be
included directly.
GCSS7_ISUP_CFG_CCTGRP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
GCSS7_TRUNK_CFG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
S7_IE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
S7_IE_BLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
S7_MAKECALL_BLK. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
S7_SIGINFO_BLK . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

147
GCSS7_ISUP_CFG_CCTGRP configures an ISUP circuit
GCSS7_ISUP_CFG_CCTGRP
configures an ISUP circuit
typedef struct {
unsigned long
version;
unsigned long
dpc;
unsigned short basic_cic;
unsigned short basic_cid;
unsigned long
cic_mask;
unsigned long
options;
unsigned char
user_inst;
unsigned char
user_id;
unsigned long
opc;
unsigned long
ssf;
unsigned char
variant;
unsigned long
option2;
} GCSS7_ISUP_CFG_CCTGRP;
Description
The GCSS7_ISUP_CFG_CCTGRP data structure configures an ISUP circuit group, which
matches the ISUP_CFG_CCTGRP configuration command in the config.txt file.
Field Descriptions
The fields of the GCSS7_ISUP_CFG_CCTGRP data structure are described as follows:
version
The version of the data structure. The initial version is 0x1000.
dpc
The Destination Point Code (DPC) for all circuits in the circuit group.
basic_cic
The first Circuit Identification Code (CIC) in the circuit group.
basic_cid
The Logical Circuit Identifier (CID) corresponding to the first CIC.
cic_mask
A 32-bit mask with bits set to indicate which circuits are to be allocated.
options
A 32-bit value containing run-time options for the ISUP circuit group.
user_inst
The instance number of the user application.
user_id
The user application module ID.
opc
The Originating Point Code (OPC) for all circuits in the circuit group.
ssf
The value to be used in the Sub_Service Field (SSF) of all ISUP messages.
variant
The protocol variant for this circuit group.
148

configures an ISUP circuit GCSS7_ISUP_CFG_CCTGRP
option2
A 32-bit value containing additional run-time options for the ISUP circuit group.

149
GCSS7_TRUNK_CFG configures a trunk device in a circuit group
GCSS7_TRUNK_CFG
configures a trunk device in a circuit group
typedef struct {
unsigned long
char
unsigned char
unsigned char
} GCSS7_TRUNK_CFG;
version;
trunk_name[20];
base_ts;
pref_siu;
Description
The GCSS7_TRUNK_CFG data structure configures a Global Call trunk device in a circuit group,
which matches the CGrp configuration command in the gcss7.cfg file.
Field Descriptions
The fields of the GCSS7_TRUNK_CFG data structure are described as follows:
version
The version of the data structure. The initial version is 0x1000.
trunk_name[20]
The physical device name where the circuits in the group are terminated (e.g., dtiB1 or dkB1).
base_ts
The first time slot of the trunk that corresponds the first circuit of the group.
pref_siu
The default SIU for the group.
150

describes an ISUP message parameter S7_IE
S7_IE
describes an ISUP message parameter
typedef struct {
unsigned char parm;
unsigned char length;
unsigned char value;
} S7_IE;
/* Parameter type */
/* Number of bytes in the value part */
/* First byte of the value part (there may be more) */
Description
The S7_IE data structure describes an ISUP message parameter. This structure should not be used
to allocate storage space for message parameters because its value field is defined as a single byte,
whereas an actual parameter value may be multi-byte. The S7_IE_BLK structure can be used to
allocate storage for a block of parameters, if required.
Field Descriptions
The fields of the S7_IE data structure are described as follows:
parm
The parameter type.
length
The number of bytes in the value part.
value
The first byte of the value part.

151
S7_IE_BLK contains ISUP message parameters
S7_IE_BLK
contains ISUP message parameters
typedef struct {
short length;
char data[S7_MAXLEN_IEDATA];
} S7_IE_BLK, *S7_IE_BLK_PTR;
/* must be less than MAXLEN_IEDATA

/* First IE (there may be more)
*/
*/
Description
The S7_IE_BLK data structure contains ISUP message parameters.
Field Descriptions
The fields of the S7_IE_BLK data structure are described as follows:
length
IE data block length, which must be less than S7_MAXLEN_IEDATA. This length includes a
trailing 0 that is included in each message.
Note: The cc_s7.h header file mistakenly defines S7_MAXLEN_IEDATA as 254. The
correct value is 320.
data[s7_MAXLEN_IEDATA]
Message parameters themselves, one after the other.
152

holds SS7-specific parameters S7_MAKECALL_BLK
S7_MAKECALL_BLK
holds SS7-specific parameters
typedef union {
struct ss7 {
unsigned char trans_medium_req;
/*
TMR_SPEECH
TMR_64K_UNREST
TMR_3DOT1K_AUDIO
TMR_64K_PREFERRED
TMR_2_64K_UNREST
TMR_386K_UNREST
TMR_1536K_UNREST
TMR_1920K_UNREST
TMR_3_64K_UNREST
TMR_4_64K_UNREST
TMR_5_64K_UNREST
TMR_7_64K_UNREST
TMR_8_64K_UNREST
TMR_9_64K_UNREST
...
TMR_23_64K_UNREST
TMR_25_64K_UNREST
...
TMR_29_64K_UNREST
*/
unsigned char destination_number_type;
/*
SS7_UNKNOWN_NUMB_TYPE
- spare
SS7_SUBSCRIBER_NUMBER
- Subscriber number (national use)
SS7_UNKNOWN_NATIONAL
- Unknown (national use)
SS7_NATIONAL_NUMBER
- National (significant) number
SS7_INTERNATIONAL_NUMBER - International number
SS7_NETWORK_SPECIFIC
- Network-specific number (national use)
*/
unsigned char destination_number_plan;
/*
SS7_UNKNOWN_NUMB_PLAN
- Unknown plan
SS7_ISDN_NUMB_PLAN
- ISDN numb. plan E.164
SS7_DATA_NUMB_PLAN
- Data numb. plan X.121
SS7_TELEX_NUMB_PLAN
- Telex numb. plan F.69
*/
unsigned char internal_network_number;
/*
INN_ALLOWED
- routing to internal network allowed
INN_NOT_ALLOWED
- routing to internal network not allowed
*/
unsigned char origination_number_type;
/*
SS7_UNKNOWN_NUMB_TYPE
- spare
SS7_SUBSCRIBER_NUMBER
- Subscriber number (national use)
SS7_UNKNOWN_NATIONAL
- Unknown (national use)
SS7_NATIONAL_NUMBER
- National (significant) number
SS7_INTERNATIONAL_NUMBER - International number
SS7_NETWORK_SPECIFIC
- Network-specific number (national use)
*/

153
S7_MAKECALL_BLK holds SS7-specific parameters
unsigned char origination_number_plan;

/*
SS7_UNKNOWN_NUMB_PLAN
- Unknown plan
SS7_ISDN_NUMB_PLAN
- ISDN numb. plan E.164
SS7_DATA_NUMB_PLAN
- Data numb. plan X.121
SS7_TELEX_NUMB_PLAN
- Telex numb. plan F.69
*/
char origination_phone_number[MAXPHONENUM];
unsigned char origination_present_restrict;
/*
PRESENTATION_ALLOWED
PRESENTATION_RESTRICTED
PRESENTATION_NOT_AVAILABLE
*/
unsigned char origination_screening;
/*
SCREEN_USER_PROVIDED
SCREEN_USER_PROVIDED_VERIFIED
SCREEN_USER_PROVIDED_FAILED
SCREEN_NETWORK_PROVIDED
*/
unsigned short calling_party_category;
/*
SS7_UNKNOWN_CATEGORY
SS7_FR_OPERATOR_CATEGORY
SS7_EN_OPERATOR_CATEGORY
SS7_GE_OPERATOR_CATEGORY
SS7_RU_OPERATOR_CATEGORY
SS7_SP_OPERATOR_CATEGORY
SS7_RESERVED_CATEGORY
SS7_ORDINARY_SUBS_CATEGORY
SS7_PRIORITY_SUBS_CATEGORY
SS7_DATA_CATEGORY
SS7_TEST_CATEGORY
SS7_PAYPHONE_CATEGORY
*/
unsigned short forward_call_indicators;
/* bitmask - see defines below */
void *usrinfo_bufp;
/* RFU */
unsigned char satellite_indicator;
/*
SI_NOSATELLITES
SI_1SATELLITE
SI_2SATELLITES
*/
unsigned char echo_device_indicator;
/*
EDI_ECHOCANCEL_NOTINCLUDED
EDI_ECHOCANCEL_INCLUDED
*/
unsigned char continuity_check_indicator;
/*
CCI_CC_NOTREQUIRED
CCI_CC_REQUIRED
CCI_CC_ONPREVIOUS
*/
154

unsigned char user_to_user_indicators;

long rfu[6];
} ss7;
} S7_MAKECALL_BLK,
Note:
/* RFU */
*S7_MAKECALL_BLK_PTR;
The comment /* bitmask - see defines below */ in the preceding code listing refers to the fact that
the bitmask is created using an OR operation on the defines from the header file.
Description
The S7_MAKECALL_BLK union contains SS7-specific parameter values for a specific call.
Field Descriptions
The fields of the S7_MAKECALL_BLK union are described as follows:
trans_medium_req
Specifies the format of the transmission medium requirement. Possible values are:
TMR_SPEECH speech
TMR_64K_UNREST 64 kbps unrestricted
TMR_3DOT1K_AUDIO 3.1 KhZ audio
TMR_64K_PREFERRED 64 kbps preferred
TMR_2_64K_UNREST 2x 64 kbps unrestricted
TMR_23_64K_UNREST
TMR_25_64K_UNREST
TMR_29_64K_UNREST
destination_number_type
Specifies the destination number type. Possible values are:
SS7_UNKNOWN_NUMB_TYPE Spare
SS7_SUBSCRIBER_NUMBER Subscriber number (national use)
SS7_UNKNOWN_NATIONAL Unknown (national use)
SS7_NATIONAL_NUMBER National (significant) number
SS7_INTERNATIONAL_NUMBER International number
SS7_NETWORK_SPECIFIC Network-specific number (national use)
destination_number_plan
Specifies the destination number plan. Possible values are:
SS7_UNKNOWN_NUMB_PLAN Unknown plan

155
S7_MAKECALL_BLK holds SS7-specific parameters
SS7_ISDN_NUMB_PLAN ISDN number plan E.164

SS7_DATA_NUMB_PLAN Data number plan X.121
SS7_TELEX_NUMB_PLAN Telex number plan F.69
internal_network_number
Specifies whether routing is allowed to an internal network. Possible values are:
INN_ALLOWED Routing to internal network allowed
INN_NOT_ALLOWED Routing to internal network not allowed
origination_number_type
Specifies the origination number type. Possible values are:
SS7_UNKNOWN_NUMB_TYPE Spare
SS7_SUBSCRIBER_NUMBER Subscriber number (national use)
SS7_UNKNOWN_NATIONAL Unknown (national use)
SS7_NATIONAL_NUMBER National (significant) number
SS7_INTERNATIONAL_NUMBER International number
SS7_NETWORK_SPECIFIC Network-specific number (national use)
origination_number_plan
Specifies the origination number plan. Possible values are:
SS7_UNKNOWN_NUMB_PLAN Unknown plan
SS7_ISDN_NUMB_PLAN ISDN number plan E.164
SS7_DATA_NUMB_PLAN Data number plan X.121
SS7_TELEX_NUMB_PLAN Telex number plan F.69
origination_phone_number [MAXPHONENUM]
Specifies the calling party address. If not specified, default to the address set using
gc_SetCallingNum( ) or gc_SetParm( ).
origination_present_restrict
Specifies the calling party address presentation restrictions. Possible values are:
PRESENTATION_ALLOWED Presentation allowed.
PRESENTATION_RESTRICTED Presentation restricted.
PRESENTATION_NOT_AVAILABLE Address not available.
origination_screening
Specifies calling party address screening. Possible values are:
SCREEN_USER_PROVIDED Address is user provided, not verified (National use
only).
SCREEN_USER_PROVIDED_VERIFIED Address is user provided, verified, and
passed.
SCREEN_USER_PROVIDED_FAILED Address is user provided, verified, and failed
(National use only).
SCREEN_NETWORK_PROVIDED Address is network provided.
calling_party_category
Information sent in the forward direction indicating the category of the calling party and, in
case of semi-automatic calls, the service language to be spoken by the incoming, delay, and
assistance operators. Possible values are:
SS7_UNKNOWN_CATEGORY Unknown category
SS7_FR_OPERATOR_CATEGORY French language operator
SS7_EN_OPERATOR_CATEGORY English language operator
SS7_GE_OPERATOR_CATEGORY German language operator
SS7_RU_OPERATOR_CATEGORY Russian language operator
156

SS7_SP_OPERATOR_CATEGORY Spanish language operator

SS7_RESERVED_CATEGORY Reserved
SS7_ORDINARY_SUBS_CATEGORY Ordinary subscriber
SS7_PRIORITY_SUBS_CATEGORY Priority subscriber
SS7_DATA_CATEGORY Specifies a data call using voice-band data.
SS7_TEST_CATEGORY Specifies a test call.
SS7_PAYPHONE_CATEGORY Specifies a pay phone call.
forward_call_indicators
Specifies forward call indicators. Bitmask built by ORing defines from the header file.
satellite_indicator
Specifies the presence of satellites along the voice path. Possible values are:
SI_NOSATELLITES No satellite
SI_1SATELLITE One satellite
SI_2SATELLITES Two satellites
echo_device_indicator
Specifies whether echo cancellation devices are being used. Possible values are:
EDI_ECHOCANCEL_NOTINCLUDED Echo cancellation devices are not being used.
EDI_ECHOCANCEL_INCLUDED Echo cancellation devices are being used.
continuity_check_indicator
Specifies whether a continuity check should be performed on the circuit as part of the call, if it
is being performed on a previous circuit, or if it is not requested at all. Possible values are:
CCI_CC_NOTREQUIRED Continuity check is not required.
CCI_CC_REQUIRED Continuity check is required.
CCI_CC_ONPREVIOUS Continuity check is being performed on the previous circuit.
user_to_user_indicators
Specifies the type of user-to-user service that is supported in the outbound call. Possible values
are:
UUI_UUS1_REQ_NE Service 1, request, non-essential
UUI_UUS1_REQ_E Service 1, request, essential
UUI_UUS1_RSP_P Service 1, response, provided
UUI_UUSx_RSP_P Service 1, 2, and 3, response, provided

157
S7_SIGINFO_BLK contains ISUP message information
S7_SIGINFO_BLK
contains ISUP message information
typedef struct {
short length;
/* length of SigInfo block plus 1 */
unsigned char prim;
/* ISUP primitive */
S7_IE data;
/* First IE of the message (there may be more) */
} S7_SIGINFO_BLK, *S7_SIGINFO_BLK_PTR;
Description
The S7_SIGINFO_BLK data structure contains ISUP messages as returned by the
gc_GetSigInfo( ) function. This structure should not be used to allocate storage space for message
parameters because its value field is defined as a single byte, whereas an actual parameter value
may be multiple bytes. The S7_IE_BLK structure can be used to allocate storage for a block of
parameters.
Field Descriptions
The fields of the S7_SIGINFO_BLK data structure are described as follows:
length
Block length, including the primitive byte (prim) and the parameters (data), plus 1 for the
NULL character.
prim
ISUP primitive (IAM, ANM, REL).
data
Message parameters, one after the other.
158

SS7-Specific Error Codes and

Event Cause Codes
10.
10
This chapter lists the supported SS7-specific error codes and event cause codes and provides a
description of each code. The codes are defined in the cc_s7.h header file, which is included by
including the Libgcs7.h in the application.
10.1
SS7-Specific Error Codes

When a function fails, the gc_ErrorInfo( ) function, or the gc_ErrorValue( ) function
(deprecated), can be used to retrieve error code information.
When the gc_ErrorInfo( ) function is used, the a_Infop parameter is a pointer to a GC_INFO
structure that contains both the standard Dialogic Global Call Software error value (gcValue
field), and an SS7-specific error value (ccValue field).
When the gc_ErrorValue( ) function is used, function parameters point to a standard Dialogic
Global Call Software error code (gc_errorp function parameter), and an SS7-specific error code
(cclib_errorp function parameter).
The SS7-specific error codes are presented in hex code value order. A dagger symbol () next to an
error code indicates that the error code is not currently supported.
S7ERR_NO_SESSION (0x8001)
No session was established with SS7 server.
S7ERR_UNSUPPORTED (0x8002)
Function or function parameter not supported. The code is returned when a user calls:
gc_CallAck( ) with GC_CALLACK_BLK->type=GCACK_SERVICE_INFO and
GC_CALLACK_BLK->service.info.info_type=ORIGINATION_ADDRESS
gc_CallAck( ) with GC_CALLACK_BLK->type=GCACK_SERVICE_PROC
gc_ReqMoreInfo( ) with info_id=ORIGINATION_ADDRESS
gc_SendMoreInfo( ) with info_id=ORIGINATION_ADDRESS
gc_Extension( ) with any ext_id that is not supported by the SS7 call control library
gc_GetCallInfo( ) with any info_id that is not supported by the SS7 call control library
S7ERR_INV_PARM (0x8003)
Invalid parameter.
S7ERR_INV_INFO_ID (0x8004)
Invalid call info ID.
S7ERR_INV_PARM_ID (0x8005)
Invalid parameter ID (in Set/GetParm).

159
SS7-Specific Error Codes and Event Cause Codes
S7ERR_INV_SIGINFO_SIZE (0x8006)
Invalid SigInfo buffer size.
S7ERR_LDEV_RELATED (0x8007)
Event is related to a LineDevice (therefore no CRN, no SigInfo).
S7ERR_NO_SIGINFO (0x8008)
No SigInfo was associated with the event.
S7ERR_NO_SCBUSCONNECTOR (0x8009)
Device does not support routing functions.
S7ERR_INV_DEVNAME (0x800A)
Invalid device name.
S7ERR_INV_STATE (0x800B)
Invalid state (Call/LineDev).
S7ERR_INV_CRN (0x800C)
Invalid CRN.
S7ERR_INV_CID (0x800D)
Internal error.
S7ERR_INV_LINEDEV (0x800E)
Invalid LineDevice.
S7ERR_INV_TRUNKDEV (0x800F)
Invalid TrunkDevice.
S7ERR_INV_CHANNEL (0x8010)
TrunkDevice has no such channel (ts).
S7ERR_NO_BASE_TS (0x8011)
BaseTimeSlot not defined for the trunk.
S7ERR_TLS_NULL (0x8012)
ThreadLocalStorage is NULL.
S7ERR_PING_EVENT (0x8013)
System error.
S7ERR_MSGQ_FULL (0x8014)
Internal error.
S7ERR_INV_PARM_SIZE (0x8015)
Internal error.
S7ERR_SRL (0x8016)
SRL error.
S7ERR_SRL_PUTEVT (0x8017)
SRL PutEvt error.
S7ERR_DTI_GENERIC (0x8018)
Unspecified DTI error.
S7ERR_DTI_OPEN (0x8019)
Error opening DTI device.
160

S7ERR_DTI_GETXMIT (0x801A)
Error getting DTI TX time slot.
S7ERR_DTI_LISTEN (0x801B)
Error listening on DTI device.
S7ERR_DTI_UNLISTEN (0x801C)
Error unlistening on DTI device.
S7ERR_LOG_ATTACH (0x801D)
Error attaching file to logger.
S7ERR_NOMEM (0x801E)
Out of memory.
S7ERR_GCT_SYSTEM (0x801F)
Error in GCT system.
S7ERR_COM_SYSTEM (0x8020)
Error in COM system.
S7ERR_TIMER_INIT (0x8021)
Error initializing Timer subsystem.
S7ERR_TIMER_ACTIVE (0x8022)
Attempt to start an already active timer.
S7ERR_NO_MORE_CRN (0x8023)
Too many CRNs allocated on the LineDevice.
S7ERR_ISUP_CODING (0x8024)
Generic error while coding ISUP message.
S7ERR_ISUP_DECODING (0x8025)
Generic error while decoding ISUP message.
S7ERR_INV_MODE (0x8026)
SYNC/ASYNC mode not supported.
S7ERR_OPEN_VOICE (0x8027)
Error opening voice device (in gc_OpenEx).
S7ERR_NO_VOICE (0x8028)
No voice resource attached.
S7ERR_VOX_LISTEN (0x8029)
Error in routing voice resource (dx_listen function failed).
S7ERR_VOX_GETXMIT (0x802A)
Error in routing voice resource (dx_getxmitslot function failed).
S7ERR_INIT_EVTMSK (0x802B)
Internal error.
S7ERR_CIRCUIT_IN_USE (0x802C)
Circuit is already in use in another process.
S7ERR_SERVICE_NOT_READY (0x802D)
SS7 server is not running or not correctly initialized.

161
S7ERR_NOT_ATTACHED (0x802E)
Internal error.
S7ERR_WATCHDOG_FAIL (0x802F)
Internal error.
S7ERR_NO_MORE_DIGITS (0x8030)
No additional digit can be obtained.
S7ERR_GC_CME (0x8031)
Internal error.
S7ERR_GC_DB (0x8032)
Internal error.
S7ERR_SRL_DEPOSIT (0x8033)
Internal error.
S7ERR_UNKNOWN (0x80FF)
Unknown error.
10.2
SS7-Specific Event Cause Codes

When an event is received, the gc_ResultInfo( ) function, or the gc_ResultValue( ) function
(deprecated), can be used to retrieve event cause code information.
When the gc_ResultInfo( ) function is used, the a_Info parameter is a pointer to a GC_INFO
structure that contains both the standard Dialogic Global Call Software event cause code (gcValue
field), and an SS7-specific event cause code (ccValue field).
When the gc_ResultValue( ) function is used, function parameters point to a standard Dialogic
Global Call Software event cause code (gc_resultp function parameter), and an SS7-specific event
cause code (cclib_resultp function parameter).
The SS7-specific event cause codes are presented below in hex code value order (within the event
type that they are related to). A dagger symbol () next to an event cause code indicates that the
event cause code is not currently supported.
S7RV_SUCCESS (0x4000)
Success, no error.
S7RV_TIMEOUT (0x4001)
A timeout has occurred, for example, in a gc_MakeCall( ).
S7RV_GLARE (0x4003)
Indicates a glare condition.
S7RV_MGMT (0x400A)
Event caused by management operation.
162

The following event cause codes relate to the GCEV_BLOCKED and GCEV_UNBLOCKED
events:
S7RV_SIU_TRANSFER (0x4002)
Circuit blocked for transferring its group between units. This cause value is used to indicate
the beginning and the end of the circuits group transfer between units.
S7RV_BLK_LOCAL_MAINT (0x4004)
Circuit is locally maintenance blocked or unblocked.
S7RV_BLK_LOCAL_HARD (0x4005)
Circuit is locally hardware blocked or unblocked.
S7RV_BLK_REMOTE_MAINT (0x4006)
Circuit is remotely maintenance blocked or unblocked.
S7RV_BLK_REMOTE_HARD (0x4007)
Circuit is remotely hardware blocked or unblocked.
S7RV_BLK_MTP (0x4008)
Blocked or unblocked at MTP level (DPC not available).
S7RV_BLK_SIU_DOWN (0x4009)
Blocked or unblocked based on SIU status.
S7RV_LOCAL_RESET (0x400b)
Circuit locally reset. Possible local maintenance and hardware blocking are cleared. (related to
GCEV_UNBLOCKED only)
S7RV_REMOTE_RESET (0x400c)
Circuit remotely reset. Possible remote maintenance and hardware blocking are cleared.
(related to GCEV_UNBLOCKED only)
The following event cause codes relate to the GCEV_EXTENSION event, where the extension ID
(ext_id) is S7_EXT_CONTCHECK:
S7RV_CC_INBOUND (0x4080)
Inbound continuity check; must apply loopback.
S7RV_CC_OUTBOUND (0x4081)
May proceed with the outbound continuity check.
The following event cause codes relate to the GCEV_EXTENSION event, where the extension ID
(ext_id) is S7_EXT_CONTCHECK_END:
S7RV_CCEND_INBOUND_FAILURE (0x4090)
Inbound continuity check failed.
S7RV_CCEND_INBOUND_SUCCESS (0x4091)
Inbound continuity check succeeded.
S7RV_CCEND_OUTBOUND_ERROR (0x4092)
Outbound continuity check encountered an error.
S7RV_CCEND_OUTBOUND_GLARE (0x4093)
Outbound continuity check ended due to glare with incoming IAM or CCR.

163
S7RV_CCEND_OUTBOUND (0x4094)
Outbound continuity check ended by the S7_EXT_SENDCONTCHECKRESULT.
The following event cause codes relate to the GCEV_MOREDIGITS and GCEV_MOREINFO
events:
S7RV_INFO_PRESENT_ALL (0x40a0)
The requested information is available.
S7RV_INFO_PRESENT_MORE (0x40a1)
The requested information is available. More information can be requested.
S7RV_INFO_SOME_TIMEOUT (0x40a2)
The requested information is not yet available. Only some of the information is present.
S7RV_INFO_SOME_NOMORE (0x40a3)
The requested information is not yet available. No more information is coming in.
S7RV_INFO_NONE_TIMEOUT (0x40a4)
The requested information is not available. No information came in.
S7RV_INFO_NONE_NOMORE (0x40a5)
The requested information is not available. No information came in and none is expected.
S7RV_INFO_SENT (0x40a6)
The information has been sent successfully.
S7RV_DESTINATION_ADDRESS_REQ (0x40a7)
The destination information has been requested by the remote side.
S7RV_ORIGINATION_ADDRESS_REQ (0x40a8)
The origination information has been requested by the remote side.
The following event cause codes relate to layer 1 alarms:
S7RV_PCM_LOSS (0x40a9)
Loss of PCM stream.
S7RV_PCM_OK (0x40aa)
Recovery of PCM stream.
S7RV_FRAME_SYNC_LOSS (0x40ab)
Loss of frame synchronization.
S7RV_FRAME_SYNC_OK (0x40ac)
Recovery of frame synchronization.
S7RV_AIS_DETECTED (0x40ad)
Alarm Indication Signal (AIS) alarm detected.
S7RV_AIS_CLEARED (0x40ae)
Alarm Indication Signal (AIS) alarm cleared.
S7RV_FRAME_SLIP (0x40af)
Frame slip detected.
S7RV_BER3 (0x40b0)
A Bit Error Rate (BER) of greater than 1 in 1,000 has been detected.
164

S7RV_BER3_CLEARED (0x40b1)
A BER of greater than 1 in 1,000 has been cleared.
S7RV_BER5 (0x40b2)
A BER of greater than 1 in 100,000 has been detected.
S7RV_BER5_CLEARED (0x40b3)
A BER of greater than 1 in 100,000 has been cleared.
S7RV_REMOTE_ALARM_DETECTED (0x40b4)
Detection of remote alarm.
S7RV_REMOTE_ALARM_CLEARED (0x40b5)
Clearing of remote alarm.

165
166

Supplementary Reference
Information
1.
11
This chapter lists references to publications about SS7 technology.

The following publications provide information about SS7 fundamentals:
Signaling System No. 7: Protocol, Architecture and Services
Lee Dryburgh, Jeff Hewett

Ciscopress.com
ISBN 1-58705-040-4
Common-Channel Signaling, Richard J. Manterfield, IEEE Telecommunications Series 26
1991, Peter Peregrinus Ltd. on behalf of the IEEE

ISBN 0 86341 240 8
Signaling System #7, Travis Russel
1995, McGraw-Hill
ISBN 0-07-054991-5
ISDN & SS7 - Architectures for Digital Signaling Networks, Uyless Black
1997, Prentice Hall

ISBN 0-13-259193-6
The following web sites provide background information on SS7 fundamentals when SS7 signaling
is used over a circuit-switched network:
Dialogic Signaling and SS7 Products Public Network Signaling Tutorial -
http://www.dialogic.com/support/helpweb/signaling/tutorial/ss7.htm
Web ProForums - http://www.iec.org/online/tutorials/ss7/
The following web site provides more information on SS7:

Dialogic Signaling and SS7 Products web page -
http://www.dialogic.com/support/helpweb/signaling/default.htm
All URLs and site content were verified at the time of writing.

167
Supplementary Reference Information
168

Glossary
CT Bus: A time division multiplex (TDM) bus that provides 1024, 2048, or 4096 time slots for exchanging voice,
fax, or other network resources on a PCI (H.100) or CompactPCI (H.110) backplane. The Enterprise Computer
Telephony Forum (ECTF) developed the H.100 hardware compatibility specification that defined the CT Bus, a
high-performance mezzanine bus. The CT Bus works with both SCbus and Multivendor Integration Protocol
(MVIP) compatible products. The ECTF implementation of the CT Bus for CompactPCI bus is called the H.110
standard.
Dialogic Configuration Manager (DCM): A Windows application the enables the configuration of
Dialogic products.
DPC: Destination Point Code. Identifies the address (point code) of the SS7 network node to which a Message
Signal Unit (MSU) should be directed.
DTI: A generic term for a Dialogic Network Interface Board, such as Dialogic DM/V960-4T1, Dialogic
DM/V1200-4T1, etc.
E1: A digital transmission link that carries information at the rate of 2,048 Mbps. This is the rate used by European
carriers to transmit thirty 64 Kbps digital channels for voice or data calls, plus one 64 Kbps channel for signaling,
and one 64 Kbps channel for framing (synchronization) and maintenance.
Global Call SS7 Software: The software and libraries that implement Dialogic Global Call Software on SS7.
IPC: Inter Process Communication. In the SS7 system software environment, IPC refers to the method by which
modules communicate with each other using messages.
ISDN: Integrated Services Digital Network. A service that offers simultaneous digital data and voice
communication over a single copper pair wire in residential and business phone connections. There are two basic
flavors, BRI (Basic Rate Interface) which is 144 Kbps and designed for the desktop, and PRI (Primary Rate
Interface) which is 1.544 Mbps and designed for telephone switches, computer telephony, and voice processing
systems.
ISUP: ISDN User Part. A layer in the SS7 protocol stack. Defines the messages and protocol used in the
establishment and tear-down of voice and data calls over the public switched network, and to manage the trunk
network on which they rely.
Message Transfer Part: Layers 1 to 3 of the SS7 protocol stack equivalent to the Physical, Data Link, and
Network layers in the OSI protocol stack. See also MTP1, MTP2, and MTP3.
MTP1: Message Transfer Part Level 1. Defines the physical and electrical characteristics of the signaling links of
the SS7 network. Signaling links use DS0 channels and carry raw signaling data at a rate of 56 Kbps or 64 Kbps (56
Kbps is currently the more common implementation).
MTP2: Message Transfer Part Level 2. Provides link-layer functionality. Ensures that two end points of a signaling
link can reliably exchange signaling messages. It provides error checking, flow control, and sequence checking.

169
MTP3: Message Transfer Part Level 3. Provides network-layer functionality. Ensures that messages can be
delivered between signaling points across the SS7 network regardless of whether the signaling points are directly
connected. It provides node addressing, routing, alternate routing, and congestion control.
OPC: Originating Point Code. Identifies the address (point code) of the SS7 network node from which a Message
Signal Unit (MSU) originated.
PSTN: Public Switched Telephone Network. The worldwide voice telephone network accessible to all those with
telephones and access privileges.
RSI: Remote Socket Interface.
SCbus: The standard bus for communicating within an SCSA node. The SCbus features a hybrid bus architecture
consisting of a serial message bus for control and signaling, and a 16-wire TDM data bus.
SCCP: Signal Connection Control Part. A layer in the SS7 protocol stack that allows a software application at a
specific node in an SS7 network to be addressed. It also supports Global Title Translation, which frees an
originating signaling point from having to know every possible destination to which a message may have to be
routed.
SCP: Service Control Point. Databases that provide information necessary for advanced call processing
capabilities.
Signaling Link: A bidirectional transmission path for signaling, comprising two data channels operating together
in opposite directions at the same data rate.
SIU: The Dialogic SS7 server solution.
SP: Signaling Point. Any point in a signaling network capable of handling SS7 control messages. Examples of
Signaling Points are SSP (Service Switching Point), STP (Signal Transfer Point), and SCP (Service Control Point).
SS7: Signaling System Number 7. A common channel signaling standard that defines the procedures and
protocols required for the connection of network elements in the Public Switched Telephone Network (PSTN).
SS7 System Software Environment: A collective name for the software modules that make up SS7 system
environment.
SSP: Service Switching Point. Telephone switches (end offices or tandems) equipped with SS7-capable software
and terminating signaling links. They generally originate, terminate, or switch calls.
STP: Service Transfer Point. A signaling point capable of routing control messages to another signaling point.
STPs receive and route incoming signaling messages towards the proper destination and perform specialized
routing functions.
T1: A digital transmission link with a capacity of 1.544 Mbps. T1 uses two pairs of normal twisted wires and can
handle 24 voice conversations, each one digitized at 64 Kbps.
TCAP: Transaction Capabilities Part. A layer in the SS7 protocol stack that defines the messages and protocol
used to communicate between applications (deployed as subsystems) in SS7 nodes. TCAP is used for database
170

services such as calling card, 800, and AIN, as well as switch-to-switch services including Repeat Dialing and Call
Return.
TUP: Telephone User Part. The predecessor to ISUP. TUP was employed for call control purposes within and
between national networks, both wireline and wireless. ISUP adds support for data, advanced ISDN, and IN
(Intelligent Networks). See also ISUP.
User Part: A generic name given to an SS7 stack protocol at layer 4 or above, such as ISUP, TUP, ICAP, MAP,
etc.

171
172

Index
A
ACM
gc_SetBilling(_) 143
ANM
gc_AnswerCall(_) 136
Application Service Elements
definition 21
dual-resilient configuration 113

benefits of 113
circuit groups
controlling priority 106
clear channel
how to use 112
CON
gc_AnswerCall 136
config.txt file 39
configuration
config.txt file 39
CT Bus 40
Dialog SS7 software 44
ISUP 41
protocol stack 39
SS7 system software environment 37
system.txt file 37
continuity check 115
inbound 115
outbound in-call 117
outbound out-of-call 116
continuity test
role of GCEV_EXTENSION event 137
CT Bus
configuration 40
gc_AnswerCall(_)
variances for SS7 136
gc_DropCall(_)
gc_ErrorValue(_)
gc_GetCallInfo(_)
gc_GetParm(_)
gc_MakeCall(_)
gc_Open Ex(_)
gc_ResetLineDev (_)
gc_SetBilling(_)
gc_SetInfoElem(_)
gc_SetParm(_)
gc_SndMsg(_)
gc_Start(_)
gc_StopTrace(_)
GCEV_EXTENSION event
in continuity tests 137
glare
handling 105
Global Call SS7 Library
function of 34
data structure
S7_IE 151
Dialogic SS7 software
configuration 44
IAM
B
BCI
gc_MakeCall(_) 141

173
ISDN
SS7 support for 20
ISUM message support
gc_SetInfoElem(_) 144
ISUP
configuration 41
definition 20
resume call 114

RLC
gc_DropCall(_) 137
routing
functions for 111
S7_IE data structure 151

S7_IE_BLK data structure 158
SCCP
definition 20
Service Control Point
definition 17
Signal Transfer Point
definition 17
signaling link
definition 18
Signaling Point
definition 17
Signaling System 7
definition 17
SIU-based system
starting 55
SS7 board system
starting 54
SS7 protocol stack
description 19
structure of 19
SS7 Server
function of 34
SS7 stack
function of 35
SS7 system software environment
configuration 37
stack
description 19
starting
an SIU system 55
suspend call 114
system.txt file 37
log file
enabling 44
M
Message Transfer Part
description 20
MTP1
definition 20
MTP2
definition 20
MTP3
definition 20
multiple hosts
connecting to SIUs 112
N
NSP
definition 20
O
OMAP
definition 21
OSI 7-layer reference model 19
overlap send and receive
handling 113
P
priority
of circuit groups 106
protocol stack
configuration 39
description 19
R
REL
T
TCAP
definition 21
time slot
assignment for SS7 boards 111
using time slot 16 112
gc_DropCall(_) 137
174

TUP
configuration 43
definition 20

175
176


Dialogic SS7 Call Flow

Uploaded by

Copyright:

Available Formats

Dialogic SS7 Call Flow

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Dialogic SS7 Call Flow

Uploaded by

Copyright:

Available Formats

Dialogic Global Call SS7

Copyright and Legal Notice

Dialogic Global Call SS7 Technology Guide November 2008

Dialogic Global Call Architecture for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

SS7 and Computer Telephony . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Configuration and Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

SS7 System Environment Configuration (system.txt) . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dialogic Global Call SS7 Technology Guide November 2008

SS7 Call Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

3.10.1 Proving the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Dialogic Global Call SS7 Technology Guide November 2008

SS7-Specific Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Header Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

Debugging Dialogic Global Call SS7 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Handling of Glare Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Building Dialogic Global Call SS7 Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

4.6.1 Glare Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

SS7 Call Control Library Trace File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

SS7-Specific Function Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Dialogic Global Call Functions Supported by SS7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Dialogic Global Call SS7 Technology Guide November 2008

Dialogic Global Call Function Variances for SS7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

SS7-Specific Data Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

SS7-Specific Error Codes and Event Cause Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

SS7-Specific Error Codes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Supplementary Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Dialogic Global Call SS7 Technology Guide November 2008

Signaling and Information Transfer Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Dialogic Global Call SS7 Technology Guide November 2008

Dialogic SS7 Board Example Configurations - Features and Benefits. . . . . . . . . . . . . . . . . . . 25

Dialogic Global Call SS7 Technology Guide November 2008

Global changes: Made global changes to reflect Dialogic brand.

Dialogic Global Call SS7 Technology Guide November 2008

Dialogic Global Call SS7 Technology Guide November 2008

General: Updates to acknowledge Intel NetStructure as a registered trademark.

Dialogic Global Call SS7 Technology Guide November 2008

Table 1, Intel NetStructure SS7 Board Configurations - Features and Benefits:

Dialogic Global Call SS7 Technology Guide November 2008

About This Publication

Dialogic Global Call SS7 Technology Guide November 2008

About This Publication

How to Use This Publication

building Global Call Software applications that use SS7 technology.

debugging Global Call Software applications that use SS7 technology.

specific Global Call Software functions used with SS7 technology.

specific event cause codes.

Dialogic Global Call SS7 Technology Guide November 2008

About This Publication

http://www.dialogic.com/support/ (for Dialogic technical support)

Dialogic Global Call SS7 Technology Guide November 2008

About This Publication

Dialogic Global Call SS7 Technology Guide November 2008

SS7 and Computer Telephony

Dialogic Global Call SS7 Technology Guide November 2008

Dialogic Global Call SS7 Technology Guide November 2008

SS7 Protocol Stack

Figure 2. SS7 Protocol Stack Layers

Dialogic Global Call SS7 Technology Guide November 2008

Lower Stack Layers for SS7 over a Circuit-Switched

Upper Stack Layers