New to Azure - Auto Provision not working

[total9]

I feel like I am missing something obvious.

I used PBX Express and setup new instance on Azure V16.0.0.1581
All went well from what I could tell.
I can't seem to get any phone to provision.
Firewall checker runs without error.
I have run Remote Connect Test tool and all comes back normal.
I have tried manually entering settings Registration Fails.
Mostly testing with Yealink.
Android App works great.
I can get phone to provision on other instances of 3cx hosted elsewhere.
I was even able to download .CFG file from Provisioning URL without problem.
Firmware is on 3CX recommend.
Tested with 2 different phones. T32G, T46G
Tried reboot of System
Ip is not blocked
I am using instance.my3cx.us and there is no problem with FQDN routing
Provisioning Method is set to Direct SIP (STUN- remote)
I have made sure Disallow use of extension outside LAN is not checked.
Double checked mac and port
Was thinking of setting up a SBC but I really feel like I have missed something obvious.
New to this version. Mostly worked with older version 12/14
I am going to move on to setting up SIP Trunks and inbound / outbound rules in hopes that someone can give me a clue on what I missed.

Thanks

 

[CentrexJ]

Check blacklist for IP address of the remote site the phones are on.

 

[ASC Admin]

No help with STUN, but so far I've been very happy with the Azure pbx express when paired with an sbc.

 

[total9]

Doubled checked blacklist and all is good there... even added Allow for my ip.
I am worried about setting up a SBC since I have other Phones in that office on a different 3CX instance that are working. (Older hosted version)

Since Firewall checker says Azure is all good and Remote Connection Test Tool says my LAN is all good. My phones work on an older 3CX instance, I am left scratching my head as to what I have missed.
Manual and Auto Provisioning fails. I have not dug into the log files on 3CX or the Yealink as that starts to get a bit beyond my basic knowledge. (not even sure where to look). I have been holding off paying for a support incident with 3CX in hopes that I would have an ah ha moment but that has not worked yet.

I am a bit lost as to where to look for the next clue in figuring this one out. Any suggestions are appreciated.

 

[AWS2P]

Huumm, if i understood well, you have several phones on same lan connected to several cloud 3CX .
if this is the case, install a SBC for your new phones, only port 5090 has to be forwarded, with a simple RPi 3B+ you can set until 20 phones with BLF. no headache.

 

[total9]

I am going to go SBC. Thanks for the advice. The plan was to put one in down the line anyway.

I do have a small update. I have been able to get the phone to register by manually entering all the settings.

I also changed the log level to 6 on the phone and ran the auto provisioning. From what I can tell from the log it had some kind of DNS error. So I modified the provisioning URL to be https://IPaddress/blahblah instead of the my3cx.us and I now get these messages on the phone:
Configuration Updating....
The operation is done.

But..... still not working..... I thought I had it for a minute. I am going to keep on digging.

I tried http and https for the Auto Provisioning and putting a slash at the end as that was a trick that worked once upon a time. It looks like it is working but no account info is on the phone.

 

[JohnS_3CX]

@total9 EOL devices will not provision unless you disable PCI compliance "SSL Transport and Ciphers"

Please read the restriction notes on the bottom of the page for these models https://www.3cx.com/sip-phones/yealink-t32g-t38g-t42g-t46g/

 

[cam]

I am in exactly the same boat, 3cx in azure, android and windows working fine, Cannot provision Yealink T21p

 

[JohnS_3CX]

@cam

Please check the limitations of the specific devices https://www.3cx.com/sip-phones/yealink-t20p-t22p-t26p-t28p/ and refer to my previous post

 

[cam]

Thanks John, Sorry I should of said mine is the E2 model so I think those limitations are not an issue?

 

[JohnS_3CX]

@cam T21P E2 is supported, start a new thread in General and we can take a look

 

[JohnS_3CX]

I am going to go SBC. Thanks for the advice. The plan was to put one in down the line anyway.

I do have a small update. I have been able to get the phone to register by manually entering all the settings.

I also changed the log level to 6 on the phone and ran the auto provisioning. From what I can tell from the log it had some kind of DNS error. So I modified the provisioning URL to be https://IPaddress/blahblah instead of the my3cx.us and I now get these messages on the phone:
Configuration Updating....
The operation is done.

But..... still not working..... I thought I had it for a minute. I am going to keep on digging.

I tried http and https for the Auto Provisioning and putting a slash at the end as that was a trick that worked once upon a time. It looks like it is working but no account info is on the phone.

The T32G phone will not be able to provision over HTTPS because its not compatible with Let's Encrypt. Disable ciphers and see if it works when provisioned the 3CX way to verify everything is ok.

You can also check to see if the configuration file is downloadable (from the phone site internet connection of course) by entering your provisioning link a browser (don't post it here, should be kept secret) and including the phone mac address of the phone in the following format:

https://yourfqdn.com:5001/provisioning/uniqueid/macaddress.cfg
(im assuming your HTTPS port is 5001 here - replace it if different)