[asterisk-users] Asterisk rtp.conf stunaddr setting - what happens if there is an outage

[Joshua C. Colp]

On Mon, Feb 6, 2023 at 6:05 PM Dan Cropp <dan at amtelco.com> 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 were able to answer
> the call because the SIP provider didn’t CANCEL the call.
>
> However, upstream from the service provider the calls were terminated.
>
> Resulting in a call from the SIP provider to Asterisk that’s live, but
> there is no caller so it appears to be dead air.
>
>
>
> Does the res_rtp_asterisk stunaddr DNS TTL expiration mentioned in change
> ID I7955a046293f913ba121bbd82153b04439e3465f require the dnsmgr.conf to be
> enabled?
>

It doesn't use dnsmgr so it's not required to be enabled. If the TTL is
long, or it's cached locally then it could stick around longer.

Fundamentally though is there a reason you're using STUN in the first
place? Can you not just configure the public IP address and not rely on an
external STUN server? rtp.conf has ice_host_candidates specifically for
situations like AWS.

-- 
Joshua C. Colp
Asterisk Project Lead
Sangoma Technologies
Check us out at www.sangoma.com and www.asterisk.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20230206/679d9614/attachment.html>