nanog mailing list archives
Re: Routing issues to AWS environment.
From: Dovid Bender <dovid () telecurve com>
Date: Thu, 9 May 2019 07:25:06 -0400
Interesting at my 9-5 we use NTT exclusively for SIP traffic and it has been flawless. If there are any tests that you want me to run over NTT via their pop at 111 8th let me know. On Thu, May 9, 2019 at 6:35 AM Chuck Church <chuckchurch () gmail com> wrote:
Are you sure the problem isn’t NTT? My buddy’s WISP peers with Spirit and had a boatload of problems with random packet loss affecting initially just SIP and RTP (both UDP). Spirit was blaming NTT. Problems went away when Spirit stopped peering with NTT yesterday. Path is through Telia now to their main SIP trunk provider. chuck *From:* NANOG <nanog-bounces () nanog org> *On Behalf Of *Curt Rice *Sent:* Wednesday, May 08, 2019 10:56 AM *To:* nanog () nanog org *Subject:* Routing issues to AWS environment. Hi are there any AWS engineers out there? We are seeing routing problems between NTT and AWS in Ashburn, Va and would like to find out which side is having the problem. Thanks, Curt
Current thread:
- Routing issues to AWS environment. Curt Rice (May 08)
- Re: Routing issues to AWS environment. John Von Essen (May 08)
- RE: Routing issues to AWS environment. Chuck Church (May 09)
- Re: Routing issues to AWS environment. Dovid Bender (May 09)
- Re: Routing issues to AWS environment. Job Snijders (May 09)
- RE: Routing issues to AWS environment. Nick Ellermann (May 09)
- Re: Routing issues to AWS environment. Job Snijders (May 09)