= Frequently Asked Questions =
[[TOC]]

'''SAMBRO specific FAQs'''
* [wiki:Deployments/SAMBRO#INTRODUCTION Why do I need SAMBRO?]
* [wiki:UserGuidelines/SAMBRO#SystemAdministrators How do I install SAMBRO?]
* [wiki:Deployments/SAMBRO/FAQs#WhydoIneedaSMSGateway Why does SAMBRO need a SMS Gateway?]
* [wiki:Deployments/SAMBRO/FAQs#UnicodeDisplayProblem Why do I see funny characters in the text?]
* [wiki:Deployments/SAMBRO/Evaluation How do I evaluate a SAMBRO Implementation?]
* [wiki:Deployments/SAMBRO/FAQs#WhatcandifferentusersinSAMBROdo What can different users in SAMBRO do?]
* [http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO/FAQs#Canapprovedalertsbeedited Can approved alerts be edited?]
* [http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO/FAQs#WhyismyAlertHubnotfetchingmessages Why is my Alert Hub not fetching messages?]
* [http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO/FAQs#WhyamInotreceivingEmailSMS Problem receiving Email/SMS?]




== Why do I need a SMS Gateway? ==

Here is an example of a SMS gateway: http://www.smsglobal.com/rest-api/ .Notice the menu below the banner - it has a set of API types, like REST API, SMPP API, HTTP API, etc. We would prefer the REST API. Typically, when you acquire a bulk of SMS from MPT, for example, they would provide you with a script. MPT will provide you a user name and password as well. Then we can add the script, username, and password into SAMBRO for you to begin sending/receiving SMS.

You need the SMS gateway for three reasons:

=== 1. Alerting first responders ===
SMS would be one channel to be used as a wake function with targeted groups, also know as Closed User Groups of focal points. For example, when you are not in office or traveling, you would receive the SMS alerts. It serves as an attention getter directing you to the complete message. This is what we also call as a wake up function.

=== 2. Alert approval process ===
Issuing an alert is a 2 step process. First someone will author (or edit) the message. Then it must be approved, usually by a Supervisor. The Supervisor may be at a meeting or not in the premises. They will receive an SMS requesting to approve the alert. The SMS will contain a URL to the approval page. When they click the approval URL and authenticate, it is only then that the alerts would be disseminated.

=== 3. Acknowledge alert receipt ===
It is a best-practice that first-responders and focal points acknowledge the receipt of the alert message. This way you are guaranteed to know they have received and read the message. Otherwise, the phone can be charging in the kitchen
while you are watching TV and don't hear receiving the alert. Therefore, the person must acknowledge. For this we have incorporated
a special SMS text that they can send, simply type ACK and message id and send SMS. At the central server we can then see who has
acknowledged. Hence, the SMS gateway should be able to receive alerts as well.

== Unicode Display Problem ==
See http://unicode.org/help/display_problems.html

== How do I Evaluate an Implementation ==

[http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO/Evaluation Simulation and Evaluation Methodology] for ensuring your system performs to your requirements before going live. Implementers are encourage to conduct simulations and evaluate the system periodically, at least, once every year.

== What can different users in SAMBRO do? ==

There are six types of users in SAMBRO as of 2016-10-11[[BR]]
1. '''ANONYMOUS''' -> The public users(having no login account)
1. '''AUTHENTICATED''' -> Users having login account with minimal permissions. All other users except anonymous are authenticated plus the designated role.
1. '''MAP_ADMIN''' -> This role is mostly given to the GIS technical personnel in the office.
1. '''ALERT_EDITOR''' -> They can create, edit the alert and submit the alert for approval.
1. '''ALERT_APPROVER''' -> Besides Authorizing Message to disseminate (publish), they can also act as CAP Editor.
1. '''ADMIN''' -> They are the superuser. They are granted with all the permissions.

The detailed list of different roles with permissions are listed [http://eden.sahanafoundation.org/wiki/UserGuidelines/SAMBRO#UserRolesandPermissions here].

== Can approved alerts be edited? ==

No the approved alerts cannot be edited, or deleted. Usually in the CAP world, if there is a mistake, error or have to cancel the previous alert,[[BR]]
you need to create another alert that reference this alert. In SAMBRO, this can be achieved simply via a click a button. More details [http://eden.sahanafoundation.org/wiki/UserGuidelines/SAMBRO/Publish#UpdateCancelorErroraCAPMessage here]


== Why is my Alert Hub not fetching messages? ==

There can be several reasons why your alert hub is not fetching the alerts from external system. There may be some potential bug due to some unforeseen condition which may cause breaking. This should be addressed by the experience developer as may lead to data loss and other issues. Other reasons can be solved through UI. Note that both the described problem may exist in the system.

'''1. Message Polling Timeout/ Error etc.'''

a. Login as admin.
b. Go to raw database table. From UI: Administration -> Database or from URL: /eden/appadmin/index
c. Search for msg_rss_channel. Click on it and open up.
d. Look for the RSS Channel which is not fetching up the messages. Note the channel_id for the same channel.
e. Go back to raw database tables.
f. Go to scheduler_task table.
g. In the query, you can search for message polling as: db.scheduler_task.args =='["msg_rss_channel", channel_id]'. The channel_id is the one we got from step d.
h. This will bring up the required channel. Check the scheduler_task.status. This should be QUEUED. If this is TIMEOUT or STOPPED or EXPIRED or FAILED, turn this to QUEUED and set the next run time.
i. This should solve the problem. Check Problem Number 2 as well for confirmation.

'''2. Message Parsing Timeout/ Error etc.'''

a. Login as admin.
b. Go to raw database table. From UI: Administration -> Database or from URL: /eden/appadmin/index
c. Search for msg_rss_channel. Click on it and open up.
d. Look for the RSS Channel which is not fetching up the messages. Note the channel_id for the same channel.
e. Go back to raw database tables.
f. Go to scheduler_task table.
g. In the query, you can search for message polling as: db.scheduler_task.args == '[channel_id, "parse_rss_2_cap"]'. The channel_id is the one we got from step d.
h. This will bring up the required channel. Check the scheduler_task.status. This should be QUEUED. If this is TIMEOUT or STOPPED or EXPIRED or FAILED, turn this to QUEUED and set the next run time.
i. This should solve the problem.
[[BR]]
NB: If it didn't run after you try to solve the problem by following above steps, give it one/two more try. If the problem persists, then its best to contact the Service Providers to look at the problem.
[[BR]][[BR]]

== Why am I not receiving Email/SMS? ==

SAMBRO uses the scheduler tasks to queue the Email and SMS every 5 minutes. The Eden scheduler is the wrapper to [http://web2py.com/books/default/chapter/29/4#Scheduler-%28experimental%29 web2py scheduler]. There can be several reasons why you are receiving Email/SMS. There may be some potential bug due to some unforeseen condition which may cause breaking. This should be addressed by the experienced developer as may lead to data loss and other issues. Other reasons can be solved through UI.

a. Login as admin.
b. Go to raw database table. From UI: Administration -> Database or from URL: /eden/appadmin/index
c. Search for scheduler_task. Click on it and open up.
d. In the query, you can search as: '''db.scheduler_task.vars == '{"contact_method": "EMAIL"}' '''. Open up the row that comes up.
e. Check if the '''STATUS''' is '''QUEUED'''. If not, change it to '''QUEUED'''. Change '''Next Run Time''' to sometime future that will run.
f. Repeat the same for SMS. In the query, you can search as: '''db.scheduler_task.vars == '{"contact_method": "SMS"}' '''.
g. Repeat the same process as for Email.
h. You can change the '''Period''' to change the time to run scheduler. But be very very careful about it.

[[BR]]
NB: If it didn't run after you try to solve the problem by following above steps, give it one/two more try. If the problem persists, then its best to contact the Service Providers to look at the problem.
[[BR]][[BR]]

[http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO/Evaluation Simulation and Evaluation Methodology] for ensuring your system performs to your requirements before going live. Implementers are encourage to conduct simulations and evaluate the system periodically, at least, once every year.
[http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO/Evaluation Simulation and Evaluation Methodology] for ensuring your system performs to your requirements before going live. Implementers are encourage to conduct simulations and evaluate the system periodically, at least, once every year.
[http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO/Evaluation Simulation and Evaluation Methodology] for ensuring your system performs to your requirements before going live. Implementers are encourage to conduct simulations and evaluate the system periodically, at least, once every year.
[http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO/Evaluation Simulation and Evaluation Methodology] for ensuring your system performs to your requirements before going live. Implementers are encourage to conduct simulations and evaluate the system periodically, at least, once every year.
[http://eden.sahanafoundation.org/wiki/Deployments/SAMBRO/Evaluation Simulation and Evaluation Methodology] for ensuring your system performs to your requirements before going live. Implementers are encourage to conduct simulations and evaluate the system periodically, at least, once every year.