USSD GW - Revision history

Oana: /* Keyword values */

2015-09-14T14:35:09Z

‎Keyword values

Oana: /* ussd.finalize */

2014-11-11T10:21:26Z

‎ussd.finalize

Oana: /* ussd.update */

2014-11-11T10:20:59Z

‎ussd.update

Oana: /* ussd.execute */

2014-11-11T10:19:50Z

‎ussd.execute

Oana: /* camel_map module */

2014-11-11T10:14:47Z

‎camel_map module

Oana: /* Network initiated USSD requests */ Changed description as per Vladimir's notes

2014-08-07T14:42:48Z

‎Network initiated USSD requests: Changed description as per Vladimir's notes

Oana: /* ysmpp module */

2014-02-07T12:36:21Z

‎ysmpp module

Oana: /* camel_map module */

2014-02-07T12:34:52Z

‎camel_map module

Oana: /* Keyword values */

2014-02-06T16:14:12Z

‎Keyword values

Oana: /* ysmpp module */

2014-02-06T16:09:24Z

‎ysmpp module

@@ Line 613: / Line 613: @@
 ** throttling_error: error signaling that a message failed to be processed due to processing side being in congestion state.
 ** protocol_error: SMPP generic error. This error is put whenever there is a SMPP specific error that cannot be mapped into one of the other errors.
 * '''text.encoding'''

@@ Line 555: / Line 555: @@
 ** type: boolean
 ** True if the language was decoded from the USSD string and not from the data coding scheme or if should be encoded on MAP in the USSD string payload.
 * error:
 ** type: keyword

@@ Line 503: / Line 503: @@
 ** type: boolean
 ** True if the language was decoded from the USSD string and not from the data coding scheme or if should be encoded on MAP in the USSD string payload.
 * error:
 ** type: keyword

@@ Line 398: / Line 398: @@
 ** type: boolean
 ** True if the language was decoded from the USSD string and not from the data coding scheme or if should be encoded on MAP in the USSD string payload.
 * imsi:
 ** type: string

← Older revision		Revision as of 10:14, 11 November 2014
Line 732:		Line 732:

	==== camel_map module ====		==== camel_map module ====
		+
		+	'''NOTE''': As of SVN revision 1285, there is a new ''camelmap'' module. For compatibility reasons, the old module, ''camel_map'', was also kept. Both modules read the same configuration file, ''camel_map.conf''. In order to avoid issues, please make sure to only enable one of these modules in the ''[postload]'' section of ''yate.conf''.
		+
		+	The new module is the one that offers USSD UCS2 encoding without language indication, but beware that TCP functionality has been removed from it. That functionality has been moved to the ''xml_tcp'' module. The module only uses messages to communicate with applications. ''ussd_map'' uses messages, so there should be no need for TCP functionality.
		+

	Configuring of tracking IDs is done in the ''general'' section:		Configuring of tracking IDs is done in the ''general'' section:

@@ Line 38: / Line 38: @@
 * network notification requests.
-User interaction requests are USSD requests that the network makes in which it requires some type of information back from the mobile subscriber. These are started by the network through a TCAP BEGIN containing an ''unstructuredSS-Request'' Invoke. The answer from the mobile subscriber will be received in a TCAP CONTINUE containing an ''unstructuredSS-Request'' ResultLast. If the network still wants to request further information, it will repeat the process. Otherwise, it will send a TCAP END to close the TCAP dialog.
+User interaction requests are USSD requests that the network makes in which it requires some type of information back from the mobile subscriber. These are started by the network through a TCAP BEGIN containing an ''unstructuredSS-Request'' Invoke. The answer from the mobile subscriber will be received in a TCAP CONTINUE containing an ''unstructuredSS-Request'' ResultLast. If the network still wants to request further information from the user it can send another ''unstructuredSS-Request'' Invoke in a TCAP CONTINUE and wait for the answer. Once the network obtains all needed information, but wants (for user friendliness) to notify the user about the result of the operations, it can send:
 Network notification requests are USSD requests in which the network only sends a notification to the user. This is achieved by sending a TCAP BEGIN message containing a ''unstructuredSS-Notify'' Invoke. The mobile subscriber side will only respond with a TCAP CONTINUE containing an empty ''unstructuredSS-Notify'' in order to signal that the notification was received. The network will close the TCAP dialog through TCAP END.

← Older revision		Revision as of 12:36, 7 February 2014
Line 1,097:		Line 1,097:


−	'''NOTE''' The module encodes text to ASCII for default encoding (configuration parameter ''default_encoding_type'').	+	'''NOTE''' The module encodes text to ASCII for default encoding (configuration parameter ''default_encoding_type''). If you want to send GSM 7 Bit for SMPP default encoding, please see how the setting is set below.

	'''Configuration Example''''		'''Configuration Example''''

@@ Line 868: / Line 868: @@
   ussd-string=octets
   ussd-decode=all
 ==== ussd_map module ====

← Older revision		Revision as of 16:14, 6 February 2014
Line 606:		Line 606:
	** protocol_error: SMPP generic error. This error is put whenever there is a SMPP specific error that cannot be mapped into one of the other errors.		** protocol_error: SMPP generic error. This error is put whenever there is a SMPP specific error that cannot be mapped into one of the other errors.

		+	* '''text.encoding'''
		+	** gsm7bit / GSM7Bit: text was encoded/is to be encoded GSM 7 Bit
		+	** ucs2 / UCS2: text was encoded/is to be encoded UCS 2
		+
		+	* '''text.lang'''
		+	** two character string specifying a language according to ISO 639-1 or integer value if mapping is not provided.

	==== SMPP custom parameters ====		==== SMPP custom parameters ====

@@ Line 1,087: / Line 1,087: @@
 TODO - configuration explanations
 '''NOTE''' The module encodes text to ASCII for default encoding.
 '''Configuration Example''''
@@ Line 1,107: / Line 1,109: @@
   addr=0.0.0.0
   port=12345
 === Monitoring ===