One Way Audio Issues and STUN

DustinB3403

@scottalanmiller So are STUN servers recommended or frowned upon?

scottalanmiller

@dustinb3403 said in SIP Desk Phones Not Re-Registering with Main WAN's IP After WAN Fail-back:

@scottalanmiller So are STUN servers recommended or frowned upon?

Recommended. Not always needed, but often needed unexpectedly without warning. A system can go years without needing STUN, then something happens and things stop working because STUN was missing. Making it even harder to figure out because "it was working" and nothing changed.

DustinB3403

@scottalanmiller said in SIP Desk Phones Not Re-Registering with Main WAN's IP After WAN Fail-back:

@dustinb3403 said in SIP Desk Phones Not Re-Registering with Main WAN's IP After WAN Fail-back:

@scottalanmiller So are STUN servers recommended or frowned upon?

Recommended. Not always needed, but often needed unexpectedly without warning. A system can go years without needing STUN, then something happens and things stop working because STUN was missing. Making it even harder to figure out because "it was working" and nothing changed.

That is what I was thinking based on a few experiences.

krisleslie

@scottalanmiller My problem lies in that "something" has to be identified and measured so we can come to a conclusion and how to resolve it. After poking around I didn't realize the Yealink phones have some form of monitoring and logging. However I'm trying to find out if the monitoring part with Telchemy http://www.telchemy.com/ is even free

In theory I seem to keep understanding more and more about VoIP each week. However, it seems I'm not closer to figuring out on my end how to make sure my network isn't causing most if not all the issues (which is where my heart burns with desire to know wtf lol).

krisleslie

Let the suck begin!
http://www.yealink.com/products_94.html

So Yealink has a tool to manage mass phones for "specific models". How anti-cool. In this day and age they should have a tool like Unfi which I could poke into to see the health of the phones and drill down into troubleshooting.

DustinB3403

@krisleslie said in SIP Desk Phones Not Re-Registering with Main WAN's IP After WAN Fail-back:

Let the suck begin!
http://www.yealink.com/products_94.html

So Yealink has a tool to manage mass phones for "specific models". How anti-cool. In this day and age they should have a tool like Unfi which I could poke into to see the health of the phones and drill down into troubleshooting.

Their DMP is meant to setup and manage the phones, not to continually inspect the phones.

krisleslie

True. But the point is, that's better than what the rest of us are left with. Surely you could have a tool to deploy and a seperate tool to manage. If Ubiquiti can do it, surely Yealink can.

DustinB3403 I'm to the point of believing no voip should cross talk with any other device at all.

Feels like one dedicated, managed switch for all the phones, with a dedicated ISP is better in theory than leaving it on the flat network shared with other devices. I know we all believe it is just data (and I agree), but in my defense I'm left with a big haystack trying to find a needle but the stack is in an unknown location lol.

DustinB3403

@krisleslie what issues are you encountering?

krisleslie

@dustinb3403 as of today 1-way audio.

JaredBusch

@krisleslie said in SIP Desk Phones Not Re-Registering with Main WAN's IP After WAN Fail-back:

@dustinb3403 as of today 1-way audio.

on internal ext to ext calls? Because if not that, then the problem is unlikely to be the phones.

JaredBusch

Granted 1 way audio is almost never the phone anyway.

krisleslie

Intra-office calls (so far) are fine no issues. Someone dialing in from outside of our network has the issues mostly.

DustinB3403

@krisleslie said in SIP Desk Phones Not Re-Registering with Main WAN's IP After WAN Fail-back:

Intra-office calls (so far) are fine no issues. Someone dialing in from outside of our network has the issues mostly.

Can they hear you or can you not hear them?

krisleslie

@dustinb3403 well right now I'm wondering is there an issue with the STUN server or is there a firewall issue between me and the STUN server. I've used the common one on the internet:

stun.stunprotocol.org