Isup.decode - Revision history

Dana at 11:53, 21 January 2013

2013-01-21T11:53:36Z

Dana: /* Example of message-prefix */

2012-10-08T13:04:15Z

‎Example of message-prefix

Dana: /* Example of message-prefix */

2012-10-08T13:03:03Z

‎Example of message-prefix

Dana: /* Example of message-prefix */

2012-10-08T13:02:26Z

‎Example of message-prefix

Dana at 13:01, 8 October 2012

2012-10-08T13:01:33Z

Dana: Created page with " '''isup.decode''' is a message sent by a module wishing to decode a buffer containing an ISUP message === Parameters === '''message-prefix''' :::Optional string indicating ..."

2012-10-08T13:00:29Z

Created page with " '''isup.decode''' is a message sent by a module wishing to decode a buffer containing an ISUP message === Parameters === '''message-prefix''' :::Optional string indicating ..."

New page

'''isup.decode''' is a message sent by a module wishing to decode a buffer containing an ISUP message

=== Parameters ===

'''message-prefix'''
:::Optional string indicating the prefix for 'protocol-type' and 'protocol-basetype' parameters and for all decoded parameters
'''protocol-type'''
:::Keyword indicating the encoding standard used to create the data buffer to decode: itu-t, ansi
'''protocol-basetype'''
:::Additional information about the encoding standard to be used when the protocol-type might indicate an unknown/unsupported encoding standard
'''rawdata'''
:::Named pointer containing a data block buffer with the ISUP message to decode. The data buffer must contain the ISUP message starting from the message type byte

=== Example of message-prefix ===

message-prefix=isup.
The other parameters must be:
isup.protocol-type=
isup.protocol-basetype=
On return the message parameters will look like:
isup.message-type=IAM
isup.CallingPartyNumber=some-number

==== Return ====

True if the message was succesfully decoded. The message's parameter list will be filled with the decoded ISUP parameters and the "message-type" parameter will be filled with the ISUP message type.
False on decoding failure. The message's parameter list may contain an incomplete ISUP message

← Older revision		Revision as of 11:53, 21 January 2013
Line 32:		Line 32:

	True if the message was succesfully decoded. The message's parameter list will be filled with the decoded ISUP parameters and the "message-type" parameter will be filled with the ISUP message type.		True if the message was succesfully decoded. The message's parameter list will be filled with the decoded ISUP parameters and the "message-type" parameter will be filled with the ISUP message type.
−	False on decoding failure. The message's parameter list may contain an incomplete ISUP message	+	False on decoding failure. The message's parameter list may contain an incomplete ISUP message.
		+
		+
		+	'''See also'''
		+
		+	* [[isup.encode]]

@@ Line 19: / Line 19: @@
 The other parameters must be:
-isup.protocol-type= \n
+isup.protocol-type=
-isup.protocol-basetype= \n
-On return the message parameters will look like: \n
+isup.protocol-basetype=
-isup.message-type=IAM \n
-isup.CallingPartyNumber=some-number \n
+On return the message parameters will look like:
 ==== Return ====

@@ Line 19: / Line 19: @@
 The other parameters must be:
-isup.protocol-type=\n
+isup.protocol-type= \n
-isup.protocol-basetype=\n
+isup.protocol-basetype= \n
-On return the message parameters will look like:\n
+On return the message parameters will look like: \n
-isup.message-type=IAM\n
+isup.message-type=IAM \n
-isup.CallingPartyNumber=some-number\n
+isup.CallingPartyNumber=some-number \n
 ==== Return ====