On Mon, Feb 6, 2023 at 6:05 PM Dan Cropp <d...@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
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Check out the new Asterisk community forum at: https://community.asterisk.org/ New to Asterisk? Start here: https://wiki.asterisk.org/wiki/display/AST/Getting+Started asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
