[Software] VVX UC Software 6.4.3

[SteffenBaierUK]

Hello all,

we just released UC Software UCS 6.4.3 A for all compatible VVX phones (VVX 150, 250, 350, 450 and EM 50, VVX 101, 201, 301/311, 401/411, 501, 601).

What’s New in This Release

Poly Unified Communications (UC) Software 6.4.3 A is a release for OpenSIP deployments. These
release notes provide important information on software updates, phone features, and resolved issues.

• Support of New VVX 250, 350, 450, and EM50 Revision
• Server Redundancy for a Registered Line
• New Zoom Phone “Warm Transfer” Interoperation
• Accessory Update
• Software Updates
  

Support of New VVX 250, 350, 450, and EM50 Revision

Poly Unified Communications (UC) Software 6.4.3 A introduces support for hardware component
changes to VVX 250, VVX 350, VVX 450, and VVX EM50 with the intent to improve the supply profile by mitigating impacts caused by global semiconductor shortages.
For more details about these changes, see Product Shipping Configuration Change for VVX Series
(EA210826) on the Poly Support website.

NOTE: The new Hardware for VVX 250, VVX 350 and VVX 450 will not be able to run older Software.UC Software 6.4.3 is the first release for these phones. They also only run UC Software and cannot be converted into an ObiEdition phone!

Example VVX 350 Console Label and Revision Code

Example VVX 250 Colored Shipping Box Label and Revision Code 

Example VVX 450 Web Configuration Utility

Example VVX 450 Phone UI

Server Redundancy for a Registered Line

You can now configure a fallback server for a registered line on your phones. Procedure

• Open the configuration file.
• Set the phone to send a SIP required to the server that sent the proxy authentication request in the event of a failover. Replace x with the desired line key value.

• req.x.auth.optimizedInFailover="1"

  • Configure the mode for failover failback. Replace x with the desired link key value.

  Note: This setting overrides the configuration  for reg.x.server.y.failOver.failBack.mode.

  Set one of the following values:

  • duration (default) - The phone tries the primary server again after the time specified by reg.x.outboundProxy.failOver.failBack.timeout expires.
  • newRequests – The phone forwards all new requests first to the primary server regardless of the last used server.
  • DNSTTL - The phone tries the primary server again after a timeout equal to the DNS TTL you configured for the server the phone is registered to.

  reg.x.outboundProxy.failOver.failBack.mode="<value>"

  • Configure the time to wait, in seconds before failback occurs. Replace x with the desired line key value.

  Note: This setting overrides the configuration for reg.x.server.y.failOver.failBack.timeout. 

  The default is 3200. The value range is 0 (no timeout), and 60 to 65535.

  req.x.outboundProxy.failOver.failBack.timeout="<value>"

  • Enable the global and per-line reRegisterOn parameter. The existing registrations remain active.

  Replace x with the desired line key value.

  reg.x.outboundProxy.failOver.failRegistrationOn="0"

  • Enable the global and per-line reRegisterOn and failRegistrationOn parameters. Signaling is accepted from and sent to a server that has failed. Replace x with the desired line key value.

  reg.x.outboundProxy.failOver.onlySignalWithRegistered="0"

  • Configure the phone to attempt to register with (or via, for the outbound proxy scenario), the secondary server. Replace x with the desired line key value.

  Note: This parameter overrides reg.x.server.y.failOver.reRegisterOn. 

  reg.x.outboundProxy.failOver.failRegistrationOn="1"

  • Configure the SIP server port to which the phone sends all requests. Replace x with the desired line key value.

  The default is 0. The value range is 65535.

  reg.x.outboundProxy.port="<value>"

  • Configure the transport method the phone uses to communicate with the SIP server. Replace x with the desired line key value:

  DNSnaptr (default)

  TCPpreferred

  UDPOnly

  TLS TCPOnly 
  

  reg.x.outboundProxy.transport="<value>"​

• 10 Configure the phone to register concurrently with other servers for the registration. Replace x with the desired line key value. Replace y with the desired server key value. Note that by default, the phone adds the value you specify for y to the set of redundant failover servers.

  By default, parameter reg.x.server.y.failOver.concurrentRegistration=0, which adds

  the value you specify for y to the set of redundant failover servers. If you want to register the server Note:

  concurrently with  other servers, set reg.x.server.y.failOver.concurrentRegistration=1.

  reg.x.server.y.failOver.concurrentRegistration="1"

  11 Save the configuration file.

New Zoom Phone “Warm Transfer” Interoperation

SIP messaging for consultative transfers, also known as “warm transfers,” on phones that support Zoom services must now include call routing information when starting a warm transfer and forwarding the new call to the transfer target. You must add the new routingid key to all phones that use this feature.

The following examples show updates to the Call-Info header to include the new routingid key:

Example 1: Incoming call from a transferee to transferor (routing information within the INVITE message)

Transferor devices receive the INVITE from the transferee with a Call-Info header.  

Call-Info: <action=dialog>;routingid=xx;sid=xx;server=10.10.4.22;set=10.10.4.18;siplb=q a01sipsj01;xx

Example 2: Outbound call from transferor to transferee (routing information within the 200 OK message)

Transferor devices receive the answer 200 OK with a Call-Info header from the transferee. 

Call-Info: <action=dialog>;routingid=xx;sid=xx;server=10.10.4.22;set=10.10.4.18;siplb=q a01sipsj01;xx   

Example 3: Warm transfer (transferor sending the INVITE to the desired transfer target)

Transferor devices must send their INVITE to the transfer target with the Call-Info header containing the routing information they received from either of the above messages (routingid).

INVITE sip:1234@889900.zoomcloudpbx.com;transport=TLS
SIP/2.0 xxxx Call-Info: action=transfer;routingid=xx xxxx

In this scenario, you must also add the action=transfer parameter to the Call-Info header.

Note: The following instructions for “Factory Reset” and “Access the Updater Menu” apply to the new VVX 250, 350, and 450 hardware models. You can identify the new models by reviewing the information in the new Shipping Configuration Engineering Advisory: Product Shipping Configuration Change for VVX Series (EA210826).

Factory Reset

You can perform a factory reset during bootup. 

Procedure

• Power on, power cycle, or reboot the phone.
• Immediately after the headset and hands-free LEDs turn on and off, press and hold the 1-3-5 multiple key combination (MKC) on the dialpad until the factory reset screen appears.
• Enter the admin password. If you don’t have the admin password, you can enter the MAC address instead. The MAC address is located at the back of the phone.
• Press Ok.

Performing a factory reset during boot up also results in a file system format. The phone recovers and the application runs afterwards. 

Access the Updater Menu 

You can access the Updater menu during bootup.

Procedure

• Power on, power cycle, or reboot the phone.
• Immediately after the headset and hands-free LEDs turn off, press and hold the 1-3-5 MKC until the factory reset screen appears.
• Press Cancel a few times, until the countdown screen appears.
• Press Setup.
• Enter the admin password.
• Press Ok.

Older Software:

• Older 6.4.2 release >here<
• Older 6.4.1 release >here<
• Older 6.4.0 release >here<
• Older 6.3.1 release >here<
• Older 6.3.0 release >here<
• Older 6.2.1 release >here<
• Older 6.2.0 release >here<
• Older 6.1.1 release >here<
• Older 6.1.0 release >here<
• Older 6.0.0 release >here<

[SteffenBaierUK]

we just released UC Software UCS 6.4.3 A for all compatible VVX phones (VVX 150, 250, 350, 450 and EM 50, VVX 101, 201, 301/311, 401/411, 501, 601).

What’s New in This Release

Poly Unified Communications (UC) Software 6.4.3 A is a release for OpenSIP deployments. These
release notes provide important information on software updates, phone features, and resolved issues.

• Support of New VVX 250, 350, 450, and EM50 Revision
• Server Redundancy for a Registered Line
• New Zoom Phone “Warm Transfer” Interoperation
• Accessory Update
• Software Updates
  

Support of New VVX 250, 350, 450, and EM50 Revision

Poly Unified Communications (UC) Software 6.4.3 A introduces support for hardware component
changes to VVX 250, VVX 350, VVX 450, and VVX EM50 with the intent to improve the supply profile by mitigating impacts caused by global semiconductor shortages.
For more details about these changes, see Product Shipping Configuration Change for VVX Series
(EA210826) on the Poly Support website.

NOTE: The new Hardware for VVX 250, VVX 350 and VVX 450 will not be able to run older Software.UC Software 6.4.3 is the first release for these phones. They also only run UC Software and cannot be converted into an ObiEdition phone!

Example VVX 350 Console Label and Revision Code

Example VVX 250 Colored Shipping Box Label and Revision Code 

Example VVX 450 Web Configuration Utility

Example VVX 450 Phone UI

Server Redundancy for a Registered Line

You can now configure a fallback server for a registered line on your phones. Procedure

• Open the configuration file.
• Set the phone to send a SIP required to the server that sent the proxy authentication request in the event of a failover. Replace x with the desired line key value.

• req.x.auth.optimizedInFailover="1"

  • Configure the mode for failover failback. Replace x with the desired link key value.

  Note: This setting overrides the configuration  for reg.x.server.y.failOver.failBack.mode.

  Set one of the following values:

  • duration (default) - The phone tries the primary server again after the time specified by reg.x.outboundProxy.failOver.failBack.timeout expires.
  • newRequests – The phone forwards all new requests first to the primary server regardless of the last used server.
  • DNSTTL - The phone tries the primary server again after a timeout equal to the DNS TTL you configured for the server the phone is registered to.

  reg.x.outboundProxy.failOver.failBack.mode="<value>"

  • Configure the time to wait, in seconds before failback occurs. Replace x with the desired line key value.

  Note: This setting overrides the configuration for reg.x.server.y.failOver.failBack.timeout. 

  The default is 3200. The value range is 0 (no timeout), and 60 to 65535.

  req.x.outboundProxy.failOver.failBack.timeout="<value>"

  • Enable the global and per-line reRegisterOn parameter. The existing registrations remain active.

  Replace x with the desired line key value.

  reg.x.outboundProxy.failOver.failRegistrationOn="0"

  • Enable the global and per-line reRegisterOn and failRegistrationOn parameters. Signaling is accepted from and sent to a server that has failed. Replace x with the desired line key value.

  reg.x.outboundProxy.failOver.onlySignalWithRegistered="0"

  • Configure the phone to attempt to register with (or via, for the outbound proxy scenario), the secondary server. Replace x with the desired line key value.

  Note: This parameter overrides reg.x.server.y.failOver.reRegisterOn. 

  reg.x.outboundProxy.failOver.failRegistrationOn="1"

  • Configure the SIP server port to which the phone sends all requests. Replace x with the desired line key value.

  The default is 0. The value range is 65535.

  reg.x.outboundProxy.port="<value>"

  • Configure the transport method the phone uses to communicate with the SIP server. Replace x with the desired line key value:

  DNSnaptr (default)

  TCPpreferred

  UDPOnly

  TLS TCPOnly 
  

  reg.x.outboundProxy.transport="<value>"​

• 10 Configure the phone to register concurrently with other servers for the registration. Replace x with the desired line key value. Replace y with the desired server key value. Note that by default, the phone adds the value you specify for y to the set of redundant failover servers.

  By default, parameter reg.x.server.y.failOver.concurrentRegistration=0, which adds

  the value you specify for y to the set of redundant failover servers. If you want to register the server Note:

  concurrently with  other servers, set reg.x.server.y.failOver.concurrentRegistration=1.

  reg.x.server.y.failOver.concurrentRegistration="1"

  11 Save the configuration file.

New Zoom Phone “Warm Transfer” Interoperation

SIP messaging for consultative transfers, also known as “warm transfers,” on phones that support Zoom services must now include call routing information when starting a warm transfer and forwarding the new call to the transfer target. You must add the new routingid key to all phones that use this feature.

The following examples show updates to the Call-Info header to include the new routingid key:

Example 1: Incoming call from a transferee to transferor (routing information within the INVITE message)

Transferor devices receive the INVITE from the transferee with a Call-Info header.  

Call-Info: <action=dialog>;routingid=xx;sid=xx;server=10.10.4.22;set=10.10.4.18;siplb=q a01sipsj01;xx

Example 2: Outbound call from transferor to transferee (routing information within the 200 OK message)

Transferor devices receive the answer 200 OK with a Call-Info header from the transferee. 

Call-Info: <action=dialog>;routingid=xx;sid=xx;server=10.10.4.22;set=10.10.4.18;siplb=q a01sipsj01;xx   

Example 3: Warm transfer (transferor sending the INVITE to the desired transfer target)

Transferor devices must send their INVITE to the transfer target with the Call-Info header containing the routing information they received from either of the above messages (routingid).

INVITE sip:1234@889900.zoomcloudpbx.com;transport=TLS
SIP/2.0 xxxx Call-Info: action=transfer;routingid=xx xxxx

In this scenario, you must also add the action=transfer parameter to the Call-Info header.

Note: The following instructions for “Factory Reset” and “Access the Updater Menu” apply to the new VVX 250, 350, and 450 hardware models. You can identify the new models by reviewing the information in the new Shipping Configuration Engineering Advisory: Product Shipping Configuration Change for VVX Series (EA210826).

Factory Reset

You can perform a factory reset during bootup. 

Procedure

• Power on, power cycle, or reboot the phone.
• Immediately after the headset and hands-free LEDs turn on and off, press and hold the 1-3-5 multiple key combination (MKC) on the dialpad until the factory reset screen appears.
• Enter the admin password. If you don’t have the admin password, you can enter the MAC address instead. The MAC address is located at the back of the phone.
• Press Ok.

Performing a factory reset during boot up also results in a file system format. The phone recovers and the application runs afterwards. 

Access the Updater Menu 

You can access the Updater menu during bootup.

Procedure

• Power on, power cycle, or reboot the phone.
• Immediately after the headset and hands-free LEDs turn off, press and hold the 1-3-5 MKC until the factory reset screen appears.
• Press Cancel a few times, until the countdown screen appears.
• Press Setup.
• Enter the admin password.
• Press Ok.

Older Software:

• Older 6.4.2 release >here<
• Older 6.4.1 release >here<
• Older 6.4.0 release >here<
• Older 6.3.1 release >here<
• Older 6.3.0 release >here<
• Older 6.2.1 release >here<
• Older 6.2.0 release >here<
• Older 6.1.1 release >here<
• Older 6.1.0 release >here<
• Older 6.0.0 release >here<

[SteffenBaierUK]

Hello all,

based on customer requirements we just release 6.4.3 Rev I 6.4.3.5813 for VVX and 6.4.3.5814 for the new hardware described in Product Shipping Configuration Change Notice (EA210826) 

• VOICE-74313 For the new VVX x50 Hardware, there was an issue with the phones not receiving an IP address on certain switches 

What’s New in This Release

Poly Unified Communications (UC) Software 6.4.3 I is a release for OpenSIP deployments. These release notes provide important information on software updates, resolved issues, and the following phone features.

● Poly Lens Enhancements

Poly Lens Enhancements

This release includes the following enhancements to Poly Lens:

● Improved connectivity
● Fixed critical issues