MTU & MTR User Guide
Contents
1. iii 20 6 Referentes o Le cyan LI E LU T Et UIT 21 IE eee 22 Appendix A Example configuration files using SPCI4 23 AA SY SUC IVA SM 24 A 1 1 system txt for point code 1 MTU and point code 2 MTR seen 24 A 2 Using different operating systems and board configurations 25 A 2 1 Running MTU MTR with SS7HD sse eene nnne 25 A 2 2 Running MTU MTR with SS7G2xX iii 25 A 2 3 Running MAP TCAP SCCP on the board sisi 25 A 2 4 Running MTU MTR with other operating systems 25 AS COMING A EE 26 A 3 1 config txt for point code 1 ek e 27 A 3 2 config txt for point code 2 MT RI tenter tetra aiaa eiaa XR Rx ug 29 A 4 Using different operating systems and board configurations 31 Appendix B Example configuration files using SIGTRAN 2 32 B 33 B COMM Tm 34 B 2 1 config txt for point code 1 MTU iii 35 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic B 2 2 config txt for point code 2 MTR iii 37 Appendix C Sample Output cesses 39 Dialogic2. LOCAL 0x00 Timer Task jOCAL Oxcf 57 mgt Management config task OCAL Oxef 57 log Display and logging utility 0 2 mbm Management task OCAL Oxd0 SCTPD module LOCAL 0 1 SCTP module LOCAL Oxcl M2PA module OCAL 0x22 MTP3 module OCAL 0x33 SCCP module OCAL 0x14 TCAP module OCAL 0x15 MAP module LOCAL 0x2d MTR or MTU module Now start up all local tasks FORK PROCESS ie Vas NEEE FORK PROCESS tick nt exe FORK_PROCESS sctpd exe FORK PROCESS sctp exe FORK_PROCESS m2pa nt exe t FORK PROCESS s Naw Nas Ves MED DESeXe t FORK PROCESS mbm exe d FORK PROCESS sccp nt exe t FORK_PROCESS tcp nt exe t FORK PROCESS map nt exe t FORK PROCESS s7_mgt exe d FORK PROCESS s7_log exe fss7 log If using operating systems other than Windows the names of some of the executable files used in the FORK PROCESS commands need to be changed Refer to the SIGTRAN Programmer s Manual 8 as appropriate 33 e e Dial SIC Appendix B Example configuration files using SIGTRAN M2PA B 2 config txt This section provides two example config txt files for SIGTRAN M2PA hosts running under Windows using the example configuration described earlier in this appendix The following example config txt files are for point code 1 and point code 2 All comment
3. Configure individual E1 T1 interfaces LIU CONFIG board id liu id liu type line code frame format crc mode 0 5 1 U CONFIG 0 1 1 TP Parameters TP CONFIG reserved reserved options _CONFIG 0 0 0 00000000 E ox ox X UES MT Define linksets MTP LINKSET linkset id adjacent spc num links flags local spc lt ssf gt 2 _LINKSET 0 1 0 0000 1 0 08 Define signaling links MTP LINK link id linkset id link ref slc board id blink stream timeslot flags The SS7HD board requires a compound parameter for blink of the No form sp id sp channel For SPCI4 SPCI2S CPM8 boards LINK 0 0 0 0 0 0 0 1 0 0006 For SS7HD boards LINK 0 0 0 0 0 0 0 0 1 0 0006 Define a route for each remote signaling point ROUTE lt gt linkset id user part mask MTP ROUTE 2 0 0 0008 SCCP Parameters SCCP CONFIG local spc ssf options SCCP CONFIG 1 0x8 0x0102 Enable SCCP traces SCCP TRACE op evt mask ip evt mask non prim mask P 27 e e Dial SIC Appendix A Example configuration files using SPCI4 boards SCCP TRACE 0x3 0 7 0x3 Define Remote Signaling Points SCCP SSR ssr id RSP remote spc flags po mas
4. Section 1 Introduction 1 Introduction The Dialogic MAP Test Utility MTU and the responder MTR are example applications for demonstrating the use of the Dialogic MAP module using the direct interface to the protocol module This user guide describes the design building and usage of this application for developers The MTU and MTR demonstrate the behavior of the Dialogic MAP module by offering simple functionality while showing real examples of the interface to the module The MTU and MTR applications can also be used to provide simple verification of system configuration and set up This user guide is intended for users who choose to develop their own applications that will interface with and use the functionality provided by the MAP module 1 1 Software requirements The MTU MTR application requires the following software 1 Dialogic 557 Development Package 2 Dialogic User Part Development Package 3 For TDM based configurations SS7 dC3 or ss7 dc4 codefile e Dialogic MTP3 SCCP TCAP MAP host binaries as required 4 For SIGTRAN based configurations Dialogic M2PA MTP3 SCCP and TCAP MAP host binaries as required Software can be downloaded from http www dialogic com support helpweb signaling software3 htm e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic 2 MTU Application The Dialogic MTU and MTR applications may be used to demonstrate sending MAP services in GSM networ
5. for details as appropriate 5 1 MTU Command Line Arguments The module takes a number of command line arguments which are summarized below Option Default Notes destination address encoded in accordance with Q 713 definition of called party address This parameter is mandatory 0x0000 base MAP dialogue ID Mode of operation see section 5 1 1 for details originating address encoded in accordance with Q 713 definition of called party address This parameter is mandatory Displays help message Ox2d MTU module ID 0x400 number of dialogues to use 0x000f Output display options add together required values for tracing options section 5 1 2 u 0x15 MAP module ID X 0 number of active dialogues to maintain Example mtu 0 43020008 443010008 s good morning 1987654321 The above example will open single dialogue and send short message from point code 1 55 0x8 to point code 2 SSN 0x8 The short message sent will be good morning and the international mobile subscriber ID will be 987654321 If option were added MTU would open multiple dialogues up to the value specified by option x or up to the maximum that could be supported If this maximum is exceeded and error tracing is activated section 5 1 1 a message indicating failure will be displayed 18 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic 5 1 1 MTU Modes of Operation MTU is able to accept param
6. link ref slc board id blink stream timeslot flags LIN 0 0 0 0 0 1 0 0 0x80000006 Define a route for each remote signaling point MTP ROUTE lt dpc gt linkset id user part mask MTP ROUTE 1 0 0 0008 SCCP Parameters SCCP CONFIG local spc ssf options SCCP_CONFIG 2 0x8 0x0102 Enable SCCP traces SCCP TRACE op evt mask ip evt mask non prim mask SCCP TRACE 0x3 0x7 0x3 Define Remote Signaling Points SCCP SSR ssr id RSP remote spc flags po mask SCCP SSR 1 RSP 1 0 0x0000 Define Local Sub Systems SCCP SSR ssr id LSS local ssn module id flags protocol SCCP SSR 2 LSS 0x08 0 2 0 MAP Define Remote Sub Systems SCCP SSR ssr id RSS remote spc remote ssn flags SCCP SSR 3 RSS 1 0x08 0 TCAP Parameters CONFIG base ogdlg id nog dialogues base icdlg id nic dialogues options dlg hunt lt addr_format gt CAP CONFIG 0x0 8192 0x8000 8192 0x0000 0 0 Hox ox Enable TCAP traces TCAP TRACE op evt mask ip evt mask non prim mask TCAP TRACE 0x7 Oxf 0x0 37 e e Dial 2gg1C Appendix B Example configuration files using SIGTRAN M2PA MAP Parametes MAP CONFIG options P CONFIG 0x0 Enable MAP traces MAP TRACE op evt mask ip evt mask
7. non prim mask MAP TRACE Oxf Oxf 0x15 ds MOORE 38 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Di al eg 1C Appendix C Sample Output The following is a sample output from the Dialogic MTU and MTR applications Both MTU and MTR have module id of Ox2d MTU was started using mtu 0 443010008 a43020008 1987654321 s Hello World MTU example output MTU MAP Test Utility Copyright C Dialogic Corporation 1997 2006 All Rights Reserved MTU mod ID 0x2d MAP module Id 0x15 mode 0 Forward Short Message MTU Tx sending Open Request MIU Tx 10000 M tc7e2 10000 f2d 415 500 p010b0906070400000100190201044302000803044301000800 MTU Tx sending Forward Short Message Request Tx 10000 M 7 0 10000 f2d 415 500 p030e01011707000589674523 118080406a121436587 9191c2 090421436587 904006010022123420005c832 9 065 72361924023 0000 MTU Tx sending Delimiter Request MTU Tx 10000 tc7e2 10000 f2d 415 500 p0500 MTU Rx received Open Confirmation MTU Rx 10000 M t87e3 10000 15 d2d 500 p820501000b0906070400000100190201044301000803044302000800 MTU Rx received Forward Short Message Confirmation MIU Rx 10000 M t87el i0000 15 d2d s00 p840e010100 MTU Rx received Close Indication MTU Rx 10000 M t87e3 10000 15 d2d 500 p0400 Corresponding MTR output MTR MAP Test Responder C Dialogic Corporation 1997 2006 All Rights Reserved MTR mod ID
8. 0x2d MAP module Id 0x15 MTR Rx I0000 M t87e3 i8003 15 d2d s00 p020104430200080304430100080b0906070400000100190200 MTR Rx Received Open Indication MTR Tx Sending Open Response MTR Tx 0000 tc7e2 18003 2 415 500 p810501000b0906070400000100190200 MTR Rx 10000 t87el 18003 f15 d2d 500 p040e0101191c2 090421436587 904006010022123420005c8329b 8065ddf 7236191707000589674523 11808 0406a121436587 900 MTR Rx Received Forward Short Message Indication MTR Rx Short Message User Information MTR Rx Hello World MTR Rx 0000 M t87e3 18003 15 d2d 00 p0600 MTR Rx Received delimiter Indication MTR Tx Sending Forward SM Response MTR Tx 0000 M tc7e0 18003 f2d d15 s00 830 010100 MTR Tx Sending Close Request MIR Tx 0000 M tc7e2 18003 2 415 s00 0307010000 39
9. Message Sequence Chartrand ex x d etr ERE ain Ex 9 2 4 Customising the MTU and MTR applications 11 2 5 MTU SOUC S 12 2 6 MIR Code 12 3 Building the MTU MTR 13 3 1 Host software directory 0 sis 14 3 2 Building MTU and MTR nnns nnns 14 Menit ERES 16 4 1 System Configuration oed te ee A FE RE OPE ae aae De Hia dO 16 4 1 1 SPCI2S SPCIA and SS7HD 16 1 2 5 6 2 2 M 16 18 SO GOK qM 16 4 2 Protocol Configuration issues 17 42 rA 17 A227 GAP 17 42 3 MAP nete Re E a 17 5 Running the MTU and MTR applications enne nennen nennen nnn anna nnne nana 18 5 1 MTU Command Line Arguments 18 5 1 1 MTU Modes of Op ration Rata trek eno tes Ene te ku Fee Ex et eau edu uada 19 Display OptlOnS ritur trt ertt 19 5 2 MTR Command Line
10. Test Utility MTU and Responder MTR User Guide Issue 3 Dialeg 1C 2 3 Message Sequence Chart The following pages contain message sequence charts showing a typical message flow for a single dialogue between MTU and MTR Each chart shows the message flow between the application and the MAP 7 TCAP 6 and SCCP 5 modules d MTU MAP IDLE DLG REQ OPEN SRV REQ TC INVOKE y DLG REQ DELIMIT TC BEGIN gt WAIT N QPEN DLG IND OPEN RSP SWAT N lt SMS 7 SRV IND WAIT N lt GLOSE IND gt DLG IND CLOSE DLE gt Figure 3 Single dialogue at MTU node TCAP TC END TC RESULT L UDT TX SCCP UDT RX Sent to MTR on remote system Reply from on remote system Dialegic Section 2 MTU Application 0000000 SCCP Message UDT RX from MTU Reply back to MTU 10 MAP MTR TC RESULT L TCAP TC BEGIN TC INVOKE a UDT TX Figure 4 Single dialogue at MTR node TC END DLG IND OPEN SRV IND DLG IND DELIMIT DLG REQ OPEN RSP SRV REQ DLG REQ CLOSE e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic 2 4 Customizing the MTU and MTR applications MTU MTR are example programs for development using the MAP module and as such a number of simplifications and limitations have been imposed for this purpose MTU does not try to pre
11. A M2PA 1 PPORT 3565 MTP Parameters MTP_CONFIG lt reserved gt lt reserved gt lt options gt MTP_CONFIG 0 0 0x00000000 Define linksets MTP_LINKSET linkset id adjacent spc num links flags local spc lt ssf gt MTP_LINKSET 0 2 1 0 0000 1 0x08 Define signaling links MTP_LINK lt link_id gt lt linkset_id gt lt link_ref gt lt slc gt lt board_id gt lt blink gt stream timeslot flags LINN 0 0 0 0 0 1 0 0 0x80000006 Define a route for each remote signaling point ROUTE lt gt linkset id user part mask MTP ROUTE 2 0 0 0008 SCCP Parameters SCCP CONFIG local spc ssf options SCCP_CONFIG 1 0x8 0x0102 Enable SCCP traces SCCP TRACE op evt mask ip evt mask non prim mask SCCP TRACE 0x3 0 7 0x3 Define Remote Signaling Points SCCP SSR ssr id RSP remote spc flags po mask SCCP SSR 1 RSP 2 0 0x0000 Define Local Sub Systems SCCP SSR ssr id LSS local ssn module id flags protocol SCCP SSR 2 LSS 0x08 0x2d 0 MAP Define Remote Sub Systems SCCP SSR ssr id RSS remote spc remote ssn flags SCCP SSR 3 RSS 2 0x08 0 TCAP Parameters TCAP CONFIG base ogdlg id nog dialogues base icdlg id nic dialogues
12. CAL 0x22 MTP3 module Modules running on the board all redirected via ssd REDIRECT 0x71 0x20 MTP2 module REDIRECT 0x10 0x20 CTbus Clocking control module REDIRECT 0x8e 0x20 On board management module Redirection of status indications REDIRECT Oxdf Oxef LIU MTP2 status messages to s7 log REDIRECT 0x9e Oxef Now start up all local tasks FORK PROCESS ssds exe d FORK PROCESS ie Nee Ves ver VE LMM sexe FORK_PROCESS tick nt exe FORK PROCESS s7_mgt exe d FORK PROCESS Vas NSTLLLOQ exe FORK PROCESS map nt exe t FORK PROCESS ss Nae Nes VssNECap Hb exe E FORK PROCESS ea Vas Ves Nes NSCOD NE EXE HE FORK_PROCESS mtp_nt exe t 24 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic A 2 Using different operating systems and board configurations The following subsections provide information regarding the system txt file if using different operating systems or board based configurations A 2 1 Running MTU MTR with SS7HD If using SSHD the following lines REDIRECT 0 71 0 20 MTP2 module FORK PROCESS SSDS EXE d should be replaced by REDIRECT 0x81 0x20 MTP2 module id for SPO REDIREC 0x91 0x20 MTP2 module id for SP1 REDIRECT Oxel 0x20 MTP2 module_id for SP2 REDIREC Oxf1 0x20 MTP2 module id fo
13. CP CONFIG local gt ssf options SCCP_CONFIG 2 0x8 0x0102 Enable SCCP traces SCCP TRACE op evt mask ip evt mask non prim mask 29 e e Dial SIC Appendix A Example configuration files using SPCI4 boards SCCP TRACE 0x3 0 7 0x3 Define Remote Signaling Points SCCP SSR ssr id RSP remote spc flags po mask SCCP SSR 1 RSP 1 0 0x0000 Define Local Sub Systems SCCP SSR ssr id LSS local ssn module id flags protocol SCCP SSR 2 LSS 0x08 0x2d 0 MAP Define Remote Sub Systems SCCP SSR ssr id RSS remote spc remote ssn flags SCCP SSR 3 RSS 1 0x08 0 TCAP Parameters TCAP CONFIG base ogdlg id nog dialogues base icdlg id nic dialogues options dlg hunt lt addr_format gt CAP CONFIG 0x0 8192 0x8000 8192 0x0000 0 0 ox Enable TCAP traces TCAP TRACE op evt mask ip evt mask non prim mask TCAP TRACE 0 7 Oxf 0x0 MAP Parametes MAP CONFIG options P CONFIG 0x0 Enable MAP traces MAP TRACE op evt mask ip evt mask non prim mask P TRACE Oxf Oxf 0x15 NM MN RM 30 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic A 4 Using different operating systems and board configurations The following subsections provide information regarding the config txt file if using different opera
14. D Before configuring the protocol modules it is useful to determine information such as the local point code and remote point code relative to each network entity For this example configuration the MTU point code is 1 and the MTR point code is 2 Figure 5 Example configuration 32 Operating system Windows Link type SIGTRAN M2PA Local point code 1 MTU Remote point code 2 MTR MTU module ID Local point code Ox2d MTR module ID Remote point code Ox2d MTU MTR Point code 1 Point code 2 subsystem 0x8 subsystem 0x8 IP 192 168 0 1 IP 192 168 0 2 Figure 6 Example configuration e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic B 1 system txt This section provides example system txt files for SIGTRAN M2PA hosts running under Windows using the example configuration described earlier in this appendix The following example system txt file is valid for point code 1 and point code 2 All comments are denoted KKEKKKKKKKKKKKKKKKKKKKKK kk CK kk kk Ck kk kk kk Ck kk kk kk kk ko kk Sk kx kv ko ko ko ko Example system txt Edit this file to reflect your configuration cc ck c 0k 0k KKK KKK ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck 0k ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck KKK ck ck ck kk ck Sk kk A ko ko EX ko kx Modules running on the host
15. Dialegic Dialogic SS7 Protocols MAP Test Utility MTU and Responder MTR User Guide Document Reference U30SSS www dialogic com Dialogic Section 1 Introduction Copyright 2005 2007 Dialogic Corporation All Rights Reserved You may not reproduce this document in whole or in part without permission in writing from Dialogic Corporation 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 Reasonable effort is made to ensure the accuracy of the information contained in the document However Dialogic Corporation 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
16. SCCP The local point code is contained in the main SCCP configuration command and this should be set to the appropriate value In addition configuration commands are required for the local subsystem remote point code and remote sub system 4 2 2 TCAP TCAP should be configured for ITU operation in the flags parameter of the TCAP configuration command refer to the programmer s manual 6 for details The dialogue id ranges should be set to allow the appropriate number of ids split between incoming and outgoing dialogues Some applications may require initiation of dialogues in one direction only 4 2 3 MAP The TCAP dialogue base id and number values should be set to match those given in the TCAP configuration module The user dialogue values are a separate independent range from the TCAP dialogue ids but will need to be similarly dimensioned e g if 16 incoming dialogue ids are configured in MAP then TCAP must also support at least 16 incoming dialogue ids 17 e e Dialegic Section 5 Running the MTU and MTR applications 5 Running the MTU and MTR applications Copy the host binaries to the Dialogic SS7 Development Package directory Before running the Dialogic MTU and MTR applications the environment must first be initialized and the signaling links brought into service This is achieved by running the Dialogic gctload program and activating the links using the Dialogic mtpsl utility Refer to manuals 1 3 or 4
17. ags code file run mode SEPTELPCI BOARD 0 0 0002 ss7 dc3 MTP2 For SS7HD PCI boards SS7 BOARD SS7 BOARD For SS7HD SS7 BOARD board id board type flags code file run mode 0 SS7HDP 0x0002 ss7 dc4 MTP2 cP boards board id board type flags code file run mode SS7 BOARD 0 SS7HDC 0x0002 ss7 dc4 2 Configure individual E1 T1 interfaces LIU CONFIG board id liu id liu type line code frame format crc mode 0 5 1 U CONFIG 0 1 1 TP Parameters TP CONFIG reserved reserved options _CONFIG 0 0 0 00000000 E ox ox X UES MT Define linksets MTP LINKSET linkset id lt adjacent_spc gt num links flags local spc lt ssf gt MTP_LINKS ET 0 1 1 0 0000 2 0x08 Define signaling links MTP LINK link id linkset id link ref slc board id blink stream timeslot flags The SS7HD board requires a compound parameter for blink of the No form sp id sp channel For SPCI4 SPCI2S CPM8 boards LINK 0 0 0 0 0 0 0 1 0 0006 For SS7HD boards LINK 0 0 0 0 0 0 0 0 1 0 0006 Define a route for each remote signaling point MTP ROUTE lt dpc gt linkset id user part mask MTP ROUTE 1 0 0 0008 SCCP Parameters SC
18. are denoted Using the two example config txt files at each end of the link will allow dialogues using MAP with 14 bit point codes to be demonstrated If connecting to other equipment all the various parameters in the file need to be examined to determine if they are compatible with the configuration at the other end of the link for example point codes OPC DPC e signaling timeslot e sub system numbers SSN 26 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic A 3 1 config txt for point code 1 MTU Ck Ck ck ck koc ok kk kk kk Ck Ck C Ck kk Ck kk kk Ck kk kk kk KKKKKKKKKKKK KKK Example config txt Edit this file to reflect your configuration cC cC Ck Ck 00k 00k 00k 00k CC Ck ck Ck Ck Ck Ck ck ck ck Ck ck Ck ck Ck ck 0k c 0k ck ck ck kk Ck ck Ck ck ck ck cc Sk ck ck ok Sk Sk Sk ko Sk kv kx ko EX ko kx ko ko Configure individual boards For SPCIA SPCI2S boards SEPTELPCI BOARD board id flags code file run mode SEPTELPCI BOARD 0 0 0003 ss7 dc3 MTP2 For SS7HD PCI boards SS7 BOARD SS7 BOARD For SS7HD SS7 BOARD board id board type flags code file run mode 0 SS7HDP 0x0003 ss7 dc4 2 cP boards board id board type flags code file run mode SS7 BOARD 0 SS7HDC 0x0003 ss7 dc4 2
19. depending on the operating system makdefs mak Linux makdefs sol mak Solaris makdefs mnt Windows For Windows a dynamically linked GCT library that allows the application to link to the GCT functions is supplied in the Dialogic 557 Development Package as follows gctlib dll Visual C compiler For UNIX a GCT shared object is supplied in the Dialogic SS7 Development Package e g libgctlib so 1 0 0 Linux amp Solaris The source code for the example program should be compiled and linked with the appropriate library for the operating system in use 13 e e Dialogic Section 3 Building the MTU and MTR applications 3 1 Host software directory structure To build the MTU application the user should first ensure that the required files are copied into the correct directories as follows 1 Copy either the zip or tar file from the Dialogic User Part Development Package to the Dialogic SS7 Development Package directory and decompress using the appropriate tool The choice of the zip or tar file is up to the user both will create the UPD directory structure shown in the table below The table below shows files required by the MTU and MTR programs only 2 The C header files in the INC directory shown in the table below lists the header files required by the MTU and MTR programs The following table lists the directory structure and files required to build the MTU and MTR programs supplied on the Dialogic User Part De
20. eters other than those shown in section 5 1 Whether the extra parameters can be used is dependent on the value provided for option d mode of operation There are four acceptable values for option d ranging from 0 to 3 The meaning of these values and other parameters which MTU can accept are detailed in the tables below If d parameter has value 0 default Forward short message Option Notes p MAP phase can also take value 1 i international mobile subscriber ID see programmer s manual for format 7 This parameter is mandatory Service centre address see programmer s manual for format 7 short message free text This parameter is mandatory If d parameter has value 1 Send IMSI Option Notes e MSISDN see programmer s manual for format 7 If cd parameter has value 2 Send routing info for GPRS f GGSN number see definition of ISDN AddressString 9 i international mobile subscriber ID see programmer s manual for format 7 This parameter is mandatory If d parameter has value 3 Send IMSI amp Send routing info for GPRS Option Notes MSISDN see programmer s manual for format 7 GGSN number see definition of ISDN AddressString 9 5 1 2 MTU Display Options Tracing option Value Notes MTU TRACE TX 0x0001 Trace transmitted dialogue messages MTU TRACE RX 0x0002 Trace received dialogue requests MTU TRACE ERROR 0x0004 Trace error messages MTU TRACE STATS 0
21. gistered 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 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 and Visual C are registered trademarks 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 Publication Date October 2007 Document Number U30SSS Issue 3 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic Revision History 03 Oct 01 Initial Issue 15 Feb 02 Updated after review 2 31 Jan 03 Branding changed Septel PCI now SPCI4 SPCI2S and Septel cP now CPM8 3 01 Oct 07 Changed copyright to Dialogic Corporation Remove reference to PCCS6 include non circuit protocol configuration commands in config txt and add support for SIGTRAN M2PA links Dialogic Section 1 Introduction Contents ahi 6 1 1 Software requirements 22 2 aaa A ee ied 6 2 RUP ume lm 7 2 RE a 8 2 2 M 8 2 3
22. he MTR program change to the SRC MTR directory and type one of the following commands depending on the operating system make f mtr mak make f mtr sol mak nmake f mtr mnt 15 Dialegic Section 4 Configuration 4 Configuration The local and remote ends of the system need to be configured before the Dialogic MTU and MTR applications may be run Example configuration files are provided in the Dialogic User Part Development Package and after installation will be stored in the directories as shown in the following table Root MTU MTR CONFIG CONFIG config txt config txt system txt system txt Example configurations for TDM and SIGTRAN are provided The configuration files in the MTU and MTR directories should be copied to the appropriate node Refer to Appendix A Example configuration files for further information 4 1 System Configuration The GCT environment is configured using the Dialogic gctload program and the system txt file The basic board configuration along with the Dialogic MTP SCCP TCAP and MAP modules is achieved using the config txt file 4 1 1 SPCI2S 5 4 and SS7HD For TDM based configurations example board based configuration files are provided in Appendix A for MTU and MTR When running MTU and MTR on a Windows host system using SPCIA with MTP2 running on the board and Dialogic MTP3 SCCP TCAP and MAP running on the host the provided configuration file
23. k SCCP SSR 1 RSP 2 0 0x0000 Define Local Sub Systems SCCP SSR ssr id LSS local ssn module id flags protocol SCCP SSR 2 LSS 0x08 0x2d 0 MAP Define Remote Sub Systems SCCP SSR ssr id RSS remote spc remote ssn flags SCCP SSR 3 RSS 2 0x08 0 TCAP Parameters TCAP CONFIG base ogdlg id nog dialogues base icdlg id nic dialogues options dlg hunt lt addr_format gt CAP CONFIG 0x0 8192 0x8000 8192 0x0000 0 0 ox Enable TCAP traces TCAP TRACE op evt mask ip evt mask non prim mask TCAP TRACE 0 7 Oxf 0x0 MAP Parametes MAP CONFIG options P CONFIG 0x0 Enable MAP traces MAP TRACE op evt mask ip evt mask non prim mask P TRACE Oxf Oxf 0x15 NM MN RM 28 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic A 3 2 config txt for point code 2 MTR Ck Ck ck kk ck ok kk kk CK kk CC Ck Kk Ck kk kk Ck kk kk kk Ck kk kk kk kk kk Sk kx Kk kv ke kx kv Kk kx kx ko ko ko ko ko ko ko ko ko Example config txt Edit this file to reflect your configuration cC cC Ck Ck 0k 00k 00k 00k 0k ck Ck ck Ck Ck ck ck Ck c Ck Ck ck Ck ck Ck ck Ck ck 0k c Ck ck ck ck ck kk ck Ck ck ck Ck cc ck ck ck ko Sk ko Sk kv kx ko EX ko kx ko ko Configure individual boards For SPCIA SPCI2S boards SEPTELPCI BOARD board id fl
24. k MTU is able to generate the following services e MAP SEND IMSI e MAP SEND ROUTING INFO FOR GPRS e MAP FORWARD SHORT MESSAGE The following diagram shows the network entities involved in the MAP FORWARD SHORT MESSAGE service Servicing Base Mobile Station MSC VLR Station Figure 1 GSM Network Architecture Dialogic Section 2 MTU Application 000000000 The SS7 layers involved and the two applications are shown below in Figure 2 MTU MAP MTR TCAP MAP SCCP CL MTP3 TCAP MTP2 or M2PA SCCP CL MTP3 Point Code 1 Figure 2 Typical configuration 2 1 MTU MTP2 or M2PA Point Code 2 MTU is the Dialogic MAP Test Utility which generates the dialogues to which MTR responds It first opens a dialogue to the remote node then sends the service request and finally waits for the result Using command line options you may set the dialogue addresses data fields and dialogue ids to be used Further options allow the utility to generate a single dialogue or multiple dialogues Full tracing of sent and received messages is also included 2 2 MTR The MTR utility responds to the MTU generated requests and displays the message data It also allows the tracing of sent and received messages As it replies to dialogues from the remote node it need not allocate dialogue ids itself as the Dialogic MAP module will take that responsibility e e MAP
25. le configuration Windows SPCI4 1 MTU 2 MTR 2 2 MAP TCAP SCCP MTP3 MTR Point code 2 subsystem 0x8 23 e e Dial SIC Appendix A Example configuration files using SPCI4 boards A 1 system txt This section provides one example system txt file for an SPCI4 board running under Windows using the example configuration described earlier in this appendix The following example system txt file is valid for point code 1 and point code 2 All comments are denoted A 1 1 system txt for point code 1 MTU and point code 2 MTR Ck CK CK Ck Ck CI C CK CI CK CI C CK CK CIC CK C CK CC CC CK CIC CK C CK Ck CC Ik CI Ck Ck S A Kk Kk ko Example system txt Edit this file to reflect your configuration cc ck c ck 0k 0k 0k 0k c Ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck 0k ck ck ck ck ck ck ck ck ck ck ck ck ck ck ck KK ck ck ck ck ck ok ck ck kk x kx A EX EX ko ko Essential modules running on the host LOCAL 0x20 ssd Board Interface task OCAL 0x00 Timer Task Optional modules running on the host LOCAL Oxcf s7_mgt Management config task OCAL Oxef s7 log Display and logging utility Modules that optionally run on the host LOCAL 0 2 MTR or MTU module OCAL 0x15 MAP module OCAL 0x14 TCAP module OCAL 0x33 SCCP module O
26. life sustaining critical control or safety systems or in nuclear facility applications 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 Corporation or its subsidiaries may infringe one or more patents or other intellectual property rights owned by third parties Dialogic Corporation 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 Corporation or its subsidiaries and no such licenses are provided except pursuant to a signed agreement with Dialogic Corporation More detailed information about such intellectual property is available from Dialogic Corporation s legal department at 9800 Cavendish Blvd Montreal Quebec Canada 2V9 Dialogic Corporation 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 is a re
27. options dlg hunt addr format TCAP CONFIG 0x0 8192 0x8000 8192 0x0000 0 0 35 e e Dial 2gg1C Appendix B Example configuration files using SIGTRAN M2PA Enable TCAP traces TCAP TRACE op evt mask ip evt mask non prim mask TCAP TRACE 0 7 Oxf 0x0 MAP Parametes MAP CONFIG options MAP CONFIG 0x0 Enable MAP traces MAP TRACE op evt mask ip evt mask non prim mask P TRACE Oxf Oxf 0x15 Db 36 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic B 2 2 config txt for point code 2 MTR Ck Ck ck kk kk kk kk Ck Kk Ck CC Ck Kk Ck kk kk Ck kk kk Sk kk kk Sk kk kk kk kk Kk kv Kk kx kx ko ko ko ko ko ko ko ko ko Example config txt Edit this file to reflect your configuration 0k 00k 00k 00k CC Ck ck Ck Ck Ck Ck c ck ck ck ck ck ck ck Ck ck Ck ck Ck ck ck ck ck ck ck Ck ck Ck ck 0k ck kk ck ck Sk Sk ko Sk ke kx ko EX ko ko ko ko CNSYS IPADDR 192 168 0 2 PER 20 SNSLI SNLINK 1 1PADDR 192 168 0 1 SNEND S SNTYPE M2PA M2PA 1 PPORT 3565 MTP Parameters MTP CONFIG reserved reserved options MTP CONFIG 0 0 0 00000000 Define linksets MTP_LINKSET linkset id adjacent spc num links flags local spc lt ssf gt MTP LINKSET 0 1 1 0 0000 2 0x08 Define signaling links MTP LINK link id linkset id
28. r SP3 FORK PROCESS SSDH EXE d Refer 4 for further information A 2 2 Running MTU MTR with SS7G2x If using the SIU additional commands required by the SIU will need to be included Therefore the example system txt provided in this appendix should not be used Refer to 2 for further information A 2 3 Running MAP TCAP SCCP on the board If using a board license button so that the MAP TCAP SCCP and MTP3 modules are run on the board instead of the host remove the FORK PROCESS command for the MAP host binary the LOCAL declaration should be removed for the MAP module and a REDIRECT command which redirects messages for that module to the board should be added Similar changes should also be made for the SCCP and TCAP modules Refer to 2 3 and 4 as appropriate A 2 4 Running MTU MTR with other operating systems If using operating systems other than Windows the names of some of the executable files used in the FORK PROCESS commands need to be changed Refer to 3 and 4 as appropriate 25 e e Dial SIC Appendix A Example configuration files using SPCI4 boards A 3 config txt This section provides two example config txt files for a SPCI4 board running under Windows using the example configuration described earlier in this appendix showing the protocol modules can be configured for use The following example config txt files are for point code 1 and point code 2 All comments
29. s alphabetically used in this user guide GGSN Gateway GPRS Support Node GPRS General Packet Radio Service GSM Global System for Mobile Communications HLR Home Location Register IMSI International Mobile Subscriber Identity MAP Mobile Application Part MSC Mobile Switching Centre MTP Message transfer part MTR MAP Test Responder MTU MAP Test Utility SCCP Signaling Connection Control Part SIU Signaling Interface Unit SMS Short Message Service TCAP Transaction Capabilities Application Part VLR Visitor Location Register 22 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialeg 1C Appendix A Example configuration files using SPCIA boards This section provides example configuration files for use with Dialogic MTU and MTR applications on a Windows host system for SPCI4 boards The Dialogic MAP TCAP SCCP and MTP3 modules are running on the host and both MTU and MTR are running as module ID Ox2d Before configuring the protocol modules it is useful to determine information such as the local point code and remote point code relative to each network entity For this example configuration the MTU point code is 1 and the MTR point code is 2 Figure 5 Example configuration Figure 5 Operating system Board type Local point code Remote point code MTU module ID Local point code MTR module ID Remote point code Modules running on the host MTU Point code 1 subsystem 0x8 Examp
30. s are denoted Using the two example config txt files at each end of the link will allow dialogues using MAP with 14 bit point codes to be demonstrated If connecting to other equipment the various parameters in the file need to be examined to determine if they are compatible with the configuration at the other end of the link for example e point codes OPC DPC e signaling timeslot e sub system numbers e host addresses If using the example config txt files please edit the ip address of the local and remote host to match your system Refer to 8 for SIGTRAN related parameter changes such as port numbers IP addresses etc 34 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic B 2 1 config txt for point code 1 MTU Ck Ck ck ck Ck kk Ck Kk kk Ck Ck Ck Ck Ck Ck kk Ck KKK kk Ck Sk kk kk kk kk kk kk KKK KKKKKKKKKKKKKKKKKKKKK Example config txt Edit this file to reflect your configuration Ck Ck c Ck Ck Ck 0k Ck Ck ck Ck ck Ck ck Ck Ck ck ck ck Ck ck Ck ck Ck ck ck ck ck ck ck Ck ck Ck ck Ck ck Ck ck ck ck kk ck ok ck ok Sk Sk Sk E Sk ok Kk EX ko kx NOTE The ip addresses in the CNSYS and SNSLI command needs to match your configuration Change the ip address in the CNSYS command to match your local machine and in the SNSLI command to match your remote machine CNSYS IPADDR 192 168 0 1 PER 0 SNSLI SNLINK 1 IPADDR 192 168 0 2 SNEND C SNTYPE M2P
31. s may be used without any modification Configuration details for other board types are also provided for reference 4 1 2 SIGTRAN M2PA It is also possible to run a similar configuration as described in Section 4 1 1 but with SIGTRAN M2PA links Configuration files for such systems are contained in Appendix B When running MTU and MTR on a Windows host system using Dialogic M2PA MTP3 SCCP TCAP and MAP running on the host the provided configuration files may be used without any modification 4 1 3 SS7G2x System and protocol information is configured using the management module and commands in the config txt and system txt files for the SS7G2x Further information on this can be obtained from the user manual 2 Note These files are not contained in the User Part Development Package 16 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic 4 2 Protocol Configuration All protocol modules are configured using commands in the config txt file The example configuration files given in the appendices will perform the appropriate protocol configuration shown below If the user wishes to better understand or alter the configuration given the following sections will be of interest Before configuring the protocol modules it is useful to determine the following information relative to each network entity e Local point code e Local sub system number e Remote point code and e Remote sub system number 4 2 4
32. t dialogue and service requests destined for MAP and also to convert indications from MAP into a structured format mtu h Contains macro and structure definitions used in MTU 2 6 MTR source code 12 The MTR program can be found in the Dialogic User Part Development Package The following table describes the files required by the MTR application mtr main c This file contains the main function This reads the command line arguments and passes them to mtr ent mtr c This file contains mtr ent which sends an open response using MTR send OpenResponse when an open dialogue indication is received and then waits for a service indication and a delimiter When both have been received a service response is sent followed by a close dialogue request using MTR send MapClose Contains macro and structure definitions used in MTR e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic 3 Building the MTU and MTR applications Example make files for the following operating systems are provided and identified by a unique suffix Operating system Suffix Generic UNIX Solaris Linux mak Windows mnt A single definitions file one for each operating system which contains the definitions relating to the user s own development environment is supplied in the Dialogic User Part Development Package The definitions files are as follows and the appropriate file should be used
33. ting systems or board based configurations A 4 1 1 Running MTU MTR with SS7HDP If using SS7HDP boards the SEPTELPCI_BOARD command should be replaced with the following SS7 BOARD 0 SS7HDP 0x0003 ss7 dc4 2 Refer to 4 for further information A 4 1 2 Running MAP TCAP SCCP on the board When using a license button so that the MAP TCAP SCCP and MTP modules run on the board instead of the host e For SPCI2S and SPCIA the run mode field in the SEPTELPCI BOARD command should be set to MAP e For SS7HDP the run mode field in the S87 BOARD command should be set to MAP Refer to 3 and as appropriate A 4 1 3 Running MTU MTR with the SIU If using the SIU additional commands required by the SIU will need to be included Therefore the example config txt provided in this appendix should not be used Refer to 2 3 and 4 for further information A 4 1 4 Running MTU MTR with other operating systems There are no additional commands specific to various operating systems Refer to 3 and 4 as appropriate 31 e e Dial SIC Appendix B Example configuration files using SIGTRAN M2PA Appendix B Example configuration files using SIGTRAN M2PA This section provides example configuration files for use with Dialogic MTU and MTR applications on a Windows host system using SIGTRAN M2PA links The Dialogic MAP TCAP SCCP MTP3 and M2PA modules are running on the host Both MTU and MTR are running as module I
34. velopment Package Root directory Septel INC UPD asciibin h BIN SRC ed BACKUP BINWIN MTU MTR makdefs mnt msg h BACKUP BINLNX mtu mnt mtr mnt 2 E mtu mak mtr mak makdefs ma ss7 inc h BACKUP BINSO sol mak mtr sol mak makeall bat strtonum h L mtu c mtr c m m sysgct h mtu fmt c mtr main c makeall so system h mtu main c mtr h mtu h mtr iss txt mtu iss txt 3 2 Building MTU and MTR It is assumed that the UPD is extracted in the Dialogic 557 Development Package directory i e for Windows C Septel as shown above Similarly for Linux a symbolic link should be created it is assumed that the UPD is unpacked and stored within in the DPK directory A script is provided in the BINNSRC directory to build and copy all of the example programs into the UPD BIN directory To run this script change to the BIN SRC directory and type one of the following commands depending on the operating system makeall Linux makeall sol Solaris makeall bat Windows A pre built copy of the MTU and MTR applications for each operating system can be located within the backup subdirectories in the BIN directory 14 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialeg 1 To build the MTU program change to the SRC MTU directory and type one of the following commands depending on the operating system make f mtu mak make f mtu sol mak nmake f mtu mnt To build t
35. vent congestion on the link so it is possible to generate more traffic than the links can handle The lower levels of the stack provide some protection from the effect of link congestion by simply discarding messages Without changes MTU should be run at lower traffic loading levels MTU does not provide support for segmentation of messages that are too long for the short message service MTR assumes the use of MTU as the dialogue generating application and supports only the functionality required to reply to dialogues generated by MTU The developer should be aware of the limited nature of the example applications when making use of the source code for building their own 11 Dialegic Section 2 MTU Application 000000000 2 5 MTU source code The MTU program can be found in the Dialogic User Part Development Package The following table describes the files that make up the MTU application mtu_main c This file contains the main function This reads the command line arguments and passes them to mtu_ent mtu c mtu ent calls the function open dlg to open a dialogue send a service request message and send a delimiter to indicate that currently no further requests will be made It waits for indications to be received and these are handled by the main state machine MTU smac Depending on the trace options the message is displayed by display recvd msg mtu fmt c Contains functions to forma
36. x0008 Trace the number of opened dialogues 19 e Dialegic Section 5 Running the MTU and MTR applications 5 2 MTR Command Line Arguments The module takes a number of command line arguments which are summarized below Option Default Notes Ox2d MTR module id 0x15 MAP module id Enabled Disable tracing If t parameter is provided tracing is disabled Displays help information Example mtr mOxd The above example will run MTR with a module id of 0x0d MTR will assume the MAP module below has a module id of 0x15 MTR will also trace any messages received or transmitted 20 e e MAP Test Utility MTU and Responder MTR User Guide Issue 3 Dialegic 6 References 1 U10SSS Dialogic Software Environment Programmer s Manual 2 05 2302 Dialogic SS7G2x SIU Mode User Manual 3 UO3HSP Dialogic Programmer s Manual for SPCI2S 5 4 and CPM8 4 05 2063 Dialogic SS7HD Programmer s Manual 5 UO5SSS Dialogic SCCP Programmer s Manual 6 006955 Dialogic TCAP Programmer s Manual 7 U14SSS Dialogic MAP Programmer s Manual 8 UO4STN Dialogic Programmer s Manual for Sigtran Host Software 9 ETSI TS 100 974v7 5 1 Digital Cellular Telecommunications System Phase 2 Updates to the documentation are available on the Dialogic web site at http www dialogic com support helpweb signaling default htm 21 Dialegic Section 7 Abbreviations 7 Abbreviations The following lists acronym
Download Pdf Manuals
Related Search