On Mon, Feb 6, 2023 at 6:05 PM Dan Cropp wrote:
> A quick follow-up.
>
>
>
> Looking at other customers running 18.12.1 who reported problems at the
> exact same time with AWS issue described below.
>
>
>
> We are seeing similar behavior.
>
> For these systems, the third STUN failure occurs. We
A quick follow-up.
Looking at other customers running 18.12.1 who reported problems at the exact
same time with AWS issue described below.
We are seeing similar behavior.
For these systems, the third STUN failure occurs. We were able to answer the
call because the SIP provider didn't CANCEL
Over the weekend, we had several customers running at AWS. AWS had an outage
during this time.
This customer is running Asterisk 16.23.0 (which has the STUN timeout crash
fix).
>From what I have been told, other customers are running newer Asterisk 18.12.1
>but encountered similar issues. (I
