Failing Calls and Registrations

This issue has now been resolved.

A High CPU issue on the serving SBC aeuwa08 20.126.150.164/32 caused a failover to the secondary SBC aeuwf08 40.69.2.153/32.

This is standard policy in this issue

A routing issue, which was the cause of the call failures, requires further testing. We have addressed the High CPU issue so feel confident that this will not trigger the issue again.

We are investigating an issue where some accounts will have experienced a loss of registration and the ability to make and receive calls.