Slingshot VoIP with Yeastar TA100 ATA

Forums › VoIP › Slingshot VoIP with Yeastar TA100 ATA

Nition

12 posts

Geek
+1 received by user: 2

#249427 10-May-2019 09:46

I'm on Slingshot fibre with a VoIP phone service and I'm trying to get a Yeastar TA100 ATA working so I can connect an analogue phone. I've read all the related posts here and I seem to have got it almost fully working. I can successfully place outbound calls, but inbound calls just go to a disconnected tone. The Yeastar's own status page also seems to think that the connection is fine, but that the phone is disconnected (despite the fact that the phone can place outbound calls successfully).

Is there anyone that could share their Slingshot settings or suggest a fix to try here? I'm thinking I probably need to source another analogue phone from someone to see if the Yeastar detects it as connected, as it kinda seems like everything is working except the phone actually being detected.

Here are my current settings:

speed

296 posts

Ultimate Geek
+1 received by user: 101

#2234333 10-May-2019 09:51

Your ATA is completing the registration process (which, as you have surmised, is not required for outbound calling), but then becoming unreachable from the PBX.

The most common reason for this is when a firewall "helps" with the VoIP packets (not very helpful at all), or when it's internal NAT table times out before the registration expire period, or at an lower interval than the PBX's SIP session keep-alive mechanism.

Try changing your registration protocol to use TCP (instead of UDP) to work around it.

Not sure if Slingshot support it or not, but it won't hurt to try - you can always put it back...

Nition

12 posts

Geek
+1 received by user: 2

#2234335 10-May-2019 09:56

OK, I just tried TCP but got the same result. My router (Asus RT-AC68U) has a firewall option but it's not turned on. Thanks for the suggestions though.

speed

296 posts

Ultimate Geek
+1 received by user: 101

#2234342 10-May-2019 10:11

Bummer. Then in a last ditch attempt, try setting the SIP keep-alive interval to 20 (from the current 30). Crossing fingers but not too hopeful.

FWIW, I think you've mis-interpreted the column headers in the first screenshot. Your sentence "The Yeastar's own status page also seems to think that the connection is fine, but that the phone is disconnected (despite the fact that the phone can place outbound calls successfully)." leads me to believe that you think the "Phone Status" column (showing 'Disconnected') is related to the analog phone. But I don't think it is. I think this column may in fact be showing the SIP registration status (poorly named). I think the column headed "UP/Down/Break" may actually be the column reflecting the FXS port status (ie the analog phone port), and the page is therefore saying that your SIP registration has not connected successfully.

I may be wrong so take it with a grain of salt - I'm not familiar with this particular firmware at all! But I've also had to decipher my fair share of Engrish in my days :)

Nition

12 posts

Geek
+1 received by user: 2

#2234348 10-May-2019 10:16

Yeah, no luck sadly.

The manual for the Yeastar re "Phone Status" says "Connected: An analog phone or fax machine is connected to the port." "Disconnected: No device is connected to the port."

So I think it's legitimately not detecting the phone. Whether that's the phone (it's just a typical cordless phone), or a setting somewhere, or even a faulty Yeastar unit I don't know. Which is why I'm thinking I probably need to get another analogue phone to test.

speed

296 posts

Ultimate Geek
+1 received by user: 101

#2234350 10-May-2019 10:18

Hmm ok fair call if that's what the manual says. Out of interest what does it say re the "Up/Down/Break" column?

And also did you try reloading that page with the analog phone off-hook (ie on 'talk' for a cordless)?

Nition

12 posts

Geek
+1 received by user: 2

#2234360 10-May-2019 10:28

"Up: The FXS module works well."

"Down: The FXS module is broken."

No mention of "Break"...

Discovered something I hadn't realised via your suggestion though.

Putting the phone in talk mode set the status to Off Hook successfully, but even more interestingly, set the Phone Status to Connected. Then I discovered that when I refresh the Disconnected status with the phone on the hook, it actually rings the phone. No idea if I'm meant to answer it or not when it rings, but either way the Phone Status goes back to Disconnected afterwards (with the phone back "on hook").

In the manual the example screenshot has a phone both "on hook" and "connected", so it seems that it should be possible and something's wrong on my end.

Lenovo

Shop now for Lenovo laptops and other devices (affiliate link).

Nition

12 posts

Geek
+1 received by user: 2

#2236503 14-May-2019 10:39

Just to follow up on this, I didn't manage to fix it. Went back to using a Cisco VoIP phone I had that works fine. Sorry to anyone in the future who discovers this thread - I don't have a solution for you.