Interesting that one of my services via ISS satellite and RSP SkyMesh, has survived the whole time.
The others with Telstra ... not so lucky.
Extensions coming back on now
We reach them over WAIX and apart from a short blip are online and working normally. We have another Telstra DSL service that can't register though.
No registrations for us at the moment either
Extensions connected over Internode back online but not Telstra ADSL or Optus 4G.
I've got desk phone extensions registered for outgoing but no incoming yet and mobile cloud phone not registering.
I can confirm my experience is that call forwarding from the control panel appears to be working, however registered extensions do not receive calls routed via either standard geographic DID's or 1300 numbers.
My trunk now appears to be working. Calls coming in.
Nothing here yet, not even reroute (line hunt) to mobile numbers.
Working on iinet DSL but not on Telstra Fiber/DSL, both in Melbourne.
No extensions are registering here yet either. However things seem to be improving: as compared to before where incoming calls would die and the back-end was unreachable, now I can actually log-in to the back-end, and the DIDs appear to be ringing (from the perspective of the caller obviously, nothing is happening on our end) � eventually going to voicemail which then gets forwarded to our email as usual.
Far out I wonder who's behind the DDOS?
No extensions are registering here yet either. However things seem to be improving: as compared to before where incoming calls would die and the back-end was unreachable, now I can actually log-in to the back-end, and the DIDs appear to be ringing when called � eventually going to voicemail which then gets forwarded to our email as usual.
^ x2
Inbound calls are working for me now :)
Lost all registrations now
All extensions and inbound calls have been offline for 4+ hours at this point. Made for quite a Monday!
No reply to my 1-week-old ticket or today's outage ticket either.
No doubt everything will come good.
Update
Please change your registration address to 103.193.167.89
This is a temporary measure until we can get the DDoS protection in place.
We are still getting attacked on the sip urls.
Edit: This is only for those who can't register to their extensions. If you are connected to sip.telecube... and registering ok then leave the settings as it is. You will be connected through one of the peering networks.
What determines how often my Yealink handsets try to re-register as an extension with Telecube or do I have to go into each handset and "confirm: for it to register.?
Please change your registration address to 103.193.167.89
No registration on this for me either
Please change your registration address to 103.193.167.89
Sorry, that doesn't work: Register Failed (says a Yealink 41P).
No registration on this for me either
Same, no registration (on Telstra ADSL).
Please change your registration address to 103.193.167.89
Yep that fixed the problem for me running my PBX from AWS host. Finally getting some incoming calls for the day!
What determines how often my Yealink handsets try to re-register as an extension with Telecube or do I have to go into each handset and "confirm: for it to register.?
Registration needs only to be done once, but you set the renewal time for it to be refreshed in the extension section on your device under SIP Expiry with the desired number of seconds.
Please change your registration address to 103.193.167.89
I can ping the IP from Telstra fiber but no registration yet; comes back with request timeout 408.
Ditto
up and running on Telstra services now
Please change your registration address to 103.193.167.89
Sorry, that didn't help.
Still can't register.
How do I do this? � change the registration, that is
Sorry, that doesn't work: Register Failed (says a Yealink 41P).
Same on a Yealink T23G. All the possible options fail for me.
WAIX registrations to telecube dropped ~2:45.
We can ping but can't register it seems
Edit: Working on non-hardcoded IP now it seems
I can see the congestion is slowly easing for the main IPs.......
Can no longer register handsets on Internode via host name or the temp IP. Telstra ADSL and Optus 4G seem to be up though.
We've just been attacked on 103.193.167.89 which I only posted here. It's been null routed.
John, I was going to say they seem to be watching WP.......
Just came back up, Telstra Cable in Leichhardt, NSW
All extensions registered and working now.
We've just been attacked on ...
Hi John � have you spoken to James at Micron21?
Yep, we're getting organised with that now.
All good again. Thanks for the very quick response to this.
We are still getting attacked on the sip urls.
I don't understand. URLs end up going to an IP address anyway.
Edit. Oh.. different than the DNS record for .net.au. Didn't notice at first.
We've just been attacked on 103.193.167.89 which I only posted here. It's been null routed.
They could be doing a network scan on your (reasonably) well known subnets and attacking whichever port responds.
Any possibility to whitelist from your ACLs? (assuming all this is not from a customer)
Confirmed as well online here on Telstra ADSL2
Confirmed as well online here on Telstra ADSL2
Still not for me also telstra brisbane
Cloud soft phone working on Telstra 4G � called a mobile and it was clear.
This is to the whole forum: I love telecube but sometimes things do go south.
Any recommendations for a secondary standby VOIP provider to be used as a backup? Ideally something with minimal or $0 ongoing costs that we only pay per call... (I'm probably asking for too much).
It's not going to bring back the fallen over DIDs but at least people in the office will be able to make outgoing calls.
Any recommendations would be welcome.
By definition a DDOS (distributed denial of service attack) is not from one person/origin as the name suggests, which is part of the problem and issue with successfully mitigating such attacks, so therefore selectively white listing ACL would not do anything here.
It really can be seen as a reverse domino effect, whereby the concentration of traffic/request/flooding is targeted to an exposed endpoint (by virtue of the service), taking that system offline. Mitigation attempts would then be passed up the chain, but if the transit providers up the chain can't handle the inbound traffic, or effectively filter/route it, they need to stop advertising the addresses or range being attacked (null route) � hence Telecube would then drop off the air.
It will be interesting (maybe not the right word to describe this) to see how this crappy game of cat-and-mouse continues :(
All the best John & Team.
We're back too...
As suggested above, it would be great if Telecube had a status page like : http://status.status.io/ or even a Twitter feed for alerts.
It solves that first step of troubleshooting the voip outage, discovering if is a internal network / isp or voip provider outage.
Although, customers can setup their own monitoring of this or other SAAS products, by using Pingdom or Statuscake etc, to monitor the Sip server.
Any recommendations for a secondary standby VOIP provider to be used as a backup? Ideally something with minimal or $0 ongoing costs that we only pay per call... (I'm probably asking for too much).
Freshtel provide calling to landlines and 13/1300 numbers for a flat 10c per call on their Free (prepaid balance) offering.
MyNetFone have a WhirlpoolSaver Plan here � https://www.mynetfone.com.au/
With that all being said, let's dig in and get around John and team � they are no doubt working tirelessly to get this resolved.
My .com.au registrations are also back
Sweet, thanks. Gonna give Telecube a try. What what the actual down time for the port? Few mins/hours/days?
My port only took a couple of days. The day before the port, I received an email from Telecube with a date and time....and a reminder get the extensions, queue etc set up. All very efficient!
My port only took a couple of days. The day before the port, I received an email from Telecube with a date and time....and a reminder get the extensions, queue etc set up. All very efficient!
Yeah, I can attest to the porting process with Telecube being great. Once the port is accepted, they pre-load the numbers into their system so you can pre-configure your extensions/queues/etc... while you wait for the port to finish.
On the day of the port you shouldn't really see anything more than 5 � 10 mins of downtime when it's being switched.
Thanks for that. Sure, I wish I could help somehow as well. Just as DDoS is distributed, it would be nice if there was a way to somehow contribute to the mitigation of it in a distributed way to stop the a/h's.
This is to the whole forum: I love telecube but sometimes things do go south.
Any recommendations for a secondary standby VOIP provider to be used as a backup?
I highly recommend Pennytel.
Looking at their web site it appears they're being bought out by MyNetFone.
#sarcasm
there are more appropriate forums to talk about backup providers, i think its bad manners to do so here.
If one wants a stable/reliable provder as a backup, wouldnt you choose that provider in the first place :)
at least people in the office will be able to make outgoing calls.
For an office it is a must you have at least one backup VSP. We use two, one TC and the other one is a global provider which gives us a lot of flexibility. All of our DIDs are with TC which unfortunately means no incoming calls in an event like today's.
Update
We've support from upstream which is keeping the attack under control and we're implementing a permanent DDoS protection solution which should be in place over the next 48 � 72 hours.
I'm really sorry about the issues today and thank you for your patience.
All of our DIDs are with TC which unfortunately means no incoming calls in an event like today's.
Forward them to another providers DID?
Pretty sure the DIDs come over on a seperate handoff to customer SIP traffic, and if it was outgoing over PTSN it might not of been effected either
Forward them to another providers DID?
Couldn't even get to TC's portal while the attack was in full swing ..........
I'm really sorry about the issues today and thank you for your patience.
Thanks for keeping us in the loop. It's the reason we support you.
I'm really sorry about the issues today and thank you for your patience.
Good learning experience John! It just means that you will continue to improve the level of your service. And I'm sure you have enough goodwill here to ride this out.
Things could be worse. I was just thinking of when I lost my landline last year. Phone call to iiNet who logged a fault with Telstra. From memory it was 3 days to get fixed and there sure weren't any ongoing updates.
I'm really sorry about the issues today and thank you for your patience.
Really appreciate your efforts to restore services John.
Any chance you could decouple the portal from the sip cluster so that we could at least divert calls in a similar event?
I'm really sorry about the issues today and thank you for your patience.
Thank you John. Like everyone else here, really appreciate your efforts today.
Thank you John. Like everyone else here, really appreciate your efforts today.
Thank you to John and the Telecube team.
Any chance you could decouple the portal from the sip cluster so that we could at least divert calls in a similar event?
They don't seem to be in the same location. According to my tracert they are not even on the same continent.
Name: sip.telecube.net.au
Address: 103.193.167.41
Name: telecube.com.au
Address: 54.200.103.143
Aliases: www.telecube.com.au
Interesting DDoS to take out the web page and the SIP server at the same time on opposite sides of the globe.
S.
Interesting DDoS to take out the web page and the SIP server at the same time on opposite sides of the globe.
manage.telecube.com.au is on a similar IP range to SIP.
They don't seem to be in the same location.
I think he might have meant SIP and portal i.e. the manage subdomain:
[matt@sws-per-dev1 ~]# host manage.telecube.com.au
manage.telecube.com.au has address 103.193.166.39
Matt
Anyone have a fun day?
apart from phones going out, before lunch I also lost,
- online shopping platform due to database malfunction
- half of my remote P.O.S. appliances collapsed after an application update
- my NZ office shipping system keeled over
coffee machine unscathed, nothing much else could go wrong.
Job for tomorrow, send memo to my programmer, dont break things when our phones dont work.
manage.telecube.com.au is on a similar IP range to SIP
Thanks
That explains it. I hadn't noticed the manage.
And thanks to Matt too.
S.
So I'm still getting registration failures, I can ping sip.telecube.net.au fine.
I see a number of people were saying they could register again, anyone on Telstra ADSL able to register?
Same same. Extensions in Australia are registering fine. Can't register from Japan however.
All my extensions are good, I am connecting on TPG ethernet, and registering to sip.telecube.com.au
Yup, can confirm international connectivity issues.
When I switched my device to VPN via Australia, no problems. When I try it from a Japanese connection, it fails to connect. Must be something to do with the DDOS mitigation.
I'm on a Telstra Australia ADSL IP l and can't register, so I suspect they are blocking my IP for some reason.
It not surprising that they are blocking IP from outside australia, given the DDOS.
Not sure why they are blocking local IP's unless there is some DDOS being spoofed from it or something.
I'm still not able to register. I'm on Telecube ADSL.
I'm still not able to register. I'm on Telecube ADSL.
LOL that's pretty funny, blocking from their own ADSL service.
Maybe those that can register are coming via peering not over normal inbound links.
I'm not going via any peering, so maybe that why I'm blocked still.
I'm still not able to register
I'm on a Telstra Australia ADSL IP l and can't register
Can you email support please with your details so I can have a look?
I'm on a Telstra Australia ADSL IP l and can't register, so I suspect they are blocking my IP for some reason.
Have you set the expiry time on your equipment to less than 180 seconds? I know other VSP's like Pennytel implemented DoS protection blocks if you attempted to renew registration at less than 5min intervals.
Can you email support please with your details so I can have a look?
Hi,
Email sent with tracert, IP address and mobile phone contact details.
Happy to work with you to resolve.
Regards.
Have you set the expiry time on your equipment to less than 180 seconds? I know other VSP's like Pennytel implemented DoS protection blocks if you attempted to renew registration at less than 5min intervals.
Registration refresh time is 180s, which I got from their wiki.
edit Changed to 360s made no difference.
LOL that's pretty funny, blocking from their own ADSL service.
I'm using an unlocator service so maybe that's throwing a spanner in the works. I'll send an email John, but it's not really urgent.
4 extension all on-line but one in the US dropped about 1.30pm today and is still out. 3 of these are registering with .com and 1 with .net.
3 of these are registering with .com and 1 with .net
.com and .net are resolving to the same IP for me?
com and .net are resolving to the same IP for me?
.net is the old platform and I haven't seen its resolution vary. .com is the load balancing one and varies with servers. It is normally different to .net but today traffic was probably moved back to the .net platform. for a while.
Any recommendations for a secondary standby VOIP provider
Prolly a bit OT. I used to use SipMe as my backup VoIP provider for years, but too many people did the same thing! They went broke. Factortel tried to capitalise on the SipMe demise, I cannot too strongly NOT recommend them.
FWIW. I'm currently using Maxo and PennyTel as backups, just hope that the PennyTel plans migrate to MNF without too much agro.
HTH, G20.
I noticed my registrations still hadn't happened automatically after the issues today (both extensions were "Failed" still, some hours later). So, I logged in to the portal to see if I could troubleshoot, and generated a password on one of the extensions and updated the registration on my Gigaset to match, and it connected straight away on that extension. I repeated the same on the other extension, and a minute later both were happily registered and working again.
It might be worth trying, if people are still having issues connecting.
Also, given todays issues, I have set my incoming DID as Line Hunt (rather than queue). Normally my Gigaset voicemail will collect the call well before diverting, but atleast if it loses registration for some reason, hopefully the DID will route to my mobile instead. My thinking is that it will be a fallback position, without having to try to gain access to the TC portal on the fly.
I believe that we are all very fortunate to be with a provider who reacts so quickly to resolve a problem of this magnitude and is already working to strengthen the platform against future disruptions.
Maybe the best way we can work to ensure greater stability and redundancy is to simply give John more business- his commitment and honest, open attitude deserve it.
I'm using an unlocator service so maybe that's throwing a spanner in the works.
It was indeed this. I removed the proxy DNS settings in the router, rebooted and got immediate registration.
The FA Cup is coming up this weekend John!! I hope this will all settle down by the end of the week.
Edit. Actually I just realised I won't want to be getting any phone calls during the match anyway, so maybe it's a good thing?
Actually I just realised I won't want to be getting any phone calls during the match anyway
:-)
Ported a DID in from another VoIP provider today � have to say the functionality on the control panel is quite extensive.
One small problem though. I can ring the DID from a Telstra mobile, but not Optus or Vodafone. Do things like this generally take time to "propagate", for lack of a better word?
I can ring the DID from a Telstra mobile, but not Optus or Vodafone
Sometimes some networks aren't updated properly when a number ports, please email support with the details and we'll get it checked out.
I've just returned to the office to try and get going for tomorrow and power cycled my whole network.
All phones are set to register to .net.au and are all configured the same except for the username and password.
Really weird � only 1 out of the 6 handsets has successfully registered. All the others report "Failed � No response"
Any help?
Any help?
Email support please .. I'm here now and I can have a look at your extensions
I'm here now and I can have a look at your extensions
Try and get this kind of service from Telstra. Thanks John, email sent
Little confused � haven't been following the thread for a while.
Are we supposed to register to .com.au or to .net.au?
Anyone able to connect from overseas? Am in India and not able to connect to sip.telecube.com.au
Anyone able to connect from overseas? Am in India and not able to connect to sip.telecube.com.au
Same here for overseas. In Japan, I can connect through NTT Docomo mobile network but Softbank ADSL is a no go.
Anyone able to connect from overseas?
John has told me they will have to continue to block international traffic for a day or so, until they get the DDoS protection in place.
Edit: This also includes people in Australia who use a proxy ip address.
Down again?
Got reg but can't place or receive calls or get to portal
The web site comes up but cant login....:-((
My DID's ring to the IVR but no extensions ring and when a voicemail picks up it doesn't play the greeting
I got in to the web site, but it shows all my extensions as 'inactive' of which they aren't, and weren't when I first logged in.
And only 2 mins prior showed me as off-line, of which I had registration, but now flashing red as off-line.
Not bothered at this time of day.
John & the team sure are doing a top job trying to get it all sorted out.
Edit: Slight addition to first comment. :)
Top marks TC.
Edit 2: All extensions are showing as active again, and back online accordingly. As at 713am.
Amazing service John.
Anyone able to connect from overseas? Am in India and not able to connect to sip.telecube.com.au
Same here, unable to register from Switzerland (sip.telecube.net.au )
Not bothered at this time of day.
Some of us have businesses that start trading at 6am
John & the team sure are doing a top job trying to get it all sorted out.
No doubt and getting support from the man himself at 10:30 at night is a credit to the business
Things seem to be recovering slowly now. Perhaps a change was made early this morning. Just started freaking out when I spent all night testing things to a working point after copping flack from my superiors, and returning this morning to find I'm back to square one.
Main thing is to get to the portal where I can change routing to a mobile if all else fails which is definitely working now.
Thanks TC!
Telecube is down again. Someone wants revenge!
edit: forward all calls to my mobile. Hopefully that worked.
Yep spoke too soon. At least I got diversions working
Sorry guys .. working on it
Same here. (Most) extensions registering but call queues ringing out and going to voicemail. Have changed DID to forward to mobile temporarily which seems to be working.
Ditto Exactly.
also The Cloud Softphone clients cannot register.
Looks like no softphones can register. Tried Zoiper, Softphone and MicrSIP. All dead. Oh well, as long as the landlines continue to chug along, no probs...
John, You're killing us. I got no work done yesterday because every site was down and now it's dragging into a second day. Customers are more than furious. Have you got an ETA?
Is there an option in the TC portal to be add a failsafe number? So if the lines are down calls get diverted?
We had this with iinet
John, You're killing us.
Actually the criminals that are attacking John's company are killing you.
WTH, my extensions are registering with an OK response, and incoming calls to DIDs appear to be ringing for callers but no traffic from Telecube is notifying my server about incoming calls!
So once again incoming call traffic is not working.
Edit: The extension registrations that occurred this morning around 6:45am are all showing as online in the portal, but the extensions I have manually refreshed registration this hour are showing as offline in the portal.
However in all cases my PBX is getting an OK response to registrations with everything shown as registered on my server, but all incoming calls on all extensions are just ringing out as phantom calls with no communication to my PBX.
I'm lucky enough to have another voip provider I'm also a reseller for...only have one business on telecube so far � so was able to just connect their pbx to the other providers sip trunk, activate a temp DID, and forward calls from the main number to the temporary sip trunk DID.
That seems to be working fine for the moment
Is there an option in the TC portal to be add a failsafe number
setup a linehunt
John, You're killing us. I got no work done yesterday because every site was down
What's your business continuity plan?
Have changed DID to forward to mobile temporarily which seems to be working.
This works for me too, so may be a good option till this is cleared up.
setup a linehunt
Can anyone supply instructions for this or point us to the wiki entry?
Edit:
I realise that there is http://wiki.telecube.com.au/d
But it is not resolving
Good instructions here:
http://wiki.telecube.com.au/
Line hunting (or hunt group) is the method of distributing phone calls from a single telephone number to a group of several phone lines. Specifically, it refers to the process or algorithm used to select which line will receive the call in a sequential manner (e.g. 1st number then to 2nd number, then to 3rd number, and so on). This gives you an option to use not only VOIP extensions but external numbers such as your mobile or standard home service as well.
This feature allows calls to be forwarded to another line if the first line is unable to pick up the call.
To add a hunt group, log in to your account. Go to the 'Services' area, click on 'Add New' tab. Select 'LineHunt (Hunt Group)' option.
Configure its settings:
Input Label Name. Wait for the system to create the Hunt Group. Then, go to 'Services'. Click on 'Manage' next to the hunt group name.
Select extensions or numbers to hunt and associate a voicemail if desired.
Input desired Ring Timeout.
Possible Sequences:
Digital Extensions > Mobile Number
Digital Extension > Mobile Number > Voicemail
Call Queue > Mobile Number > Voicemail
Finally you will need to go into "manage" option for your DID and select Line Hunt at "Profile Type" input box.
Update
We're moving ahead with DDoS Protection with Micron21, hopefully it should be in place by the end of the day.
In the meantime we'll keep trying to shuffle traffic around the attacks and you should be able to route incoming calls to mobiles or fixed lines.
Apologies again to those affected, I expect to have it resolved through the day.
But it is not resolving
Screenshots just in case:
http://s32.postimg.org/haxt8hclx/lh01.jpg
What's your business continuity plan?
Even Telstra lost services for a day (twice) in recent times.
Good instructions here:
Thanks.
and
Wamuran4512
It did eventually resolve but after the above posts.
Having trouble with outgoing calls as well. Due to Telecube SIP servers giving a false OK registration outgoing calls hang doing nothing for 30+ secs then Telecube servers accept the call and you hear the call ringing but the call never rings the destination at all!
Phantom ringing now for both incoming and outgoing calls.
John, I would prefer if your servers rejected registration until the problem is fixed rather than give a false registration that screws up our outgoing call routing and has incoming calls ring out rather than be rejected.
Even Telstra lost services for a day (twice) in recent times.
My point was not to rely on a single provider where practical, regardless of who it is.
Screenshots just in case:
http://s32.postimg.org/haxt8hclx/lh01.jpg
http://s32.postimg.org/r94zpqhw5/lh2.jpg
http://s32.postimg.org/pqnu9cwet/lh3.jpg
Thank you :) A++++
It's hurting us now but once resolved it will make the network stronger, I'm sincerely sorry to those that are affected.
+1
Understand entirely about this being an issue that is beyond Telecube's control, but it would be great if there was communication of the issues outside of Whirlpool (only just thought to check here after the phone line didn't work).
Agree 100% � the last place I thought to go looking was Part 4 of the Telecube Whirlpool offer thread.
The support phone lines are just ringing out, surely there could have been a recorded message explaining the outage and no one was available to answer calls. And what about a 'current service status' page on the Telecube website ? Surely it wouldn't bee hard to get some traffic light style monitoring that customers could refer to when there phones aren't ringing.
At the very least there should be a seperate 'Telecube outage' or a 'Telecube issues' thread here on Whirlpool rather than throwing all of this banter in a service offer thread.
In my IVR I am diverting all options to mobile phones, but the mobile phone doesnt receive the call
it ends up on the mobile phone users voicemail.
- the caller hears the phone ringing. so obviosulty the 'network' is not placing the call.
the last place I thought to go looking was Part 4 of the Telecube Whirlpool offer thread.
You may find this is a "whirlpool" issue. Perhaps providers are not allowed to start or have multiple threads.
For me personally, it was the first place I looked because I always firstly assume that other people are having the same issues and move on from there.
Also agree that there needs to be better support communication. Also experienced no answer on support line, no email response on Murray's or the support email address. I have a large customer base on TC and I look like a goose when I have no information or explanation or ETA on the situation and have to trawl Whirlpool for answers! I'm a huge fan/supporter of TC, but managing customer expectations with good communication is definitely something that I would like improved. Agree with a Status page that is kept up to date. Look forward to having the current issues resolved. Keep up the good work John!
Yes please, like many others, this is costing us money. We really, really do need either an SMS broadcast to mobiles or a goto page for status updates when faults like this occur.
Due to Telecube SIP servers giving a false OK registration
Even on-net extension to extension calls are failing.
lso agree that there needs to be better support communication. Also experienced no answer on support line, no email response on Murray's or the support email address.
One of the serious side affects of a small service provider outage is that its a catch 22, their support area gets overloaded with enquiries but its the same people that handle the communications, and in this case the same people are doing the fixing.
If it was telstra, then sure you can get through to support, who will tell you its broken, and give no details nor an eta, because they dont have any info, and are under instructions not to annoy the higher levels of support, who are busy trying to solve the problem. So despite the ability to speak to someone, you are no better off.
The best thing we can all do right now, to get this solved quicker, is dont overload them with enquiries, nags and feedback, Save that for later. Also now is not the right time to work on their communication platform.
Also now is not the right time to work on their communication platform.
I completely agree, but I hope it happens as a result of this episode.
I suspect that DDoS is what is causing my FreePBX server to not register. All good; thought it was my fault and was about to open a support ticket.
Actually, on an unrelated note:
John, on the Telecube site in Extension Settings, it lists the SIP server as
sip.telecube.com.au
In the wiki here, it's
sip.telecube.net.au
Which one do we actually use? :)
Which one do we actually use? :)
Officially .. .net.au .. however .com.au should work too but is still under development
I completely agree, but I hope it happens as a result of this episode.
Definitely a high priority
Which one do we actually use? :)
When you add an extension in the portal, it defaults to sip.telecube.com.au so it looks that is the one TC would like us to use, although .net should still work also.
edit: just saw John's post. Looks like it is the other way around. Strange that the portal wants us to use .com.
I'm aware there's ongoing issues with Telecube � in Perth, I cannot connect at all to the SIP provider � I get the following error:
Problem at server (Sip error 408). Try again later.
Any ETA for a fix? Without being able to connect to the SIP servers at all, I can't make local or international calls, it's a dead line.
Update
A permanent fix is very close, we've peered up with Micron21 now and as soon as they can take our routes traffic will pass through their scrubbers and we should be back to normal.
Once we have a resolution there'll be an email sent out to all customers explaining the events and the solution we have implemented.
Thank you for your patience and apologies again.
then sure you can get through to support, who will tell you its broken, and give no details nor an eta, because they dont have any info, and are under instructions not to annoy the higher levels of support
In most ISPs/telcos, the engineering teams have no interaction with the support team � they know things are going wrong by using their own monitoring tools, not by the call centre stats.
This said, Telecube really do need an outage notification system of some sort.
Come on, John. You've got a support staff member, don't you? How are they not tasked with sending out email updates? Website status alert? SMS?
*Staff member asks me if there's any update*
*I scour a whirlpool offer thread*
"Oh it'll be back 'in minutes now'"
*Wait an hour*
"..."
*I scour the thread again*
"Oh I need to update your phones to point to some other IP"
*nup*
"Oh that was already out-of-date info"
My bosses confirmed with me that it isn't April 1st.
I'd better get back to scouring this thread instead of complaining.
This said, Telecube really do need an outage notification system of some sort.
Yep I agree and it's going to be implemented as soon as this is all over.
Officially .. .net.au
That's what I thought. *goes to fix*
If I may suggest: A write up similar to this � detailing it from your point of view. It did wonders for the company in question.
The .net.au SIP server is back for me
.com.au still down.
So slowly switching extensions over
The .net.au SIP server is back for me
Thanks, I just moved mine over to .net.au and my extension came back to life!
The .net.au SIP server is back for me
They might register but do inbound/outbound calls actually work?
No point having registration say OK only to have it screw up your routing priority.
I've noticed the com.au hostname now points to Rackspace cloud servers. Is that the DDoS protection server?
They might register but do inbound/outbound calls actually work?
No point having registration say OK only to have it screw up your routing priority.
Yeah, I've been online all day according to my handsets, but can't make or receive calls.
Just waiting patiently for them to come back. We're getting voicemails...so not too worried
I've been online all day according to my handsets, but can't make or receive calls.
Reboot your router and handsets/ata. May have some bad route or DNS info.
from TPG the routes look good, latency is acceptable.
2 bri-sot-wic-bras4-loopback20.tpgi.com.au (10.20.20.248) 17.991 ms 18.996 ms 20.338 ms
3 203-219-166-2.static.tpgi.com.au (203.219.166.2) 21.321 ms 22.739 ms 24.397 ms
4 bri-nxg-alf-csw1-tengi-4-3.tpgi.com.au (202.7.162.130) 88.462 ms 90.677 ms 92.063 ms
5 183.177.59.30 (183.177.59.30) 92.471 ms 93.815 ms 94.217 ms
6 sip.telecube.net.au (103.193.167.41) 95.136 ms 87.111 ms 87.822 ms
[2016-05-17 14:02:11] NOTICE[5001]: chan_sip.c:12104 sip_reg_timeout: � Registration for 'XXXXXX@sip.telecube.net.au'
timed out, trying again (Attempt #130)
Coming via megaport IX my eyeBeam Softphone registers but can't make calls.
Reboot your router and handsets/ata. May have some bad route or DNS info.
Oh ok, wasn't sure if it was ready to be working again yet. Will try
I've been online all day according to my handsets, but can't make or receive calls.
Setup a re-direct to your mobile or voice mail,
Instructions here
I've been online all day according to my handsets, but can't make or receive calls.
Yep, that's why I suggested to John at 10:30am to deny registration if calls can't be made and a few minutes later .com.au registrations stopped being accepted (assume John made the change).
Before that incoming calls were ringing out without notifying extensions and outgoing calls were hanging then indicating the destination was ringing when it wasn't. I'd rather have registration show as failing than have calls appear to ring out when they haven't rung at all.
Reboot your router and handsets/ata. May have some bad route or DNS info.
No go. That's ok...happy to wait
Oh ok, wasn't sure if it was ready to be working again yet. Will try
I had a try at home about an hour ago so thought it was all working, thought might have been heading out through my other VSP now that you mention that.
Hey guys .. let's move this to a dedicated outages/support thread please.
I had a try at home about an hour ago so thought it was all working,
Registration to .net (new server) is working but Invites only get as far as Trying then nothing.
Edit . To late sorry I posted too soon.
Is it possible to add a mobile to a ring group?
I think this would allow me to leave a mobile connected and ringing all the time. If there is an outage like this at least I won't miss all the incoming calls
I have changed my line hunt to ring the mobile, this seems to be a temporary solution to get by until things are sorted
pepe
Continues here: /forum-replies.cfm?t=2531073
Không có nhận xét nào:
Đăng nhận xét