Enterprise Communicate – October

Your monthly product updates from Gamma

gamma voice, mobile, data and cloud

Horizon

Visible Call Park (VCP) notification for monitored users within a Busy Lamp Field (BLF)

As of the 19th November 2018, we have enabled a Visible Call Park (VCP) service for monitored extensions within a Busy Lamp Field (BLF). This update applies to customers with the following Polycom devices only:

VVX310
VVX410
VVX411
VVX500
VVX600

Excluded from the updates are Polycom SoundPoint and Cisco SPA range of handsets.

The VCP feature enables a notification to assist users with identifying and retrieving calls parked against monitored users.

If a call is parked against a specific users extension, there will be no visibility on that users device. The indicator will now only appear against a monitored extension in a BLF configuration.

How does visible call park work?

When a call is parked against a monitored user, the icon will appear in front of the user and the message “Call is Parked” will appear on the right top corner of the screen.

To view the information of the parked call and retrieve it press and hold the corresponding line key for 2 seconds, the user will be highlighted and then go off.

Then press the “More” soft key until you see the “Park Info” soft key. This soft key will be placed automatically on the first available position

The “Park Info” soft key will be visible for 5 seconds. If you can’t see the soft key then repeat the above step.

Once you press the “Park Info” soft key information about the caller will appear on the screen (i.e DDI number or Username/Extension for internal users) with the following options:

Ignore – If the user presses the ignore option the call will return to the person who parked the call and the indicator will disappear.
Retrieve – If the user presses the Retrieve option then the parked caller and user will be connected.
Exit – If the user presses Exit they will return to the main page but the call will remain parked and visible in the BLF.

Once a parked call is retrieved the screen will update to provide in call options for the user as per the following image.

SIP ALG bypass for Horizon desktop clients coming on the 9th January 2019

Due to its portability, the Horizon desktop client is often used in remote access situations, at home or on public internet connections where SIP ALG may be present and it is outside the user’s control to disable it.

We are delighted to advise that from the 9th January 2019 Horizon desktop clients will be enabled to access the Horizon platform via TCP port 5080 as its first choice of routing, this port is not subject to SIP ALG inspection and the packet interference associated to the service. If the client cannot reach the Horizon SBCs on TCP 5080 it will reattempt on the standard UDP 5060 route exactly as it does today, so existing deployments behind restrictive firewalls will continue to be able to make and receive calls but it is this port that is subject to SIP ALG inspection.

For optimal performance it is strongly recommended that access to Horizon SBCs via TCP 5080 is allowed.

What happens when TCP port 5080 isn’t open or SIP ALG is still enabled on the firewall?

If you are behind firewalls with no access to the Horizon platform via TCP port 5080 the client will display a ‘Calls Unavailable’ error for 10 seconds every 30 minutes. If a user is unlucky enough to receive a call in this 10 seconds it won’t reach the Desktop client but will hit voicemail or ring on the users alternate devices or call forwarding destinations. Desktop client users will also be unable to make a call for 10 seconds. Active calls are not affected. The solution is to open their firewall to TCP 5080 or disable SIP ALG