You are here: CSP Developer’s Guide: Common Channel Signaling > 2 Introduction to SS7 > MTP3-to-Host Example
ISUP Call Flow
The following example illustrates the message flow from an ISUP call where both stacks are configured for remote ISUP. This call flow include the call establishment and release. Each step in the call flow is described following the two figures.
Call Flow Steps
The following steps break down the call flow. The OPCs of the stacks are as follows:
• Stack 0: OPC is 0-0-3
• Stack 1: OPC is 0-0-6
1. The host sends the Transfer Request (0x0A) for IAM to the Matrix Controller for Component MTP3 HMRT (0x002C).
H->X
00 44 00 44 00 28 04 00 01 08 01 01 00 2c 00 0a 01 03 00 2b 00 30 04 25 00 0c 00 00 00 03 00 00 00 06 05 00 02 00 04 26 00 1c 01 01 01 00 20 00 0a 00 02 09 07 03 10 05 88 26 53 00 0a 07 03 11 05 88 26 03 00 00
Refer to Transfer Request for IAM - Message Breakdown for an explanation of this message.
2. The MTP3 transmits an IAM on the SS7 link.
3. The MTP3 on Stack 0 receives an IAM and sends a Transfer Indication (0x14) for IAM from component HMDT (0x002B) to the host.
X->H
00 44 00 43 00 25 04 00 01 08 01 00 00 2b 00 14 01 03 00 2b 00 30 04 25 00 0c 00 00 00 03 00 00 00 06 05 00 02 00 04 26 00 1c 01 01 01 00 20 00 0a 00 02 09 07 03 10 05 88 26 53 00 0a 07 03 11 05 88 26 03 00 00
Refer to Transfer Indication for IAM for an explanation of this message.
4. The host sends a Transfer Request (0x0A) for ACM to the matrix for Component MTP3 HMRT (0x002C) on stack 0.
H->X
00 2e 00 44 00 29 04 00 01 08 01 00 00 2c 00 0a 01 03 00 2b 00 1a 04 25 00 0c 00 00 00 06 00 00 00 03 05 00 02 00 04 26 00 06 01 01 06 10 00 00
5. MTP3 transmits ACM on the SS7 link.
6. MTP3 on Stack 1 receives an ACM and sends a transfer indication (0x14) for ACM from component HMDT (0x002B) to the host.
X->H
00 2e 00 43 00 26 04 00 01 08 01 01 00 2b 00 14 01 03 00 2b 00 1a 04 25 00 0c 00 00 00 06 00 00 00 03 05 00 02 00 04 26 00 06 01 01 06 10 00 00
7. The host sends a Transfer Request (0x0A) for ANM to the Matrix for Component MTP3 HMRT (0x002C) on stack 0.
H-X
00 2c 00 44 00 2a 04 00 01 08 01 00 00 2c 00 0a 01 03 00 2b 00 18 04 25 00 0c 00 00 00 06 00 00 00 03 05 00 02 00 04 26 00 04 01 01 09 00
8. MTP3 transmits an ANM on the SS7 link.
9. MTP3 on Stack 1 receives an ANM and sends a Transfer Indication (0x14) for ANM from component HMDT (0x002B) to the host.
X-H
00 2c 00 43 00 27 04 00 01 08 01 01 00 2b 00 14 01 03 00 2b 00 18 04 25 00 0c 00 00 00 06 00 00 00 03 05 00 02 00 04 26 00 04 01 01 09 00
10. The call is established.
Call Release
1. Send transfer request (0x0a) for REL to matrix for Component MTP3 HMRT (0x2c) on stack 1.
H-X
00 2c 00 44 00 00 04 00 01 08 01 01 00 2c 00 0a 01 03 00 2b 00 18 04 25 00 0c 00 00 00 03 00 00 00 06 05 00 02 00 04 26 00 04 01 01 12 00
2. MTP3 on Stack 0 receives REL and sends a transfer indication (0x14) for REL from component HMDT (0x2b) to the host.
X-H
00 2c 00 43 00 1a 04 00 01 08 01 00 00 2b 00 14 01 03 00 2b 00 18 04 25 00 0c 00 00 00 03 00 00 00 06 05 00 02 00 04 26 00 04 01 01 12 00
3. Send transfer request (0x0a) for RLC to matrix for Component MTP3 HMRT (0x2c) on stack 0.
H-X
00 2c 00 44 00 00 04 00 01 08 01 00 00 2c 00 0a 01 03 00 2b 00 18 04 25 00 0c 00 00 00 06 00 00 00 03 05 00 02 00 04 26 00 04 01 01 10 00
4. MTP3 on Stack 1 receives RLC and sends a transfer indication (0x14) for RLC from component HMDT (0x002B) to the host.
X-H
00 2c 00 43 00 1b 04 00 01 08 01 01 00 2b 00 14 01 03 00 2b 00 18 04 25 00 0c 00 00 00 06 00 00 00 03 05 00 02 00 04 26 00 04 01 01 10 00
Service Indicator
The Service Indication part of the messages below differs depending on the protocol as follows.
• SNM - 0
• SNM_MAINT - 1
• SCCP - 3
• TUP - 4
• ISUP - 5
• DUP_CIRC - 6
• DUP_REG - 7
Transfer Request for IAM - Message Breakdown
00 44 'length
00 44 'message type
00 28 'seq
04 'node id
00 01 08 01 01 'stack aib
00 2c 00 0a 'mtp transfer request S
01 'number of icbs
03 'icb type - extended
00 2b 'icb subtype - raw_msu_data
00 30 'length
04 25 'parameter name
00 0c 'length
00 00 00 03 'dpc
00 00 00 06 'opc
05 ‘service indicator
00 ‘message priority
02 ‘network indicator
00 ‘signaling link set
04 26 'parameter name
00 1c 'length
01 01 ‘CIC number 0x01 01
01 'msg id (IAM)
00 ‘MF parameter 1 – Nature of Connection
20 00 ‘MF parameter 2 – Fwd Call Indicator
0a ‘MF parameter 3 – Calling Party’s Category
00 ‘MF parameter 4 – Trans Medium Requirement
02 ‘pointer to MV parameter
09 ‘pointer to optional parameter
07 ‘length of MV parameter
03 10 05 88 26 53 00
‘MV parameter – Called Party Number
0a ‘opt. param. 1 name – Calling party number
07 ‘optional parameter 1 length
03 11 05 88 26 03 00
’optional parameter 1 value
00 ‘end of optional parameters.
00 44 'msg length
00 43 'msg type
00 25 'seq
04 'node id
00 01 08 01 00 'stack aib
00 2b 00 14 'transfer indication
01 'number of icbs
03 'icb type - extended
00 2b 'icb subtype - raw_msu_data
00 30 'length
04 25 'parameter name
00 0c 'length
00 00 00 03 'dpc
00 00 00 06 'opc
05 ‘service indicator
00 ‘message priority
02 ‘network indicator
00 ‘signaling link set
04 26 'parameter name
00 1c 'length
01 01 ‘CIC number 0x01 01
01 'msg id
00 ‘MF parameter 1 – Nature of Connection
20 00 ‘MF parameter 2 – Fwd Call Indicator
0a ‘MF parameter 3 – Calling Party’s Category
00 ‘MF parameter 4 – Trans Medium Requirement
02 ‘pointer to MV parameter
09 ‘pointer to optional parameter
07 ‘length of MV parameter
03 10 05 88 26 53 00
‘MV parameter – Called Party Number
0a ‘optional parameter 1 name – Calling party
number
07 ‘optional parameter 1 length
03 11 05 88 26 03 00
‘optional parameter 1 value
00 ‘end of optional parameters.
TCAP Call Flow
The following call flow is for an incoming TCAP call.
API Message
begin:(send ppl req for UDT from stack1)
message:
(00 3b 00 44 00 00 00
00 01 08 01 01
00 2c 00 0a
01 03 00 2b 00 27
04 25 00 0c 00 00 00 01 00 00 00 02 03 00 02 00
04 26
00 13
09 80 03 07 0b 04 43 01 00 82 04 43 02 00 92 03 0a 0b 0c)
response:(00 07 00 44 00 00 00 00 10)
report:
(00 3b 00 43 00 00 00
00 01 08 01 00
00 2b 00 14
01 03
00 2b
00 27
04 25
00 0c
00 00 00 01
00 00 00 02
03 00 02 00
04 26
00 13
09 80 03 07 0b 04 43 01 00 82 04 43 02 00 92
03 0a 0b 0c)
report_wait:(4000)
onfail:(exit)
end:(send ppl req for UDT from stack1)
begin:(send TR.REQ for UDTS from stack0)
message:
(00 3b 00 44 00 00 00
00 01 08 01 00
00 2c
00 0a
01 03
00 2b
00 27
04 25
00 0c
00 00 00 02
00 00 00 01
03 00 02 00
04 26
00 13 0a 80 03 07 0b 04 43 01 00 82 04 43 02 00 92 03 0a 0b 0c)
response:(00 07 00 44 00 00 00 00 10)
report:(00 3b 00 43 00 00 00 00 'tr. ind. for UDTS.
01 08 01 01
00 2b 00 14
01 03 00 2b 00 27
04 25 00 0c 00 00 00 02 00 00 00 01 03 00 02 00
04 26
00 13 0a 80 03 07 0b 04 43 01 00 82 04 43 02 00 92 03 0a 0b 0c)
report_wait:(40000)
onfail:(exit)
end:(send TR.REQ for UDTS from stack0)