Troubleshooting

In a techlead heaven, we would have immeadiate physical access to gateway phones, but alas, most of the time we have to hand them over to the partner. Fortunately, comes this guide on debugging gateway problems.

Follow the steps as below (if you don’t have physical access to the phone, start with step 2 i.e debug from the server side first)

1. Make sure that the device:

   1. Is connected to the internet. You can check this by opening any Browser app in the phone and going to https://google.com.

   2. Check if the instance name, instance type and gateway user password are set correctly in the Gateway Settings app screen.

      

   3. Has the latest Gateway version. Get the latest version by opening the Google Playstore, searching for Medic Gateway and updating the existing app

   4. Medic Gatway should be set as the default app for SMS. To check, go to Settings in the Gateway app. If Medic Gateway is not the default, you will be met with the below app screen. In that case, click Help me change.

      

   5. If messages are not going through to the server, in the To Webapp tab, select some of them and press Retry at the bottom and wait for about 5-10 minutes.

   6. If messages are not going through to the users, in the From Webapp tab, select some of them and press Retry at the bottom and wait for about 5-10 minutes.

   7. In CDMA networks, there are operator issues where messages get to the users in chunks of around 160 characters when the message is too long. If this is the case, go to Settings in the gateway screen and make sure you tick CDMA compatibility mode

   8. Check if the phone has adequate free space

   9. Restart the phone if no solution seems to work. Resetting the Adroind state sometimes resolves some persistent problems

2. When attacking the problem from the phones end does not work, move on to the server and try to solve it from there. Maybe the server has a configuration issue which hinders the processing or the acceptance of the messages by Medic-Api Follow the steps:

   1. Navigate to /srv/storage/gardener/logs/
   2. Perform ls -lt to arrange the log files in order of modified date. Note the concerned file which was last modified on the date you are investigating
   3. Pipe it to grep to get only SMS logs e.g grep api/sms medic_medic_medic-api4.log. As below, note the errors and work from there.

cd /srv/storage/gardener/logs/   
ls -lt   
grep api/sms medic_medic_medic-api4.log

If the above steps don’t yield the problem, get the Android logs using the steps outlined in the doc in this link, note the make/model/android version their gateway handset is and escalate with those details to the PM/project techlead.

Related Content

Feedback

Was this page helpful?

Glad to hear it! Please tell us how we can improve.

Sorry to hear that. Please tell us how we can improve.