Enhanced Call Park feature

[notonlyeveryone]

I'm wondering if there's a working config for Enhanced Call Park feature (for Broadsoft/BroadWorks) as per release notes for software 5.3 

I've searched forum (earlier topics didn't have definitive answer) and looked at Partner configuration guides.

I've tried it on VVX 501 with latest available software (as well as 5.9.5):

Phone Model	VVX 501
Part Number	3111-48500-001 Rev:A
UC Software Version	6.2.0.4023
Updater Version	6.2.0.3999

The best I can get is showing that monitored (BLF) line is parked, but if a call is parked against the primary line of the phone - it doesn't show.

[SteffenBaierUK]

Hello @notonlyeveryone ,

Welcome back to the Poly Community.

Have you tried >here<

Enhanced Call Park Parameters

The following list includes the configuration parameters you can use to enable and configure this feature.

reg.x.enhancedCallPark.enabled

0 (default) - To disable the BroadWorks Enhanced Call Park feature.

1 - To enable the BroadWorks Enhanced Call Park feature.

reg.x.lineAddress

The line extension for a shared line. This parameter applies to private lines and BroadSoft call park and retrieve. If there is no extension provided for this parameter, the call park notification is ignored for the shared line.

Null (default)

String

feature.enhancedCallPark.allowAudioNotification

0 (default) - Disables the audio notifications for parked calls on private and shared lines.

1 - Enables the audio notifications for parked calls on private and shared lines.

call.parkedCallRetrieveString

The star code that initiates retrieval of a parked call.

Null (default)

Permitted values are star codes.

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

[notonlyeveryone]

Steffen, thank you for quick response!

I've tried exactly this:

<phone>
<call call.parkedCallRetrieveString="*88" />
<reg reg.1.enhancedCallPark.enabled="1" reg.1.lineAddress="1505" />
<feature feature.enhancedCallPark.allowAudioNotification="1" feature.callPark.enabled="1" />
</phone>

... but when I park call against this extension (1505 which is single on this phone), this VVX 501 doesn't show anything.

[SteffenBaierUK]

Hello @notonlyeveryone ,

as this feature most likely relies on the Broadsoft server we would need to see logs etc. As we cannot do this via the medium of a forum you would need to work with support.

In order to raise a support ticket, you need to work with your Poly reseller as they may need to do this for you.

End Customers are usually unable to open a ticket directly with Poly support. Available End User Poly services offerings are detailed here

If this is some sort of an Internet discounter providing your MAC address or your Poly devices serial will enable us to look up who would be able to support you. This may not be who you purchased the Poly device from.

If the unit is no longer within the warranty please be prepared to Pay Per Incident / PPI. This is all outlined in detail here

Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.

Best Regards

Steffen Baier

[notonlyeveryone]

Thanks again, Steffen!

I'll see if I can reach your support team for that.

In the meantime is there any log channel you'd recommend to enable and any particular SIP/other message to look for there?

[SteffenBaierUK]

Hello @notonlyeveryone ,

everyone can reach our support team using the officially outlined methods.

Our FAQ contains:

Jan 19, 2012 Question: How to troubleshoot Polycom VoIP related Issues?

Resolution: Please check => here <=

Best Regards

Steffen Baier

[notonlyeveryone]

Surprisingly it started working today.

Here's Export Web config for future reference if anyone needs it:

Spoiler

<PHONE_CONFIG>
<WEB
call.parkedCallRetrieveString="*88"
feature.callPark.enabled="1"
feature.enhancedCallPark.allowAudioNotification="1"
up.screenCapture.enabled="1"
reg.1.enhancedCallPark.enabled="1"
reg.1.lineAddress="1505"
/>
</PHONE_CONFIG>

I've tested on several FW versions from 5.6 to 6.2 on VVX 501.

Not sure why it didn't work before.