GlobalCall for SS7 Status Update October 2003

Page 2 GlobalCall SS7 - Overview  Provides GlobalCall Call Control Library for SS7 ISUP and TUP protocols  Only deals with switched circuit call control (non-circuit stacks such as TCAP/INAP/MAP are not supported through GlobalCall)  Works on top of all Intel® NetStructure™ SS7 Boards (including BlueBranch) and Signaling Interface Units  Provides integration within Intel® Dialogic® software architecture (GC API, CTbus, DCM...) on Windows and Linux

Page 3 GlobalCall SS7 - Supported Configurations  All Intel® NetStructure™ SS7 Boards –Only one board supported per chassis –Signaling can be received on SS7 board or routed over CTbus from Intel/Dialogic E1/T1 interface board(s) –Circuits can terminate on SS7 board or on Intel Dialogic E1/T1 interface board(s)  All Intel® NetStructure™ SIU –Single SIU with single or multiple hosts –Dual-Resilient SIU with single or multiple hosts  Same application binaries, only configuration changes

Page 4 GlobalCall SS7 - Features  Supports any number of application processes  Supports all basic call control GC functions gc_MakeCall, gc_AnswerCall, gc_DropCall …  Advanced GC functions allow direct access to ISUP or TUP protocol messages gc_SendMsg, gc_SetInfoElem, gc_GetSigInfo  Automatic and transparent handling of Dual- Resilient SIU operations

Page 5 GlobalCall SS7 – Some history  1998 – v1.0 ‘Early Adopter’ (patch for DNA3.1)  1999 – v1.0 Beta Program (patch for DNA3.2)  2000 – v2.0 generally available in DNA3.3  2001 – v2.1 under development (first GC/SS7 release for Linux)  2002 – v2.1 generally available in SR5.1 SP1 for Linux  2003 – v3.0 generally available in SR5.1 FP1 for Linux and is available as a patch for all other System Releases (5.1, and 6.0 cPCI)

Page 6 What’s new in version 3.0? (1)  Common code for Windows and Linux –Increases software quality and guarantees simultaneous availability of all updates on both platforms  Simplified architecture –GC/SS7 applications don’t require a GCT module ID anymore –Less installed files  Robust configuration parsing –Makes it easier to troubleshoot most frequent config.txt and system.txt errors  Support for new SS7HDPD4TE board (BlueBranch)

Page 7 What’s new in version 3.0? (2)  Circuits are maintenance-blocked at start-up –Prevents incoming calls on configured circuits as long as there is no application controlling them  Log files are in binary format –Allows better performance –Less disk storage is used –A trace decoder is provided to get an ASCII file  Improved logging mechanisms –Comprehensive traces allows easy system debugging –S7_log output can be redirected to GlobalCall service/daemon

Page 8 GC SS7 and NBD System Releases for Windows System Release Includes GC/SS7 Comments Windows SR Yes Version 2.0 Use GC/SS7 3.0 overlay (1) to take advantage of the latest improvements if required Windows SR SP1 Yes Version 2.0 “A” Use GC/SS7 3.0 overlay (1) to take advantage of the latest improvements if required Windows SR FP1 Yes Version 2.0 “E” Use GC/SS7 3.0 overlay (1) to take advantage of the latest improvements if required Windows SR 6.0 cPCI No Use GC/SS7 3.0 overlay (1) (1)The 3.0 overlay is a set of files that will overwrite the previous GC/SS7 version 2.0

Page 9 GC SS7 and NBD System Releases for Linux System Release Kernel updates Includes GC/SS7 Comments Linux SR 5.1 RH7.1: RH7.2: No Use GC/SS7 3.0 overlay to take advantage of the latest improvements if required Linux SR 5.1 SP1 RH7.2: RH7.3: Yes version 2.1 “E” (SS7 cards not supported) Use GC/SS7 3.0 overlay to take advantage of the latest improvements if required (e.g. to use SS7 cards) Linux SR 5.1 FP1 RH7.2 and 7.3: Yes version Use GC/SS7 3.0 overlay to take advantage of the latest improvements if required Linux SR 6.0 cPCI RH7.3: No Use GC/SS7 3.0 overlay to take advantage of the latest improvements if required - SS7 cards not supported at this time (1) (1)This is due to PTR#31307 More info on

Page 10 Why should I upgrade to GC/SS7 v3.0?  v3.0 is still a living branch (it will go in production in SR6.0 PCI) - new builds are coming out with new features, improvements and updates (v2.x is a dead branch, no more updates)  Using the latest v3.0 build allows to: –benefit from the latest improvements (e.g. Auto- detection of SS7 board and SIU in the DCM) –use SS7 boards on Linux SR5.1 SP1 (v2.1 only supports SIU) –use SS7HDPD4TE board (aka BlueBranch)  You can check v3.0 build history on

Page 11 How do I get the latest GC/SS7 v3.0 overlay? Depending on your region, send an to:  Elizabeth Russo (US)  Hongdong Chen (APAC)  Bertrand Guimfacq (EMEA) … and ask for the overlay with some information such as the customer name, the reason why he/she needs to upgrade to the latest v3.0 build etc. There is no formal process as such, and no licensing either.

Page 12  Production version of GlobalCall SS7 v3.0 will be part of SR6.0 PCI Windows and Linux (it will remain available for older SR’s too)  Features for next GlobalCall SS7 release (v3.1) have now to be discussed – your input is greatly appreciated!!! Please send your questions, feedback or suggestions about GlobalCall SS7 to What’s coming next?

Page 13 Backup Materials

Page 14 Architecture Overview (1)  Intel SS7 modules communicate with each other by putting messages into one another’s message queue  Intel/Dialogic SS7 service needs to send and receive ISUP messages and therefore must live within an Intel SS7 module (like any application written directly to the Intel SS7 direct API)  consequently, Dialogic SS7 service must have a module id assigned (via system.txt) – it is usually set to 0x4d

Page 15 Architecture Overview (2) Application 1 GC API Libgcs7 Application 2 GC API Libgcs7 Intel SS7 Stack GlobalCall SS7 service / daemon [module id 0x4d]

Page 16 GlobalCall SS7 service/daemon  Processes ISUP messages from SS7 stack and manages call state machines for all circuits  Translates call control command from application into ISUP messages that it sends to SS7 stack  Handles management messages received from SS7 stack (e.g. Dual Resilient Operations - circuit groups activation and transfer)  Performs start-up tasks, such as CTbus transmit timeslots assignment  Started together with all Intel/Dialogic system components (via DCM on Windows or dlstart on Linux)

Page 17 GlobalCall SS7 library  Translates GlobalCall API functions invoked by applications into call control commands that it sends to GlobalCall SS7 service  Proxies the call state machines (which are managed in the service) to the application  Sends GlobalCall events to applications (GCEV_OFFERED, GCEV_DISCONNECTED…)

Page 18 Call Scenarios (1) gc_WaitCall( )  WaitCall_REQ Prepared for handling IAM messages CRN assigned  GCEV_OFFERED  Offered_IND  IAM gc_GetDNIS( )  (optional) Return immediately  with DNIS gc_GetANI( )  (optional) Return immediately  with ANI Network Initiated Inbound Call Application Library Service/Daemon Intel SS7 Stack

Page 19 gc_AcceptCall()  Accept_REQ  ACM   GCEV_ACCEPTCALL gc_AnswerCall()  Answer_REQ  ANM (*)   GCEV_ANSWERED Call Scenarios (2) * in ITU mode, in case no ACM has been sent (no gc_AcceptCall() done) CON message is sent instead of ANM. Application Library Service/Daemon Intel SS7 Stack Network Initiated Disconnect gc_DropCall( )   GCEV_DROPCALLRLC  Application Library Service/Daemon Intel SS7 Stack  GCEV_DISCONNECTED  Disconnected_IND  REL gc_ReleaseCallEx()   GCEV_RELEASECALL Release call resources

Page 20 Call Scenarios (3) Application Initiated Outbound Call gc_MakeCall()  MakeCall_REQ  IAM  Application Library Service/Daemon Intel SS7 Stack  GCEV_ALERTING  Alerting_IND  ACM  GCEV_CONNECTED  Connected_IND  ANM gc_MakeCall()  MakeCall_REQ  IAM  Application Library Service/Daemon Intel SS7 Stack  GCEV_CONNECTED  Connect_IND  CON In ITU operation, the following scenario is also possible:

Page 21 Call Scenarios (4) Or if ‘no indication’ is received in ACM: gc_MakeCall()  MakeCall_REQ  IAM  Application Library Service/Daemon Intel SS7 Stack  GCEV_ALERTING  Alerting_IND  CPG  GCEV_CONNECTED  Connected_IND  ANM  ACM

Page 22 Call Scenarios (5) Application Terminated Call gc_DropCall()  DropCall_REQ  REL  Application Library Service/Daemon Intel SS7 Stack  GCEV_DROPCALL  RLC gc_ReleaseCallEx()   GCEV_RELEASECALL Release call resources

Page 23 Version tag  “ ” means GCSS7 v3.0 build 4 and sub-version (intermediate build) 2  Same version tag applies for Windows and Linux  Version tag is included in all the installed binary files: –Windows: RightClick->Property->Version->File Version –Linux: $ strings FileName | grep Version