• Home
  • Announcements
  • Platform Events

2022-05-25 Outbound Call Failures (Resolved)

Written by Marissa Orsini

Updated at April 22nd, 2023

Contact Us

  • The Essentials
    FAQs Forms
  • Announcements
    Carrier Events mFax Events Platform Events Release Notes
  • Billing Administration
    Datagate OneBill
  • Faxing
    mFax - Analog mFax - Digital Native Fax
  • Hardware & Software
    Manual Configuration Provisioning NDP Axis Cisco Fanvil Grandstream Polycom Snom Yealink Mobile Applications Desktop Applications Mobile-X SNAPbuilder TeamMate Connector UC Integrator
  • Hosted Voice
    Auto Attendants Branding Call Queues Call Routing CDRs Conferencing E-911 Features Fraud Integrations Inventory / Phone Numbers Local & Toll Free Porting Onboarding Recommendations SNAP.HD SIP Trunking SMS / MMS Users Voicemail Caller ID
  • Troubleshooting
    VoIPmonitor Firewalls PBX
  • Ray's Stuff
+ More

Table of Contents

Affected Services Event Timeline (All times 24-hour format, EST) May 25th, 2022 Root Cause Analysis Future Preventative Action

Event Description: Off-net outbound 10 & 11 digit calls across all cores were receiving a 404 Not Found Error.

Event Start Time: 2022-05-25 10:25 AM EST

Event End Time: 2022-05-25 10:31 AM EST

Event Report Issue Date: 2022-05-25

 

 

Affected Services

Off-net outbound 10 & 11 digit calls across all cores. 

Inbound calls, emergency dialing, international calls and other services were not affected during this period.


Event Timeline (All times 24-hour format, EST)

May 25th, 2022

  • 1025 - During the course of a support incident, a change to call routing on all cores was made. Initial testing showed inbound and outbound calls were processing successfully.    
  • 1029 - First report of outbound call failures received, engineers began investigating the issue
  • 1030 - A review of failed calls showed that the modified routing was sending outbound calls with an extra digit in the sender
  • 1031 - Call route change was undone, further testing confirmed that outbound calling was successful
  • 1034 - Notified partners and clients of resolution via discord
  • 1047 - Notified partners and clients of resolution via email

Root Cause Analysis

The modified call route was intended to modify the display of outbound calling numbers in line with NANPA standards. This was to improve the behavior of forwarded calls. Unfortunately, the modification caused outbound calls to send out with an additional digit in the destination, causing outbound off-net calls to fail. 


Future Preventative Action

Our change and review processes have been augmented to include additional steps to prevent this oversight in the future, including improved testing methodology for implementations.

 

resolved call failures

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • 2021-05-04 Poor Call Quality (Resolved)
  • 2020-02-15 - Outbound Call Failure (Resolved)
  • 2022-07-14 - Device Provisioning Server Unreachable (Resolved)
  • 2021-03-16 - Call History Display Failure (Resolved)

Knowledge Base Software powered by Helpjuice

Expand