TCAP:Creating new transaction - Revision history

Allyntree at 19:34, 24 April 2018

2018-04-24T19:34:36Z

← Older revision		Revision as of 15:34, 24 April 2018
Line 1:		Line 1:
	The '''transaction initiation''' (request/response) message is used to create and initialize a new TCAP transaction. The new transaction instance stays active until ~~sending~~ the transaction and dialogue portions.		The '''transaction initiation''' (request/response) message is used to create and initialize a new TCAP transaction. The new transaction instance stays active until the transaction and dialogue portions are sent.


Line 5:		Line 5:


	To complete the TCAP message, components and parameters must be individually added using the transaction ~~cottrmponent~~ add message. Message type, called and calling addresses, quality of service, dialogue and user information, etc., must be initialized using the '''transaction component send''' message. The TCAP message assembly and transmission to the SCCP layer occurs only when the TCAP layer receives the '''transaction component send''' message.		To complete the TCAP message, components and parameters must be individually added using the transaction component add message. Message type, called and calling addresses, quality of service, dialogue and user information, etc., must be initialized using the '''transaction component send''' message. The TCAP message assembly and transmission to the SCCP layer occurs only when the TCAP layer receives the '''transaction component send''' message.


	~~[[category:Needs revising]]~~

Ktrueman: clean up

2009-09-08T18:50:15Z

clean up

← Older revision		Revision as of 14:50, 8 September 2009
Line 1:		Line 1:
	The transaction initiation (request/response) message is used to create and initialize a new TCAP transaction. The new transaction instance stays active until sending the transaction and dialogue portions:		The '''transaction initiation''' (request/response) message is used to create and initialize a new TCAP transaction. The new transaction instance stays active until sending the transaction and dialogue portions.


	Each transaction must be uniquely identified. The transaction identifier of outgoing transaction is determined by TCAP service user and must be within the range 0x80000000 to 0xFFFFFFFF. The transaction identifier of incoming transaction is determined by TCAP layer and will always be within the range 0x00000001 to 0x7FFFFFFF.		Each transaction must be uniquely identified. The transaction identifier of an outgoing transaction is determined by the TCAP service user and must be within the range 0x80000000 to 0xFFFFFFFF. The transaction identifier of an incoming transaction is determined by the TCAP layer and will always be within the range 0x00000001 to 0x7FFFFFFF.


	To complete the TCAP message, components and parameters must be individually added using the transaction cottrmponent add message. Message type, called and calling addresses, quality of service, dialogue and user information, etc., must be initialized using the transaction component send message. The TCAP message assembly and transmission to the SCCP layer occurs only when the TCAP layer receives the transaction component send message.		To complete the TCAP message, components and parameters must be individually added using the transaction cottrmponent add message. Message type, called and calling addresses, quality of service, dialogue and user information, etc., must be initialized using the '''transaction component send''' message. The TCAP message assembly and transmission to the SCCP layer occurs only when the TCAP layer receives the '''transaction component send''' message.


	[[category:Needs revising]]		[[category:Needs revising]]

Ktrueman: clean up

2009-09-08T18:44:16Z

clean up

← Older revision		Revision as of 14:44, 8 September 2009
Line 5:		Line 5:


	To complete the TCAP message, components and parameters must be individually added using the transaction cottrmponent add message. Message type, called and calling addresses, quality of service, dialogue and user ~~information…~~ must be initialized using the transaction component send message. The TCAP message assembly and transmission to the SCCP layer occurs only when the TCAP layer receives the transaction component send message.		To complete the TCAP message, components and parameters must be individually added using the transaction cottrmponent add message. Message type, called and calling addresses, quality of service, dialogue and user information, etc., must be initialized using the transaction component send message. The TCAP message assembly and transmission to the SCCP layer occurs only when the TCAP layer receives the transaction component send message.


			[[category:Needs revising]]

Ktrueman: initial content

2009-09-08T18:43:38Z

initial content

New page

The transaction initiation (request/response) message is used to create and initialize a new TCAP transaction. The new transaction instance stays active until sending the transaction and dialogue portions:

Each transaction must be uniquely identified. The transaction identifier of outgoing transaction is determined by TCAP service user and must be within the range 0x80000000 to 0xFFFFFFFF. The transaction identifier of incoming transaction is determined by TCAP layer and will always be within the range 0x00000001 to 0x7FFFFFFF.

To complete the TCAP message, components and parameters must be individually added using the transaction cottrmponent add message. Message type, called and calling addresses, quality of service, dialogue and user information… must be initialized using the transaction component send message. The TCAP message assembly and transmission to the SCCP layer occurs only when the TCAP layer receives the transaction component send message.