Yeastar PBX to 2Talk stopped working

Forums › VoIP › Yeastar PBX to 2Talk stopped working

Dynamic

4015 posts

Uber Geek
+1 received by user: 1849

ID Verified

Trusted

Lifetime subscriber

#205069 28-Oct-2016 14:44

We have a Yeastar Asterisk-based PBX that has been working beautifully for a couple of years. Between 1am and 2am this morning the PBX stopped talking to 2Talk, and we've been unable to establish why. Rebooting the device and the 2-talk supplied VDSL router has not helped, and restoring the configuration of both devices from recent backups has not made a difference either.

All suggestions welcome!

“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams

chevrolux

4962 posts

Uber Geek
+1 received by user: 2638
Inactive user

#1659869 28-Oct-2016 15:09

The quickest and easiest thing to do would be a packet capture. You would see quite quickly what's going on.

But silly question, is your 2talk account password still working ok?

Dynamic

4015 posts

Uber Geek
+1 received by user: 1849

ID Verified

Trusted

Lifetime subscriber

#1659875 28-Oct-2016 15:21

Nice suggestion. Log viewing via the web interface is almost nonexistant.

Yes a softphone logs in using the account credentials just fine.

“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams

ArcticSilver

731 posts

Ultimate Geek
+1 received by user: 148

#1659876 28-Oct-2016 15:23

Can you register the same SIP trunk from another device? If you cannot, can you from another device on another Internet connection?

ArcticSilver

731 posts

Ultimate Geek
+1 received by user: 148

#1659878 28-Oct-2016 15:24

Dynamic:

Nice suggestion. Log viewing via the web interface is almost nonexistant.

Yes a softphone logs in using the account credentials just fine.

Just saw your post, after I posted.

If that is the case then it sounds like a packet capture is probably the next best port of call. You may need to put a laptop on a hub between your PBX and the switch connecting you to the Internet to get this information.

Alternatively the PBX or your switch may offer a packet capture method.

Edit: I believe the Yearstar PBX's are based on Asterisk, you may be able to change the logging level on them to get more meaningful logs.

CYaBro

4708 posts

Uber Geek
+1 received by user: 1182

ID Verified

Trusted

#1659903 28-Oct-2016 15:49

Interesting, I had a customer email today to say that one of their lines, provisioned on a Cisco ATA wasn't working.

Looking at the 2talk account I could see that it was last online at about 1:50 this morning.

They've just rebooted and that has got it back online.

The other line on the ATA has carried on working fine.

Opinions are my own and not the views of my employer.

speed

296 posts

Ultimate Geek
+1 received by user: 101

#1659904 28-Oct-2016 16:00

I don't have a suggestion specifically to help you get your equipment back online (other than rebooting), but I thought I'd at least confirm that we also had multiple 2talk alarms during that that timeframe overnight, including some 2talk-IP hosted VMs which lost public internet connectivity from approx 1:45am until approx 2:00am. So there was definitely some sort of transient issue on their network, and although correlation is not causation it stands to reason that the issues you have experienced are likely related, ie it's not just you.

Samsung

Shop now on Samsung phones, tablets, TVs and more (affiliate link).

Dynamic

4015 posts

Uber Geek
+1 received by user: 1849

ID Verified

Trusted

Lifetime subscriber

#1659911 28-Oct-2016 16:16

Thanks for the packet capture suggestions. Actually, it is looking like a credentials issue. Quite why a credential issue happens in the middle of the night on an account not touched in months or years I cannot imagine. Possible account compromise of some sort?

Resetting credentials in the portal does not seem to have helped so a ticket has been logged.

2016-10-28 15:57:22] WARNING[2017]: chan_sip.c:19724 handle_response_register: Forbidden - wrong password on authentication for REGISTER for '0800xxxxxx@sip.2talk.co.nz:5060' to 'sip.2talk.co.nz'

“Don't believe anything you read on the net. Except this. Well, including this, I suppose.” Douglas Adams