TCAP:Receiving transaction and dialogue portions
(initial content) |
m |
||
| Line 1: | Line 1: | ||
| − | The '''transaction data received''' (event) message is used by [[TCAP]] to notify and send received transaction and dialogue portions to TCAP service user. The transaction identifier of a received transaction remains valid until: | + | The '''transaction data received''' (event) message is used by [[TCAP]] to notify and send received transaction and dialogue portions to the TCAP service user. The transaction identifier of a received transaction remains valid until: |
*TCAP receives a message among these types and the last component of the TCAP message: | *TCAP receives a message among these types and the last component of the TCAP message: | ||
| Line 17: | Line 17: | ||
| − | If TCAP detects that the received message is incorrect, it sends an abort indication to TCAP service user. The message type is set to '''provider abort''' in the case of ITU, and '''ANSI provider abort''' in the case of ANSI92 and 96. In the case of ANSI88, the TCAP service user is informed by sending the local reject indication using the '''component received''' message. The '''abort cause''' parameter is used to indicate the cause of abort. | + | If TCAP detects that the received message is incorrect, it sends an abort indication to the TCAP service user. The message type is set to '''provider abort''' in the case of ITU, and '''ANSI provider abort''' in the case of ANSI92 and 96. In the case of ANSI88, the TCAP service user is informed by sending the local reject indication using the '''component received''' message. The '''abort cause''' parameter is used to indicate the cause of abort. |
| Line 35: | Line 35: | ||
*Dialogue parameters | *Dialogue parameters | ||
*User information buffer | *User information buffer | ||
| − | |||
| − | |||
| − | |||
Latest revision as of 14:36, 24 April 2018
The transaction data received (event) message is used by TCAP to notify and send received transaction and dialogue portions to the TCAP service user. The transaction identifier of a received transaction remains valid until:
- TCAP receives a message among these types and the last component of the TCAP message:
- End
- Response
- User abort
- Provider abort
- ANSI user abort
- ANSI provider abort
- TCAP service user sends TCAP message with one of the following message types:
- End
- Response
- User abort
- ANSI user abort
If TCAP detects that the received message is incorrect, it sends an abort indication to the TCAP service user. The message type is set to provider abort in the case of ITU, and ANSI provider abort in the case of ANSI92 and 96. In the case of ANSI88, the TCAP service user is informed by sending the local reject indication using the component received message. The abort cause parameter is used to indicate the cause of abort.
The transaction portion contains the following parameters:
- TCAP userpart handle
- TCAP transaction identifier
- Message type identifier
- Component present indicator
- Calling address
- Called address
- Quality of service parameters
- ISNI parameters
- Abort cause indicator
The dialogue portion contains the following parameters:
- Dialogue parameters
- User information buffer
