Status  >> VoIP

Order posts by limited to posts

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

14 Apr 20:10:20
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

6 Apr 11:43:17
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

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

08 Jul 2011 19:03:25
Details
08 Jul 2011 19:01:10

As I am sure you are aware, our control pages allow you to enter location details for use in the event of an emergency call (999/112).

To date this has been an issue with some of the number blocks we have, and the details have not been updated in to the BT database to pass to emergency services in all cases. Obviously we have made this clear to you on the control pages.

However, I am pleased to say that due to a sort of phone number NAT we are now able to do this for all numbers. Any numbers we cannot update are allocated a special additional number (at no charge) which is just for use with 999/112. It is what is sent if you call 999 or 112 and starts 0200.

We hope to resolve the underlying problem with updates on all number blocks eventually, but this is a practical interim solution to ensure location data can be passed.

I urge all users of our VoIP servcies that use the service from a fixed location to update your location details on the control pages. This could save your life one day.

Started 08 Jul 2011 19:00:00

08 Mar 2011 14:11:30
Details
08 Mar 2011 14:05:53

New recorded calls were declined for a few minutes. It's now fixed.

Ongoing calls, and all calls without call recording enabled, don't appear to have been affected.

Closed 08 Mar 2011 14:11:30

03 Mar 2011 15:45:00
Details
03 Mar 2011 16:25:29

One of our telephony carriers had a network problem this afternoon which affected some VoIP calls and mobile SIM services.

 

Resolution

The problem has been resolved (sorry for the delay in us posting this), and their initial investigation looks to be some kind of DDOS attack.

Started 03 Mar 2011 15:30:00
Closed 03 Mar 2011 15:45:00
Cause Carrier

10 Feb 2011 17:00:00
Details
10 Feb 2011 11:39:33

Our main SIP server had a brief problem with setting up recorded calls.

This resulted in new calls being dropped, although ongoing calls seemed unaffected.

Now fixed - sorry for any inconvenience.

Closed 10 Feb 2011 17:00:00

13 Feb 2011 18:14:00
Details
09 Feb 2011 17:40:54

We have a list of minor niggles that has built up and we are planning to work on these this weekend. Most of the work will, of course, be on out test platform, but as we complete each stage we will be loading on the live VoIP system for final customer testing and confirmation.

This should not cause any problems, obviously. But there is a risk of issues arrising.

In general, the way the new VoIP system works, if there are problems then calls in progress continue but don't get charged.

Part of this work is testing IPv6 VoIP phones.

Update
12 Feb 2011 13:47:21

Work has been done today on the test and backup server. We plan to apply these changes to the live server this evening.

The main changes have been down to slight quirks in the operation. e.g. voicemail not working unless call recoridng email also set; calls from some types of gigaset not gving right ring tone; Quirks when two simultaneous voicemails apply on one call; and such things.

Tomorrows work is going to be related to IPv6 interworking.

Update
12 Feb 2011 17:22:02

OK minor change to the syslog caller display format.

Resolution

We were unabkle to complete the IPv6. We will be testing some IPv6 work on the test server during the week.

Started 12 Feb 2011
Closed 13 Feb 2011 18:14:00
Previously expected 13 Feb 2011 23:59:59

26 Jan 2011 16:07:27
Details
26 Jan 2011 15:35:53

We had a minor issue routing calls on our SIP platform a few minutes ago.

It should be back to normal now, but we're investigating.

Update
26 Jan 2011 15:44:35

We're rebooting c.speechless, our main SIP server.

Sorry for the inconvenience.

Update
26 Jan 2011 16:07:48

There were some further problems. Now fixed.

Started 26 Jan 2011 15:32:02
Closed 26 Jan 2011 16:07:27

26 Jan 2011 11:13:26
Details
26 Jan 2011 10:14:13

AQL, one of the carriers we use for routing VoIP calls, is having some problems this morning.

We have changed routing for outbound calls to route via a different carrier for the moment, but some inbound calls may still be affected.

They're working to fix the problem as soon as possible.

Update
26 Jan 2011 11:13:36

This problem has been resolved.

Started 26 Jan 2011 10:11:00
Closed 26 Jan 2011 11:13:26

10 Dec 2010 18:46:16
Details
10 Dec 2010 11:50:04

We've had a couple of moments this morning where VoIP calls had had problems. We are investigating and have clues as to what has been causing this. Calls are working at the moment and it's being monitored closely by staff.

Update
10 Dec 2010 18:46:36

We believe we have found the cause of the issue and have deployed a work around and active monitoring.

Started 10 Dec 2010 11:15:00 by AAISP Staff
Closed 10 Dec 2010 18:46:16

02 Dec 2010 10:11:19
Details
02 Dec 2010 10:11:19

We are keen to test IPv6 VoIP services, but initial testing has found a slight flaw in the logic!

Our SIP server handles IPv6, but it passes RTP between enpoints to negotiate for themselves. That works fine for codecs as we say customers have to support alaw and all carriers support alaw, so unless other preferences are agreed it is alaw.

However RTP pass-through does not work well for IPv6. In theory each end is told what to send to the other. And if one end says "send me IPv6" the other should. The problem is that the other end does not understand IPv6 and so the call fails. Sadly our call carriers are not IPv6 yet, so even if we support IPv6 and our customers support IPv6, it won't work.

To solve this we are working on a new generation of call server. It will have a simple back to back media gateway to allow IPv4/6 mapping. This may be a media forwarding box, or a special case of our firewall/routers creating customer mapping sessions. We have not decided yet.

However, we just want to re-assure customers we are commited to full IPv6 support for VoIP services.


30 Nov 2010 16:11:41
Details
30 Nov 2010 16:14:18

Voicemail greeting messages were broken briefly earlier (around 16:04), resulting in silence when a call got to voicemail. It has been fixed. We're investigating the cause. Sorry for any inconvenience.

 

Started 30 Nov 2010 16:04:00
Closed 30 Nov 2010 16:11:41

29 Nov 2010
Details
23 Nov 2010 15:06:04

We just had a problem with VoIP calls being unable to be made - this affected accounts that have call recording enabled. (This also happened earlier this morning too) The cause of the problem will be investigated by our developers, we do apologise.

Update
24 Nov 2010 11:44:29

This happened again just now for a few minutes. Calls are working again and we're investigating. Sorry for the inconvenience.

Update
24 Nov 2010 12:17:05

We are still seeing some issues today, but have an idea what may be causing it at last. We'll update this evening.

Update
24 Nov 2010 17:36:52

We have made a number of changes which should resolve the issue. We'll post another update if there are more problems.

Update
25 Nov 2010 11:03:05

We had a problem again at 10:45 - now resolved, but clearly still some issues.

The main problem with calls recordings being delayed seems fixed now, which is good, but we are hitting something new now.

Being investigated.

Update
26 Nov 2010 16:04:40

This happened again at around 15:25. We're still investigating.

Update
29 Nov 2010 10:20:23

We are monitoring the situation still. Seems OK all weekend.

Started 23 Nov 2010 14:58:31 by AAISP Staff
Closed 29 Nov 2010

24 Nov 2010 17:35:57
Details
24 Nov 2010 17:35:57

It seems the default recording format for new numbers (voicemail and call recordings) was set to MP3 by mistake. It is now WAV for all new numbers.

The MP3 option is the lowest quality option, and not the smallest size, so we would suggest anyone using MP3 consider the options and change if they wish. We have added a new options as well.

The options are:-

WAV: This is the largest file, with 8KHz 8bit alaw mono (voicemail) or stereo (recording). It is the best quality and is directly the data from the telephone network.

ZIP: You can opt for the WAV file zipped (may save 40% of file size)

OGG: OGG/Vorbis is the best trade off for quality and size that we offer

MP3: Provides compatibility with many players and is a lot smaller than WAV, but not as good quality as OGG or WAV