Application Note SS7 and Media Processing Boards Circuit-Switched Telephony Systems Creating SS7 Circuit- Switched Applications using ® Dialogic Global Call API Installation and Configuration Application Note An Introduction to Using Dialogic and Dialogic Diva Board Technologies in a Common Server Executive Summary This application note describes the installation and conŢguration of ® circuit-switched telephony systems that combine Dialogic Signaling ® Boards and Dialogic DM3 Media Boards on platforms based on Linux ® and Windows operating systems. An Introduction to Using Dialogic and Dialogic Diva Board Technologies in a Common Server Application Note Table of Contents Introduction........................................................................................................... 2 System Description................................................................................................ 2 Hardware Requirements................................................................................. 2 Software Requirements .................................................................................. 2 ® Step 1 – Installing the Dialogic Software ............................................................... 2 Linux Operating System.................................................................................. 2 ® Windows Operating System........................................................................... 5 Locating the Appropriate Clear Channel Media Load....................................... 6 ® Step 2 – Installing the Dialogic SS7 Development Package ................................. 7 Linux Operating System.................................................................................. 7 ® Windows Operating System........................................................................... 7 ® Step 3 – ConŢguring the Dialogic Signaling Distributed Architecture .................... 8 Software (system.txt and conŢg.txt) system.txt....................................................................................................... 8 conŢg.txt ........................................................................................................ 9 Step 4 – Proving the SS7 ConŢguration ............................................................... 12 ® Step 5 – ConŢguring the Dialogic Global Call API for SS7 Software (gcss7.cfg) ...... 13 Step 6 – Starting the Software.............................................................................. 14 Step 7 – Running the gc_basic_call_model Demo ............................................... 15 Troubleshooting ................................................................................................... 15 Summary ............................................................................................................ 15 References.......................................................................................................... 15 Appendix A: Linux system.txt File ........................................................................ 16 Appendix B: Linux conŢg.txt File ......................................................................... 17 Appendix C: Linux gcss7.cfg.txt File .................................................................... 18 ® Appendix D: Windows system.txt File ................................................................. 21 ® Appendix E: Windows conŢg.txt File................................................................... 22 ® Appendix F: Windows gcss7.cfg.txt File.............................................................. 23 Acronyms............................................................................................................ 25 For More Information........................................................................................... 25 1 ® Application Note Creating SS7 Circuit-Switched Applications using Dialogic Global Call API System A — Linux System B — Windows DM/V1200-4E1 DM/V1200-4E1 SPCI4 SPCI4 Figure 1. Sample System ConŢguration • SS7 code Ţle for SPCI4 (ss7.dc3) V1.13 (or Introduction greater) This application note describes the installation, ® • Dialogic System Release 6.1 for Linux Service conŢguration, and run-time operation of two computer ® Update 268 (or greater) telephony systems that combine a Dialogic Signaling ® Board and a Dialogic DM3 Media Board. ® Windows Operating System ® These systems will be connected back-to-back using • Microsoft Windows XP crossover cables. The gc_basic_call_model demo ® ® • Dialogic SS7 Development Package for Windows ® will show how the Dialogic Global Call API library V5.02 (or greater) facilitates the development of SS7 telephony applications • SS7 code Ţle for SPCI4 (SS7.DC3) V1.13 (or running on top of the ISDN User Part (ISUP) signaling greater) protocol. ® ® • Dialogic System Release 6.0 PCI for Windows System Description Service Update 166 (or greater) In this application note, System A runs Red Hat Notes: ® Enterprise Linux v3 and System B runs Windows XP; ® 1. Dialogic Signaling Distributed Architecture however, readers are free to use the same operating system (SigDiA) software can be downloaded from on both System A and System B (see Figure 1). Since the http://www.dialogic.com/support/helpweb/ conŢguration Ţles given in the appendices are operating signaling/default.htm system independent, this should not cause any problems. ® 2. More information about Dialogic System Releases Hardware Requirements and Service Updates can be found on • 2 PCs with Pentium III processors, 512 MB RAM http://resource.dialogic.com/telecom/support/ ® • 2 Dialogic SPCI4 SS7 Interface Boards with ISUP or releases/serviceUpdates/index.htm ISUP-L license buttons ® ® ® • 2 Dialogic DM/V1200-4E1 Voice Boards (Dialogic Step 1 – Installing the Dialogic Software ® Voice Boards, Dialogic DM/V-A Media Boards or Linux Operating System ® Dialogic DM/V-B Media Boards in PCI) ® Refer to the Dialogic System Release 6.1 for Linux • 2 H.100 CT Bus cables Software Installation Guide (http://www.dialogic.com/ • 2 crossover E-1 cables manuals/sr61lin/release_install.pdf) for instructions on ® how to install the Dialogic System Release software. Software Requirements ® Note that you select “Dialogic DMV/DMN/DMT” and Linux Operating System the Global Call SS7 Support Software packages at the • Red Hat Enterprise Linux V3 Update 4 installation menu. ® • Dialogic SS7 Development Package for Linux V5.05 (or greater) 2 ® Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Application Note ® 1. When the Dialogic System Release Software is successfully installed, start the config.sh script to copy and load ® the DM3 driver Ţles. When this process completes, the Dialogic DM3 Media Board should be detected and you should be prompted with this menu: Dialogic(R) Configuration Manager - Main Screen ___________________________________________________________________________________ 1) Dialogic(R)) DM3 Board Summary 2) Dialogic(R) Board Summary (NO BOARDS) 3) Dialogic(R) IPT Board Summary 4) TDM Bus Settings ___________________________________________________________________________________ (s to save, x to save & quit, q to quit) the configuration ? for help and ! for navigation help You can only configure one board at a time. Enter the number associated with the product category of the board you want to configure :1 2. Select item 1 to get the list of DM3 Media Boards that are detected on your system: Dialogic (R) DM3 Board Summary _______________________________________________________________________________ You must configure or disable each board shown. After a board is configured, a valid PCD file name is displayed in the PCD File Name column. ________________________________________________________________________________ Thumb Board Log PCD Wheel Status Model ID File Name _______________________________________________________________________________ 0) C DM/V1200-4E1 1 NOT_SET ________________________________________________________________________________ (s to save, x to save & quit, q to quit) the configuration p to return to Dialogic(R) Configuration Manager - Main Screen ? for help and ! for navigation help Enter the Thumb Wheel of the board to configure: 0 3. Enter the Thumb Wheel number of the board you want to conŢgure (0 in this case). Modify Board Settings _______________________________________________________________________________ These are the current settings for the board selected: Physical Slot...... : 0 Model Name......... : DM/V1200-4E1 Logical ID......... : 1 Board Status....... : Configured PCD File Name...... : NOT_SET CONFIG File Name... : NOT_SET ________________________________________________________________________________ The following items can be modified: 1) Specify the PCD File 2) Trunk Configuration 3) Protocol Development Kit (PDK) Configuration (NOT APPLICABLE) 4) Modify NIC Configuration (NOT APPLICABLE) 5) Copy Configuration From Board 6) Advanced Board Settings _______________________________________________________________________________ (s to save, x to save & quit, q to quit) the configuration p to return to Dialogic(R) DM3 Board Summary ? for help and ! for navigation help Enter the number of the item to modify: 1 3 ® Application Note Creating SS7 Circuit-Switched Applications using Dialogic Global Call API 4. Select item number 1 (Specify the PCD File) and you should be prompted with a list of available media loads for the board you are using. Specify the PCD File _______________________________________________________________________________ A Product Configuration Description (PCD) file must be selected to configure your board. The corresponding CONFIG file will be automatically selected. The following PCD files are valid for your board: 1) ml1_qs_dass2.pcd 2) ml1_qs_dpnss.pcd 3) qs_isdn_net5.pcd 4) ml1_qs_net5.pcd 5) qs_isdn_qsige1.pcd 6) ml1_qs_qsige1.pcd 7) qs_r2mf.pcd 8) ml1_qs_r2mf.pcd 9) ml1_qs_ts16.pcd _______________________________________________________________________________ * is current setting (s to save, x to save & quit, q to quit) the configuration p to return to Modify Board Settings ? for help and ! for navigation help Enter the number corresponding to the PCD file you want to select: 1 5. Select a clear channel media load, such as: ® • ml1_qs_ts16.pcd for a regular Dialogic DM/V1200-4E1 Media Board ® • ml2_qsa_ts16.pcd for a Dialogic DM/V1200A-4E1 Media Board ® Note: When using a Dialogic DM/V-B Media Board, select Trunk ConŢguration (option 2 in the menu below) and assign E1CC on your E1 trunks. Modify Board Settings _______________________________________________________________________________ These are the current settings for the board selected: Physical Slot...... : 4 Model Name......... : DMV1200BTEP Logical ID......... : 2 Board Status....... : Configured PCD File Name...... : qsb_default.pcd CONFIG File Name... : qsb_default.config ____________________________________________________________________________________________ _The following items can be modified: 1) Specify the PCD File 2) Trunk Configuration 3) Protocol Development Kit (PDK) Configuration (NOT APPLICABLE) 4) Modify NIC Configuration (NOT APPLICABLE) 5) Copy Configuration From Board 6) Advanced Board Settings ________________________________________________________________________________ _ (s to save, x to save & quit, q to quit) the configuration p to return to Dialogic(R) DM3 Board Summary ? for help and ! for navigation help Enter the number of the item to modify: 1 ® 6. From the Dialogic ConŢguration Manager - Main Screen, type the number 4 and press Enter to select the TDM Bus Settings option. 7. Select the “” menu (item number 2 in the TDM Bus Settings menu) and make sure that your Dialogic DM/V board ® is set as “Secondary Master Board” (item number 2), because the Dialogic SS7 board is to be the primary CT Bus clock master. 4 ® Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Application Note Figure 2. Forcing a Hardware Detection ® ® Windows Operating System • Demos — Installs the sample programs for Dialogic ® boards and, among others, the Refer to the Dialogic System Release 6.0 PCI for Windows gc_basic_call_model application, which will Software Installation Guide be used to make and receive calls between the two (http://www.dialogic.com/manuals/sr60winpci/release_ systems. install.pdf) for installation instructions. ® Once the Dialogic System Release Software has been 1. When the “Select Features” window appears during installed and the system has been rebooted, do the installation, check these options: following: • Development Package — Allows for recompiling the ® 2. Open up the Dialogic ConŢguration Manager application, if it is needed. ® 3. Right click on the DM3 device and select “Restore • Core Runtime Package — Installs Dialogic board Device Default” to force a re-detection of your drivers, Ţrmware, and parameter Ţles. ® Dialogic hardware, as shown in Figure 2. 5 ® Application Note Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Figure 3. Selecting a Clear Channel Media Load 4. Select a clear channel media load (for example, 3. Change the parameter value to 6 to conŢgure the ml1_qs_ts16.pcd for a regular DM/V1200-4E1), as corresponding trunk in clear channel mode: shown in Figure 3. [lineAdmin.1] … SetParm=0x1602,6 ! SignalingType Locating the Appropriate Clear Channel Media (CAS=4, CCS=5, Clear=6) Load … If you cannot Ţnd an appropriate clear channel media 4. Repeat this operation for the other trunks you want ® load for your Dialogic DM3 Media Board (for example, to set in clear channel mode ([lineAdmin.2], ® for a Dialogic DM/V960-4T1 Voice Board or for a [lineAdmin.3], etc.) ® Dialogic DM/IP Board), then manually edit the corre- ® 5. For Windows and Linux operating systems, the sponding *.config Ţle in order to conŢgure the E-1 or FCD Ţle is automatically created when the PCD Ţle T-1 trunk in clear channel mode as follows: and modiŢed CONFIG Ţle are downloaded to the 1. Identify the *.config Ţle that corresponds to the board. media load you have chosen for your DM3 Media ® 6. Re-start the Dialogic Service, and verify that there Board (for example, ml1_qs_cas.config) and are now 24 T-1 time slots or 31 E-1 time slots on the open it in a text editor. clear channel trunks, using “Devmapdump”: 2. Search for the Ţrst occurrence of the 0x1602 c:\Program Files\Dialogic\bin\ parameter: Devmapdump > a.txt notepad a.txt [lineAdmin.1] … SetParm=0x1602,4 ! SignalingType (CAS=4, CCS=5, Clear=6) … 6 ® Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Application Note ® Windows Operating System Step 2 – Installing the Dialogic® SS7 ® Development Package The Dialogic SS7 Development Package for Windows ® has an Install Shield script that copies the Ţle and drivers 1. Download the Dialogic Signaling Distributed to the appropriate directories. More information can be Architecture (SigDiA) software components from the found in Section 2.1 of the SS7 Boards Programmer’s Dialogic web site. The download sections discussed Manual for SPCI2S, SPCI4 and CPM8 (see the For More in this application note can be found at Information section). http://www.dialogic.com/support/helpweb/signal- ing/default.htm. 1. The SPCI device driver must be manually registered to the system using the following command: 2. Go to the Product SpeciŢc on the web page and in Section 2.7 download the SS7 Binary (code Ţle) for c:\> net start septel ® ® Dialogic SPCI2S SS7 Interface Board and Dialogic 2. Once you have done this, open up the Windows SPCI4 SS7 Interface Board. Keep the code Ţle Device Manager. (SS7.DC3) in a directory on your system (usually the “Septel” directory for simplicity). On a Linux 3. Make sure to turn on the Show Hidden devices system, rename SS7.DC3 to ss7.dc3. option in the View menu. You should now be able to see the Septel device under the Non-Plug and Play 3. Go to the Generic Information section on the web Drivers. ® page and, in Section 3.1, download the Dialogic ® SS7 Development Package for Windows or the 4. Double-click on the Septel device, go to the Driver Dialogic SS7 Development Package for Linux. tab, and change the startup mode to automatic. Linux Operating System Step 3 – Configuring the Dialogic® 1. For Linux, the Dialogic SS7 Development Package is Signaling Distributed Architecture a compressed tar Ţle. Manually uncompress and Software (system.txt and config.txt) extract the contents of this Ţle (using the tar utility) ® Before conŢguring the Dialogic SS7 board and protocol into a directory you have previously created. stack, an understanding of the underlying SS7 concepts, 2. Before attempting to load the SPCI driver module, such as link, link set, point codes, routes, and speciŢcally compile the object Ţle from the driver source code the Message Transfer Part (MTP) layers and the ISDN using the build_spci_cpm.sh script Ţle. This User Part (ISUP) is fundamental. If you are unfamiliar build script assumes a suitable environment for build- with those concepts, you can review the SS7 tutorial on ing Kernel modules is available. This must include the Dialogic web site at http://www.dialogic.com/ the appropriate kernel include Ţles found at: support/helpweb/signaling/tutorial/ss7.htm. For more /usr/src/linux-`uname -r`/include (for example, information about the SS7 architecture, read ISDN & /usr/src/linux-2.4.7-10/include). If these are not SS7 – Architectures for Digital Signaling Networks [Black] found, the build will fail. Following that, the (see the References section.) install_spci_cpm.sh script installs the device Two conŢguration Ţles are used when setting up the driver, automatically allocates a major device number, ® software for a Dialogic Signaling Board: system.txt and creates the four appropriate device nodes. and config.txt. Figure 4 illustrates the protocols to Note: ‘install_spci_cpm.sh’ dynamically loads the driver be conŢgured. module into the kernel. The module will remain loaded as long as the PC is not rebooted. After a system reboot, you will have to re-load the module using the insmod utility. 7 ® Application Note Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Figure 4. SS7 Protocol Stack Software Environment Programmer’s Manual system.txt (http://www.dialogic.com/support/helpweb/signaling/soft- The system.txt Ţle speciŢes how the SigDiA software ware3.htm). environment is set up. This software environment is commonly referred to as the GCTLOAD environment. Two working system.txt Ţles (one for Linux, one for ® Windows ) are included in Appendices A and D, You can think of the operation of this SigDiA software as respectively, for this cross conŢguration. Manually copy if each protocol layer is an independent module. Each them into the directory where you have installed the protocol module can run either on the host CPU or on ® ® Dialogic SS7 Development Package. the Dialogic SS7 signaling board, except MTP1 and MTP2, which must always run on the SS7 board. A review of the three major sections of the system.txt Ţle Protocol modules use inter-process communication follows: mechanisms to exchange messages with each other. LOCAL GCTLOAD modules are identiŢed with a module ID. The The LOCAL commands assign module IDs for the module ID uniquely identiŢes protocol modules in the modules that will run on the host CPU. The host GCTLOAD environment. Any piece of software (for machine is the computer where the application is example, the user application) that directly communicates running. DeŢning modules in this section also creates with the SS7 protocol modules is also considered a queues for incoming messages. GCTLOAD module and must also be assigned its own module ID. You can learn more about Dialogic SS7 GCTLOAD software environment in the SS7 Protocols 8 ® Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Application Note Our system.txt will include the following LOCAL commands: LOCAL 0x20 * Module ID for SSD LOCAL 0xcf * Module ID for s7_mgt LOCAL 0xef * Module ID for s7_log LOCAL 0x4d * Module ID for the GC/SS7 service/daemon • SSD (System Seven Dispatcher) — Special host module that is responsible for relaying messages from the host to the board • S7_mgt — ConŢguration utility that reads the config.txt Ţle and conŢgures the board and protocol modules (see config.txt; and Appendix B for Linux, Appendix E for Windows) • S7_log — General-purpose logger; use to analyze system run-time behavior and troubleshoot problems ® • GC/SS7 service daemon — Server side of the Dialogic Global Call Software for SS7 client/server architecture, responsible for receiving and sending SS7 messages from and to the ISUP protocol module REDIRECT The REDIRECT section redirects messages sent to one module ID to an alternative module. For example, if you REDIRECT messages sent to ISUP (0x23) to SSD (0x20), these messages will be sent to the board via the SSD process. This would be used where protocol modules are running on the board. Since we are running MTP2, MTP3, and ISUP on the signaling board, we REDIRECT the messages for these layers. REDIRECT 0x71 0x20 * MTP2 messages redirected to SS7 card REDIRECT 0x22 0x20 * MTP2 messages redirected to SS7 card REDIRECT 0x23 0x20 * ISUP messages redirected to SS7 card FORK_PROCESS The FORK_PROCESS section actually executes programs, such as protocol modules running on the host or management tools (for example, s7_mgt). In the conŢguration described here, no protocols are running on the host, so only manage- ment tools will be forked (for example, s7_log, s7_mgt). config.txt The config.txt Ţle is used for protocol conŢguration. It contains conŢguration commands for the MTP and ISUP protocols. s7_mgt reads the contents of this Ţle and translates the conŢguration commands into management messages that are sent to the different protocol modules. ® Two working config.txt Ţles (one for Linux, one for Windows ) are included in Appendices B and E for this cross conŢguration. Manually copy them into the directory where you have installed the Dialogic SS7 Development Package. For a description of the protocol conŢguration commands for the SPCI4 and SPCI2S products, refer to Appendix A of the SS7 Programmer’s Manual for SPCI2S, SPCI4 and CPM8 (see the For More Information section). 9 ® Application Note Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Physical Configuration The SEPTELPCI_BOARD command deŢnes the settings of the board itself. It allows deŢning the clock source for the board, and identiŢes what protocol modules are running on the board. * <ţags> SEPTELPCI_BOARD 0 0x0043 ss7.dc3 ISUP <ţags> - Possible values CTbus Slave 0x00C2 CTbus Master – clock derived from one of the SS7 card line interfaces 0x0043 CTbus Master – clock derived from SS7 card internal oscillator 0x0042 In this case, set on System A to 0x0042 and on System B to 0x0043, so that System B synchronizes on the clock generated by System A. The LIU_CONFIG command conŢgures the operating parameters for an E-1/T-1 trunk interface. These parameters include the line encoding, the frame format, and whether Cyclical Redundancy Check (CRC) is enabled or not. * LIU_CONFIG 0 0 5 1 1 1 MTP Configuration The three types of point codes to be conŢgured are as follows: • Local Point Code (LPC) — The SS7 address of the signaling point to be conŢgured. Assign Point Code 1 to System A and Point Code 2 to System B. • Adjacent Point Code (APC) — The SS7 address of the adjacent signaling point; this is the node to which the system has physical connection(s). For System A, the APC is Point Code 2. For System B, it is Point Code 1. • Destination Point Code (DPC) — The SS7 address of the remote signaling point; this is the node the system has to exchange SS7 messages with. In this case (back-to-back conŢguration), the APC is also the DPC. MTP_CONFIG is the main conŢguration command for the MTP module. The Ţrst two parameters are not used and can be left to 0. The Ţeld allows conŢguring the variant being used (ITU or ANSI). • For ITU operation, bits can be set to 0. • For ANSI operation, bits 8, 9, 10, and 11 must be set to 1, leading to a value of 0x00000f00. * MTP_CONFIG 0 0 0x00000000 The MTP_LINKSET command is used for the conŢguration of a link set to an adjacent signaling point. * MTP_LINKSET 0 2 1 0x0000 1 0x8 The parameter is a 4-bit value made up (DCBA) with: D C Network type 0 0 International network 0 1 International spare 1 0 National network 1 1 National spare B A Priority value 0 0 0 0 1 1 1 0 2 1 1 3 10 ® Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Application Note In ITU, the most common SSF value for MTP3 messages is 0x8. In ANSI operation, the most common SSF value for MTP3 is 0xb. The MTP_LINK command is used to deŢne the links within every link set. * <ţags> MTP_LINK 0 0 0 0 0 0 0 16 0x0006 Notes: refers to the signaling processor resource that will handle that particular SS7 link. can refer to the following : • When the signaling link is on an E-1/T-1 trunk that is physically connected to the Dialogic SS7 board, is the actual E-1/T-1 port ID (ranging from 0 to 3 for an SPCI4 board) that is used for that particular trunk. In this situation, the refers to the actual time slot position on that trunk (for example, time slot 16). • When the signaling link is on an E-1/T-1 trunk that is physically connected on another board in the chassis (such as a ® ® Dialogic DM/N Digital Telephony Interface Board or Dialogic DM3 Media Boards [DM/V boards]), must be set to 0x83. In this case, the refers to an internal bus slot in the SS7 board. Normally, you would start with time slot 1 for the Ţrst link and increment this value for each additional link coming from a separate board. The MTP_ROUTE command deŢnes the DPC for the system, and speciŢes which link set is used to reach it. Up to two link sets can be associated to a single DPC. * <ţags> MTP_ROUTE 567 0 0x0020 0x0000 0 Note: The is a 16-bit value with bit n (n=0...15) set to allow the route to be used for messages with Service Indicator n. The service indicators are deŢned as follows: User Part Service Indicator SCCP 3 0x0008 TUP 4 0x0010 ISUP 5 0x0020 BICC 13 0x2000 ISUP Configuration The ISUP_CONFIG command deŢnes the ISUP characteristics: point codes, CIC codes, etc. The point codes in this section must match those in the MTP ConŢguration section. DeŢne the voice circuits, specify how many, and where they are supposed to go. * ISUP_CONFIG0 0 0x4d 0x04752 64 Note: For ANSI operation, the Ţeld of ISUP_CONFIG, which is a bit Ţeld, must have bits 8 and 9 set in order to enable ANSI-compliant operations. These bits are 0 by default. The ISUP_CFG_CCTGRP command deŢnes the conŢguration parameters for a group of ISUP circuits. Usually a circuit group is made of the voice circuits on a single E-1 or T-1 trunk. Note: For the parameter, a circuit group may contain gaps in the CIC allocation. This is usually the case in Europe, where SS7 service providers usually skip every multiple of 16. This convention is used in our system set-up. 11 ® Application Note Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Group ID Total Circuits CIC Ranges Remarks 0 30 1-15, 17-31 Time slot 16 is used to carry SS7 link 1 30 33-47, 49-63 Time slot 16 is not used Note that multiples of 16 (0, 16, 32, 48) have been skipped in the CIC allocation scheme. The parameter allows for gaps in the CIC range of a particular circuit group. To build the cic_mask, follow these procedures: 1. Take an empty array of 32 bits. Bit 0 corresponds to the and to the . Bit n corresponds to , as well as to . 2. For each CIC belonging to the circuit group, turn the corresponding bit to 1 in the . Which gives the following mask: 0x7fff7fff. By setting the to 1 and by turning bit 15 off, CIC 16 is excluded ( + 15 = 16) from the Ţrst circuit group. By setting the to 33 and by clearing bit 15 in the , CIC 48 is excluded from ( + 15 = 48) from the second circuit group. Step 4 – Proving the SS7 Configuration ® Note: For Linux users: log in as a “super user” (root) to properly use Dialogic SS7 OA&M commands. 1. Once the config.txt and system.txt have been properly copied in the Dialogic SS7 directory (for example, /usr/septel on Linux and c:\Septel on Windows), open a command shell. Go to this directory, and type: ./gctload –d (Linux) or gctload –d (Windows) If a crossover cable is present and has been plugged into the correct trunk interface, the following messages display in the gctload window: S7L:I0000 LIU Status : id=0 PCM OK S7L:I0000 LIU Status : id=0 IN SYNC S7L:I0000 LIU Status : id=0 AIS CLEARED 2. If you are not getting the above mentioned LIU status indications, verify your LIU settings (PCM encoding, CRC generation, etc.) again and Ţx these problems Ţrst. Note: If you are not getting those LIU Status indications, it means that something is wrong in the physical conŢguration (maybe a wrong cable or a cable is connected to the wrong port). 3. If the physical connection is good, then you can try to bring the MTP link into service. To do so, open another com- mand window, go the SS7 directory, and type: ./mtpsl act 0 0 (Linux) or mtpsl act 0 0 (Windows) You should then get the following status indications in the gctload window: 12 ® Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Application Note ® Figure 5. DCM Showing Dialogic SS7 Board after gcss7.cfg ModiŢcations ® Windows Operating System S7L:I0000 Level 2 State : id=0 INITIAL ALIGNMENT S7L:I0000 Level 2 State : id=0 ALIGNED READY S7L:I0000 Level 2 State : id=0 IN SERVICE S7L:I0000 MTP Event : linkset_id/link_ref=0000 Changeback S7L:I0000 MTP Event : linkset_id=00 Link set recovered S7L:I0000 MTP Event : linkset_id=00 Adjacent SP accessible S7L:I0000 MTP Event : point code=00000001 Destination available Linux Operating System You should get similar messages, with the only difference that the remote point code is 00000002. ® Step 5 – Configuring the Dialogic Global Call API for SS7 Software (gcss7.cfg) ® ® The Dialogic System Release contains a Ţle called gcss7.cfg, which is used to conŢgure the Dialogic Global Call API for SS7 software. • On Linux operating systems, this Ţle is located in /usr/dialogic/cfg ® • On Windows operating systems, this Ţle is located in $DIALOGICDIR\Dialogic\cfg (for example, c:\Program Files\Dialogic\cfg) Working gcss7.cfg Ţles are given in Appendices C and F. Refer to Section 3.3 of the Global Call SS7 Technology Guide for a description of the gcss7.cfg conŢguration commands and parameters. ® 1. Once the gcss7.cfg has been properly updated, Windows users may close the Dialogic ConŢguration Manager (DCM) and re-open it. Then, the SPCI board should appear in the device tree, as shown in Figure 5. 13 ® Application Note Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Figure 6. ConŢguring the SPCI Board as the TDM Bus Primary Master 2. Double-click on the ‘Bus-0’ device, in order to conŢgure the SPCI board as the CT Bus Primary Master. This is illus- trated in Figure 6. Step 6 – Starting the Software Once everything has been conŢgured, starting the software requires two steps: 1. Start-up the Dialogic SS7 environment, using gctload(-d). Keep the gctload program running at all times. ® 2. Start-up the Dialogic service: • Linux: Invoke the dlstart script in /usr/dialogic/bin. ® • Windows : Click on the green triangle in the DCM. Since the Global Call API for SS7 software has been enabled to automatically activate the SS7 links, there is no need to manually do this with mtpsl. If everything goes well, the Dialogic service will start without any errors and the SS7 links will be activated, resulting in the following indication messages to be printed in the gctload window: S7L:I0000 Level 2 State : id=0 INITIAL ALIGNMENT S7L:I0000 Level 2 State : id=0 ALIGNED READY S7L:I0000 Level 2 State : id=0 IN SERVICE S7L:I0000 MTP Event : linkset_id/link_ref=0000 Changeback S7L:I0000 MTP Event : linkset_id=00 Link set recovered S7L:I0000 MTP Event : linkset_id=00 Adjacent SP accessible S7L:I0000 MTP Event : point code=00000001 Destination available 14 ® Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Application Note Section 7.2 of the Global Call SS7 Technology Guide (see Step 7 – Running the gc_basic_call_model the For More Information section) for information on Demo Global Call API for SS7 service traces. 1. Edit the gc_basic_call_model.cfg Ţle, un- comment the SS7 device, and rename it to dkB1T1. Note that is possible to collect both s7_log and Global • Linux operating system: Set the Direction to “Out”. Call API for SS7 service traces in a single Ţle. To do this, you have to redirect the s7_log module (0xef) to the ® • Windows operating system: Set the Direction to Global Call API for SS7 service module (0x4d) in your “In”. system.txt Ţle: 2. Run the application binary on each system, and you REDIRECT 0xef 0x4d should see GCEV_UNBLOCKED on each side and, after a short period of time, calls will start to be sent If your problem is related to the Global Call API for SS7 from the Linux system to the Windows system. application, you can also enable Global Call API for SS7 library traces in gcss7.cfg. This will result in a binary 3. Use CTRL-C to quit the demo. Ţle called ss7.log. You can use a decoder tool, called ss7trace, to convert this binary log Ţle into an ASCII Troubleshooting Ţle. Refer to Section 7.1 of the Global Call SS7 SS7-related problems can be diagnosed in different ways: Technology Guide for more information on Global Call ® API for SS7 library traces. If your problem is related to Dialogic SS7 hardware or software conŢguration, add the “debug mode” option to ssds and s7_mgt in your system.txt Ţle: Summary FORK_PROCESS ssds.exe –d This application note has described the steps to set up a FORK_PROCESS s7_mgt.exe -d ® pair of telephony systems that combine Dialogic ® When starting up the gctload environment, use the –d Signaling Boards and Dialogic DM3 Media Boards on ® option as well. platforms based on Linux and Windows operating systems. ® If your problem is related to the integration of Dialogic ® SS7 products in the Dialogic System Release Software, References then enable the Global Call API for SS7 service traces (via [Black] Uyless Black, ISDN & SS7: Architectures for gcss7.cfg). This will result in a binary Ţle called Digital Signaling Networks, Prentice Hall (ISBN 0-13- DlgcS7.log. Use a decoder tool, called ss7trace, to 259193-6), 1997. convert this binary log Ţle into an ASCII Ţle. Refer to 15 ® Application Note Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Appendix A: Linux system.txt File ******************************************************************************** * * Linux system.txt file * ******************************************************************************** * * Essential modules running on host: * LOCAL 0x20 * ssds/ssdh - Board interface task LOCAL 0x00 * tim_lnx - 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 * GC/SS7 daemon * * 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 * MTP2 module_id for SP 1 (SS7HD boards only) * REDIRECT 0xe1 0x20 * MTP2 module_id for SP 2 (SS7HD boards only) * REDIRECT 0xf1 0x20 * MTP2 module_id for SP 3 (SS7HD boards only) 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 0x22 0x20 * MTP3 module * * Redirection of status indications: * REDIRECT 0xdf 0xef * LIU/MTP2 status messages -> s7_log * * Now start-up all local tasks: * (For SPCI4/SPCI2S/CPM8 start-up use ssds and * for SS7HD boards use ssdh) * FORK_PROCESS ./ssds * FORK_PROCESS ./ssdh FORK_PROCESS ./tim_lnx FORK_PROCESS ./tick_lnx FORK_PROCESS ./s7_mgt FORK_PROCESS ./s7_log –fss7.log * ******************************************************************************** 16 ® Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Application Note Appendix B: Linux config.txt File ******************************************************************************** * * Linux config.txt * ******************************************************************************** * * * Configure individual boards: * For SPCI4 / SPCI2S boards: * SEPTELPCI_BOARD SEPTELPCI_BOARD 0 0x0042 ss7.dc3 ISUP * * * Configure individual E1/T1 interfaces: * LIU_CONFIG * LIU_CONFIG 0 0 5 1 1 1 * * * MTP parameters: * * MTP_CONFIG MTP_CONFIG 0 0 0x00000000 * * Define linksets: * MTP_LINKSET MTP_LINKSET 0 2 2 0x0000 1 0x08 * * Define signaling links: * MTP_LINK * * For SPCI4 / SPCI2S / CPM8 boards: MTP_LINK 0 0 0 0 0 0 0 16 0x0006 * * Define a route for each remote signaling point: * MTP_ROUTE MTP_ROUTE 2 0 0x0020 * * * ISUP parameters: * * Configure ISUP module: * ISUP_CONFIG ISUP_CONFIG 0 0 0x4d 0x0475 2 64 * * Configure ISUP circuit groups: * ISUP_CFG_CCTGRP * ISUP_CFG_CCTGRP 0 2 0x01 0x01 0x7fff7fff 0x001c 0 0x4d 1 0x8 0 0x00 ISUP_CFG_CCTGRP 1 2 0x21 0x21 0x7fff7fff 0x001c 0 0x4d 1 0x8 0 0x00 * ******************************************************************************** 17 ® Application Note Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Appendix C: Linux gcss7.cfg File # # Dialogic GlobalCall SS7 Configuration File (gcss7.cfg) # # for Linux # ################################ # 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) will be # used or not. # Format: String - [“None”, “Card”, “SIU”, “DualSIU”] System.Configuration = “Card” ########################################################## # 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/daemon # ################################################## # 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 # Format: Integer, Default: 200 #Service.LogMaxSize = 200 # Does the service need to start GCTLOAD automatically? # Format: String - [“Yes”, “No”] Service.GCTLOAD_Control = “No” # 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 = “/usr/septel” # GCT-environment module id used by the service # Format: Integer, Default: 0x4d #Service.ModuleID = 0x4d 18 ® Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Application Note # Maximum timeout (in seconds) for server-application keep-alive mechanism # Format: Integer; Default: 7; 0 means the mechanism is off #Service.WatchDogMaxTime = 7 # 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 = “/usr/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 = “111.112.113.114” # 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. # Format: Integer, Default: 10 #SIU.InitTimeout = 10 ############################################################ # Parameters specific to Dual-Resilient SIU Configurations # ############################################################ # SIU B Parameters - See the same parameters for SIU.A #SIU.B.IP_Address = “111.112.113.114” #SIU.B.FTP_Account = “ftp” #SIU.B.FTP_Password = “ftp” #SIU.B.RemoteConfigDir = “.” 19 ® Application Note Creating SS7 Circuit-Switched Applications using Dialogic Global Call API # Max time (in seconds) to wait for group (de)activation command # responses from SIU. # Format: Integer, Default: 5 #SIU.Dual.SiuCommandTimeout = 5 # Debounce time (in seconds) for SIU Down indications # Format: Integer, Default: 8 #SIU.Dual.SiuUpDebounceTime = 8 # Maximum number of retries for SIU group (de)activation commands # Format: Integer, Default: 5 #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_source”> # Circuit Group configuration, Group ID must match the value in config.txt. # CGrp <”trunk_name”> [ [<”Pref_SIU”>]] CGrp 0 “dkB1” CGrp 1 “dtiB1” # # End of gcss7.cfg # 20 ® Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Application Note ® Appendix D: Windows system.txt File ******************************************************************** * * Windows system.txt * ******************************************************************** * * 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 * GC/SS7 service * * 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 * MTP2 module_id for SP 1 (SS7HD boards only) * REDIRECT 0xe1 0x20 * MTP2 module_id for SP 2 (SS7HD boards only) * REDIRECT 0xf1 0x20 * MTP2 module_id for SP 3 (SS7HD boards only) 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 0x22 0x20 * MTP3 module * * Redirection of status indications: * REDIRECT 0xdf 0xef * LIU/MTP2 status messages -> s7_log * * Now start-up all local tasks: * (For SPCI4/SPCI2S/CPM8 start-up use ssds.exe and * for SS7HD boards use ssdh.exe) * FORK_PROCESS ssds.exe * FORK_PROCESS ssdh.exe FORK_PROCESS tim_nt.exe FORK_PROCESS tick_nt.exe FORK_PROCESS s7_mgt.exe FORK_PROCESS s7_log.exe –fss7.log * ******************************************************************************** 21 ® Application Note Creating SS7 Circuit-Switched Applications using Dialogic Global Call API ® Appendix E: Windows config.txt File ******************************************************************************** * * Windows config.txt * ******************************************************************************** * * * Configure individual boards: * For SPCI4 / SPCI2S boards: * SEPTELPCI_BOARD SEPTELPCI_BOARD 0 0x0043 ss7.dc3 ISUP * * * Configure individual E1/T1 interfaces: * LIU_CONFIG * LIU_CONFIG 0 0 5 1 1 1 * * * MTP parameters: * * MTP_CONFIG MTP_CONFIG 0 0 0x00000000 * * Define linksets: * MTP_LINKSET MTP_LINKSET 0 1 2 0x0000 2 0x08 * * Define signaling links: * MTP_LINK * * For SPCI4 / SPCI2S / CPM8 boards: MTP_LINK 0 0 0 0 0 0 0 16 0x0006 * * Define a route for each remote signaling point: * MTP_ROUTE MTP_ROUTE 1 0 0x0020 * * Define any user provided Layer 4 protocol: * MTP_USER_PART *MTP_USER_PART 0x0a 0x2d * * * ISUP parameters: * * Configure ISUP module: * ISUP_CONFIG ISUP_CONFIG 0 0 0x4d 0x0475 2 64 * * Configure ISUP circuit groups: * ISUP_CFG_CCTGRP * ISUP_CFG_CCTGRP 0 1 0x01 0x01 0x7fff7fff 0x001c 0 0x4d 2 0x8 0 0x00 ISUP_CFG_CCTGRP 1 1 0x21 0x21 0x7fff7fff 0x001c 0 0x4d 2 0x8 0 0x00 * ******************************************************************************** 22 ® Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Application Note ® Appendix F: Windows gcss7.cfg File # # Dialogic GlobalCall SS7 Configuration File (gcss7.cfg) # # for Windows # ################################ # 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) will be # used or not. # Format: String - [“None”, “Card”, “SIU”, “DualSIU”] System.Configuration = “Card” ########################################################## # 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/daemon # ################################################## # 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 # Format: Integer, Default: 200 #Service.LogMaxSize = 200 # Does the service need to start GCTLOAD automatically? # Format: String - [“Yes”, “No”] Service.GCTLOAD_Control = “No” # 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 mechanism # Format: Integer; Default: 7; 0 means the mechanism is off 23 ® Application Note Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Service.WatchDogMaxTime = 0 ######################################### # Configuration for Septel Card Systems # ######################################### # Path to the config.txt file # Format: String SeptelCard.ConfigDir = “c:\Septel” # Should MTP links be activated automatically? # 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 = “172.22.197.103” # 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 = “” # SIU A - Directory to which to change (in FTP session) in order to get config.txt # Format: String #SIU.A.RemoteConfigDir = “.” ############################################################ # Parameters specific to Dual-Resilient SIU Configurations # ############################################################ # SIU B Parameters - See the same parameters for SIU.A #SIU.B.IP_Address = “111.112.113.114” #SIU.B.FTP_Account = “ftp” #SIU.B.FTP_Password = “ftp” #SIU.B.RemoteConfigDir = “.” ############################################# # Parameters that are related to config.txt # ############################################# # MTP Link source, link ID must match the value in config.txt. # MtpLink <”link_source”> # Circuit Group configuration, Group ID must match the value in config.txt. # CGrp <”trunk_name”> [ [<”Pref_SIU”>]] CGrp 0 “dkB1” CGrp 1 “dtiB1” # # End of gcss7.cfg # 24 ® Creating SS7 Circuit-Switched Applications using Dialogic Global Call API Application Note Acronyms For More Information ® APC Adjacent Point code Dialogic Signaling Distributed Architecture (SigDiA) software can be downloaded at http://www.dialogic.com/ BICC Bearer Independent Call Control support/helpweb/signaling/default.htm CIC Circuit IdentiŢcation Code SS7 Boards Programmer’s Manual for SPCI2S, SPCI4 and CRC Cyclical Redundancy Check CPM8 – Issue 2 http://www.dialogic.com/support/helpweb/signaling/ DPC Destination Point Code software2.htm ISUP ISDN User Part SS7 Protocols Software Environment Programmer’s Manual LPC Local Point Code – Issue 5 http://www.dialogic.com/support/helpweb/signaling/ MTP Message Transfer Part software3.htm ® SigDiA Dialogic Signaling Distributed Architecture Global Call SS7 Technology Guide – August 2005 http://www.dialogic.com/manuals/docs/globalcall_for_ss7 _v4.pdf ® Dialogic System Release 6.0 PCI for Windows Software Installation Guide — http://www.dialogic.com/manuals/sr60winpci/release_ install.pdf ® Dialogic System Release 6.1 for Linux Software Installation Guide — http://www.dialogic.com/manuals/sr61lin/release_ install.pdf ® Dialogic System Releases and Service Updates — http://resource.dialogic.com/telecom/support/releases/ serviceUpdates/index.htm 25 To learn more, visit our site on the World Wide Web at http://www.dialogic.com. Dialogic Corporation 9800 Cavendish Blvd., 5th ţoor Montreal, Quebec CANADA H4M 2V9 INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH PRODUCTS OF DIALOGIC CORPORATION OR ITS SUBSIDIARIES (“DIALOGIC”). 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. Dialogic may make changes to speciŢcations, product descriptions, and plans at any time, without notice. Dialogic is a registered trademark of Dialogic Corporation. Dialogic’s trademarks may be used publicly only with permission from Dialogic. Such permission may only be granted by Dialogic’s 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 Dialogic’s 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 products mentioned herein are the trademarks of their respective owners. Dialogic encourages all users of its products to procure all necessary intellectual property licenses required to implement their concepts or applications, which licenses may vary from country to country. Copyright © 2007 Dialogic Corporation All rights reserved. 09/07 9443-02 www.dialogic.com