This scenario typically occurs when there are capacity issues between the affected carrier and PacWest. Perhaps a circuit is down somewhere or there is an abnormally high call volume between AT&T and PacWest in a given area. This seems logical given that you said calls originating from Sprint are fine.
PacWest is our primary origination carrier and we have not had any reports of this today. Must be an isolated issue. On Wed, Feb 26, 2014 at 4:16 PM, Blaine Reeve <[email protected]> wrote: > It wouldn't happen to be 650-239-xxxx in CA would it? We are receiving > reports of VZ Wireless subscribers not being able to call that exchange and > it is predominately assigned to Pac West. I just happen to have several > numbers in that exchanged ported in to my network that are filing the > complaints. The numbers were ported from Pac West. > > > > *From:* Outages [mailto:[email protected]] *On Behalf Of *Darren > Schreiber > *Sent:* Wednesday, February 26, 2014 2:17 PM > *To:* [email protected] > *Subject:* [outages] Weird issue with PacWest > > > > We got a report from a client that inbound calls to only one of their > blocks are not working. What's strange is we have only been able to > recreate it from AT&T. Calls from Sprint are being delivered. > > > > Anyone else experiencing this and can explain why this would happen? > > > > Client claims Verizon, T-Mobile and AT&T can't reach their block. Yet I > can. > > > > > > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages > >
_______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
