Status  >> VoIP

Order posts by limited to posts

18 Aug 10:00:00
Details
18 Aug 10:48:39

Our legacy 'C' VoIP platform will be removed from service on March 2nd 2015.

This platform is now old, tired and we have a better VoIP platform: our FireBrick-based 'Voiceless' platform.

We have created a wiki page with details for customers needing to move platforms: http://wiki.aa.org.uk/VoIP_-_Moving_Platform

We will be contacting customers individually by email later in the year, but we'd recommend that customers start moving now. The wiki page above explains how to move, and in most cases it is simply changing the server details in your VoIP device. Please do contact Support for help though.

Started 18 Aug 10:00:00 by AAISP Staff
Update expected 02 Mar 2015 11:00:00
Expected close 02 Mar 2015 10:00:00

23 May 12:00:00
Details
23 May 12:07:01

Our legacy 'A' VoIP platform will be removed from service on November 10th 2014.

This platform is our original Asterisk based system; it is now old, tired and we have a better VoIP platform: our FireBrick based 'Voiceless' platform.

We have created a wiki page with details for customers needing to move platforms: http://wiki.aa.org.uk/VoIP_-_Moving_Platform

We will be contacting customers individually by email in the coming weeks.

Our Asterisk platform has historically been used by customers using IAX or who have phones behind NAT. Our current 'Voiceless' platform should work just as well for phones behind NAT. This does mean that we will no longer be providing a IAX service. The wiki pages have details on configuring asterisk to use SIP instead.

The feature set on Voiceless is the same (if not better) than on 'A' (apart from the IAX support).

Please see the wiki page for more information: http://wiki.aa.org.uk/VoIP_-_Moving_Platform

Update
19 Aug 13:42:19
We are starting to email customers about this work this week.
Started 23 May 12:00:00 by AAISP Staff
Expected close 10 Nov 10:00:00

11 Apr 15:50:28
Details
11 Apr 15:53:42
There is a problem with the C server and it needs to be restarted again after the maintenance yesterday evening. We are going to do this at 17:00 as we need it to be done as soon as possible. Sorry for the short notice.
Started 11 Apr 15:50:28

7 Apr 13:45:09
Details
7 Apr 13:52:31
We will be carrying out some maintenance on our 'C' SIP server outside office hours. It will cause disruption to calls, but is likely only to last a couple of minutes and will only affect calls on the A and C servers. It will not affect calls on our "voiceless" SIP platform or SIP2SIM. We will do this on Thursday evening at around 22:30. Please contact support if you have any questions.
Update
10 Apr 23:19:59
Completed earlier this evening.
Started 7 Apr 13:45:09
Previously expected 10 Apr 22:45:00

Yesterday 14:45:53
Details
17 Oct 16:43:25
Planning to do some work early Saturday and possible Sunday, before 8am. It should be virtually no disruption though. This is on the Maidenhead routers so any impact would be VoIP, colocation and Ethernet links from there. We have some slight tweaks to apply.
Started 18 Oct
Previously expected 20 Oct

2 Aug 12:02:18
Details
2 Aug 12:02:18
We are planning an expansion of our VoIP services which will require the use of more IP addresses than we have told customers to allow through their firewalls, so have added additional IP ranges to the list.

We are not using these new IP ranges yet, but are giving advanced notice of the change to give customers time to update their firewall rules.

The list is at http://wiki.aa.org.uk/VoIP_Firewall

Started 2 Aug 11:50:35

9 Jul 15:50:00
Details
9 Jul 15:27:03
We are experiencing problem with VoIP platform, this is affecting calls for customers. We are investigating.
Update
9 Jul 15:38:20
Outgoing and 'internal' calls are OK - the problem is with inbound calls not working.
Update
9 Jul 15:42:38
Actually - outbound and internal calls over IPv6 were working, but over IP4 failing.
Update
9 Jul 15:43:10
The problem has been found. Calls should start working again shortly.
Resolution VoIP has been a bit off for a couple of days with two unrelated incidents. Not good. It looks like in both cases many incoming calls were failing. Yesterday was an issue with the code that steers calls - we made a change done in an emergency for a customer (who was trying to abuse SIP and not have to pay for lots of licence fees on his VoIP switch). The change worked for him, but broke many other customers (not all, and not our office). The testing done before this was deployed did not pick up the issue as the test calls were the type that worked (like calls to our office). It was spotted and fixed very quickly. We're trying to work out how we can create more comprehensive tests in future - we want to be agile and responsive to customer needs, but we need any changes to be robust and not cause problems. Today was very different. We noticed an issue on one called server impacting some SIP2SIM customers, so took it out of service to investigate. We have multiple call servers, and switching the active servers is a routine task that can be done in cases just like this to ensure service continues. Switching a call server out of service is done using a function on our control pages which has been tested many times in the past. Unfortuntely it pushes out the zone files for one of the domains as part of the process as it adjusts SRV records for the call servers. This is, again, normally quite safe. What has caught us out is that somehow the zone database was broken, missing some key records, so when it was pushed out the call servers vanished on IPv4. This caused yet more confusion as all of our test calls worked as they come from IPv6 equipment. This took several minutes to pin down and fix. We're now checking archives to try and find when and how the DNS records vanished. We're still investigating why the one call server is playing up, and hope to put it back in service later this evening.
Started 9 Jul 15:20:00
Closed 9 Jul 15:50:00

1 Jul 17:44:07
Details
1 Jul 17:44:07
We have been looking again in to CDRs. We have some new logic that should show correct I/C logs for calls to your number. The exception is where that is done as part of an also ring from another number that was called. It should also show calls to another A&A number (as free) with the exception of where this is an also ring from another number. I.e. the intermediate legs are not longer showing (they were not showing properly before). We believe the charging is correct.

As a separate issue, customers billed for use of BT lines we provide (which is only a few customers that have outgoing calls) have seen a lack of call bills for a few weeks. This should catch up (hopefully today) with any previously unbilled calls being billed.

Started 1 Jul 17:30:00

27 Jun 10:07:44
Details
27 Jun 10:08:52
It looks like we have not been recording logs of incoming calls that have been answered in the CDRs on our VoIP service. These have no call cost implications obviously. This has now been fixed and the logs should now show such calls. Sorry for any concern this may have caused.
Started 23 Jun 15:00:00
Closed 27 Jun 10:07:44

23 Jun 10:30:09
Details
23 Jun 10:29:01
We have added some quite sensitive checks to try and detect VoIP attacks, i.e. where someone has compromised your call server or obtained your SIP details and is using them.

These types of attacks can cause rather large unexpected bills. They are quite rare for us as we have a default low call rate allowed on international calls, but some customers with these rates set higher have had some attacks lately.

The new measures should not cause any problems, but we are monitoring the situation closely. If your account is locked down you will get a recorded message when trying to make calls, and an email. You can unlock the account from our control pages without the need to contact us first.

Obviously, if you do get locked down and a warning, please do check the call records to confirm this is not an attack.

We are able to adjust the thresholds we have set if we find it is too sensitive.

As these new features are only on the new call server (voiceless) we recommend people move to the new server. Once you have moved to the new server you will not be able to make calls via the old call servers so that the new security measures cannot be bypassed.

Started 23 Jun 10:00:00

10 Jun 20:01:12
Details
10 Jun 20:01:12
For customers on the current platform (voiceless) we are now sending emails when we see a new device (user agent) or IP address make use of your VoIP number credentials. This should help mitigate and detect fraud. You can change the setting to just check user agent (e.g. if using mobile or frequenctly changing IP) or disable it (though that is not recommended).

If you have an IP lock down, the warning is sent for any new IP/device that does not meet the IP lock down subnet but with a correct password, regardless of the warning settings.

Any questions please ask.

Started 10 Jun 20:00:00

6 Jun 18:33:22
Details
6 Jun 18:33:22
Junk callers are getting smart and calling from "real" numbers. We don't have a very big list of these yet but we have added a new option on the call control pages to allow screening against known junk callers. The suppliments the existing anonymous call reject options that we offer. The plan is that the recording of a monologue with the junk caller will be emailed to the Information Commissioners Office automatically after each call (as per section 32 of the PECR). We are enabling this basic screening on all new numbers, so do log in and disable under the ACR section of you do not want this.
Started 6 Jun 18:31:04

17 May 17:00:00
Details
17 May 12:02:10
We are running in to some problems calling some mobiles. This is be being worked on.
Update
17 May 15:00:27
A work around was deployed on the current call server (voiceless) shortly after posting, and has now been deployed on the old call servers as well.
Started 17 May 12:00:00
Closed 17 May 17:00:00

17 May 12:01:25
Details
17 May 11:26:59
Our old call server (due to be deprecated soon) has had some sort of issue this morning, and is being rebooted to try and clear the problem. Some customers reported they were unable to get incoming calls.
Resolution Restart completed quickly.
Closed 17 May 12:01:25

11 May 17:34:54
Details
6 Apr 11:43:17
We are working on changes to the source IP addresses used for SIP messages we send where we have authentication details to provide. The reason is that asterisk boxes cannot easily be configured to tell "peers" from "users" in order to decide if a challenge is needed. This has caused problems for customers using VoIP unauthenticated from our IPs and SIP2SIM authenticated as a user. The first stage of the change has been done today, and involves the source IPv6 addresses. For all authenticated IPv6 messages (i.e. those for which we expect a challenge) we are sending from 2001:8b0:0:30::5060:a000/116 whilst any unauthenticated are from 2001:8b0:0:30::5060::/116 As this is within the 2001:8b0:0:30::5060::/112 block we have advised for VoIP use, this should not need any firewall changes or config changes, but we are interested in any feedback on any issues encountered. The change for IPv4 will take a bit longer - as we are unsure if to try and free up space in the 81.187.30.110-119 range previously advised, or to allocate a new range for this. This only affects calls originating from the new "voiceless" servers, which includes all SIP2SIM, but affects all authenticated messages whether SIP2SIM or otherwise. Please let us know of any issues.
Started 6 Apr 11:00:00

11 May 17:34:19
Details
14 Apr 20:10:20
Work on the billing system has resulted in interim data and call usage bills today. These will have normal payment terms, and obviously mean lower charges on your next bill. If any customers need extra time to pay because these are interim bills, please contact accounts who can extend the terms on this occasion.
Update
14 Apr 20:20:46
We have extended the terms on these interim invoices by two weeks for those otherwise due this month.
Update
15 Apr 07:55:13
For the technically minded - what we were attempting to do was sort an issue where a SIM gets suspended on the date of the last bill, and so the suspend date and the billed-to date are the same but some usage has not been billed for that day. We had customer complaints about this and the fact that up to a day's worth of calls and usage were not billed. The fix was a tad overzealous. We think we have this sorted now though. I do apologise for any concern this has caused.
Started 14 Apr 20:09:03
Previously expected 15 Apr 00:09:03

12 Apr 08:42:39
Details
11 Apr 08:50:44
Customers using our VoIP services will be aware that we have reserved 10 IPv4 addresses for all of our VoIP control traffic. For our current platform "Voiceless" these are also used for the media (RTP) traffic. This makes firewalling simpler, etc. Customers using asterisk will know that the config for these can be somewhat complex, listing 10 hostnames each for IPv4 and IPv6 as the way asterisk works is to look up an IP for a hostname, pick the first, and check that against the request IP address. Asterisk really needs fixing. For voiceless we have been using two addresses 81.187.30.111 and 81.187.30.112 as well as IPv6 addresses 2001:8b0:0:30::5060::1 and 2001:8b0:0:30::5060::2. We recently tried a slight change on the IPv6 addresses, and this caused some issues. What we are planning to do now, for the "voiceless" call servers is use two addresses per server for each of IPv4 and IPv6. These shall be 81.187.30.111 and 81.187.30.113 for the A server and 81.187.30.112 and 81.187.30.114 for the B server. You do not need to know if A or B. The additional two addresses will be used as "source" addresses for any request from these servers to you that need authentication. This allows asterisk to be configured separately for authenticated and unauthenticated requests. Requests may also come from other addresses within the published block when test servers are used, etc. We are also making the corresponding change to IPv6 addresses using :1 and :3 for the A server and :2 and :4 for the B server. We may adjust which IPs are which server at a future date as we also have to consider how we expand beyond the two servers in use currently. These IPs will be accessible via DNS as a.voiceless.aa.net.uk and a.auth.voiceless.aa.net.uk, and so on. If your existing asterisk config is working as per the recommendations, no changes will be needed. The wiki will be updated to explain how you can use these changes.
Update
12 Apr 08:44:38

We have made changes this morning - these are slightly different to planned so as to allow for future expansion.

A.voiceless 81.187.30.111 and 2001:8b0:0:30::5060:1

A.Auth.voiceless 81.187.30.112 and 2001:8b0:0:30::5060:2

B.voiceless 81.187.30.113 and 2001:8b0:0:30::5060:3

B.Auth.voiceless 81.187.30.114 and 2001:8b0:0:30::5060:4

I believe all of the necessary DNS changes have been made to match and allow existing configs to work.

Update
12 Apr 17:56:53
We have seen some issues with calls to registered phones coming from the auth'd address and this is being looked in to now.
Update
12 Apr 18:46:08
We tracked it down - and was a slight error in this mornings config. IPv4 was all coming from the auth address even if no authentication required. This would have had an impact on some calls to some devices not working properly during today.
Started 12 Apr
Closed 12 Apr 08:42:39
Previously expected 14 Apr

10 Feb 14:00:00
Details
10 Feb 13:36:59
Some customers are experiencing problems making and receiving calls, this is being investigated.
Update
10 Feb 14:07:47
A particular type of VoIP configuration looks to be the cause of this. We are working on a fix.
Update
10 Feb 14:41:12
The affected configuration has been changed. The VoIP service should be back to normal, but we are monitoring the situation.
Closed 10 Feb 14:00:00

01 Nov 2013 11:00:00
Details
01 Nov 2013 10:44:13
We're experiencing problems with the C server. Ongoing calls should continue, but registrations will break which requires phones to log in again. This also affects the A server, as A routes calls through C. We're investigating.
Update
01 Nov 2013 11:18:03
Rebooting the C server. Ongoing calls through this server will be cut off. Sorry!
Update
01 Nov 2013 11:22:44
Now looking better. We are monitoring, but please let support know if you have any problems.
Started 01 Nov 2013 10:00:00
Closed 01 Nov 2013 11:00:00

7 Feb 16:10:16
Details
7 Feb 16:06:27
One of our VoIP servers is having problems with calls. This is being looked in to and is affecting some customers from making and receiving calls.
Update
7 Feb 16:07:10
The callserver has been restarted
Update
7 Feb 16:10:38
Calls are working again now. We'll investigate the cause of this.
Started 7 Feb 16:00:00
Closed 7 Feb 16:10:16

14 Dec 2013 17:00:00
Details
07 Dec 2013 11:16:12
During the coming week we are making a number of minor changes to our VoIP systems. These changes include both the call servers themselves (voiceless) and the back end database call routing servers and even changes on the control pages (clueless). None of these changes should impact existing VoIP customers, they are to allow a new service which we hope to launch next year. We are currently testing on our trial systems, which involves several levels of voice servers and database call routing servers which are not part of the live platform. The next step is testing on our office VoIP platform. This puts calls to/from our offices at risk from Monday, but is an important step before deploying on live systems. When we are happy with all of the changes we will introduce in to the live VoIP platform, one server at a time, in such that we can easily fall back to the old version if there are problems.
Started 07 Dec 2013
Closed 14 Dec 2013 17:00:00
Previously expected 14 Dec 2013

04 Nov 2013 16:56:16
Details
04 Nov 2013 12:13:28
We're investigating a problem with calls on the A and C VoIP server.
Update
04 Nov 2013 12:41:04
We have identified that the fault is being caused by VoIP software crashing by an obscure call set up configuration. Another update is due shortly.
Update
04 Nov 2013 12:51:59
We've pinned this down to a the actual Number that is triggering this problem, and are in the process of changing the config.
Update
04 Nov 2013 13:24:55
The config has been changed, but we are still investigating the underlying problem.
Update
04 Nov 2013 16:56:16
Service had been stable this afternoon, we're still investigating the root cause.
Started 04 Nov 2013 12:00:00
Closed 04 Nov 2013 16:56:16

09 Oct 2013 11:51:18
Details
05 Jun 2013 14:10:38

We are looking for more testers for the new VoIP platform. Eventually we'll move everyone over but we need people to test the new platform as much as possible before we do that. We have tested with a range of phones and the various features we offer.

http://aa.net.uk/telecoms-voiceless.html


26 Sep 2013 09:50:00
Details
26 Sep 2013 09:33:01
Customers are experiencing some VoIP calls failing. Were are investigating this.
Update
26 Sep 2013 09:57:46
This was affecting some customers on our A and C VoIP servers and has now been resolved. Customers on our new V servers were unaffected. More details about our new V server can be found here: http://aa.net.uk/telecoms-voiceless.html
Started 26 Sep 2013 09:15:00
Closed 26 Sep 2013 09:50:00

14 Sep 2013 09:33:21
Details
14 Sep 2013 09:30:29
We have seen some issues in the last few minutes that may have caused calls to drop. The matter is being investigated.
Resolution We found the underlying cause, and it was affecting some outgoing calls. This has been rectified now.
Started 14 Sep 2013 09:17:00
Closed 14 Sep 2013 09:33:21

13 Aug 2013 15:14:13
Details
13 Aug 2013 14:55:16
Some calls are failing at the moment on our voip platform. We are investigating.
Update
13 Aug 2013 15:14:04
The problem has been found, and calls are working as normal now.
Closed 13 Aug 2013 15:14:13

11 Jul 2013 19:06:07
Details
25 Jun 2013 12:55:49

We're investigating a problem with one of our call servers.

Resolution

This has been fixed by fire-walling a remote attacker which our usual monitoring did not pick up and block automatically.

Started 25 Jun 2013 12:50:00

27 Jun 2013 09:59:48
Details
27 Jun 2013 09:54:00

There have been a few cases this morning with some call drops, we believe we have identified the issue. Sorry for any inconvenience.

Resolution

This looks to be sorted now.

Started 27 Jun 2013 09:00:00
Closed 27 Jun 2013 09:59:48

19 May 2013 09:37:11
Details
19 May 2013 09:40:24

A database issue this morning has affected incoming calls due to registration timeouts. This has been corrected and registrations are now working correctly.

Started 19 May 2013 08:12:10
Closed 19 May 2013 09:37:11

11 May 2013 21:31:24
Details
11 May 2013 21:30:30

We have changed centrex dialling such that calls to 101 and 111 will no longer be recognised as centrex dialling.

I.e. if you have three digit local (centrex) dialling, and extensions 111 and 101, we suggest you reassign these internal numbers.

101 and 111 now route to a carrier for non emergency police and HNS direct.

As you know, you cannot use extensions 112 or 999 for internall calling anyway (emergency services numbers).

Sorry for any inconvenience caused.

Started 11 May 2013 21:28:48

07 Mar 2013 11:13:11
Details
07 Mar 2013 11:13:11

We recently added a box on our Telephony price page where you can put in a phone number and it will look up the cost when calling via our VoIP service. See: http://aa.net.uk/telecoms-prices.html

Started 07 Mar 2013 11:00:00

20 Feb 2013 12:14:17
Details
20 Feb 2013 12:05:15

There has been an issue with the main VoIP call routing database which means we have had to restore the database from a copy taken early this morning.

Any changes to call routing, or other settings on VoIP numbers made today will need to be checked and reentered.

We apologise for any invonvenience caused.

Update
20 Feb 2013 12:08:48

While this is updating, some people may not get call recordings or voicemails emailed. The restore should be complete in a moment.

Resolution

The restore has been completed.

Started 20 Feb 2013 12:00:00
Closed 20 Feb 2013 12:14:17

05 Feb 2013 22:38:18
Details
05 Feb 2013 14:08:00

We'll be rebooting our core VoIP server this evening. It shouldn't be down long, although it'll break calls in progress when it happens.

We will try and make sure that there are no calls in progress when we do this, but if not possible we'll do it around 22:30.

Update
05 Feb 2013 22:38:49

This was completed successfully.

Started 05 Feb 2013 14:04:44 by AAISP Staff
Closed 05 Feb 2013 22:38:18

31 Jan 2013 18:21:35
Details
31 Jan 2013 18:21:35

We have reduced rates to major UK mobile networks to 5p/min (+VAT)

Started 31 Jan 2013 18:00:00

20 Nov 2012 15:10:41
Details
19 Nov 2012 22:11:16

Some users will be seeing problems with their SIP phones/devices not registering against registrar.aasip.co.uk - we are investigating this at the moment.

Update
19 Nov 2012 22:25:38

We may have tracked this down - phones should be able to register ok now and we're monitoring the situation.

Update
19 Nov 2012 22:36:29

VoIP does appear to be stable again now.

Update
20 Nov 2012 14:31:55

The service was stable over night, and has been fine today.

Update
20 Nov 2012 15:10:21

This problem just returned. Back now.

We're getting closer to finding the cause.

Update
20 Nov 2012 15:10:41

Service stable again now.

Started 19 Nov 2012 22:00:00
Closed 20 Nov 2012 15:10:41

23 Nov 2012 09:00:00
Details
20 Nov 2012 14:31:12

In light of last night's problems with VoIP, we have made changes to our SIP platform to make debugging easier in future.

The changes require a full restart to go live, so we will be carrying out this restart out of hours on Thursday evening at 23:00.

This affects all of our call routing too, so will drop calls made through the 'A' server and via IAX2 as well as SIP. Phones will need to re-register.

The outage is not expected to last longer than a couple of minutes, and if anything goes wrong we will roll back the changes.

Sorry for the short notice.

Update
22 Nov 2012 23:07:00

Restart is going to be a little later than anticipated. Sorry, won't be long.

Update
22 Nov 2012 23:29:57

All done. Calls testing and working.

Sorry for any disruption.

Started 22 Nov 2012 23:00:00
Closed 23 Nov 2012 09:00:00
Previously expected 23 Nov 2012 09:00:00

17 Nov 2012 12:00:00
Details
17 Nov 2012 11:19:25

We have reports of issues with incoming and outgoing calls and are investigating now.

Update
17 Nov 2012 11:23:40

Not sure of cause yet, but services started working again after restarting processes.

Started 17 Nov 2012 09:45:45
Closed 17 Nov 2012 12:00:00

14 Sep 2012 11:00:18
Details
14 Sep 2012 10:46:44

We currently have a call routing problem on our VOIP platform, caused by a change made this morning (that was tested first - this is unexpected).

The change is being rolled back now.

Sorry for any inconvenience.

Update
14 Sep 2012 11:00:39

This has now been resolved.

Started 14 Sep 2012 10:40:00
Closed 14 Sep 2012 11:00:18
Previously expected 14 Sep 2012 10:50:00

13 Aug 2012 15:32:41
Details
13 Aug 2012 15:26:43

Some customers are experiencing audio breakup on VoIP calls through our VoIP service. This is being investigated at the moment.

Update
13 Aug 2012 15:34:30

This has been resolved.

Started 13 Aug 2012 15:15:35
Closed 13 Aug 2012 15:32:41

06 Mar 2012 14:50:16
Details
06 Mar 2012 14:47:17

We are currently looking in to a problem with VoIP calls not being routed. This is affecting inbound and outbound calls.

Update
06 Mar 2012 14:50:30

Calls are working now

Resolution

We're not yet sure what caused this, but will continue to look through our logs etc.

Started 06 Mar 2012 14:47:16
Closed 06 Mar 2012 14:50:16

14 Feb 2012 20:42:34
Details
14 Feb 2012 19:21:44

Sending of SMSs is not working at the moment, either from our notification systems (eg when a line drops) or from customers sending via our website or 'curl'.

 

Update
14 Feb 2012 20:42:34

We believe we have fixed this, and are monitoring the situation now.

Started 14 Feb 2012 19:18:18
Closed 14 Feb 2012 20:42:34

14 Feb 2012 13:05:28
Details
14 Feb 2012 12:35:43

Phones registered to our 'C' server are losing registration once their registration times out. We're investigating.

Update
14 Feb 2012 13:05:34

Now fixed.

Closed 14 Feb 2012 13:05:28

17 Jan 2012 14:55:00
Details
17 Jan 2012 14:55:47

One of our upstream carriers for VoIP is having a network problem and we have 60% packetloss to them.

This will cause VoIP problems for some calls and customers.

We expect this to be resolved quickly

Update
17 Jan 2012 15:00:19

Back to normal now

Resolution

Problem resolved on carriers network

Started 17 Jan 2012 14:50:00 by AAISP Staff
Closed 17 Jan 2012 14:55:00

28 Dec 2011 11:00:00
Details
28 Dec 2011 08:38:53

There is a major issue with one of our carriers affecting some incoming calls and text messaging. They are working on the issue now.

Engineers are on site now.

Update
28 Dec 2011 10:45:12

OK switch in place but some things still to be finished.

Update
28 Dec 2011 10:59:40

Looks like things are working now.

Started 28 Dec 2011 04:41:00
Closed 28 Dec 2011 11:00:00

03 Oct 2011 09:08:52
Details
03 Oct 2011 09:08:28

As you know we have multiple call servers, including an "old" one that is used by a few customers that still use NAT or IAX.

There is a setting to control this which staff can adjust. It defines which call server you are using for a specific number.

Up until now this has not been checked for outgoing calls. However, the "old" call server cannot do the same level of checking as the new call server (e.g. IP address lockdown), and it looks like this has left a possible loophole allowing calls made using the "old" call server for numbers that are configured for the new server.

We have updated the system to disallow this. If you are set to use the new calls servers (as all new numbers are) then you will not be able to make use of the "old" call server.

Staff are monitoring the logs to see if this happens so they can contact customers. However, if you have problems making calls today please contact support.


02 Oct 2011 13:28:43
Details
02 Oct 2011 13:28:43

We are starting to set warning emails based on VoIP usage. 

On the control pages, a VoIP number has a 'bill warning' amount set. When this amount is reached we'll email the email on the number and on the login it's associated to.

The default for new numbers is £10, for number who spent more than £10 in September we've set the level to 1.2 times Septembers level.

For more information on VoIP security please see this wiki page:

http://wiki.aaisp.net.uk/index.php/VoIP_Security

This feature does not cut the service off.

Started 02 Oct 2011 13:24:20

30 Sep 2011 13:16:41
Details
29 Sep 2011 13:14:17

Users on the A call server may need to re-register their phones.

This was due to a change made to fix a problem where password changes were not being applied to the A server without manual intervention. Although that problem has been fixed, it's had the side effect of invalidating existing registrations which, due to the nature of some phones, requires the users to re-register or reboot the phone themselves.

Sorry for any inconvenience.

Update
30 Sep 2011 10:14:41

Seems that some customers have had ongoing problems with registrations on the A server.

We're investigating.

Update
30 Sep 2011 13:16:51

This should be fixed now.

Closed 30 Sep 2011 13:16:41

13 Aug 2011 18:30:00
Details
13 Aug 2011 18:25:49

Seeing some issues so planning to reboot the primary call server dropping calls in progress.

Started 13 Aug 2011 18:25:23
Closed 13 Aug 2011 18:30:00

13 Aug 2011 18:25:23
Details
13 Aug 2011 18:29:27

Seeing some issues so planning to reboot the primary call server dropping calls in progress.

Started 13 Aug 2011 18:25:23
Closed 13 Aug 2011 18:25:23

11 Jul 2011 12:42:40
Details
11 Jul 2011 12:05:35

Some customers (specifically those with a few also rings) are getting delays on inbound calls.

We're investigating.

It's occasionally manifesting itself as a silent call - this is where the caller has already hung up by the time the call connects.

Update
11 Jul 2011 12:43:34

Should now be fixed.

It was related to last week's 999/112 address info changes.

Started 11 Jul 2011 08:00:00
Closed 11 Jul 2011 12:42:40