T46 Firmware Update - Things I Learned

[eryp]

I've been getting away with not assigning individual listening or "Local SIP Port" for remote STUN extensions. Fully aware that it is not best practice. It seems that by checking "PBX delivers Audio" using the same port of 5065 for many extensions behind the same firewall it was working well until....

Reference this thread: https://www.3cx.com/community/threads/v16-update-2-problems-with-yealink.66732/#post-288457

The upgrade to V16.03 and firmware update to 66.84.0.95 caused major problems getting phones to register, make or pickup calls, etc. Phones would sometimes take a long time to register, they would show up in the pbx phone list 3 or 4 times, calls were questionable and other strange behavior.

So - follow best practice and use different ports for each remote extension. I got away with it for a long time but got caught after upgrades.

I'm just sharing this as something learned if anyone else get's caught with the same problem.

 

[cobaltit]

Appreciate you sharing your experience, but realistically, don't set yourself up for failure like this. Grab some RPi's, setup some SBCs and save yourself some headache.

 

[eryp]

@cobaltit - I've been thinking of moving that way for future installs. What hardware do you recommend? Just something from Amazon like CanaKit?

 

[Saqqara]

If looking at Raspberry PI, only the model 3B+ version is supported.

Just get a decent power supply

 

[craigreilly]

Pi4 is on the "radar" https://www.3cx.com/blog/releases/v16-roadmap/ but as a MAYBE.

 

[wsd-tim]

Remote SIP also has issues. need to duplicate "Account1" settings on Yealinks to "Account2" after auto provision. Otherwise every call takes 10+ seconds to connect for some reason. Softphones on the same network works just fine