On Sun, Mar 27, 2022 at 10:32:05PM -0400, Peter Beckman wrote:
> My first evidence that UTF-8 was supported was January 13, 2017.
Using which of the methods that Vitelity provides (XMPP, email, other?)?
> There are weird issues with Vitelity, such as odd length limits to SMS
> messages, but we
I integrated with Vitelity for SMS in August 2013.
My first evidence that UTF-8 was supported was January 13, 2017.
There are weird issues with Vitelity, such as odd length limits to SMS
messages, but we worked around them. SMS is reliable enough, though the 48
outages since August 2015 should
On Sun, Mar 27, 2022 at 07:08:01PM -0400, Peter Beckman wrote:
> Why I'm Posting
>
> This is the 48th SMS outage since August 2015 that Vitelity has
> experienced, and in most cases, I have been the first person to alert them
> to a problem. They do not monitor inbound SMS, they just wait for a
>
Sounds like you need to find another provider...?
On Sun, Mar 27, 2022, 7:10 PM Peter Beckman wrote:
> Vitelity hasn't posted anything about this, so I will for those that care.
>
> Short Version: Inbound SMS to all Vitelity DIDs failed between 0150 UTC and
> 1720 UTC on March 27, 2022
>
> Long
Vitelity hasn't posted anything about this, so I will for those that care.
Short Version: Inbound SMS to all Vitelity DIDs failed between 0150 UTC and
1720 UTC on March 27, 2022
Long Version:
At 0150 UTC our Inbound SMS Monitoring detected that one of our DIDs did
not receive a sent SMS.
This
