Welltech Dialogic SS7 Protocols ISUP Instrukcja Użytkownika Strona 24
- Strona / 203
- Spis treści
- BOOKMARKI
Oceniono. / 5. Na podstawie oceny klientów
Section 6 Interface to Application
24
call_ref is used to identify the circuit or call to which the message refers.
Currently, when 32768 circuits or less are configured, the most significant bit
of the
call_ref is ignored by the ISUP module, and the remaining bits map
directly to the Circuit Identifier
cid so the valid range for call_ref is from 0 to
one less than the number of circuits supported. If more than 32768 circuits
are configured, then the call_ref is identical to the cid.
Note: Earlier revisions of the ISUP module required the most significant bit of the
call_ref to be set in all messages relating to outgoing calls.
6.2.2 Receive Indication
This primitive is used by the ISUP module to send a message to the
application module.
Primitive Indication From ISUP
Field Name Meaning
type ISP_MSG_RX_IND (0x8701)
id call_ref
src ISUP module ID
dst Application module ID
rsp_req 0x00
hclass 0x00
status 0x00
err_info 0x00
len Number of bytes of user data
parameters User data (Len bytes in length)
call_ref is used to identify the circuit or call to which the message refers.
Currently, when 32768 circuits or less are configured and the ISPF_16CID
flag is set to 0, the most significant bit of the
call_ref is set to 1 by the ISUP
module for all messages relating to outgoing calls and the remaining bits map
directly to the Circuit Identifier
cid. If 32768 circuits or less are configured
and the ISPF_16CID flag is set to 1, or if more than 32768 circuits are
configured, then the call_ref is identical to the cid.
Note: Earlier revisions of the ISUP module required the most significant bit of the
call_ref to be set in all messages relating to outgoing calls. To allow for
interworking with earlier application software which make use of this bit the ISUP
module continues to set the bit in all messages relating to outgoing calls for
configurations with 32768 circuits or less, when the ISPF_16CID flag has been set
to 0. It is recommended that existing applications be modified to ignore the
setting of the most significant bit.
- Dialogic 1
- SS7 Protocols 1
- Contents 3
- Figures 6
- Revision History 7
- About this Publication 9
- 1.3 Related Documentation 10
- 1.4 Feature Overview 11
- 2 General Description 13
- Value Mnemonic Meaning 14
- 3 Internal Data Structures 17
- 4.1 System Functions 19
- 4.2 Timer Operation 19
- 5 Interface to MTP 21
- Section 5 Interface to MTP 22
- 6 Interface to Application 23
- 6.2.2 Receive Indication 24
- 6.5.1 Alerting Request 28
- 6.5.6 Confusion Request 32
- 6.5.7 Continuity Request 32
- 6.5.9 Exit Request 33
- 6.5.10 Facility Request 33
- 6.5.11 Facility Response 35
- 6.5.15 Information Request 37
- 6.5.19 Overload Request 40
- 6.5.21 Proceeding request 41
- 6.5.22 Progress Request 42
- 6.5.23 Release Response 43
- 6.5.24 Release Request 44
- 6.5.26 Resume Request 45
- 6.5.27 Segmentation Request 46
- 6.5.28 Setup Request 46
- 6.5.29 Setup Response 49
- 6.5.31 Suspend Request 52
- 6.6.1 Alerting Indication 56
- 6.6.6 Confusion Indication 60
- 6.6.7 Continuity Indication 61
- 6.6.9 Exit Indication 61
- 6.6.10 Facility Indication 62
- 6.6.11 Facility Confirmation 63
- 6.6.19 Overload Indication 68
- 6.6.21 Proceeding Indication 69
- 6.6.22 Progress Indication 70
- 6.6.23 Release Confirmation 71
- 6.6.24 Release Indication 71
- 6.6.26 Resume Indication 73
- 6.6.28 Setup Confirmation 74
- 6.6.29 Setup Indication 76
- 6.6.31 Suspend Indication 79
- 6.7 Parameter Definitions 80
- 6.7.1 Called Party Number 86
- 6.7.2 Calling Party Number 86
- 6.7.3 Cause Indicators 87
- 6.7.4 Custom Parameter 88
- 6.7.5 Message Data 88
- 6.7.7 Tariff Type 89
- 6.7.8 Unrecognised Parameter 90
- 6.8.3 Hop Counter Procedure 94
- 6.8.4 Continuity Testing 95
- Call Set Up 99
- Service 108
- 6.8.6 Message Segmentation 109
- 7 Management Interface 113
- reserved Set to zero 116
- 7.6 Local Overload Request 118
- Parameters 120
- 8 Non-Primitive Interface 121
- 8.3.1 Timer default values 138
- 8.5 Variant Initialisation 141
- operation 142
- message type 142
- 8.8 Read RAM Request 145
- 8.10 Read Circuit Request 146
- 8.11 Read Revision Request 146
- Section 150
- Event specific data 158
- Call states 164
- 8.22 Trace Event Indication 166
- A.1 German ISUP 171
- A.2 UK ISUP 172
- A.3 Japan (TTC) ISUP 173
- A.4 Nortel RLT 174
- A.4.2 Nortel RLT (ITU) 175
- A.5 Italian ISUP 176
- A.6 French ISUP 177
- A.7 China ISUP 178
- A.8 Finnish ISUP 180
- A.9 BICC 180
- Hex Dec Min Max 181
- Reference 181
- ISUP Module 183
- B.2 ITU-T Parameters 184
- B.3 ANSI T1.113 Messages 188
- B.4 ANSI T1.113 Parameters 189
- More Extended Options 195
- Appendix F: Timer Services 199
- F.1 Timer Expiry 200
- Variant Initialisation, 141 203
Powiązane produkty i podręczniki dla Komunikacja Welltech Dialogic SS7 Protocols ISUP
Komunikacja Welltech WG5290 Instrukcja Użytkownika
(149 strony)
(149 strony)
© 2020, manymanuals.pl. Wszelkie prawa zastrzeżone. | 0.045 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Komentarze do niniejszej Instrukcji