notifius / wctp-gateway Goto Github PK

Replies may not work properly when a directory listing includes formatting like -, (, )

This is a result of normalizing outbound SMS numbers to E.164 notation (+15552223333) to be compatible with Twilio conventions.

When we receive the inbound reply from Twilio, which is in E.164 notation, we take off the +1 to be compatible with Intelligent Series directory listings (typically 10 digits)

Amtelco looks for a verbatim match to the originally sent match (including any non-numeric formatting characters) which will fail from the conversion to E.164 and back as a result of carrier requirements.

So, we need to track the originally formatted telephone number so can properly lead Amtelco back to the correct listing on replies.

Improve notifications for the following use cases:

• Network timeout between CG and EH (i.e., is your WCTP site up)
• Network timeout between Twilio/ThinQ (i.e., upstream is failing)
• Message failure status (i.e., individual number is failing)
• Test E2E delivery somehow

Other useful notification tasks:

• Improved long queue notification setup through Laravel Horizon - it's config file based currently.

CG - WCTP Carrier Gateway (i.e., wctp-gateway)

EH - WCTP Enterprise Host (i.e., WCTPWeb endpoint)

Feature that will not send messages out to recipients until they opt-in.

Possibly require a code?
Perhaps a 1st send message that introduces service and asks them to reply to opt-in?

Need to research best practice on this.