We are experiencing some call connectivity issues when calls routed through BT . The problem has been reported to BT. The same problem are also being reported by other providers.

UPDATE 10:50

BT have acknowledged the problem and working to resolve this issue.

UPDATE 13:30

There has been an issue on the ENUM server that affected the data. This issue has now been resolved and calls should now be completing successfully.

We are experiencing some call quality issues. Our engineers currently investigating this issue.

UPDATE 19/05/2010

We believe it is being resolved. Should you experience any call quality issues please contact our support team.

We are experiencing some connectivity issues on our SIP2 telephone Registration Server which we are currently investigating.

UPDATE: The problem has been temporary fixed. Should you still experiencing phone registration problems please reboot your telephone. If the problem still persist please call our support hotline 01708 39 39 39.

UPDATE: We have rebooted our SIP2 registration server.

Some of our customers experiencing  loss of connectivity to our VoIP platform.  This might caused by the same issue yesterday.

Some of our customers experiencing  loss of connectivity to our VoIP platform.

UPDATE 06:45pm

The problem has been identified with one of our servers, which is currently causing this issue and the problem will be resolved by our engineering staff this evening.

UPDATE 10:30pm

One of our VoIP equipment server (VIBE) is back up know. The problem caused by some sort of kernel error that caused the machine to lock up.

If your phone shows (NR) on your display or is not registered, please reboot your phone.

We are experiencing some delays on voice traffic from one of our upstream provider.

UPDATE: 04:25pm

Our engineers found the problem and working to resolve this issue right now.

UPDATE: 04:45pm

Our upstream link to our phone registration server had some abnormalities. Our engineers and upstream provider are still investigating this issue.

Phones should now register properly.

We are experiencing some call quality issues on outbound calls. Our engineers currently investigating this issue.

UPDATE: 06:00pm

Our engineers still investigating this issue. However, we are also in contact with BT because of their recent issue where traffic has to be moved from the Kingston SBC to re-balance traffic.

UPDATE: 13-10-2009 03:00pm

Please refer to issue “BT IP EXCHANGE”.

We have experienced loos of connectivity for around 10 seconds to our sip registration server in one our data centers. The issue has been resolved. We apologise for any inconvenience caused.

We are experiencing some issues on our inbound traffic. Our engineers currently investigating this problem.

UPDATE 02:35pm:

Our engineers still investigating this problem.

UPDATE 02:55pm:

It seems to be a latency issue in the network from one of our service providers. Our engineers and engineers from one of our service providers still investigating the problem.

UPDATE 03:25pm:

The network issue settled down. However, the engineers still looking into the problem occurred earlier.

UPDATE 08:30pm

The issue occurred earlier today was down to our sip server where its not responding fast enough on some sip packages. However, we awaiting confirmation from our senior engineer whether the cause of the problem was down to our sip server.

UPDATE 06/10/2009 2:25pm

The issue has been resolved. The problem caused by some delays in our network where our sip server couldn’t response properly.

We are experiencing some problems with the voice quality. Our engineers are investigating the cause of this problem.

UPDATE 11:40am

Our engineers found the problem and they resolving the issue now.

UPDATE 11:45am

Our engineers arrived in our data centre in telecity.

UPDATE 12:05pm

Our engineers resolved the problem.

Cause of problem:

The bad call quality caused by a denial of service (DoS) attack coming into our inbound traffic. However, our firewall and high security measures in place prevented any further intrusion into our servers.  But due to the continuously high load traffic into our inbound traffic caused some congestion in our network.  Our engineers were able to cut-off the source where the high load traffic comes from.

We apologise for any inconvenience caused.