getup / kooragang Goto Github PK

Run last night had an SMS as a response, those never got delivered however since Plivo had applied a geo block. This error was not reported in any KG logs.

This requires updating plivo-node past 0.4.1 version (a.k.a legacy), then fixing the API breakage.

See: https://www.acma.gov.au/choose-your-phone-number#use-phone-numbers-for-fiction for the list

If a choice response is configured to send a text, when using the Test Campaign feature, the caller should get the text message.

After hanging up accidentally without entering responses for a call, the caller will be promoted to enter a response, but when they re-join the pool they won't be given a new session id.

Plivo is restricting signups (at least in Canada) due to "internal risk assessment", are there alternatives that can be used? I know of Twilio but I think their API might be different. Are there plans to support it?
Thanks!

• OPEN
• PTN
• FWD(?)

When selecting Test Campaign for a campaign in Dispatch, the call is placed, but hangs up immediately on answer.

API logs the following:

2022-03-10T03:09:13.602338+00:00 heroku[router]: at=info method=POST path="/connect?campaign_id=222&number=61414555123&assessment=1" host=api.hostname request_id=a54ec987-080e-4b00-bb84-67abefb70769 fwd="111.222.111.222" dyno=web.1 connect=0ms service=10ms status=404 bytes=446 protocol=https
2022-03-10T03:09:14.894750+00:00 heroku[router]: at=info method=POST path="/call_ended?campaign_id=222&number=61414555123&assessment=1" host=api.hostname request_id=59d8548b-d628-425d-9c68-76a611dbb708 fwd="111.222.111.222" dyno=web.1 connect=0ms service=5ms status=404 bytes=449 protocol=https

However these paths seem to work fine for actual campaigns.