let me give a little illustration of a service called call2service (C2S) or SMS2Service

_____________ � � � � ____________ � � � �______________

| Ad save 30% | � � � � | � � � � � � � � � | � � � �| ��welcome to�xyz| � � � � � � � � �

|____________| � � � � |__________ | � � � �| � �2> feedback � |

� � � � � � � � � � � � � � � � � � � � � � � � � � � � � �| _____________ |

user calls a number � �user is not � � � � � � �the call handler sends back �

on the advert � � � � � � charged � � � � � � � ��an SMS or USSD MAP request

well, if you want to see how am testing ussdtweet.co.ke send your number to me offlist�

On Thu, Jul 14, 2011 at 1:21 PM, Paul Kevin <paultitude@gmail.com> wrote:

True, it depends on the Mobile Service Provider

On Thu, Jul 14, 2011 at 1:17 PM, Tony Likhanga <tlikhanga@gmail.com> wrote:

Me thoughts: (I just hope I get the clarity of thought to understand half of what I'll say/write next )

Refer to USSD spec doc 22.090 downloadable from http://webapp.etsi.org/key/queryform.asp

<Quote>

5.1.4 Allocation of service codes (to be noted by network operators)
Service codes for use in control of Supplementary Services are standardized by international agreement, so must not be
used by PLMNs unless authorized, except for those codes allocated for PLMN use.
If the message is of the format:
1, 2 or 3 digits from the set (*, #), followed by
NN(N), where N=0-9,
optionally followed by "* and any number of any characters",
and terminating in # SEND:

</Quote>

1. USSD protocol imposes limitatations on input format & length ----> A hitch in getting a unique global USSD code that points to your service.
This means that you've got tough luck in fronting� "+254 799 353535" as your USSD service universal access code. This leaves you with the regular *yyy# scenario.

2. With only the *yyy# scenario at your disposal, Imagine the hustle in getting all mobile operators to agree to reserve that yyy code for you! Well one may argue that USSD short code re-usability can be enforced by extending that to *yyy*zzzzzzzzz# line of thinking; but heck! Some operator has to effect some changes somewhere.

3. With 1 & 2 above done & dusted there's the commercial aspect. How do the operators who channel the USSD traffic to your app benefit from this whole thing? Who takes care of charging for the access (Not service);� them? You? <------Not even your worst enemy should wish you this.

In Short. You have to engage the Mobile operators one on one to achieve this. Unless there's an angle that I have refused to see here. :)

Tony.

_______________________________________________
Skunkworks mailing list
Skunkworks@lists.my.co.ke
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
------------
Skunkworks Rules
http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
------------
Other services @ http://my.co.ke

_______________________________________________
Skunkworks mailing list
Skunkworks@lists.my.co.ke
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
------------
Skunkworks Rules
http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
------------
Other services @ http://my.co.ke