USSD being synchronous, it makes a lot of sense to impose the timeout per request trip. this way you can play with it for even 10 mins as long as you make a trip within a minute. this is how many USSDGW works. for example the *100# for safcom. For slow end users, get them to use SMS until they fasten up otherwise adding more time would affect the network performance dramatically On Thu, Jul 14, 2011 at 10:55 PM, Tony Likhanga <tlikhanga@gmail.com> wrote:
Another point of interest:
If the flows truly utilize the USSD capability of a mobile network, there is a timer on the HLR that determines the maximum duration of any USSD session. This timer is typically set to 60 seconds, though this can be stretched to a system maximum of 120 seconds. It will also interest me to see if this impose any limitation to the workings of your app. (Think of slow end users)
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