UnwiredtecDocumentation - EnterflexMessaging

2008-01-17 04:28:55

Comparison for /Enterflex Messaging of 2008-01-17 04:28:55 and 2008-01-17 04:31:54

Additions:

In general, messaging functionality is almost equal to ticketing functionality. You even can use the same utility names that where used for ticketing: store-content, store). Or you can use utility send-adapted, which is clone of store-content utility with one exception – default routings-list-task parameter value; you can use send, which is clone of store utility with one exception – default routings-list-task parameter value. Here is the general flow: you provide all additional parameters, required to send message. Ticket is generated and returned as a request execution result if required – just like in ticketing. The only difference is that the generated link (or contents of the message in case, when you use transfer=sms for send-adapted/store-content utility or if you send simple message using send/store utility) is sent to the device you specified.
to – msisdn of device to send message to.
from – shortcode.
tariff – tariff to use. Please note that tariff is a required field for US carriers.
text – message text
max-part-count – max message part count. If message is too big to transfer it in one message, it is automatically splited into several messages that are sent separatly to device and restored there. If you want max part count to be limited, just specify this parameter in the request.

Deletions:

In general, messaging functionality is almost equal to ticketing functionality. You even can use the same utility names that where used for ticketing: store-content, store). Or you can use utility send-adapted, which is clone of store-content utility with one exception – default routings-list-task parameter value; you can use send, which is clone of store utility with one exception – default routings-list-task parameter value. Here is the general flow: you provide all additional parameters, required to send message. Ticket is generated and returned as a request execution result if required – just like in ticketing. The only difference is that the generated link (or just simple message in case, when you use transfer=sms for send-adapted/store-content utility or if you send simple message using send/store utility) is sent to the device you specified.
to – msisdn of device to send message to.
from – shortcode.
tariff – tariff to use. Please note that tariff is a required field for US carriers.
text – message text
max-part-count – max message part count. If message is too big to transfer it in one message, it is automatically splited into several messages that are sent separatly to device and restored there. If you want max part count to be limited, just specify this parameter in the request.

2008-01-17 04:24:49

Comparison for /Enterflex Messaging of 2008-01-17 04:24:49 and 2008-01-17 04:28:55

Additions:

routings-list-task – name of internal task that is responsible for delivering messages. For each gateway this name is unique. Values to use are specified separatly for each gateway. Default value for store-content, store utilitities is storage-routings-list – its a routing list, which do not deliver any messages, just generates ticket and returns it. Default value for send-adapted, send utilitities is clickatell-routings-list – its a routing list, which delivers messages through clickatell gateway.
max-part-count – max message part count. If message is too big to transfer it in one message, it is automatically splited into several messages that are sent separatly to device and restored there. If you want max part count to be limited, just specify this parameter in the request.

Deletions:

routings-list-task – name of internal task that is responsible for delivering messages. For each gateway this name is unique. Values to use are specified separatly for each gateway. Default value for store-content, store utilitities is storage-routings-list – its a routing list, which do not deliver any messages, just generates ticket and returns it. Default value for send-adapted, send utilitities is “clickatell-routings-list” – its a routing list, which delivers messages throw clickatell gateway.
max-part-count – max message part count. If message is too big to transfer it in one sms message, it is automatically splited into several messages that are sent separatly to device and restored there. If you want max part count to be limited, just specify this parameter in request.

2008-01-17 04:13:50

Comparison for /Enterflex Messaging of 2008-01-17 04:13:50 and 2008-01-17 04:24:49

Additions:

routings-list-task – name of internal task that is responsible for delivering messages. For each gateway this name is unique. Values to use are specified separatly for each gateway. Default value for store-content, store utilitities is storage-routings-list – its a routing list, which do not deliver any messages, just generates ticket and returns it. Default value for send-adapted, send utilitities is “clickatell-routings-list” – its a routing list, which delivers messages throw clickatell gateway.
from – shortcode.
tariff – tariff to use. Please note that tariff is a required field for US carriers.
text – message text
max-part-count – max message part count. If message is too big to transfer it in one sms message, it is automatically splited into several messages that are sent separatly to device and restored there. If you want max part count to be limited, just specify this parameter in request.

Deletions:

2008-01-17 04:05:56

Comparison for /Enterflex Messaging of 2008-01-17 04:05:56 and 2008-01-17 04:13:50

Additions:

Messaging is an extension to ticketing that allows client to send sms, wap push messages to client. Enterflex supports several external gateways to send messages throw: Mobile Messenger?, Clickatell and others. If gateway, that you are going to use, requires authentification and charges messages, those charges and billing process are not in the enterflex functionality scope. Enterflex only uses those gateways by your request and sends you callback notifications if any.
In general, messaging functionality is almost equal to ticketing functionality. You even can use the same utility names that where used for ticketing: store-content, store). Or you can use utility send-adapted, which is clone of store-content utility with one exception – default routings-list-task parameter value; you can use send, which is clone of store utility with one exception – default routings-list-task parameter value. Here is the general flow: you provide all additional parameters, required to send message. Ticket is generated and returned as a request execution result if required – just like in ticketing. The only difference is that the generated link (or just simple message in case, when you use transfer=sms for send-adapted/store-content utility or if you send simple message using send/store utility) is sent to the device you specified.
Here is the list of extra parameters supported:
routings-list-task – name of internal task that is responsible for delivering messages. For each gateway this name is unique. Values to use are specified separatly for each gateway. Default value for store-content, store utilitities is “storage-routings-list” – its a routing list, which do not deliver any messages, just generates ticket and returns it. Default value for send-adapted, send utilitities is “storage-routings-list” – its a routing list, which do not deliver any messages, just generates ticket and returns it.
to – msisdn of device to send message to.

Deletions:

Messaging is an extension to ticketing that allows client to send sms, wap push messages to client. Enterflex supports several ways to send wap push messages throw external gateways of Mobile Messenger?, Clickatell and others. If gateway, that you are going to use, requires authentification and charges messages, those charges, billing process are not in the enterflex functionality scope. Enterflex only uses those gateways by your request and sends you callback notifications if any.
In general, messaging functionality is almost equal to ticketing functionality. You even can use the same utility names that where used for ticketing: store-content, store). Or you can use send-adapted which is clone of store-content functionality with one exception – default routings-list-task parameter value, or send which is clone of store utility with one exception – default routings-list-task parameter value. Here is the general flow: you provide all additional parameters, required to send message. Ticket is generated and returned as a request execution result if required – just like in ticketing. The only difference is that the generated link (or just simple message in case when you use transfer=sms for send-adapted/store-content utility or if you send simple message using send/store utility) is send to the device you specified.
Messaging functionality fully extends ticketing functionality and there is list of extra parameters supported:
routings-list-task – name of internal task that is responsible for delivering messages. For each gateway this name is unique. Values to use are specified separatly for each gateway. Default value is “storage-routings-list” – its a routing list, which do not deliver any messages, just generates ticket and returns it.
to – identifier of

2008-01-17 04:01:01

Comparison for /Enterflex Messaging of 2008-01-17 04:01:01 and 2008-01-17 04:05:56

Additions:

Deletions:

In general, messaging functionality is almost equal to ticketing functionality. You even use the same utility names that where used for ticketing (store-content, store). Here is the general flow: you provide all additional parameters, required to send message. Ticket is generated and returned as a request execution result if required – just like in ticketing. The only difference is that link to generated ticket (or just simple message in case when you use transfer=sms for store-content utility or if you send simple message using store utility) is send to device you specified in

2008-01-17 03:27:42

Comparison for /Enterflex Messaging of 2008-01-17 03:27:42 and 2008-01-17 04:01:01

Additions:

Messaging is an extension to ticketing that allows client to send sms, wap push messages to client. Enterflex supports several ways to send wap push messages throw external gateways of Mobile Messenger?, Clickatell and others. If gateway, that you are going to use, requires authentification and charges messages, those charges, billing process are not in the enterflex functionality scope. Enterflex only uses those gateways by your request and sends you callback notifications if any.

In general, messaging functionality is almost equal to ticketing functionality. You even use the same utility names that where used for ticketing (store-content, store). Here is the general flow: you provide all additional parameters, required to send message. Ticket is generated and returned as a request execution result if required – just like in ticketing. The only difference is that link to generated ticket (or just simple message in case when you use transfer=sms for store-content utility or if you send simple message using store utility) is send to device you specified in

Messaging functionality fully extends ticketing functionality and there is list of extra parameters supported:

routings-list-task – name of internal task that is responsible for delivering messages. For each gateway this name is unique. Values to use are specified separatly for each gateway. Default value is “storage-routings-list” – its a routing list, which do not deliver any messages, just generates ticket and returns it.
to – identifier of

Deletions:

2008-01-17 03:27:24

Comparison for /Enterflex Messaging of 2008-01-17 03:27:24 and 2008-01-17 03:27:42

Additions:

Deletions:

Messaging is an extension to ticketing that allows client to send sms, wap push messages to client. Enterflex supports several ways to send wap push messages throw external gateways of Clickatell, Mobile Messenger? and others. If gateway you are going to use, requires authentification, authentification parameters should be requested from the gateway administration and specified for Enterflex.

2008-01-16 09:32:30

Comparison for /Enterflex Messaging of 2008-01-16 09:32:30 and 2008-01-17 03:27:24

Additions:

Messaging is an extension to ticketing that allows client to send sms, wap push messages to client. Enterflex supports several ways to send wap push messages throw external gateways of Clickatell, Mobile Messenger? and others. If gateway you are going to use, requires authentification, authentification parameters should be requested from the gateway administration and specified for Enterflex.

Deletions: