There are four possibilities to this problem listed below and each one will have to be checked.
- Check the system clock, if the system has restarted due to a power supply interruption it is possible the time/date says Jan 01; in systems configured for time and date related access restriction Jan 01, being a bank holiday, may be listed as an 'exception day' consequently barring o/g calls from being made - reset the time & date correctly in the system. Charges could be possible if the problem is proven to non BT causes.
- If the system clock is correct but this problem persists there could be a loss of an outgoing route. Many systems now have some of their exchange connections via other suppliers. Are there alarms displayed on the console? If the alarm or problem persists, and the difficulty appears to be concerning a BT supplied service, report it as a fault for further diagnostics. Charges could be possible if the problem is proven to non BT causes.
- If the system clock is correct and there are no alarms displayed on the system then it's possible there is a routing problem; Many systems now have programming configurations operating a 'Least Cost Routing' protocol, modifying dialled numbers to route out over the most cost effective ways. Additionally some networked systems have 'Optimised Routing' programming in place. If either of these have been modified recently contact the person concerned and advise them of the difficulties.
- Lastly and less commonly there can be a 'Smart Box' located externally to the system, a proprietary piece of equipment also used to route calls in a cost effective manner - check that the Smart Box is operational, and contact the maintainer for reset if necessary. If the problem persists raise a fault report for further diagnostics. Charges could be possible if the problem is proven to non BT causes.