I.T Communications Limited incident

Outbound Calls Failing

Major Resolved View vendor source →

I.T Communications Limited experienced a major incident on August 2, 2019 affecting Outbound Calling, lasting 19h 38m. The incident has been resolved; the full update timeline is below.

Started
Aug 02, 2019, 03:50 PM UTC
Resolved
Aug 03, 2019, 11:28 AM UTC
Duration
19h 38m
Detected by Pingoru
Aug 02, 2019, 03:50 PM UTC

Affected components

Outbound Calling

Update timeline

  1. investigating Aug 02, 2019, 03:50 PM UTC

    We are investigating reports of some customers not able to make outbound calls. Update to follow

  2. investigating Aug 02, 2019, 04:15 PM UTC

    We are still trying to identify the cause. We beleive this is only affecting customers using SIP Trunks where the SIP URL is sip-gw.it-communicationsltd.co.uk We are not seeing any issues with sip-gw2.it-communicationsltd.co.uk

  3. monitoring Aug 02, 2019, 04:35 PM UTC

    We have not been able to identify the cause of the issue. We have spent over 2 hours looking at the logs. Howeer we can see calls are now completing without issue. We will contine to investigate to find out what the cause was and will monitor the cluster.

  4. monitoring Aug 02, 2019, 05:14 PM UTC

    Ok small update just to let you know we are still investigating. however it looks like one of our SIP Trunk Clusters was not getting the Status: 183 Session Progress from our outbound termination carriers. This would have caused customers to have silence on outbound calls and waiting a few seconds most customers simply ended the call which we can see from the logs. The issue appears to have started around 3pm and resolved by 5pm. We have spoken to the carrier involved and they are investigating and will provide us with a detailed response once they have reviewed the logs we have sent. We apologise for any inconvenience caused, rest assured we will be following this up to learn what caused the carrier not to send us the Status: 183 Session Progress.

  5. resolved Aug 03, 2019, 11:28 AM UTC

    We have not had any further issues so will now close this issue. We will provide a RFO once we get a detailed resposne from the outbound carrier.