Common features

Messages are represented hierarchically in XML format. There may be more parameters than described in this specification. Unknown parameters should be ignored.

Each message contains four major parts:

• Transport
• Application
• Components (payload)
• Latency determination

In XML these map like in this example:

<m>

	<transport>
		<mtp>
			<LocalPC>101</LocalPC>
			<RemotePC>5000</RemotePC>
			<sls>2</sls>
		</mtp>
		<sccp>
			<CalledPartyAddress>
				<ssn>5</ssn>
 				<pointcode>101</pointcode>
			</CalledPartyAddress>
			<CallingPartyAddress>
				<ssn>0</ssn>
			</CallingPartyAddress>
		</sccp>
 		<tcap>
			<request-type>Begin"</request-type>
			<remoteTID>12 34 56 78</remoteTID>
		</tcap>
	</transport>
	<application>contextName-v2</application>
	<component remoteCID="1" type="Invoke" operationCode="20">
		application-specific
		...
		application-specific
	</component>
	...
	<timestamp-send>1377071763411706</timestamp-send>

</m>

In these examples the XML is nicely indented for readability. In practice any whitespace between XML elements may be omitted.