Enabling SMS in SS7 Telephony Applications Using
Contents
1. and Signaling Gateways SMS Enabled Telephony Application MAP Global Call MTP Layer 3 MTP Layer MTP Layer 1 Figure 3 User s Guide for Linux and Windows at http resource intel com telecom support releases winnt SR51 1FP1 onldoc htmlfiles index html for more details on this The left side of Figure 3 shows the non circuit related protocols that are needed to bring SMS into a telephony application The SMS Service is provided by the Mobile Application Part MAP which relies on the services provid ed by the Transaction Capability Application Part TCAP which itself uses the services of the Signaling Connection Control Part SCCP Hence these three different protocols must be running and properly configured The software environment is controlled by system txt The reference system uses host based protocols and hence the corresponding modules must be declared as LOCAL and must be forked using the FORK PROCESS command in system txt Configuration of MTP and ISUP is done within config txt On both systems MTP USER PART must be invoked to register SCCP module id 0x33 as a user part with Service Indicator Ox3 this is SCCP SCCP TCAP and MAP are configured using discrete messages It is important to properly configure the local subsystem and remote subsystem numbers on both sides as well as bringing them into service For this purpose the scripts mtucfg ms7 and mtrcfg ms7 can be se2. el args el args El args el args el args CIRS ElL angs CIRS CJL args CIES CJL args el args Men mee acl mtu map id Sase elle id comem Clie ieg gjHnssx dueibibwe simsii Orig access SGmwice CEMteS OSs _eceliasss L350 20008 p DEFAULT MODULE ID DEFAULT MAP ID derer T E MTOR PV2 mode MTU FORWARD SM options DEFAULT OPTIONS BASE DLG ID NUM OF DLG IDS DEFAULT MAX ACTIVE 4065200377 430100087 Wi 7i message Hello World ggadeeuam vr ggn mumos E mtu ent tol args mtu_ForwardsMs function instead of placing an outgoing call static int CIU incoming Call call Fu C7 C7 Eel rU CALG emp per call data structure 16 Eici fs logieai cirouit sl LUBA sO cme ally 10 The originating address and destination address the cl_args structure in the mtu_ForwardSMS need to be set according to your configuration Application Note 11 Application Note 12 Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards and Signaling Gateways printe Call 36 cali eol p Check to see if the cpc value matches that for calls that we will answer a AE call gt cpe CTU_release_req IC_ID cid CAUSEV_NULL GuMBJ eei call gt state j else idie eebil s REJECT CPC call gt instance STATE WATT TDLE Complete the
3. SCCP TCAP and MAP User Part Development Package Intel Dialogic System Release 5 1 1 FP1 for Windows optional System Installation Hardware Boards must be inserted in each chassis Please refer to the corresponding User Manual for guidance on this Connect the two chassis with an E 1 T 1 cross cable from the first Line Interface Unit LIU of each Intel NetStructure SS7 board m On the chassis running the SMS enabled telephony application cross connect the second LIU to the third LIU of the SS7 board and Signaling Gateways Software Install the SS7 Development Package Please refer to the Installation section in the SS7 Programmer s Manual for Septel cP Septel PCI at http resource intel com telecom support ss7 downloads index htm for detailed installation instructions Copy the SS7 binary for the SPCIA ss7 dc3 and the host protocols isp Inx scp Inx tcp Inx and map Inx for Linux isp_nt exe Scp nt exe tcp nt exe and map nt exe for Windows in the directory where you installed the Development Package e g usr septel on Linux and c septel on Windows Also extract the User Part Development package in that same directory If needed install Intel Dialogic System Release For Linux the LiS package needs to be installed prior to installing the System Release Please refer to System Release 5 1 for Linux Feature Pack 1 Release Notes at http resource intel com telecom sup
4. chassis hosting point code 1 and the MTR demo on the other chassis which simulates the MSC VLR SMS enabling the Call Test Utility Now that all pieces are correctly installed and configured the final objective of this application note is to SMS enable a telephony application In our particular case we will merge the code of the MAP Test Utility which demonstrates SMS forwarding functionality with the code of the Call Test Utility Here is the process 1 Copy all the MTU files in the CTU directory 2 Add the MTU object files in the CTU makefile For example in ctu mnt OBIS etu eb Calico Cigpack oloj ctu mein Gj mew cbj mew Tue Ga mtu_main obj Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards and Signaling Gateways 3 Delete the entire contents of mtu main c and copy and paste the following simplified code include mtu h Default values for MTU s command line options uA define DEFAULT MODULE ID 0x2d define DEFAULT MAP ID MAP TASK ID define DEFAULT OPTIONS 0x000f define DEFAULT MAX ACTIVE 0 Structure that stores the data entered on the command line wi Stacie Cl ARGS Gl mue void mtu_ForwardSMS 4 n ctu c declare the prototype of the above defined function this is void mtu_ForwardSMS Upon receipt of an incoming call indication this is in the ctu incomingcall function call CJL uere CJL euegie CJ euegje
5. incoming call setup Sy CrUMaileratms ec Caen Calc CTU_setup_resp IC_ID cid STATE IC ACTIVE call gt state mtu ForwardSMS j return 0 5 Recompile the enhanced CTU program HLR Interrogation When an SMS enabled service node tries to send a message to a mobile phone it must first identify where that mobile is This is achieved by querying the mobile s HLR for location information In some cases the point code of a given operator s HLR is locally known in other cases it is not This will obvi ously be true when the mobile phone is bound to a foreign operator This leads to two differ ent ways of performing HLR interrogation direct and indirect Direct HLR Interrogation Direct HLR interrogation occurs when the point code of a given mobile phone s HLR is known in the local service node For every HLR that can be directly addressed the following command must be added in the local config txt call gt instance call gt instance MTP ROUTE with lt dpc gt set the HLR s point code and user part mask set to 0x8 Using s7 play a set of discrete messages need to be sent to SCCP to configure the point code and subsystem number of the remote HLR S m SCP MSG CONF SSR 0x7741 with ssr type set to RSP and lt spc gt to the actual HLR s point code m SCP_MSG_CNF_SSR 0x7741 with ssr type set to RSS spc to the actual HLR s point code and lt ssn gt to Ox6
6. subscriber number is used to retrieve the HLR point code to send a MAP_SEND_ROUTING_INFO_FOR_SM message 5 The HLR sends the requested information back to the voice mail service node in a MAP_SEND_ROUTING_INFO_FOR_ SM_ACK message 6 The voice mail formats and sends the short message to the MSC VLR currently visited by User B using a MAP_FORWARD_ SHORT_MESSAGE message 7 Once the short message has been delivered to User B s cell phone the MSC VLR sends a MAP_FORWARD_ SHORT_MESSAGE_ACK back to the voice mail system Reference System To simulate the components involved in the previous scenario two systems were constructed each running Microsoft Windows 2000 and containing an Intel NetStructure SPCIA board One chassis hosts the actual SMS enabled telephony application point code 1 while the other one simulates the MSC VLR point code 2 To keep the configuration simple the SSP point code 3 is hosted by the chassis running the telephony application calls will be made between these two point codes using a loop back connec tion For simplicity point codes 2 MSC VLR and 3 SSP are only set up for testing purposes and are not pieces of the system and service that this application note is intended to describe For further simplicity no location query will be sent to the HLR this can be easily achieved by adding this service request into the MTU application More information on the actual HLR interrogation proc
7. which is usually the reserved SSN value for HLR Please refer to the SCCP Programmer s Manual at http resource intel com telecom support ss7 downloads index htm for more details on SCCP configuration The destination address of the dialogue in 11 Note that for an SIU based service node the following commands are available in config txt to configure the Remote Signaling Point and the Remote Subsystems SCCP_RSP and SCCP_RSS Please refer to the Intel NetStructure SIU520 Developer s Manual for more details on these commands Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards which the Send Location Information for SM will be sent must contain the point code of the HLR as well as the SSN This address must be encoded with the Q 713 definition of Called party address starting with the address indicator set to Ox43 and containing signaling point code and subsystem number set to 0x06 for HLR Indirect HLR Interrogation When the HLR s point code is not known to the Service Node Global Title Translation GTT is needed in order to properly route the location information query to the remote HLR The Global Title will be the mobile number itself and the location request Send Routing Info for SM must be sent to a GTT capable node within the SS7 network To make this node known to the local stack the following command must be added in the local config txt MTP ROUTE with dpc
8. 0x20 0x20 0x20 status Oxef Oxef MTP3 module MTP2 module CT bus Clocking control module On board management module E e M ia indications LIU MTP2 status messages gt s7 log Now start up all local tasks For Septel ISA PCCS6 start up ssd and ssd poll for Septel cP PCI start up ssds ssd exe ssd_po ll exe ssds exe fede Tuc o PIS tick nt exe cio im Cepen map_nt LED Ea s7_mgt Gy lOG Xe exe exe exe exe Spe Application Note Application Note Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards i and Signaling Gateways System simulating the MSC VLR Stu PER t o DOES DNE S System txt for the Intel NetStructure Windows Development Package Essential modules running on host OCAR OCAL OCAL Op CAL OCAL OCAR OCAR 0x20 0x00 Oxef Oye Ox33 0x14 0x5 Application modules LOCAL 0x2d MTR Moules cumming om the boeze aell x REDIRECT 0x22 0x20 MTP3 MOCI REDIRECT Ox7il Ox20 JH MOCHI REDIRECT Ox10 Ox20 REDIRECT Ose 0x20 REDIRECT FO FO FO FO FO FO FO FO For Septel ISA Redirection of Oxdf 0x9e ssd ssds Board interface task tim me Timer task SES Oe S7 log SS7 message clisplay tasik tional modules running
9. Application Note Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards and Signaling Gateways Intel in Communications Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards Application Note and Signaling Gateways Table of Contents Abstract 1 Assumptions and Objectives 1 Scenario 1 Reference System 2 Components 2 Hardware 3 Software 3 System Installation 3 Hardware 3 Software 3 System Configuration 3 System txt Files 5 Config txt Files 7 Proving the Configuration 10 SMS enabling the Call Test Utility 10 HLR Interrogation 12 Direct HLR Interrogation 12 Indirect HLR Interrogation 13 Definitions and Acronyms 13 Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards Abstract This document describes the installation and configuration of Intel NetStructure SS7 boards and system level platforms in a circuit switched telephony system requiring short messaging service SMS messaging capabilities Adding SMS in telephony applications such as voice mail or unified messaging is a value added feature for end users lets solution developers differentiate products from competitors and generates extra revenues for service providers By applying the concepts presented in this application note readers should be able to enhance their existing SS7 telephony application with SMS capabilities Further information on referenced docu
10. G O0 5 I L1 1 EU CONFIG 0 121 5 1 X3 1 iy CONEIEG 0 2 5 1 1 1 AMER qoyeuegueiEeEe IMINE CONEIG reserved lt uescevech gt lt cepiciloms gt MANE CONG 0 0x0000 Define linksets MTP LINKSET linkset id adjacent spc num links lt flags gt Socal fex lt SS MTP_LINKSET 0 2 1 0x0000 1 0x08 MTP LINKSET 1 3 1 0x0000 1 0x08 Me LINKSE 2 11 1 020000 5 0208 Define signaling links MD DINK lt link icb lt limnkset ich lt link rei gt lt sle gt lt boarel ich lt blink gt lt stream gt lt timeslot gt lt flags gt Note For Septel ISA PCCS6 boards the first LIU port is stream 16 whilst for Septel cP PCI boards the first LIU port is stream 0 MTP LINK 0 0 0 0 0 0 0 16 0x0006 impe tw 1 id 0 09 1 1 31 0006 MONE LINE 2 2 0 0 0 2 2 16 00006 Define a route for each remote signaling point jud ROUTE elo lt limmsee ach lt uiseie part masis MTP ROUTE 2 0 0x0008 MTP ROUTE 1 2 0x0020 MTP ROUTE 3 1 0x0020 Define any user provided Layer 4 protocol jud USN PNR exeuwihele stab lt imochile she MTP USER PART 0x03 0x33 Application Note Application Note Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards and Signaling Gateways Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards and Signaling Gateways System simulating the MSC VLR Config
11. OVIDED IN CONNECTION WITH INTEL PRODUCTS NO LICENSE EXPRESS OR IMPLIED BY ESTOPPEL OR OTHERWISE TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT EXCEPT AS PROVIDED IN INTEL S TERMS AND CONDITIONS OF SALE FOR SUCH PRODUCTS INTEL ASSUMES NO LIABILITY WHATSOEVER AND INTEL DISCLAIMS ANY EXPRESS OR IMPLIED WARRANTY RELATING TO SALE AND OR USE OF INTEL PRODUCTS INCLUDING LIABILITY OR WARRANTIES RELATING TO FITNESS FOR A PARTICULAR PURPOSE MERCHANTABILITY OR INFRINGEMENT OF ANY PATENT COPYRIGHT OR OTHER INTELLECTUAL PROPERTY RIGHT Intel products are not intended for use in medical life saving life sustaining critical control or safety systems or in nuclear facility applications Intel may make changes to specifications product descriptions and plans at any time without notice Intel Intel Dialogic Intel NetStructure Pentium and the Intel logo are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries Other names and brands may be claimed as the property of others Performance tests and ratings are measured using specific computer systems and or components and reflect the approximate performance of Intel products as measured by those tests Any difference in system hardware or software design or configuration may affect actual performance Buyers should consult other sources of information to evaluate the performance of systems or components they are consi
12. Telephony Applications Using Intel NetStructure SS7 Boards and Signaling Gateways Proving the Configuration First of all verify that MTP is properly configured To do this run gctload on each system and then activate all the signaling links using mtpsl This is the output of s7 log on the system running the telephony application S7L 10000 M TE lweme 8 limkeeie icl ilimis seeuc 0 000 Cluesageleeelk SyIg 10000 Wi Event s limkeset icd 00 Link set recovered S710000 MIE Event g limksee id 00 Adjacent SP aceessilole S7L I0000 MTP Event point code 00000002 Destination available S LELOOOO Mare wer llamkeeic da liak seeur 0L00 Clnaimesloacle S710000 MIE Event g linkset id 01l Link set recovered S710000 Wi Event s limkset AGO Adjacent SP aceessilole S7L I0000 MTP Event point code 00000003 Destination available S7 L2TOOOO NP Evean g akset a nk seeur 002000 Clhaimedloaelk 71 10000 We Ier 3 limkset aLol 02 Link set recovered S7I5830 0000 MIP Eweme g limkset id 02 Adjacent SP aceessilole S7L 10000 MTP Event point code 00000001 Destination available Once MTP configuration has been proved the ISUP configuration can be checked This can be easily done by running the CTU demo on the system where it has been configured Please refer to the Call Test Utility CTU User Guide to get details on how to compile and run the CTU applica tion Similarly the MAP configuration can be proved by running the MTU demo on the
13. concepts will apply for the IS41 protocol The MAP Test Utility MTU and the MAP Test Responder MTR are example applications designed to demonstrate the use of the GSM MAP module from Intel using the direct interface to the protocol module Source code makefile and the User s Manual are available contact Technical Support 3 The Call Test Utility CTU is an example application designed to demonstrate the use of the telephony modules from Intel e g ISUP and TUP using the direct interface to the protocol module Source code makefile and the User s Manual are available contact Technical Support Application Note Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards and Signaling Gateways SMS Enabled Telephony Application MAP Link Point Code 2 Point Code 1 ISUP Link ISUP Circuits Point Code 3 Figure 2 Under normal conditions these steps occur 1 User A calls User B who is not able to take that call e g already in a call 2 User A s local exchange or Service Switching Point SSP routes the call to User B s voice mail service node 3 The voice mail system records User A s message and releases that call All this is usually done using the ISUP or TUP protocol 4 The voice mail queries User B s Home Location Register HLR for User B s current location within the wireless network User B s mobile
14. dering purchasing For more information on performance tests and on the performance of Intel products reference http www intel com performance resources Limits htm or call U S 1 800 628 8686 or 1 916 356 3104 Printed in the USA Copyright O 2003 Intel Corporation All rights reserved 7 Printed on recycled paper 09 03 00 8775 001
15. edure is available in this document Components The following components were included in the reference system based on the Intel NetStructure SPCIA board Other products Such as the Intel NetStructure PCCS6 board or an Intel NetStructure Signaling Interface Unit SIU131 231 520 could be used alternatively Configuration files must be modified accordingly 4 t is also possible to build a voice mail application using the services of the INAP protocol 5 It is possible to duplicate this configuration on a system based on the Linux operating system using the components listed in the Components section n a real deployment the SSP HLR and MSC VLR are external network nodes managed by the network operator Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards Hardware Industrial chassis with PCI bus based on the Intel Pentium Ill processor E Intel NetStructure SPCl4 SS7 board MTP3 license button for SPCIA E Intel Dialogic DM V1200 4E1 PCI voice board optional Two E 1 T 1 crossed cables Software RedHat Linux 7 2 or 7 3 SS7 Development Package 2 02 for Linux SS7 binary for SPCIA v1 03 Host protocols for Linux ISUP SCCP TCAP and MAP User Part Development Package E Intel Dialogic System Release 5 1 FP1 for Linux optional Windows 2000 SS7 Development Package 2 01 for Windows SS7 binary for SPCIA v1 03 Host protocols for Windows ISUP
16. mentation and SS7 solutions from Intel can be found at http www intel com go ss7 Assumptions and Objectives The purpose of this application note is to guide the reader step by step through the installation configuration and compilation of an SMS enabled SS7 telephony application using Intel NetStructure SS7 boards and system level SMS Enabled Voice Mail and Signaling Gateways ORBE EOR Note platforms It is assumed that the reader already has an existing SS7 telephony application The primary objective is to show the configuration modifications needed to integrate the processing of GSM MAP primitives into a call processing ISUP or TUP application The second objective is to compile such an application and make it run This process will be demonstrated by merging the SMS forwarding capabilities of the MAP Test Utility see the MAP Test Utility MTU and Responder MTR User Guide into the Call Test Utility see the Call Test Utility CTU User Guide Scenario Figure 1 illustrates an incoming call from the circuit switched network being answered by an SMS enabled voice mail system After normal call processing that is recording the message left by the calling party the voice mail system notifies the called user that he she has a pending message by delivering a Short Message SM to his her cell phone Figure 1 The SMS services of the GSM MAP protocol will be used in this application note The main
17. nt to the board using s7_play on point code 1 and point code 2 respectively Please refer to the MAP Test Utility MTU and Responder MTR User Guide for details on this 9 Local and remote subsystem numbers are to be specified by the network operator In wireless networks MSCs usually have subsystem number 0x08 Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards System txt Files and Signaling Gateways System containing the SMS enabled application Package C Be Ee E ee ey LOCAL LOCAL LOCAL 0x20 0x00 Oxef System txt for the Intel NetStructure Windows Development Essential modules running on host ssd ssds Board interface task tim nt Timer task sg7 log SS7 message display task Optional modules running on the host LOCAL LOCAL LOCAL LOCAL LOCAL Oxer 0x33 0x14 0x15 0223 Application modules LOCAL Ox2d s7_mgt Management config task SCCP module TCAP module MAP module ISUP module feo MSS enctiolec cM CWU Modules running on the board all redirected via ssd REDIRECT REDIRECT REDIRECT REDIRECT O22 ozm 0x10 0x8e Redirection of REDIRECT REDIRECT o Ee Fo Een Ee E FORK PROCESS FORK PROCESS FORK PROCESS EIORINSSEEG GEBISS FORK PROCESS FORK PROCESS FORK PROCESS FORK PROCESS FORK PROCESS Oxdf 0x9e FORK PROCESS FORK PROCESS 0x20
18. on the host S7 mgt Management config task Sec mci TCAP modul MAP module le Le redirected via ssd e e bus Clocking control module On board management module status indications Oxef Oxef LIU MIP2 sietus messages se7 log Now start up all local tasks ECS Skart u PES mess cM ON fOr Sepeell cPE PEE Stat UD SS FORK PROC FORK PROC ESS R R R R REDIRECT R RK PI RK PROCI RK Pl RK PROCI RK PROCI RK PROCI RK PI RK PI ROC ROC ROC ROC ESS ESS ESS ESS ESS ESS ESS ESS ESS ssd ex e SiS ero oxlerqo ssds e xe Tim ME ese Tiek nt Gx SCPENE TEI Meo map nt s7 mgt Si log exe exe exe exe exe Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards and Signaling Gateways Config txt Files System containing the SMS enabled application Configure individual boards For Septel ISA PCCS6 boards EPCOS OERBOARD PONTING lt lgogicl ach uu jocm gt lt ilagss lt ocla_itilile gt PCCS6 BOARD 0 O O 0x0043 mtp76 dc2 So RO NB RR X For Septel cP PCI boards rs ci ally HE TE NETS OV NUD MESS TO cis cT MESS Ee pM MTS SEPTELPCI BOARD 0 0x0042 ss7 ckeS We Configure individual E1 Tl interfaces LIU CONFIG lt board ich lt liu id lt liu_iyoe gt line code lt frame for mat gt m crc mode Liv CONEL
19. port releases unix51 linux51fp1 Onldoc index html for details on this For Windows the Java Runtime Environment must be installed before installing the System Release Please refer to System Release 5 1 1 for Windows Service Pack 1 Release Notes at http resource intel com telecom support releases winnt SR51 1FP1 onldoc htmlfiles index html for details on this System Configuration Figure 3 depicts the different SS7 protocol layers involved when enabling SMS in a telephony application The right side of Figure 3 shows the protocols needed for the telephony circuit oriented part of the application Depending on the country either ISUP or TUP will be used The applica tion developer can decide to directly interface the ISUP or TUP module or may use Global Call to deal with calls Configuration files will be slightly different when Global Call is used Please refer to the Global Call SS7 Technology 7 The Intel Dialogic DM V1200 4E1 voice board is necessary if the telephony application needs to perform some media processing e g playing prompts detecting DTMF digits etc Note that another media resource card such as an Intel Dialogic D 300JCT E1 combined media board could be used alternatively 8 The Intel Dialogic System Release is needed only if an Intel Dialogic board and or Global Call is used Application Note Application Note Enabling SMS in SS7 Telephony Applications Using Intel NetStructure SS7 Boards
20. set to the point code of the node that performs GTT It is also necessary to configure the point code of this GTT node in the local SCCP by sending the following message for example using s7 play m SCP MSG CNF SSR 0x7741 with ssr type set to RSP and lt spc gt to the point code of the node that performs GTT The destination address of the dialogue in which the Send Location Information for SM will be sent must contain the point code of the node performing GTT as well as the actual Global Title This address must be encoded with the Q 713 definition of Called party address For the Adaress Indicator Bit 1 must be set to 1 to indicate the address contains signaling point code Bit 2 must be set to O to indicate the address does not contain any subsystem number Bits 3 6 known as the Global Title Indicator must reflect the contents of the actual Global Title in the address translation type numbering plan and Signaling Gateways BpNenton Note Bit 7 must be set to 1 to indicate that rout ing must be performed based on Global Title Bit 8 is set to O on an international network check this with the operator For both methods a MAP dialogue must be established with the peer entity the HLR itself or the node performing GTT Within this dialogue a MAP SEND ROUTING INFO FORSM REQ service primitive must be sent Please refer to the MAP Programmer s Manual at http resource in
21. tel com telecom support ss7 downloads index htm for details about the specific parameters that must be set in this service primitive Definitions and Acronyms CTU Call Test Utility Example application designed to demonstrate the use of the Intel NetStructure telephony modules e g ISUP TUP and NUP using the direct interface to the protocol module HLR Home Location Register ISUP ISDN User Part MAP Mobile Application Part MSC Mobile Switching Centre MTR MAP Test Responder Example appli cation designed to demonstrate the use of the Intel NetStructure MAP module using the direct interface to the protocol module MTU MAP Test Utility Example application designed to demonstrate the use of the Intel NetStructure MAP module using the direct interface to the protocol module SMS Short Message Service Service for sending messages of up to 160 characters to mobile phones SSP Service Switching Point SSPs are Switches that originate terminate or tandem calls An SSP sends signaling messages to other SSPs to setup manage and release voice circuits required to complete a call VLR Visitor Location Register 12 For example the destination address is 0x43020006 if the point code of the HLR is 0x02 13 To learn more visit our site on the World Wide Web at http www intel com 1515 Route Ten Parsippany NJ 07054 Phone 1 973 993 3000 INFORMATION IN THIS DOCUMENT IS PR
22. ure individual boards For Septel ISA PCCS6 boards PCCS6 BOARD port id board id num pcm flags code file gt PCCS6 BOARD O 0 0O 0x0043 mtp76 dc2 For Septel cP PCI boards SUNPHPSINCI ISOVNS D lt ls eicel ach lt itllecis gt evele iude SEPTELPCI BOARD 0 0x0043 S87 cleS We Configure individual E1 Tl interfaces LIU CONFIG lt boarel ich lt lin ich lt iliu_type gt lt line coe lt ieime_ior mat gt ki crc mode Ed Cowexc gg O0 5 1 il il MER cisameeerssr MTP CONFIG reserved reserved options MTP CONFIG O 0 0x0000 Define linksets MANS DINKSET lt linkset ich lt achacemc spc lt num limks gt lt ilacs gt locu Sx eei MTP LINKSET 0 al al Os 2 0x08 Define signaling links MOND LINK lt link ice lt llimkset ic gt lt link ied lt sle lt ls eiecl_ ich lt blink gt stream 16 lt stream gt lt timeslot gt lt flags gt Note For Septel ISA PCCS6 boards the first LIU port is whilst for Septel cP PCI boards the first LIU port is stream 0 MIP EINK 0 0 0 0 0 0 lb 00006 MT MT Define a route for each remote signaling point MEN INOW lt Clcs lt iliimisicie ach lt UsGic jee meals le P ROUTE 1 0 0x0008 Define any user provided Layer 4 protocol MTP USER PART service ind module id P USER PART 0x03 0x33 Application Note e Application Note 10 Enabling SMS in SS7
Download Pdf Manuals
Related Search