@JaredBusch said in FreePBX extension oddity:

@art_of_shred you need to have the process started over.

Original phone on original port and verify behavior.

Original phone on new port and verify behavior.

We had the original phone on the original port that was malfunctioning as described in the OP. We replaced the phone and got the same result. The new phone, which had the same exact behavior as the original (so it's not the phone) was moved to another port and had the same issue plus the lack of audio on the other end of a call.

@Mike-Ralston look at the PBX I have with NTG you can see outbound route there like that

equivalent GUI settings.
0_1486133068408_upload-3e7834fd-c9c3-4a6d-a929-b3db2cc95e78

@RamblingBiped said in SIP Phone registers no audio...:

Here is the guide I followed to get the Yealink T23G to work with OpenVPN: http://www.sunstatetechnology.com/docs/YealinkOpenVPNGuide.pdf

When I disable NAT on the extension the phone is unable to register.

Something is wrong there, that sounds like the VPN is not working as there is no NAT when there is a VPN.

@scottalanmiller said in FreePBX External/Remote Extensions:

@JaredBusch said in FreePBX External/Remote Extensions:

@RamblingBiped said in FreePBX External/Remote Extensions:

Option #1 up and running. Now to work on the OpenVPN part of the equation... 🙂

I have set this up but then ran into the problem of the OpenVPN port being blocked. Slightly hard to change once out in the wild.

On which end?

The remote end obviously. As I have full control of the server side.

Ok, I resolved this problem by reverting back to 29.73.0.50. As soon as the phone finished booting with the 29.73.0.50 firmware, I heard the CS540 base click active. I pushed the button on the headset to deactivate it and I knew it was going to work before i even picked it up to test.

This does not explain why the EHS previously worked with 29.80.0.60.

After confirming everything working correctly, I upgraded to 29.80.0.60. The headset no longer worked correctly. I downgraded back to 29.73.0.50 and it worked correctly again.

This is a problem with the new firmware for the phone and obviously not a problem with the 3.16.0.0 EHS firmware.

Email sent to yealink support. Hopefully this will be resolved in future firmware.

Looks like nope. that is the close port on the left.

0_1454033387138_2016-01-28 20_09_05-yealink t20 - Google Search.png

@Minion-Queen said:

This is what happens when I post from my phone on a subway 😛 even this is bad for me

I figured it was an autocorrect....

@Dominica exactly. And you would be struggling to even do that. If locked down the extension would be locked by IP range and the phone would hopefully be blocked from making its own external VPN connections. So it really would only be a gateway to other security flaws. On its own it should do very little.