Fun with Polycom and v16 New Install - Shared Park and Two Trunks

[dkirk-ads]

New/Fresh install of v16 "Debian" version. Not by my choice but I have $9k in new Polycom VVX300 and VVX410 phones to use, new in the box. While I prefer my beloved YeaLink the Polycom hasn't been too bad to work around. I tried the recommended 5.6 version of the firmware as well as the recent 5.9 and have not seen any differences as of yet. One problem and one annoyance, with the annoyance first:

I understand the two trunks/bridging issue with v16, but do we need to show two trunks when I really have one? I am trying very hard to not go down the custom template route and hack that second trunk off the screen. Anybody encounter this and if so, any solutions? Shown below is default template Polycom VVX410 showing two trunks even though I only have one, taking up an extra BLF slot.



The problem is when a call is parked at one of the three SPs. The Android and Windows client works fine with the Shared Park, and the Polycom phone displays the red LED parked indicator when a call is parked, but the phone is never able to retrieve the SP call. Using the BLF or directly with *10/1/2 command. When the BLF is pressed a window appears showing the correct parked phone number but the second line shows "8.15.19:5060" which is the last part of the 3CX server at 192.168.15.19:5060. Smells like a possible bug somewhere.

Any help is greatly appreciated.

 

[cobaltit]

FYI what you are talking about are line appearances, not trunks. In 3CX trunks are something different. As far as the VVX phones, if you look at the notes at the bottom of this page you'll see that shared parking is not supported:

https://www.3cx.com/sip-phones/polycom-vvx/

 

[dkirk-ads]

I did read that page several times and knew about the speed dials, but totally missed the second part about parking. That's a real kicker.

Thanks, now I need to figure out why two "line appearances" are showing.

 

[cobaltit]

The two line appearances are hard coded into the template. You'll have to go the custom template route to resolve that.

 

[dkirk-ads]

Is there a purpose for showing two lines like that?

What is REALLY strange is that I put a VVX300 and VVX410 on the same 5.9.1.065 firmware and my first test with SPs worked great! More testing needed for sure as it hasn't worked all day, and some sequence I did recently has it working as expected now.

 

[cobaltit]

So my understanding is it's a known issue with with the way the VVX phones were requesting updates from 3CX for monitoring functions. It would drive up memory usage in 3CX and would cause the VVX phones to get sluggish/act up and require a reboot. But otherwise they would work typically. Perhaps it was finally resolved with 5.9 firmware?

 

[dkirk-ads]

Thanks, I'll keep an eye on server resources! Yesterday it was at 4% memory usage according to the Dashboard and this morning I'm seeing 5% with only two test extensions lit.

Here on day 2 of testing the SPs are working fine using the function keys. I am able to pass a call onto and off SPs using two different Polycom devices but all running the recent 5.9 firmware.