CommConnect Help

Hello, working on setting up some SMS reminders, but running into issues
that aren’t really tackled by the commcare documentation.

The issue revolves around receiving messages,

  1. When verifying mobile workers, workers in Nepal receive verification
    texts, but workers in US do not receive texts even though they appear in
    the message log. (I think this is due to the inherent backend_id when
    adding mobile worker #s).

  2. Though mobile workers in Nepal can receive verification texts, they do
    not receive texts from reminders that I setup, although mobile beneficiary
    #'s in the US do receive the messages. (backend_id for numbers in the
    states are all tropo, and mecha for international).

Eventually the goal is to have 3 reminders, 1 is an immediate response to
the addition of a new beneficiary, the second is a 3 day follow-up
reminder, and the third is a 10 day reminder.

Any thoughts on how to approach this?
Thanks in advance, I really appreciate the support.

Hi Mark,

When verifying mobile workers, workers in Nepal receive verification texts,
but workers in US do not receive texts even though they appear in the
message log. (I think this is due to the inherent backend_id when adding
mobile worker #s).
[SS] That’s correct. At the moment, we don’t use our US-based backend for
verification. That being said, you can always send 123 to 617-575-2704
after clicking on the verify button. 617-575-2704 is the phone number of
Tropo, our US gateway that supports incoming messages. Do you need support
for US based workers?

Though mobile workers in Nepal can receive verification texts, they do not
receive texts from reminders that I setup, although mobile beneficiary #'s
in the US do receive the messages. (backend_id for numbers in the states
are all tropo, and mecha for international).
[SS] Which number are the workers in Nepal receiving a verification text
from? Are you using mecha as the backend for international? I think you
need to use “mach”.

For your use case, do you need to message the beneficiaries or the new
workers?

Thanks,
Sheel

··· On Sun, Apr 7, 2013 at 4:41 PM, Mark Maples wrote:

Hello, working on setting up some SMS reminders, but running into issues
that aren’t really tackled by the commcare documentation.

The issue revolves around receiving messages,

  1. When verifying mobile workers, workers in Nepal receive verification
    texts, but workers in US do not receive texts even though they appear in
    the message log. (I think this is due to the inherent backend_id when
    adding mobile worker #s).

  2. Though mobile workers in Nepal can receive verification texts, they do
    not receive texts from reminders that I setup, although mobile beneficiary
    #'s in the US do receive the messages. (backend_id for numbers in the
    states are all tropo, and mecha for international).

Eventually the goal is to have 3 reminders, 1 is an immediate response to
the addition of a new beneficiary, the second is a 3 day follow-up
reminder, and the third is a 10 day reminder.

Any thoughts on how to approach this?
Thanks in advance, I really appreciate the support.


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Sheel Shah
Project Manager | Dimagi India
t: +91 1146704670 | m: +91 9560187282

Hi Mark,

I am intrigued to learn more about your project. I am based in Nepal and
working with Dimagi since last July. Can you please provide more backgroud
about your work in Nepal?

Thanks,
Sangya

··· On Mon, Apr 8, 2013 at 5:11 AM, Mark Maples wrote:

Hello, working on setting up some SMS reminders, but running into issues
that aren’t really tackled by the commcare documentation.

The issue revolves around receiving messages,

  1. When verifying mobile workers, workers in Nepal receive verification
    texts, but workers in US do not receive texts even though they appear in
    the message log. (I think this is due to the inherent backend_id when
    adding mobile worker #s).

  2. Though mobile workers in Nepal can receive verification texts, they do
    not receive texts from reminders that I setup, although mobile beneficiary
    #'s in the US do receive the messages. (backend_id for numbers in the
    states are all tropo, and mecha for international).

Eventually the goal is to have 3 reminders, 1 is an immediate response to
the addition of a new beneficiary, the second is a 3 day follow-up
reminder, and the third is a 10 day reminder.

Any thoughts on how to approach this?
Thanks in advance, I really appreciate the support.


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Mark,

We made a change today that should simplify the connectivity issues you
were having. From now on, your U.S. mobile workers will be able to receive
the verification texts as well as those in Nepal, and when sending sms to
cases, you can now leave the contact_backend_id case property blank (or
omit it entirely). If this case property is not present, the system will
automatically choose which sms gateway to use based on the destination
number.

This should solve both of the connectivity issues you were having. As
Sheel mentioned, could you give us a little more detail about your specific
reminder use case? It sounds like you want to send an sms to a case’s
owner(s) as soon as the case is created, 3 days after creation, and 10 days
after creation - is that correct?

Regards,
Giovanni

··· On Mon, Apr 8, 2013 at 7:27 PM, Sheel Shah wrote:

Hi Mark,

When verifying mobile workers, workers in Nepal receive verification
texts, but workers in US do not receive texts even though they appear in
the message log. (I think this is due to the inherent backend_id when
adding mobile worker #s).
[SS] That’s correct. At the moment, we don’t use our US-based backend
for verification. That being said, you can always send 123 to
617-575-2704 after clicking on the verify button. 617-575-2704 is the
phone number of Tropo, our US gateway that supports incoming messages. Do
you need support for US based workers?

Though mobile workers in Nepal can receive verification texts, they do not
receive texts from reminders that I setup, although mobile beneficiary #'s
in the US do receive the messages. (backend_id for numbers in the states
are all tropo, and mecha for international).
[SS] Which number are the workers in Nepal receiving a verification text
from? Are you using mecha as the backend for international? I think you
need to use “mach”.

For your use case, do you need to message the beneficiaries or the new
workers?

Thanks,
Sheel

On Sun, Apr 7, 2013 at 4:41 PM, Mark Maples mrmaples@gmail.com wrote:

Hello, working on setting up some SMS reminders, but running into issues
that aren’t really tackled by the commcare documentation.

The issue revolves around receiving messages,

  1. When verifying mobile workers, workers in Nepal receive verification
    texts, but workers in US do not receive texts even though they appear in
    the message log. (I think this is due to the inherent backend_id when
    adding mobile worker #s).

  2. Though mobile workers in Nepal can receive verification texts, they do
    not receive texts from reminders that I setup, although mobile beneficiary
    #'s in the US do receive the messages. (backend_id for numbers in the
    states are all tropo, and mecha for international).

Eventually the goal is to have 3 reminders, 1 is an immediate response to
the addition of a new beneficiary, the second is a 3 day follow-up
reminder, and the third is a 10 day reminder.

Any thoughts on how to approach this?
Thanks in advance, I really appreciate the support.


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.


Sheel Shah
Project Manager | Dimagi India
t: +91 1146704670 | m: +91 9560187282


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Sangya,

This is Greg. I’m working with Mark on the app and larger deployment. It
would be great to talk tomorrow if you have time. You can email me at
greg@ottoclave.com.

-Greg

··· On Thursday, April 11, 2013 9:30:25 PM UTC+8, sangya wrote: > > Hi Mark, > > I am intrigued to learn more about your project. I am based in Nepal and > working with Dimagi since last July. Can you please provide more backgroud > about your work in Nepal? > > Thanks, > Sangya > > > > > On Mon, Apr 8, 2013 at 5:11 AM, Mark Maples <mrma...@gmail.com wrote: > >> Hello, working on setting up some SMS reminders, but running into issues >> that aren't really tackled by the commcare documentation. >> >> The issue revolves around receiving messages, >> >> 1. When verifying mobile workers, workers in Nepal receive verification >> texts, but workers in US do not receive texts even though they appear in >> the message log. (I think this is due to the inherent backend_id when >> adding mobile worker #s). >> >> 2. Though mobile workers in Nepal can receive verification texts, they do >> not receive texts from reminders that I setup, although mobile beneficiary >> #'s in the US do receive the messages. (backend_id for numbers in the >> states are all tropo, and mecha for international). >> >> Eventually the goal is to have 3 reminders, 1 is an immediate response to >> the addition of a new beneficiary, the second is a 3 day follow-up >> reminder, and the third is a 10 day reminder. >> >> Any thoughts on how to approach this? >> Thanks in advance, I really appreciate the support. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "commcare-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to commcare-user...@googlegroups.com . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

Hi Giovanni and Sheel,

I’m working with Mark on this, and hopefully I can provide some clarity.

Background on our use case:
We track surgical outcomes (post-op infections) in remote health posts in
Nepal.
We want to intake patient data on the day of the procedure (day 0), and get
patients to follow up with the nurses on day3 and day10. Our project
(test-space) has 3 forms, one for each day. We are using SMS reminders to
(hopefully) increase patient followup.

When patient data is entered, we schedule 6 reminder messages to go out. 3
to the last submitting user and 3 to the case:
– immediately,
– 2 days (1 day advanceof 3-day followup)
– 9 days(1-day advance of 10 day followup)

Sheel - we did text 123 to the tropo number (617-575-2704) to verify the US
mobile worker number (used for our testing purposes). It verified in the
commcare system, and the message log (in reports) showed that messages were
exiting the commcare system, but nothing was received. We will test with
the new changes, and report back.
** also, you’re right about the mach backend_id and that’s how it was
entered in our datanode. Just a spelling mistake here in the forum.**

Giovanni - do you recommend removing the backend_id datanode? Haven’t
tested, but that’s a great fix. Thanks for hiding all the complexity!

Final question:
In my experimentation with the reminders, i was unable to get multiple
events within one reminder to show up in the reminder schedule.
I tried changing the “repeat the schedule” to 2 and only got the first one
to show up in the reminder schedule.
Repeat the schedule the following number
of times: indefinitely

"
I also tried creating multiple events and only the first event would show
up in the reminder schedule.

This behavior only occured for “schedule-based” schedule types. I was able
to get multiple events to work in “offset-based” schedule type. Don’t know
if this is a bug or if only the schedule only shows the next SMS event.

If you would like to have this in a new thread, please let me know.

Thanks for your continued support
Greg

··· On Tuesday, April 9, 2013 10:06:52 AM UTC+8, Giovanni Capalbo wrote: > > Hi Mark, > > We made a change today that should simplify the connectivity issues you > were having. From now on, your U.S. mobile workers will be able to receive > the verification texts as well as those in Nepal, and when sending sms to > cases, you can now leave the contact_backend_id case property blank (or > omit it entirely). If this case property is not present, the system will > automatically choose which sms gateway to use based on the destination > number. > > This should solve both of the connectivity issues you were having. As > Sheel mentioned, could you give us a little more detail about your specific > reminder use case? It sounds like you want to send an sms to a case's > owner(s) as soon as the case is created, 3 days after creation, and 10 days > after creation - is that correct? > > Regards, > Giovanni > > > On Mon, Apr 8, 2013 at 7:27 PM, Sheel Shah <ss...@dimagi.com wrote: > >> Hi Mark, >> >> When verifying mobile workers, workers in Nepal receive verification >> texts, but workers in US do not receive texts even though they appear in >> the message log. (I think this is due to the inherent backend_id when >> adding mobile worker #s). >> [SS] That's correct. At the moment, we don't use our US-based backend >> for verification. That being said, you can always send 123 to >> 617-575-2704 after clicking on the verify button. 617-575-2704 is the >> phone number of Tropo, our US gateway that supports incoming messages. Do >> you need support for US based workers? >> >> Though mobile workers in Nepal can receive verification texts, they do >> not receive texts from reminders that I setup, although mobile beneficiary >> #'s in the US do receive the messages. (backend_id for numbers in the >> states are all tropo, and mecha for international). >> [SS] Which number are the workers in Nepal receiving a verification text >> from? Are you using mecha as the backend for international? I think you >> need to use "mach". >> >> For your use case, do you need to message the beneficiaries or the new >> workers? >> >> Thanks, >> Sheel >> >> >> On Sun, Apr 7, 2013 at 4:41 PM, Mark Maples <mrma...@gmail.com wrote: >> >>> Hello, working on setting up some SMS reminders, but running into issues >>> that aren't really tackled by the commcare documentation. >>> >>> The issue revolves around receiving messages, >>> >>> 1. When verifying mobile workers, workers in Nepal receive verification >>> texts, but workers in US do not receive texts even though they appear in >>> the message log. (I think this is due to the inherent backend_id when >>> adding mobile worker #s). >>> >>> 2. Though mobile workers in Nepal can receive verification texts, they >>> do not receive texts from reminders that I setup, although mobile >>> beneficiary #'s in the US do receive the messages. (backend_id for numbers >>> in the states are all tropo, and mecha for international). >>> >>> Eventually the goal is to have 3 reminders, 1 is an immediate response >>> to the addition of a new beneficiary, the second is a 3 day follow-up >>> reminder, and the third is a 10 day reminder. >>> >>> Any thoughts on how to approach this? >>> Thanks in advance, I really appreciate the support. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "commcare-users" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to commcare-user...@googlegroups.com . >>> For more options, visit https://groups.google.com/groups/opt_out. >>> >>> >>> >> >> >> >> -- >> Sheel Shah >> Project Manager | Dimagi India >> t: +91 1146704670 | m: +91 9560187282 >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "commcare-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to commcare-user...@googlegroups.com . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

Hi Greg,

Answers inline.

Thanks,
Giovanni

Hi Giovanni and Sheel,

I’m working with Mark on this, and hopefully I can provide some clarity.

Background on our use case:
We track surgical outcomes (post-op infections) in remote health posts in
Nepal.
We want to intake patient data on the day of the procedure (day 0), and
get patients to follow up with the nurses on day3 and day10. Our project
(test-space) has 3 forms, one for each day. We are using SMS reminders to
(hopefully) increase patient followup.

When patient data is entered, we schedule 6 reminder messages to go out.
3 to the last submitting user and 3 to the case:
– immediately,
– 2 days (1 day advanceof 3-day followup)
– 9 days(1-day advance of 10 day followup)

I see, this sounds like a pretty straightforward use case. The easiest way
to do this would be to have two reminder definitions. They would be
identical except that one would send to the case, and the other to the user
or owner. The reminders would trigger when “Case Property name exists”,
start “as soon as it triggers” with a 0 Start Offset, and then you could
just set up an “Offset-Based” schedule with three events after waiting 0,
2, and 9 days (leaving Time to Wait as 00:00). Finally, you’d want to just
"Repeat the schedule the following number of times: 1".

Since the solution above uses an Offset-Based schedule, the time that
everyone receives the reminders would be the time of day that the first
form was submitted to create the case. If you want the 2-day and 9-day
reminders to go out at a specific time of day, you could split them out
into their own schedule-based reminder definitions.

Sheel - we did text 123 to the tropo number (617-575-2704) to verify the
US mobile worker number (used for our testing purposes). It verified in
the commcare system, and the message log (in reports) showed that messages
were exiting the commcare system, but nothing was received. We will test
with the new changes, and report back.
** also, you’re right about the mach backend_id and that’s how it was
entered in our datanode. Just a spelling mistake here in the forum.**

Giovanni - do you recommend removing the backend_id datanode? Haven’t
tested, but that’s a great fix. Thanks for hiding all the complexity!

For your project, I would recommend to leave out the contact_backend_id
case property (and set it to an empty string for any existing cases you
have), since you’ll get the same result and it would be much simpler to
manage and test with. Just note that for each sms project, it’s important
to test sms connectivity with all mobile networks in the country you’re
supporting, since sms connectivity can vary based on carrier. If you end
up seeing connectivity issues with a certain network, then you may have to
add the contact_backend_id to “override” the system’s default sms gateway
choice just for contacts from the network(s) having issues.

Final question:
In my experimentation with the reminders, i was unable to get multiple
events within one reminder to show up in the reminder schedule.
I tried changing the “repeat the schedule” to 2 and only got the first one
to show up in the reminder schedule.

At the moment, this is actually expected behavior. The reminder calendar
only shows the next scheduled reminder event, and not all events at once.
In the future, we’re planning to change it so that it shows all of them at
once.

··· On Tue, Apr 9, 2013 at 5:30 AM, Greg Tao wrote:

Repeat the schedule the following number
of times: indefinitely

"
I also tried creating multiple events and only the first event would show
up in the reminder schedule.

This behavior only occured for “schedule-based” schedule types. I was
able to get multiple events to work in “offset-based” schedule type. Don’t
know if this is a bug or if only the schedule only shows the next SMS
event.

If you would like to have this in a new thread, please let me know.

Thanks for your continued support
Greg

On Tuesday, April 9, 2013 10:06:52 AM UTC+8, Giovanni Capalbo wrote:

Hi Mark,

We made a change today that should simplify the connectivity issues you
were having. From now on, your U.S. mobile workers will be able to receive
the verification texts as well as those in Nepal, and when sending sms to
cases, you can now leave the contact_backend_id case property blank (or
omit it entirely). If this case property is not present, the system will
automatically choose which sms gateway to use based on the destination
number.

This should solve both of the connectivity issues you were having. As
Sheel mentioned, could you give us a little more detail about your specific
reminder use case? It sounds like you want to send an sms to a case’s
owner(s) as soon as the case is created, 3 days after creation, and 10 days
after creation - is that correct?

Regards,
Giovanni

On Mon, Apr 8, 2013 at 7:27 PM, Sheel Shah ss...@dimagi.com wrote:

Hi Mark,

When verifying mobile workers, workers in Nepal receive verification
texts, but workers in US do not receive texts even though they appear in
the message log. (I think this is due to the inherent backend_id when
adding mobile worker #s).
[SS] That’s correct. At the moment, we don’t use our US-based backend
for verification. That being said, you can always send 123 to
617-575-2704 after clicking on the verify button. 617-575-2704 is the
phone number of Tropo, our US gateway that supports incoming messages. Do
you need support for US based workers?

Though mobile workers in Nepal can receive verification texts, they do
not receive texts from reminders that I setup, although mobile beneficiary
#'s in the US do receive the messages. (backend_id for numbers in the
states are all tropo, and mecha for international).
[SS] Which number are the workers in Nepal receiving a verification text
from? Are you using mecha as the backend for international? I think you
need to use “mach”.

For your use case, do you need to message the beneficiaries or the new
workers?

Thanks,
Sheel

On Sun, Apr 7, 2013 at 4:41 PM, Mark Maples mrma...@gmail.com wrote:

Hello, working on setting up some SMS reminders, but running into
issues that aren’t really tackled by the commcare documentation.

The issue revolves around receiving messages,

  1. When verifying mobile workers, workers in Nepal receive
    verification texts, but workers in US do not receive texts even though they
    appear in the message log. (I think this is due to the inherent backend_id
    when adding mobile worker #s).

  2. Though mobile workers in Nepal can receive verification texts, they
    do not receive texts from reminders that I setup, although mobile
    beneficiary #'s in the US do receive the messages. (backend_id for numbers
    in the states are all tropo, and mecha for international).

Eventually the goal is to have 3 reminders, 1 is an immediate response
to the addition of a new beneficiary, the second is a 3 day follow-up
reminder, and the third is a 10 day reminder.

Any thoughts on how to approach this?
Thanks in advance, I really appreciate the support.


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user…@**googlegroups.com.

For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


Sheel Shah
Project Manager | Dimagi India
t: +91 1146704670 | m: +91 9560187282


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user…@**googlegroups.com.

For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hi Greg,

My name is Gillian Javetski and I am a program analyst at Dimagi. Thanks
for your email this morning! This is completely separate from the
discussion on this topic, but I was curious about how you created that
dropdown menu within your Google email the one that begins with “Repeat the
schedule.” Very cool!

Thanks again for getting in contact with us, hopefully is helpful!

Gillian

··· On Tue, Apr 9, 2013 at 5:30 AM, Greg Tao wrote:

Hi Giovanni and Sheel,

I’m working with Mark on this, and hopefully I can provide some clarity.

Background on our use case:
We track surgical outcomes (post-op infections) in remote health posts in
Nepal.
We want to intake patient data on the day of the procedure (day 0), and
get patients to follow up with the nurses on day3 and day10. Our project
(test-space) has 3 forms, one for each day. We are using SMS reminders to
(hopefully) increase patient followup.

When patient data is entered, we schedule 6 reminder messages to go out.
3 to the last submitting user and 3 to the case:
– immediately,
– 2 days (1 day advanceof 3-day followup)
– 9 days(1-day advance of 10 day followup)

Sheel - we did text 123 to the tropo number (617-575-2704) to verify the
US mobile worker number (used for our testing purposes). It verified in
the commcare system, and the message log (in reports) showed that messages
were exiting the commcare system, but nothing was received. We will test
with the new changes, and report back.
** also, you’re right about the mach backend_id and that’s how it was
entered in our datanode. Just a spelling mistake here in the forum.**

Giovanni - do you recommend removing the backend_id datanode? Haven’t
tested, but that’s a great fix. Thanks for hiding all the complexity!

Final question:
In my experimentation with the reminders, i was unable to get multiple
events within one reminder to show up in the reminder schedule.
I tried changing the “repeat the schedule” to 2 and only got the first one
to show up in the reminder schedule.
Repeat the schedule the following
number of times: indefinitely

"
I also tried creating multiple events and only the first event would show
up in the reminder schedule.

This behavior only occured for “schedule-based” schedule types. I was
able to get multiple events to work in “offset-based” schedule type. Don’t
know if this is a bug or if only the schedule only shows the next SMS
event.

If you would like to have this in a new thread, please let me know.

Thanks for your continued support
Greg

On Tuesday, April 9, 2013 10:06:52 AM UTC+8, Giovanni Capalbo wrote:

Hi Mark,

We made a change today that should simplify the connectivity issues you
were having. From now on, your U.S. mobile workers will be able to receive
the verification texts as well as those in Nepal, and when sending sms to
cases, you can now leave the contact_backend_id case property blank (or
omit it entirely). If this case property is not present, the system will
automatically choose which sms gateway to use based on the destination
number.

This should solve both of the connectivity issues you were having. As
Sheel mentioned, could you give us a little more detail about your specific
reminder use case? It sounds like you want to send an sms to a case’s
owner(s) as soon as the case is created, 3 days after creation, and 10 days
after creation - is that correct?

Regards,
Giovanni

On Mon, Apr 8, 2013 at 7:27 PM, Sheel Shah ss...@dimagi.com wrote:

Hi Mark,

When verifying mobile workers, workers in Nepal receive verification
texts, but workers in US do not receive texts even though they appear in
the message log. (I think this is due to the inherent backend_id when
adding mobile worker #s).
[SS] That’s correct. At the moment, we don’t use our US-based backend
for verification. That being said, you can always send 123 to
617-575-2704 after clicking on the verify button. 617-575-2704 is the
phone number of Tropo, our US gateway that supports incoming messages. Do
you need support for US based workers?

Though mobile workers in Nepal can receive verification texts, they do
not receive texts from reminders that I setup, although mobile beneficiary
#'s in the US do receive the messages. (backend_id for numbers in the
states are all tropo, and mecha for international).
[SS] Which number are the workers in Nepal receiving a verification text
from? Are you using mecha as the backend for international? I think you
need to use “mach”.

For your use case, do you need to message the beneficiaries or the new
workers?

Thanks,
Sheel

On Sun, Apr 7, 2013 at 4:41 PM, Mark Maples mrma...@gmail.com wrote:

Hello, working on setting up some SMS reminders, but running into
issues that aren’t really tackled by the commcare documentation.

The issue revolves around receiving messages,

  1. When verifying mobile workers, workers in Nepal receive
    verification texts, but workers in US do not receive texts even though they
    appear in the message log. (I think this is due to the inherent backend_id
    when adding mobile worker #s).

  2. Though mobile workers in Nepal can receive verification texts, they
    do not receive texts from reminders that I setup, although mobile
    beneficiary #'s in the US do receive the messages. (backend_id for numbers
    in the states are all tropo, and mecha for international).

Eventually the goal is to have 3 reminders, 1 is an immediate response
to the addition of a new beneficiary, the second is a 3 day follow-up
reminder, and the third is a 10 day reminder.

Any thoughts on how to approach this?
Thanks in advance, I really appreciate the support.


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user…@**googlegroups.com.

For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


Sheel Shah
Project Manager | Dimagi India
t: +91 1146704670 | m: +91 9560187282


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user…@**googlegroups.com.

For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

response below.

Hi Greg,

My name is Gillian Javetski and I am a program analyst at Dimagi. Thanks
for your email this morning! This is completely separate from the
discussion on this topic, but I was curious about how you created that
dropdown menu within your Google email the one that begins with “Repeat the
schedule.” Very cool!

I just copy and pasted straight out of the reminder editing page. That
simple.

··· On Tuesday, April 9, 2013 10:41:39 PM UTC+8, Gillian Javetski wrote:

Thanks again for getting in contact with us, hopefully is helpful!

Gillian

On Tue, Apr 9, 2013 at 5:30 AM, Greg Tao <greg...@gmail.com <javascript:>>wrote:

Hi Giovanni and Sheel,

I’m working with Mark on this, and hopefully I can provide some clarity.

Background on our use case:
We track surgical outcomes (post-op infections) in remote health posts in
Nepal.
We want to intake patient data on the day of the procedure (day 0), and
get patients to follow up with the nurses on day3 and day10. Our project
(test-space) has 3 forms, one for each day. We are using SMS reminders to
(hopefully) increase patient followup.

When patient data is entered, we schedule 6 reminder messages to go out.
3 to the last submitting user and 3 to the case:
– immediately,
– 2 days (1 day advanceof 3-day followup)
– 9 days(1-day advance of 10 day followup)

Sheel - we did text 123 to the tropo number (617-575-2704) to verify the
US mobile worker number (used for our testing purposes). It verified in
the commcare system, and the message log (in reports) showed that messages
were exiting the commcare system, but nothing was received. We will test
with the new changes, and report back.
** also, you’re right about the mach backend_id and that’s how it was
entered in our datanode. Just a spelling mistake here in the forum.**

Giovanni - do you recommend removing the backend_id datanode? Haven’t
tested, but that’s a great fix. Thanks for hiding all the complexity!

Final question:
In my experimentation with the reminders, i was unable to get multiple
events within one reminder to show up in the reminder schedule.
I tried changing the “repeat the schedule” to 2 and only got the first
one to show up in the reminder schedule.
Repeat the schedule the following
number of times: indefinitely

"
I also tried creating multiple events and only the first event would show
up in the reminder schedule.

This behavior only occured for “schedule-based” schedule types. I was
able to get multiple events to work in “offset-based” schedule type. Don’t
know if this is a bug or if only the schedule only shows the next SMS
event.

If you would like to have this in a new thread, please let me know.

Thanks for your continued support
Greg

On Tuesday, April 9, 2013 10:06:52 AM UTC+8, Giovanni Capalbo wrote:

Hi Mark,

We made a change today that should simplify the connectivity issues you
were having. From now on, your U.S. mobile workers will be able to receive
the verification texts as well as those in Nepal, and when sending sms to
cases, you can now leave the contact_backend_id case property blank (or
omit it entirely). If this case property is not present, the system will
automatically choose which sms gateway to use based on the destination
number.

This should solve both of the connectivity issues you were having. As
Sheel mentioned, could you give us a little more detail about your specific
reminder use case? It sounds like you want to send an sms to a case’s
owner(s) as soon as the case is created, 3 days after creation, and 10 days
after creation - is that correct?

Regards,
Giovanni

On Mon, Apr 8, 2013 at 7:27 PM, Sheel Shah ss...@dimagi.com wrote:

Hi Mark,

When verifying mobile workers, workers in Nepal receive verification
texts, but workers in US do not receive texts even though they appear in
the message log. (I think this is due to the inherent backend_id when
adding mobile worker #s).
[SS] That’s correct. At the moment, we don’t use our US-based backend
for verification. That being said, you can always send 123 to
617-575-2704 after clicking on the verify button. 617-575-2704 is the
phone number of Tropo, our US gateway that supports incoming messages. Do
you need support for US based workers?

Though mobile workers in Nepal can receive verification texts, they do
not receive texts from reminders that I setup, although mobile beneficiary
#'s in the US do receive the messages. (backend_id for numbers in the
states are all tropo, and mecha for international).
[SS] Which number are the workers in Nepal receiving a verification
text from? Are you using mecha as the backend for international? I think
you need to use “mach”.

For your use case, do you need to message the beneficiaries or the new
workers?

Thanks,
Sheel

On Sun, Apr 7, 2013 at 4:41 PM, Mark Maples mrma...@gmail.com wrote:

Hello, working on setting up some SMS reminders, but running into
issues that aren’t really tackled by the commcare documentation.

The issue revolves around receiving messages,

  1. When verifying mobile workers, workers in Nepal receive
    verification texts, but workers in US do not receive texts even though they
    appear in the message log. (I think this is due to the inherent backend_id
    when adding mobile worker #s).

  2. Though mobile workers in Nepal can receive verification texts, they
    do not receive texts from reminders that I setup, although mobile
    beneficiary #'s in the US do receive the messages. (backend_id for numbers
    in the states are all tropo, and mecha for international).

Eventually the goal is to have 3 reminders, 1 is an immediate response
to the addition of a new beneficiary, the second is a 3 day follow-up
reminder, and the third is a 10 day reminder.

Any thoughts on how to approach this?
Thanks in advance, I really appreciate the support.


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user…@**googlegroups.com.

For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


Sheel Shah
Project Manager | Dimagi India
t: +91 1146704670 | m: +91 9560187282


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user…@**googlegroups.com.

For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-user...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.

Hey Giovanni,

thanks for the clarifications. Helps a lot. I will leave the

I’m wondering if you support any other "backend_id"s or SMS gateways other
than
TROPO_US
MACH
UNICEL

Just wondering if there is a way to hook into other SMS gateways that
collaborate with different networks. Or ways to figure out what networks
the “MACH” gateway interfaces with in Nepal. Thanks.

··· On Tuesday, April 9, 2013 9:43:37 PM UTC+8, Giovanni Capalbo wrote: > > Hi Greg, > > Answers inline. > > Thanks, > Giovanni > > > On Tue, Apr 9, 2013 at 5:30 AM, Greg Tao <greg...@gmail.com >wrote: > >> Hi Giovanni and Sheel, >> >> I'm working with Mark on this, and hopefully I can provide some clarity. >> >> Background on our use case: >> We track surgical outcomes (post-op infections) in remote health posts in >> Nepal. >> We want to intake patient data on the day of the procedure (day 0), and >> get patients to follow up with the nurses on day3 and day10. Our project >> (test-space) has 3 forms, one for each day. We are using SMS reminders to >> (hopefully) increase patient followup. >> >> When patient data is entered, we schedule 6 reminder messages to go out. >> 3 to the last submitting user and 3 to the case: >> -- immediately, >> -- 2 days (1 day advanceof 3-day followup) >> -- 9 days(1-day advance of 10 day followup) >> > > I see, this sounds like a pretty straightforward use case. The easiest > way to do this would be to have two reminder definitions. They would be > identical except that one would send to the case, and the other to the user > or owner. The reminders would trigger when "Case Property *name*exists", start "as soon as it triggers" with a 0 Start Offset, and then you > could just set up an "Offset-Based" schedule with three events after > waiting 0, 2, and 9 days (leaving Time to Wait as 00:00). Finally, you'd > want to just "Repeat the schedule the following number of times: *1*". > > Since the solution above uses an Offset-Based schedule, the time that > everyone receives the reminders would be the time of day that the first > form was submitted to create the case. If you want the 2-day and 9-day > reminders to go out at a specific time of day, you could split them out > into their own schedule-based reminder definitions. > > >> >> Sheel - we did text 123 to the tropo number (617-575-2704) to verify the >> US mobile worker number (used for our testing purposes). It verified in >> the commcare system, and the message log (in reports) showed that messages >> were exiting the commcare system, but nothing was received. We will test >> with the new changes, and report back. >> ** also, you're right about the mach backend_id and that's how it was >> entered in our datanode. Just a spelling mistake here in the forum.** >> >> Giovanni - do you recommend removing the backend_id datanode? Haven't >> tested, but that's a great fix. Thanks for hiding all the complexity! >> > > For your project, I would recommend to leave out the contact_backend_id > case property (and set it to an empty string for any existing cases you > have), since you'll get the same result and it would be much simpler to > manage and test with. Just note that for each sms project, it's important > to test sms connectivity with all mobile networks in the country you're > supporting, since sms connectivity can vary based on carrier. If you end > up seeing connectivity issues with a certain network, then you may have to > add the contact_backend_id to "override" the system's default sms gateway > choice just for contacts from the network(s) having issues. > > >> >> Final question: >> In my experimentation with the reminders, i was unable to get multiple >> events within one reminder to show up in the reminder schedule. >> I tried changing the "repeat the schedule" to 2 and only got the first >> one to show up in the reminder schedule. >> > > At the moment, this is actually expected behavior. The reminder calendar > only shows the next scheduled reminder event, and not all events at once. > In the future, we're planning to change it so that it shows all of them at > once. > > >> Repeat the schedule the following >> number of times: indefinitely >> >> " >> I also tried creating multiple events and only the first event would show >> up in the reminder schedule. >> >> This behavior only occured for "schedule-based" schedule types. I was >> able to get multiple events to work in "offset-based" schedule type. Don't >> know if this is a bug or if only the schedule only shows the next SMS >> event. >> >> If you would like to have this in a new thread, please let me know. >> >> >> >> Thanks for your continued support >> Greg >> >> >> On Tuesday, April 9, 2013 10:06:52 AM UTC+8, Giovanni Capalbo wrote: >> >>> Hi Mark, >>> >>> We made a change today that should simplify the connectivity issues you >>> were having. From now on, your U.S. mobile workers will be able to receive >>> the verification texts as well as those in Nepal, and when sending sms to >>> cases, you can now leave the contact_backend_id case property blank (or >>> omit it entirely). If this case property is not present, the system will >>> automatically choose which sms gateway to use based on the destination >>> number. >>> >>> This should solve both of the connectivity issues you were having. As >>> Sheel mentioned, could you give us a little more detail about your specific >>> reminder use case? It sounds like you want to send an sms to a case's >>> owner(s) as soon as the case is created, 3 days after creation, and 10 days >>> after creation - is that correct? >>> >>> Regards, >>> Giovanni >>> >>> >>> On Mon, Apr 8, 2013 at 7:27 PM, Sheel Shah wrote: >>> >>>> Hi Mark, >>>> >>>> When verifying mobile workers, workers in Nepal receive verification >>>> texts, but workers in US do not receive texts even though they appear in >>>> the message log. (I think this is due to the inherent backend_id when >>>> adding mobile worker #s). >>>> [SS] That's correct. At the moment, we don't use our US-based backend >>>> for verification. That being said, you can always send 123 to >>>> 617-575-2704 after clicking on the verify button. 617-575-2704 is the >>>> phone number of Tropo, our US gateway that supports incoming messages. Do >>>> you need support for US based workers? >>>> >>>> Though mobile workers in Nepal can receive verification texts, they do >>>> not receive texts from reminders that I setup, although mobile beneficiary >>>> #'s in the US do receive the messages. (backend_id for numbers in the >>>> states are all tropo, and mecha for international). >>>> [SS] Which number are the workers in Nepal receiving a verification >>>> text from? Are you using mecha as the backend for international? I think >>>> you need to use "mach". >>>> >>>> For your use case, do you need to message the beneficiaries or the new >>>> workers? >>>> >>>> Thanks, >>>> Sheel >>>> >>>> >>>> On Sun, Apr 7, 2013 at 4:41 PM, Mark Maples wrote: >>>> >>>>> Hello, working on setting up some SMS reminders, but running into >>>>> issues that aren't really tackled by the commcare documentation. >>>>> >>>>> The issue revolves around receiving messages, >>>>> >>>>> 1. When verifying mobile workers, workers in Nepal receive >>>>> verification texts, but workers in US do not receive texts even though they >>>>> appear in the message log. (I think this is due to the inherent backend_id >>>>> when adding mobile worker #s). >>>>> >>>>> 2. Though mobile workers in Nepal can receive verification texts, they >>>>> do not receive texts from reminders that I setup, although mobile >>>>> beneficiary #'s in the US do receive the messages. (backend_id for numbers >>>>> in the states are all tropo, and mecha for international). >>>>> >>>>> Eventually the goal is to have 3 reminders, 1 is an immediate response >>>>> to the addition of a new beneficiary, the second is a 3 day follow-up >>>>> reminder, and the third is a 10 day reminder. >>>>> >>>>> Any thoughts on how to approach this? >>>>> Thanks in advance, I really appreciate the support. >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "commcare-users" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to commcare-user...@**googlegroups.com. >>>>> >>>>> For more options, visit https://groups.google.com/**groups/opt_out >>>>> . >>>>> >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Sheel Shah >>>> Project Manager | Dimagi India >>>> t: +91 1146704670 | m: +91 9560187282 >>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "commcare-users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to commcare-user...@**googlegroups.com. >>>> >>>> For more options, visit https://groups.google.com/**groups/opt_out >>>> . >>>> >>>> >>>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "commcare-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to commcare-user...@googlegroups.com . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

Hi Greg,

The values for contact_backend_id that we support at the moment are listed
here:
https://wiki.commcarehq.org/display/commcarepublic/Configure+a+Case+for+CommConnect

If you have your own SMS gateway account which you’d like to use, we can
also make that work. In terms of networks supported by MACH, we’ve found
that it’s usually best to test outright, but you could also try contacting
them (http://www.mach.com) to find out specific connectivity details.

Thanks,
Giovanni

··· On Tue, Apr 9, 2013 at 1:13 PM, Greg Tao wrote:

Hey Giovanni,

thanks for the clarifications. Helps a lot. I will leave the

I’m wondering if you support any other "backend_id"s or SMS gateways other
than
TROPO_US
MACH
UNICEL

Just wondering if there is a way to hook into other SMS gateways that
collaborate with different networks. Or ways to figure out what networks
the “MACH” gateway interfaces with in Nepal. Thanks.

On Tuesday, April 9, 2013 9:43:37 PM UTC+8, Giovanni Capalbo wrote:

Hi Greg,

Answers inline.

Thanks,
Giovanni

On Tue, Apr 9, 2013 at 5:30 AM, Greg Tao greg...@gmail.com wrote:

Hi Giovanni and Sheel,

I’m working with Mark on this, and hopefully I can provide some clarity.

Background on our use case:
We track surgical outcomes (post-op infections) in remote health posts
in Nepal.
We want to intake patient data on the day of the procedure (day 0), and
get patients to follow up with the nurses on day3 and day10. Our project
(test-space) has 3 forms, one for each day. We are using SMS reminders to
(hopefully) increase patient followup.

When patient data is entered, we schedule 6 reminder messages to go out.
3 to the last submitting user and 3 to the case:
– immediately,
– 2 days (1 day advanceof 3-day followup)
– 9 days(1-day advance of 10 day followup)

I see, this sounds like a pretty straightforward use case. The easiest
way to do this would be to have two reminder definitions. They would be
identical except that one would send to the case, and the other to the user
or owner. The reminders would trigger when “Case Property nameexists”, start “as soon as it triggers” with a 0 Start Offset, and then you
could just set up an “Offset-Based” schedule with three events after
waiting 0, 2, and 9 days (leaving Time to Wait as 00:00). Finally, you’d
want to just “Repeat the schedule the following number of times: 1”.

Since the solution above uses an Offset-Based schedule, the time that
everyone receives the reminders would be the time of day that the first
form was submitted to create the case. If you want the 2-day and 9-day
reminders to go out at a specific time of day, you could split them out
into their own schedule-based reminder definitions.

Sheel - we did text 123 to the tropo number (617-575-2704) to verify
the US mobile worker number (used for our testing purposes). It verified
in the commcare system, and the message log (in reports) showed that
messages were exiting the commcare system, but nothing was received. We
will test with the new changes, and report back.
** also, you’re right about the mach backend_id and that’s how it was
entered in our datanode. Just a spelling mistake here in the forum.**

Giovanni - do you recommend removing the backend_id datanode? Haven’t
tested, but that’s a great fix. Thanks for hiding all the complexity!

For your project, I would recommend to leave out the contact_backend_id
case property (and set it to an empty string for any existing cases you
have), since you’ll get the same result and it would be much simpler to
manage and test with. Just note that for each sms project, it’s important
to test sms connectivity with all mobile networks in the country you’re
supporting, since sms connectivity can vary based on carrier. If you end
up seeing connectivity issues with a certain network, then you may have to
add the contact_backend_id to “override” the system’s default sms gateway
choice just for contacts from the network(s) having issues.

Final question:
In my experimentation with the reminders, i was unable to get multiple
events within one reminder to show up in the reminder schedule.
I tried changing the “repeat the schedule” to 2 and only got the first
one to show up in the reminder schedule.

At the moment, this is actually expected behavior. The reminder calendar
only shows the next scheduled reminder event, and not all events at once.
In the future, we’re planning to change it so that it shows all of them at
once.

Repeat the schedule the following
number of times: indefinitely

"
I also tried creating multiple events and only the first event would
show up in the reminder schedule.

This behavior only occured for “schedule-based” schedule types. I was
able to get multiple events to work in “offset-based” schedule type. Don’t
know if this is a bug or if only the schedule only shows the next SMS
event.

If you would like to have this in a new thread, please let me know.

Thanks for your continued support
Greg

On Tuesday, April 9, 2013 10:06:52 AM UTC+8, Giovanni Capalbo wrote:

Hi Mark,

We made a change today that should simplify the connectivity issues you
were having. From now on, your U.S. mobile workers will be able to receive
the verification texts as well as those in Nepal, and when sending sms to
cases, you can now leave the contact_backend_id case property blank (or
omit it entirely). If this case property is not present, the system will
automatically choose which sms gateway to use based on the destination
number.

This should solve both of the connectivity issues you were having. As
Sheel mentioned, could you give us a little more detail about your specific
reminder use case? It sounds like you want to send an sms to a case’s
owner(s) as soon as the case is created, 3 days after creation, and 10 days
after creation - is that correct?

Regards,
Giovanni

On Mon, Apr 8, 2013 at 7:27 PM, Sheel Shah ss...@dimagi.com wrote:

Hi Mark,

When verifying mobile workers, workers in Nepal receive verification
texts, but workers in US do not receive texts even though they appear in
the message log. (I think this is due to the inherent backend_id when
adding mobile worker #s).
[SS] That’s correct. At the moment, we don’t use our US-based
backend for verification. That being said, you can always send 123 to
617-575-2704 after clicking on the verify button. 617-575-2704 is
the phone number of Tropo, our US gateway that supports incoming messages.
Do you need support for US based workers?

Though mobile workers in Nepal can receive verification texts, they do
not receive texts from reminders that I setup, although mobile beneficiary
#'s in the US do receive the messages. (backend_id for numbers in the
states are all tropo, and mecha for international).
[SS] Which number are the workers in Nepal receiving a verification
text from? Are you using mecha as the backend for international? I think
you need to use “mach”.

For your use case, do you need to message the beneficiaries or the new
workers?

Thanks,
Sheel

On Sun, Apr 7, 2013 at 4:41 PM, Mark Maples mrma...@gmail.com wrote:

Hello, working on setting up some SMS reminders, but running into
issues that aren’t really tackled by the commcare documentation.

The issue revolves around receiving messages,

  1. When verifying mobile workers, workers in Nepal receive
    verification texts, but workers in US do not receive texts even though they
    appear in the message log. (I think this is due to the inherent backend_id
    when adding mobile worker #s).

  2. Though mobile workers in Nepal can receive verification texts,
    they do not receive texts from reminders that I setup, although mobile
    beneficiary #'s in the US do receive the messages. (backend_id for numbers
    in the states are all tropo, and mecha for international).

Eventually the goal is to have 3 reminders, 1 is an immediate
response to the addition of a new beneficiary, the second is a 3 day
follow-up reminder, and the third is a 10 day reminder.

Any thoughts on how to approach this?
Thanks in advance, I really appreciate the support.


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to commcare-user…@**googlegroups.**com.

For more options, visit https://groups.google.com/groups/opt_outhttps://groups.google.com/groups/opt_out
.


Sheel Shah
Project Manager | Dimagi India
t: +91 1146704670 | m: +91 9560187282


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user…@**googlegroups.**com.

For more options, visit https://groups.google.com/groups/opt_outhttps://groups.google.com/groups/opt_out
.


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user…@**googlegroups.com.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Hey Giovanni,

I tried deleting the contact_backend_id and leaving it blank as a datanode.
Result: SMS appeared in the reminder schedule, but never got sent out
through the Report tab’s message log.

Not sure what is going on, but my guess is that no backend_id is being
registered?

Anyway, my workaround is the following. In the contact_backend_id
calculation field:
if( /data/Patient_Qs/contact_phone_number>=20000000000,
‘MOBILE_BACKEND_MACH’, ‘MOBILE_BACKEND_TROPO_US’)

20000000000 = 20million which is greater than any US phone number.

-Greg

··· On Wednesday, April 10, 2013 2:44:14 AM UTC+8, Giovanni Capalbo wrote: > > Hi Greg, > > The values for contact_backend_id that we support at the moment are listed > here: > https://wiki.commcarehq.org/display/commcarepublic/Configure+a+Case+for+CommConnect > > If you have your own SMS gateway account which you'd like to use, we can > also make that work. In terms of networks supported by MACH, we've found > that it's usually best to test outright, but you could also try contacting > them (http://www.mach.com) to find out specific connectivity details. > > Thanks, > Giovanni > > > On Tue, Apr 9, 2013 at 1:13 PM, Greg Tao <greg...@gmail.com >wrote: > >> Hey Giovanni, >> >> thanks for the clarifications. Helps a lot. I will leave the >> >> I'm wondering if you support any other "backend_id"s or SMS gateways >> other than >> TROPO_US >> MACH >> UNICEL >> >> Just wondering if there is a way to hook into other SMS gateways that >> collaborate with different networks. Or ways to figure out what networks >> the "MACH" gateway interfaces with in Nepal. Thanks. >> >> >> >> On Tuesday, April 9, 2013 9:43:37 PM UTC+8, Giovanni Capalbo wrote: >> >>> Hi Greg, >>> >>> Answers inline. >>> >>> Thanks, >>> Giovanni >>> >>> >>> On Tue, Apr 9, 2013 at 5:30 AM, Greg Tao wrote: >>> >>>> Hi Giovanni and Sheel, >>>> >>>> I'm working with Mark on this, and hopefully I can provide some >>>> clarity. >>>> >>>> Background on our use case: >>>> We track surgical outcomes (post-op infections) in remote health posts >>>> in Nepal. >>>> We want to intake patient data on the day of the procedure (day 0), and >>>> get patients to follow up with the nurses on day3 and day10. Our project >>>> (test-space) has 3 forms, one for each day. We are using SMS reminders to >>>> (hopefully) increase patient followup. >>>> >>>> When patient data is entered, we schedule 6 reminder messages to go >>>> out. 3 to the last submitting user and 3 to the case: >>>> -- immediately, >>>> -- 2 days (1 day advanceof 3-day followup) >>>> -- 9 days(1-day advance of 10 day followup) >>>> >>> >>> I see, this sounds like a pretty straightforward use case. The easiest >>> way to do this would be to have two reminder definitions. They would be >>> identical except that one would send to the case, and the other to the user >>> or owner. The reminders would trigger when "Case Property *name*exists", start "as soon as it triggers" with a 0 Start Offset, and then you >>> could just set up an "Offset-Based" schedule with three events after >>> waiting 0, 2, and 9 days (leaving Time to Wait as 00:00). Finally, you'd >>> want to just "Repeat the schedule the following number of times: *1*". >>> >>> Since the solution above uses an Offset-Based schedule, the time that >>> everyone receives the reminders would be the time of day that the first >>> form was submitted to create the case. If you want the 2-day and 9-day >>> reminders to go out at a specific time of day, you could split them out >>> into their own schedule-based reminder definitions. >>> >>> >>>> >>>> Sheel - we did text 123 to the tropo number (617-575-2704) to verify >>>> the US mobile worker number (used for our testing purposes). It verified >>>> in the commcare system, and the message log (in reports) showed that >>>> messages were exiting the commcare system, but nothing was received. We >>>> will test with the new changes, and report back. >>>> ** also, you're right about the mach backend_id and that's how it was >>>> entered in our datanode. Just a spelling mistake here in the forum.** >>>> >>>> Giovanni - do you recommend removing the backend_id datanode? Haven't >>>> tested, but that's a great fix. Thanks for hiding all the complexity! >>>> >>> >>> For your project, I would recommend to leave out the contact_backend_id >>> case property (and set it to an empty string for any existing cases you >>> have), since you'll get the same result and it would be much simpler to >>> manage and test with. Just note that for each sms project, it's important >>> to test sms connectivity with all mobile networks in the country you're >>> supporting, since sms connectivity can vary based on carrier. If you end >>> up seeing connectivity issues with a certain network, then you may have to >>> add the contact_backend_id to "override" the system's default sms gateway >>> choice just for contacts from the network(s) having issues. >>> >>> >>>> >>>> Final question: >>>> In my experimentation with the reminders, i was unable to get multiple >>>> events within one reminder to show up in the reminder schedule. >>>> I tried changing the "repeat the schedule" to 2 and only got the first >>>> one to show up in the reminder schedule. >>>> >>> >>> At the moment, this is actually expected behavior. The reminder >>> calendar only shows the next scheduled reminder event, and not all events >>> at once. In the future, we're planning to change it so that it shows all >>> of them at once. >>> >>> >>>> Repeat the schedule the following >>>> number of times: indefinitely >>>> >>>> " >>>> I also tried creating multiple events and only the first event would >>>> show up in the reminder schedule. >>>> >>>> This behavior only occured for "schedule-based" schedule types. I was >>>> able to get multiple events to work in "offset-based" schedule type. Don't >>>> know if this is a bug or if only the schedule only shows the next SMS >>>> event. >>>> >>>> If you would like to have this in a new thread, please let me know. >>>> >>>> >>>> >>>> Thanks for your continued support >>>> Greg >>>> >>>> >>>> On Tuesday, April 9, 2013 10:06:52 AM UTC+8, Giovanni Capalbo wrote: >>>> >>>>> Hi Mark, >>>>> >>>>> We made a change today that should simplify the connectivity issues >>>>> you were having. From now on, your U.S. mobile workers will be able to >>>>> receive the verification texts as well as those in Nepal, and when sending >>>>> sms to cases, you can now leave the contact_backend_id case property blank >>>>> (or omit it entirely). If this case property is not present, the system >>>>> will automatically choose which sms gateway to use based on the destination >>>>> number. >>>>> >>>>> This should solve both of the connectivity issues you were having. As >>>>> Sheel mentioned, could you give us a little more detail about your specific >>>>> reminder use case? It sounds like you want to send an sms to a case's >>>>> owner(s) as soon as the case is created, 3 days after creation, and 10 days >>>>> after creation - is that correct? >>>>> >>>>> Regards, >>>>> Giovanni >>>>> >>>>> >>>>> On Mon, Apr 8, 2013 at 7:27 PM, Sheel Shah wrote: >>>>> >>>>>> Hi Mark, >>>>>> >>>>>> When verifying mobile workers, workers in Nepal receive verification >>>>>> texts, but workers in US do not receive texts even though they appear in >>>>>> the message log. (I think this is due to the inherent backend_id when >>>>>> adding mobile worker #s). >>>>>> [SS] That's correct. At the moment, we don't use our US-based >>>>>> backend for verification. That being said, you can always send 123 to >>>>>> 617-575-2704 after clicking on the verify button. 617-575-2704 is >>>>>> the phone number of Tropo, our US gateway that supports incoming messages. >>>>>> Do you need support for US based workers? >>>>>> >>>>>> Though mobile workers in Nepal can receive verification texts, they >>>>>> do not receive texts from reminders that I setup, although mobile >>>>>> beneficiary #'s in the US do receive the messages. (backend_id for numbers >>>>>> in the states are all tropo, and mecha for international). >>>>>> [SS] Which number are the workers in Nepal receiving a verification >>>>>> text from? Are you using mecha as the backend for international? I think >>>>>> you need to use "mach". >>>>>> >>>>>> For your use case, do you need to message the beneficiaries or the >>>>>> new workers? >>>>>> >>>>>> Thanks, >>>>>> Sheel >>>>>> >>>>>> >>>>>> On Sun, Apr 7, 2013 at 4:41 PM, Mark Maples wrote: >>>>>> >>>>>>> Hello, working on setting up some SMS reminders, but running into >>>>>>> issues that aren't really tackled by the commcare documentation. >>>>>>> >>>>>>> The issue revolves around receiving messages, >>>>>>> >>>>>>> 1. When verifying mobile workers, workers in Nepal receive >>>>>>> verification texts, but workers in US do not receive texts even though they >>>>>>> appear in the message log. (I think this is due to the inherent backend_id >>>>>>> when adding mobile worker #s). >>>>>>> >>>>>>> 2. Though mobile workers in Nepal can receive verification texts, >>>>>>> they do not receive texts from reminders that I setup, although mobile >>>>>>> beneficiary #'s in the US do receive the messages. (backend_id for numbers >>>>>>> in the states are all tropo, and mecha for international). >>>>>>> >>>>>>> Eventually the goal is to have 3 reminders, 1 is an immediate >>>>>>> response to the addition of a new beneficiary, the second is a 3 day >>>>>>> follow-up reminder, and the third is a 10 day reminder. >>>>>>> >>>>>>> Any thoughts on how to approach this? >>>>>>> Thanks in advance, I really appreciate the support. >>>>>>> >>>>>>> -- >>>>>>> You received this message because you are subscribed to the Google >>>>>>> Groups "commcare-users" group. >>>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>>> send an email to commcare-user...@**googlegroups.**com. >>>>>>> >>>>>>> For more options, visit https://groups.google.com/**grou**ps/opt_out >>>>>>> . >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Sheel Shah >>>>>> Project Manager | Dimagi India >>>>>> t: +91 1146704670 | m: +91 9560187282 >>>>>> >>>>>> >>>>>> -- >>>>>> You received this message because you are subscribed to the Google >>>>>> Groups "commcare-users" group. >>>>>> To unsubscribe from this group and stop receiving emails from it, >>>>>> send an email to commcare-user...@**googlegroups.**com. >>>>>> >>>>>> For more options, visit https://groups.google.com/**grou**ps/opt_out >>>>>> . >>>>>> >>>>>> >>>>>> >>>>> >>>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "commcare-users" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to commcare-user...@**googlegroups.com. >>>> For more options, visit https://groups.google.com/**groups/opt_out >>>> . >>>> >>>> >>>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "commcare-users" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to commcare-user...@googlegroups.com . >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > >

Hi Greg,

I tested this and I’m getting a successful result when contact_backend_id
is omitted from a case, when it takes a blank value from a datanode, and
when it takes the value of an empty string from a datanode. Can you make
sure that the number you were testing with is not duplicated with another
contact in the system?

If you’re still seeing the issue, you can also use the 'Report an Issue’
link at the lower-right of the page (and it would be good to include a link
to the reminder definition used and a link to the case that gave you the
issue).

Thanks,
Giovanni

··· On Thu, Apr 11, 2013 at 9:26 AM, Greg Tao wrote:

Hey Giovanni,

I tried deleting the contact_backend_id and leaving it blank as a
datanode. Result: SMS appeared in the reminder schedule, but never got
sent out through the Report tab’s message log.

Not sure what is going on, but my guess is that no backend_id is being
registered?

Anyway, my workaround is the following. In the contact_backend_id
calculation field:
if( /data/Patient_Qs/contact_phone_number>=20000000000,
‘MOBILE_BACKEND_MACH’, ‘MOBILE_BACKEND_TROPO_US’)

20000000000 = 20million which is greater than any US phone number.

-Greg

On Wednesday, April 10, 2013 2:44:14 AM UTC+8, Giovanni Capalbo wrote:

Hi Greg,

The values for contact_backend_id that we support at the moment are
listed here: https://wiki.commcarehq.org/display/commcarepublic/
Configure+a+Case+for+**CommConnecthttps://wiki.commcarehq.org/display/commcarepublic/Configure+a+Case+for+CommConnect

If you have your own SMS gateway account which you’d like to use, we can
also make that work. In terms of networks supported by MACH, we’ve found
that it’s usually best to test outright, but you could also try contacting
them (http://www.mach.com) to find out specific connectivity details.

Thanks,
Giovanni

On Tue, Apr 9, 2013 at 1:13 PM, Greg Tao greg...@gmail.com wrote:

Hey Giovanni,

thanks for the clarifications. Helps a lot. I will leave the

I’m wondering if you support any other "backend_id"s or SMS gateways
other than
TROPO_US
MACH
UNICEL

Just wondering if there is a way to hook into other SMS gateways that
collaborate with different networks. Or ways to figure out what networks
the “MACH” gateway interfaces with in Nepal. Thanks.

On Tuesday, April 9, 2013 9:43:37 PM UTC+8, Giovanni Capalbo wrote:

Hi Greg,

Answers inline.

Thanks,
Giovanni

On Tue, Apr 9, 2013 at 5:30 AM, Greg Tao greg...@gmail.com wrote:

Hi Giovanni and Sheel,

I’m working with Mark on this, and hopefully I can provide some
clarity.

Background on our use case:
We track surgical outcomes (post-op infections) in remote health posts
in Nepal.
We want to intake patient data on the day of the procedure (day 0),
and get patients to follow up with the nurses on day3 and day10. Our
project (test-space) has 3 forms, one for each day. We are using SMS
reminders to (hopefully) increase patient followup.

When patient data is entered, we schedule 6 reminder messages to go
out. 3 to the last submitting user and 3 to the case:
– immediately,
– 2 days (1 day advanceof 3-day followup)
– 9 days(1-day advance of 10 day followup)

I see, this sounds like a pretty straightforward use case. The easiest
way to do this would be to have two reminder definitions. They would be
identical except that one would send to the case, and the other to the user
or owner. The reminders would trigger when “Case Property nameexists”, start “as soon as it triggers” with a 0 Start Offset, and then you
could just set up an “Offset-Based” schedule with three events after
waiting 0, 2, and 9 days (leaving Time to Wait as 00:00). Finally, you’d
want to just “Repeat the schedule the following number of times: 1”.

Since the solution above uses an Offset-Based schedule, the time that
everyone receives the reminders would be the time of day that the first
form was submitted to create the case. If you want the 2-day and 9-day
reminders to go out at a specific time of day, you could split them out
into their own schedule-based reminder definitions.

Sheel - we did text 123 to the tropo number (617-575-2704) to verify
the US mobile worker number (used for our testing purposes). It verified
in the commcare system, and the message log (in reports) showed that
messages were exiting the commcare system, but nothing was received. We
will test with the new changes, and report back.
** also, you’re right about the mach backend_id and that’s how it was
entered in our datanode. Just a spelling mistake here in the forum.**

Giovanni - do you recommend removing the backend_id datanode? Haven’t
tested, but that’s a great fix. Thanks for hiding all the complexity!

For your project, I would recommend to leave out the contact_backend_id
case property (and set it to an empty string for any existing cases you
have), since you’ll get the same result and it would be much simpler to
manage and test with. Just note that for each sms project, it’s important
to test sms connectivity with all mobile networks in the country you’re
supporting, since sms connectivity can vary based on carrier. If you end
up seeing connectivity issues with a certain network, then you may have to
add the contact_backend_id to “override” the system’s default sms gateway
choice just for contacts from the network(s) having issues.

Final question:
In my experimentation with the reminders, i was unable to get multiple
events within one reminder to show up in the reminder schedule.
I tried changing the “repeat the schedule” to 2 and only got the first
one to show up in the reminder schedule.

At the moment, this is actually expected behavior. The reminder
calendar only shows the next scheduled reminder event, and not all events
at once. In the future, we’re planning to change it so that it shows all
of them at once.

Repeat the schedule the following
number of times: indefinitely

"
I also tried creating multiple events and only the first event would
show up in the reminder schedule.

This behavior only occured for “schedule-based” schedule types. I was
able to get multiple events to work in “offset-based” schedule type. Don’t
know if this is a bug or if only the schedule only shows the next SMS
event.

If you would like to have this in a new thread, please let me know.

Thanks for your continued support
Greg

On Tuesday, April 9, 2013 10:06:52 AM UTC+8, Giovanni Capalbo wrote:

Hi Mark,

We made a change today that should simplify the connectivity issues
you were having. From now on, your U.S. mobile workers will be able to
receive the verification texts as well as those in Nepal, and when sending
sms to cases, you can now leave the contact_backend_id case property blank
(or omit it entirely). If this case property is not present, the system
will automatically choose which sms gateway to use based on the destination
number.

This should solve both of the connectivity issues you were having.
As Sheel mentioned, could you give us a little more detail about your
specific reminder use case? It sounds like you want to send an sms to a
case’s owner(s) as soon as the case is created, 3 days after creation, and
10 days after creation - is that correct?

Regards,
Giovanni

On Mon, Apr 8, 2013 at 7:27 PM, Sheel Shah ss...@dimagi.com wrote:

Hi Mark,

When verifying mobile workers, workers in Nepal receive verification
texts, but workers in US do not receive texts even though they appear in
the message log. (I think this is due to the inherent backend_id when
adding mobile worker #s).
[SS] That’s correct. At the moment, we don’t use our US-based
backend for verification. That being said, you can always send 123 to
617-575-2704 after clicking on the verify button. 617-575-2704 is
the phone number of Tropo, our US gateway that supports incoming messages.
Do you need support for US based workers?

Though mobile workers in Nepal can receive verification texts, they
do not receive texts from reminders that I setup, although mobile
beneficiary #'s in the US do receive the messages. (backend_id for numbers
in the states are all tropo, and mecha for international).
[SS] Which number are the workers in Nepal receiving a verification
text from? Are you using mecha as the backend for international? I think
you need to use “mach”.

For your use case, do you need to message the beneficiaries or the
new workers?

Thanks,
Sheel

On Sun, Apr 7, 2013 at 4:41 PM, Mark Maples mrma...@gmail.comwrote:

Hello, working on setting up some SMS reminders, but running into
issues that aren’t really tackled by the commcare documentation.

The issue revolves around receiving messages,

  1. When verifying mobile workers, workers in Nepal receive
    verification texts, but workers in US do not receive texts even though they
    appear in the message log. (I think this is due to the inherent backend_id
    when adding mobile worker #s).

  2. Though mobile workers in Nepal can receive verification texts,
    they do not receive texts from reminders that I setup, although mobile
    beneficiary #'s in the US do receive the messages. (backend_id for numbers
    in the states are all tropo, and mecha for international).

Eventually the goal is to have 3 reminders, 1 is an immediate
response to the addition of a new beneficiary, the second is a 3 day
follow-up reminder, and the third is a 10 day reminder.

Any thoughts on how to approach this?
Thanks in advance, I really appreciate the support.


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to commcare-user…@**googlegroups.****com.

For more options, visit https://groups.google.com/grou**
ps/opt_out https://groups.google.com/groups/opt_out.


Sheel Shah
Project Manager | Dimagi India
t: +91 1146704670 | m: +91 9560187282


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it,
send an email to commcare-user…@**googlegroups.****com.

For more options, visit https://groups.google.com/grou**
ps/opt_out https://groups.google.com/groups/opt_out.


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user…@**googlegroups.**com.
For more options, visit https://groups.google.com/groups/opt_outhttps://groups.google.com/groups/opt_out
.


You received this message because you are subscribed to the Google
Groups “commcare-users” group.
To unsubscribe from this group and stop receiving emails from it, send
an email to commcare-user…@**googlegroups.com.
For more options, visit https://groups.google.com/**groups/opt_outhttps://groups.google.com/groups/opt_out
.


You received this message because you are subscribed to the Google Groups
"commcare-users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to commcare-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.