Connection problem or invalid MMI code
Do you guys get this error when running USSD strings on your Android devices ? Connection problem or invalid MMI code Any idea what the cause could be ?
I usually get it on my phone especially just after a call. I can't use USSD for a few seconds, then it goes back to normal. Over to the GSM guys to explain this phenomenon. Regards, Alex On Thu, Sep 11, 2014 at 5:28 PM, Joram Gachuiri via skunkworks < skunkworks@lists.my.co.ke> wrote:
Do you guys get this error when running USSD strings on your Android devices ?
Connection problem or invalid MMI code
Any idea what the cause could be ?
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe 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
@Alex, my guess is that there might be some hastily configured "Call-Cost notification system" involved. Probably, after making a call, the system triggers a USSD message to your handset while using a different encoding format from the one your handset understands - hence the message does not display on your handset. As a result, your handset is technically in an active USSD session that is later torn down after the session limit lapses. I bet that if you can reboot your phone quick enough when experiencing this, then the USSD service will be accessible almost immediately. Tony.
Hi Tony For 1. Target application is down/unreachable or not responding, the error would be. ESME UNREACHABLE or USDC:NO REPLY from ESME Kindly note that the USSD string is correctly configured both on USSD and HLR and the error is intermittent ( 40 % cases) On Thu, Sep 11, 2014 at 3:37 PM, Tony Likhanga via skunkworks < skunkworks@lists.my.co.ke> wrote:
@Alex, my guess is that there might be some hastily configured "Call-Cost notification system" involved.
Probably, after making a call, the system triggers a USSD message to your handset while using a different encoding format from the one your handset understands - hence the message does not display on your handset. As a result, your handset is technically in an active USSD session that is later torn down after the session limit lapses.
I bet that if you can reboot your phone quick enough when experiencing this, then the USSD service will be accessible almost immediately.
Tony.
_______________________________________________ skunkworks mailing list skunkworks@lists.my.co.ke ------------ List info, subscribe/unsubscribe 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
3 Possible causes; in order of likelihood. 1. Non existent USSD short code. The Operator has not yet set-up the code properly. 2. Mismatch on the encoding formats between the USSD packets sent from the phone and what the end application normally uses. 3. Target application is down/unreachable or not responding Tony.
participants (3)
-
Alex Ngatia -
Joram Gachuiri -
Tony Likhanga