I just called from a Verizon mobile in the Charlotte NC metro area and get the auto attendant. Works fine.
I have seen these types of problems before where the routing table the carriers use to send traffic between each other is “broken” somewhere. I don’t know enough about carrier transport to say exactly but that’s how it’s been explained to me in the past. Jason > On Feb 24, 2020, at 11:29 AM, Hunter Fuller <hf0...@uah.edu> wrote: > > Calling from a Comcast line in Huntsville, AL, results in exactly 60 > seconds of silence (no ringback), followed by an instant connection as > soon as my stopwatch ticks over to 60 seconds. I have never seen > anything like that before. > > I would open a ticket, but the call does technically complete, and I'm > already currently trying to shame their support into fixing another > issue I'm having. But hopefully the data helps. > > -- > Hunter Fuller > Router Jockey > VBH Annex B-5 > +1 256 824 5331 > > Office of Information Technology > The University of Alabama in Huntsville > Network Engineering > >> On Mon, Feb 24, 2020 at 9:00 AM Anthony Holloway >> <avholloway+cisco-v...@gmail.com> wrote: >> >> I called just now (~8:55am us central time) from a twilio sip trunk and from >> a t-mobile cell (technically google fi) and neither worked. I was getting a >> very strange ringback pattern for nearly a minute or more, and then fast >> busy on both. >> >>> On Mon, Feb 24, 2020 at 1:52 AM Ryan Huff <ryanh...@outlook.com> wrote: >>> >>> Yeah, sounds like you may have the problem sorted/known, and if it truly is >>> that other carrier’s have an offending/stale route that need updated... its >>> a pain.... cause sometimes the issue isn’t always with the LEC, it can be >>> upstream to the LEC too. >>> >>> Having users open tickets with their carrier’s is really the only way.. and >>> it can be a grueling, support ticket generating nightmare cause there is >>> really nothing you can do until the call is on your upstream provider’s >>> network. >>> >>> I called from a Verizon Mobile (Atlanta Metro/GA) just a few moments ago >>> and got a “Thank You for calling FastTrack Communications” prompt. >>> >>> Thanks, >>> >>> Ryan >>> >>>> On Feb 23, 2020, at 23:47, Natambu Obleton <noble...@fasttrackcomm.net> >>>> wrote: >>> >>> >>> >>> Hey group, >>> >>> >>> >>> I am a member of this list because we do operate a CUCM cluster and >>> apologize for misusing this list for a non-cisco related issue. >>> >>> >>> >>> I need help troubleshooting an incoming calling issue. I run an SS7 >>> connected Metaswitch in Colorado, USA and am having issues with incoming >>> calls from USA based mobile phones. We did call trap with Centurylink, our >>> tandem provider, and problem calls are not reaching them. They recommended >>> having the callers open tickets with their local providers. This hasn’t >>> resulted in any success with getting a carrier to address this issue. This >>> started on Thursday, 2/20/2020, and we have been unable to reproduce it >>> with our local phones and have been relying on other callers to open the >>> tickets. >>> >>> >>> >>> I would appreciate the USA based members of this could try to call my auto >>> attendant at 970-247-3366. If you are unable to reach the recording, could >>> you please open a ticket with your local carrier? Our customers are >>> reporting ring-no-answer on these calls that never hit my switch. >>> >>> >>> >>> Thank you for your time. >>> >>> >>> >>> -- >>> >>> >>> >>> Natambu Obleton >>> >>> CISSP #370414 CCIE #38491 R&S+Security >>> >>> Director of Network Engineering and Operations >>> >>> FastTrack Communications, Inc. >>> >>> 970.247.3366 >>> >>> >>> >>> _______________________________________________ >>> cisco-voip mailing list >>> cisco-voip@puck.nether.net >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__nam11.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fpuck.nether.net-252Fmailman-252Flistinfo-252Fcisco-2Dvoip-26amp-3Bdata-3D02-257C01-257C-257C8463a77dac2c4f8c003608d7b8e4b75f-257C84df9e7fe9f640afb435aaaaaaaaaaaa-257C1-257C0-257C637181164773376164-26amp-3Bsdata-3DwQY-252Fzl5IB6FxwEV-252FOp15n6-252B4RDfZePgurEfN88Rkang-253D-26amp-3Breserved-3D0&d=DwIGaQ&c=CrVsPA4meZ6vEtstSPLQqC5izq21_OrN_h8zxKzEuwc&r=cxTKAF4Iaor9PiEwHMcKcEgAJ-ObtwqWBXjTvqngqNk&m=8E9LOWm0xLMWybWtfqRgWN9ODA6VazvG_02HpB-fEkk&s=Nof1mobb_xSGZV9fqDs9GpnHjrLqIhqCO9PUJzt5nEU&e= >>> >>> >>> _______________________________________________ >>> cisco-voip mailing list >>> cisco-voip@puck.nether.net >>> https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_cisco-2Dvoip&d=DwIGaQ&c=CrVsPA4meZ6vEtstSPLQqC5izq21_OrN_h8zxKzEuwc&r=cxTKAF4Iaor9PiEwHMcKcEgAJ-ObtwqWBXjTvqngqNk&m=8E9LOWm0xLMWybWtfqRgWN9ODA6VazvG_02HpB-fEkk&s=oZT_0DH42rBn_22G9icxsBe1b5wr3gov-SIZX7QTGrM&e= >>> >> >> _______________________________________________ >> cisco-voip mailing list >> cisco-voip@puck.nether.net >> https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_cisco-2Dvoip&d=DwIGaQ&c=CrVsPA4meZ6vEtstSPLQqC5izq21_OrN_h8zxKzEuwc&r=cxTKAF4Iaor9PiEwHMcKcEgAJ-ObtwqWBXjTvqngqNk&m=8E9LOWm0xLMWybWtfqRgWN9ODA6VazvG_02HpB-fEkk&s=oZT_0DH42rBn_22G9icxsBe1b5wr3gov-SIZX7QTGrM&e= >> > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_cisco-2Dvoip&d=DwIGaQ&c=CrVsPA4meZ6vEtstSPLQqC5izq21_OrN_h8zxKzEuwc&r=cxTKAF4Iaor9PiEwHMcKcEgAJ-ObtwqWBXjTvqngqNk&m=8E9LOWm0xLMWybWtfqRgWN9ODA6VazvG_02HpB-fEkk&s=oZT_0DH42rBn_22G9icxsBe1b5wr3gov-SIZX7QTGrM&e= > _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
