Home

What is Messaging Manager?

1. SERVICE SMS Submit 1 slee acs SMS Submit Added by xmsScp SERVICE SMS Deliver 1 slee acs SMS Deliver Added by xmsScp Note The service names must be exactly SMS Submit and SMS Deliver for the Messaging Manager Director service to function correctly The service keys 102 and 103 are provided by a question during installation These are the default values The service keys 120 and 121 must match the service keys defined in the tdp conf file For details on this see Editing tdp conf on page 24 SLEE cfg details for PME The following lines are added if the PME service is installed SERVICEKEY INTEGER 122 CCS SM MO Added by xmsScp SERVICEKEY INTEGER 123 CCS SM MT Added by xmsScp SERVICE CCS SM MO 1 slee acs CCS SM MO Added by xmsScp SERVICE CCS SM MT 1 slee acs CCS SM MT Added by xmsScp tdp conf The tdp conf file is the configuration file that is used by the system to define the trigger tables used to determine when to trigger a call to the SCF If it has been installed the acsScp package will have created tdp conf If acsScp has not been installed itis necessary to take a copy of the tdp conf example file that is installed by Messaging Manager and rename it to tdp conf No manual modification of this file is required unless SLEE service keys different to the recommended 120 and 121 are used in the SLEE cfg see SLEE cfg on page 23 Always make a
2. Success Success 144 NCC Messaging Manager Technical Guide FDA submit attempt success MM ASP Message 1541 CDMA Success Default routing path attempt E Message IS41 CDMA Success RC Submit Convert to RC FDA Attempt Deliver part of FDA EMI Fail Attempt Submit part of FDA Success Success RC Submit Convert to RC FDA Attempt Deliver part of FDA EMI Attempt Submit part of FDA EMI eooo d o ases Chapter 5 Configuring Messaging Manager Services 145 Mobile to Application diagram Using the Messaging Manager Multigate and the Messaging Manager Director modules MM can be configured to provide a Mobile to Application service In this example we will receive mobile originating IS 41 messages and deliver them to ASPs over EMI using FDA This diagram shows the modules required Messaging Manager node Editing the eserv config Using the example network on page 140 follow the steps below to set up MM to do MO SMS to ASP with First Delivery Attempt Step Action 1 Take a copy of the example eserv config provided at install of MM 2 Edit the eserv config file to have only two adapters an IS41 CDMA adapter and an EMI adapter Note You can place a comment tag at the beginning of each unwanted line Configure the 1S41 CDMA and EMI adapters In the xmsTrigger area of the configuration file configure the following features i
3. Refer to SMS CauseCodes on page 111 for a list of cause codes 39 defaultPermanentFailureCauseCode 39 defaultTransientFailureCauseCode Syntax Description defaultTransientFailureCauseCode cod Default SMS CauseCodes mappings for Transient failures if no releaseCauseMap entry matches Chapter 3 Configuring Messaging Manager Multigate 107 Optionality Allowed Refer to SMS CauseCodes on page 111 for a list of cause codes Default 33 Example defaultTransientFailureCauseCode 33 Delivery failure error class and status code Values of the parameters e deliveryFailureErrorClass e deliveryFailureStatusCode Set the default error class and status code to be used in a failure delivery report SMSDelAckMsg gt BearerData gt MessageStatus gt ErrorClass SMSDelAckMsg gt BearerData gt MessageStatus gt MsgStatusCode They must form a valid pair Valid pairs are Status code Bo to 1 91 Invalid pairs will be reset to 2 and 5 respectively in the code deliveryFailureErrorClass Syntax deliveryFailureErrorClass class Description This value will be used in the error class of delivery receipt messages which signify non delivery of a message Optionality Allowed 0 no error 2 temporary condition 3 permanent condition Default 2 Example deliveryFailureErrorClass 2 deliveryFailureStatusCode Syntax deliveryFailureStatusCode code Description This value will be used in
4. serviceType EMS teleservice 4101 allowAlternateDelivery true dataCodingMap data_coding 0x08 alphabet UCS 2 Chapter 3 Configuring Messaging Manager Multigate 93 messageClass 1 messageWaitingGroup 0 messageWaitingIndicator 0 messageWaitingType 0 data coding OxF0 alphabet GSM8Bit messageClass 1 messageWaitingGroup 0 messageWaitingIndicator 0 messageWaitingType 0 includePayloadDRInfo false maxValidityPeriod 0 smppDefaults outgoingOriginatingNumberRules fromNoa 2 prefix 04 min 4 max 32 remove 1 prepend 0064 resultNoa 1 fromNoa 3 prefix 4 min 4 max 32 remove 0 prepend 0064 resultNoa 1 outgoingDestinationNumberRules incomingOriginatingNumberRules incomingDestinationNumberRules a Global SMPP parameters Here are the parameters for configuring the global SMPP adapter suppressPathl Syntax Description Type Optionality Allowed Default Notes Example InfoReport suppressPathInfoReport true fals Do we want path connection reports to be suppressed Boolean true false true An ASP receives heartbeats from the SMSC when Messaging Manager is configured to operate as an SMSC then it will respond to these heartbeats These are logged in the xmsTrigger logfile This can cause the logfile to fill up unnecessarily If this parameter is set to true the he
5. Chapter 5 Configuring Messaging Manager Services 141 Configuring Messaging Manager Here is the process used to configure the service The following steps are carried out using the Messaging Manager screens See MM User s Guide Stage Description 1 Create adapters 2 Create nodes 3 Create schemes 4 Create Message Center 5 Open scheme 6 Configure adapters 7 Configure paths 8 Configure connections 9 Configure domain 10 Configure throttling 11 Configure triggering 12 Configure routing Application to Mobile Messaging Description Application to mobile is a simple service that provides basic delivery of SMSs to a mobile phone Application to Mobile diagram Using only the Messaging Manager Base module MM can be configured to provide an application to mobile service In this example we will receive EMI protocol messages from ASPs and deliver them to an SMSC over SS7 using the IS 41 protocol 142 NCC Messaging Manager Technical Guide The following diagram shows the modules required Messaging Manager node SLEE ane e Editing the eserv config Using the example network on page 140 follow the steps below to set up MM to do basic MT SMS Step 1 2 Action Take a copy of the example eserv config provided at install of MM Edit the eserv config file to have only two adapters an IS41 adapter and an EMI adapter Note You can place a comment tag at the beginning of each unwanted line
6. cdr CDR section parameters tracing tracing section parameters pstore pstore section parameters adapters first_adapter parameters second adapter parameter next adapter parameters Note The configuration of the adapters is described in Configuring Messaging Manager Multigate on page 63 High level parameters XMS trigger application accepts the following global parameters adapters Description Array of adapters and their parameters within See Configuring the Required adapters on page 63 allowConcatenatedFDA Syntax allowConcatenatedFDA true fals Description Whether or not we are allowed to perform First Delivery Attempt for concatenated messages Messages whose segment number is gt 1 Type boolean Optionality Allowed true false Default true Notes This can be overridden by each adapter This option is consulted for each outbound route candidate because it is entirely likely one would want to enable it for IP but disable it for SS7 Example allowConcatenatedFDA tru 40 NCC Messaging Manager Technical Guide alwaysProduceNonDeliveryReceipt Syntax Description Type Optionality Allowed Default Notes Example baseIDPSize Syntax Description Type Optionality Allowed Default Notes Example cdr Description Default alwaysProduceNonDeliveryReceipt true fals Global Un
7. defaultProtocolld If a protocol ID is found that is not in the protocolldMap this is the result value Default 0 Note Optional parameter defaultTransientFailureErrorCode The default MAP error code used for transient failures when no mapping from CS1 release cause is specified Default 32 Allowed See deliveryFailureStatusCode on page 73 for list of values deliveryFailureStatusCode Sets the default status code to be used in a failure status report Default 64 Allowed 0 to 127 See table of values for value meaning o Short Message received by the SME 1 Short message forwarded by the SC to the SME but the SC is unable to confirm deliver Short message replaced by the SC Reserved Values Chapter 3 Configuring Messaging Manager Multigate 73 Error in SME Quality of service not available Reserved transfer attempts SM Validity Period Expired SM Deleted by SC Administration SM does not exist The SM may have previously existed in the SC but the SC no longer had knowledge of it or the SM may never had previously existed in the SC Error in SME 112 127 Values specific to each SC disableConcatenatedSegmentPad Syntax Description Type Optionality Allowed Default disableConcatenatedSegmentPad true false Controls segment padding behavior in a concatenated message Boolean Optional default used if not set true false 74 NCC Messaging Manager Technical Guide Not
8. 13 Mmx Service MSG PATH DELIVER RTl1 TIME MAP SME Connl 5163 Mmx Service MSG SUBMIT SUCCESS INTERNAL SME Wrapper 2 Mmx Service MSG SUBMIT SMPP ASP1 44 Mmx Service MSG PATH SUBMIT ATTEMPT SMPP_SMSC1 42 Mmx Service MSG SUBMIT SUCCESS SMPP ASP1 42 Mmx Service MSG SUBMIT FAIL REJECT SMPP_ASP1 2 Mmx Service MSG NOTIFY SMPP_SMSC1 41 Mmx Service MSG PATH DELIVER ATTEMPT SMPP ASPl 41 160 NCC Messaging Manager Technical Guide Mmx Service MSG PATH DELIVER RT1 COUNT SMPP ASP1 41 Mmx Service MSG PATH DELIVER _RT1_ TIME SMPP ASP1 7329 Mmx Service MSG NOTIFY SUCCESS SMPP_SMSC1 41 Mmx Service MSG ROUTEINFO CDMA Foreign SMSC 9 Mmx Service MSG PATH LOCATE ATTEMPT CDMA SME Conn 9 Mmx Service MSG PATH LOCATE TEMP ERR CDMA SME Connl 2 Mmx Service MSG ROUTEINFO FAIL ROUTING CDMA Foreign SMSC 2 Mmx Service MSG ROUTEINFO SUCCESS CDMA Foreign SMSC 7 Mmx Service MSG PATH SUBMIT ATTEMPT EMI SMSC 25 Mmx Service MSG NOTIFY EMI SMSC 23 Mmx Service MSG PATH DELIVER ATTEMPT EMI ASP 21 Mmx Service MSG PATH DELIVER RT1 COUNT EMI ASP1 21 Mmx Service MSG PATH DELIVER RT1 TIME EMI ASP 3827 Mmx Service MSG NOTIFY SUCCESS EMI SMSC 23 Mmx Service MSG SUBMIT MAP SME Conn 11 Mmx Service MSG PATH SUBMIT ATTEMPT MAP MC 6 Mmx Service MSG SUBMIT SUCCESS MAP SME Conn 9 Mmx Service M
9. Configure the 1S41 and EMI adapters In the xmsTrigger area of the configuration file configure the following features if required e Collecting statistics on page 62 e Generating CDRs on page 56 Rename the eserv config that is in use to a known name Rename the copy of the eserv config that you have made all your changes to to be eserv config Reread the configuration file See Rereading the eserv config file on page 26 for details Configuring Messaging Manager Here is the process used to configure the service Chapter 5 Configuring Messaging Manager Services 143 The following steps are carried out using the Messaging Manager screens See MM User s Guide Stage Description 1 Create adapters 2 Create nodes 3 Create schemes 4 Create Message Center 5 Open scheme 6 Configure adapters 7 Configure paths 8 Configure connections 9 Configure domain 10 Configure throttling 11 Configure triggering 12 Configure routing Mobile to Application Messaging Description The mobile to application to service provides delivery of SMSs that originated on a mobile phone to an ASP Messaging Manager will attempt to deliver the SMS directly to the ASP falling back to an SMSC if the direct delivery FDA fails Setting the scene This example covers the configuration required for the following flows FDA deliver attempt success RC Submit Convert to RC FDA Attempt Deliver part of FDA EMI
10. D allowAlternat livery true dataCodingMap data_coding 0x08 alphabet UCS 2 messageClass 1 messageWaitingGroup 0 messageWaitingIndicator 0 messageWaitingType 0 data coding OxFO0 alphabet GSM8Bit messageClass 1 messageWaitingGroup 0 messageWaitingIndicator 0 messageWaitingType 0 32 NCC Messaging Manager Technical Guide includePayloadDRInfo false maxValidityPeriod 0 uw scheduledDeliveryTim convertMessageIdToHex fals fixedLengthMessageId tru smppDefaults outgoingOriginatingNumberRules fromNoa 2 prefix 04 min prepend 0064 resultNoa 1 4 max 32 remove 1 fromNoa 3 prefix 4 min resultNoa 1 outgoingDestinationNumberRules incomingOriginatingNumberRules incomingDestinationNumberRules mmxiSMPP so config IS 41 CDMA adapter lib xmsiIS41 so CDMAL 1005 adapterName pointCodes SSN 18 1006 earlyAckMC earlyAckSME false false natedFDA tru allowConcat config true true allowlncoming allowOutgoing PC 1005 SSN 6 GT originatingTimeout 20 smsreqTimeout 10 smdppTimeout 10 smdppTimeoutSME 10 fallbackAlphabet UCS 2 supportIS841 true defaultMessagePriority Normal defaultEndpointType SME 4 max 32 remove 0 prepend 0064
11. If e True and the incoming MO ForwardSM has TP Reply Path set allowAlternateDelivery will be set to false e False or the incoming MO ForwardSM has TP Reply Path not set allowAlternateDelivery will be set to true Default false Allowed true false hybridiseMapVersions If e True MAP version 1 MO ForwardSM messages will contain a MAP phase 2 SMS Submit e False they will contain a MAP phase 1 SMS Submit Default false Allowed true false 76 NCC Messaging Manager Technical Guide lastSegmentDeliveryReceiptOnly If true a delivery receipt will only be sent for the last part of a concatenated message Status report requests on the first parts of a concatenated message will be ignored Default false Allowed true false localTimeZone Time zone in which the service center that is the adapter is located The SM Service Center Time Stamps and Validity Period are set relative to this time zone Default UTC Allowed Any zoneinfo database time zone is acceptable maxUnsegmentedLength Length of TP User Data in octets beyond which messages will be segmented Default 120 mscTimeout Syntax mscTimeout seconds Description The timer for MSC delivery transactions It is the period at which an outgoing message that is while Messaging Manager waits for a response from the MSC network will be timed out The adapter will close the connection to the network and return a transient failure to Messaging Manage
12. It is intended that in future the same processing logic will be used for internally generated delivery receipts as for external ones Whenever it generates a delivery receipt MM will increment the following statistics MSG NOTIFY Detail field is INTERNAL DR path s statistics category MSG ROUTING DELIVER ee pe ee ge MSG_PATH_DELIVER_ATTEMPT Detail field is Inbound path s statistics category MSG_NOTIFY_SUCCESS Detail field is INTERNAL_DR path s statistics category MSG_NOTIFY_FAIL_ROUTING be O MSG_ROUTING_DELIVER_SUCCESS C MSG PATH DELIVER bucket COUNT Detail field is inbound path s statistics category See Routing class statistics Deliver on page 157 MSG PATH DELIVER bucket TIME Detail field is inbound path s statistics category See Routing class statistics Deliver on page 157 MSG PATH DELIVER result Where result can be one of e TIMEOUT e TEMP ERR e PERM ERR See routing class statistics Deliver on page 157 Example statistics printout Here is an example of a list of statistics produced while running MM Thu Sep 7 22 45 33 2006 Rims Service MSG GET ROUTING INFO 1484 Rims Service MSG IS41 SMSREQ ATTEMPT 113 Rims Service MSG IS41 SMSREQ PERM ERR 5 Mmx Service MSG ROUTING FDA 1344 Rims Service MSG GET ROUTING INFO SUCCESS 1479 Mmx Service MSG ROUTING LOCATE 74 Mmx Service MSG ROUTING FDA SUCCESS SUBMIT 21 Mmx Service MSG ROUTING Default 43 Chapter 6 Background Pro
13. This chapter provides a high level overview of the application It explains the basic functionality of the system and lists the main components It is not intended to advise on any specific Oracle Communications Network Charging and Control NCC network or service implications of the product In this chapter This chapter contains the following topics What is Messaging Manager 1 Messaging Manager Platform 5 Messaging Manager Multigate 6 Messaging Manager Director 8 Message Processing 9 Mobile to Mobile Messaging 13 Application to Mobile Messaging 14 Mobile to Application Messaging 16 Mobile to Mobile triggering to ACS 17 Instant Messaging 18 What is Messaging Manager Introduction Messaging Manager MM is a messaging system for mobile networks It acts as a Virtual Message Point VMP for a variety of different messaging traffic for example SIP email MMS and SMS Depending upon the role that it is performing the VMP can act as any of the following e Message Service Center MSC e Short Message Entity SME that terminates and or originates messaging traffic e Multi media Message Service Center MMSC e Email host MM integrates advanced routing and protocol delivery options with extended service control in order to support all forms of traditional MO SMS and MT SMS services while retaining flexible support for new types of messaging Processing model Messaging Manager s architectural approach as a Virtual
14. WEMT Wireless Enhanced Messaging Teleservice XMS Three letter code used to designate some components and path locations used by the Oracle Communications Network Charging and Control Messaging Manager on page 183 service and the Short Message Service The published code is MM on page 184 formerly MMX 188 NCC Messaging Manager Technical Guide Index A AAA 181 abortMessagesWithZeroLengthTPDA 73 About Installation and Removal 171 About This Document v AC 181 ACS 181 acs conf 23 acs conf settings 23 acsChassis configuration in acs conf 128 Adapter interface location 154 Adapter overview 65 adapterName 70 89 95 107 118 121 adapters 40 51 Adapters 154 Adding and Removing Replication Nodes 170 Advancing the Timestamp 94 alarmMask 73 109 allowAlternateDeliveryForWEMT 109 allowConcatenatedFDA 40 allowDirectDelivery 74 allowFDAforWEMT 109 allowIncoming 74 109 allowIncomingMap3 74 allowOutgoing 74 110 allowUserRequestedDeliveryReceipt 74 alphabet 100 alwaysProduceNonDeliveryReceipt 41 70 71 AMC 181 ANI 181 anti spam 3 51 API 181 Application to Mobile diagram 14 144 Application to Mobile Messaging 14 144 ASN 1 181 asn1Tags 81 ASP 181 ASP connection state management 7 Audience v Available adapters 154 Background Processes 153 baselDPSize 41 C cache size 61 callsPerMinute 54 callTimeFo
15. e With multiple alternate routing Chapter 1 System Overview 15 Mobile to Application Messaging Mobile to Application diagram Using the Messaging Manager Multigate and the Messaging Manager Director modules MM can be configured to provide a Mobile to Application service In this example we will receive mobile originating IS 41 messages and deliver them to ASPs over EMI using FDA This diagram shows the modules required Messaging Manager node Variations Mobile to Application messaging may be configured in several different ways using MM e NoFDA e With FDA only as shown e With multiple alternate routing that is with FDA using an SMSC as an alternative should FDA fail 16 NCC Messaging Manager Technical Guide Mobile to Mobile triggering to ACS Diagram Using the Messaging Manager Multigate and the Messaging Manager Director modules MM can be configured to provide a Mobile to Mobile service triggering to ACS In this example we will receive mobile originating MAP messages and deliver them to SMSCs over MAP having triggered them to ACS to offload all large messages to a separate SMSC The following diagram shows the modules required Messaging Manager Director onvergen Billing MES Manager Access rging Access Messaging Manager OSABE OSABE N Driver 2 Driver N Variations Using the Messaging Manager Director module messages may be triggered to ACS for advanced message processing in any o
16. resultNoa 2 max 32 fromNoa 999 prefix incomingDestinationNumberRules outgoingOriginatingNumberRules outgoingDestinationNumberRules emiDefaults defaultMessagePriority pstoreNumberRules fromNoa 999 prefix 010 prepend 7 min 1 m aa Normal min 1 max 32 remove 3 Chapter 2 Configuration 31 fromNoa 999 prefix 091 min 1 max 32 remove 3 prepend 7 timestampAdvance true timestampBucketSize 5000 timestampFlush 2 4 emiDefaults mmxiEMI so config Third adapter SMPP lib mmxiSMPP so pointCodes 1003 1004 SSN 0 adapterName SMPP1 earlyAckMC false earlyAckSME true allowConcatenatedFDA tru config suppressPathInfoReport true displayZeroPathReport false PathReportingInterval 60 fallbackAlphabet UCS 2 TLVs tlvID 0x0030 tlvType 0x01 profileTagID 4532781 direction inbound tlvID 0x020b tlvType 0x02 profileTagID 4532782 direction outbound tlvID 0x1382 tlvType 0x05 profileTagID 4532783 direction both smppDefaults throttledCommandStatus 88 ESME RTHROTTLED 88 teleserviceRoutingMap serviceType teleservice ll o allowAlternateDelivery true serviceType CMT teleservice 4098 allowAlternateDelivery true serviceType EMS teleservice 4101
17. sssssssssssssesseeeeeenennren nennen nennen nennen 17 Instant MESSAGING s ri onini I stetur di ese e terra ee trea vera P ea ere db dares 18 Chapter 2 syn Me 21 Sul PH 21 Configuration Overview sssssssssssssssesesee enne enne ernst entente s stris intent enne sinn ns sistere renis 21 Configuring the Environment sssssssssesesseeee enne snnt nn tens ennt ennnen 22 eserv config Configuration enne enne enne nnne nennen resin sinn nn enne 25 Messaging Manager Configuration Sections in eserv config cccsccececsseceeeesteeeeesseeeeeeaaes 37 XIMSAGQGMM EE ER 38 OIN CIE 39 Tracing SMS cce te aii dese ghee ts eee nee 53 Configuring EDR Collection sssesesssssesseeeeee enne enne nnne trennt nennt inttr en renis 56 Setting Early Acknowledgment sss ener enne nennen nens 58 Setting Bajo RR E 60 Collecting Statistics 1 nee ee lie ubere e ed ee 62 Defining the Screen Language sssssssssssseseseseeseeee einn nnn en nennen senis tenen 62 Chapter 3 Configuring Messaging Manager Multigate 63 eJ teas 63 Configuring the Required Adapters sse eene ener enne 63 Configuring the MAP Adapt r neon recent rentas ap
18. tlvType lt type gt The type of TLV value Integer 1 byte long may be hexadecimal or decimal Mandatory Chapter 3 Configuring Messaging Manager Multigate 95 Allowed Five types are supported The mappings are e 0x01 gt INT8 e 0x02 gt INT16 e 0x03 gt INT32 e 0x04 gt CString e 0x05 gt OctetString Default Notes Example tlvType 0x01 profileTagID Syntax profileTagID profiletag Description The profile tag ID which the TLV maps to Type Integer 4 bytes long can be in hexadecimal or decimal Optionality Mandatory Allowed Default Notes Example profileTagID 453281 direction Syntax direction lt direction gt Description What type of SMPP message this TLV presents in Type String Optionality Mandatory Allowed Three options are supported e inbound e outbound or e both Default Notes Example direction inbound SMPP Defaults configuration The smppDefaults section of the eserv config specifies the SMPP values that will be used for connections smppDefaults throttledCommandStatus 88 ESME RTHROTTLED 88 teleserviceRoutingMap serviceType teleservice 0 allowAlternat livery true serviceType CMT teleservice 4098 allowAlternat livery true serviceType EMS teleservice 4101 allowAlternat livery true C Ibe lp 2 d 96 NCC Messaging Manager Technical Guide dataCodingMap data_
19. A list of asn1 tag values giving the location of the TBCD STRING within the private extension Compulsory if privateExtensions is present Member of the privateExtensions array asnlTags OxEO 0x80 profileTagID tagid The mapped profile tag ID in the Temporary Storage profile block Integer Compulsory if privateExtensions is present 327814 is a special profile tag being the one defined in ACS for holding the IMEI Therefore xmsTrigger will put the value extracted from the private extension into the InitialDP iMEI parameter as well as in a temporary storage profile tag 327814 is the only tag value this rule applies to Member of the privateExtensions array profileTagID 327814 name name A string for debug purposes String Compulsory if privateExtensions is present Member of the privateExtensions array name imei Chapter 3 Configuring Messaging Manager Multigate 79 Example Extract IMEI into profile tag The example configuration below is to extract the IMEI into profile tag 327814 according to the following Abstract Syntax Notation One ASN 1 notation mo ForwardSM OPERATION ARGUMENT SEQUENCE sm RP DA CHOICE imsi 0 IMPLICIT OCTET STRING SIZE 3 8 lmsi 1 IMPLICIT OCTET STRING SIZE 4 serviceCentreAddressDA 4 IMPLICIT OCTET STRING SIZE 1 20 noSM RP DA 5 IMPLICIT NULL
20. Here are the parameters for configuring the global MAP adapter alarmMask Alarm masking Default 0 Allowed Sum of 1 Mask that is do not generate originating timeout alarm 2 Mask alarm for Messaging Manager originated abort 4 Mask alarm for timeout waiting for HLR 8 Mask alarm for TCAP ABORT from HLR 16 Mask alarm for timeout waiting for MSC 32 Mask alarm for TCAP ABORT from MSC 64 Mask alarm for timeout waiting for SMSC 128 Mask alarm for TCAP ABORT from SMSC abortMessagesWithZeroLengthTPDA Syntax abortMessagesWithZeroLengthTPDA true false Description Whether or not MM shall return a TCAP U ABORT to the MSC upon receipt of a message with a zero length TP Destination Address Type Boolean Optionality Optional Allowed true false Default true Notes If set to false MM sends a SM Delivery Failure with the cause set to InvalidSMEAddress Example abortMessagesWithZeroLengthTPDA true Chapter 3 Configuring Messaging Manager Multigate 71 allowIncoming Syntax allowIncoming true false Description Determines whether inbound messages are allowed Optionality Mandatory Allowed true false Default false Example allowIncoming false allowOutgoing Syntax allowOutgoing true false Description Determines whether initial messages may be sent out through the MAP interface Optionality Mandatory Allowed true false Default false Example allowOutgoing false allowDirectDelivery Deter
21. Message class 0 2006 09 01 04 17 01 908 ID 010 i MAP Status Report Requested 0 2006 09 01 04 17 01 908 ID 010 i MAP MSISDN 004001000004 SCA 0040015114406267 2006 09 01 04 17 01 908 ID 010 i MAP OA 004001000004 DA 004001000004 2006 09 01 04 17 01 908 ID 010 i MAP Alternate delivery is allowed 2006 09 01 04 17 01 909 ID 010 i MAP Sending GenericSM to MMX 2006 09 01 04 17 01 909 ID 010 MMX Handling SM for adapter MAP1 Message Type Submit 0 2006 09 01 04 17 01 909 ID 010 MMX Source adapter protocol was MAP 2006 09 01 04 17 01 914 ID 010 MMX Inbound path MAP SME MAPI 162 NCC Messaging Manager Technical Guide 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 2006 09 0 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 04 0
22. Optionality Allowed Default Notes Defined by Oracle Example SECUREKey 123456 singleShotDeliveryReport Syntax singleShotDeliveryReport true fals Description Indicates if a Delivery Report failure should be retried or not Type Boolean Optionality Optional default used if not set Allowed e true use legacy behaviour for internally generated delivery reports e false DR failure is retried Default false Notes Set true to use legacy behaviour for internally generated delivery reports that is use a single delivery attempt through the inbound transaction No other processing logic for example Trigger Routing Rules is applied Example singleShotDeliveryReport tru sleeEventSize Syntax sleeEventSize bytes Description The number of bytes SLEE event should be This sets both e the size of events requested by xmsTrigger and e the size xmsTrigger constructs SLEE events to be Type Integer Optionality Optional default used if not set Allowed Default 2048 Notes This is the default size of SLEE event to construct You need to set a corresponding EVENTSIZE in SLEE cfg For more information about SLEE cfg see SLEE Technical Guide Example sleeEventSize 4096 statistics Description List of statistics parameters within See Collecting Statistics on page 62 stopRoutingOnTransientFailure Syntax stopRoutingOnTransientFailure true fals Description U
23. Routing Information for Mobile Services Used to cache HLR lookup information Note Now known as Messaging Manager Navigator SCA 1 Service Centre Address 2 Session Control Agent for Session Initiation Protocol SIP SCCP Signalling Connection Control Part part of the SS7 protocol stack SCF Service Control Function this is the application of service logic to control functional entities in providing Intelligent Network services SCI Send Charging Information An INAP operation sent from ACS to the SSP to control real time charging by the SSP SCTP Stream Control Transmission Protocol A transport layer protocol analogous to the TCP or User Datagram Protocol UDP SCTP provides some similar services as TCP reliable in sequence transport of messages with congestion control but adds high availability Session Diameter exchange relating to a particular user or subscriber access to a provided service for example a telephone call SGML Standard Generalized Markup Language The international standard for defining descriptions of the structure of different types of electronic document SGSN Serving GPRS Support Node SIM Usually referred to as a SIM card the Subscriber Identity Module is the user subscription to the mobile network The SIM contains relevant information that enables access onto the subscripted operator s network SIP Session Initiation Protocol a signaling protocol for Int
24. Syntax messageClass class Description The MAP DCS message class Allowed 0 none Default Notes Example 1 Display GSM class 0 also known as Flash 2 Mobile Equipment GSM class 1 3 SIM GSM class 2 4 External GSM class 3 0 Refer to GSM 03 38 version 7 2 0 for the full specification messageClass 1 messageWaitingGroup Syntax Description Allowed Default Notes Example messageWaitingGroup group The MAP DCS message waiting group 0 none not specified 1 Discard 2 Store 0 Refer to GSM 03 38 version 7 2 0 for the full specification messageWaitingGroup 0 messageWaitingIndicator Syntax Description Allowed Default Notes Example messageWaitingIndicator ind The MAP DCS message waiting indicator 0 Inactive none or not specified 1 Active 0 Refer to GSM 03 38 version 7 2 0 for the full specification messageWaitingIndicator 0 messageWaitingType Syntax Description Allowed Default Notes Example messageWaitingType type The MAP DCS message waiting type 0 none or not specified 1 Voicemail 2 Fax 3 Email 4 Other 0 Refer to GSM 03 38 version 7 2 0 for the full specification messageWaitingType 0 SMPP command statuses Here is a list of SMPP command statuses for use in 100 NCC Messaging Manager Technical Guide e throttledCommanaStatus e acsReleaseCauseToS8mppCommandStatus Sas Dem O ESME avea
25. The following section of the eserv config specifies the general parameters for all MAP connections adapters First adapter MAP lib xmsiMap so adapterName MAP1 pointCodes 1001 1002 SSN 8 earlyAckMC true earlyAckSME true allowConcatenatedFDA tru alwaysProduceNonDeliveryReceipt fals config global_parameters General MAP parameters Here are the general parameters for MAP adapterName Syntax adapterName name Description Identifier for the adapter Allowed Any text string but should be meaningful for example include the protocol used For example e MAP1 for MAP e EMI1 for EMI e SCA1 for SCA e SMPP1 for SMPP e CDMA1 for IS 41 CDMA e TDMA1 for IS 41 TDMA e Wrapper for Wrapper Default No default Notes This name must also be in the configuration database before Messaging Manager will run correctly See MM User s Guide alwaysProduceNonDeliveryReceipt Local Unsolicited Non Delivery Receipt flag Causes MM to send an unsolicited non delivery receipt in the event that a Early ack was performed b The outgoing message could not be delivered through any route This setting overrides the global flag Default Global alwaysProduceNonDelivery Receipt on page 41 value Allowed true false 68 NCC Messaging Manager Technical Guide Note This only applies when early ack is on See Setting Early Acknowledgement see Setting Earl
26. ao Chapter 2 Configuration 33 rimsInterfaceName rimsIf pathRetryRandomisation 1 pathRetrySegmentOffset 1 alarmMask 0 relaySmsNotifications false minHLRTransType 3 mdnHLRTransType 14 defaultTransientFailureCauseCode 33 destination busy defaultPermanentFailureCauseCode 39 other terminal problem throttledFailureCauseCode 35 destination resource shortage deliveryFailureErrorClass 2 deliveryFailureStatusCode 5 protocol CDMA allowFDAforWEMT true allowAlternateDeliveryForWEMT true tcapInterfaceServiceKey 22 incomingOriginatingNumberRules fromNoa 3 prefix 04 min 4 max 32 remove 1 prepend 0064 resultNoa 4 fromNoa 2 prefix 4 min 4 max 32 remove 0 prepend 0064 resultNoa 4 incomingDestinationNumberRules outgoingOriginatingNumberRules outgoingDestinationNumberRules End IS 41 CDMA adapter config section IS 41 TDMA adapter lib xmsiIS41 so adapterName TDMA1 pointCodes 1005 1006 SSN 18 earlyAckMC false earlyAckSME false allowConcatenatedFDA tru config allowIncoming true allowOutgoing true PC 1005 SSN 6 GT originatingTimeout 20 34 NCC Messaging Manager Technical Guide 4 End SCA smsreqTimeout 10 smdppTimeout 10 defaultMessagePriority Normal supportIS841 true rimsInterfaceN
27. disclosure modification and adaptation of the programs including any operating system integrated software any programs installed on the hardware and or documentation shall be subject to license terms and license restrictions applicable to the programs No other rights are granted to the U S Government This software or hardware is developed for general use in a variety of information management applications It is not developed or intended for use in any inherently dangerous applications including applications that may create a risk of personal injury If you use this software or hardware in dangerous applications then you shall be responsible to take all appropriate fail safe backup redundancy and other measures to ensure its safe use Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications Oracle and Java are registered trademarks of Oracle and or its affiliates Other names may be trademarks of their respective owners Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International Inc AMD Opteron the AMD logo and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices UNIX is a registered trademark of The Open Group This software or hardware and documentation may provide access t
28. false Defining the Screen Language Introduction The default language file sets the language which the Java administration screens will start in The user can change to another language once they have logged in The default language can be changed by the system administrator By default the language is set to English If English is your preferred language you can skip this step and proceed to the next configuration task Defining the Help Screen Language Example screen language If Dutch is the language you want to set as the default create a soft link from the Default lang file to the Dutch lang file 62 NCC Messaging Manager Technical Guide Chapter 3 Configuring Messaging Manager Multigate Overview Introduction This chapter explains how to configure the adapters in Messaging Manager Multigate In this chapter This chapter contains the following topics Configuring the Required Adapters 63 Configuring the MAP Adapter 67 Configuring the EMI Adapter 86 Configuring the SMPP Adapter 92 Configuring the IS 41 CDMA Adapter 103 Configuring the IS 41 TDMA Adapter 113 Configuring the SCA Adapter 115 Configuring the Wrapper Adapter 118 Configuring the Required Adapters Limitation All adapters have a section in this part of the configuration file The array of adapters section starts as below and is followed by a section for each available adapter adapters Note This technical guide documents all a
29. the adapter uses the MAP error configured in the defaultTransientFailureErrorCode parameter or the defaultPermanentFailureErrorCode parameter in the eserv config file If the MAP error code is 32 If the MAP error code determined by the above procedure is 32 sm DeliveryFailure then the error message s sm DeliveryFailureCause parameter is set to SC congestion for Messaging Manager transient failures or to subscriber not SC subscriber for Messaging Manager permanent failures MM Result Code sm DeliveryFailureCause transient failure SC congestion permanent failure subscriber not SC subscriber Example MAP config In this example SRI SMs will be received with SSN 8 and a PC other than 1001 1002 or 1003 This means that the message will match both MAP1 and MAP2 adapters so one will be picked based on GPRS support If the SRI SM specifies that GPRS is supported it will be passed to the MAP1 adapter otherwise it will be passed to the MAP2 adapter MM will send an SRI SM query to the HLR and replace the address it gets in the response with its own addresses If the HLR returns a VMSC address MM will replace it with the GT of the MAP2 adapter 5114406268 If the HLR returns an SGSN address MM will replace it with the GT of the MAP1 adapter 5114406267 The calling SMSC will then send an MT ForwardSM to one or other of these GT addresses The network should be configured to translate this to the appropriate point code so th
30. xmsWrapper interface xmsIf pe 55 ssn 7 type itu gt ny xmsTrigger pe 51 ssn 3 type itu gt n adapters xmsTrigger ChassisActions SendGenericMessageAction interfaceName xmsIf timeoutTick 5 tcapOrigAddr PC 0 SSN tcapDestAddr PC 0 SSN ussdChassisAction tcapInterfaceName hssScIf timeoutTick 5 recordResponseTimes fals macroNodes SendShortMessageNode xmsiWrapperlfName xmsIf tcapOrigAddr PC 0 SSN tcapDestAddr PC 0 SSN dateFormat SA Sd SB SY timeFormat I M Sp time24Format SH M 2 60 0 0 type type type type itu itu itu itu 36 NCC Messaging Manager Technical Guide callTimeFormat I M Sp maximumDestinations 1000 numberPlan 1 SendUSSDNotificationNode MSISDNTranslationType 2 destSSN 6 macroNodes XMS Messaging Manager Configuration Sections in eserv config Introduction The XMS section of the eserv config provides the configuration parameters for Messaging Manager It includes three sections e Servicelibrary for details see Configuring Messaging Manager to load ACS Control Plans on page 136 e xmsTrigger for details see xmsTrigger on page 151 on page 39 e macroNodes for details see Configuring Macro Nodes on page 126 High level overview Here is a high l
31. 0800 nnnnnn from a phone at location xxx then put the call through to bb bbb bbbb cron Unix utility for scheduling tasks crontab File used by cron CS1 ETSI INAP Capability Set 1 An ITU standard DB Database Diameter A feature rich AAA protocol Utilises SCTP and TCP transports 180 NCC Messaging Manager Technical Guide DP Detection Point DTMF Dual Tone Multi Frequency system used by touch tone telephones where one high and one low frequency or tone is assigned to each touch tone button on the phone EDR Event Detail Record Note Previously CDR The industry standard for CDR is EDR Event Detail Record Over time EDR will replace CDR in the NCC documentation EMI Exchange Message Interface protocol ETSI European Telecommunications Standards Institute FDA First Delivery Attempt the delivery of a short message directly to the SME rather than relaying it through the MC GMSC Gateway MSC The first MSC which handles a call For a MOC this is the caller s attached MSC For an MTC this is the first non transit MSC in the subscriber s network that receives the inbound call GPRS General Packet Radio Service employed to connect mobile cellular users to PDN Public Data Network for example the Internet GSM Global System for Mobile communication It is a second generation cellular telecommunication system Unlike first generation systems GSM is digital and thus introduced
32. Description How much to delay later segments of a concatenated message when a delayed retry is attempted Allowed integer Notes Example pathRetrySegmentOffset 1 PC Originating Point Code in outgoing MAP messages Default 55 Allowed integer in range 0 255 Note privateExtensions Syntax privateExtensions mapping Description List of private extension TBCD STRINGs from the MO ForwardSM for CPE manipulation Type Array Optionality Optional Allowed Default Notes Example privateExtensions extId 1 2 776 8 8 8 8 11 asnlTags OxEO 0x80 profileTagID 327814 name imei For full description including the ASN 1 notation used see Example Extract IMEI into profile tag on page 80 78 NCC Messaging Manager Technical Guide extid Syntax Description Type Optionality Allowed Default Notes Example asnlTags Syntax Description Type Optionality Allowed Default Notes Example profileTagI Syntax Description Type Optionality Allowed Default Notes Example name Syntax Description Type Optionality Allowed Default Notes Example extId value The ID of the private extension as a comma separated sequence of integers representing an object ID String Compulsory if privateExtensions is present Member of the privateExtensions array extId 1 2 776 8 8 8 8 11 asnlTags tags
33. EX Ey EY Od O0e OH O Om OM OS Ou OU OV Ow 96OW Oy are supposed to provide alternate representations Additionly OB implemented to represent alternative months names used standalone without day mentioned e Replaced by the day of month as a decimal number 1 31 single digits are preceded by a blank Equivalent to Y m d 9 G Replaced by a year as a decimal number with century This year is the one that contains the greater part of the week Monday as the first day of the week Replaced by the same year as in G but as a decimal number without century 00 99 k Replaced by the hour 24 hour clock as a decimal number 0 23 single digits are preceded by a blank Replaced by the hour 12 hour clock as a decimal number 1 12 single digits are preceded by a blank The same as E p Replaced by national representation of either ante meridiem or post meridiem as appropriate Equivalent to 96H 96M Equivalent to l M S p Replaced by the second as a decimal number 00 60 Equivalent to 96H 96M 96S Chapter 4 Configuring Messaging Manager Director 131 Replaced by a tab U Replaced by the week number of the year Sunday as the first day of the week as a decimal number 00 53 Replaced by the weekday Monday as the first day of the week as a decimal number 1 7 YN Replaced by the week number of the year Monday as the first day of the week as a decimal
34. INDEX1 as the install process will use these raw devices and the location to create the data and index tablespaces used to store relevant MMX tables The name and location of the file is IN service_packages XMS db install create SMP xms_devices sql Example blank file The blank file that is provided for the person installing MM to fill out looks like this Id xms devices sql v 1 1 6 1 2006 09 05 23 35 03 radamson Exp Copyright c 2006 Oracle This file contains the raw devices that will be used when creating the MMX DATA and MMX INDEX tablespaces on a cluster installation X X X X X ox Chapter 8 About Installation and Removal 169 Tt must be updated with the correct raw devices before installing the xmsSms package on a cluster x Raw device for the MMX DATA tablespace define DEVICE MMX DATA1 Raw device for the MMX INDEX tablespace define DEVICE MMX INDEX1 Example completed file An example of a file that has been completed by the person installing MM might look something like this Id xms devices sql v 1 1 4 1 2006 06 01 04 24 46 gthomas Exp Copyright c 2006 Oracle This file contains the raw devices that will be used when creating the MMX DATA and MMX INDEX tablespaces on a cluster installation It must be updated with the correct raw devices before installing the xmsSms package on a cluster X X X FF FF X Raw device for
35. This will populate the ACS global profile with the tag and value Syntax The syntax is mmxPMEConfig sh tag value where e lagis the name of the tag e value is the value for the tag Example To populate the global profile tag MM Enhanced SMS to Email Shortcode with the value 71 which is required for Enhanced SMS to Email processing mmxPMEConfig sh ENHANCED SMS TO EMAIL 71 or mmxPMEConfig sh ENHANCED SMS EMAIL 71 or mmxPMEConfig sh enhanced sms email 71 Chapter 7 Tools and Utilities 167 Tags This table describes each tag Tag Suggested Value BARRING_RESPONSE BAR_RESPONSE bar_response 00 Accept 01 Reject 02 Discard BARRING_NOTIFY BAR_NOTIFY bar_notify True False WAIT_FOR_HUNTING_RESULT WAIT_FOR_HUNTING wait_for_huntin True False UNIQUE_AUTOREPLY_INTERVAL AUTOREPLY_INTERVAL autoreply_ Note This is not required by MM 4 0 so does not have to be populated 7890 7899 801 T 71 ENHANCED SMS TO EMAILIENHANCED SMS EMAlL enhanced sm B i s email Note You can specify any of the three forms of each tag for example SMS TO IM or SMS IM or sms im Adding and Removing Replication Nodes Introduction SLCs running MM can be added to or removed from the main Messaging Manager platform configuration This means you can take a SLC out of service for a while and then add it back in as needed install routing node sh You must run the followin
36. When applying e Submit routing the key determinant of the outbound path is the message center name and the originating or domain address e Deliver routing the key determinant of the outbound path is the destination domain name or prefix and or originating domain name or prefix e Locate routing the key determinant of the outbound path is the destination domain name or prefix and or originating domain name or prefix For more information about routing see Routing 32806 htm in MM User s Guide 2 One or more outbound paths may be selected by the routing rule If there is more than one then each is tried in turn until success occurs or a permanent error is encountered 3 The adapter for each selected path will build the appropriate PDU based on the path protocol and select a connection within the path for transmission 4 If a message control plan is active it will be notified of the outcome from outbound routing to complete any service logic such as finalize charging retry by switching to an alternate route Routing Messaging Manager routes all messages based on one of the following e Routing class e Prefix and domain Triggering rules Messaging Manager allows rules to be determined that will trigger a message to ACS for further processing These ACS Triggering Rules may be set so that the message is triggered to ACS using a match based on a prefix containing one of the following e The originating number origi
37. adapters adapters Syntax adapters Description Type Optionality Allowed e MAP e CDMA e TDMA e EMI e SMPP e API Default Notes Example adapters gateways Syntax gateways Description Type Optionality 50 NCC Messaging Manager Technical Guide Allowed e MO SMS e MT SMS e VAS SMS Default MO SMS MT SMS VAS SMS Notes Example gateways MO SMS MT SMS VAS SMS options Syntax options ol1 o2 Description Array listing the licence options for this installation of MM Type Optionality Allowed e MCC Message Charging Control billing e SAS SMS Anti Spam Screening e EDR Express Delivery Routing also known as FDA e MCP Message Control Pack also known as AMC triggering to ACS e API Internal protocol that is wrapper adapter Default MCC SAS EDR MCP API Notes If the line is not present all options are enabled but maxConcurrentTransactions is limited to 5 Example adapters MCC SAS EDR MCP API limits The following parameters set the performance limits of the system These are pre defined by Oracle and should not be changed clearConcurrentTransactionsPeriod Syntax clearConcurrentTransactionsPeriod period Description How often to report that we are below warnConcurrentTransactionsPercentage concurrent transactions Type Optionality Allowed Default 10 Notes In seconds Example clearConcurrentTransactionsPeriod 10 maxConcur
38. an effect if the useCustomUSSDNotificationNoARules on page 126 parameter is set to 1 The denormalization rules have the same format as the rules from the acsChassis section of acs conf For more information see ACS Technical Guide Example sendUSSDNotification DenormalisationRule 00 2 0 E m useCustomUSSDNotificationNoARules Syntax useCustomUSSDNotificationNoARules 0 1 Description Which rules to use when denormalizing numbers which are sent by the Send USSD Notification node Type Boolean Optionality Optional default used if not set Allowed O Apply the standard denormalization rules 1 Apply the denormalization rules defined in the sendUSSDNotification on page 126 section Default 0 Notes Example useCustomUSSDNotificationNoARules 1 Configuring Macro Nodes Introduction Macro nodes are feature nodes that are used by ACS using the ACS Control Plan Editor but are not part of the ACS product They are supplied by other NCC applications but require the presence of ACS for use Macro nodes require some configuration to be entered into the eserv config file The following sections will detail the configuration that is necessary for the MM macro nodes The macro node reads the global configuration file eserv config on initialization Should the configuration of a macro node be changed the configuration files must be re read 126 NCC Messaging Manager Technical Guide For more information abou
39. backup copy of tdp conf before making any modifications Do not modify the file in any other way except as directly instructed by an Oracle technical engineer For further information on the IN Call Model and tdp conf please refer to Configuring IN Call Model Triggers Location The tdp conf file is located in IN service_packages XMS etc Example tdp conf This is an example of a tdp conf file The file must contain the following contents This file is supplied with the XMS product installation and should not be changed except as directly instructed by an Oracle Technical Engineer i I21 3 R all all L 120 3 R all all The following lines will also be present if the PME service is installed Trigger all Submit messages to the CCS SM MO service 122 3 R all all 24 NCC Messaging Manager Technical Guide Trigger all Deliver Notify RouteInfo messages to the CCS_SM MT service a1 S73 Rali 4p Note All lines starting with are treated as comments The first line defines the terminating triggering rule The second number on this line 121 must match the service key of the SMS_ Deliver SLEE service The second line defines the originating triggering rule The second number on this line 120 must match the service key of the SMS_Submit SLEE service eserv config Configuration Introduction The eserv config file is a shared configuration file from which many NCC applications read their configuration Ea
40. data between calling and called parties ITU International Telecommunication Union LMSI The subscriber s Local Mobile Subscriber Identity When the subscriber is roaming FDA uses both a LMSI and an IMSI MAP Mobile Application Part a protocol which enables real time communication between nodes in a mobile cellular network A typical usage of the protocol would be for the transfer of location information from the VLR to the HLR MC Message Centre Also known as SMSC MCC Mobile Country Code In the location information context this is padded to three digits with leading zeros Refer to ITU E 212 Land Mobile Numbering Plan documentation for a list of codes MDN Mobile Directory Number Messaging Manager The Messaging Manager service and the Short Message Service components of Oracle Communications Network Charging and Control product Component acronym is MM formerly MMX MIN Mobile Identification Number also known as an MSID Messaging Manager Formerly MMX see also XMS on page 188 and Messaging Manager on page 183 MM4 Multimedia Messaging Reference Point 4 defines the link between MMS Relay Server belonging to different MMSE Multimedia Messaging Service Environment MM7 Multimedia Messaging Reference Point 7 defines the link between the MMS Relay Server and MMS VAS Value Added Services applications MNC Mobile Network Code The part of an international address following the mobi
41. eene nennen sitne nrnn enne 170 Post installation Configuration ssesssssssseseseeeeeeeeeene enne nennen nennen nnne nnne 172 Appendix A Configuring IN Call Model Triggers 173 NCC Glossary of Terme eiecit ice o tnos een batte aere eO CERE ne OBS nnna 179 li 189 iv NCC Messaging Manager Technical Guide About This Document Scope The scope of this document includes all the information required to install configure and administer the Messaging Manager application Audience This guide was written primarily for system administrators and persons installing configuring and administering the Messaging Manager application However sections of the document may be useful to anyone requiring an introduction to the application Prerequisites Although there are no prerequisites for using this guide familiarity with the target platform would be an advantage A solid understanding of Unix and a familiarity with IN concepts are an essential prerequisite for safely using the information contained in this technical guide Attempting to install remove configure or otherwise alter the described system without the appropriate background skills could cause damage to the system including temporary or permanent incorrect operation loss of service and may render your system beyond recovery This manual describes syste
42. g Start timer schemes DBirbert Checks for Timer fires Change N g Start timer up all SCPs Checks for Timer fires Read most ignificant Change Updates table change Read table BEEN Compute differences Start timer Messaging Manager Multigate Introduction Multigate is the core VMP component that provides multi protocol message handling It employs a message model abstraction that gives enormous power to the service designer in classifying filtering and routing message traffic Multigate provides the message delivery and retry logic driven by the message model and dynamic changes made by Messaging Manager Director The following features are provided e Routing for all types of SMS including protocol translation e High speed criteria based classification filtering switching e First Delivery Attempt FDA to a destination handset or ASP e Alternate delivery options for conditional and or optimal routing e Forwarding to a specified SMSC or ASP through a load weighted group e Service logic triggering for charging and enhanced message services e Service level OA amp M support statistics and alarms and EDR management 6 NCC Messaging Manager Technical Guide Diagram Here is a diagram showing the Messaging Manager Multigate module Messaging Manager node Messaging Manager Multigate Trigger Routing Manager Manager Messaging Manager Flat files ETHERNET Using Messaging Manager Multigate T
43. greater enhancements such as security capacity quality and the ability to support integrated services GT Global Title The GT may be defined in any of the following formats e Type 1 String in the form 1 lt noa gt lt BCD address digits gt e Type 2 String in the form 2 trans type BCD address digits gt e Type3 String in the form 3 lt trans type num plan gt lt BCD address digits e Type 4 String in the form 4 lt trans type num plan gt lt noa gt lt BCD address digits The contents of the Global Title are defined in the Q713 specification please refer to section 3 4 2 3 for further details on defining Global Title GUI Graphical User Interface HLR The Home Location Register is a database within the HPLMN Home Public Land Mobile Network It provides routing information for MT calls and SMS It is also responsible for the maintenance of user subscription information This is distributed to the relevant VLR or SGSN Serving GPRS Support Node through the attach process and mobility management procedures such as Location Area and Routing Area updates HPLMN Home PLMN HTML HyperText Markup Language a small application of SGML used on the World Wide Web It defines a very simple class of report style documents with section headings paragraphs lists tables and illustrations with a few informational and presentational items and some hypertext and multimedia IDP INAP message Init
44. list TonNpi format must be enclosed in double quotes that is tttnnn Example origAddress 0064212 0064213 0064214 outputFile Syntax outputFile file Description The file that all tracing details are to be written to The primary output file Refer to note on maxNumFiles Type Optionality Allowed Default Itmp smsTrace trc Notes Once established Messaging Manager cannot remove or rename the tracing output file Example outputFile tmp smsTrace trc outputFileCycle Syntax outputFileCycle num Description Close and re open the file every N calls Checks for file size exceeded at this time also Type Optionality Allowed Chapter 2 Configuration 55 Default Notes Example shmKey Description Note shmSizeKb Description Note showPrivate Syntax Description Type Optionality Allowed Default Notes Example useTONNPI Syntax Description Type Optionality Allowed Default Notes Example 1024 Tracing buffered data is flushed to the output file before closing outputFileCycle 1024 Shared memory key Not currently supported Size of shared memory in KB Not currently supported showPrivate true fals Enables the viewing of the message payload in the tracing output Boolean Optional true Allows viewing of payload false Bars viewing of payload false showPrivate true useTONNPI true false Whether or not to inclu
45. match is used e IP protocols don t have a default path For more information about paths and connections see Paths and Connections in MM User s Guide A default routing class is assigned to the message based on its transaction type Each transaction is classified as one of Submit Deliver Notify Route Info or Command Exception If the message has a command routing class it will be forwarded directly to the configured default path for that protocol For more information see Default routing in MM User s Guide For more information about routing classes see Routing Class in MM User s Guide Each message is assigned to a default SMSC Operations performed by Messaging Manager will take place in a fashion consistent with the assigned SMSC name For more information see SMSCs in MM User s Guide Screening options are applied which potentially filter out undesired messages For more information about screening configuration see Screening Rules in MM User s Guide The originating address and destination addresses are matched against address rules to determine the originating domain name and the destination domain names For more information about addressing rules see Address Domains in MM User s Guide Message processing This table describes how Messaging Manager processes messages Stage 4 Description Based on the criteria assigned by the classification rules the message is checked by congestion control This may re
46. mdnHLRTransType 112 Message flow 9 Message processing 9 10 Message Processing 9 messageClass 102 messageWaitingGroup 103 Index 191 messageWaitingIndicator 103 messageWaitingType 103 Messaging Manager 185 186 190 Messaging Manager components 4 Messaging Manager Configuration Sections in eserv config 22 37 Messaging Manager Director 4 8 Messaging Manager EDRs 57 166 Messaging Manager features 3 Messaging Manager Multigate 4 6 Messaging Manager Platform 5 min 67 MIN 185 minHLRTransType 112 MM 186 190 MM and XMS naming conventions 21 MM4 186 MM7 186 MMX Notification Standard Application Port Example 137 138 mmxlsdn 46 mmxlsdnGprs 46 MNC 186 MO 186 MO SMS diagram 13 143 Mobile to Application diagram 16 148 Mobile to Application Messaging 16 146 Mobile to Mobile Messaging 13 Mobile to Mobile triggering to ACS 17 149 Mobile to SMSC Messaging 142 MOC e 186 MS 186 MSC 186 mscTimeout 79 123 mscVersionCacheSize 80 MSID 186 MSIN 186 MSISDN 186 MSISDNTranslationType 135 MT 186 MTC 187 MTP 187 mtTransactionLifetimeSeconds 46 Multigate 4 6 7 16 17 22 65 N name 82 131 natureOfAddress 80 Navigator 4 77 83 167 NOA 187 NOA and Normal rules 69 nonGprsAdapter 80 Normalization parameters 66 Note 135 138 Note 1 177 Notes 133 Notificatio
47. message has been successfully sent However this cannot work in all cases because some networks have a normal HLR lookup time that exceeds 3 seconds and an MSC response time that exceeds 2 seconds Forcing the sending party to wait during an FDA attempt both causes excessive use of network resources and alters the user experience A MMX B SMS invoked Acknowledgement Message sent Message acknowledged 58 NCC Messaging Manager Technical Guide e The alternative is to mimic the SMSC functionality and acknowledge the message the moment that the recipient appears valid This is called an early ack However this carries the risk that messages will be lost before they are delivered as there is no persistence or replication SMS invoked arly Acknowledgement Acknowledgement HLR lookup HLR result Message acknowledged Early ack configuration If desired earlyAck parameters can be defined at trigger level and or adapter level The values defined at adapter level will override those defined at Trigger Level Note The earlyAck parameters at adapter level are read from the adapter section of the eserv config file for the outbound adapter Not the inbound adapter Messaging Manager will produce an early ack when the message is accepted by the outbound adapter for delivery where early ack is on for one of the following e SME direct delivery e MC delivery to a Message Cen
48. number 01 53 If the week containing January 1 has four or more days in the new year then it is week 1 otherwise it is the last week of the previous year and the next week is week 1 Equivalent to e b Y AW Replaced by the week number of the year Monday as the first day of the week as a decimal number 00 53 Replaced by the weekday Sunday as the first day of the week as a decimal number 0 6 Replaced by national representation of the time Replaced by national representation of the date Replaced by the year with century as a decimal number Replaced by the year without century as a decimal number 00 99 Replaced by the time zone name Z Replaced by the time zone offset from UTC a leading plus sign stands for east of UTC a minus sign for west of UTC hours and minutes follow with two digits each and no delimiter between them common form for RFC 822 date headers A Replaced by national representation of the date and time the format is similar to that produced by date 1 Replaced by Send USSD Notification Node configuration Here are the macroNodes configuration parameters for the Send USSD Notification feature node destSSN Syntax destSSN int Description The SSN used in the outgoing destination TCAP address Type Integer Optionality Optional default used if not set Allowed Default 6 Notes Example destSSN 147 MSISDNTranslationType Syntax MSISDNTranslation
49. receiving delivery receipts Notes 1 ASP MM SS7 SMSC is only going to work if the HLR is configured to map the ASP s address to Messaging Manager 2 Handset MM SS7 SMSC Similarly the DR is only going to go via MM rather than straight to the handset if the network is set up to use Messaging Manager Navigator to direct MT traffic to Messaging Manager 3 DRs may also be produced due to the alwaysProduceNonDeliveryReceipt adapter setting 4 Some protocols for example SMPP have separate flags for requesting delivery and non delivery receipts 5 The Translation Type can be passed in delivery receipts sent by the MAP protocol This requires the TT to be set in the inbound adapter s outbound TT field Chapter 6 Background Processes 165 Chapter 7 Tools and Utilities Overview Introduction This chapter explains the tools and utilities that are installed by the Messaging Manager application and how to configure them In this chapter This chapter contains the following topics PME Configuration 167 Adding and Removing Replication Nodes 168 PME Configuration Introduction The mmxPMEConfig sh shell script is provided to allow you to configure the per product type profile tags that are used by MM for configuring terminating services such as PME and email IM lt gt SMS PME configuration script Run the command mmxPMEConfig sh from IN service_packages XMS bin as acs oper for each of the tags listed below
50. seconds of inbound transactions Type Integer Optionality Optional Default 5 Example inboundTimeout 5 interface Syntax interface name Description The SLEE service name for SCA to send messages from the SCA adapter to SCA Allowed String Default No default Notes This must match the entry in the SLEE cfg file Configure either this parameter or the serviceKey parameter but not both Example interface sca outboundTimeout Syntax inboundTimeout seconds Description The timeout in seconds of outbound transactions Type Integer Optionality Optional Default 10 Example outboundTimeout 5 PathReportingInterval Syntax Description Type PathReportingInterval seconds The frequency in seconds of path connection reports Integer Chapter 3 Configuring Messaging Manager Multigate 117 Optionality Optional Default 2 Example PathReportingInterval 60 serviceKey Syntax serviceKey key Description The SLEE service key for SCA to send messages from the SCA adapter to SCA Allowed 52 Default No default Notes This must match the entry in the SLEE cfg file Configure either this parameter or the interface parameter but not both Example serviceKey 52 Configuring the Wrapper Adapter General Wrapper adapter configuration The following section of the eserv config specifies the general parameters for the Wrapper adapter the endpoint for the SSMN mac
51. short messages through a mobile phone MT SMS is a service that allows customers to receive short messages via a mobile phone Using Messaging Manager to provide these services ensures the collection of meaningful statistical information and customer usage records 140 NCC Messaging Manager Technical Guide MO SMS diagram Using only the Messaging Manager base module MM can be configured to provide an MO SMS service In this example we will receive mobile originating MAP messages and deliver to the SMSC over TCP IP using the SMPP protocol The following diagram shows the modules required Messaging Manager node Editing the eserv config Using the example network on page 140 follow the steps below to set up MM to do basic MO SMS and MT SMS Step Action 1 Take a copy of the example eserv config provided at install of MM 2 Edit the eserv config file to have only two adapters a MAP adapter and an SMPP adapter Note You can place a at the beginning of each unwanted line Configure the MAP and SMPP adapters In the xmsTrigger area of the configuration file configure the following features if required e Collecting statistics on page 62 e Generating CDRs on page 56 5 Rename the eserv config that is in use to a known name 6 Rename the copy of the eserv config that you have made all your changes to to be eserv config 7 Reread the configuration file See Rereading the eserv config file on page 26 for details
52. size of the list If the list is allowed to grow huge then the flush will take longer since the whole list is traversed The actual number of entries in the list is determined by the incoming call rate the value of this parameter and the number of entries whose timestamp has been advanced Configuring the SMPP Adapter SMPP adapter overview The SMPP adapter communicates between the Messaging Manager platform and any configured ASPs and SMSCs using SMPP In a system using SMPP the adapter must be configured to know of all entities that may connect to it and all entities that it may connect to General SMPP configuration The following section of the eserv config specifies the general parameters for all SMPP connections adapters Third adapter SMPP lib mmxiSMPP so pointCodes 1003 1004 SSN 0 adapterName SMPP1 earlyAckMC false earlyAckSME true allowConcatenatedFDA tru config global parameters General SMPP parameters Here are the general parameters for SMPP adapterName Syntax adapterName name Description Identifier for the adapter Allowed Any text string but should be meaningful for example include the protocol used For example e MAP1 for MAP e EMI1 for EMI e SCA1 for SCA e SMPP1 for SMPP e CDMA1 for IS 41 CDMA e TDMA1 for IS 41 TDMA e Wrapper for Wrapper Default No default 92 NCC Messaging Manager Technical Guide Notes conf
53. system performance depending on the free IO bandwidth and the speed of the disks where the log file is being written We do not suggest tracing every SMS going through the system this could impact performance Tracing output is cached and the cache written to file periodically The file is closed and reopened when a specified number of tracepoints have been traced this flushes anything in the cache The tracing output is appended to the file specified each time the cache is flushed either because it is full or the outputFileCycle period is reached The tracing output file may become large over time so it is recommended that it be cleaned out regularly using the smslogcleaner Tracing output Here is an example tracing output 2006 09 01 04 17 01 902 ID 010 i MAP Started originating transaction for adapter MAP1 2006 09 01 04 17 01 902 ID 010 i MAP Got TCAP BEGIN OA 00001310 9 DA 0000139 8 2006 09 01 04 17 01 904 ID 010 o MAP incomingOriginatingNumberRules unmatched 2006 09 01 04 17 01 904 ID 010 4 000004 2006 09 01 04 17 01 905 ID 010 i MAP DataCodingScheme 0 2006 09 01 04 17 01 906 ID 010 i MAP Received MAP v2 ForwardSM 2006 09 01 04 17 01 907 ID 010 i MAP Message Type O 2006 09 01 04 17 01 908 ID 010 i MAP Text Test Message 2006 09 01 04 17 01 908 ID 010 i MAP Priority 0 2006 09 01 04 17 01 908 ID 010 i MAP Timezone 2006 09 01 04 17 01 908 ID 010 i MAP
54. the MMX DATA tablespace define DEVICE MMX DATA1 dev md ora0 rdsk d92 Raw device for the MMX INDEX tablespace define DEVICE MMX INDEX1 dev md ora0 rdsk d93 Installation and Removal Overview Introduction For information about the following requirements and tasks see NCC Installation Guide e NCC system requirements e Pre installation tasks e Installing and removing NCC packages PI packages An installation of Messaging Manager includes the following packages on the e SMS xmsSms e SLC xmsSop Checking the Installation Checking the xmsSms installation On successful installation the xmsSms package will have created the following directories 170 NCC Messaging Manager Technical Guide e llNiservice packages XMS e llNiservice packages XMS lib e llNiservice packages XMS tmp e llNiservice packages XMS db On successful installation the xmsSms package will have installed the following e llNiservice packages XMS bin lmmxPMEConfig sh This shell script allows you to populate the ACS Global Profile with the tags required for PME For more information on setting PME tags see PME Configuration on page 167 Compiling control plans manually If the ACS control plan compiler fails to compile control plans for any reason you can manually compile using the Control Plan Editor You should check the two control plans that use the Sub Control Plan node to make sure that these no
55. the TP Status code of delivery receipt messages which signify non delivery of a message Optionality 108 NCC Messaging Manager Technical Guide Allowed 0 Message accepted 1 Message deposited to Internet 2 Message delivered 3 Message canceled 4 Network congestion 5 Network error 6 Cancel failed 7 Blocked destination 8 Text too long 9 Duplicate message 10 Invalid destination 11 Message expired 31 Unknown error Default 5 Example deliveryFailureStatusCode 5 GT Syntax GT gt Description Originating global title in outgoing messages Optionality Allowed Default M Example GT mdnHLRTransType Syntax mdnHLRTransType type Description The global title translation type to be used for lookups to the HLR when using an MDN Default 3 Notes mdnHLRTransType 3 minHLRTransType Syntax minHLRTransType type Description The global title translation type to be used for lookups to the HLR when using a MIN Default 3 Notes minHLRTransType 3 originatingTimeout Syntax originatingTimeout num Description Configure our timeout on processing of inbound messages Allowed Seconds Notes originatingTimeout 20 Chapter 3 Configuring Messaging Manager Multigate 109 pathRetryRandomisation Syntax Description Allowed Default Notes Example pathRetryRandomisation seconds The amount of randomization for the delay interval when selecting a delay fora retry integer 1 pathRetryRandom
56. the network and return a transient failure to Messaging Manager Type Integer Optionality Optional Allowed 80 NCC Messaging Manager Technical Guide Default 5 Example rimsTimeout 5 rimsInterfaceName Syntax rimsInterfaceName name Description Name of the configured Messaging Manager Navigator interface Default rimslf Notes This must match the interface name in IN service packages SLEE etc SLEE cfg Example rimsInterfaceName rimsIf SCA Originating service center address in outgoing MAP messages Default none Allowed string Note Defaults to GT if not set or empty scheduledDeliveryTime Syntax scheduledDeliveryTime time Description The scheduled delivery time to set on outgoing submits that have previously failed at FDA Type String Optionality Optional default used if not set Allowed Format is as per the SMPP spec Default Null Notes Example scheduledDeliveryTime 000000001000000R Configures a 10 minute delay sgsnPrefixes Number rules to allow the adapter to distinguish between VMSC and SGSN for originating RIMS updates Default 000 smscTimeout Syntax smscTimeout seconds Description The timer for MC deliveries It is the period at which an outgoing message that is while Messaging Manager waits for a response from the SMSC network will be timed out The adapter will close the connection to the network and return a transi
57. used if not set true false false If true the response time is stored in tag 3932504 which is of type Unsigned 32 bit Integer and is named USSD_NOTIF_RESPONSE_TIME recordResponseTimes fals tcapInterfaceName Syntax Description Type Default Example timeoutTick Syntax Description Note Example tcapInterfaceName name The SLEE interface to send the USSD message to String hssSclt tcapInterfaceName hssScIf timeoutTick seconds The granularity of SLEE dialog timeout checks This can conflict with the option of the same name in the RIMS chassis actions In case of a conflict the value to use is undefined timeoutTick 5 acsChassis configuration in acs conf This text shows the denormalization configuration in acs conf for the Send USSD Notification node Note This text only shows the configuration which is specific to the node For more information about acs conf see ACS Technical Guide Chapter 4 Configuring Messaging Manager Director 125 acsChassis useCustomUSSDNotificationNoARules O 1 sendUSSDNotification DenormalisationRule 00 2 0 E sendUSSDNotification Syntax sendUSSDNotification DenormalisationRule rule D Description The denormalization rules to apply to outbound notifications from the Send USSD Notification node Type Array Optionality Optional not used if not set Allowed Default None Notes This parameter will only have
58. 1 F failureDeliveryReceiptText 45 FDA 183 File name and location 166 filename 58 166 fixedLengthMessageld 101 Flash 3 102 flush period 61 flushTime 139 fromNoa 67 G gateways 51 General EMI configuration 89 General EMI parameters 89 General IS 41 CDMA configuration 106 General IS 41 CDMA parameters 107 117 General IS 41 TDMA configuration 116 General IS 41 TDMA parameters 117 190 NCC Messaging Manager Technical Guide General MAP configuration 70 General MAP parameters 70 General SCA configuration 118 General SCA parameters 118 General SMPP configuration 94 General SMPP parameters 95 General Wrapper adapter configuration 121 General Wrapper adapter parameters 121 Global configuration parameters 175 Global EMI configuration 90 Global EMI parameters 90 Global IS 41 CDMA configuration 108 Global IS 41 CDMA parameters 109 118 Global IS 41 TDMA configuration 117 Global IS 41 TDMA parameters 118 Global MAP configuration 71 Global MAP parameters 73 Global SCA configuration 119 Global SCA parameters 120 Global SMPP configuration 96 Global SMPP parameters 97 Global Wrapper adapter configuration 122 Global Wrapper adapter parameters 122 GMSC 183 GPRS 183 gprsSupport 77 80 GSM 183 gt 122 GT 78 112 183 GTMap 78 GUI 184 H High level overview 37 High level parameters 40 HLR 184 honou
59. 1049 eserv config files delivered Most applications come with an example eserv config configuration in a file called eserv config example in the root of the application directory for example IN service_packages eserv config example Editing the file Open the configuration file on your system using a standard text editor Do not use text editors such as Microsoft Word that attach control characters These can be for example Microsoft DOS or Windows line termination characters for example M which are not visible to the user at the end of each row This will cause file errors when the application tries to read the configuration file Always keep a backup of your file before making any changes to it This will ensure you have a working copy to which you can return Loading eserv config changes If you change the configuration file then you must restart the appropriate parts of the service to enable the new options to take effect Rereading the eserv config file xmsTrigger re reads the configuration from eserv config on startup It can also be told to re read its configuration while running using the xmsRereadConfig sh script IIN service_packages XMS bin xmsRereadConfig sh usr Run the xmsRereadConfig script as the user who starts the xmsTrigger application from your console or telnet session on the SLC In most cases the user who starts the xmsTrigger application is acs oper xmsRereadConfig sh supports the following
60. 113 releaseCauseMap 113 releaseCode 113 remove 68 remove routing node sh 170 Rereading the eserv config file e 26 143 145 149 151 result 48 Result statistics e 156 158 resultNoa 68 RIMS 187 rimsInterfaceName 83 114 rimsTimeout 83 Routing 12 Routing class statistics 158 Routing options 7 9 routingScheme 48 Run install routing node sh 174 S SCA 18 66 83 118 187 SCA adapter overview 118 SCCP 187 Scenario assumptions 18 SCF e 187 scheduledDeliveryTime 84 105 SCI 187 Scope v SCTP e 188 SECURE section 23 50 SECUREkey 48 Send Short Message Node configuration 130 Send Short Message node parameter descriptions 130 Send USSD Notification Node configuration 135 SendGenericMessageAction parameters 126 Sending a MAP sm DeliveryFailure error message 86 sendUSSDNotification 128 ServiceConfig Parameters 137 serviceKey 121 serviceLibrary configuration 138 serviceLibrary parameters 139 Session 188 Setting Early Acknowledgment 22 41 44 59 71 Setting Pstore 22 48 60 Setting SMPP Parameters for Notifications from a Control Plan 136 Setting the scene 146 Setting up statistics collection 155 SGML 188 SGSN 188 sgsnPrefixes 84 shmKey 56 shmSizeKb 56 showPrivate 56 SIM 188 singleShotDeliveryReport 48 SIP 18 19 66 118 187 188 SIP to SMS 19 SLC 188 SLE
61. 27 callTimeFormat Syntax callTimeFormat format Description Defines the format of the lt CALL_TIME gt token Type Optionality Allowed See Date and time formats on page 131 Default 96l 96M Yp Notes Example callTimeFormat I M p dateFormat Syntax dateFormat format Description Defines the format of the lt DATE gt token Type Optionality Allowed See Date and time formats on page 131 Default WA d B Y Notes Example dateFormat SA d SB Y maximumDestinations Syntax maximumDestinations num Description Specifies the absolute limit of addresses that will get an SMS if the Profile Tag destination address type is used Default 1000 Notes The node will loop over the profile list sending notification SMSs for an individual call until this limit is reached This is purely a safety limit to prevent a massive load on the system and not intended to be the normal method of broadcasting there is already a better way to broadcast 1 million identical SMSs Example maximumDestinations 1000 name Description Name of unit type Note Unknown unit types will have a name of units numberPlan Syntax numberPlan num Description The Number plan value to use on the message Type Integer Optionality Mandatory Allowed These more or less follow the SMPP 0 unknown 1 isdn data 4 telex 128 NCC Messaging Manager Technical Guide 6 land_mobile 8 national
62. 4 04 04 04 04 04 04 04 04 04 04 say YN YN YN NN NNN NN YN NNN NI SN NN NN NN NIN NN YAY YN YANNI J J NYY J J J J J Se ee J 1 J J I aS 3 2 0 1 x2 4 2 C3 C C0 C0 2 O0 D X3 CX 0 x 0 0Dtt x OG O xXx uitizcc UO XO XO XO XO XO XO tO iO tO iO XO WO XO XO XO XO OO OO OO COO OO J 1 OY O1 935 936 936 937 997 938 944 945 945 945 945 947 948 948 949 949 951 951 951 951 951 953 953 953 958 958 958 961 UUUUUUUUUIUUUUUUKUUIUUUUUUKUUUUUUUUUUUUUUUUUUUuUUJ GJKUUGUUUUU U U U U UUUUU U 2 O OGO O GOTOO Q eS OS a ee SO oS 0 8 a Oe Oa sO a OG a oO 0x0 t utu OGO O Oo OO MX MX MX MX MX MX MX MX MX MX MX MX MX MX MX MX MX MX MX MX MX MX CDR for adapter MAP1 at 2006 Set originating domain 9242 Set destination domain 9242 1 concurrent transactions 1 Message not throttled Initialised routing class to Message Type Submit 0 Orig address 000004 Matched on domain Disabled triggering to AC Action Route 2 Outgoing Message Type Message Type Submit 0 Dest address 000004 Disabled triggering to AC Action Route 2 Routing class Submit 0 domain Submit orig trigger rule found Default routing class Submit 0 domain No matching Submit dest t
63. 41 true false IS 841 is an extension of IS 41 and allows the storing of an MSID in SMSRequestResults The feature is needed for IMSI masking true false true Set this to false if your hardware does not support IS 841 supportIS841 true throttledFailureCauseCode Syntax Description Allowed Default Example throttledFailureCauseCode cod Cause code to return when message is throttled Refer to SMS CauseCodes on page 111 for a list of cause codes 35 throttledFailureCauseCode 35 Configuring the IS 41 TDMA Adapter IS 41 TDMA adapter overview The IS41 adapter communicates between the Messaging Manager platform and SMSCs HLRs and MSCs using IS 41 The IS41 adapter needs to be configured to know about SMSCs that it will connect to General IS 41 TDMA configuration The following section of the eserv config specifies the general parameters for all IS 41 TDMA connections adapters Chapter 3 Configuring Messaging Manager Multigate 113 IS 41 TDMA adapter lib xmsiIS41 so adapterName TDMA1 pointCodes 1005 1006 SSN 18 earlyAckMC false earlyAckSME false allowConcatenatedFDA tru config global_parameters General IS 41 TDMA parameters The parameters for the IS 41 TDMA adapter are the same as those for the IS 41 CDMA adapter See General IS 41 CDMA parameters on page 104 for the description of each parameter Note The lib parameter is the s
64. 6 destSSN 135 Diagram 7 8 17 150 155 166 dialledHashEncoding 42 DialledNumberAvailable 139 dialledStarEncoding 42 Diameter 182 direction 99 Director 4 8 16 17 22 125 disableConcatenatedSegmentPad 77 disabled 119 Document Conventions vi doProtocolldMapping 77 DP e 183 DTMF 183 E Early ack configuration 59 Early ack functionality support 60 Early ack options 60 earlyAckMC 44 earlyAckSME 44 Editing the eserv config 143 145 148 150 Editing the file 26 Editing the SLEE cfg 24 Editing the statistics configuration 62 EDR 183 EDR collection 166 EDR configuration example 57 EDR fields 13 EDR parameters 58 EMI 183 EMI adapter overview 89 EMI Defaults configuration 92 EMI Defaults parameters 93 EMI error codes 91 92 emiDefaults 92 enable 61 62 enabled 55 Environment variables 175 eserv config 23 eserv config Configuration 22 23 25 154 eserv config files delivered 26 eserv config Macro Node configuration 129 ETSI 183 Example Extract IMEI into profile tag 81 82 Example blank file 171 Example completed file 172 Example current message type statistics 157 Example eserv config 26 Example inbound message statistics 156 Example MAP config 86 Example network 142 143 145 148 150 Example screen language 63 Example statistics printout 161 Example tdp conf 24 extld 8
65. 9 private 10 ermes 13 pc_ssn 14 ip 18 wap Default 1 Example numberPlan 1 BC Syntax PC pc Description The point code Type Integer Optionality Optional Allowed integer in range 0 255 Default Notes Example PC 123 SSN Syntax SSN num Description Subsystem number Allowed Integer in range 0 65535 Note Required if TCAP addresses are defined Example SSN 0 tcapDestAddr Description TCAP destination address to use when ACS and MM are on different machines Default Not set Note Required only if MM and ACS are on separate machines See PC SSN and type parameters Example tcapDestAddr PC 1 SSN 40 type itu tcapOrigAddr Description TCAP originating address to use when ACS and MM are on different machines Default Not set Note Required only if MM and ACS are on separate machines See PC SSN and type parameters time24Format Syntax time24Format format Description Defines the format of the lt TIME24 gt token Chapter 4 Configuring Messaging Manager Director 129 Type Optionality Allowed Default Notes Example timeFormat Syntax Description Type Optionality Allowed Default Notes Example type Syntax Description Allowed Example xmsiWrapperl Syntax Description Optionality Type Default Note Example Notes See Date and time formats on page 131 H M Z time24Format SH M Z timeFormat format Defines th
66. AIL ABORT 17 Rims Service MSG GET ROUTING INFO FAIL 5 Mmx Service MSG PATH DELIVER RT3 TIME 362381 Mmx Service MSG SUBMIT IDP ROUTE 42187 Mmx Service MSG ROUTING FDA SUCCESS DELIVER 484 Acs Service CALLS DISCONNECTED 479 Mmx Service MSG DELIVER FAIL REJECT 7 Mmx Service MSG SUBMIT IDP ACCEPT 343 Mmx Service MSG SUBMIT IDP REJECT 22 Mmx Service MSG NOTIFY FAIL REJECT 6 Mmx Service MSG SUBMIT FAIL SCREENING 2 Mmx Service MSG DELIVER IDP ROUTE 1419 Mmx Service MSG NOTIFY IDP TRIGGERED 7 Mmx Service MSG DELIVER FAIL ROUTING 4 Mmx Service MSG DELIVER IDP TRIGGERED 6 Mmx Service MSG SUBMIT IDP TRIGGERED 469 Mmx Service MSG ROUTEINFO IDP ROUTE 74 Mmx Service MSG NOTIFY SUCCESS 31 Rims Service MSG SET ROUTING INFO 23 Mmx Service MSG PATH DELIVER RTX TIME 3302637 Mmx Service MSG ROUTING LOCATE SUCCESS 69 Mmx Service MSG PATH DELIVER ATTEMPT 1566 Rims Service MSG MAP SRI SM ATTEMPT 41 Mmx Service MSG DELIVER SUCCESS 22 Mmx Service MSG PATH LOCATE TEMP ERR 3 Mmx Service MSG PATH SUBMIT TEMP ERR 25725 Mmx Service MSG NOTIFY IDP ROUTE 69 Mmx Service MSG ROUTING SUBMIT SUCCESS 1990 Mmx Service MSG ROUTING DELIVER SUCCESS 110 Mmx Service MSG SUBMIT EMI ASP1 23 Mmx Service MSG SUBMIT INTERNAL SME Wrapper 2 Mmx Service MSG PATH DELIVER ATTEMPT MAP SME Connl 16 Mmx Service MSG SUBMIT SUCCESS EMI ASP1 23 Mmx Service MSG PATH DELIVER RT1 COUNT MAP SME Connl
67. E 188 SLEE cfg 22 23 24 50 SLEE cfg details for PME 24 sleeEventSize 49 SMDPP 188 smdppTimeout 115 smdppTimeoutSME 115 SME 188 SMPP 188 SMPP adapter overview 94 SMPP command statuses 103 106 SMPP Defaults configuration 99 SMPP Defaults parameters 100 SMS 188 SMS forwarded to SIP 18 SMS to SIP 19 SMS CauseCode 114 SMS CauseCodes 110 113 114 116 SMSC e 189 smscTimeout 84 SMS MO 189 SMS MT 189 smsreqTimeout 115 SM TL 189 SN 189 Spam 4 51 splitLongMessages 84 SRF 189 SRI 189 SS7 189 ssn 123 SSN 71 84 90 96 107 115 122 131 189 SSP 189 statistics 49 Statistics 5 13 22 49 62 143 145 148 150 155 Statistics parameters 62 Stopping and starting xmsAgent 154 Stopping and starting xmsTrigger XMS 154 stopRoutingOnPermanentFailure 49 stopRoutingOnTransientFailure 49 Submit 160 Index 193 successDeliveryReceiptText 50 supportlS841 116 suppressPathInfoReport 92 97 Syntax 169 System Overview 1 T Tags 170 targetNoa 68 TCAP 189 tcapDestAddr 126 132 tcapInterfaceName 127 tcapInterfaceServiceKey 85 tcapOrigAdar 126 132 tcapTimeout 123 TCP 190 tcpWaitTimeMilliSec 39 TDMA 190 TDP 190 TDP event type values 179 tdp conf 23 24 teleserviceRoutingMap 105 tempdir 58 Temporary Storage Tag Configuration 136 Terminating t
68. EST_PC pc If defined all initialDPs will be sent with an SCCP called party See note 2 destination address that includes a Point Code defined by the integer pc Note This value may be defined in hex using a prefix of Ox DEST_SSN ssn If defined all initialDPs will be sent with an SCCP called party See note 2 destination address that includes a subsystem number defined by 174 NCC Messaging Manager Technical Guide Po the integer ssn DEST_GT 1 n addr or If defined all initialDPs will be sent with an SCCP called party DEST GT 2 t addr or destination address that includes a Global Title defined by the DEST GT 3 t p addr or T i B and the ee giu Be t DEST GT 4 t p n addr e initia value 1 to 4 identifies the Global Title type nis the NOA See note 2 tis the translation type p is the numbering plan addr is the address digits 0 to 9 A to F ACH WARN PERIOD period Sets the default ApplyCharging warning to occur period seconds before the end of the call ACH RESOURCE ad Sets the default ApplyCharging warning announcement tone to use the resource identified by the address digits ad Note This is only applicable if the underlying controlled call supports the ability to play announcements tones ACH Causes the default ApplyCharging warning to use announcement with ANNOUNCE messageld message identifier messageld Note This is only applicable if the underlying controlled call supports the ability to pl
69. Global IS 41 TDMA parameters The parameters for the IS 41 TDMA adapter are the same as those for the IS 41 CDMA adapter See Global IS 41 CDMA parameters on page 106 for the description of each parameter Configuring the SCA Adapter SCA adapter overview The SCA adapter provides support for SIP instant messaging It interacts with the NCC Session Control Agent SCA to convert SIP instant messages MESSAGE messages to and from SMSs The SCA adapter does not provide an interface to SIP clients but instead interacts with the SCA and xmsTrigger The SCA adapter converts adapts SipSleeEvents received from the SCA to GenericSM events processed by Messaging Manager In the reverse direction the SCA adapter converts GenericSM events to SipSleeEvents Note The SCA adapter in MM interacts with the SCA SCA must be configured in order to make the adapter work See SCA Technical Guide for SCA configuration details General SCA configuration The following section of the eserv config specifies the general parameters for all SIP connections adapters SCA SIP adapter disabled False interfaceName xmsIf lib mmxiSCA so adapterName SCA config Chapter 3 Configuring Messaging Manager Multigate 115 global_parameters General SCA parameters Here are the general parameters for SCA adapterName Syntax adapterName name Description Identifier for the adapter Allowed Any text string but shou
70. Message Point means that all messaging involves transactions that can combine real time charging with direct delivery to the destination This is the new messaging model that is aligned with the Internet age and replaces the previous store and forward model with higher value and lower cost infrastructure Chapter 1 System Overview 1 The VMP processes all message services in real time but it can integrate transparently with an existing SMSC for store and forward processing when real time delivery is not possible It delivers e High capacity messaging on low cost infrastructure e Very flexible switching and routing serving a multiple purposes e Proven efficiencies using real time charging and delivery e Enhanced message services using a service creation environment SCE e Performance gains over existing SMSC infrastructure e Anenhanced customer experience MM provides a broad range of message processing capabilities at both the network layer and at the service layer To the network it presents standard signaling interfaces to act in the role of e SMS IWMSC SMS Inter Working MSC e SMS GMSC SMS Gateway MSC e HLR proxy and emulation services e Email host with SEI e MMSC with mbuni By performing multiple functions in one system MM simplifies the messaging infrastructure and frees up resources MM components operating at the network layer can route traffic from one communication path to another and will automatically
71. NAP to the ACS service slee acs e Possibly pass delivery notifications to an MM interface for relay Chapter 6 Background Processes 151 Stopping and starting xmsTrigger XMS xmsTrigger is a SLEE interface Like other SLEE interfaces it is stopped and started through the SLEE administration scripts xmsTrigger is restarted when the SLEE is restarted For more information about starting and stopping the SLEE see SLEE Technical Guide Configuration xmsTrigger supports extensive configuration from eserv config For more information see eserv config Configuration on page 25 xmsAgent Purpose xmsAgent is a proxy gateway for the SMPP adapter It will proxy traffic from a single remote ASP MC to multiple xmsTrigger instances Stopping and starting xmsAgent xmsAgent is a SLEE interface Like other SLEE interfaces it is stopped and started via the SLEE administration scripts xmsAgent is restarted when the SLEE is restarted For more information about starting and stopping the SLEE see SLEE Technical Guide Adapters Adapter interface location Adapter interfaces are supplied as libraries These are located in IN service_packages XMS lib Adapter interfaces are libraries loaded by the xmsTrigger application and are started and accessed by this application as required Available adapters There are several adapters available from Oracle listed below mmxiSMPP so IS 41 CDMA xmsilS41 so IS 41 TDMA xmsilS41
72. Oracle Communications Network Charging and Control Messaging Manager Technical Guide Release 5 0 1 June 2013 ORACLE Copyright Copyright 2013 Oracle and or its affiliates All rights reserved This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws Except as expressly permitted in your license agreement or allowed by law you may not use copy reproduce translate broadcast modify license transmit distribute exhibit perform publish or display any part in any form or by any means Reverse engineering disassembly or decompilation of this software unless required by law for interoperability is prohibited The information contained herein is subject to change without notice and is not warranted to be error free If you find any errors please report them to us in writing If this is software or related documentation that is delivered to the U S Government or anyone licensing it on behalf of the U S Government the following notice is applicable U S GOVERNMENT END USERS Oracle programs including any operating system integrated software any programs installed on the hardware and or documentation delivered to U S Government end users are commercial computer software pursuant to the applicable Federal Acquisition Regulation and agency specific supplemental regulations As such use duplication
73. SG SUBMIT CDMA SME Conn 15 Mmx Service MSG PATH SUBMIT ATTEMPT CDMA MC 10 Mmx Service MSG SUBMIT SUCCESS CDMA SME Conn 14 Mmx Service MSG PATH SUBMIT TIMEOUT CDMA MC 3 Mmx Service MSG PATH SUBMIT TEMP ERR CDMA MC 4 Mmx Service MSG SUBMIT FAIL REJECT CDMA SME Conn 4 Mmx Service MSG PATH SUBMIT TEMP ERR EMI SMSC 2 Mmx Service MSG SUBMIT FAIL TIMEOUT MAP SME Conn 2 Mmx Service MSG ROUTEINFO MAP Foreign SMSC 5 Mmx Service MSG PATH LOCATE ATTEMPT MAP SME Conn 5 Mmx Service MSG ROUTEINFO SUCCESS MAP Foreign SMSC 5 Mmx Service MSG DELIVER MAP Foreign SMSC 5 Mmx Service MSG DELIVER SUCCESS MAP Foreign SMSC 5 Mmx Service MSG PATH DELIVER ATTEMPT CDMA SME Conn 10 Mmx Service MSG PATH DELIVER RT1 COUNT CDMA SME Conn 6 Mmx Service MSG PATH DELIVER RT1 TIME CDMA SME Conn 5468 Mmx Service MSG PATH DELIVER RT2 COUNT MAP SME Conn 3 Mmx Service MSG PATH DELIVER RT2 TIME MAP SME Connl 4170 Mmx Service MSG DELIVER CDMA Foreign SMSC 4 Mmx Service MSG PATH DELIVER_TEMP ERR CDMA SME Conn 4 Mmx Service MSG DELIVER FAIL ROUTING CDMA Foreign SMSC 2 Mmx Service MSG DELIVER SUCCESS CDMA Foreign SMSC 2 Tracing Introduction The Messaging Manager tracing feature when turned on captures all the major decision points in an MM transaction A trace identifier is generated by the originating adapter transaction and stored in the parent context at the start of a new call When the terminating transaction is created it fetches the stored trace i
74. Solicited Non Delivery Receipt Flag Causes Messaging Manager to send an un solicited non delivery receipt in the event that a Early ack was performed b The outgoing message could not be delivered via any route The default is false no response required however setting the parameter to true in the xmsTrigger section of either eserv config or adapter config level will mean a delivery receipt is sent for every delivery failure boolean true false false This only applies when early ack is on See Setting Early Acknowledgement see Setting Early Acknowledgment on page 58 alwaysProduceNonDeliveryReceipt fals baselDPSize value The base size in octets of the IDP without extensions Integer Optional default used if not set 200 The parameter is used to determine the size of slee events sent from XMS to ACS If errors similar to SleeException Overfill event detected 10000 are produced by xmsTrigger then increasing the above paramter may resolve them Warning This parameter should not be changed without the consultation of an eSG support engineer baseIDPSize 300 List of CDR setting and collecting parameters within See Configuring EDR Collection on page 56 N A convertMessageldToHex Syntax Description convertMessageldToHex true fals Global option to work around a potentially troublesome feature in some SMSCs where they return hex message ids in their submit_s
75. TDP will trigger Together with tdp cg Pn and cdPn it defines the condition that the trigger will fire on If set the trigger will not fire until the called party number has this number of digits Note The wild parameter can be set to a special value of stop If it is set to this value then the trigger will only fire when a stop digit is received keep If this optional flag is defined then all numbers triggered by this TDP will keep their stop digits if they have one 176 NCC Messaging Manager Technical Guide TDP event type values The following table defines the list of TDPs as defined by the CS 1 standard It also defines the point at which the trigger will be instantiated by the NCC IN Call Model E CS 1 Trigger Name Call Model TDP Creation Point origAttemptAuthorized aoe eee itsReceived collectedinfo ldgitsReceved 3 analyzedlInformation digitsReceived routeSelectFailure released cause 16 17 18 19 21 or 31 oCalledPartyBusy released Aparty cause 17 oNoAnswer released Aparty cause 18 19 or 21 answered Aparty mm oMidCall not supported 9 oDiscomect released Aparty cause 16 or 31 released Aparty cause 16 or 31 termAttemptAuthorized digitsReceived 13 released Bparty cause 17 released Bparty cause 18 19 or 21 answered Bparty not supported released Bparty cause 16 or 31 released Bparty cause 16 or 31 ringing Aparty ringing Bparty Appendix A Con
76. The total number of messages in the buffer is determined by the incoming message rate the flush period and the number of messages held in the buffer because their timestamp was advanced Advancing the Timestamp This functionality is used where EMI messages need to emulate SMSC behavior in advancing the timestamp This is done to ensure that the SM field is unique for messages to the same destination within the same 1 second time frame The functionality to advance the timestamp is implemented in the following way A list is kept that maps the B number to the last timestamp sent There is only one entry for a B number and it contains the last timestamp sent When the list is flushed the current system time is compared with the last timestamp in the list If this is older than the current system time the entry is removed For speed of lookup a hash map is used that contains the B number and a pointer to the entry in the list The size of the map is determined by the timestampBucketSize parameter This is fixed at startup and not reread at SIGHUP The following parameters influence this e timestampBucketSize For fast lookup this value should be big The larger the number the faster the lookup but requires more memory A small value gives slow lookup but requires less memory Chapter 3 Configuring Messaging Manager Multigate 91 e timestampFlush This value determines how often the linked list is flushed and therefore also the
77. Type int Description The destination party translation type for USSD messages sent by the Send USSD Notification node Type Integer Optionality Mandatory 132 NCC Messaging Manager Technical Guide Allowed Any valid For more information about valid types translation type see Q 713 0 Do not set a translation type Default 0 Notes Example MSISDNTranslationType 3 Note The Send USSD Notification node uses the Send Short Message time token formatting parameters to format the time tokens used in its notifications Creating Control Plans Creating service control plans Service control plans are created using the ACS Control Plan Editor The MM CPE nodes are described in the XMS feature nodes chapters in NCC Feature Nodes Reference Guide however for full details see CPE User s Guide Messaging Manager allows messages to be routed to ACS for more complicated processing than Messaging Manager alone may achieve To use this feature all ACS service control plans to be used for processing of Messaging Manager messages must be owned by the ACS super user that is the ACS level 7 user and the control plan versioning feature must be turned off See ACS User s Guide and CPE User s Guide for details Configuring Messaging Manager to Send SMPP Parameters in Notifications Setting SMPP Parameters for Notifications from a Control Plan You can use temporary storage tags to set parameters in MAP or SMPP messages sent in notificat
78. Versions false maxUnsegmentedLength 120 splitLongMessages tru alarmMask 0 honourReplyPath false ll p pathRetryRandomisation pathRetrySegmentOffset 1 localTimeZone UTC defaultTransientFailureErrorCode 32 defaultPermanentFailureErrorCode 32 incomingOriginatingNumberRules fromNoa 2 prefix 04 min 4 max 32 remove 1 prepend 0064 resultNoa 1 fromNoa 3 prefix 4 min 4 max 32 remove 0 prepend 0064 resultNoa 1 incomingDestinationNumberRules outgoingOriginatingNumberRules outgoingDestinationNumberRules ao privateExtensions 30 NCC Messaging Manager Technical Guide extId 1 2 776 8 8 8 8 11 profileTagID 327814 name imei xmsiMap so config Non GPRS MAP adapter lib adapterName pointCodes SSN config xmsiMap so MAP2 W 1003 8 GT 5114406268 TT 0 gprsSupport unsupported xmsiMap so config second adapter EMI lib SSN adapterName earlyAckMC earlyAckSME allowConcat mmxiEMI so EMI1 true true natedFDA tru config true false 60 suppressPathInfoReport displayZeroPathReport PathReportingInterval throttledErrorCode 4 transientFailureErrorCode 4 permanentFailureErrorCode 3 incomingOriginatingNumberRules asnlTags remove 0 OxEO
79. ages you send Feature Node Palette soa e Send Notification Credit Wallet Transfer CCS Charging Friends And Destination Configuration CCS Subscriber Friends And Family Configuration CCS Subscriber Account Status SMS CCS Wallet SMS Low Balance CCS Wallet Call Information SMS CCS Charging Universal Attempt Termination with CCS Charging CCS Billing Send Short Message Notification XMS Control Messaging Manager Temporary Storage Tag Configuration You configure the temporary storage tags that will be copied into the user data header in MAP or SMPP messages in the XMS ServiceConfig section of the eserv config file XMS ServiceConfig ParameterMappings UserDataHeader profileTag tag code informationElementIdentifier int profileTag tag code informationElementIdentifier int ServiceConfig Parameters Here are the ServiceConfig parameters profileTag Syntax profileTag tag code Description The number used to identify the profile tag to copy from temporary storage to the informationElementIdentifier in the user data header Type Integer Optionality Required Allowed A valid profile tag number Notes For more information about profile tags see ACS User s Guide Example profileTag 3932482 134 NCC Messaging Manager Technical Guide informationElementIdentifier Syntax informationElementIdentifier int Description The information element
80. ame rimsIf alarmMask 0 releaseCauseMap lt is this still in config gt releaseCode 31 SMS CauseCode 12 releaseCode 16 SMS CauseCode 12 releaseCode 17 SMS CauseCode 9 defaultTransientFailureCauseCode 8 defaultPermanentFailureCauseCode 7 causeCodeMap SMS CauseCode 12 failureCode 31 permanent false SMS CauseCode 9 failureCode 16 permanent true defaultReleaseCause 13 defaultReleaseCausePermanent fals deliveryFailureErrorClass 2 deliveryFailureStatusCode 5 protocol TDMA tcapInterfaceServiceKey 22 incomingOriginatingNumberRules fromNoa 3 prefix 04 min 4 max 32 remove 1 prepend 0064 resultNoa 4 fromNoa 2 prefix 4 min 4 max 32 remove 0 prepend 0064 resultNoa 4 incomingDestinationNumberRules outgoingOriginatingNumberRules outgoingDestinationNumberRules End IS 41 TDMA adapter config section IS 41 TDMA adapter definition SIP adapter disabled False interfaceName xmsIf lib mmxiSCA so adapterName SCA config sca serviceKey 52 Chapter 2 Configuration 35 interface sca pathReportingInterval inboundTimeout 5 outboundTimeout 5 Internal adapter The endpoint for the SSMN macro node lib xmsiWrapper so SSN 9 adapterName Wrapper config xmsTimeout 5 tcapTimeout 10
81. ame name as for IS41 CDMA but the adapterName is different Global IS 41 TDMA configuration The following section of the eserv config specifies the global parameters for all IS 41 TDMA connections config allowIncoming true allowOutgoing true PC 1005 SSN 6 GT originatingTimeout 20 smsreqTimeout 10 smdppTimeout 10 defaultMessagePriority Normal supportIS841 true rimsInterfaceName rimsIf alarmMask 0 releaseCauseMap lt is this still in config gt releaseCode 31 SMS CauseCode 12 releaseCode 16 SMS CauseCode 12 releaseCode 17 SMS CauseCode 9 defaultTransientFailureCauseCode 8 defaultPermanentFailureCauseCode 7 causeCodeMap SMS CauseCode 12 failureCode 31 permanent false SMS CauseCode 9 failureCode 16 permanent true 114 NCC Messaging Manager Technical Guide defaultReleaseCause 13 defaultReleaseCausePermanent fals deliveryFailureErrorClass deliveryFailureStatusCode protocol TDMA tcapInterfaceServiceKey 22 incomingOriginatingNumberRules fromNoa 3 prefix 04 min 4 max 32 remove 1 prepend 0064 resultNoa 4 fromNoa 2 prefix 4 min 4 max 32 remove 0 prepend 0064 resultNoa 4 incomingDestinationNumberRules outgoingOriginatingNumberRules outgoingDestinationNumberRules End IS 41 TDMA adapter config section
82. artbeat message being written to the xmsTrigger log is suppressed suppressPathInfoReport true 94 NCC Messaging Manager Technical Guide TLVs Syntax Description Type Optionality Allowed Default Notes Example TLVs parameters tlvID Syntax Description Type Optionality Allowed Default Notes Example tlvType Syntax Description Type Optionality TLVs tag maps List of TLV tags to map to a profile buffer Inbound e The SMPP adapter checks all inbound messages for the TLVs mentioned in TLVs section and if present passes them to slee acs which then populates the configured profile buffer in the temporary profile block for each TLV that was present Outbound e The CPE can use the copy set nodes to populate the configured profile tag IDs with data desired for the outbound TLVs and pass them to the SMPP adapter e The SMPP adapter uses this config to populate outbound TLVs if any of the configured fields are present Array of TLV elements Optional Please ensure tlvIDs and profileTaglDs are unique within each configuration TLVs tlvID 0x0030 tlvType 0x01 profileTagID 4532781 direction inbound tlvID 0x020b tlvType 0x02 profileTagID 4532782 direction outbound tlvID 0x1382 tlvType 0x05 profileTagID 4532783 direction both tlvID lt tag ID gt The TLV tag ID Integer 2 bytes long Can be in hexadecimal or decimal Mandatory tlvID 0x0030
83. at the MT ForwardSM goes to the right adapter So for this example 5114406267 1001 or 1002 Chapter 3 Configuring Messaging Manager Multigate 83 5114406268 1003 Example config adapters First adapter MAP lib xmsiMap so adapterName MAP1 pointCodes 1001 1002 SSN 8 earlyAckMC true earlyAckSME true allowConcatenatedFDA tru alwaysProduceNonDeliveryReceipt fals config abortMessagesWithZeroLengthTPDA true allowIncoming true allowOutgoing true allowDirectDelivery tru allowIncomingMap3 true allowUserRequestedDeliveryReceipt tru lastSegmentDeliveryReceiptOnly false tcapInterfaceServiceKey 22 originatingTimeout 10 smscTimeout 8 Timer for MC deliveries rimsTimeout 3 Timer for RIMS queries mscTimeout 15 Timer for MSC delivery transactions rimsInterfaceName rimsIf gprsSupport supported nonGprsAdapter MAP2 sgsnPrefixes 000 doProtocolldMapping false defaultProtocolId protocolldMap in 127 out Oo ll o ae fallbackAlphabet UCS 2 scheduledDeliveryTime defaultMessagePriority Normal PG x55 SSN 8 84 NCC Messaging Manager Technical Guide GT 5114406267 TT 0 GTMap prefix 0010019198 value 919827002402 tt 0 SCA 5114406267 natureOfAddress 1 international numberPlan 6 E 212 defaul
84. ault lib xmsilS41 so pcl pc2 Destination point codes array of messages to be handled by this adapter This parameter takes priority over SSN match pointCodes Optional Defined by network administrator pointCodes 1001 1002 104 NCC Messaging Manager Technical Guide SSN Destination subsystem number of messages to be handled by this adapter Syntax SSN num Description Allowed Valid subsystem number Notes Non zero to handle incoming TCAP Example SSN 18 Global IS 41 CDMA configuration The following section of the eserv config specifies the global parameters for all IS 41 CDMA connections config true true allowIncoming allowOutgoing PC 1005 SSN 6 GT wee originatingTimeout 20 smsreqTimeout 10 smdppTimeout 10 smdppTimeoutSME 10 fallbackAlphabet UCS 2 supportIS841 true defaultMessagePriority defaultEndpointType rimsInterfaceName rims pathRetryRandomisation pathRetrySegmentOffset alarmMask 0 relaySmsNotifications fa minHLRTransType 3 mdnHLRTransType 14 defaultTransientFailureCauseCode defaultPermanentFailureCauseCode throttledFailureCauseCode deliveryFailureErrorClass deliveryFailureStatusCode protocol CDMA allowFDAforWEMT true allowAlternateDeliveryForWEMT tcapInterfaceServiceKey n Normal SME If 1 1 lse 33 destination
85. ax loadReportingPeriod seconds Description The maximum SMS rate SMS per second is reported in the syslog The loadReportingPeriod sets the time between these reports Type integer Optionality Optional default used if not set Allowed Default 1 Notes Example loadReportingPeriod 10 mmxIsdn Syntax mmxlIsdn isdn Description The Messaging Manager VMSC address that will be returned in the result of a Routelnfo message Type number string Optionality Allowed valid ISDN Default Notes Example mmxlIsdn 0640041234567 mmxIsdnGprs Syntax mmxIsdnGprs sgsn Description MMX SGSN Address that will be returned in the result of a Routelnfo message if GPRS support was specified Chapter 2 Configuration 45 Type number string Optionality Allowed valid ISDN Default Notes Example mmxIsdnGprs 0640041234568 mtTransactionLifetimeSeconds Syntax mtTransactionLifetimeSeconds seconds Description How long correlation transactions between routelnfos and delivers should exist before being removed Type integer Optionality Allowed Default 30 Notes in seconds Example mtTransactionLifetimeSeconds 30 oracledatabase Syntax oracledatabase db Description The Oracle database Type String Optionality Optional Allowed Default Notes Example oracledatabase oraclepassword Syntax oraclepassword pw Description The Oracle password Ty
86. ay announcements tones ACS TONE id dur Causes the default ApplyCharging warning to use tone with identifier id for a duration of dur seconds Note This is only applicable if the underlying controlled call supports the ability to play announcements tones Note 1 If none of these entries is defined all InitialDPs will be sent without an SCCP calling party address Trigger detection point definitions After any global parameters have been set the configuration file may take one or more trigger detection point TDP definitions Each line defines a single trigger its trigger parameter values that get sent and the conditions under which it gets sent Each line takes the following form tdp svcKey eventType msgType cgPn cdPn wild keep The table below defines the meanings and forms of these parameters Global Parameter Value Type Description integer This integer value defines the point that the TDP is triggered at Together with cgPn cdPn and wild it defines the condition that the trigger will fire on See the TDP event type table for a list of valid values and meanings This parameter defines the serviceKey value that will be Appendix A Configuring IN Call Model Triggers 175 Global Parameter Value Type Description inserted into the initialDP message when this trigger fires eventType integer This parameter defines the eventTypeBCSM value that will be inserted into the InitialDP message when this trigger
87. busy 39 other terminal problem 35 4 destination resource shortage 2 ENS 22 Chapter 3 Configuring Messaging Manager Multigate 105 incomingOriginatingNumberRules fromNoa 3 prefix 04 min 4 max 32 remove 1 prepend 0064 resultNoa 4 fromNoa 2 prefix 4 min 4 max 32 remove 0 prepend 0064 resultNoa 4 incomingDestinationNumberRules outgoingOriginatingNumberRules outgoingDestinationNumberRules End IS 41 CDMA adapter config section Global IS 41 CDMA parameters Here are the parameters for configuring the global IS 41 CDMA adapter alarmMask Syntax alarmMask num Description Alarm masking Allowed Sum of 1 Mask originating timeout alarm 2 Mask SMSREQ timeout alarm 4 Mask SMSREQ abort alarm 8 Mask SMDPP timeout alarm 16 Mask SMDPP abort alarm Default 0 Example alarmMask 0 allowAlternateDeliveryForWEMT Syntax allowAlternateDeliveryForWEMT true false Description Allow alternate delivery if the Teleservice identifier is WEMT Allowed true false Default true Notes Wireless enhanced messaging teleservice WEMT is used to carry enhanced messaging service EMS over SMS Example allowAlternateDeliveryForWEMT true allowFDAforWEMT Syntax allowFDAforWEMT true false Description Allow FDA if the Teleservice identifier is WEMT Allowed true false Default true Notes Wireless enhanced me
88. bytes and the customer wants to set the application port in information element ID 5 to be four bytes containing 5498 in the first two bytes and also containing 5498 in the third and fourth bytes The customer uses a Set feature node to set profile tag 29020 to 360322426 Because 5498 is 0x157A in hexadecimal and 360322426 is 0x157A157A this means that the first two bytes of information element ID 5 will contain 5498 and the third and fourth bytes will also contain 5498 Chapter 4 Configuring Messaging Manager Director 135 Configuring Messaging Manager to load ACS Control Plans Configuring MMX to load ACS Control Plans Messaging Manager uses ACS control plans to perform advanced call processing These control plans must be loaded into cache in order to be used The following section of the configuration file sets the parameters for this serviceLibrary configuration Here is example of the configuration of the serviceLibrary section in the eserv config serviceLibrary validityTime 5 flushTime 60 maxAge 3600 DialledNumberAvailable false xmsUndoNumTranslation false Note The configuration parameters validityTime flushTime and maxAge apply only to caching of control plans which are matched by the Originator and Destination addresses Control plans that are matched purely by NAME of the control plan in the ACS triggering rules are actually stored in the ACS Global Cache The validity period on that cac
89. ced Type Optionality Allowed Default Refer to Prefix parameters You can specify 0 for all numbers Notes Prefixes in this list TonNpi format must be enclosed in double quotes that is tttnnn Example destAddress 0064213 0064214 enabled Syntax nabled true fals Description Determines whether Messaging Manager collects tracing details of numbers whose prefixes match those specified in the origAddress and destAddress parameter lists Type Boolean Optionality Allowed true false Default false Notes Example nabled fals maxFileSizeKB Syntax maxFileSizeKB siz Description The maximum file size in KB Type Integer Optionality Allowed Default 0 unlimited Notes Example maxFileSizeKB 0 54 NCC Messaging Manager Technical Guide maxNumFiles Maximum number of additional files Default 4 Note If e maxFileSizeKB is gt 0 and e maxNumFiles is gt 0 then every outputFileCycle a check to see if the outputFile size is gt maxFileSizeKB is made If max file size is exceeded the trace file is renamed to outputFile N where Nis 1 to maxNumFiles If all N files exist then the oldest file is overwritten origAddress Syntax origAddress addi add2 Description Array of originating addresses for which calls will be traced Type Optionality Allowed Default Refer to Prefix parameters You can specify 0 for all numbers Notes Prefixes in this
90. celncompatibilit 7 OtherRadiolnterfaceProblem Values 67 through 95 reserved treat as OtherRadiolnterfaceProblem 96 EncodingProblem o O 99 SupplementayServiceNotSuppoted Value 101 reserved MissingExpectedParameter MissingMandatoryParameter UnrecognizedParameterValue UnexpectedParameterValue 106 DataSizeError OtherGeneralProblems fF Values 108 through 255 reserved treat as 107 OtherGeneralProblems smsreqTimeout Syntax smsreqTimeout seconds Description Configure our timeout on processing of the outbound timers for the SMSREQ messages Allowed Example smsreqTimeout 10 smdppTimeout Syntax smdppTimeout seconds Description Configure our timeout on processing of outbound timers for the SMDPP messages Allowed Example smdppTimeout 10 112 NCC Messaging Manager Technical Guide smdppTimeout SME Syntax Description Allowed Default Note Example SSN Syntax Description Allowed Notes Example support Syntax Description Allowed Default Note Example m smdppTimeoutSME seconds Configure our timeout on processing of outbound timers for the SMDPP messages to an SME no default If it is not specified then smdppTimeout will be used smdppTimeout 10 SSN num Destination subsystem number of messages to be handled by this adapter Valid subsystem number Non zero to handle incoming TCAP SSN 18 S841 supportIS8
91. cess MMX Delivery receipt ID SMPP1 SMSC no dr MMX Got result success from term trans i MAP SMS delivery succeeded i MAP Sending MAP v2 ForwardSM Ack MMX Inbound adapter returned success O SMPP MMX returned success Messaging Manager EDRs EDR collection The xmsTrigger of Messaging Manager produces EDRs to be used in post processing as required Chapter 6 Background Processes 163 Diagram This diagram shows the components on the SLC that generate and migrate Messaging Manager EDRs ame foe ee ae aca File name and location Messaging Manager EDRs are saved to file in the eserv config e With the base filename specified by the filename on page 57 parameter in the format Base_file_nameDate_and_time cdr e Inthe location specified by the destdir on page 57 parameter by default IN service packages XMS cdr closed List of tags For a full list of tags and description of Messaging Manager EDRs refer to NCC Event Detail Record Reference Guide Delivery Receipts Introduction When an SMS is sent a delivery receipt may be requested A delivery receipt may be requested for a number of reasons e The sender may request a delivery receipt e MM may request a delivery receipt This may be used for billing on delivery of a SMS to the handset rather than just to the SMSC A delivery receipt is requested from the SMSC by setting the registered delivery flag After delivering th
92. cesses 159 Mmx Service MSG ROUTING Default SUCCESS 35 Mmx Service MSG ROUTING SUBMIT 40701 Mmx Service MSG PATH SUBMIT ATTEMPT 40693 Mmx Service MSG PATH LOCATE ATTEMPT 63 Mmx Service MSG PATH DELIVER TIMEOUT 841 Mmx Service MSG PATH DELIVER TEMP ERR 931 Mmx Service MSG PATH DELIVER RT1 TIME 103275 Mmx Service MSG PATH DELIVER RT2 COUNT 67 Mmx Service MSG PATH SUBMIT PERM ERR Mmx Service MSG PATH DELIVER RT2 TIME 192103 Mmx Service MSG PATH DELIVER RT3 COUNT 55 Mmx Service MSG PATH DELIVER RTX COUNT 147 Mmx Service MSG DELIVER 81 Mmx Service MSG NOTIFY 153 Mmx Service MSG PATH SUBMIT TIMEOUT 26 Acs Service CALLS AT 121 Mmx Service MSG ROUTEINFO 63 Mmx Service MSG SUBMIT SUCCESS 2637 Mmx Service MSG SUBMIT FAIL THROTTLED 10168 Mmx Service MSG SUBMIT FAIL REJECT 24 Mmx Service MSG SUBMIT FAIL ROUTING 24133 Mmx Service MSG SUBMIT 52511 Mmx Service MSG SUBMIT FAIL ABORT 6798 Mmx Service MSG PATH DELIVER RT1 COUNT 256 Mmx Service MSG SUBMIT FAIL TIMEOUT 559 Mmx Service MSG DELIVER FAIL ABORT 3 Mmx Service MSG ROUTEINFO SUCCESS 60 Mmx Service MSG ROUTING DELIVER 279 Mmx Service MSG ROUTEINFO FAIL ROUTING 3 Mmx Service MSG NOTIFY FAIL ROUTING 3 Mmx Service MSG NOTIFY F
93. cessfully delivered MM will increment this statistic MSG DELIVER SUCCESS 154 NCC Messaging Manager Technical Guide Current message types A control plan may be triggered based on the inbound message type If direct delivery is attempted on a Submit message that is the action changed to Deliver or FDA then two control plans Submit and Deliver may be triggered A new Deliver message is created for the delivery attempt so at this point the current message is a Deliver message and the inbound message is a Submit message This table describes the current message types MSG SUBMIT MSG DELIVER MSG NOTIFY Control Plans result statistics For all current message types a result statistic will be incremented IDP DISCARD In either of the following cases e Atrigger rule specifies a Discard action e Acontrol plan sends a ReleaseCall operation with the Discard release cause without having done a Connect or Continue IDP ACCEPT In either of the following cases e Atrigger rule specifies an Accept action e Acontrol plan sends a ReleaseCall operation with the Accept release cause without having done a Connect or Continue IDP REJECT In either of the following cases e Atrigger rule specifies a Reject action e A control plan sends a ReleaseCall operation with any release cause other than Accept or Discard without having done a Connect or Continue Notes e The format of the statistic produced is MSG_CurrentWMessag
94. ch NCC machine SMS SLC and VWS has its own version of this configuration file containing configuration relevant to that machine The eserv config file contains different sections each application reads the sections of the file that contains data relevant to it The eserv config file is located in the IN service_packages directory The eserv config file format uses hierarchical groupings and most applications make use of this to divide up the options into logical groupings Configuration file format To organize the configuration data within the eserv config file some sections are nested within other sections Configuration details are opened and closed using either or e Groups of parameters are enclosed with curly brackets e An array of parameters is enclosed in square brackets e Comments are prefaced with a at the beginning of the line To list things within a group or an array elements must be separated by at least one comma or at least one line break Any of the following formats may be used as in this example name route6 id 3 prefixes 00000148 0000473 name route7 id 4 prefixes 000001049 or name route6 id 3 prefixes 00000148 0000473 name route7 id 4 prefixes 000001049 or name route6 id 3 prefixes 00000148 0000473 name route7 id 4 Chapter 2 Configuration 25 prefixes 00000
95. coding 0x08 alphabet UCS 2 messageClass 1 messageWaitingGroup 0 messageWaitingIndicator 0 messageWaitingType 0 data coding OxF0 alphabet GSM8Bit messageClass 1 messageWaitingGroup 0 messageWaitingIndicator 0 messageWaitingType 0 includePayloadDRInfo false maxValidityPeriod 0 scheduledDeliveryTime convertMessageIdToHex fals fixedLengthMessageId tru SMPP Defaults parameters Here are the parameters for configuring the SMPP defaults in the SMPP adapter alphabet Syntax alphabet charset Description Character set of the desired alphabet Type String Allowed Binary 8859 1 8859 2 8859 3 8859 4 8859 5 8859 6 8859 7 8859 8 8859 9 8859 10 8859 11 8859 12 8859 13 8859 14 Chapter 3 Configuring Messaging Manager Multigate 97 8859 15 8859 16 ASCII7Bit 646 UTF 8 UCS 2 GSM7Bit GSMB8Bit GSM7BitComp GSMBinaryComp GSMUCS2Comp JIS XKJIS ISO 2022 JP PCK ko_KR euc SMPPPictogram Example dataCodingMap Syntax dataCodingMap Description alphabet UCS 2 datacoding parameters Data Coding Map allows you to modify the data coding of SMPP short messages to have a different interpretation of Message Class Waiting Group and character set to the predefined values If set here it will override any associated predefined DCS value that Messaging Manager starts up with Optionality Opt
96. contained in a GenericSM event This event is sent through the SLEE to the SCA Adapter The SCA Adapter converts the GenericSM event to a SipSleeEvent and forwards this event to the SCA Messaging Manager Director onvergen Billing Charging OSA CS Subscriber Access Charging Access SMS to SIP In this scenario Tom sends a short message to a special short code 64121 that will forward the short message to Dick s instant message user agent This scenario is similar to the scenario described above and the path is the same as shown in that diagram except that the destination address is specified as part of the message content for example Dick imdomain com Watson come here The SSMN or other node extracts the destination address from the content The short message is swallowed by MM SIP to SMS In this scenario Tom sends an instant message to Dick addressed to a handset the E 164 telephone number for example 64123402 The SCA converts this message to a SipSleeEvent and passes this to the SCA Adapter The SCA Adapter creates a GenericSM event and MM routes this to the MAP adapter The MAP adapter sends a MAP MO ForwardSM to the SMSC Chapter 1 System Overview 19 In this scenario Tom uses his E 164 alias for example 64123570 as the originating address This allows a reply through SMS e Manager node aging Manager Multigate oe Hd oe Hd eem perna 20 NCC Messaging Manager Technical Guide Chap
97. dapter 4 69 Configuring the Required Adapters 9 40 65 Configuring the SCA Adapter 5 118 Configuring the SMPP Adapter 4 94 Configuring the Wrapper Adapter 121 130 Connection 182 Control Plans result statistics 157 convertMessageldToHex 42 43 102 Copyright ii CPE 182 Creating Control Plans 135 Creating service control plans 135 cron 182 crontab 182 CS1 182 Index 189 Current message types 157 D Data life cycle 6 data coding 101 dataCodingMap 101 Date and time formats 130 132 133 dateFormat 130 DB 182 defaultEndpointType 110 defaultMapVersionMsc 74 defaultMapVersionSmsc 75 defaultMessagePriority 75 93 110 defaultPermanentFailureCauseCode 110 defaultPermanentFailureErrorCode 75 defaultProtocolld 75 defaultTransientFailureCauseCode 110 defaultTransientFailureErrorCode 75 deferred delete 61 Defining the Screen Language 22 62 Deliver 159 161 Delivery failure error class and status code 111 Delivery receipt 161 Delivery Receipt rules 167 Delivery Receipts 43 166 Delivery Report failure 13 deliveryFailureErrorClass 111 deliveryFailureStatusCode 75 111 deliveryReceiptld 42 43 Deployment diagram 3 Description 13 142 144 146 149 desegmentation 43 desegmentation failure cause 44 desegmentation failure code 43 desegmentation timeout 43 destAddress 54 destdir 58 16
98. dapters available from NCC By documenting all available adapters Oracle in no way commits to supplying the software thus described NCC will supply only the adapters purchased by the customer thus configuration for each installation will differ Adapter overview There are a number of interfaces that provide communication between the Messaging Manager platform and the ASPs and SMSCs These interfaces are provided as adapter interfaces Each of these interfaces performs several roles 1 Receive message send requests from an ASP or MS 2 Deliver outbound short messages to an SMSC or MS and return a delivery result to the application 3 Receive delivery notifications from an SMSC or MS and forward to MM 4 Relay delivery notifications to an ASP or MS Chapter 3 Configuring Messaging Manager Multigate 63 MM may be configured to use as many adapters as required Each adapter receives and transmits a different protocol Which adapters do need This will have been determined at the time of purchasing Messaging Manager There are several different adapters available e MAP MAP adapter for GSM networks e IS 41 CDMA IS 41 adapter for CDMA networks e IS 41 TDMA IS 41 adapter for TDMA networks e SCA SCA adapter for support of SIP instant messaging e SMPP SMPP adapter for ASP SMSC proxy connections e EMI UCP EMI adapter for ASP SMSC proxy connections Additional adapters may be purchased at a later date as required to acco
99. de TON and NPI in the address for trace prefix matching Boolean Optional true false useTONNPI true Configuring EDR Collection Configuring EDR collection Messaging Manager will produce EDRs to be used in post processing as required All EDR configuration is done in the cdr section of the eserv config file These EDRs will be saved to file in the location specified in the eserv config EDRs are saved to file in tag value pairs separated by in the following form tagl valuel tag2 value2 Please note that there are some parameters that may not be changed after startup These parameters are as follows e desidir 56 NCC Messaging Manager Technical Guide e num files e num files leaf All other cdr parameters may be changed as required EDR configuration example The following section sets the EDR collection and configuration for Messaging Manager For further details on the generation and format of EDRs please refer to the EDRs on page 163 section of the Messaging Manager Processes chapter cdr log true filename xms_ tempdir IN service packages XMS cdr current maxno 10000 time out 1800 destdir IN service packages XMS cdr closed num files 64000 num files leaf 64 EDR parameters Here are the EDR parameters destdir Syntax destdir dir Description The base filestore directory for completed EDR log files Type String Optionality Mandatory Allo
100. dentifier from the parent context Once tracing has been turned on for an SMS transaction it is on for the duration of that transaction and will not be turned off Trace points Here are guidelines as to the bare minimum of trace points in an Messaging Manager adapter transaction Input 1 Message received from network With which addresses 2 Message decoding information Do we allow alternate delivery Chapter 6 Background Processes 161 Which protocol version is this What was the message text if showPrivate 3 Message passed to MM Result from ParentContext handleSMSubmit 4 Response received from MM 5 Response sent to network Output 1 SMSubmit received from MM Is the delivery type SME or MC Do we need to consult a third party for example HLR for any reason What are the addresses involved 2 Outgoing encoding information Which protocol version are we using 3 Message sent to network 4 Response received from network 5 Response sent to MM Configuring SMSs to trace The prefixes of SMSs that are to be traced must be configured in the tracing section of the eserv config file Any number entered into the origAddress or destAddress lists in this section will be matched against the CLI or DN If any match is found then this specific Messaging Manager transaction will be traced through the system Setting the prefixes to be traced too broadly for example to trace all prefixes could have some impact on the
101. des are configured correctly The two control plans are e SMS Submit has a single instance of the Sub Control Plan that invokes SMS to IM via TAN e PME Delivery has two instances of the Sub Control Plan which invoke the IM to SMS and Email to SMS control plans The notes beside these nodes state which sub control plan they should be attached to Follow these steps to compile the control plans Step Action 1 Open the control plan in the Control Plan Editor 2 Open the Sub Control Plan node 3 Check that the right control plan is selected 4 Save the node 5 After this you can save and compile the main control plan Checking the xmsScp installation On successful installation the xmsScp package will have installed the following binaries e lN service packages XMSibin xmsTrigger e llNiservice packages XMS bin oraPStoreCleaner The following configuration files will have been installed e IN service packages XMSletc eserv config example e lN service packages XMSletc tdp conf example The following shared libraries will have been installed e llNiservice packages XMS lib xmsilP so e IN service packages XMS lib xmsiMap so e llNiservice packages XMS lib xmsilS41 so e llNiservice packages XMS lib xmsSvcLibrary so e lINiservice packages XMS lib libxmsMacroNodes so e llNiservice packages XMS lib libnumberRules so e IN service packages XMS lib xmsiWrapper so e lN service packages XMSl lib liboraPStore so Chapt
102. digits If s is also defined then the scflD of the ETC is also appended on afterwards in the same way For example With ETC RULES 6 4 and an ETC message with assistingSSPIPRoutingAddress 1111 correlationID 255 scflD 0x42 Then the actual assistingSSPIPRoutingAddress used will be 11110000550042 USER LIB library If defined the call model will use the user written shared object ibrary specified by the full pathname library when dealing with ApplyCharging operations ACza b c Sets the TCAP application context used by the call model to the comma separated list of OIDs supplied ORIG PC pc If defined all InitialDPs will be sent with an SCCP calling party See note 1 origination address that includes a Point Code defined by the integer pc Note This value may be defined in hex using a prefix of Ox ORIG SSN ssn If defined all initialDPs will be sent with an SCCP calling party See note 1 origination address that includes a subsystem number defined by the integer ssn ORIG GT 1 n addr or If defined all initialDPs will be sent with an SCCP calling party ORIG GT 2 t addr or origination address that includes a Global Title defined by the ORIG GT 3 t p addr or integers n t p and the number string addr The initial value 1 to 4 identifies the Global Title type ORIG GT 4 t p n addr SE ie A yP Fea note tis the translation type p is the numbering plan addr is the address digits 0 to 9 A to F D
103. dyinboundstte 0x0005 ESME already in bound state 0x0006 Invalid priority flag 0x0007 Invalid registered delivery flag 0x0008 0x000A Invalid source address 0x000B 0x000D 0x000E Invalid password Invalid system ID 0x0011 Cancel SM failed 0x0013 Replace SM failed 0x0014 Message queue full 0x0015 Invalid service type 0x0033 Invalid number of destinations 0x0034 Invalid distribution list name x0040 Destination flag is invalid submit multi x0042 Submit w replace functionality has been requested where it is either unsupported or inappropriate for the particular MC 0x0043 Invalid esm class field data 0x0044 Cannot submit to distribution list 0x0045 submit sm data sm or submit multi failed 0x0048 Invalid source address TON 0x0049 Invalid source address NPI 0x0050 Invalid destination address TON 0x0051 Invalid destination address NPI 0x0053 Invalid system type field 0x0054 Invalid replace if present flag Chapter 3 Configuring Messaging Manager Multigate 101 x0063 Predefined message ID is Invalid or specified predefined message was not found x0064 ESME receiver permanent app error code x0066 x0067 x00CO x00C1 x00C2 x00C3 x00C4 xooFE Transaction delivery failure XOOFF scheduledDeliveryTime x010E query_broadcast_sm operation failed Syntax scheduledDeliveryTime time Description An outgoing submit that has previously failed at FDA will have a scheduled deli
104. e MM allows individual routing based on the following criteria e Incoming protocol e MOorMT e Destination number e Originating number e Message content e Time of day Message Processing Introduction Messaging Manager processing falls into three logical parts Understanding the different parts is important to understand how to configure an MM service The three parts are 1 Incoming classification addressing on page 9 2 Message processing on page 10 3 Outbound routing on page 11 Message flow This diagram shows the flow of the message through Messaging Manager e nem gt HLR Incoming classification addressing This table describes how Messaging Manager processes inbound messages Stage Description 1 Messages are received over a protocol specific adapter Chapter 1 System Overview 9 Stage Description The configuration of which adapter will be used is done in eserv config For more information about eserv config see Configuring the Required Adapters on page 63 For signaling protocols the PC SSN GT and potentially the setting of the GPRS support parameters are used to direct the inbound message to the correct adapter The adapter establishes the inbound connection and path for the message using the configuration in the currently deployed routing scheme Notes e The adapter matches against the connections in the paths which have been configured to be available to it e The best
105. e The steps shown for the configuring of each service give the minimum that is required to be configured to achieve the service In this chapter This chapter contains the following topics Mobile to SMSC Messaging 140 Application to Mobile Messaging 142 Mobile to Application Messaging 144 Mobile to Mobile triggering to ACS 147 Chapter 5 Configuring Messaging Manager Services 139 Example network For the purposes of this document let us pretend that the network entities that are to be configured to use Messaging Manager are as follows TTT TSS ST ESS SE SSS Reserwe B t l Charge ae 4 Billing System i 00007 F ees amp MO and MT and MO and MT and MT SMS MO SMS MT SMS MO SMS Submits d subite Submits Submits HLR Deliver Deliver Deliver Deliver MO and MT and MO and MT and MT SMS MO SMS MT SMS MO Pec o N x SIM E 5 Deliver Submits gt a P Network SS7 Network F i MC ASP A ASP B These details will be used throughout the document as we work through examples of setting up and configuring Messaging Manager to perform standard services Mobile to SMSC Messaging Description The MO SMS service is a basic service that provides delivery to an SMSC of SMSs that originated from a mobile phone MO SMS and MT SMS are services that validate customers requests to send and receive short messages through mobile phones MO SMS is a service that allows customers to send
106. e SMS to the destination the SMSC sends a delivery receipt back to the sender This indicates if the SMS was successfully sent or not The delivery receipt contains an ID or delivery receipt ID that links it to the original SMS sent 164 NCC Messaging Manager Technical Guide Delivery Receipt rules Here are the basic delivery receipt rules for all adapters e Delivery Receipts for FDA to an SME Messaging Manager will produce delivery receipts for direct delivery where the originating party has requested a delivery receipt This applies for successful FDAs Only one attempt will be made to send these internally produced delivery receipts They will be sent direct to the sender over the originating Protocol e Delivery Receipts Received from a Message Centre Requested Delivery receipts can be sent to Messaging Manager over the IP adapters The original transaction must have had a delivery path where either inbound or outbound processing was over the IP adapter e Delivery Receipts are timestamped in local time These delivery receipts will be subject to the normal routing rules of the relevant adapter It is important to note that a delivery receipt can only be sent over a route that is going to an SME FDA Each delivery receipt is prefixed with the value of the deliveryReceiptld parameter Exceptions are e The TDMA instance of the IS41 adapter as this will not accept delivery receipts e MAP v1 of the MAP protocol will not support
107. e codes releaseCode Syntax releaseCode cod Description INAP releaseCode identifier Allowed Refer to SMS CauseCodes on page 111 for a list of cause codes rimsInterfaceName Syntax rimsInterfaceName name Description Name of the configured Messaging Manager Navigator interface Default rimslf Notes This must match the interface name in IN service packages SLEE etc SLEE cfg Example rimsInterfaceName rimsIf SMS CauseCode Description Error code in SMDPP Nack Notes Refer to SMS CauseCodes on page 111 for a list of cause codes SMS CauseCodes Here is a list of SMS CauseCodes used by the following parameters e releaseCauseMap e defaultTransientFailureCauseCode e defaultPermanentFailureCauseCod e throttledFailureCauseCode CauseCode AddressVacant AddressTranslationFailure NetworkResourceShortage NetworkFailure 4 InvalidTeleservicelD 5S OtherNetworkProblem a Values 6 through 31 reserved treat as 5 OtherNetworkProblem NoPageResponse DestinationBusy Chapter 3 Configuring Messaging Manager Multigate 111 Be ccn a5 DesinaionResoueeShorlags bs sMSDeiverPosioned SS a8 DestnaonNoLongeraiTHisAddress SS o OtherTeminalProblem O Values 40 through 47 reserved treat as 39 OtherTerminalProblem EE Values 48 through 63 reserved treat as 36 SMSDeliveryPostponed soo RadiolnterfaceResourceShortage Radiolnterfa
108. e format of the lt TIME gt token See Date and time formats on page 131 l M 96p timeFormat I M Sp type type Address type itu ansi type itu fName xmsiWrapperlIfName name Which SLEE interface name to send the message to Mandatory String xmslf This should be the interface name of the XMS remote wrapper interface xmsiWrapperlIfName xmsIf e While the three date and time formats as configured above are true to their names they need not be Each format will be used to convert the same time t into a string So the three options represent three completely interchangeable date formats e f ACS and Messaging Manager Director is on a different machine to Messaging Manager Multigate the whole of the tcapOrigAddr and tcapDestAddr is required and used for routing e f ACS Messaging Manager Director and Messaging Manager Multigate are installed on the same machine only the SSN from the tcapDestAddr is used the PC and type must be defined but are ignored by the system This is because Messaging Manager uses the SSN to select the adapter to route to 130 NCC Messag ing Manager Technical Guide Date and time formats The formats are all derived from the standard C function strftime which converts a time_t into ordinary characters Equivalent to m d y Replaced by the day of the month as a decimal number 01 31 E O POSIX locale extensions The sequences Ec EC Ex
109. e statistic listed below with the inbound path s statistics category in the detail field Inbound Message Type Statistice MSG COMMAND MSG SUBMIT MSG DELIVER Notify MSG NOTIFY Routelnfo MSG ROUTEINFO Note Command type messages are immediately relayed and no further processing is done The only further statistic that can be recorded for them is to indicate a successful relay When the recipient acknowledges receipt of a relayed command message MM will increment the MSG COMMAND SUCCESS statistic with the inbound path s statistics category in the detail field For detailed information on transaction types refer to MM User s Guide Result statistics For all message types except Command a corresponding overall result statistic will also be incremented at some subsequent point in the processing Failed screening FAIL SCREENING Throttled FAIL THROTTLED Control plan accept SUCCESS FAL ABORT 0 0 Inbound abort FAIL ABORT Note The format of the statistic produced is MSG_ nboundMessageType_ResultStatistic Example inbound message statistics Here are some examples of the statistics incremented Example 1 When a Submit message is rejected due to any of the screening checks MM will increment this statistic MSG SUBMIT FAIL SCREENING Example 2 When a Deliver message is rejected due to throttling MM will increment this statistic MSG DELIVER FAIL THROTTLED Example 3 When a Deliver message is suc
110. e two MAP adapters setting this parameter appropriately e Routing to an HLR for GPRS needs the adapters associated with both the incoming and outgoing paths to be GPRS supported Example gprsSupport supported GT Syntax GT int Description Originating Global Title in outgoing MAP messages Type Integer Optionality Optional default used if not set Allowed Default 5114406267 Notes Used if no match found in GTMap Also used when MM overrides the VMSC SGSN address in an SRI SM response with its own address Chapter 3 Configuring Messaging Manager Multigate 75 Example GT 5114406267 TT Syntax TT int Description The translation type used for the corresponding SCCP Calling Party GT Type Integer Optionality Optional default used if not set Allowed Default 0 Notes e This applies to both Forward SMs and SendRoutingInfoForSM messages e fthe TT value is specified in the control plan from within RIMS IS41 Query and MAP Query nodes it will override the default value specified in the configuration Example TT 0 GTMap Syntax GTMap array Description Map of incoming originating global title prefix to outgoing originating global title for MO Also indicates the translation type for SCCP Calling Party GT Type Array Optionality Optional default used if not set Allowed Default 0 Notes A GTMap Example prefix 0010019198 value 919827002402 tt 0 honourReplyPath
111. eType_ResultStatistic e f the message is rejected discarded or accepted by a trigger rule or control plan no further processing is done and the appropriate statistic is updated to indicate the final result Example current message type statistics Here are some examples of the statistics incremented Example 1 When a Submit message triggers a control plan MM will increment this statistic MSG SUBMIT IDP TRIGGERED Chapter 6 Background Processes 155 Example 2 When a trigger rule or control plan specifies a Route action for a Deliver message MM will increment this statistic MSG_DELIVER_IDP_ROUTE Example 3 When a trigger rule or control plan specifies a Relay action for a Notify message MM will increment this statistic MSG_NOTIFY_IDP_RELAY Example 4 When a trigger rule specifies a Discard action or a control plan sends a ReleaseCall operation with a Discard release cause and without having done a Connect or Continue for a Deliver message MM will increment this statistic MSG DELIVER IDP DISCARD Example 5 When a trigger rule specifies an Accept action or a control plan sends a ReleaseCall operation with a Accept release cause and without having done a Connect or Continue for a Submit message MM will increment this statistic MSG SUBMIT IDP ACCEPT Routing class statistics The message will then proceed to routing with a routing class e Deliver e FDA e Submit e Relay e Locate These are set from the m
112. ed digits If they can be understood by built in mechanisms the NOA can unambiguously be one of the values Subscriber National International or a finer classification determined by the protocol variant Otherwise the NOA is unknown and the dialed digits must be disambiguated by a set of usually simple rules specified by a Numbering Scheme Leading zeros are used in many countries but the leading characters could be any arbitrary sequence that the numbering scheme could specify Ultimately the usage of NOA is determined by the phone network itself which may classify and possibly modify a phone number while it is being transmitted between the service logic and the switch Configuring the MAP Adapter MAP adapter overview The MAP adapter communicates between the Messaging Manager platform and e HLR and MSC in FDA situations e SMSOCs using MAP In a system using MAP the MAP adapter must be configured to know of all entities that may connect to it and all entities that it may connect to The MAP adapter is compliant with several versions of MAP e Map v1 ETSI GTS 09 02 V3 11 0 1995 01 ETSI GTS 03 40 V3 7 0 1995 01 e Map v2 ETSI ETS 300 599 ed 3 1996 09 GSM 09 02 ETSI ETS 300 536 ed 4 1996 10 GSM 03 40 e Map v3 3GPP ETSI GSM TS 09 02 version 7 5 0 Release 1998 3GPP ETSI GSM TS 03 40 version 7 5 0 Release 1998 Chapter 3 Configuring Messaging Manager Multigate 67 General MAP configuration
113. efault Notes Example min Syntax Description Type Optionality Allowed Default Notes Example prefix Syntax Description Type Optionality Allowed Default Notes Example fromNoa noa The original nature of address NOA that the number is received from prior to normalization and denormalization fromNoa 306 max len The maximum number length Integer Optional default used if not set This is 999 Used in number normalization on page 64 and denormalization rules max 32 min len The minimum number length Integer Optional default used if not set 0 Used in number normalization on page 64 and denormalization rules min 4 prefix digit This rule is applied to numbers with this prefix String Optional One or more decimal digits Used in number normalization on page 64 and denormalization rules prefix 25 Chapter 3 Configuring Messaging Manager Multigate 65 prepend Syntax Description Type Optionality Allowed Default Notes Example remove Syntax Description Type Optionality Allowed Default Notes Example resultNoa Syntax Description Type Optionality Allowed Default Notes Example targetNoa Syntax Description Type Optionality Allowed Default Notes Example prepend digits Determines the digits that are to be prepended to the number after stripping any as specif
114. en is a check made for data older than its validity time Positive integer Optional 60 Applies to control plans matched on originator or destination addresses only flushTime 90 maxAge seconds The time after which an unused or unchanged control plan is dropped from the control plan cache Positive integer Optional 3600 Applies to control plans matched on originator or destination addresses only maxAge 1800 validityTime seconds The maximum age of the data before it is refreshed from the database Positive integer Optional Any positive integer 5 Applies to control plans matched on originator or destination addresses only validityTime 15 xmsUndoNumTranslation Syntax Description Type Optionality Allowed Default Notes Example xmsUndoNumTranslation true false Indicates when processing a long held reservation whether or not the service library will undo hash and star number mapping to regain the original dialed numbers Boolean Optional true false false If true undo hash and star number mapping to regain the original dialed numbers If false do not undo hash and star number mapping to regain the original dialed numbers xmsUndoNumTranslation true Chapter 4 Configuring Messaging Manager Director 137 Chapter 5 Configuring Messaging Manager Services Overview Introduction This chapter explains the steps required to configure several standard services Not
115. ent failure to Messaging Manager Type Integer Optionality Optional Allowed Default 5 Example smscTimeout 5 Chapter 3 Configuring Messaging Manager Multigate 81 splitLongMessages Syntax splitLongMessages true fals Description If the user data is too long to fit into a single MAP SMS this option will cause it to be split into multiple outgoing concatenated messages when set to true Type Boolean Optionality Optional Allowed true false Default true Notes Example splitLongMessages tru SSN Originating subsystem number in outgoing MAP messages Default 8 Allowed Valid sub system number tcapInterfaceServiceKey SLEE service key of the TCAP interface to use for sending outbound messages Default Must match the TCAP interface s service key as specified in the SLEE cfg file Note Required parameter throttledDeliveryFailureCause Syntax throttledDeliveryFailureCause caus Description MAP SM delivery failure cause to set when message is throttled Type Integer Optionality Optional default used if not set Allowed e SMFmemoryCapacityExceeded 0 e SMFequipmentProtocolError 1 e SMFequipmentNotSM Equipped 2 e SMFunknownServiceCentre 3 e SMFsc Congestion 4 e SMFinvalidSME Address 5 e SMFsubscriberNotSC Subscriber 6 Default 4 Notes Example throttledDeliveryFailureCause 0 Receiving a MAP sm DeliveryFailure error message When the adapt
116. er About Installation and Removal 171 Post installation Configuration Run install_routing_node sh For SLCs you must run the install_routing_node sh script to include the SLC in the Messaging Manager platform configuration 172 NCC Messaging Manager Technical Guide Appendix A Configuring IN Call Model Triggers Overview This introduces the generic configuration requirements of the NCC IN Call Model The NCC IN Call Model is not a separate product rather it is a set of libraries that is bound into a final usable interface such as the UCA ISUP Environment variables This table describes the UNIX shell environment variables to be configured Environment Variable Name Description Example Value TDP_DEFINITIONS Defines the full path name of the IN service packages SLEE etc tdp con Trigger Detection Point definition f file Trigger detection point TDP definition file The tdp conf file has two sections 1 Anumber of configuration parameters 2 Thetrigger tables used to determine when to trigger a call to the SCF Example This text shows an example tdp conf file A comment KEEP SD ETC RULES 6 3 31 3 request all 123 6 4 2 4 notify all 222 keep 31 3 request 2 122 3 222 5 keep Note All lines starting with are treated as comments If no TDP definition file is defined a default action is taken where e ALL calls are triggered to the SCF with a service key of 1 one and a
117. er receives a MAP error message from a MSC in direct delivery scenarios or from a SMSC the adapter translates the error to a Messaging Manager transient or permanent failure based on the mapping configured in the forwardSmErrorMap parameter in eserv config If the MAP error code is not specified in the forwardSmErrorMap parameter the default is permanent failure unless the MAP error code is 32 sm DeliveryFailure 82 NCC Messaging Manager Technical Guide In that case the adapter uses the hard coded mapping shown below to convert from the FailureCause parameter contained within the sm DeliveryFailure error message to transient or permanent failure unknown service centre permanent failure 2 3 4 SC congestion transient failure 5 invalid SME address permanent failure 6 subscriber not SC subscriber permanent failure Sending a MAP sm DeliveryFailure error message Determining the MAP error code When the adapter receives an Messaging Manager transient or permanent failure the adapter translates the Messaging Manager failure message to a MAP error message If the Messaging Manager failure message specifies the release cause as a parameter in the Messaging Manager error message the adapter uses the mapping to MAP error configured in the releaseCauseMap parameter in the eserv config file If the Messaging Manager failure message does not specify a release cause or no mapping is configured in the releaseCauseMap parameter
118. ernet conferencing telephony event notification and instant messaging IETF SLC Service Logic Controller formerly UAS SLEE Service Logic Execution Environment SMDPP SMSDeliveryPointToPoint SM TL Message SME Short Message Entity an entity which may send or receive Short Messages It may be located in a fixed network a mobile or an SMSC SMPP Short Message Peer to Peer protocol SMS Depending on context can be e Short Message Service 186 NCC Messaging Manager Technical Guide e Service Management System platform e NCC Service Management System application SMSC Short Message Service Centre stores and forwards a short message to the indicated destination subscriber number SMS MO Short Message Service Mobile Originated SMS MT Short Message Service Mobile Terminating SM TL Short Message Transport Layer SN Service Number SRF Specialized Resource Function This is a node on an IN which can connect to both the SSP and the SLC and delivers additional special resources into the call mostly related to voice data for example play voice announcements or collect DTMF tones from the user Can be present on an SSP or an Intelligent Peripheral IP SRI Send Routing Information This process is used on a GSM network to interrogate the HLR for subscriber routing information SS7 A Common Channel Signalling system used in many modern telecoms networks that provides a suite of protoco
119. es If e true no non final message segments in a concatenated message will be padded Note Padding only affects messages which are UCS 2 encoded e false all non final message segments in a concatenated message which is UCS 2 encoded are padded to the maximum message segment length Example disableConcatenatedSegmentPad false doProtocollIdMapping Whether or not to apply mapping rules to the TP PID field Default false Allowed true false Note If true defaultProtocolId and protocolIdMap default values apply gprsSupport Syntax gprsSupport str Description Whether to ask GPRS questions of the HLR through Messaging Manager Navigator Also determines whether inbound messages are allocated to this adapter if separate MAP adapters have been configured for GPRS non GPRSmessages Type Integer Optionality Optional default used if not set Allowed e unsupported e supported e preferred Default supported Notes e When supported or preferred the adapter will include a GPRS supported flag in the Messaging Manager Navigator query Messaging Manager Navigator may reply with both the VMSC and SGSN numbers If preferred the MAP adapter will then use the SGSN number instead of the VMSC number If Messaging Manager Navigator replies with only the VMSC number this will be used instead of SGSN e f you are supporting both SMSCs that support GPRS and SMSCs that do not support GPRS you need to configur
120. es B IS41 uses D we cannot always rely on TC_PROTOS to get it right Make sure these values match with the ones in acs conf dialledStarEncoding D deliveryReceiptid Syntax Description Type Optionality Allowed Default deliveryReceiptId ID String prefixed to delivery receipt ID to ensure that internally generated IDs are unique any string blank 42 NCC Messaging Manager Technical Guide Notes Refer to Delivery Receipts on page 164 for details This must be hex value only or blank when convertMessageIdToHex on page 41 is set to true in an adapter section Example deliveryReceiptId desegmentation Syntax desegmentation true false Description Whether or not concatenated messages with multiple segments are desegmented into a single message for processing true or processed as individual messages false Type boolean Optionality Allowed true false Default false Example desegmentation false desegmentation_timeout Syntax Description Type Optionality Allowed Default Notes Example desegmentation timeout time The timeout for collecting the multiple segments of a concatenated message in seconds 0 or a positive integer 0 0 means no timeout is applied desegmentation false desegmentation failure code Syntax Description Type Optionality Allowed Default Notes Example desegmentation failure code n The value o
121. es tracing work The Messaging Manager tracing feature allows individual messages to be identified and traced To activate tracing the tracing section of the xmsTrigger configuration must be set to enabled and the prefixes to be traced must be defined Tracing output is written to file at a specified interval The tracing section of the eserv config file is required but may be empty In this case the tracing enabled parameter will be set to false by default For further details on how tracing works please refer to the Tracing on page 161 section of the Messaging Manager Processes chapter Tracing configuration The tracing section of the eserv config determines the SMSs that are to be traced if any tracing nabled tru showPrivate true outputFile tmp xmsTrigger trc outputFileCycle 512 maxFileSizeKB 0 maxNumFiles 4 shmKey 92403 shmSizeKb 64 callsPerMinute 2 origAddress 0064212 0064213 0064214 destAddress 0064213 0064214 useTONNPI true Tracing parameters Here are the tracing parameters callsPerMinute Syntax callsPerMinute num Description The maximum number of calls per minute to trace Type Integer Optionality Allowed Default 2 Chapter 2 Configuration 53 Notes Example callsPerMinute 2 destAddress Syntax destAddress addi add2 Description Array of destination addresses for which calls will be tra
122. essage type default trigger rule or control plan For detailed information on routing classes refer to MM User s Guide If there is no routing rule matching the specified routing class then a virtual routing class of Default will be used for all MSG ROUTING statistics This table describes the MSG Routing statistics mmi Nm MSG ROUTING routingClass When a message is passed to routing MSG ROUTING routingClass SUCCESS If a message is successfully delivered and the routing class is not FDA MSG ROUTING FDA SUCCESS DELIVER If the routing class is FDA and the message is successfully delivered via a Deliver routing rule MSG ROUTING FDA SUCCESS SUBMIT If the routing class is FDA and the message is successfully delivered via a Submit routing rule Once a message gets to the routing stage the overall result will be either SUCCESS FAIL ROUTING or TIMEOUT with the inbound path s statistics category in the detail field See Result statistics on page 154 156 NCC Messaging Manager Technical Guide Deliver If the routing class is Deliver or FDA MM will look for routing rules that specify a routing class of Deliver Each path listed in the routing rule will be attempted in turn until either a successful or permanent failure response is received Statistics are recorded for each path that delivery is attempted on with the detail field being populated by the outbound path s statistics category T
123. evel overview of the XMS section of the eserv config Ensure that your eserv config has at least the following sections present in it If a section is not present use a text editor to create the section for completion later XMS ServiceLibrary service library section parameters xmsTrigger SECURE secure section parameters xmsTrigger global parameters cdr CDR section parameters tracing tracing section parameters pstore Chapter 2 Configuration 37 pstore section parameters adapters first adapter parameters second adapter parameters next adapter parameters macroNodes SendShortMessageNode SendShortMessageNode parameters ADPBNode ADPBNode_parameters xmsAgent xmsAgent configuration Here is an example of the xmsAgent section of the eserv config xmsAgent tcpWaitTimeMilliSec 10 rateLimitAlarmIntervalSec 60 xmsAgent parameters xmsAgent accepts the following parameters rateLimitAlarmIntervalSec Syntax rateLimitAlarmIntervalSec num Description The number of seconds between rate limiting alarms on a connection s Type Integer Optionality Optional default used if not set Allowed Default 60 Notes Example rateLimitAlarmIntervalSec 60 tcpWaitTimeMilliSec Syntax tcpWaitTimeMilliSec msec Description The number of milliseconds that xmsAgent will wa
124. f required e Collecting statistics on page 62 e Generating CDRs on page 56 146 NCC Messaging Manager Technical Guide Step Action 5 Rename the eserv config that is in use to a known name 6 Rename the copy of the eserv config that you have made all your changes to to be eserv config 7 Reread the configuration file See Rereading the eserv config file on page 26 for details Configuring Messaging Manager Here is the process used to configure the service The following steps are carried out using the Messaging Manager screens See MM User s Guide Stage Description Create adapters 2 Create nodes 3 Create schemes 4 Create Message Center 5 Open scheme 6 Configure adapters 7 Configure paths 8 Configure connections 9 Configure domain 10 Configure throttling 11 Configure triggering 12 Configure routing Mobile to Mobile triggering to ACS Description The Mobile to Mobile messaging MO SMS service allows customers to send short messages from one mobile phone to another In this example messages will be triggered to an ACS control plan to route large messages to a specific SMSC Chapter 5 Configuring Messaging Manager Services 147 Diagram Using the Messaging Manager Multigate and the Messaging Manager Director modules MM can be configured to provide a Mobile to Mobile service triggering to ACS In this example we will receive mobile originating MAP messages and deliver them to SMSCs
125. f the desegmentation failure code Integer Mandatory The result code error type to use for desegmentation errors 1 transient failure 2 permanent failure 3 abort When the desegmentation process fails for example if an invalid segment number is received an error will be sent for any received segments that haven t had a response yet This does not apply if a segment fails to show up in that case a transient failure is returned for the other segments The error to use is configured by the two desegmentation_failure parameters desegmentation failure code 1 desegmentation failure cause Syntax Description desegmentation failure cause n The value of the release cause to use for desegmentation errors Chapter 2 Configuration 43 Type Optionality Allowed Default Notes Example earlyAckMC Syntax Description Type Optionality Allowed Default Notes Example earlyAckSMI LH Syntax Description Type Optionality Allowed Default Notes Example failureDeliv Integer Mandatory desegmentation failure cause 27 earlyAckMC true false Determines whether early acknowledgement is enabled for messages that are to be sent to an MC See Setting Early Acknowledgement see Setting Early Acknowledgment on page 58 boolean true false false earlyAckMC false earlyAckSME true false Determines whether early acknowledgement is enabled for messages
126. figuring IN Call Model Triggers 177 NCC Glossary of Terms AAA Authentication Authorization and Accounting Specified in Diameter RFC 3588 AC Application Context A parameter in a TCAP message which indicates what protocol is conveyed May indicate for example MAP CAMEL or INAP Also usually specifies the particular version of the conveyed protocol for example which CAMEL Phase ACS Advanced Control Services configuration platform AMC The Advanced Message Control component of Messaging Manager It provides e Real time billing interaction e Customized Service Control e SMS service plan capability e Enhanced service support Note Also known as SMS Director ANI Automatic Number Identification Term used in the USA by long distance carriers for CLI API Application Programming Interface ASN 1 Abstract Syntax Notation One a formal notation used for describing data transmitted by telecommunications protocols ASN 1 is a joint ISO IEC and ITU T standard ASP e Application Service Provider or e Application Server Process An IP based instance of an AS An ASP implements a SCTP connection between 2 platforms CAMEL Customized Applications for Mobile network Enhanced Logic This is a 3GPP Third Generation Partnership Project initiative to extend traditional IN services found in fixed networks into mobile networks The architecture is similar to that of traditional IN in that the control fu
127. fires See the TDP event type table for a list of valid values and meanings Generally this will be the same value as tdp msgType request or notify This parameter defines whether the TDP is sent as a TDP R request or TDP N notify Generally request is used here num or This parameter defines the calling party numbers that will natnum or trigger the TDP all Together with tdp cdPn and wild it defines the condition that the trigger will fire on e num defines the prefix of the calling party digits numbers must begin with these digits for the trigger to fire nat is optional and defines additionally a nature of address NOA of the calling party that must match for the trigger to fire If not provided a nature of 2 unknown is assumed If all is defined then ALL calling party numbers will match num or This parameter defines the called party numbers that will all Together with tdp cg Pn and wild it defines the condition that the trigger will fire on e num defines the prefix of the called party digits numbers must begin with these digits for the trigger to fire nat is optional and defines additionally a nature of address NOA of the called party that must match for the trigger to fire If not provided a nature of 2 unknown is assumed If all is defined then ALL called party numbers will match wild integer This optional parameter defines the number of digits that must be present in the called party numbers before the
128. g script to add a SLC to the Messaging Manager platform IN service packages XMS bin install routing node sh remove routing node sh You must run the following script to remove a SLC to the Messaging Manager platform IN service packages XMS bin remove routing node sh 168 NCC Messaging Manager Technical Guide Chapter 8 About Installation and Removal Overview Introduction This chapter provides details of the installation and removal process for the application In this chapter This chapter contains the following topics Pre installation 169 Installation and Removal Overview 170 Checking the Installation 170 Post installation Configuration 172 Chapter Pre installation Raw devices When installing xmsSms on a clustered SMS you must provide the location of the raw devices MM can allocate tablespace storage based on raw without a file system partitions This enhances the performance of MM on the SMS You must create the raw partitions before installing the database using tools such as the system s format command The raw devices file which you will be prompted to complete during the installation must contain the full paths of the device files for the appropriate partitions The partitions must be at least as big as the required datafile sizings listed in the sizing file which will be used by the installation You must provide the location of the raw devices created for DEVICE MMX DATA1 and DEVICE MMX
129. ged you need to send a SIGHUP to xmsTrigger with pstore to reread the configuration file nable false in eserv config disables pstore flushes cache deletes pstore then removes the database connection nable true in eserv config causes xmsTrigger to reread the pstore config updates oraPStore with the values and re establishes a database connection Pstore configuration example Here is an example of the pstore sub section of xmsTrigger pstore enable true cache size 10000 1 mean no max size flush period 10 interfaceName xmsStoreIf over size max age seconds 60 max age seconds 30 max writes per flush 10 deferred delete tru userpass scp scp Pstore parameters Here are the parameters in the pstore sub section of xmsTrigger cache size Maximum number of elements in cache Default 10000 Note This value is only read on startup 60 NCC Messaging Manager Technical Guide deferred_delet If true do not actually delete items from the database just mark them as deleted Default true Allowed true false enable Enable or disable persistent storage Default false Allowed true false flush_period Time in seconds between flushing cache to DB Default 300 Note This value is only read on startup interfaceName Syntax interfaceName ifname Description The name of the SLEE interface providing xmsStore services Type String Optionality Optiona
130. he Messaging Manager SMS Multigate module provides e Standard SMS MO service support e Standard SMS MT service support e SMS NO switching from MS to ASP with First Delivery Attempt e SMS MO switching from MS to MS with First Delivery Attempt e SMS MT switching from ASP to MS with First Delivery Attempt Routing options Using the Messaging Manager Multigate module MM allows individual routing based on different criteria e Incoming protocol message center originating number or originating domain e Destination number or destination domain Triggering The Messaging Manager Multigate module allows triggering of service control logic based on the following criteria e Incoming protocol e Originating number or originating domain e Destination number or destination domain ASP connection state management MM maintains a state for each ASP The state defines how MM will handle the data and command flow between MM and the ASP Chapter 1 System Overview 7 Note When a TCP connection is dropped by the ASP the ASP can not immediately reconnect because the TCP IP stack is in a cleaning up state TIME_WAIT Messaging Manager Director Introduction Messaging Manager Director provides complete control over all aspects of the VMP services Its advanced service control facilities enable extended and customised SMS processing including real time billing interaction by supporting user defined message control plans Message con
131. he is controlled by the globalProfileMaxAge parameter in the acs conf file Please be aware that the default value for globalProfileMaxAge is 300 seconds which is considerably longer than the validity period for the control plans in the Orig Dest matching cache Trigger rules are defined in the GUI Refer to MM User s Guide Where the matched ACS triggering rule does not specify a control plan name the originating or terminating number is looked up in the CLI or Service Number tables within ACS to find the required control plan and the values in the serviceLibrary section of the eserv config are used serviceLibrary parameters Here are the serviceLibrary parameters DialledNumberAvailable Syntax DialledNumberAvailable true fals Description Retrieves the dialed number from the Original Originating Address Type Boolean Optionality Optional Allowed true false Default false Notes If true retrieve the dialed number from the Original Originating Address If false do not retrieve the dialed number Only used for IS 41 Example DialledNumberAvailable true 136 NCC Messaging Manager Technical Guide flushTime Syntax Description Type Optionality Allowed Default Notes Example maxAge Syntax Description Type Optionality Allowed Default Notes Example validityTime Syntax Description Type Optionality Allowed Default Notes Example flushTime seconds How oft
132. he term attempt includes any retries that are configured for the path The outcome of a delivery attempt is one of Statistic Description MSG_PATH_DELIVER_RETRY_SUCCESS Delivery initially fails but is successful on the first or subsequent retries MSG_PATH_DELIVER_TEMP_ERR Initial delivery and all retries return a temporary error MSG_PATH_DELIVER_PERM_ERR Initial delivery or one of the retries returns a permanent error so there are no further retries MSG_PATH_DELIVER_TIMEOUT Initial delivery or one of the retries times out so there are no further retries MSG_PATH_DELIVER_ATTEMPT For every delivery attempt on a path listed in a Deliver routing rule MM will increment this statistic with the outbound path s statistics category in the detail field MSG_PATH_DELIVER_bucket_COUNT For every successful delivery attempt on a path listed in a Deliver routing rule MM will increment this statistic where the bucket is determined by the response time from the MSC with the outbound path s statistics category in the detail field Where bucket can be Response Time RT3 gt 1 second lt 5 seconds gt 5 seconds lt 10 seconds gt 10 seconds MSG_PATH_DELIVER_bucket_TIME For every successful delivery attempt on a path listed in a Deliver routing rule MM will add the response time to this statistic with the outbound path s statistics category in the detail field where bucket is determi
133. ial DP Initial Detection Point IMSI International Mobile Subscriber Identifier A unique identifier allocated to each mobile subscriber in a GSM and UMTS network It consists of a MCC Mobile Country Code a MNC Mobile Network Code and a MSIN Mobile Station Identification Number The IMSI is returned by the HLR query SRI SM when doing FDA This tells the MSC exactly who the subscriber is that the message is to be sent to IN Intelligent Network INAP Intelligent Network Application Part a protocol offering real time communication between IN elements Initial DP Initial Detection Point INAP Operation This is the operation that is sent when the switch reaches a trigger detection point IO Input Ouput IP 1 Internet Protocol 2 Intelligent Peripheral This is a node in an Intelligent Network containing a Specialized Resource Function SRF 182 NCC Messaging Manager Technical Guide IP address Internet Protocol Address network address of a card on a computer IS 41 Interim Standard 41 is a signaling protocol used in cellular telecommunications systems It deals with the signalling between the MSC and other network elements for the purpose of handovers and roaming etc ISDN Integrated Services Digital Network set of protocols for connecting ISDN stations ISUP ISDN User Part part of the SS7 protocol layer and used in the setting up management and release of trunks that carry voice and
134. ices defined in the SLEE cfg file for details see SLEE cfg on page 23 Location The acs conf file is located in IN service packages ACSletc acs conf settings Set the following in acs conf UseContinueOperation 0 For more information about this parameter see ACS Technical Guide eserv config The eserv config file is a shared configuration file from which many NCC applications read their configuration For details see the eserv config Configuration on page 25 topic The eserv config file needs to contain a SECURE section on page 50 within the xmsTrigger section This includes the list of licenses adapters and gateways for this installation of Messaging Manager This section is provided by NCC SLEE cfg The SLEE cfg file is the configuration file for the SLEE see the SLEE Technical Guide for further details about this file On installation of xmsScp some Messaging Manager specific lines are added to the file Warning Always make a backup copy of SLEE cfg before making any modifications Chapter 2 Configuration 23 Editing the SLEE cfg The following lines must be present in SLEE cfg SERVICEKEY INTEGER 102 xmsAgent xmsAgent inbound SERVICEKEY INTEGER 103 xmsAgent xmsAgent outbound INTERFACE xmsAgent xmsAgent sh IN service packages XMS bin EVENT SERVICEKEY INTEGER 120 SMS Submit Added by xmsScp SERVICEKEY INTEGER 121 SMS Deliver Added by xmsScp
135. ied previously String Used in number normalization on page 64 and denormalization rules prepend 1111 remove num Determines the number of digits that are stripped from the beginning of the number Integer Used in number normalization on page 64 and denormalization rules remove 2 resultNoa noa Resulting NOA after the normalization Used in number normalization on page 64 and denormalization rules resultNoa 4 targetNoa noa The target NOA 999 EMI only If unspecified defaults to 999 Used in number normalization on page 64 rules targetNoa 999 66 NCC Messaging Manager Technical Guide NOA and Normal rules The NOA nature of address is a classification to determine in what realm Local National or International a given phone number resides for the purposes of routing and billing Details vary between different implementations of telephone systems but the following table is representative 477 9425 1 Subscriber Number within local telephone exchange 4477 9425 3 5 National Number within country telephone exchange 64 4 477 9425 4 International Number within world telephone exchange 477 9425 2 2 UNKNOWN Numbering Scheme rule Subscriber 0 4 477 9425 2 UNKNOWN Numbering Scheme rule National 00 64 4 477 9425 2 UNKNOWN Numbering Scheme rule International In essence the subscriber s telephone system may try to ascertain the nature by examining the dial
136. ig This name must also be in the configuration database before Messaging Manager will run correctly See MM User s Guide The parameters in this sub section below this give the configuration for all messages for this adapter lib Syntax Description Allowed Default Example pointCodes Syntax Description Optionality Allowed Example SSN Syntax Description Allowed Notes Example lib library The name of the library that contains the SMPP adapter being configured mmxiSMPP so No default lib mmxiSMPP so pointCodes pcl pc2 Destination point codes array of messages to be handled by this adapter This parameter takes priority over SSN match Optional Defined by network administrator pointCodes 1001 1002 SSN num Destination subsystem number of messages to be handled by this adapter Valid subsystem number Non zero to handle incoming TCAP SSN 18 Global SMPP configuration The following section of the eserv config specifies the global parameters for all SMPP connections config suppressPathInfoReport true displayZeroPathReport false PathReportingInterval 60 fallbackAlphabet UCS 2 smppDefaults throttledCommandStatus 88 ESME RTHROTTLED 88 teleserviceRoutingMap serviceType teleservice 0 allowAlternateDelivery true serviceType CMT teleservice 4098 allowAlternateDelivery true
137. igits long before writing the value to pstore This helps maintain consistency in the message ID format stored in pstore and may help with improving pstore matching for message IDs shorter than 10 digits This option must be used in conjunction with convertMessageIdToHex on page 41 Only message IDs shorter than 10 digits are affected Message IDs longer than 10 digits are not padded regardless of the setting of this field fixedLengthMessageld tru includePayloadDRInfo Syntax includePayloadDRInfo true false Description If set forces MM to build a delivery receipt message payload containing the extra information in Appendix B of the SMPP 3 4 specification Whether set or not the standard TLVs message_state and receipted_message_id will be used Allowed true false Default false Notes This option only applies to MM generated delivery receipts If a delivery receipt is received from an SMSC MM will send the SME one in the same format Example includePayloadDRInfo false maxValidityPeriod Syntax maxValidityPeriod seconds Description If set and non zero defines the maximum possible validity period for outbound messages from the adapter Type Integer Optionality Optional Allowed Default 0 Notes Validity periods that would have been greater are shortened to this value when it is set Chapter 3 Configuring Messaging Manager Multigate 99 Example maxValidityPeriod 0 messageClass
138. in the user data header that profileTag is copied to Type Integer Optionality Required Example informationElementIdentifier 5 MMX Notification Standard Application Port Example The following example configuration maps the profile tag 3932482 to information element ID 5 in the user data header in an SMPP notification ServiceConfig ParameterMappings UserDataHeader profileTag 3932482 informationElementIdentifier 5 The profile tag 3932482 MMX Notification Standard Application Port is defined as a SHORT two bytes and matches the standard two byte destination port encoding used by the information element ID 5 application port in SMPP notifications A Set feature node is used to set the MMX Notification Standard Application Port profile tag value to 5498 and an SMS Send SMS Notification feature node placed after the Set feature node in the control plan is used to send the SMPP notification When the message is sent the value for the application port in the user data header will be 5498 MMX Notification Standard Application Port Example The following example configuration maps the profile tag 29020 to information element ID 5 in the user data header in an SMPP notification ServiceConfig ParameterMappings UserDataHeader profileTag 29020 informationElementIdentifier 5 In this example the custom profile tag 29020 is configured to hold an unsigned integer four
139. ing ssssssssssssseseeneneee enne enne en nennen sinn nn nennen nes 140 Application to Mobile Messaging sesssseseeenenen nennen enne n nennen nnns 142 Mobile to Application Messaging esee enne nennen nnne 144 Mobile to Mobile triggering to ACS sssssssssssssseeseneeenneen ener 147 Chapter 6 zti e peigliges l 151 emu p 151 xmsTrigger Application nennen nnne nennen inen nennen nn nnnees 151 MERI 152 herecume EE 152 Statistics rM c EEE 153 Jc EE 161 Messaging Manager EDRS ssssssseseseeeeenee nennen nnn ener nennen entren nns 163 Delivery Recelpts 1 x rece ee Heec cad ds ieee UHR EXER ELE Cue Enn XE EE e ER ERE ER E EXE th s 164 Chapter 7 Tools I qDnEDUlceee e 167 OVGIVIOW C H 167 PME GConfigutatiOri accu reet b eee ke need an nece syns Reda neu Venta Pa ete Exe t E ERR ETE E eua 167 Adding and Removing Replication Nodes sesseeeeeeeeenennenen eene 168 Chapter 8 About Installation and Removal sees 169 emu t 169 Chapter sme Em 169 Installation and Removal Overview sse enne nennen nnne enne 170 Checking the Installation essssessssseses
140. ing schemes and message control plans that are used to configure and control all service logic components For a full description of this component refer to MM User s Guide Virtual Message Point components This diagram shows the service execution components of Messaging Manager that implement the VMP along with other platform support components ACS Advanced Control Services Messaging Manager Director Control Multigate Manager Agent Navigator Session Messaging Manager Messaging ChargingMax EE EE iw a a dl I ILEJ SIGTRAN SMPP UCP s SIGTRAN CORBA Convergent ae ITP to MSC toASP S ITP to HLR MMS MMS osA Parlay Billing or SMSC SMSC f or SMSC CAMEL IniialDP Protocols supported This table describes the function of each field Protocol More Information SMPP Configuring the SMPP Adapter on page 92 Configuring the EMI Adapter on page 86 Configuring the MAP Adapter on page 67 4 NCC Messaging Manager Technical Guide Protocol More Information IS 41 Configuring the IS 41 CDMA Adapter on page 103 Configuring the IS 41 TDMA Adapter on page 113 Configuring the SCA Adapter on page 115 mbuni Tech Guide mbuni Tech Guide Messaging Manager Platform Introduction The Messaging Manager platform is required to provide basic transaction and switching functionality for the MM message service It is a prerequisite to any additional MM component
141. ional Notes For inbound messages MM will select the data coding number for example 0x08 value and match the parameters for that data coding For outbound messages MM will match the parameters then uses it to calculate the data coding If there is more than one set of parameters with all values the same MM will select the last data coding Example dataCodingMap messag messag messageWaitingIndicator messag data coding alphabet messag messag messag messag I data_coding 0x08 alphabet UCS 2 eClass dy eWaitingGroup 0 0 eWaitingType 0 OxFO GSM8Bit eClass 1 eWaitingGroup 0 eWaitingIndicator eWaitingType 0 0 In this example for outbound messages if the alphabet for both data codings for 8 and FO were the same then MM would select FO 98 NCC Messaging Manager Technical Guide data_coding Syntax Description Allowed Example data_coding coding The MAP DCS data coding Hex value of number up to 255 data coding OxFO fixedLengthMessageId Syntax Description Type Optionality Allowed Default Notes Example fixedLengthMessageld true fals An SMPP option to allow xmsTrigger to perform padding of message IDs so they are always 10 digits long Boolean Optional default used if not set true false true When set to true MM performs automatic padding of the hex message IDs so it is always 10 hex d
142. ions from a control plan For example to set the value of the protocol id field in a MAP or SMPP notification message set the MMX Protocol Identifier temporary storage tag by using a feature node such as the Set feature node or the Copy feature node in your control plan You send the notification by placing a notifications feature node in the control plan after the Set or Copy feature node See Notifications Feature Nodes Table on page 133 for a list of notifications feature nodes that you can use You can also define configuration in the xMS section of the eserv config file to copy temporary storage tags byte for byte into information elements in the user data header for MAP or SMPP messages Note This feature applies to notifications sent by feature nodes that use a notifications processor such as the XMS Send SMS Notification feature node or the ACS Send Notification feature node It does not apply to network originated messages modified by ACS control plans For more information about NCC feature nodes see NCC Feature Nodes Heference Guide Notifications Feature Nodes Table This table lists the feature nodes that can be used to send SMPP messages and the palette group and NCC application for each feature node For more information about NCC feature nodes see NCC Feature Nodes Reference Guide Chapter 4 Configuring Messaging Manager Director 133 Note You can use the Short Message Charging SMCB feature node to charge for mess
143. isation 1 pathRetrySegmentOffset Syntax Description Allowed Notes Example PE Syntax Description Allowed Notes Example protocol Syntax Description Allowed Notes Example pathRetrySegmentOffset seconds How much to delay later segments of a concatenated message when a delayed retry is attempted integer pathRetrySegmentOffset 1 PC code Originating point code in outgoing messages integer in range 0 255 PC 1005 protocol prot The outbound protocol that this adapter uses CDMA for IS 41 CDMA TDMA for IS 41 TDMA protocol CDMA relaySmsNotifications Syntax Description Optionality Allowed Default Example relaySmsNotifications true false We can relay SMS NOT alerts from the HLR to the SMSC but that is usually a bad idea because the SMSC will have registered for its own alerts It does not need ours as well Mandatory true false false relaySmsNotifications false 110 NCC Messaging Manager Technical Guide releaseCauseMap Description Map of releaseCauses to SMS_CauseCodes plus default mappings for transient and permanent failures if no releaseCauseMap entry matches Notes If ACS did not release the call and the outbound adapter generated an error result code the following releaseCodes will be used e TransientFailure 1001 e PermanentFailure 1002 e Abort 1003 Refer to SMS CauseCodes on page 111 for a list of caus
144. it may connect to General EMI configuration The following section of the eserv config specifies the general parameters for all EMI connections adapters second adapter EMI lib mmxiEMI so SSN 8 adapterName EMII earlyAckMC true earlyAckSME true allowConcatenatedFDA tru config global_parameters General EMI parameters Here are the general parameters for EMI adapterName Syntax adapterName name Description Identifier for the adapter 86 NCC Messaging Manager Technical Guide Allowed Default Notes config Any text string but should be meaningful for example include the protocol used For example e MAP1 for MAP e EMI1 for EMI e SCA1 for SCA e SMPP1 for SMPP e CDMA1 for IS 41 CDMA e TDMA1 for IS 41 TDMA e Wrapper for Wrapper No default This name must also be in the configuration database before Messaging Manager will run correctly See MM User s Guide The parameters in this sub section below this give the configuration for all messages for this adapter lib Syntax Description Allowed Default Example SSN Syntax Description Allowed Notes Example lib library The name of the library that contains the EMI adapter being configured mmxiEMI so No default lib mmxiEMI so SSN num Destination subsystem number of messages to be handled by this adapter Valid subsystem number Non ze
145. it on the socket for work Type Integer 38 NCC Messaging Manager Technical Guide Optionality Optional default used if not set Allowed Default 10 Notes Example tcpWaitTimeMilliSec 10 xmsTrigger xmsTrigger configuration Here is a high level view of the xmsTrigger section of the eserv config xmsTrigger SECURE secure section parameters SECUREKey 123456 xmsAgentInboundServiceKey xmsAgentOutboundServiceKey pollTime 100000 loadReportingPeriod 10 routingScheme loadIntervalSeconds 60 mtTransactionLifetimeSeconds 102 103 0 30 oracieusername ll os Q O oraclepassword scp oracledatabase dialledStarEncoding dialledHashEncoding I E Jg mmxlIsdn 0640041234567 mmxlIsdnGprs 0640041234568 deliveryReceiptId scpl desegmentation false desegmentation timeout 0 desegmentation failure code desegmentation failure cause baseIDPSize 200 allowConcatenatedFDA tru earlyAckMC true earlyAckSME true 1 27 alwaysProduceNonDeliveryRec ipt fals Chapter 2 Configuration 39 stopRoutingOnTransientFailure false stopRoutingOnPermanentFailure false processMsgSCI true successDeliveryReceiptText Your message to lt destination gt was delivered failureDeliveryReceiptText Your message to lt destination gt was NOT delivered
146. jGAmtvdid S lUrgentmessagenotalowed o Urgent message not allowed Legitimization code for urgent message failure Reverse charging not allowed New AC not valid E New legitimization code not valid a Standard text not valid Time period not valid 88 NCC Messaging Manager Technical Guide Message type not valid for the pager type Message not found in SMSC Subscriber hang up Fax group not supported Fax message type not supported go Address already in list 60 series 34 o O Address not in list 60 series 35 List full cannot add address to list 60 series Be o RPID already in use Delivery in progress Message forwarded emiDefaults The emiDefaults sub section contains the default EMI configurations permanentFailureErrorCode Syntax permanentFailureErrorCode code Description The error code to return for permanent failures Type Integer Optionality Optional default used if not set Allowed Refer to EMI error codes on page 88 for list of values Default 3 Notes Example permanentFailureErrorCode 3 suppressPathInfoReport Syntax suppressPathInfoReport true fals Description Do we want path connection reports to be suppressed Type Boolean Optionality Allowed true false Default true Notes An ASP receives heartbeats from the SMSC when Messaging Manager is configured to operate as an SMSC then it will respond to these heartbeats The
147. l default used if not set Allowed Default xmsStorelf Notes Example interfaceName xmsStoreIf max age seconds Minimum time that the item may reside in the cache in seconds before it can be flushed to the database Default 300 max writes per flush Maximum number of records to write per Oracle transaction when flushing This stops the process blocking on Oracle writes which can cause xmsTrigger to be killed by the watchdog Default 1 Note 1 means no limit over size max age seconds Flush items older than this number of seconds when cache is overfull Default 60 userpass Username and password login to use to attach to the Oracle database if the host application is not already logged in Default 2 Note This value is only read on startup Chapter 2 Configuration 61 Collecting Statistics Editing the statistics configuration When configured MM will gather extensive operational statistics Using the NCC SMS application these statistics are stored in the database for subsequent reporting For a full list of the MM statistics that will be gathered please refer to the Statistics on page 153 topic in the Background Processes chapter Statistics parameters To collect statistics there is a single parameter that must be set to true in the xmsTrigger section of the eserv config file enable Determines whether Messaging Manager collects operational statistics Default false Allowed true
148. ld be meaningful for example include the protocol used For example e MAP1 for MAP e EMI1 for EMI e SCA1 for SCA e SMPP1 for SMPP e CDMA1 for IS 41 CDMA e TDMA1 for IS 41 TDMA e Wrapper for Wrapper Default No default Notes This name must also be in the configuration database before Messaging Manager will run correctly See MM User s Guide disabled Syntax disabled true fals Description To enable or disable the adapter Allowed true false Default false Example disabled False interfaceName Syntax interfaceName name Description The SLEE interface name for Messaging Manager to send messages from SCA to Messaging Manager Allowed String Default xmslf Note This must match the name specified in the SLEE cfg file Example interfaceName xmsIf lib Syntax lib library Description The name of the library that contains the SCA adapter being configured Allowed mmxiSCA so Default No default Example lib mmxiSCA so 116 NCC Messaging Manager Technical Guide Global SCA configuration The following section of the eserv config specifies the global parameters for all SCA connections config sca serviceKey 52 interface sca pathReportingInterval 60 inboundTimeout 5 outboundTimeout 5 Global SCA parameters Here are the parameters for configuring the global SCA adapter inboundTimeout Syntax inboundTimeout seconds Description The timeout in
149. le country code MCC or at the start of a national format address This specifies the mobile network code that is the operator owning the address In the location information context this is padded to two digits with a leading zero Refer to ITU E 212 Land Mobile Numbering Plan documentation for a list of codes MO Mobile Originated MOC Managed Object Class MS Mobile Station MSC Mobile Switching Centre Also known as a switch MSID Mobile Subscriber Identification also Known as an MIN MSIN Mobile Station Identification Number MSISDN Mobile Station ISDN number Uniquely defines the mobile station as an ISDN terminal It consists of three parts the country code CC the national destination code NDC and the subscriber number SN MT Mobile Terminated 184 NCC Messaging Manager Technical Guide MTC Mobile Terminated Call The part of the call associated with a subscriber receiving an inbound call MTP Message Transfer Part part of the SS7 protocol stack NOA Nature Of Address a classification to determine in what realm Local National or International a given phone number resides for the purposes of routing and billing NPI Number Plan Indicator Oracle Oracle Corporation PC Point Code The Point Code is the address of a switching point Peer Remote machine which for our purposes is capable of acting as a Diameter agent PLMN Public Land Mobile Network RIMS
150. ls which enables circuit and non circuit related information to be routed about and between networks The main protocols include MTP SCCP and ISUP SSN Subsystem Number An integer identifying applications on the SCCP layer For values refer to 3GPP TS 23 003 SSP Service Switching Point TCAP Transaction Capabilities Application Part layer in protocol stack message protocol TCP Transmission Control Protocol This is a reliable octet streaming protocol used by the majority of applications on the Internet It provides a connection oriented full duplex point to point service between hosts TDMA Time Division Multiple Access a communications technique that uses a common channel for communications among multiple users by allocating each a unique time slot TDP Trigger Detection Point TLV Tag Length Value Optional parameters introduced in the SMPP protocol since version 3 4 URI Uniform Resource Identifier USSD Unstructured Supplementary Service Data a feature in the GSM MAP protocol that can be used to provide subscriber functions such as Balance Query and Friends and Family Access VLR Visitor Location Register contains all subscriber data required for call handling and mobility management for mobile subscribers currently located in the area controlled by the VLR VMP Virtual Message Point VMSC Visited Mobile Switching Centre VWS Oracle Voucher and Wallet Server formerly UBE
151. m responses but decimal message ids in the payload parts of their delivery receipts Chapter 2 Configuration 41 Type Optionality Allowed Default Notes Example dialledHashl Syntax Description Type Optionality Allowed Default Notes Warning Example dialledStar Syntax Description Type Optionality Allowed Default Notes Warning Example Boolean Optional default used if not set true false no automatic adjustment of message IDs between decimal and hex false Without this option the behavior interferes with the MM pstore mapping of message IDs If this is set to true then the deliveryReceiptId on page 42 parameter must be hex value only not ASCII convertMessageldToHex tru Encoding dialledHashEncoding encode The value to use when a hash is pressed String Optional The default behaviour is to perform no special translation Because different protocols map asterisks and hashes to different BCD numbers for example MAP uses C IS41 uses E we cannot always rely on TC_PROTOS to get it right Make sure these values match with the ones in acs conf dialledHashEncoding E Encoding dialledStarEncoding encode The value to use when an asterisk is pressed String Optional The default behaviour is to perform no special translation Because different protocols map asterisks to different BCD numbers for example MAP us
152. m tasks that should only be carried out by suitably trained operators Related documents The following documents are related to this document e NCC Advanced Control Services Technical Guide e NCC Event Detail Record Reference Guide e Messaging Manager Navigator Technical Guide e Messaging Manager User s Guide e SCA Technical Guide e SLEE Technical Guide e NCC Service Management System Technical Guide Document Conventions Typographical Conventions The following terms and typographical conventions are used in the Oracle Communications Network Charging and Control NCC documentation Names of database tables and fields Emphasis within text ZEN 77 7 NK Example To close the window either click Close or press Esc Key combinations for which the user must press and hold down one key and then press another Example Ctrl P or Alt F4 Examples of code or standard output Text that you must enter Used to indicate variables or text that should be replaced menu option gt menu option Used to indicate the cascading menu option to be selected or the location path of a file Example Operator Functions Report Functions Example IN html SMS Helptext hypertext link Used to indicate a hypertext link on an HTML page Specialized terms and acronyms are defined in the Glossary at the end of this guide vi NCC Messaging Manager Technical Guide Chapter 1 System Overview Overview Introduction
153. me 6 Configure adapters 7 Configure paths 8 Configure connections 9 Configure domain 10 Configure throttling 11 Configure triggering 12 Configure routing Chapter 5 Configuring Messaging Manager Services 149 Chapter 6 Background Processes Overview Introduction This chapter explains the processes which run automatically as part of the application These processes are started automatically by one of the following e inittab e crontab e Service Logic Execution Environment SLEE Note This chapter also includes some plug ins to background processes which do not run independently In this chapter This chapter contains the following topics xmsTrigger Application 151 xmsAgent 152 Adapters 152 Statistics 153 Tracing 161 Messaging Manager EDRs 163 Delivery Receipts 164 xmsTrigger Application Purpose xmsTrigger also known as the XMS Trigger application is a SLEE interface which is responsible for e Correlating and controlling all of the incoming short messages e Converting through adapters and relaying messages between different SLEE interfaces e Triggering INAP service logic on slee acs as required during message processing The primary tasks of xmsTrigger are e Receive incoming Send requests from an MM interface e Trigger INAP to the ACS service slee acs e Possibly pass outgoing send requests to an MM interface for relay e Receive delivery notifications from an MM interface e Trigger I
154. me charging The ability to provide SPOC Single Point of Contact to ASPs to attract more ASPs on your networks and to differentiate your offering on value added interactive applications Chapter 1 System Overview 3 Messaging Manager components The major Messaging Manager components are e Messaging Manager Multigate A multi protocol gateway and multi function router that can receive and send short messages Its layered architecture allows all signaling and IP protocols to connect to a common set of service logic maintaining independence between transport protocols and the user defined routing scheme that defines the messaging model For a full description of this component refer to Messaging Manager Multigate on page 6 e Messaging Manager Navigator A Mobile Station location service that can perform and or emulate HLR lookups by other components or network elements caching the results to optimize network signaling and direct SMS transmission toward service logic For a full description of this component refer to Messaging Manager Navigator Technical Guide e Messaging Manager Director A set of service control feature nodes that execute as a message control plan and provide enhanced logic for message delivery routing and charging and offers extended message attribute controls For a full description of this component refer to Messaging Manager Director on page 8 e Messaging Manager Manager A central UI for management of rout
155. mines whether the adapter may deliver directly to MSCs Default false Allowed true false Note Required parameter allowIncomingMap3 Whether to allow MAP v3 inbound processing Default true Allowed true false allowUserRequestedDeliveryReceipt If false turn off delivery receipts requested by the input transaction Default true Allowed true false Note Required parameter defaultMapVersionMsc MAP version to use for communication with the MSC Default 3 Note If defaultMapVersionMsc is missing it tries to find defaultMapVersion for backwards compatibility If that is also missing uses default value defaultMapVersionSmsc MAP version to use for communication with the SMSC Default 3 Note If defaultMapVersionSmsc is missing it tries to find defaultMapVersion for backwards compatibility If that is also missing uses default value 72 NCC Messaging Manager Technical Guide defaultMessagePriority Syntax defaultMessagePriority str Description The priority to be applied to incoming messages that do not have a priority Type String Optionality Optional default used if parameter absent Allowed Default Normal Notes Example defaultMessagePriority Normal defaultPermanentFailureErrorCode The default MAP error code used for permanent failures when no mapping from CS1 release cause is specified Default 32 Allowed See deliveryFailureStatusCode on page 73 for list of values
156. mmodate your changing network needs Number normalization People deal with and a database usually stores telephone numbers in their normalized form for example 00441918666223 The network however gives and receives numbers in a denormalized form that is where the type of number the Nature of Address is known explicitly for example International 441918666223 for the previous example The number rules parameters in the adapters conform to the number normalization configuration described below Example Normalized number 049393434 De Normalized number Nature of Address This table shows the different Normalization NoA values depending on the adapter type Subscriber number Unknown Possible Natures of Addresses National International Network specific Normalization parameters Enter a conversion rule for each incoming NOA This rule determines how to convert to the normalized number and a corresponding rule converts back to a denormalized number on the outgoing side Number normalization rules are in the following format fromNoa noa targetNoa noa prefix digits min len max len remove num prepend digits resultNoa noa Here are the configuration parameters for number normalization 64 NCC Messaging Manager Technical Guide fromNoa Syntax Description Type Optionality Allowed Default Notes Example max Syntax Description Type Optionality Allowed D
157. msTrigger pe 51 ssn 3 type itu gt Ww Global Wrapper adapter parameters Here are the parameters for configuring the global Wrapper adapter gt Syntax GT gt Description Global title Note This is defined by the network administrator Required only if the point code is not defined pc Syntax PC code Description Point code Chapter 3 Configuring Messaging Manager Multigate 119 Allowed Example ssn Syntax Description Allowed Note Default Example tcapTimeout Syntax Description Allowed Default Note Example type Syntax Description Allowed Example xmsTimeout Syntax Description Allowed Default Example xmsTrigger Syntax Description Note xmsWrapper Syntax Description Integer in range 0 255 PC 55 SSN Subsystem number Integer between 0 and 65535 Required only if the point code has been defined 0 SSN 0 num tcapTimeout seconds How long to wait for response from XMS remote wrapper 10 This entry is only used in conjunction with the xmsWrapperTA SLEE interface tcapTimeout 10 type type Protocol type ansi itu type itu xmsTimeout seconds How long to wait for a response from XMS trigger application Suggested value Look in the MAP adapter section and add up mscTimeout on page 77 and hlrTimeout see Messaging Manager Navigator Technical Guide and add a bit of time t
158. nating domain e The terminating number of the message or terminating domain This may result in the message being triggered to ACS twice Chapter 1 System Overview 11 Terminating triggering rules By default Messaging Manager will perform routing of deliver requests according to the following rules 1 If no routing prefix was added by the service logic the originating adapter ID will be used to determine the outgoing route 2 Ifa routing prefix was added by the service logic this will be used to find the outgoing route If both the originating and terminating service plans add prefixes the terminating value will be used 38 fnoroute is matched then the deliver will fail Interfaces and nodes Routing nodes can provide connections for one of the following e All IP connections of a routing scheme e Connections only for certain ASPs This means a connection does not need to support all the capabilities of its associated routing scheme in order to be a valid connection Routing schemes can be configured with interface records An interface record is a virtual IP connection that may be supplied or instantiated by real IP addresses on one or more routing nodes Each node can assign a different IP address to an interface record Routing nodes are configured with a list of real IP addresses When a routing scheme is assigned to a routing node you can map any of the routing scheme interfaces to the node s IP addresses This define
159. nboundServiceKey val Service key for the xmsAgent used for inbound SMPP traffic Integer Optional default used if not set The value must match the service key defined in the SLEE cfg on page 23 file 102 by install question Listen Socket inbound xmsAgentInboundServiceKey 102 Chapter 2 Configuration 49 xmsAgentOutboundServiceKey Syntax xmsAgentOutboundServiceKey val Description Service key for the xmsAgent used for outbound SMPP traffic Type Integer Optionality Optional default used if not set Allowed The value must match the service key defined in the SLEE cfg on page 23 file Default 103 by install question Notes Connect Socket outbound Example xmsAgentOutboundServiceKey 103 SECURE section Here is an example of the SECURE section configuration SECURE limits maxConcurrentTransactions 0 warnConcurrentTransactionsPercentage 70 warnConcurrentTransactionsPeriod 5 clearConcurrentTransactionsPeriod 5 maxSmsPerSecond 200 warnSmsPerSecond 180 MCC P SAS EDR 7 MCP MO SMS MT SMS VAS SMS MAP CDMA 2 TDMA EMI X SMPP h APT Wap Wao Array listing the adapters supported for this installation of MM MAP CDMA TDMA EMI SMPP API MAP A CDMA TDMA EMI F SMPp A API gl g2 Array listing the adapters supported for this installation of MM options gateways
160. nctions and switching functions are remote Unlike the fixed IN environment in mobile networks the subscriber may roam into another PLMN Public Land Mobile Network consequently the controlling function must interact with a switching function in a foreign network CAMEL specifies the agreed information flows that may be passed between these networks CC Country Code Prefix identifying the country for a numeric international address CCS 1 Charging Control Services or Prepaid Charging component 2 Common Channel Signalling A signalling system used in telephone networks that separates signalling information from user data CDMA Code Division Multiple Access is a method for describing physical radio channels Data intended for a specific channel is modulated with that channel s code These are typically pseudo random in nature and possess favourable correlation properties to ensure physical channels are not confused with one another CDR Call Data Record Note The industry standard for CDR is EDR Event Detail Record Over time EDR will replace CDR in the Oracle documentation CLI Calling Line Identification the telephone number of the caller Also referred to as ANI Connection Transport level link between two peers providing for multiple sessions CPE Control Plan Editor previously Call Plan Editor software used to define the logic and data associated with a call for example if the subscriber calls
161. nd is also used for normalization and denormalization configuration SLEE cfg All SLCs Configures which MM processes SLEE cfg on page 23 are started by the SLEE and provides some configuration for the environment in which those processes run tdp conf All SLCs The tdp conf file is the tpd conf on page 24 configuration file that is used by the system to define the trigger tables used to determine when to trigger a call to the SCF 22 NCC Messaging Manager Technical Guide SMS User Provide a graphical interface for SMS User s Guide Interface configuring many parts of SMS including e Replication e Statistics e Alarm filtering e Reports Note Most of these files are at least partially configured when the xmsScp package is installed acs conf The acs conf file is the configuration for the ACS application For more information on the acs conf file see ACS Technical Guide The xmsScp package will have added the following lines to the acsChassis section of the acs conf file No manual modification is required ServiceEntry SMS Submit xmsSvcLibrary so ServiceEntry SMS Deliver xmsSvcLibrary so ChassisPlugin libxmsChassisActions so MacroNodePluginFile libxmsMacroNodes so The following lines will be present if the PME service is installed ServiceEntry CCS SM MO dD cC dD E ccsSvcLibrary so ServiceEntry CCS SM MT cC dD ccsSvcLibrary so Note The service names for example SMS Submit match the serv
162. ned as above Note The number of attempts that produce a successful delivery with no retries required can be derived by subtracting the other outcomes from MSG PATH DELIVER ATTEMPT Chapter 6 Background Processes 157 Submit If the routing class is Submit or FDA where the Deliver leg has already failed MM will look for routing rules that specify a routing class of Submit Each path listed in the routing rule will be attempted in turn until either a successful or permanent failure response is received Statiste Description S O MSG_PATH_SUBMIT_ATTEMPT For every delivery attempt on a path listed in a Submit routing rule MSG_PATH_SUBMIT_TIMEOUT For every delivery attempt that times out on a path listed in a Submit routing rule MSG_PATH_SUBMIT_TEMP_ERR For every delivery attempt resulting in a transient failure on a path listed in a Submit routing rule MSG_PATH_SUBMIT_PERM_ERR For every delivery attempt resulting in a permanent failure on a path listed in a Submit routing rule Note All of these statistics will include the outbound path s statistics category in the detail field Locate If the routing class is Locate MM will look for routing rules that specify a routing class of Locate Each path listed in the routing rule will be attempted in turn until either a successful or permanent failure response is received sa pem MSG PATH LOCATE ATTEMPT For every delivery attemp
163. ng dialledHashEncoding I E Jg mmxIsdn 0640041234567 mmxlIsdnGprs 0640041234568 deliveryReceiptId scpl desegmentation false desegmentation timeout 0 desegmentation failure code 1 desegmentation failure cause 27 Chapter 2 Configuration 27 baseIDPSize 200 allowConcatenatedFDA tru earlyAckMC true earlyAckSME true alwaysProduceNonDeliveryReceipt fals stopRoutingOnTransientFailure false stopRoutingOnPermanentFailure false processMsgSCI true successDeliveryReceiptText Your message to lt destination gt was delivered failureDeliveryReceiptText Your message to lt destination gt was NOT delivered cdr log true filename xms _ tempdir IN service packages XMS cdr current maxno 10000 time out 1800 destdir IN service packages XMS cdr closed num files 64000 num files leaf 64 tracing nabled tru showPrivate true outputFile tmp xmsTrigger trc outputFileCycle 512 maxFileSizeKB 0 maxNumFiles 4 shmKey 92403 shmSizeKb 64 callsPerMinute 2 origAddress 0064212 0064213 0064214 destAddress 0064213 0064214 useTONNPI true pstore enable true cache size 10000 1 mean no max size flush period 10 interfaceName xmsStoreIf 28 NCC Messaging Manager Technical Guide over size max age seconds 60 ma
164. nicates between the Messaging Manager platform and SMSCs HLRs and MSCs using IS 41 The IS41 adapter needs to be configured to know about SMSCs that it will connect to General IS 41 CDMA configuration The following section of the eserv config specifies the general parameters for all IS 41 CDMA connections adapters IS 41 CDMA adapter lib xmsiIS41 so adapterName CDMAI1 pointCodes 1005 1006 Chapter 3 Configuring Messaging Manager Multigate 103 SSN 18 earlyAckMC false earlyAckSME false allowConcatenatedFDA tru config global parameters General IS 41 CDMA parameters Here are the general parameters for IS 41 CDMA adapterName Syntax Description Allowed Default Notes lib Syntax Description Allowed Default Example pointCodes Syntax Description Optionality Allowed Example adapterName name Identifier for the adapter Any text string but should be meaningful for example include the protocol used For example e MAP1 for MAP e EMI1 for EMI e SCA1 for SCA e SMPP1 for SMPP e CDMA1 for IS 41 CDMA e TDMA for IS 41 TDMA e Wrapper for Wrapper No default This name must also be in the configuration database before Messaging Manager will run correctly See MM User s Guide lib library The name of the library that contains the CDMA UCA IS41 adapter being configured xmsilS41 so No def
165. ns Feature Nodes Table 136 NPI 187 num files 58 num files leaf 58 Number normalization 66 67 68 93 numberPlan 80 131 O options 51 Oracle 187 oracledatabase 46 oraclepassword 47 oracleusername 47 origAddress 55 originating Timeout 80 112 Other statistics 160 Outbound routing 9 11 outboundTimeout 120 outputFile 56 outputFileCycle 56 over size max age seconds 62 Overview 1 21 65 125 141 153 169 171 175 P PathReportingInterval 120 pathRetryRandomisation 80 112 pathRetrySegmentOffset 80 112 pc 123 PC 81 113 131 187 Peer 187 permanentFailureErrorCode 92 PI packages 172 PLMN 187 PME Configuration 169 173 PME configuration script 169 pointCodes 71 96 107 pollTime 47 Post installation Configuration 174 prefix 67 Pre installation 171 prepend 68 Prerequisites v privateExtensions 81 Processing model 1 processMsgSCl 47 profileTag 137 profileTagID 82 98 protocol 113 protocolldMap 83 Protocols supported 4 pstore 48 Pstore configuration 60 Pstore configuration example 61 Pstore parameters 61 pstoreNumberRules 93 Purpose 153 154 192 NCC Messaging Manager Technical Guide R rateLimitAlarmIntervalSec 38 Raw devices 171 Receiving a MAP sm DeliveryFailure error message 85 recordResponseTimes 127 Related documents v relaySmsNotifications
166. o or information on content products and services from third parties Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content products and services Oracle Corporation and its affiliates will not be responsible for any loss costs or damages incurred due to your access to or use of third party content products or services ii NCC Messaging Manager Technical Guide Contents About This DOCUMEN siinse RA EE ie se s Ete REC Te enu etr mee d Ea REL ua kite V Document CONVENTIONS desc icto edet et oa kde ea SER ra SE ERR en tna evans Ro ecd ca e CRINE REL a edd vi Chapter 1 System CVT e 1 eI 1 What is Messaging Manager ssssssssssssssees eene senten terrens nnn sse enne 1 Messaging Manager Platform sss enne ener en nenrnn ener nnns 5 Messaging Manager Multigate ssseesee eene een enne nennen nnne 6 Messaging Manager Director sessssssseseeeeeenen eene nnne nnnm errem nennen nnns 8 Message Processing ierra centenarians artes 9 Mobile to Mobile Messaging sesseeeeenee nennen nennen ennemi nennen nnns 13 Application to Mobile Messaging enne nnne nnne 14 Mobile to Application Messaging sssseseeeneeeene enm eene nennen nnne 16 Mobile to Mobile triggering to ACS
167. o that up to 5 seconds 5 xmsTimeout 5 xmsTrigger trigger parameters Configuration parameters used to determine the source address for outgoing messages No dialogs needed Address section is not used for working with SSMN node xmsWrapper wrapper parameters Configuration parameters used to create dialogs to the TCAP stack and to determine the destination address 120 NCC Messaging Manager Technical Guide Note Remote side s configuration Ignored in normal operation that is no xmsWrapperTA Chapter 3 Configuring Messaging Manager Multigate 121 Chapter 4 Configuring Messaging Manager Director Overview Introduction This chapter briefly explains how to configure the Messaging Manager Director modules This includes details of the configuration of specific nodes that are used for the MM application There are many feature nodes that are supplied by the ACS application and may be used in Messaging Manager control plans These feature nodes are detailed in NCC Feature Nodes Reference Guide please refer to this document for instructions In this chapter This chapter contains the following topics Configuring Chassis Actions 123 Configuring Macro Nodes 126 Creating Control Plans 133 Configuring Messaging Manager to Send SMPP Parameters in Notifications 133 Configuring Messaging Manager to load ACS Control Plans 136 Configuring Chassis Actions Introduction The ChassisActions section
168. of Messaging Manager contains the configuration to enable e The Send Short Message Notification SSMN node to send a GenericSM and wait for a result so that it can branch on the result type e AUSSD node to send a message ChassisActions configuration Here is an example ChassisActions configuration ChassisActions SendGenericMessageAction interfaceName xmsIf timeoutTick 5 tcapOrigAddr PC 0 SSN 0 type itu tcapDestAddr PC 0 SSN 0 type itu ussdChassisAction tcapInterfaceName hssScIf timeoutTick 5 Chapter 4 Configuring Messaging Manager Director 123 recordResponseTimes fals SendGenericMessageAction parameters Here are the parameters in the SendGenericMessageAction sub section of the ChassisActions section of the eserv config InterfaceName Syntax interfaceName name Description The SLEE interface to send GenericSMs to Type String Optionality Mandatory Default xmslf Example interfaceName xmsIf tcapDestAddr Description TCAP destination address to use when ACS and MM are on different machines Default Not set Note Required only if MM and ACS are on separate machines See PC SSN and t ype parameters Example tcapDestAddr PC 1 SSN 40 type itu tcapOrigAddr Description TCAP originating address to use when ACS and MM are on different machines Default Not set Note Required only if MM and ACS are on
169. orte ne Rx dedu oes exe aaea 67 Configuring the EMI Adapter sssssssessssssessseseeee enne rentre enne nnn snnt nennen 86 Configuring the SMPP Adapter ssssssssssssssseseseeenneee enne rint enne nnn snnt senes 92 Configuring the IS 41 CDMA Adapter sse enne nnns nnne 103 Configuring the IS 41 TDMA Adapter ssssssssssssseseeeeeee enne nennen nnne nnns 113 Configuring the SCA Adapter sessssssssseses esses eene aesa aadi atandi nain nnne nnns 115 Configuring the Wrapper Adapter sssssssssssssseseneeeeeee enne 118 Chapter 4 Configuring Messaging Manager Director 123 ou 123 Configuring Chassis Actions ssssssssssseseses eene entente sinn innen nn nes 123 Configuring Macro Nodes ssssssssssssseseseeenene eee entere nentes nnn intent etri nnn sn nenn enne 126 Creating Control Plans sess en nennen senten terrens nnns internen neis 133 Configuring Messaging Manager to Send SMPP Parameters in Notifications 133 Configuring Messaging Manager to load ACS Control Plans sssssssssss 136 Chapter 5 Configuring Messaging Manager Services 139 emu U P 139 Mobile to SMSC Messag
170. over MAP having triggered them to ACS to offload all large messages to a separate SMSC The following diagram shows the modules required Messaging Manager Director Service Plan onvergen Billing Manager Access arging Access E Messaging Manager 220 Editing the eserv config Using the example network on page 140 follow the steps below to set up MM to do basic MO SMS and MT SMS Step Action 1 Take a copy of the example eserv config provided at install of MM 2 Edit the eserv config file to have only two adapters a MAP adapter and an SMPP adapter Note You can place a at the beginning of each unwanted line Configure the MAP and SMPP adapters 4 In the xmsTrigger area of the configuration file configure the following features if required e Collecting statistics on page 62 148 NCC Messaging Manager Technical Guide Step Action e Generating CDRs on page 56 5 Rename the eserv config that is in use to a known name 6 Rename the copy of the eserv config that you have made all your changes to to be eserv config 7 Reread the configuration file See Rereading the eserv config file on page 26 for details Configuring Messaging Manager Here is the process used to configure the service The following steps are carried out using the Messaging Manager screens See MM User s Guide Stage Description 1 Create adapters 2 Create nodes 3 Create schemes 4 Create Message Center 5 Open sche
171. parameter usr Syntax usr Description The unix user which is running the instance of xmsTrigger you want to update the configuration of Type String Optionality Optional default used if not set Allowed Any valid unix userid Default root Notes xmsTrigger is usually started by acs oper so acs oper should usually be specified Example acs oper Example eserv config Here is the example configuration with comments removed XMS serviceLibrary validityTime 5 flushTime 60 maxAge 3600 26 NCC Messaging Manager Technical Guide DialledNumberAvailable false xmsUndoNumTranslation false xmsAgent tcpWaitTimeMilliSec 10 rateLimitAlarmIntervalSec 60 xmsStore xmsTrigger a SECURE limits maxConcurrentTransactions 0 warnConcurrentTransactionsPercentage 70 warnConcurrentTransactionsPeriod 5 clearConcurrentTransactionsPeriod 5 maxSmsPerSecond 200 warnSmsPerSecond 180 options MCC SAS EDR MCP gateways MO SMS MT SMS VAS SMS adapters MAP CDMA TDMA EMI SMPP API SECUREKey 123456 xmsAgentInboundServiceKey 102 xmsAgentOutboundServiceKey 103 pollTime 100000 loadReportingPeriod 10 routingScheme loadIntervalSeconds 600 mtTransactionLifetimeSeconds 30 oracleusername scp oraclepassword scp oracledatabase dialledStarEncodi
172. pe String Optionality Mandatory Allowed Default Notes Example oraclepassword scp oracleusername Syntax oracleusername name Description The Oracle user name Type String Optionality Mandatory Allowed Default Notes 46 NCC Messaging Manager Technical Guide Example oracleusername scp pollTime Syntax pollTime time Description Cycle period to check for activity for TCP IP sockets Type integer Optionality Allowed Any positive non zero integer Default 100000 Notes in milliseconds Example pollTime 100000 processMsgSCI Syntax processMsgSCI true false Description Used to control SCI handling in xmsTrigger Type boolean Optionality Allowed true false Default true Notes If set to true it invokes the SCI handler in xmsTrigger Example processMsgSCI true pstore Description List of persistent storage parameters within See Setting Pstore on page 60 result Syntax result result Description Protocol specific result based on the cause value Type Optionality Allowed 0 Success 1 Transient Failure 2 Permanent Failure 3 Abort Default 1 Notes Example result 1 routingScheme Description This sub section supplies parameters for the routing scheme Example routingScheme loadIntervalSeconds 600 Chapter 2 Configuration 47 SECUREkey Syntax SECUREKey key Description Pre defined security key Type integer
173. perform protocol translation based on the inbound and outbound communication paths This can be statically configured through the management UI but can be dynamically overridden during transaction processing by the service control layers Typically all message traffic arriving at the VMP is processed for charging if necessary then immediately directed to the destination This process of delivering directly to a destination is known as First Delivery Attempt or FDA When huge traffic spikes occur such as during holiday peaks or events such as televoting MM can absorb the load and groom traffic to provide smooth processing and near real time delivery 2 NCC Messaging Manager Technical Guide Deployment diagram This diagram shows the Messaging Manager deployment architecture Administrator s Java Screens Messaging Manager features Messaging Manager provides the following features FDA First Delivery Attempt SMS are directly delivered through SS7 without going through an SMSC Overload protection from SMS traffic peaks for example special events New Year or application peaks time televoting MM enables you to offload your SMSCs and protect them from traffic peaks This enables you to extend your capability to handle extreme traffic peaks in an efficient way Value added SMS services These include Flash messaging Auto reply Anti spam SMS copy to mobile or email SMS MT forwarding Voting campaigns Real ti
174. r Type Integer Optionality Optional Allowed Default 5 Example mscTimeout 5 mscVersionCacheSize Maximum number of entries that the cache of MSC versions can grow to Default 1000 natureOfAddress Parameter which configures the destination reference IMSI when we receive a LMSI and an IMSI from the HLR lookup Default 1 numberPlan Parameter which configures the destination reference IMSI when we receive a LMSI and an IMSI from the HLR lookup Default 6 nonGprsAdapter If separate MAP adapters have been configured for GPRS non GPRS messages this setting is used in the GPRS adapter to specify the name of the corresponding MAP adapter where GPRS is not supported Default i Allowed String name of an adapter Chapter 3 Configuring Messaging Manager Multigate 77 Note Used in the adapter with the configuration of the gorsSupport on page 75 parameter set to supported or preferred originatingTimeout The period at which an incoming MAP message that is while Messaging Manager ACS process the message will be timed out and a MAP error sent to the MSC Default 10 Allowed Seconds pathRetryRandomisation Syntax pathRetryRandomisation seconds Description The amount of randomization for the delay interval when selecting a delay for a retry Allowed integer Default 1 Notes Example pathRetryRandomisation 1 pathRetrySegmentOffset Syntax pathRetrySegmentOffset seconds
175. r both of the following ways 1 Originating number for example SMS MO prepaid billing 2 Terminating number for example ASP specific processing such as context based routing Chapter 1 System Overview 17 Instant Messaging Scenario assumptions This section describes scenarios that will be supported by the SCA adapter Three scenarios are outlined and described below In these scenarios it is assumed that two subscribers have access to SIP instant messaging user agents and also GSM handsets for sending short messages It is assumed that have registered their SIP URIs with a registrar and that SCA is installed on the machine Note that SIP routing is handled by the SCA and not covered here In addition it assumes there exists a special domain Oracle com that can forward an instant message to a handset using SMS 641233570 641233402 Dick imdomain com SMS forwarded to SIP In this scenario Tom sends a short message to Dick who has enabled instant message forwarding using some mechanism not relevant to this design This will forward a copy of the short messages to Dick s SIP user agent 18 NCC Messaging Manager Technical Guide This is accomplished by executing a control plan that contains the Send Short Message Notification node SSMN which allows sending instant messages The node specifies the destination address in URI format for example Dick imdomain com The content and other information about the message is
176. rReplyPath 79 How does tracing work 53 HPLMN 184 HTML 184 hybridiseMapVersions 79 IDP 184 IMSI 184 IN 184 INAP 184 Inbound message types 156 inboundTimeout 120 includePayloadDRInfo 102 Incoming classification addressing 9 informationElementldentifier 137 Initial DP 184 install routing node sh 170 Installation and Removal Overview 172 Instant Messaging 18 66 118 interface 120 interfaceName 61 119 InterfaceName 126 Interfaces and nodes 12 internalDRTimeout 45 Introduction 1 5 6 8 9 21 25 37 62 125 129 155 163 166 169 170 172 IO 184 IP 184 IP address 185 IS 41 185 IS 41 CDMA adapter overview 106 IS 41 TDMA adapter overview 116 ISDN 185 ISUP 185 ITU 185 L lastSegmentDeliveryReceiptOnly 79 lib e 71 90 95 107 119 122 Limitation 65 limits 52 List of tags 166 LMSI 185 Loading eserv config changes 26 loadintervalSeconds 45 loadReportingPeriod 45 localTimeZone 79 Locate 160 Location 23 24 log 58 macroNodes configuration 129 Manager 4 144 155 MAP 185 MAP adapter overview 69 max 67 max age seconds 62 max writes per flush 62 maxAge 139 maxConcurrentTransactions 52 maxFileSizeKB 55 maximumbDestinations 130 maxno 58 maxNumFiles 55 maxSmsPerSecond 53 maxUnsegmentedLength 79 maxValidityPeriod 102 MC 185 MCC e 185 MDN 185
177. rentTransactions Syntax maxConcurrentTransactions period Description The maximum number of concurrent transactions that can be handled Type integer Optionality Allowed Default 5 Notes Example maxConcurrentTransactions 5 Chapter 2 Configuration 51 warnConcurrentTransactionsPercentage Syntax warnConcurrentTransactionsPercentage pc Description Percentage of maxConcurrentTransactions at which to emit a warning Type integer Optionality Allowed Default 90 Notes Example warnConcurrentTransactionsPercentage 90 warnConcurrentTransactionsPeriod Syntax WARNConcurrentTransactionsPeriod period Description How often to report we are over warnConcurrentTransactionsPercentage concurrent transactions Type Optionality Allowed Default 5 Notes In seconds Example WARNConcurrentTransactionsPeriod 5 maxSmsPerSecond Syntax ArraySize num Description The maximum number of transactions per second we will accept before throttling Type Integer Optionality Mandatory Allowed Default 1000 Notes Example maxSmsPerSecond 200 warnSmsPerSecond Syntax warnSmsPerSecond num Description The maximum number of transactions per second before warning that throttling is imminent Type Integer Optionality Mandatory Allowed Default 80 of maxSmsPerSecond Notes Example warnSmsPerSecond 180 52 NCC Messaging Manager Technical Guide Tracing SMSs How do
178. rigger rule 0901041701 NoPlan NoPlan 000 max Submit 0 Looking for originating trigger rule with NoPlan from message type S Control Plan Submit 0 Looking for destination trigger rule with NoPlan S Control Plan D 3 SE 5 0 00 C3 0 62 012 0 X2 0 t2 ES C0 D C0 O C2 QC C620 C0 D D 4D CO 2 2 OW 2 5 2 t2 Cc 00 OS oe 0000 o SSSBES8SSBSS SS SSBB BSBSBSBSBSSBSEBSSBSBSBSBSBSEBB MX Found routing rule 101869 using MX Routing class Submit 0 MX Orig address 000004 domain NoPlan MX Message Centre name Default MX Found path 11586 SMPP1 SMSC MX Using path 11586 SMPP1 SMSC MX Trying output adapter SMPP1 SMPP mmxiSMPP so MX Message modified flag false SMPP Received GenericSM from MMX SMPP OA 004001000004 DA 004001000004 SMPP Text Test Message SMPP Got outgoing connection SMPP1 SMSC S SMPP1 SMSC SMPP outgoingOriginatingNumberRules unmatched 4 000004 o SMPP outgoingDestinationNumberRules unmatched 4 000004 o SMPP Sending submit sm to protocol handler o SMPP submit sm 3 queued to be sent out on the wire MMX Term tran accepted GenericSM i MAP MMX processed GenericSM successfully MMX Input adapter handled TCAP BEGIN successfully o SMPP Handling SMPP message command id 0x80000004 submit sm res p command status 0x00000000 Sequence number 0x00000003 message id no dr o SMPP Result from MMX is suc
179. riggering rules 12 throttledCommandStatus 106 throttledDeliveryFailureCause 85 throttledErrorCode 92 throttledFailureCauseCode 116 time out 59 time24Format 132 timeFormat 132 timeoutTick 126 127 timestampAdvance 93 timestampBucketSize 94 timestampFlush 94 TLV 190 tlvID 98 TLVs 97 TLVs parameters 98 tlvType 98 Tools and Utilities 169 Trace points 163 tracing 50 Tracing 53 163 Tracing configuration 53 Tracing output 164 Tracing parameters 54 Tracing SMSs 22 50 53 transientFailureErrorCode 92 Trigger detection point TDP definition file 175 Trigger detection point definitions 177 Triggering 7 Triggering rules 12 TT 78 type 123 132 Typographical Conventions vi U URI 190 useCustomUSSDNotificationNoARules 128 userpass 62 useTONNPI 57 Using Messaging Manager Multigate 7 Using the Messaging Manager platform 5 usr 26 USSD 190 ussdChassisAction parameters 127 V validityTime 140 Variations 13 15 16 17 Virtual Message Point components 4 VLR 190 VMP e 190 VMSC 190 VWS 190 W warnConcurrentTransactionsPercentage 52 warnConcurrentTransactionsPeriod 52 warnSmsPerSecond 53 WEMT 190 What is early ack 59 What is Messaging Manager 1 When is a Delivery Report produced 12 Which adapters do need 66 X XMS 186 190 xmsAgent 38 154 xmsAgen
180. rmat 130 CAMEL 181 CC 182 CCS 182 CDMA 182 cdr 42 CDR 182 Changing the configuration 60 ChassisActions configuration 125 Checking the Installation 172 Checking the xmsScp installation 173 Checking the xmsSms installation 172 clearConcurrentTransactionsPeriod 52 CLI 182 Collecting Statistics 22 49 62 143 145 148 150 155 Compiling control plans manually 173 Concatenated messages 40 43 79 80 84 config 71 89 95 Configuration 21 154 Configuration components 22 Configuration file format 25 Configuration Overview 21 Configuration process overview 22 Configuring Chassis Actions 125 Configuring EDR collection 57 Configuring EDR Collection 22 42 57 143 145 148 150 Configuring IN Call Model Triggers 175 Configuring Macro Nodes 37 129 Configuring Messaging Manager 144 146 149 151 Configuring Messaging Manager Director 22 125 Configuring Messaging Manager Multigate 22 40 65 Configuring Messaging Manager Services 141 Configuring Messaging Manager to load ACS Control Plans 37 138 Configuring Messaging Manager to Send SMPP Parameters in Notifications 136 Configuring MMX to load ACS Control Plans 138 Configuring SMSs to trace 164 Configuring the EMI Adapter 4 89 Configuring the Environment 22 Configuring the IS 41 CDMA Adapter 5 106 Configuring the IS 41 TDMA Adapter 5 116 Configuring the MAP A
181. ro node adapters Internal adapter The endpoint for the SSMN macro node lib xmsiWrapper so SSN 9 adapterName Wrapper config General Wrapper adapter parameters Here are the general parameters for the Wrapper adapter adapterName Syntax adapterName name Description Identifier for the adapter Allowed Any text string but should be meaningful for example include the protocol used For example e MAP1 for MAP e EMI1 for EMI e SCA1 for SCA e SMPP1 for SMPP e CDMA1 for IS 41 CDMA e TDMA1 for IS 41 TDMA e Wrapper for Wrapper Default No default 118 NCC Messaging Manager Technical Guide Notes This name must also be in the configuration database before Messaging Manager will run correctly See MM User s Guide lib Syntax lib library Description The name of the library that contains the Wrapper adapter being configured Allowed xmsiWrapper so Default No default Example lib xmsiWrapper so SSN Syntax SSN num Description Destination subsystem number of messages to be handled by this adapter Allowed Valid subsystem number Notes Non zero to handle incoming TCAP Example SSN 18 Global Wrapper adapter configuration The following section of the eserv config specifies the global parameters for the Wrapper adapter config xmsTimeout 5 tcapTimeout 10 xmsWrapper interface xmsIf pe 55 ssn 7 type itu gt wo x
182. ro to handle incoming TCAP SSN 18 Global EMI configuration The following section of the eserv config specifies the global parameters for all EMI connections config suppressPathInfoReport true displayZeroPathReport false PathReportingInterval 60 throttledErrorCode 4 transientFailureErrorCode permanentFailureErrorCode 4 3 incomingOriginatingNumberRules fromNoa 999 prefix min 1 max 32 remove 0 resultNoa 2 incomingDestinationNumberRules outgoingOriginatingNumberRules outgoingDestinationNumberRules idi zu Chapter 3 Configuring Messaging Manager Multigate 87 emiDefaults defaultMessagePriority Normal pstoreNumberRules fromNoa 999 prefix 010 min 1 max 32 remove 3 prepend 7 fromNoa 999 prefix 091 min 1 max 32 remove 3 prepend 7 timestampAdvance true timestampBucketSize 5000 timestampFlush 2 emiDefaults 4 mmxiEMI so config Global EMI parameters Here are the parameters for configuring the global EMI adapter EMI error codes Here is a list of EMI error codes for the following e throttledErrorCode e transientFailureErrorCode e permanentFailureErrorCode a Oheksumemr oS O 2 Sytaxemo S 3 Operation not supported by system S O operation notated Call paring active e mea z Authentication failure S O 8 Legitimization code for all calls failure
183. rt messages MO SMS diagram Using only the Messaging Manager base module MM can be configured to provide an MO SMS service In this example we will receive mobile originating MAP messages and deliver to the SMSC over TCP IP using the SMPP protocol The following diagram shows the modules required Messaging Manager node l k A party Variations Standard person to person messaging may be configured in several different ways using MM e No FDA as shown at 1 e With FDA as shown at 2 e With multiple alternate routing Chapter 1 System Overview 13 Multiple alternate routing allows several routes to be tried to deliver a message Routing attempts may be similar to below Rack Mounted 4 Reserve Charge SS7 to SMSC SMPP to SMSC ca Network Key d Delivery Attempt 1 Delivery Attempt 2 Delivery Attempt 3 Application to Mobile Messaging Application to Mobile diagram Using only the Messaging Manager Base module MM can be configured to provide an application to mobile service In this example we will receive EMI protocol messages from ASPs and deliver them to an SMSC over SS7 using the IS 41 protocol 14 NCC Messaging Manager Technical Guide The following diagram shows the modules required Messaging Manager node SLEE EUN DN Variations Application to Mobile messaging may be configured in several different ways using MM e No FDA e With FDA only as shown
184. s It provides the following functionality e SMS transaction management for end to end delivery e Transaction throughput control e Notification and status reports e Real time convergent billing services e Flexible multi party billing e Support for all standard SMS transport options e Support for mapping between transport protocols e Connection level load balancing and redundancy e Subscriber information partitioning e Statistics generation e Alarm generation e CDR generation e Provisioning and administration Note Collection of statistics requires the NCC Service Management System SMS application Using the Messaging Manager platform Messaging Manager provides a platform from which multiple advanced messaging services including but not limited to SMS MO and SMS MT may be designed and implemented This messaging platform leverages the NCC SLC Service Logic Execution Environment SLEE The SLEE manages each message event coming into and going from MM and provides control of these messages between the network layer and the applications SLC is designed to maintain integrity simplify management and ensure high performance when servicing massive messaging volumes from various underlying networks to multiple application services Chapter 1 System Overview 5 Data life cycle The diagram below shows a time line down the diagram of activities that occur for the replication process Administrator s Java Screens
185. s what if any contribution that node makes to the scheme s routing interface requirements When is a Delivery Report produced Delivery Reports are generated and sent as a completely separate transaction like other SMSs that Messaging Manager handles That means existing routing and retry functionality can be used to deliver the DR Messaging Manager generates a delivery report DR in the following conditions e An early acknowledged message is subsequently unable to be delivered Messaging Manager can be configured to generate a delivery report regardless of whether or not the originator requested it through the alwaysProduceNonDeliveryReceipt parameter e If Messaging Manager successfully delivers a message by FDA and the originating party requested a delivery receipt then a delivery report is generated and sent to the originator Delivery Report failure Under normal default configuration a DR send failure is resent however setting the parameter singleShotDeliveryReport to true will prevent a retry to be attempted Statistics Any statistics produced by a Delivery Report will have INTERNAL DR in the detail field EDR fields The following fields within a Delivery Report EDR will always be set to these values e PRN Wrapper e OAID MMX INTERNAL DR ADAPTER 12 NCC Messaging Manager Technical Guide Mobile to Mobile Messaging Description Mobile to mobile messaging provides standard person to person sho
186. sIf gprsSupport supported nonGprsAdapter MAP2 sgsnPrefixes 000 false doProtocollIdMapping defaultProtocolld protocolidMap in 127 out 0 oO fallbackAlphabet UCS 2 scheduledDeliveryTime defaultMessagePriority Normal PC 55 SSN 8 GT 5114406267 GTMap prefix 0010019198 value 919827002402 SCA 5114406267 natureOfAddress 1 international numberPlan 6 E 212 defaultMapVersionSmsc 3 defaultMapVersionMsc 3 deliveryFailureStatusCode 64 throttledDeliveryFailureCause 4 congestion mscVersionCacheSize 1000 hybridiseMapVersions false maxUnsegmentedLength 120 splitLongMessages tru alarmMask 0 honourReplyPath false pathRetryRandomisation 1 pathRetrySegmentOffset 1 localTimeZone UTC 70 NCC Messaging Manager Technical Guide defaultTransientFailureErrorCode 32 defaultPermanentFailureErrorCode 32 incomingOriginatingNumberRules fromNoa 2 prefix 04 min 4 max 32 remove 1 prepend 0064 resultNoa 1 fromNoa 3 prefix 4 min 4 max 32 remove 0 prepend 0064 resultNoa 1 incomingDestinationNumberRules outgoingOriginatingNumberRules outgoingDestinationNumberRules ol c privateExtensions extId 1 2 776 8 8 8 8 11 asnlTags OxEO 0x80 profileTagID 327814 name imei Global MAP parameters
187. se are logged in the xmsTrigger logfile This can cause the logfile to fill up unnecessarily If this parameter is set to true the heartbeat message being written to the xmsTrigger log is suppressed Example suppressPathInfoReport true Chapter 3 Configuring Messaging Manager Multigate 89 throttledErrorCode Error code to return to throttled messages Default 4 Allowed Refer to EMI error codes on page 88 for list of values transientFailureErrorCode Error code to return for transient failures Default 4 Allowed Refer to EMI error codes on page 88 for list of values EMI Defaults configuration The emiDefaults section of the eserv config specifies the EMI values that will be used for connections emiDefaults defaultMessagePriority Normal pstoreNumberRules fromNoa 999 prefix 010 min 1 max 32 remove 3 prepend 7 fromNoa 999 prefix 091 min 1 max 32 remove 3 prepend 7 timestampAdvance true timestampBucketSize 5000 timestampFlush 2 EMI Defaults parameters Here are the parameters for configuring the EMI defaults in the EMI adapter defaultMessagePriority Syntax defaultMessagePriority str Description The priority to be applied to incoming messages that do not have a priority Type String Optionality Optional default used if parameter absent Allowed Default Normal Notes Example defaultMessagePriority Normal p
188. sed to control how xmsTrigger manages transient failure Type boolean Optionality Optional default used if not set 48 NCC Messaging Manager Technical Guide Allowed Default Notes Example true xmsTrigger will not attempt alternate routing of a message upon receipt of a transient failure false false Refer to Setting ACS Cause to Result stopRoutingOnTransientFailure false stopRoutingOnPermanentFailure Syntax Description Type Optionality Allowed Default Notes Example successDeliv stopRoutingOnPermanentFailure true fals Used to control how xmsTrigger manages permanent failure Boolean Optional default used if not set true xmsTrigger will not attempt alternate routing of a message upon receipt of a permanent failure false true stopRoutingOnPermanentFailure false Syntax Description Type Optionality Allowed Default Notes Example tracing Description ryReceiptText successDeliveryReceiptText text The text for the successful Delivery Receipt string Your message to lt destination gt was delivered where lt destination gt substitutes the destination number successDeliveryReceiptText Your message to lt destination gt was delivered List of SMS tracing parameters within See Tracing SMSs on page 53 xmsAgentInboundServiceKey Syntax Description Type Optionality Allowed Default Notes Example xmsAgentI
189. separate machines See PC SSN and type parameters timeoutTick Syntax timeoutTick seconds Description The granularity of SLEE dialog timeout checks Note This can conflict with the option of the same name in the RIMS chassis actions In case of a conflict the value to use is undefined Example timeoutTick 5 xmsDirectFromPrefix Syntax xmsDirectFromPrefix prefix Description A prefix that will be added to the source MSISDN when the MMX Direct transport is chosen in the notification configuration Type String Optionality Optional default used if not set Allowed Default no prefix is added Notes Example xmsDirectFromPrefix 1 124 NCC Messaging Manager Technical Guide xmsFDAFromPrefix Syntax Description Type Optionality Allowed Default Notes Example xmsFDAFromPrefix prefix A prefix that will be added to the source MSISDN when the MMX FDA transport is chosen in the notification configuration String Optional default used if not set no prefix is added xmsFDAFromPrefix 2 ussdChassisAction parameters Here are the parameters in the ussdChassisAction sub section of the ChassisActions section of the eserv config recordResponseTimes Syntax Description Type Optionality Allowed Default Notes Example recordResponseTimes true fals Whether to record response times in a temporary storage tag Boolean Optional default
190. sm RP OA CHOICE msisdn 2 IMPLICIT OCTET STRING SIZE 1 20 SIZE 1 9 serviceCentreAddressOA 4 IMPLICIT OCTET STRING SIZE 1 20 noSM RP OA 5 IMPLICIT NULL sm RP UI OCTET STRING SIZE 1 200 extensionContainer SEQUENCE privateExtensionsList 0 IMPLICIT SEQUENCE SIZE 1 10 OF SEQUENCE extId ExtId extType MOForwardSMType OPTIONAL OPTIONAL E pcs Extensions 1 IMPLICIT SEQUENCE OPTIONAL OPTIONAL ExtId OBJECT IDENTIFIER 0x01 0x02 0x308 0x08 0x08 0x08 0x08 0x0B OForwardSMType PRIVATE 0 IMPLICIT SEQUENCE imei 0 IMPLICIT OCTET STRING SIZE 8 OPTIONAL Here is the example configuration privateExtensions extId 1 2 776 8 8 8 8 11 asnlTags OxEO 0x80 profileTagID 327814 name imei protocoliIdMap List of TP PID translations Default empty Example Turns 7f 127 not valid in MAP 2 into 0 protocollIdMap in 127 out 0 Note Optional parameter rimsTimeout Syntax rimsTimeout seconds Description The timer for Messaging Manager Navigator queries It is the period at which an outgoing message that is while Messaging Manager waits for a response from Messaging Manager Navigator will be timed out The adapter will close the connection to
191. so xmsiMap so xmsiWrapper so 152 NCC Messaging Manager Technical Guide Statistics Introduction Messaging Manager statistics are generated by each SLC and then transferred at periodic intervals to the Service Management System SMS for permanent storage and analysis MM allows new statistics to be registered on the system without the need for manual intervention An existing statistics system provides functions for the collection of basic statistical events This is provided in the Oracle SMS application For more information about the SMS statistics subsystem see SMS User s Guide Setting up statistics collection Paths and categories used for gathering statistics against are defined using the Messaging Manager Manager screens Refer to MM User s Guide To turn on statistics gathering see Collecting Statistics on page 62 Diagram Here is an example of statistics collection There are three ASPs However the Category STOCK QUOTES has been applied to both ASP STOCK and ASP REUTERS so in this instance the statistics for both ASPs will be counted and added to the database table Category Category NZ WEATHER STOCK QUOTES ASP WEATHER ASP REUTERS STOCK QUOTES NZ WEATHER Category STOCK QUOTES Chapter 6 Background Processes 153 Inbound message types Every message coming into MM is one of the following transaction types On receipt of any message MM will increment th
192. ssaging teleservice WEMT is used to carry enhanced messaging service EMS over SMS Example allowFDAforWEMT true allowIncoming Syntax allowIncoming true false Description Determines whether inbound messages are allowed 106 NCC Messaging Manager Technical Guide Optionality Mandatory Allowed true false Default false Example allowIncoming false allowOutgoing Syntax allowOutgoing true false Description Determines whether initial messages may be sent out through the MAP interface Optionality Mandatory Allowed true false Default false Example allowOutgoing false defaultEndpointType Syntax defaultEndpointType type Description The endpoint type that is assumed when the message direction cannot be determined for example CDMA User Ack Optionality Mandatory Allowed SME MC Default SME Example defaultEndpointType SME defaultMessagePriority Syntax Description Type Optionality Allowed Default Notes Example defaultMessagePriority str The priority to be applied to incoming messages that do not have a priority String Optional default used if parameter absent Normal defaultMessagePriority Normal defaultPermanentFailureCauseCode Syntax Description Optionality Allowed Default Example defaultPermanentFailureCauseCode cod Default SMS CauseCodes mappings for Permanent failures if no releaseCauseMap entry matches
193. storeNumberRules Defines the number normalization rules to be applied for SCTS mapping Note Optional See Number Normalization on page 64 Example pstoreNumberRules number insertion rules fromNoa 999 prefix 010 min 1 max 32 remove 3 prepend 7 number lookup rules fromNoa 999 prefix 091 min 1 max 32 remov 3 prep nd 7 90 NCC Messaging Manager Technical Guide timestampAdvance Values for configuring the EMI System Message SM field Emulate SMSC behavior by advancing the timestamp e true emulate SMSC timestamp advance e false timestamp using current time Default true Allowed true false Note When on true the IP adapter simulates the behavior of the SMSC by advancing the timestamp if another message with the same destination number is found in the message buffer When off false the IP adapter uses the current system time and the SM field will not be unique for messages to the same destination received within the same 1 second timeframe timestampBucketSize Sets the size of the hash map used for searching the message buffer Default 5000 Note e The size of the message buffer is determined by the incoming message rate and the flush period NOT by this parameter e This parameter can only be set at startup timestampFlush Period between buffer cleanup Default 2 Allowed Seconds Note Setting this parameter to a large value will increase memory use
194. sult in transactions being throttled For more information about throttling see Congestion Control in MM User s Guide Based on the transaction type messages are then directed to one of four sets of trigger rules for Submit Deliver Notify or Route Info transactions This may result in triggering to ACS to run a message control plan in order to control delivery processing options Control plans can change message parameters Having selected a best match trigger rule it is possible to modify the transaction s routing class from its default value assigned during incoming classification A matching trigger rule may be one of the following e Perform an action 10 NCC Messaging Manager Technical Guide Stage Description e Trigger to ACS to run acontrol plan For more information about triggering see Triggering in MM User s Guide 3 If the message was triggered to a control plan and the control plan returned a release INAP that is the control plan exited after a Disconnect node or an error exit the ACS release cause is mapped to an action or error code The action or error code is added to a Nack which is returned to the source of the message For more information about action and error codes see Messaging Manager Action and Error Codes in MM User s Guide Outbound routing This table describes how Messaging Manager processes outbound message routing Stage Description 1 Outbound routing takes place based on the routing class
195. t configuration 38 xmsAgent parameters 38 xmsAgentlnboundServiceKey 50 xmsAgentOutboundServiceKey 50 xmsDirectFromPrefix 126 xmsFDAFromPrefix 127 xmsiWrapperlfName 132 xmsTimeout 123 xmsTrigger 22 37 39 123 xmsTrigger Application 22 37 153 xmsTrigger configuration 39 xmsUndoNumTranslation 140 xmsWrapper 124 194 NCC Messaging Manager Technical Guide
196. t on a path listed in a Locate routing rule MSG PATH LOCATE TIMEOUT For every delivery attempt that times out on a path listed in a Locate routing rule MSG PATH LOCATE TEMP ERR For every delivery attempt resulting in a transient failure on a path listed in a Locate routing rule MSG PATH LOCATE PERM ERR For every delivery attempt resulting in a permanent failure on a path listed in a Locate routing rule Note All of these statistics will include the outbound path s statistics category in the detail field Other statistics This table describes the function of each field FM pmsPm MSG inboundMsgType FAIL TIMEOUT If the inbound transaction s timeout is exceeded before sending a result MM will increment this statistic with the inbound path s statistics category in the detail field No other MSG inboundMsgType result statistics will be incremented in this case 158 NCC Messaging Manager Technical Guide Fed pese MSG jinboundMsType FAIL ABORT If the sending entity aborts the inbound transaction MM will increment this statistic with the inbound path s statistics category in the detail field No other MSG_inboundMsgType_result statistics will be incremented in this case Delivery receipt When MM generates a delivery receipt having delivered or failed to deliver an SMS directly statistics will be recorded in a way that is consistent with the procedure for handling an external delivery receipt
197. t the macro nodes used by Messaging Manager see NCC Feature Nodes Reference Guide eserv config Macro Node configuration This is a high level view of the macroNodes configuration section of eserv config XMS macroNodes Macro Node Name configuration for macro node macroNodes configuration Here is an example configuration macroNodes SendShortMessageNode xmsiWrapperIfName xmsIf tcapOrigAddr PC 0 SSN 0 type itu tcapDestAddr PC 0 SSN 0 type itu dateFormat SA d SB Y timeFormat I M Sp time24Format H M 22 callTimeFormat I M Sp maximumDestinations 1000 numberPlan 1 SendUSSDNotificationNode MSISDNTranslationType 2 destSSN 6 Send Short Message Node configuration The Send Short Message Notification node is a Messaging Manager macro node that also uses the Wrapper adapter to send out the notification Therefore there are additional configuration tasks that must be completed for this node to function correctly e The node must be configured in the macroNodes configuration section of the eserv config file e The Wrapper adapter must be configured in the eserv config file See Configuring the Wrapper Adapter on page 118 Send Short Message node parameter descriptions Here are the macroNodes configuration parameters for the Send Short Message feature node Chapter 4 Configuring Messaging Manager Director 1
198. tMapVersionSmsc 3 defaultMapVersionMsc 3 defaultDeliveryFailureStatusCode 64 throttledDeliveryFailureCause 96 congestion mscVersionCacheSize 1000 hybridiseMapVersions false maxUnsegmentedLength 120 splitLongMessages tru alarmMask 0 honourReplyPath false pathRetryRandomisation 1 pathRetrySegmentOffset 1 localTimeZone UTC forwardSmErrorMap error 9 permanent true error 32 permanent false 32 32 defaultTransientFailureErrorCode defaultPermanentFailureErrorCode incomingOriginatingNumberRules fromNoa 2 prefix 04 min 4 max 32 remove 1 prepend 0064 resultNoa 1 fromNoa 3 prefix 4 min 4 max 32 remove 0 prepend 0064 resultNoa 1 incomingDestinationNumberRules outgoingOriginatingNumberRules outgoingDestinationNumberRules aA xmsiMap so config Non GPRS MAP adapter lib xmsiMap so Chapter 3 Configuring Messaging Manager Multigate 85 adapterName MAP2 pointCodes 1003 SSN 8 config GT 5114406268 TT 0 gprsSupport unsupported xmsiMap so config Configuring the EMI Adapter EMI adapter overview The EMI adapter communicates between the Messaging Manager platform and any configured ASPs and SMSCs using EMI In a system using EMI the adapter must be configured to know of all entities that may connect to it and all entities that
199. ter By default if a Nack is received later then it will not be passed back to the sender and subsequent routing will also not send an Ack XMS xmsTrigger other Messaging Manager configuration options earlyAckSME false earlyAckMC false alwaysProduceNonDeliveryReceipt fals Early ack options This feature is configurable for each adapter instance to either be Always on earlyAckMC True earlyAckSME True Apply when a send to SME MS or ASP is earlyAckMC False first encountered earlyAckSME True Always off earlyAckMC False earlyAckSME False Chapter 2 Configuration 59 Early ack functionality support The early ack functionality is supported under e MAP 1 2 and3 e SMPP 3 4 and 5 0 e EMI UCP 4 0 e IS 41 Setting Pstore Pstore configuration Persistent storage is used for long term storage of information Information stored using pstore will be stored for as many days as required this is set using the pstore configuration in eserv config Where both early ACK and a delivery receipt have been requested for EMI messages pstore is used to store the message id that was sent by Messaging Manager When the message is delivered by the SMSC it returns to message id to Messaging Manager pstore is used to translate the SMSC message_id to the Messaging Manager generated message_id and send on in the delivery receipt Changing the configuration When the configuration is chan
200. ter 2 Configuration Overview Introduction This chapter explains how to configure the Oracle Communications Network Charging and Control NCC application In this chapter This chapter contains the following topics Configuration Overview 21 Configuring the Environment 22 eserv config Configuration 25 Messaging Manager Configuration Sections in eserv config 37 xmsAgent 38 xmsTrigger 39 Tracing SMSs 53 Configuring EDR Collection 56 Setting Early Acknowledgment 58 Setting Pstore 60 Collecting Statistics 62 Defining the Screen Language 62 MM and XMS naming conventions Reading this manual and configuring Messaging Manager you may notice that the terms MM and XMS are both used These terms have been used interchangeably throughout the software development process as a result of software evolution Many of the software processes and binaries use the term XMS and in this case the documentation will continue the use of the term The abbreviation for the Messaging Manager product is MM and this will be used in all cases except where referring to specific software binaries and processes Configuration Overview Introduction This topic provides a high level overview of how the Messaging Manager application is configured Configuration details for individual processes are located with the documentation for that process Configuration process overview This table describes the steps involved in configuring Messaging Manager for
201. that are to be sent to an SME See Setting Early Acknowledgement see Setting Early Acknowledgment on page 58 boolean true false false earlyAckSME false ryReceiptText Syntax Description Type Optionality Allowed Default Notes Example failureDeliveryReceiptText text The text for an unsuccessful Delivery Receipt string Your message to destination was NOT delivered where destination substitutes the destination number failureDeliveryReceiptText Your message to destination was NOT delivered internalDRTimeout Syntax Description Type internalDRTimeout seconds The timeout in seconds for processing and sending an internally generated delivery report Integer 44 NCC Messaging Manager Technical Guide Optionality Allowed Default Notes Example Optional default used if not set internalDRTimeout 10 loadIntervalSeconds Syntax loadIntervalSeconds seconds Description How often in seconds to check to see if we need to reload information from the database Type integer Optionality Allowed Default 600 Notes Reloads are always at intervals of this many seconds after midnight for example a value of 600 would cause reload checks at 12 00 12 10 12 20 and so on If the database has not been changed through the screens no reload is performed Example loadIntervalSeconds 600 loadReportingPeriod Synt
202. the first time Bam wem ee 1 Create the XMS section of the eserv config Messaging Manager Configuration file Sections in eserv config on page 37 Chapter 2 Configuration 21 Configure the xmsTrigger section xmsTrigger on page 151 on page 39 Configure the tracing SMSs if required Tracing SMSs on page 53 This section is required but may be empty Configure the CDR collection section Configuring CDR Collection see Configuring EDR Collection on page 56 Configure statistics collection Collecting Statistics on page 62 Set the early acknowledgement Setting Early Acknowledgement see parameters These can be done at Trigger Setting Early Acknowledgment on page and adapter level Configure the persistent storage Setting Pstore on page 60 Define the screen language for the GUI Defining the Screen Language on page interface E Configure Messaging Manager Multigate Configuring Messaging Manager Multigate on page 63 Configure Messaging Manager Director Configuring Messaging Manager Director on page 123 Configuring the Environment Configuration components MMX is configured by the following components eserv config All eserv config holds most of the eserv config Configuration configuration for MM on page 25 All SLCs Configures slee_acs the main call Configuring acs conf for processor acs conf must include the SLC the MM plug in libraries for slee_acs a
203. trigger point of 3 analyzedInformation e None of the global configuration parameters are considered set Global configuration parameters The following configuration parameters may be set once on individual lines in the TDP definition file KEEP SD If defined ALL all stop digits defined by the BCD digit F on the end of called party numbers are kept in the called party number By default the stop digit is stripped from ALL triggered numbers This parameter is intended for CAMEL testing purposes only and should not be defined under normal usage If defined the called party number is also copied into the intialDP s Appendix A Configuring IN Call Model Triggers 173 calledPartyBCDNumber CAMEL parameter The NOA of the called party number becomes the BCD number type ADDITIONALNUMS If defined the IN Call Model will request all additional numbers available from the underlying protocol and insert them into the InitialDP message sent to the SLC All these additional numbers are placed into a G8 extension in the InitialDP except any additional calling party number that is placed in the additionalCallingPartyNumber field ETC RULES c If defined then additional Establish TemporaryConnection ETC rules or are used ETC RULES c s If the integer c is defined the correlationID in all ETC messages from the SCF are appended on to the end of the assistingSSPIPRoutingAddress that is used the digits are padded to a width of c
204. trol plans can be triggered from Messaging Manager Multigate and include service logic based many properties such as e Incoming path names that is protocols and connections e Transaction types such as Submit Deliver Notify or Route Info messages e Originating and or destination address e Location of originating and or destination mobile station e Message content e Time of day A message can be triggered from Multigate to a specific message control plan to provide extended customer specific service logic For example Messaging Manager Director may modify any routing options before signalling to Multigate to continue delivery so that Multigate routes the message according to the new options Messaging Manager Director can ensure that delivery proceeds only if charging is satisfied such that delivery and charging proceeds as a single transaction Note To use the features provided by the Messaging Manager Director module the NCC ACS and SMS applications must be installed Diagram Here is a diagram showing the Messaging Manager Base Messaging Manager Multigate and Messaging Manager Director modules Messaging Manager Director Service Subscriber Plan Profile onv ergen Billing Messaging Manager Multigate Trigger Routin TTE OSA CS Subscriber MT ER cin Access I nn I Driver N I I 1 8 NCC Messaging Manager Technical Guide Routing options With the addition of the Messaging Manager Director modul
205. very time set to this Type String Optionality Optional default used if not set Allowed Format is as per the SMPP spec A 10 minute delay would be 000000001000000R Default d 102 NCC Messaging Manager Technical Guide Notes Example scheduledDeliveryTime teleserviceRoutingMap Syntax teleserviceRoutingMap mappings Description Array of teleservice mappings SMPP has an optional attribute called service_type whose value is a string like EMS or CMT The actual strings tend to be operator specific We can map these to numeric IS 41 teleservices in genericSM and set the alternate delivery allowed flag for each one Allowed Default The CMT and EMS entries are defined Notes Any service types not appearing in this list will have alternate delivery disallowed and a teleservice of 0 Example teleserviceRoutingMap teleservice 0 livery true CMT teleservice 4098 livery true EMS teleservice 4101 livery true serviceType allowAlternat serviceType allowAlternat serviceType allowAlternat C I vil voll throttledCommandStatus Syntax throttledCommandStatus status Description Command status to return to throttled messages Allowed Refer to SMPP command statuses on page 100 for a list of values Default 88 Example throttledCommandStatus 88 Configuring the IS 41 CDMA Adapter IS 41 CDMA adapter overview The IS41 adapter commu
206. wed Valid directory path Default IN service packages XMS cdr closed Notes This parameter may not be changed after installation and initial setup Example destdir IN service packages XMS cdr closed filename Base filename used to create EDR log files Allowed alphanumeric string Note The format log file name is filename YYYYMMDDHHMMSS cdr log Turns EDR logging on or off Default false Allowed true false maxno Maximum number of EDRs per file Default 10000 Chapter 2 Configuration 57 num_files Number of expected EDR files Default 64000 Note This parameter may not be changed after installation and initial setup num_files_leaf Number of EDR files per leaf directory Default 64 Note This parameter may not be changed after installation and initial setup tempdir Syntax tempdir dir Description The temporary directory for the working EDR log file Type String Optionality Mandatory Allowed Valid directory path Default IN service packages XMS cdr current Note A side effect of the CDR processing code of MMX is to remove all files in the tempdir when MMX starts Example tempdir IN service packages XMS cdr current time out Close EDR file after time out in seconds Default 1800 Setting Early Acknowledgment What is early ack There are two ways in which a delivery acknowledgement can be sent in MMX e MMxX does not acknowledge the sending party until the
207. x age seconds 30 max writes per flush 10 deferred delete tru userpass scp scp statistics nable fals adapters First adapter MAP lib xmsiMap so adapterName MAP pointCodes 1001 1002 SSN 8 earlyAckMC true earlyAckSME true allowConcatenatedFDA tru alwaysProduceNonDeliveryReceipt fals config disableConcatenatedSegmentPad fals abortMessagesWithZeroLengthTPDA true allowIncoming true allowOutgoing true allowDirectDelivery tru allowIncomingMap3 true allowUserRequestedDeliveryReceipt tru lastSegmentDeliveryReceiptOnly false tcapInterfaceServiceKey 22 originatingTimeout 10 smscTimeout 8 rimsTimeout 3 mscTimeout 15 rimsInterfaceName rimsIf gprsSupport supported nonGprsAdapter MAP2 sgsnPrefixes 000 doProtocolldMapping false defaultProtocolld 0 protocolIdMap Chapter 2 Configuration 29 in 127 out 0 fallbackAlphabet UCS 2 scheduledDeliveryTime defaultMessagePriority Normal PC 55 SSN 8 GT 5114406267 GTMap prefix 0010019198 value 919827002402 SCA 5114406267 natureOfAddress 1 international numberPlan 6 E 212 defaultMapVersionSmsc 3 defaultMapVersionMsc 3 deliveryFailureStatusCode 64 throttledDeliveryFailureCause 4 congestion mscVersionCacheSize 1000 hybridiseMap
208. y Acknowledgment on page 58 config The parameters in this sub section below this give the configuration for all messages for this adapter lib Syntax Description Allowed Default Example pointCodes Syntax Description Optionality Allowed Example SSN Syntax Description Allowed Notes Example lib The name of the library that contains the MAP adapter being configured xmsiMap so No default lib library xmsiMap so pointCodes pcl pc2 Destination point codes array of messages to be handled by this adapter This parameter takes priority over SSN match Optional Defined by network administrator pointCodes 1001 1002 SSN num Destination subsystem number of messages to be handled by this adapter Valid subsystem number Non zero to handle incoming TCAP SSN 18 Global MAP configuration The following section of the eserv config specifies the global parameters for a MAP connection config disableConcatenatedSegmentPad fals abortMessagesWithZeroLengthTPDA true allowIncoming true allowOutgoing true allowDirectDelivery tru allowIncomingMap3 true allowUserRequestedDeliveryReceipt tru lastSegmentDeliveryReceiptOnly false tcapInterfaceServiceKey 22 originatingTimeout 10 Chapter 3 Configuring Messaging Manager Multigate 69 smscTimeout 8 rimsTimeout 3 mscTimeout 15 rimsInterfaceName rim

What is Messaging Manager?

Contents

Download Pdf Manuals

Related Search

Related Contents