Actions

SCCP:Interworking: Difference between revisions

(initial content)
 
mNo edit summary
 
Line 2: Line 2:




From the point of view of the SCCP user, there is only one SCCP. It is therefore the responsibility of the SCCP to take all the necessary measures to select the correct message types to be sent out and to segment messages if necessary. Hence, at certain interworking nodes, a capability needs to
From the point of view of the SCCP user, there is only one SCCP. It is the responsibility of the SCCP to take all the necessary measures to select the correct message types to be sent out and to segment messages, if necessary. Hence, at certain interworking nodes, a capability needs to
be provided that allows conversion of the new message types (LUDT7, LUDTS7) to XUDT, XUDTS message types provided in the 1993 edition, therefore allowing the segmenting of a [[LUDT]] message into multiple [[XUDT]] messages (or possibly multiple LUDT messages if the destination understands them), or truncating a long [[LUDTS]] to fit into a single [[XUDTS]] message, if necessary.
be provided that allows conversion of the new message types (LUDT7, LUDTS7) to XUDT, XUDTS message types provided in the 1993 edition, therefore allowing the segmenting of a [[LUDT]] message into multiple [[XUDT]] messages (or possibly multiple LUDT messages if the destination understands them), or truncating a long [[LUDTS]] to fit into a single [[XUDTS]] message, if necessary.




'''NOTE:''' As of August 2009, LUDT and LUDTS are not supported.
'''NOTE:''' As of August 2009, LUDT and LUDTS are not supported.
[[category:Needs revising]]

Latest revision as of 09:06, 18 April 2018

SCCP supports interworking between various ITU-T variants (1988, 1992, and 1996) as described in the Q.715 ITU-T Specification.


From the point of view of the SCCP user, there is only one SCCP. It is the responsibility of the SCCP to take all the necessary measures to select the correct message types to be sent out and to segment messages, if necessary. Hence, at certain interworking nodes, a capability needs to be provided that allows conversion of the new message types (LUDT7, LUDTS7) to XUDT, XUDTS message types provided in the 1993 edition, therefore allowing the segmenting of a LUDT message into multiple XUDT messages (or possibly multiple LUDT messages if the destination understands them), or truncating a long LUDTS to fit into a single XUDTS message, if necessary.


NOTE: As of August 2009, LUDT and LUDTS are not supported.