This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Huawei Confidential. No disclosure without permission.
Contents
Contents ............................................................................................................................................. i
Chapter 2 Operation Guide to Message Tracing........................................................................... 3 2.1 Interface signaling trace of R003 and R005 versions.......................................................... 3 2.2 Interface Signaling Trace of R006 version .......................................................................... 6
Chapter 3 Introduction to Internal Message Flow......................................................................... 8
Chapter 4 Local Office Call Message ........................................................................................... 12 4.1 The First Stage: Caller Hooking Off.................................................................................... 12 4.2 The Second Stage: Digit Collecting.................................................................................... 21 4.3 The Third Stage: Number Analysis Before the Call Originated to Callee........................... 23 4.4 The Fourth Stage: Called Terminal Ringing ....................................................................... 27 4.5 The Fifth Stage: Callee Hooking Off and Talking With Caller ............................................ 30 4.6 The Sixth Stage: Callee Hooking On.................................................................................. 33
Chapter 5 Tandem Call Message .................................................................................................. 37 5.1 Caller Sending Setup Message for Call Attempt ................................................................ 37 5.2 CCB Starting Number Analysis After Receiving Setup Message....................................... 44 5.3 CDB Starting Routing After CCB Number Analysis Succeeds........................................... 44 5.4 CDB Returning Routing Result to CCB for Processing ...................................................... 45 5.5 CCB Requesting Caller Gateway Media Information ......................................................... 46 5.6 CCB Sending Setup Message for the Call Attempt to Callee Side .................................... 48 5.7 ISUP Sending IAM Message to PSTN After Receiving Setup Message............................ 52 5.8 Called Terminal Ringing and ACM Message Returned...................................................... 53 5.9 Callee Hooking off and Talking with Caller......................................................................... 53 5.10 Callee/Caller Hooking on and the Call Released ............................................................. 54
Chapter 6 Intelligent Call Message............................................................................................... 55 6.1 Relevant Modules ............................................................................................................... 55 6.2 Intelligent Call Flow............................................................................................................. 55 6.3 First Stage: Triggering Intelligent Service........................................................................... 58 6.4 The Second Stage: Interaction Process with the Subscriber--Playing Announcements and Collecting Digits ........................................................................................................................ 66 6.5 The Third Stage: Connecting.............................................................................................. 79 6.6 The Fourth Stage: Callee Answering the Call .................................................................... 87 6.7 The Fifth Stage: Callee Hooking On................................................................................... 89
Huawei Confidential. No disclosure without permission.
Keyword:
SoftX3000, internal message tracing, basic call flow, local office call message, intelligent call message, tandem call message, Interface signaling trace
Summary:
The document <SoftX3000 internal message tracing guide> include Operation Guide to Message Tracing, Internal message flow Introduce, Local office call message Guide, Tandem call message Guide and Intelligent call message Guide.
Abbreviation list:
MGCP: It is the protocol side of the SoftX3000, responsible for the MGCP message interaction with the gateway.
MGRA: It is used to shield the service side and protocol side. For the service side, it shields the difference of different protocols and focuses on only the service flow.
ESL: It is the common subscriber side, responsible for IAD and AG access.
SM: Subscriber module
CC: Call control module.
CR: Call reference
PID: Internal Software module ID
MID: Internal Hardware module ID, for example: MID = 22 is 22 module FCCU.
IE: Information Element
CRO: It is responsible for implementing the functions such as playing announcement, collecting digit, and conference resources.
BCSM: It is the interface module for the intelligent service and CC. It is responsible for the calling and called number analysis on the intelligent network side, charging of the intelligent call, call monitoring, and beep tone.
FDPP: It is a module responsible for checking the intelligent services and processing each DP point.
INSM: It is the control module of intelligent services.
FEAM: It is the codec module for message conversion between the SSP and SCP.
FSRM: It is the module for intelligent announcement playing.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 3 of 95
Chapter 1
1) 2)
3)
Chapter 2
2.1
Overview
Internal tracing message is “inter module” message of <Interface signaling trace> (under <User trace task>). “Inter module” message is very important for trouble shooting such as call failure, charging mistake etc. Generally, when you trace “Inter module” message for trouble shooting, you need trace other messages (For example: SIP/H323/MGCP/H248/TCAP/Bill).
The document <SoftX3000 internal message tracing guide> include six chapter such as ”overview”, “Operation Guide to Message Tracing”, “Internal message flow Introduce”, “Local office call message Guide”, “Tandem call message Guide” and “Intelligent call message Guide”.
Notes for using the guide:
If you are familiar with “inter module” trace, skip the chapter 2. The trace messages attached are base on version SoftX3000V300R003B01D039. Please view the messages with Trace viewer tools of SoftX3000V300R003B01D039. The guide is base on SoftX3000 V300R003 and V300R005. The internal messages of V300R006 are some different from V300R003 and V300R005.
Operation Guide to Message Tracing
Interface signaling trace of R003 and R005 versions
2006-09-19 Huawei Confidential. No disclosure without permission. Page 4 of 95
3) Click Interface Signaling Trace.
4) Enter the number of the subscriber in the field Subscriber number. Enter the local DN set in the field Local DN set.
For the subscriber in the local office of the SoftX3000, enter the calling or called number in the field Subscriber number. Enter the local DN set of the caller or callee in the field Local DN set.
For the message tracing of incoming trunk, the number to be entered is the calling number in the IAM message. The value of Local DN set is 65534.
5) Press Ctrl+Shift+F12 at the same time. The Inter Module dialog box appears. Click the box. The Password dialog box appears.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 7 of 95
2) Press Ctrl+Shift+F12 at the same time. The Password dialog box appears. Input password “huaweiadmin” for version R006B01, Input “lmtadmin” for
R006B02. Click OK.
3)Double-click Interface Signaling Trace
4) Enter the number of the subscriber in the field Subscriber number. Enter the local DN set in the field Local DN set.
For the subscriber in the local office of the SoftX3000, enter the calling or called number in the field Subscriber number. Enter the local DN set of the caller or callee in the field Local DN set.
For the message tracing of incoming trunk, the number to be entered is the calling number in the IAM message. The value of Local DN set is 65534.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 8 of 95
Chapter 3
Select “Inter Module” trace internal message. If you need trace other messages, please select other message such as ISUP,H248,SIP and INAP.
5) click OK, begin the trace.
Introduction to Internal Message Flow
This chapter introduces the sequence and function of internal message interaction. The following figure shows the message flow of a common ESL subscriber calling a PSTN subscriber.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 10 of 95
1)
2)
3)
4)
5)
6)
7)
8)
9)
10)
ESL_FCCB_SETUP: The caller hooks off. The subscriber side detects that the caller hooks off, and finds the corresponding subscriber according to the port number contained in the H248/MGCP message and equipment number. After verification, the subscriber side sends a Setup message to the call processing module. The message contains the caller properties such as the calling number, incoming and outgoing call authority, discrimination group number, charging source code, and call source.
Note: When the ESL subscriber hooks off, the event is reported; therefore, the setup message does not contain the called number. The called number will be reported through the subsequent Information message. However, for the SIP and H323 subscribers, the called number is contained in the setup message. FCCB_CR_SETUP_ACK: Upon receiving the setup message, the call processing module determines whether the called number exists. If yes, the module starts the call number analysis. If not, the module waits for the digit collecting and sends FCCB_CR_SETUP_ACK to the subscriber side, indicating that the call attempt is accepted. ESL_FCCB_INFORMATION: When receiving the dialing event reported by the gateway, the subscriber side sends the called number to the call processing module. Each time when the FCCB receives an information message, it starts the called number analysis and query whether the available called number exists in the prefix table. FCCB_CDB_OFC_HUNT: When the call processing module successfully queries the prefix analysis table based on the called number, it determines the minimum and maximum number length in the prefix table and decides whether to locate the callee. If the length of the called number meets the requirement, the module starts the callee location and sends the local DN set and called number to the CDB for routing query. CDB_FCCB_OFC_HUNT: If the routing query is successful, the CDB returns the office direction, circuit number, and trunk group number to the call processing module. FCCB_CR_MGW_INFO: After finding that the routing is successful, the call processing module requests the calling media information from the caller. ESL_FCCB_BEARINFO: The caller side returns the caller's routine information to the call processing module. FCCB_CR_SETUP: The call processing module originates a call attempt to the callee side. The call contains the caller media, calling number, called number, circuit number, trunk group number, and called FCCU module number. SETUP_ACKNOWLEDGE: Upon receiving the setup message, the called ISUP module sends a setupack message to the call processing module first, and then sends an IAM message to the office of the callee. Alerting: When the callee's terminal is ringing, the office of the callee sends an ACM message to theSoftX3000. The ISUP module converts the ACM message
2006-09-19 Huawei Confidential. No disclosure without permission. Page 11 of 95
11)
12)
to an internal Alerting message and sends it to the call processing module. The module transmits the Alerting message transparently, requesting the caller side and callee side hear the ring back tone or the caller side play the ring back tone. Connect: When the callee hooks off, the office of the callee sends an ANM message to theSoftX3000. The ISUP module converts the ANM message to an internal Connect message and sends it to the call processing module. The module transmits the Connect message transparently, requesting the caller side and callee side to connect with each other and start conversation. Disconnect: When the callee hooks on, the office of the callee sends an REL message to theSoftX3000. The ISUP module converts the REL message to an internal Disconnect message and sends it to the call processing module. Upon receiving the releasing message, the call processing module sends an FCCB_CR_RELEASE_COMPLETE message to the callee side to confirm the call releasing, and sends an FCCB_CR_RELEASE message to the caller side for releasing the caller.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 13 of 95
The fourth message: offhook message reported by the gateway (sent from the MGRA side to the subscriber side)
The fifth message: response message to the offhook message (It is sent form the SoftX3000 to the gateway. Here it is sent from the MGRA to the protocol side.)
The sixth message: Setup message
1)
Sendermid: The number of the module that sends the message. Here it is module 22.
Senderpid: The number of the module that sends the message. Here it is module ESL.
receivermid: The number of the module that receives the message. Here it is module 22.
receiverpid: The number of the module that receives the message. Here it is module CC.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 15 of 95
Gsvn: It is the call properties, including intra-office, local, local toll, national toll, and international toll. For a local office call, the property of the call is configured in the prefix (ADD CNACLD). The call is originated just now, so the number analysis is not available and here it is GSVN-UNKNOWN.
Calling-party-cat: It is the caller type, usually used on the trunk side. The value ranges from 0x00 to 0xED.
Have-SupDontDis: It shows whether the subscriber registered the super Do-Not-Disturb service. Value = 1 is “True”, Value = 0 is “False”.
Caller-is-virtual-pbx-user: It shows whether the caller is a virtual PBX subscriber. This flag is used in simultaneous ringing service and RBT service in simultaneous ringing mode. Value = 1 is “True”, Value = 0 is “False”.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 21 of 95
Et-address-info: It is the calling address information, for describing the internally defined address property of the caller and callee. You can ignore the parameter.
Et-trace-handle: It is the tracing handle. You can ignore the parameter.
Et-caller-mgw-id: It is the caller gateway index. It can be queried through LST MGW.
The seventh message: response message of Setup message
4.2 The Second Stage: Digit Collecting
1) Determine the digit collecting rule (from the ESL subscriber side to the MGRA side).
2006-09-19 Huawei Confidential. No disclosure without permission. Page 28 of 95
Et-source-code: It is the source information on the callee side. For the explanation of each flag, refer to the explanation of the setup message used to originate the call.
Et-address-info: It is the address information on the callee side.
2) Send a request to the gateway of the callee to establish a connection.
3) Transmit the tracing handle.
4) The gateway responds to the request to establish a connection.
5) Request the called terminal to ring.
6) Inform the caller to hear the ring back tone (ESL- CC).
2006-09-19 Huawei Confidential. No disclosure without permission. Page 35 of 95
In this call, the CC sends a release message to the subscriber side first. After releasing the resources, the subscriber side sends a release complete message to the CC. In this way, the call is released in the service layer.
5) After releasing the resources, the subscriber side informs the CC that the releasing is completed.
6) The ESL informs the gateway and sends busy tone to the caller.
7) Delete the connection and restart the endpoint.
8) The caller hooks on. The endpoint is restarted.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 38 of 95
Et-forward-call-indication: It corresponds to the Forward-Call-Indicator in the ISUP message, for describing the relevant information of the forward office.
Isup-pre-indicator,isup-indicator: It determines whether to set the ISUP prior or mandatory. In the case of incoming ISUP, outgoing SIP and H323, theSoftX3000determines whether to choose outgoing SIP and H323 according to the content of the two IEs.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 39 of 95
Caller-type: It specifies the type of the caller. Generally, it is UC_COMMON, UC_OPERATOR, UC_DATA, or UC_PRIOR. For the incoming call of caller UC_PRIOR or UC_OPERATOR, the processing of the incoming call authority and supplementary services (operator break-in and operator barring) is different from that of the call made by a common subscriber.
Gsvn: It specifies the type of the call. The commonly used types are: GSVN_LOCAL (local call), GSVN_DDD (national call), GSVN_IDD (international call), and GSVN_UNKNOWN. If the caller is a trunk subscriber, theSoftX3000determines the type of the call through the GSVN sent from the caller trunk and decides whether to perform the operations such as adding the area code according to the call type. If the call is originated by a local office subscriber and the default value of gsvn is GSVN_UNKNOWN, theSoftX3000determines the calling number and charging number adjustment according to the call type specified in ADD CNACLD.
et-address-info:
Bsn: It specifies the circuit number occupied on the caller trunk side. It corresponds to the internal logical circuit number specified in the MML command ADD N7TKC.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 40 of 95
Did: The did-isup shows that the caller trunk type is ISUP trunk.
Ofc: It specifies the number of office direction that originated the call, that is, the office direction number of the caller.
Opc: It specifies the signaling point code of the calling office direction.
Through the caller module number and the BSN in the et-address-info described in the above section, you can determines the physical timeslot, office direction number and trunk group number of the ISUP incoming call.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 41 of 95
Call-source-code: It specifies the call source number of the caller or trunk.
dNSetID: It specifies the local DN set of the caller or trunk group.
Centrex-group: It specifies the Centrex group number of the caller. For common subscribers, it is 65535.
user-type: It specifies the type of the subscriber. If it is UC_PRIOR or UC_OPERATOR, the subscriber will be treated as an operator. Therefore, the incoming call authority and break-in authority of the subscriber are affected.
interoffice Out: It indicates the outgoing call authority of the caller to make a local office call.
local Out: It indicates the outgoing call authority of the caller to make a local call.
national Out: It indicates the outgoing call authority of the caller to make a national call.
international Out: It indicates the outgoing call authority of the caller to make an international call.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 42 of 95
…………………
local In: It indicates the local incoming call authority of the caller.
Centrex-flag: If the caller is a subscriber in the Centrex group, the value is 1. If not, the value is 0.
bill-claim: It decides whether the caller generates the application bill (configured in ADD VSBR).
bill-type: It specifies the charging method for the caller. It is specified in the Charging Category of ADD VSBR.
owned-user: It is a flag that shows whether the caller is a defaulting subscriber. If yes, the value is 1.
mct-user: It shows whether the caller registers the MCT service. If yes, the value is 1.
judge-cli-and-addrinfo-matching: It decides whether to perform the caller discrimination and specifies the caller discrimination type. The type is specified in the caller address discrimination in ADD Callsrc. Value 0 means not to perform the caller discrimination.
AOCE-flag: It shows whether the caller registered the supplementary service: advice of charge at end of call.
AOCD-flag: It shows whether the caller registered the supplementary service: advice of charge at during of call
AOCS-flag: It shows whether the caller registered the supplementary service: advice of charge at start of call
Bill-group: It specifies the charging source code of the caller. It maps the caller charge source code in ADD VSBR.
Group-no: It specifies the number of the trunk group to which the caller belongs. For common subscribers, it is 65535.
Distinguish Group: It specifies the number of the caller discrimination group. It has been abandoned.
userGrp: It specifies the number of the call barring group for the caller. It is used for the call barring functions such as black and white lists and the ADD CLDGRP command.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 43 of 95
Type-of-number: It specifies the type of the number, including subscriber number, national number, and international number.
Presentation-id: It specifies whether to display the calling number. PI = 0 means to display the calling number. PI = 1 stands for the calling line identification restriction.
Number-length: It specifies the length of the number.
Complete: It is a flag that decides whether to display the number completely. If yes, the displaying of the calling number will be influenced, and the starting of the called number analysis will be influenced.
Number: It specifies the actual number.
CALLER-MGW-ID:
Mgw-index: It specifies the caller gateway index. After running LST MGW, you can query it based on Global MGW INDEX.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 44 of 95
5.2 CCB Starting Number Analysis After Receiving Setup Message
As described in chapter 1, the setup message contains the called number. When the CCB starts the re-analysis, the FCCB_FCCB_INFORMATION (an empty information message that stands for the re-analysis) is generated. Then the CCB sends a Setup_Ack message to the caller ISUP side. The called number is sent completely, so the CCB performs the number analysis successfully. Then the CCB sends a Call_Proceeding message to the ISUP, indicating that the callee is to be connected.
5.3 CDB Starting Routing After CCB Number Analysis Succeeds
FCCB-CDB-OFC-HUNT: When the number analysis is successful, the CCB sends the routeNo and caller gateway ID, and prior gateway flag to the CDB, requesting for routing.
route No: It specifies number of the route selected according to the route selection code and route selection source code after the called number analysis.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 45 of 95
opc: It specifies the signaling point code of the office direction of the caller.
CircuitTypeInd: It specifies the type of the trunk that can be selected. For example, sipInd:0x0 means that the SIP trunk cannot be selected.
Ccb-caller-Mgw: It specifies the caller gateway index. It is mainly used to inform the CDB the caller gateway index when selecting the gateway.
IncomingNi: It is the flag that decides whether to select the gateway. If yes, the value is 1.
5.4 CDB Returning Routing Result to CCB for Processing
CDB-FCCB-OFC-HUNT: The CDB queries the table corresponding to ADD RT based on the route number sent from the CCB. The CDB selects the sub-route, trunk group, and circuit number, and then returns the key information to the CCB.
return Code: It is the flag that shows whether the routing is successful. If yes, the value is 0. The other values mean that the routing fails.
group No: It specifies the number of the trunk group to which the trunk circuit belongs.
office No: It specifies the number of the office direction to which the trunk circuit belongs.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 46 of 95
module No: It specifies the number of the FCCU module to which the trunk circuit belongs.
circuit No: It specifies the number of the selected trunk circuit. It is the logical number of the internal circuit in ADD N7TKC.
did: It specifies the type of the trunk circuit.
subrouteNo: It specifies the number of the selected sub-route.
callerMgw: It specifies the caller gateway index.
calledMgw: It specifies the called gateway index.
5.5 CCB Requesting Caller Gateway Media Information
When the routing is successful, the CCB requests caller gateway media information from the caller. The ISUP delivers a SMMSG_RESERVE_CIRCUIT_REQ message to the gateway, requesting the media information. Then the gateway sends a SMMSG_RESERVE_CIRCUIT_RSP message to feedback the media information of the gateway.
During media information requesting, the requesting failure often results in failure of the call; therefore, you must check whether the media information requesting is successful.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 47 of 95
Trm-id: Trm-id is termination id. In the internal data, termination id is expressed in eight bytes. The first four bytes are used to indicate the tdm endpoint or the rtp endpoint. If the first four bytes is 0x00000000, it indicates the tdm endpoint.
If UMG serves as the gateway, the SoftX3000 will convert termination id of the start circuit to a hexadecimal number and add 0x40000000 when it adds the NO.7 circuit. Trm-id=0x0000000040000301and last four bytes is 0x40000301. Subtract 0x40000000 from 0x40000301. The result is 0x301. Convert 0x301 to a decimal number, that is, 769. This 769 is the number added through ADD N7TKC.
If the gateway is not UMG, convert Trm-id to the decimal number directly.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 48 of 95
Tdm-ret-code:
Rtp-ret-code: If the value of the three parameters is emgra-success (0), it indicates that the application for the caller media is successful.
5.6 CCB Sending Setup Message for the Call Attempt to Callee Side
Upon receiving the caller media information, the CCB originates a call attempt by sending a Setup message to the called ISUP module based on the routing result.
Et-address-info:
Receivermid: It specifies the number of the FCCU module on which the called trunk circuit is located.
Bsn: It specifies the number of the called trunk circuit. Based on the FCCU module number and bsn, you can determine the unique physical timeslot (ADD N7TKC).
Call-type: The ct-tandem stands for the tandem call.
Et-source-code:
The sourcecode in the setup message sent to the callee is the relevant property of the caller.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 50 of 95
Call-source-code: It specifies the call source number of the caller or trunk.
dNSetID: It specifies the local DN set of the caller or trunk group.
Centrex-group: It specifies the Centrex group number of the caller. For common subscribers, it is 65535.
user-type: It specifies the type of the subscriber. If it is UC_PRIOR or UC_OPERATOR, the subscriber will be treated as an operator. Therefore, the incoming call authority and break-in authority of the subscriber are affected.
interoffice Out: It indicates the outgoing call authority of the caller to make a local office call.
local Out: It indicates the outgoing call authority of the caller to make a local call.
national Out: It indicates the outgoing call authority of the caller to make a national call.
international Out: It indicates the outgoing call authority of the caller to make an international call.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 51 of 95
…………………
local In: It indicates the local incoming call authority of the caller.
Centrex-flag: If the caller is a subscriber in the Centrex group, the value is 1. If not, the value is 0.
bill-claim: It decides whether the caller generates the application bill (configured in ADD VSBR).
bill-type: It specifies the charging method for the caller. It is specified in the Charging Category of ADD VSBR.
owned-user: It is a flag that shows whether the caller is a defaulting subscriber. If yes, the value is 1.
mct-user: It shows whether the caller registers the MCT service. If yes, the value is 1.
judge-cli-and-addrinfo-matching: It decides whether to perform the caller discrimination and specifies the caller discrimination type. The type is specified in the caller address discrimination in ADD Callsrc. Value 0 means not to perform the caller discrimination.
AOCE-flag: It shows whether the caller registered the supplementary service: advice of charge at end of call.
AOCD-flag: It shows whether the caller registered the supplementary service: advice of charge at during of call
AOCS-flag: It shows whether the caller registered the supplementary service: advice of charge at start of call
Bill-group: It specifies the charging source code of the caller. It maps the caller charge source code in ADD VSBR.
Group-no: It specifies the number of the trunk group to which the caller belongs. For common subscribers, it is 65535.
Distinguish Group: It specifies the number of the caller discrimination group. It has been abandoned.
userGrp: It specifies the number of the call barring group for the caller. It is used for the call barring functions such as black and white lists and the ADD CLDGRP command.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 52 of 95
Mgw-index: It is the number of the called gateway.
Establish-indication: It shows whether the call is a hairpin call. When Establish-indication = ei-create-one-termination-2T(1) ,the call is a non-hairpin call. When Establish-indication = ei-create-one-termination-1T(0), the call is a hairpin call.
5.7 ISUP Sending IAM Message to PSTN After Receiving Setup Message
Upon receiving the setup message, the ISUP module requests the called gateway for media information and then transmits it transparently to the caller through the CCB. At the same time, when the gateway media information requesting is successful, the ISUP module sends an IAM message to the called office.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 53 of 95
5.8 Called Terminal Ringing and ACM Message Returned
After the called terminal rings, the called office returns an ACM message. The ISUP converts the ACM message to an Alerting message that indicates whether the peer office plays announcements.
Et-progress-indicator:
Description: It indicates whether the peer office plays announcements. If description = inband-info-or-appropriate-pattern-now-availabel(8), it indicates that the peer office plays announcements.
5.9 Callee Hooking off and Talking with Caller
When the callee hooks off, the called office returns an ANM message. The ISUP converts the message to an internal Connect message and sends it to the CCB. The CCB transmits the message transparently to the caller. When the caller returns the Connect_ACK message, the call is establisned. The callee begins to talk with the caller.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 54 of 95
5.10 Callee/Caller Hooking on and the Call Released
When the callee hooks on, the called office returns the REL message. The ISUP converts the message to an internal Release message and sends it to the CCB. The CCB transmits it transparently to the caller to release the call.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 55 of 95
Chapter 6
6.1
6.2
Intelligent Call Message
Relevant Modules
MGCP: It is the protocol side of the SoftX3000, responsible for the MGCP message interaction with the gateway.
MGRA: It is used to shield the service side and protocol side. For the service side, it shields the difference of different protocols and focuses on only the service flow.
CRO: It is responsible for implementing the functions such as playing announcement, collecting digit, and conference resources.
ESL: It is the common subscriber side, responsible for IAD and AG access.
CC: It is the call control module.
BCSM: It is the interface module for the intelligent service and CC. It is responsible for the calling and called number analysis on the intelligent network side, charging of the intelligent call, call monitoring, and beep tone.
FDPP: It is a module responsible for checking the intelligent services and processing each DP point.
INSM: It is the control module of intelligent services.
FEAM: It is the codec module for message conversion between the SSP and SCP.
FSRM: It is the module for intelligent announcement playing.
Intelligent Call Flow
Internal Message and TCAP message tracing attachments as follow:
2006-09-19 Huawei Confidential. No disclosure without permission. Page 58 of 95
6.3 First Stage: Triggering Intelligent Service
1) The first message: CCB_BCSM_MetDP3.
It is the message of triggering the intelligent DP. When the intelligent service is triggered, this message is generated. The message may be on DP3, DP4, or DP5.
Message content:
Sendermid: The number of the module that sends the message. Here it is module 22.
Senderpid: The number of the functional module that sends the message. Here it is module CC.
receivermid: The number of the module that receives the message. Here it is module 22.
receiverpid: The number of the functional module that receives the message. Here it is module BCSM.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 60 of 95
Message_type: The message type is DP message.
servicekey: It specifies the type of the intelligent service. Each intelligent service has a unique identification that can be queried in the higher-level module. Here it is meaningless and the value is 0.
calledPartyNumber:
callingLineID:
Currently the message explanation is as follows:
Two-byte The following two bytes respectively specifies that:
oe_flag (occupy 1 bit): odd/even indicator
0 even
1 odd
addr_inf_id (occupy 7 bit): address property of number
2006-09-19 Huawei Confidential. No disclosure without permission. Page 66 of 95
6.4 The Second Stage: Interaction Process with the Subscriber--Playing Announcements and Collecting Digits
Upon receiving the message reported by the SSP to initiate the DP, the SCP determines the type of the intelligent service according to the IDP message and whether the relevant information for the implementation of the service is sufficient. If the requirements are met, the SCP delivers the playing announcements and collecting digits message to complete the subsequent operations.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 69 of 95
connectToResource: connect to resource
Currently the SCP delivers empty messages to us. The messages are not to be processed on the SoftX3000 side.
3) The third message: TC_CONTINUE (PromptAndCollectUserInformation)
collectedDigits: It is the collected information.
minimumNbOfDigits: It specifies the minimum number of digits.
maximumNbOfDigits : It specifies the maximum number of digits.
//From the minimum and maximum numbers of digits, you can finds out the scope of the quantity of numbers for playing announcements and collecting digits.
endOfReplyDigit : It is the end of reply digit.
cancelDigit : It is the cancelled digit.
startDigit : It is the start digit.
firstDigitTimeOut : It is the first-digit timeout.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 71 of 95
elementaryMessageID: It is the ID of the basic message. It is used to identify the voice ID to be played according to the instruction of the SCP.
numberOfRepetitions: It specifies the number of repetitions. It is used to identify the times that the voice is to be played.
duration: It specifies the duration. It is used to identify the time for playing the announcement.
Interval: It specifies the time interval. If the number of repetitions is not 0, the parameter is valid and is used to identify the interval between n times of playing announcement.
4) The fourth message: INSM_FSRM_PromptCollect.
It is the message for playing announcements and collecting digits.
It is used to convert the third message (34th line) to inter-module message for transmission. The content is the same as that of the third message(34th line).
5) The fifth message: SM_CRO_PA.
It is the message to request the CRO module to play announcements.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 72 of 95
party-info: It is the type of the subscriber.
For SoftX3000, it is set to FIXEDUSER.
address: It is the address information of the caller.
enAddrType: It is the address type.
0x00: IP
0x01: ATM
ipAddr: It is the IP address of the calling MGW.
port: It is the port number allocated by the calling MGW for playing announcement. When the caller is connected to the equipment for playing announcement, the caller uses this port to transmit media stream.
codecList: It is the codec list.
ucCount: It is the number of the codec types that can be carried.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 74 of 95
0x01: Timeout tone (The tone ends after the playing announcement is completed.)
0x02: Switch tone (The tone will not end until the playing announcement is completed. The stop tone must be displayed.)
Note: The two fields are only used in mobile services. In fixed network, the CRO does not process the fields.
cycle-num: It specifies the times of the playing announcement (PA) that includes the variable tone. 0 or all-F means that the playing goes on constantly in cycle.
interval-time: It specifies the time interval between two PAs that includes the variable tone. There is no interval between variable tones. The unit is millisecond.
dtmf-info: It specifies the digit figure for collecting digits.
0xd0: It specifies the Tag value of the dtmf.
0x07: It specifies the length of the dtmf digit figure.
0x28: “(”
0x78: “X”
0x7c: “|”
0x2e: “.”
0x54: “T”
0x29: “)”
The digit figure used to instruct the delivery of the RQNT is obtained when the above parameters are combined.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 78 of 95
13) The thirteenth message(82-84th lines): SSP delivering instruction of stopping collecting digits to PA equipment
14) The fourteenth message(85-87th lines): PA equipment responding to the instruction of stopping collecting digits
15) The fifteenth message(69-72th lines): SSP reporting collected digits to SCP
16) The sixteenth message: SCP delivering messages to continue playing announcements and collecting digits
The messages numbered from 73 to 129 are messages for repeating playing announcements and collecting digits. The message explanations are not listed here.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 80 of 95
chargeMode: It specifies the charging mode. It is used to indicate whether the call is to be charged.
0x00: free
0x01: to be charged
chargeRecordIdentifier: It is the identifier for the charging record. It is used to identify the charging action. It is delivered in sequence among multiple charging applications.
chargeAction: It specifies the charging action.
0x01: It means to generate the charging record related to the network.
0x02: It means to generate the charging record related to the service.
0x03: It means to change the charging.
0x04: It means to pause the charging.
0x05: It means to restart the charging.
0x06: It means to stop the charging.
callPartToBeCharged: It specifies the call part to be charged.
0x01: from caller to SSP
0x02: from SSP to callee
0x03: from caller to callee (adopted in normal cases)
2006-09-19 Huawei Confidential. No disclosure without permission. Page 81 of 95
chargeRecordTreatment: It specifies the treatment to the charging record.
Bit 1 decides the charging related to the network.
Bit 2 decides the charging related to the service.
Bit 3 generates the charging information related to the network.
Bit 4 generates the charging information related to the service.
Bit 5 generates the charging information related to the storage and network.
Bit 6 generates the charging information related to the storage and service.
Bit 7 is used to request the SSP to send the charging record after the call is released.
Bit 8 is idle.
callingPartyNumber: It specifies the calling number.
calledPartyNumber : It specifies the called number.
The above two parameters are optional. They record the calling and called numbers of the intelligent call bill to be generated on the SoftX3000. If the SCP does not deliver the two parameters, the value of callingPartyNumber will be the content of CCB_caller_num, and the value of calledPartyNumber will be the content of CCB_dial_num, when the intelligent call bill is generated on the SoftX3000.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 82 of 95
translatedPartyNumber: It specifies the number of the destination address.
This parameter is used to record the finally connected called number in the intelligent call bill. If the SCP does not deliver the parameter, the value is the logical number. If there is no logical number, the value is the physical number.
locationNumber: It specifies the location number.
This parameter is used to transfer the geographical location information of the calling mobile subscriber. It is not used in fixed network.
surcharge: It specifies the surcharge.
surchargeValue: It is the value of the surcharge type. It ranges from 0 to 32767. For RMB, the unit is fen.
surchargeType: It is the type of the surcharge value. There are two types: fee and rate. If it is rate, the value must be consistent with the time unit specified by the charging type parameter. When the time unit for rate in charging class is one minute, the time unit of surcharge rate must be one minute; when the time unit for rate in charging class is three minute, the time unit of surcharge rate must be three minute.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 83 of 95
chargeClass: It specifies the class of the charging.
There are 1000 charging classes in total. The charging class is determined by the SCP according to the calling and called number, location number, and bearer capability. The information such as rate, segment rate, and rate unit is hidden in the charging class information. It corresponds to the command ADD CHGCLS on the SoftX3000 side.
chargeRateModulator: It specifies the rate for charging modulating.
chargeRateModulatorValue: It specifies the value of the charging modulating rate.
chargeModulatorType: There are three types of charging modulating rate: modulating to the rate, modulating to the total fee, rate table index.
startChargePattern: It specifies the pattern to start the charging.
0x01: start charging immediately
0x02: start charging after receiving response signal
0x03: start charging according to the duration of the ringing
stopChargingPattern: It specifies the pattern to stop the charging.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 84 of 95
0x03: stop charging when caller or callee hooks on
detailedBillingChargeRecordType: It specifies the type of the detailed bill record.
This parameter determines the charging type of detailed bills used by the SSP to store the charging information. There are 32 types in total.
sendingOfChargeMessage: It determines whether to send the charging information.
If the value is 1, it indicates that the detailed bill is to be sent to the billing center after the call is completed. If the value is 2, it is not necessary to send the detailed bill to the billing center.
callSupervision: It specifies the call supervision.
supervisionMethod: It specifies the method of supervision.
There are two kinds of methods: supervision fee and supervision time.
timeBeforeLimit: It specifies the warning time before limit.
warningIndicator: It specifies the warning indicator. It is the record notification to be sent.
id_forceReleaseCause: It specifies the cause of the forced release.
heartbeatTime: It is the interval of the reports (unit: second). It is the interval of intelligent call bills.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 85 of 95
sendCalculationToSCPIndication: It means to send the result to the SCP.
This parameter determines whether to expect the SSP to send application for charging report to the SCP when the charging processing is completed.
partyToCharge: It is the subscriber to be charged.
This parameter determines to perform application for charging operation on which party of the call. If the parameter is not provided, party A will be charged.
2) The second message: TC_CONTINUE. The SCP delivers request report of BCSM event to the SSP.
This message is explained in the above section. For a call, the supervision is usually performed on the DP4, DP5, DP6, DP7, DP9a, DP9b, and DP10.
3) The third message: TC_CONTINUE. The SCP delivers connection instruction to the SSP.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 86 of 95
destinationRoutingAddress: It specifies the routing address of the destination.
This parameter includes a series of called numbers to which the call will be connected.
extenField: It specifies the extended number.
When the call is with the colorful ring back tone service and simultaneous ringing service, this value is the number of the colorful ring back tone service and simultaneous ringing service.
4) The fourth message: FDPP_BCSM_SetBCSMNoAnswerTimer
Note: This message is included in the RRBE message. It is not a command separately sent by the SCP.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 87 of 95
fdpp-setNoAnswerTimer: It is used to set the timer duration when the callee does not answer the call.
timeValue: It specifies the duration of the timer.
6.6 The Fourth Stage: Callee Answering the Call
The messages numbered from 141 to 174 show the process of the CC locating the called number. Refer to the above section for the detailed message explanations.
1) The first message: CCB_BCSM_MetDP7.
The CC reports the metdp7 indicating that the callee answers the call.
2) The second message: FDPP_INSM_EventReportBCSM.
The CC reports the metdp7 indicating that the callee answers the call.
This operation is to inform the SCP an event related to the call. This event is requested in the requesting inform of BCSM event operation by the SCP.
fdpp-eventreportbcsm: It specifies the BCSM event report.
2006-09-19 Huawei Confidential. No disclosure without permission. Page 92 of 95
It means to send the GOTOPIC1 message to the BCSM module.
fdpp-gotoPic1-msg: The FDPP module converts the release message sent from the INSM module to the gotopic1 message and sends it to the BCSM module. Then the BCSM module informs the CC to process the message according to the cause.
ReleaseCause: It specifies the cause of the release.
7) The seventh message: CCB_BCSM_NormalCallClear.
The CC sends response to the releasing of the call to the BCSM module. The call is completed.