OpenScape Voice Server V9R4.48.2 Release Notes V1.0 Internal

Release Notes
Release Notes Version: V1.0 Document Owner: Giachalis Aristeidis
Product Name: OpenScape Voice Server

Product Version: V9
Software Release is identified by Version: V9 R4.48.2

Major Release Minor Release Fix Release Hotfix Release
Production Version: V9.00.01.ALL.12 (SMR4) with up to PS48E02

System:
File type Product Item Number / File name Size
iso V9_R4_48.0_UCV9R4_IMG.iso 7,297,040,384 bytes
zip c-V9R4.48.2.zip 8,460,688 bytes
Export Control Classification Data AL: 5D002C1A ECCN: 5D002ENCR
Field Trial: eeQA: Limited Availability: General Availability:
Notice:
This document contains confidential information that is proprietary to Unify Software and Solutions GmbH &
Co.KG. No part of its contents may be used, copied, disclosed, or conveyed to any party in any manner
whatsoever without prior consent.
DECLARATION DATE: Date : Dec 20, 2019
DECLARED BY: Corresponding PL-Development : Ilias Konstantopoulos
DELIVERABLES: Full Release: Delta Release:
Copyright © Unify Software & Solutions GmbH & Co. KG, 2016
Mies-van-der-Rohe-Strasse 6, 80807 Munich, Germany
All rights reserved.
The information provided in this document contains merely general descriptions or characteristics of
performance which in case of actual use do not always apply as described or which may change as a result of
further development of the products. An obligation to provide the respective characteristics shall only exist if
expressly agreed in the terms of contract. Availability and technical specifications are subject to change
without notice.
Unify, OpenScape, OpenStage and HiPath are registered trademarks of Unify Software & Solutions GmbH &
Co. KG. All other company, brand, product and service names are trademarks or registered trademarks of
their respective holders.
Table of Contents
Release Notes .....................................................................................................................................................1
PRODUCT NAME: OPENSCAPE VOICE SERVER .....................................................................................................1
PRODUCT VERSION: V9 .......................................................................................................................................1
SOFTWARE RELEASE IS IDENTIFIED BY VERSION: V9 R4.48.2 ................................................................................1
1 History of change ........................................................................................................................................3
1.1 HISTORY OF CHANGE (RELEASE NOTES)....................................................................................................3
1.2 RELEASE NOTES HISTORY .........................................................................................................................3
1.3 PRODUCT VERSION HISTORY .....................................................................................................................3
2 Important Information .................................................................................................................................5
2.1 INSTALLATION ...........................................................................................................................................5
2.2 UPGRADE / UPDATE ..................................................................................................................................5
2.3 FALLBACK ................................................................................................................................................8
2.4 SECURITY CONSIDERATIONS .....................................................................................................................8
2.5 SPECIAL SETTINGS AND INSTRUCTIONS ......................................................................................................8
3 Reported Problems / Symptoms under Analysis .................................................................................. 10
4 Restrictions, Workarounds and Hints .................................................................................................... 12
4.1 RESTRICTIONS ...................................................................................................................................... 12
4.2 W ORKAROUNDS / HINTS ........................................................................................................................ 17
5 Changes .................................................................................................................................................... 20
5.1 NEW IN THIS RELEASE ............................................................................................................................ 20
5.2 IMPLEMENTED CHANGE REQUESTS ......................................................................................................... 20
5.3 RESOLVED REPORTED PROBLEMS / SYMPTOMS ...................................................................................... 26
6 Hardware and software compatibility .................................................................................................... 31
6.1 HARDWARE REVISIONS .......................................................................................................................... 31
6.2 FIRMWARE RELEASES ............................................................................................................................ 31
6.3 LOADWARE RELEASES ........................................................................................................................... 32
6.4 SOFTWARE RELEASES............................................................................................................................ 32
6.5 OPERATING SYSTEMS (INCLUDING SECURITY ALERTS).............................................................................. 32
6.6 COMPLIANT PRODUCTS (COMPATIBILITY MATRIX) ..................................................................................... 33
7 Service information .................................................................................................................................. 34
7.1 MANAGEMENT INFORMATION BASE.......................................................................................................... 34
7.2 LICENSE MANAGEMENT .......................................................................................................................... 34
7.3 REMOTE SERVICEABILITY ....................................................................................................................... 35
7.4 PRODUCT AND DIAGNOSTICS STRUCTURE IN G-DMS/ SWS AND GSI FLOW ............................................. 35
7.5 DIAGNOSTICS REQUIREMENTS ................................................................................................................ 36
8 Documentation reference ........................................................................................................................ 37
9 Attachment ................................................................................................................................................ 38
10 Appendix A. OSV Single Load Line (SLL) .............................................................................................. 39
Release Note page 2 (of 39) [OpenScape Voice Server V9 R4.48.2]

1 History of change
1.1 History of change (Release Notes)
Version Date Changes Author

Menelaos
1.0 2019-12-20 eeQA Release
Kanavakis
1.2 Release notes history

Version Date Changes
1.0 2019-12-20 eeQA Release
1.3 Product version history

1.3.1 OpenScape Voice Server Images
The following table is a list of OpenScape Voice V9R3 software released for image installations.
SW Version Production Version Contents Release Date G-DMS Note Remarks

V9 R4.38.0 V9.00.01.ALL.12_PS0038 Server Image Installation 2019-02-08 INF-19-000116 GA
V9 R4.39.1 V9.00.01.ALL.12_PS0039E01 Server Image Installation 2019-04-01 INF-19-000158 eeQA
V9 R4.41.0 V9.00.01.ALL.12_PS0041 Server Image Installation 2019-05-24 INF-19-000158 eeQA
V9 R4.45.0 V9.00.01.ALL.12_PS0045 Server Image Installation 2019-08-30 INF-19-000290 GA
NOTES:
1. After the OSV Single Load Line (SLL) introduction, the following two images will be released instead
of one:
• V9_R4_48_UCV7R3_IMG.iso is to be used ONLY by simplex deployments that use SLL, i.e to
upgrade from OSV V8 or V9 to latest V9, while Applications remain on V7R3. – NOTE this IMG
will not be released as UCV7R3 is no longer supported
• V9_R4_48_UCV9R4_IMG.iso is for all the rest deployments (i.e. simplex deployments that will
not use SLL and standard duplex deployments irrespective of whether they will use SLL or not).
For more information on the OSV SLL concept please see the Appendix
2. A USB stick (>= 16GB) is required for physical server installations. For Virtual systems no USB is
needed, the ISO file can be directly connected to the VM. More details on this can be found in the
IUG.
1.3.2 OpenScape Voice Server Images for Virtual Appliance (vApp)

The following table is a list of OpenScape Voice V9 software released for OSV virtual appliance (vApp)
installations.
SW Version Production Version Contents Release Date G-DMS Note Remarks

V9 R0.12.4 V9.00.01.ALL.12_PS0012E04 vApp Installation (.ova) 2016-09-26 INF-16-000386 GA
V9 R3.30.0 V9.00.01.ALL.12_PS0030 vApp Installation (.ova) 2018-05-03 INF-18-000221 eeQS
1.3.3 OpenScape Voice Server patchsets

Contents Release G-DMS Note Remarks
SW Version Production Version
Date

V9 R4.38.2 V9.00.01.ALL.12_PS0038E02 Patchsets 38E01..38E02 2019-02-08 HF005195 GA
V9 R4.39.2 V9.00.01.ALL.12_PS0039E02 Patchsets 39E01..39E02 2019-04-01 HF005245 eeQA
V9 R4.45.1 V9.00.01.ALL.12_PS0045E01 Patchsets 45E01 2019-09-19 HF005430 GA
1.3.4 OpenScape Voice Server MOPs

The following table is a list of cumulative updates that require the use of MOPs (Manual Operation
Procedures), including the location of the respective documents in G-DMS. Unless specifically noted, these
MOPs must be applied after system installation. Items recently released are marked with a star ( ).
Document Number Release Date Released with G-DMS Note Title

P30310-Q3108-Q090-01-7620¹ 2017-09-29 PS29 IMG N/A Upgrade to SLES12-SP1 V9 Set4
P30310-Q3112-Q090-01-7620¹ 2018-03-22 PS33E02 IMG N/A Upgrade to SLES12-SP3 V9
P30310-Q3119-Q180-01-7620¹ 2019-08-07 PS43 IMG N/A Upgrade to SLES12-SP4 V9
Notes:
¹ ONLY delivered with the OSV image. This MOP is not available separately in SWS..
Prior to an upgrade, from a previous release, it is recommended to have all MOPs installed (f/w and
OS updates).

2 Important Information
2.1 Installation
2.1.1 RapidStat report
A RapidStat report must be generated before and after performing any upgrade or downgrade of the switch.
This will help identify any problems that may be caused by the upgrade.
2.1.2 Regarding FQDN & DNS-SRV configuration

It is recommended that geographically separated deployments as well as new co-located deployments follow
the FQDN & DNS-SRV and GEO-SEP guidelines published in G-DMS.
2.1.3 Installing new servers

New installations must use one of the installation methods described in the OpenScape Voice V9, Installation
& Upgrade Guide (IUG).
Notes regarding installation:
- NOTE: If the IBM x3550 M4 is rebooted with the USB drive in the server, the server may attempt to boot
from the USB device. It is recommended that the USB device be removed from the server when
operations with the USB device are completed.
- The Image contains English languages for announcements. If any other languages are needed for the
Integrated Simplex deployment, they must be installed from the Applications DVD after the completion of
the OSV installation
- Change/set the value for Srx/Service/CALEA/VideoTreatment to 0 (default is 1).
Installation Time:
• Simplex: approximately 70 minutes (includes Applications)
• Cluster: approximately 50 minutes
Hints:
• All needed software is listed in chapter 6.4.
IMPORTANT! Consult chapters 2.5 and 4 for important information on settings and restrictions.
2.2 Upgrade / Update

The OSV will support an upgrade (within a given Solution, e.g. V9Rx) without an impact requiring an upgrade
to any other product within the Solution definition. For example, if customers have a V9R1 Solution, then the
V9R1 OSV can be upgraded to any other V9Rx PS/E-PS combination without requiring any other products to
also upgrade.
NOTE: With SLL this statement is also valid when upgrading from V8 to V9, but not when upgrading from
V7! See also the Appendix
2.2.1 Updating the V9 patchset level

IMPORTANT NOTES:
1. V9 customers updating to PS48 and onwards must update using the image & the Toolkit; this method of
updating is required in order to pick up MOPs that are included on the PS48 (or beyond) images.
2. If UC version is below V9R3, do not use the Common Repository location; use OSV Node1 instead. In
this method the cumulative patch must be placed under directory /software/patch/<release name dir> of
node1.

Hint: Once the system was updated to PS48Ex, via one of the PS48Ex images, a Rolling Upgrade may be
performed for subsequent E-Patches.
Updating from a previous V9 patch level to the current level should be done as per the OpenScape Voice V9,
Installation & Upgrade Guide (IUG). If necessary, patchsets may be removed using the procedures described
in the same document.
If updating both the OpenScape Voice Server and OpenScape Voice Applications (CMP, Assistants,
MS), the OpenScape Applications should be updated first, before the OpenScape Voice Server.
Note: emergency patchsets are cumulative. E patchsets that are included in a cumulative patchset will show
as “Patchset – Packaged” in the Assistant; you cannot roll forward to or roll back to a “packaged” patchset –
the option will be grayed out. See this example (taken from V5 but valid also for V6 and beyond):
2.2.1.1 Update via “Common Repository” Method

For the Common Repository method the administrator must upload the corresponding software into the
repository. Only the uploaded software can be selected for software activation. After the software is selected
the administrator selects “Activate” to enforce patchsets to be transferred to the OSV node and then the
normal Rolling Upgrade procedure will be automatically initiated. Consult the Service Manual for more details.
When using the Common Repository, verify that there is no PatchSet file with root permissions on your
OpenScape Voice patchsets directory /software/patch/V9 otherwise the file transfer will fail with error: "sFTP
error - Permissions denied Please delete the existing files".
Important note: If UC version is below V9R3, do not use the Common Repository location; use OSV Node1
instead. In this method the cumulative patch must be placed under directory /software/patch/<release name
dir> of node1.
2.2.1.2 Manual Rolling Upgrade

General notes regarding Rolling upgrades:
• V6 and beyond includes a capability to maintain a “snapshot” of your system in “backup partition” of
the system hard disk, prior to execution of the rolling upgrade. This allows the possibility of
restoring the system to its previous condition, if necessary. This capability is visible in the CMP,
Maintenance, and Inventory section (see screenshot, below). The checkbox “Synchronize two
versions before Sofware Activation” is checked (enabled) by default. This will save the current
system condition to the backup partition before doing the upgrade. The checkbox “Auto continue to
2nd node” should also be checked. For more information, see the OpenScape Voice Service
Manual.

• It is strongly recommended to make a new backup of the system database (or fresh file system
backup) after upgrading. This is because restore of a down-level backup may not be possible.
• When the Assistant is upgraded before the OSV, then a “Partially Compatible” error may appear on
the CMP/Assistant. The error should disappear after the OSV upgrade.
• IMPORTANT! Consult chapters 2.5 and 3 for important information on settings and
restrictions.

2.2.2 Upgrades or Migrations to V9
Instructions for Release Upgrades to V9 can be found in the OpenScape Voice V9, Installation & Upgrade
Guide (IUG).
Notes:
• OpenScape Voice V9 uses an “edge inwards” Solution Upgrade concept. This concept is facilitated
by having nearly all the components in the compatibility matrix (Section 6, below) also released for
use with OSV versions V7R1 and V8R1. This allows solution upgrades to V9 to proceed in a
stepwise sequence, possible over several maintenance windows.
• Upgrades to V9 are possible only from releases V7R1 or V8R1. Customers with an older version
will have to do a two-step upgrade process.
• UC upgrade paths are reported on the UC V9 Release Notes.
• The Image contains English language for announcements. If any other languages were installed
prior to the Upgrade on the Integrated Simplex deployment they will not get preserved and they
must be installed from the Applications DVD also after the completion of the OSV Upgrade.
• Change/set the value for Srx/Service/CALEA/VideoTreatment to zero (default is 1).
IMPORTANT:
• With V9R4, OSV supports SLL for upgrades from V8R1. Please see the Appendix for more information
on the SLL concept and impacts in licensing.
• Prior to a Live Upgrade execute the precautionary cleanup commands mentioned the short-term
restrictions table. This is to protect against a failed upgrade, due to possible leftovers from a past
failed upgrade.
• For single step upgrades to V9R4.48.2, c-V9R4.48.2.zip should be included in the /repository/upload
folder, along with the V9R4.48.0 IMG iso. ( see section 8.3.2.1 of the OSV V9 Installation Guide on
how to do so)
• If IPv6 setup is used in source release, Live Upgrade to V9 may require the following workaround:
Bring Node A to state 3 and back to state 4. Same for node B.
2.3 Fallback
For Fallback procedures refer to the OpenScape Voice V9, Installation & Upgrade Guide (IUG).
2.4 Security Considerations

2.4.1 HiSAT
Please see this HiSat Link for more details.
2.4.2 Operating system specific

OpenScape Voice V9 is based on the SuSE Linux Enterprise Server 12 Service Pack 4 (SLES 12 SP4)
operating system.
Although security updates for this SLES are periodically released by the manufacturer, Unify does not
recommend such updates to be installed “as is“, since they may cause a negative impact on the system. For
this reason, Unify periodically releases selected SLES security updates together with OpenScape Voice
software updates, in the form of MOPs (released with OpenScape Voice patchsets) or embedded in new
OpenScape Voice SMRs.
2.5 Special settings and instructions

2.5.1 Upgrade procedures
If upgrading both the OpenScape Voice Server and OpenScape Voice Applications (CMP, Assistants, MS),
the OpenScape Applications should be updated first, before the OpenScape Voice Server.

Note: When the Assistant is upgraded before the OSV, then a “Partially Compatible” error may appear on the
CMP/Assistant. The error should disappear after the OSV upgrade.
• If a Fusion or UC Web Client call takes place during a live upgrade procedure, the call control window
may disappear. If this occurs, Fusions users should restart the Fusion client Web Client users should
refresh their browser instance.
2.5.2 Parm changes

Please check the Appendix for important information on OSV RTP Parameters.
2.5.3 Transport protocol in the OpenScape Voice Solution

It is strongly recommended to use TCP or TLS transport protocol between the OSV server and the subscriber
devices (phones) as well as GWs, rather than UDP. For new customer installations, TCP or TLS should be
used.
Note: Please also refer to the “Restrictions” section (below) for other important information on
transport restrictions.
Customers which use primarily UDP and are upgrading to V9 are not strictly required to change but are
strongly encouraged to do so.
2.5.4 Signaling protocol changes

Please check the Appendix for important information on Signaling Protocol Changes.
2.5.5 Upgrading OSV within an OSCC-E V3 environment

After upgrading/updating an OSV with “Live Upgrade” the script ‘installExportForOscce.sh’ for OSCC-E has to
be manually executed again even though it might have been executed prior to the upgrade/update. This
ensures that all required settings/scripts are available.

3 Reported Problems / Symptoms under Analysis
Outstanding problems from GSI Flow tickets
GSI Flow
Description
Ticket
NA15793069 XcmRcv restarts possibly caused subsequent node elimination
NA16077994 SA_down to survival authority is quicker than normal (1 second)
NA16245639 Cluster outage during network flapping

NA16284256 pokosv1 kern.emerg kernel: [536225.441049] do_IRQ: 1.172 No irq handler for vector
SnapshotDevice is rejected with CSTAErrorCode (deviceOutOfService), although the device is
NA16269727
registered
NA16336928 CQ00339199: Clone: V8R1.44.0 Found duplicate entries in DB ERROR reported in RapidStat
NA16354310 LicenseManager pstack in V9R3.34.14 - getRemainingDays
NA16379047 V9R3.34.9 SipSM pstack in cSipDialogBase
NA16413990 V9R3.34.12 CSTASM Pstack
NA16425746 EZIP update results to RSA_ENABLED to NO

NCPE 9.4_3.0 Update shows a duplicated SNMP entry message and deletes different SNMP entry
NA16425539
if press OK
Wrong Reg_Process value from Endpoint_t table causes misleading Rapidstat Balancing
NA16441249
information
NA16473422 Endpoints unable to register due to rejected tcp connection (errno=CACHE_FULL)
NA16486030 V9R4.39.05 license pstack in pthread_join

Race condition between JoinCall Request from VoiceRecorder and Re-Invite from GW leaves call
NA16494333
in a undefined state
NA16502732 Several ovl errors reported regarding sipsm lost messages
NA16504192 OSV cancels the Invite to the external destination
NA16484237 FileSystem Backup from CMP Fails to start with Connection refused from Node2
OSV doesn't send QueuedEvent to OSCC after RNA Timeout re-queue if calling party is silently
NA16509332
monitoring and 24_7_extern RTT tracing is active
NA16510002 OSV V9 R3.34.9 Call transfer and Redbox call recorder stays connected to MS announcement.
NA16483115 OSV V9R3.38.3 CFloop mechanism is not working for called numbers longer that 15 digits.
NA16507025 OSV sends Authorization Code to GW when using post dial, if the call is rerouted to a second GW
NA15787504 Snort is unable to start in V9/V8 when FQDN is used as Billing Server address
NA16470096 "ETAkex protocol error: type 7 seq XXX" errors during scp
NCPE Coloring inside the menu for the Outage Free/Outage classification it not in par with the
NA16529118
actual changes causing reboot/outage
OSV switches from MLHG announcement to MoH announcement after a re-INVITE from the A-
NA129479
Side.
NA16546309 OSV V9R4.41.2 SIPsm pstack
NA16550832 Upgrade V7 -> V9: Feature profile for CFB has different data
NA16552441 SNORT blacklists IPSL PC during performance test
NA16555708 DB-Error 3 when creating OSMO subscriber

OSV redundancy testing, remaining OSV node doesn't always take over the Signaling VIPs from
NA16563973
the failed node
NA16565602 Admin line 3131 was in RED/In-Use, but no actual call in the line, calls blocked
NA16573108 Sipsm pstack in cSdpNegotiator::getSdpBestEffortSrtpType
NA16573597 cdm pstack, failed healthcheck after Communication link failure

NA16576321 cstasm pstack in cSipSmMessageHandler::HandleEventForUaCstaRequest
NA16577334 SIPSM Pstack - setCisDisplayInfoFromPAI
NA16522948 CSTA link down between OSV and UC while OSB Assistant is trying to synch with OSV
PRB000048032 OSB/OSS Assistants show OSB/OSS units refering none existing OSV System
NA16580175 CSTA DeflectCall of internal caller from MLHG queue to CDSS port not working.
NA16581787 Slow but steady sipsm memory leak observed at customer
NA16546041 Call transferred (via CSTA request) to a busy external preferred device is dropped
NA16585460 Sporadically the calls could not be established, when using SILM and CAC is enabled
NA16361113 NCPE V9.4-2.0 doesn't apply the same RSA 02 IP address on Integrated Simplex
NA16014361 license restoration during toolkit upgrade failed at node1
NA16590114 sipsm pstacks - continously written pstacks
NA16594485 rolling acarscan pstack in node2 followed by NRF
NA16529272 srxqry must have a clear warning towards the administrator if the node has not joined the cluster.
NA16600873 OSV is not sending ACK for the 200ok received.
NA16469920 Update from V9R2.24.5 to V9R3.34.22 failed due to special character $ in dba pass
NA16593167 Node1 System Freeze (Step: Stopping RtpDb) from State3 to State2
Outstanding problems for FRNs

See Section 5.2 for the FRN list
FRN Description Fixed in
FRN10825 The SIP related functionality is delivered in V9R3.34.3 - the MGCP functionality will be
delivered in an upcoming HotFix

4 Restrictions, Workarounds and Hints
4.1 Restrictions
4.1.1 Short-term Restrictions
These restrictions are expected to be cleared with a future SMR or Patchset release, or via a correction to one
of the products in the OSV Product Matrix (see Section 6).
Ticket Description Deployment Workaround
After installation of V9R4.48.2 and executing Please ignore this error

Rapidstat the following error occurs: All
”The Following unknown binaries are
present on {node name}:
librestclient-cpp.so.1”
Error message: “Error while starting the upgrade. Close the pop-up window with the error, go
This is because there may be a problem with the All back to Applications menu, select again
communication or because the installation of Upgrade Version and the upgrade status
toolkit may have failed.“ when live upgrade starts should now be visible.
via Composer CMP.
Depending on the UC version, Synchronization of Execute ~srx/bin/sync8k -auto
the two versions before Software Activation may All manually on node1 prior to the Rolling
not work! Upgrade.
Do not use the Common Repository; use
When using an Assistant version prior to V9R3, a OSV Node1 instead. Upload the cumulative
V9R3 OSV HF cannot be installed via Rolling All patch under OSV node1 directory:
Upgrade when using the Common Repository /software/patch/V9. Alternatively, if possible,
update to the latest V9R3 Applications level.
Manually reboot and select to boot from the
fallback partition (do not select the Install
No automatic fallback after Live Upgrade failure All
Softswitch option). After bootup login and
execute ~srx/bin/activate8k -done
Execute as root user (on both nodes in case
of Cluster)
umount -l /var/mnt/active/root
umount -l /var/mnt/fallback/root
umount -l /var/mnt/img/optimg
rm -r '/updateSW/*'
Precautionary Cleanup commands
This to protect against a failed upgrade, due
Note: The fix is already delivered with Toolkit All
to possible leftovers from a past failed
V1.09-61
upgrade so the following messages can be
ignored:
umount: <DIR>: not mounted
/bin/rm: cannot remove
'/updateSW/*': No such file or
directory
Change RTP parameter
Srx/Sip/PassiveForkingEnable to RtpFalse
via OSV Assistant
In case OSV is to function as a SIP UAC to
No Media Server Announcements after Fresh IMG SIP forking responses, (supporting MS
All
installation Skype for Business Media Bypass), extra
configuration steps should be followed, as
described in documentation: OpenScape
Solution Set V9, OpenScape Voice with MS
Skype for Business
Reboot and select the other side (the one
that was active prior to the activate8k) then
Cluster Interconnect fails after activate8k -auto Std Duplex
instead of activate8k -auto run activate8k on
each node and reboot manually
Restart symphoniad OR Assign CSTA and
Web Client call not initiated when the caller has a
All ONS services directly (and not via a Feature
subscriber from another BG as its OND Device
Profile)
ALI data are not displayed when 'Row' and NG911 Keep the default value of the RTP parameter

'Column' numbers are used inside 'Srx/Service/E911/ANIFieldParseInfo' to
'ANIFieldParseInfo' NPA-NXX-TN
You can ignore this error – this is a
RapidStat ERROR: Database FileSpec is greater
All RapidStat check issue that will be fixed in an
than the valid one for that configuration
upcoming release
Limited visibility to first 1000 subscribers when
The user can only add a subscriber out of
trying to add a new one under an Emergency All
this range by querying it's ID
Department
4.1.2 Long-term Restrictions

These major restrictions are expected to remain applicable over the lifetime of V9.
Description Deployment Workaround

Those are newly introduced, permanent security restrictions.
Root user cannot connect to OSV nodes via ssh
User sysad can still connect via ssh with password
with password authentication. ALL
authentication; also root user can connect with public key
Session timeout has been decreased.
authentication.
The requirements for passwords are 2 Upper case, 2 Lower
Each sysad password change attempt fails case, 2 Numeric, and at least 1 special (2 for JITC)There is
ALL
claiming password is too easy also a limit of 3 repeats for the same character class.Also, for
a JITC system there must be at least *15 *characters!
• NOTE: OptiPoint 410/420 SIP devices are not longer supported, even for backward
compatibility purposes. OpenStage or Deskphone IP phones or supported soft clients are
the alternatives. *
• OpenScape Mobile Connect is no longer supported, even for backward compatibility purposes.
OpenScape Mobility is the replacement solution. *
• Comdasys proxy is no longer supported, even for backward compatibility purposes. OpenScape
Branch is the replacement solution. *
• RG2700 is no longer supported, even for backward compatibility purposes. Use a supported
gateway shown in Section 6, below. *
• OptiClient-S is no longer supported, even for backward compatibility purposes. OpenScape
Personal Edition or one of the OpenScape UC clients are replacement options. *
* To protect customer’s investment in older technology, Unify will continue to support solutions containing
such products on a best effort basis. However, while basic functionality can still be expected from these
products, if any faults/problems occur it may not be possible to address them. Customers will then have the
choice of either tolerating those issues or purchasing a replacement product.
• Customers must use the HW models specified in Section 6 of this document.
• Regarding OpenStage Video calls (FRN5571): this is released only for OpenStage to OpenStage
calls. Interworking with other video equipment is not released
• Directory numbers for OpenScape Contact Center agents should NOT be configured on multiple
devices; that is, OSCC agent DNs should not use the "multiple contacts" or "multiple prime lines"
feature.
▪ Regarding Concierge V3:
o While a Concierge V3 attendant is busy in a call, 4K users cannot invoke these features
(over SIP-Q) towards the attendant: emergency override, camp-on override or forced
release; attempts to do so will fail. No workaround.
• Regarding OSV integration with HiPath Cordless devices:
o In the OSV subscriber settings for Cordless devices, the secure media setting should be
set to “SRTP disable”. Cordless IP devices will not be able to complete a call to another
device that is “SRTP only”, either MIKEY or SDES“.
o "Call Transfer on Ringing" by a Cordless device in a branch office that goes into
survivability mode is not supported.

o Cordless IP stable calls may drop if there is an OSV failover, if the OSV is geo-separated
using different subnets for the OSV nodes.
• Regarding interworking with the OpenStage WL3:
o WL3 users cannot use the OSV feature “Call Park to Server”
• Restriction for Integrated Simplex deployment
The Media Server SIP endpoint in the OSV Integrated Simplex deployment shall be associated
with the non-standard port numbers 5062 (SIP) and 5063 (SIP-TLS) for signaling between OSV
and the Media Server.
Change the Integrated Media Server SIP listening ports via CMP from 5060/5061 to 5062/5063. If
you need to create a SIP endpoint for the MS, use ports 5062/5063 as well. Configure the MS SIP
endpoint alias with an IP address and a port number, e.g: “MS_IP_address:MS_SIP_port". Update
the corresponding packet filter rules with the new port numbers.
• Regarding IBM x3550 M3 platform:
o Shutdown OS option using the IMM is not supported. Workaround:
▪ From the IMM’s left navigation tree, select Tasks => Remote Control. Open a console
screen and enter the following:
# /unisphere/srx/3000/srx/startup/srxctrl 2 0 (takes the node to state 2)
# halt (halts the node)
▪ From the IMM’s left navigation tree, select Power => Restart. Depending on what is
desired:
Click “Power off Server Immediately” or “Restart Server Immediately”.
• No rerouting to the next conference server in case of CAC restriction.
• Regarding Fax T.38 interoperability between OSV and HiPath 4000: the G.711 codec must be
enabled between the OSV endpoint and the 4K in order for negotiation to use T.38 to be
successful.
• Regarding branch operation using a Survivability-Proxy e.g. OpenScape Branch
o Calls established from a subscriber via the proxy to the OpenScape Voice Server, will
retain their voice path even if the proxy suffers an outage while the call is still in progress.
However, further feature activation attempts, e.g. consultation, from the subscriber are not
supported and may lead to call-drop.
o Also, following the proxy outage, calls will get dropped upon the next session timer expiry.
• TLS / SRTP related restrictions:
o Gateway Cisco 3725 does not support TLS and also does not support SRTP. Calls from a
secure endpoint to one of these gateways are negotiated from SRTP to RTP.
o The following SIP endpoints do not support SRTP but can negotiate from SRTP to RTP:
Wireless WL2 and analog adapters AP11xx.
o Wrong audible-secure-call-alert tone for secure calls with Optipoint to HiPath4000.
o Regarding behavior with audible-secure-call-alert:
• OpenStage phones play audible-secure-call-alert only for calls which change
from secure to not secure.
o TLS/SRTP should not be used when interfacing to a Microsoft UM or Mediation Server.
• The OpenScape Voice “Path Replacement” feature should be ON in all switches for configurations
with 2 or more switches interconnected with SIP-Q
• Session Timers
o Do not activate session timers on other components in the OpenScape Voice solution,
including phones, gateway and other supporting servers (e.g. Xpressions). The OpenScape
Voice Server will act as the refresher for components in the solution. Activating session timers

in the devices is not supported except OpenScape Voice supports session timer activation
from the HiPath 4000.
o The Session Timer should also be deactivated in Xpressions (set parameter
sipSessionTimerExpiration = 0).
o To enable session timers change the RTP parameter Srx/Sip/Session_Timer to “YES”
(without quotes). A session timer will be activated for each call starting from when the RTP
parameter is changed.
o A quick overview of session timer:
• The goal of session timer is to detect & clear “lost” calls
• Session timers are implemented according to RFC 4028.
• To detect a lost call the OpenScape Voice Server will “poll” the devices involved in the
call by sending an INVITE to those devices
• This INVITE has the same SDP used in the last message (with SDP) sent to that
device. This is the difference between session timer and a regular INVITE: there is no
change to the SDP.
• If the devices do not send a positive response (200 OK) or fail to respond to the INVITE.
The call is disconnected and internal system resources are recovered.
• This process happens once every 30 minutes for each call (with the default configuration).
The relatively large refresh time is used to reduce the message traffic in the network.
o Special instructions for specific devices:
• RG8700 gateways: if using RG versions below SMR3 (13.31.01.25), turn on full SDP
comparison to workaround session timer issues present in earlier RG loads.
• To turn on full SDP comparison, change the RTP parameter
Srx/Sip/CompareSdpBody to 1
• Once the RGs are upgraded to the latest versions, change the parameter back to 0
(zero). The full SDP comparison increases the load in the system
• Do Not Disturb limitation via SIP-Q between two OSV servers: if DND is activated via the CMP for
a given subscriber, if that subscriber is called via SIP-Q, the caller will hear an “all circuits busy”
announcement, instead of a DND announcement. Note: the correct announcement is heard if
phone-based DND is used.
• Regarding FRN2683, “SDP Backward Compatibility for Best Effort SRTP”
o Static endpoints are not allowed to have “SRTP Automatic”
o SIPQ endpoints should only be allowed “SRTP ON”
• Xpressions related restrictions
o Xpressions Web client and conferencing plug-ins are not part of the OSV solution.
o No fax transmission from Xpression to any target possible, if both sides have their codecs in
different order; meaning: have to have devices use same codecs in same order. Not a new
restriction with either OSV or Xpressions. Same restriction existed with OSV V4R1 and prior.
• Regarding ASC Recording
o When using the ASC Recording, the Silent Monitoring Tagging Feature should not be
assigned to any of the parties involved in the scenarios (calling party, MLHG Pilot, MLHG
members.
o Local (phone-based) conferencing is not supported in combination with ASC recording. If
attempted, the call will stop being recorded when one party drops from the conference; use
OSCV based large conference instead.
• Regarding FRN469“, "Non-Service affecting method to add and delete OSV static routes"
o IPv6 is not supported by the utility provided with OSV to add/delete static routes.
• Regarding use of the " tethereal" command on the OSV server:

o If tethereal is started "without" the -w option a corresponding /tmp/etherXX... file is created
and upon exiting the temporary file remains. Each time the process is initiated without the -w
option, a file is created which can fill the /tmp partition and can cause a node failure.
Administrators should take care to remove old/uneeded files.
• Regarding interworking with the OpenStage WL3:
o A user’s WL3 number should not be used as an OSC UC ONS number.
o Known issues on interaction between WL3 and OSC UC:
• If WL3 is being used by an OSC UC user as an OND and the user attempts consultation
or alternate via UC, the attempt will fail.
• If a WL3 user is talking to a UC user who gets or makes another call via UC, the attempt
to alternate back to the WL3 user will fail.
• The locked padlock of a secure TLS call becomes unlocked if an OpenStage phone calls
a WL3 running when a session refresh occurs.
• Regarding Video Calls & Video conferencing using the OpenScape Media Server (“Video MCU”):
o The following are known issues with video:
o Intermittent, on a direct call between OSC Desktop or PE client and a Polycom
VVX, the video stream may be lost on the Polycom.
o Certain Lifesize units have a problem with Session Refresh from the OSV,
disrupting a call in progress.
o For the Polycom VVX1500 unit, the software level should be v3.3.1.0933 or above. Below
this level, video calls from the OSC PE client to the Polycom may fail.
o OpenScape Personal Edition does not support making video calls within the branch when
the branch is in survivability mode.
o Configuration hints/tips for Video MCU:
o Consult the UC Installation & Upgrade guide for information on the required
hardware or virtual environment for the Video MCU.
o Enabling Video for the OSV:
o In the CMP menus under Configuration -> Unified Communications →
Connections -> OS Voice, bring up the window for your OSV system
("OpenScape Voice Connection" window) and in the pull-down list for
"versions, select "OpenScape Voice V9.0 Video".
o Enabling Video Conferences:
o In this example, "offboard" is the default name of the backend server of the
large deployment:
CMP->Maintenance->Inventory->Nodes->offboard, show the dashboard of

the offboard server and select SHOW SERVICES STATUS.
o Filter for the Conferencing Service, edit this service
o The property "forceVideoConferences" should be set to true (default is
false).
o Configuration of the Video MCU Endpoint in OSV:
o The attribute "Allow Sending of Insecure Referred-By Header" should be
checked.
o EP Alias should be the IP address of the Media Server
o If servicing older video units from LifeSize (e.g. 4.7 software):
o CMP-> Unified Communications -> Media Server -> MS Nodes (e.g.
MediaServerConference1) -> Streaming (RTP) -> default: the RTCP
Reporting box should be checked.
• Regarding Speed Dialing:

o Administrators should remove references in Feature Profiles or from individual
subscribers *BEFORE* deleting the Speed Dial list itself. Failure to do this will result in the
following symptom: when you edit the subscriber with the Assistant, in the FEATURES
tab, no features will be listed. Workaround: if you encounter a subscriber in this situation,
you can use QUICK EDIT to edit the subscriber, remove the Speed Dial entry, then
SAVE. The Subscriber should be editable normally after doing this. Branch related
restrictions
• Regarding the new “Continuous Silent Monitoring” feature (V7R0 and beyond):
o The Silent Monitor feature from OSV V6 and prior has been replaced by the “Continuous
Silent Monitor” (“CSM”) feature. CSM does not work the same as the former SM. See the
OSV Documentation for details.
4.2 Workarounds / Hints

4.2.1 Workarounds
1. Change/set the value for Srx/Service/CALEA/VideoTreatment to 0 (default is 1)
2. Regarding OpenStage V3R1: OpenStage F/W version 3.1.43.0 and above, has a correction of an error
which was incorrectly causing calls to be Auto-Answered on the OpenStage devices when CTI Allow
Auto-Answer function was disabled. This resulted in users (without headsets) complaining that their
phones would enter hands free mode. It is now mandatory to have CTI Allow Auto-Answer enabled to
allow the OpenStage to automatically answer the call, if CTI Allow Auto-Answer is not enabled you
will receive a “The requested task could not be accomplished” error message. Please refer to INF-
13-000367 for further information and workaround instructions.
3. The backward compatibility for OSB interaction is impacted based on the RTP parameter
“Srx/Sip/CentralSbcSupport” if the value is RtpFalse. When the RtpFalse value is set the endpoint
association performed during registration will not be maintained. Although the calls to subscribers may
work, calls to FXS ports in the OSB will not be able to receive calls. It will be necessary for the RTP
parameter “Srx/Sip/CentralSbcSupport” be changed to RtpTrue (before the upgrade is suggested). If the
parameter change is performed after the upgrade, each subscriber which is associated to a branch will
have to wait until their next re-registration or a reboot of the OSB to force re-registration branch wide.
4.2.2 Technical hints
4.2.2.1 Knowledge base documents

The following table contains links to G-DMS documents with procedures and other information that is not
included in the Product Documentation. Such documents are provided directly by System Test, GVS and
Development, including certain MOPs.
Release Date G-DMS Note Title
None
Note: Items recently released are marked with a star ().
4.2.2.2 Important information regarding patching

While installing a new patchset, it will be verified that all emergency patchsets being simultaneously rolled out
are obsoleted. It will not be possible to roll in a new patchset that does not obsolete all emergency patchsets.
For example, if the system is currently at PS7E4, and the user wants to install PS8, but PS8 does not contain
all the fixes from 7E4, the user will not be able to roll from PS7E4 directly to PS8. The user will have to either
roll to a later patchset which does include all the fixes form 7E4 (i.e. PS9) or first remove the E patches which
are obsoleted by PS8 (i.e. PS7E4 and PS7E3 need to be removed in one operation if they are obsoleted by
PS8, then it is possible to roll directly from PS7E2 to PS8). This restriction is true for both the GUI-based
method of rolling upgrade, and the CLI-based method.

4.2.2.3 MWI delivery with international numbering schemes
The values allowed for the RTP parameter Srx/Main/MwiNatureOfAddress are 0 (Unknown), 1 (National) and 2
(International). If your environment is currently configured to have all DNs identified as fully qualified
international (E.164) numbers (as recommended), the RTP parameter Srx/Main/MwiNatureOfAddress may be
left as 2 for upgrades. However, for new installations it is recommended to set the value of this RTP
Parameter to zero (0). When set to 0 and provided the RTP parameter
Srx/Main/MwiEnablePrivateNumberingPlan is set to RtpTrue (as recommended), the routing of MWI
notifications should follow the same path through translation as Voice calls initiated by the voice mail server,
starting by finding a match in the PAC table of the numbering plan of the endpoint created for the voice mail
server.
4.2.2.4 Regarding configuration of Media Servers in branch offices

Please consult the following documentation if you require installation & configuration of a Media Server in a
Branch Office: Media_Server_Configuration_Instructions_IUS.pdf in INF-09-000426.
4.2.2.5 About “SIP Private Networking”

This feature is PSR, therefore it should not generally be used. SIP-Q is the recommended method to
connect two or more OSV systems., However, FRN2548 introduced some general changes in Endpoint
Programming.
4.2.2.5.1 Definition of terms

SIP-PN is PSR & proprietary; generally this option should not be used.
SIP-Q is the SIP + QSIG based interface which provides a feature-rich interface between OSV systems and it
is the interface to widely-used legacy Enterprise equipment such as the HiPath 4000 and HiPath 3000. The
RG8700 gateway also supports SIP-Q.
SIP Trunking: this term refers to a standards-based SIP interface used between OSV and a gateway or other
type of SIP server. Examples:
▪ Gateways: RG8700; Mediatrix; OpenScape Branch; other third party GWs
▪ Other SIP Servers: Xpressions; other third party IP-PBXs
4.2.2.6 Important endpoint administration settings

“SIP Private Networking”:
▪ This attribute IDENTIFIES a SIP interface as a SIP-PN interface.
▪ Attribute checked means: the interface is a SIP-PN interface
▪ Attribute NOT checked means: the interface is NOT SIP-PN; other attributes must be interrogated to
know what kind of SIP interface it is (SIP-Q or SIP Trunking)
▪ IMPORTANT: SIP-PN is PSR; do not check this attribute!
“Public/Offnet Traffic”:
▪ This attribute is ONLY meaningful (applicable) on SIP TRUNKING interfaces. That is, the attribute
should be grayed out for any interface other than SIP TRUNKING.
▪ Attribute checked means: (1) when there is an incoming call on this interface, the OSV network shall
assume the caller is a public/off-network party, i.e., a party in the PSTN. (2) for an outgoing call on a
SIP Trunking interface, if this attribute is set, only public (E.164) numbers are allowed to be sent, for
the Calling Party (also for Diversion header)
▪ Attribute NOT checked means: when there is an incoming call on this interface, the OSV network shall
assume the caller is an internal (private network) party, i.e., a subscriber somewhere in the
customer’s private network. Note: the caller is NOT necessarily an OSV subscriber – it could be a
subscriber on a HiPath 4000, HiPath 3000 or a third party PBX. Note: if the endpoint is in a different
BG than the called party, the call is still considered external because it is crossing BGs.
“SIP-Q”:
▪ This attribute IDENTIFIES a SIP interface as a SIP-Q interface.

▪ Attribute checked means: the interface is a SIP-Q interface
▪ Attribute NOT checked means: the interface is NOT SIP-Q; other attributes must be interrogated to
know what kind of SIP interface it is (SIP-PN or SIP Trunking)
”Originating Signaling Type”:
▪ This setting should always be set to “undefined” for routes between two OSV servers.
"URI in Telephone Subscriber Format ": starting with V6 PS18, this attribute has been renamed to " Send
International Numbers in Global Number Format ”GNF)".
4.2.2.6.1 Important RTP variable

With V5 and beyond, this variable is no longer used. Instead, the determination of what type of
number to send and what digits to send is done by proper configuration of the Display Number
Modification tables.
Srx/Main/OutGoingCallingPartyNumberType
4.2.2.6.2 SIP-Trunking endpoint configuration

Prior to V4 R0, we recommended configuring gateways to/from the PSTN in a BG different than the
subscribers. By doing this, it forced the system to treat the calls as external.
Starting with V4 R0, the gateways should be configured within the same BG as the subscribers. The new
“Public/Offnet Traffic” attribute now controls whether the system treats calls as internal or external.
Note however: to get the desired results, the Solution administrator has to configure the gateway and/or the
equipment behind the gateway such that all private network calls lead to an endpoint with the Public/Offnet
attribute OFF, while PSTN calls lead to an endpoint with the attribute ON. Even then, call transfer scenarios
could result in situations where the OSV handles the call one way (e.g. as an internal call) when the caller is
really the other (e.g. a party in the PSTN). Given the inherent limitations of SIP, this cannot be avoided.
4.2.3 Support of a balanced load configuration

Prior to V4R1, it was stated as a restriction (see Section 3.1 (or 13) of previous Release Notes) that all
subscribers and endpoints need to be registered to Node 1 of an OSV cluster. Beginning with V4 R1, this
restriction is removed.
Subscribers and endpoints may be balanced between the two nodes. Using a balanced distribution is most
applicable to geo-separated installations.
Note: it is not required to use a balanced configuration; it is still permissible to have all subscribers/endpoints
register to one node.
4.2.4 OSV to Hicom 300 configuration

Mandatory configuration change for OSV systems connected to Hicom 300 via RG or via HiPath 4000; without
this configuration change certain call scenarios (e.g. hold/retrieve) will result in lost speech path.
Set the parameter Srx/Sip/sipq_send_CN_NI to RtpTrue with CLI.
The default value was changed with a patch. If not, set to RtpTrue.
4.2.5 Virtualization
Please see the OpenScape Solution Set V9, OpenScape Virtual Machine Resourcing and Configuration
Guide regarding Virtualization Installation.
4.2.6 MIB changes

5 Changes
5.1 New in this release

This section describes the new features and functionality for the OpenScape Voice Server.
5.1.1 Interoperability to Circuit (ATC)

The OpenScape Voice platform has now the option to connect to the Circuit product.
Circuit Web Clients can be connected to OpenScape Voice via the Advanced Telephony Connector (ATC).
Circuit – UC coexistence in the same OpenScape Voice system:

– A user’s ONS must not be configured for a parallel usage of UC and Circuit. This is an application
restriction and it is not supported by Circuit and UC.
5.2 Implemented change requests

5.2.1 FRNs
For more information for the features below, please refer to the Feature Description in e-doku. Items recently
released are marked with a star ().
FRN # ENTopinfo-R Title SW Version
CAC Group Measurements
FRN10226 RQ00039279 should be expanded to support V9R0.11.0
Managed Services SLA Reports
RQ00039384,R
FRN10222 Disable Recall for Manual Hold V9R0.12.0
Q00039566
CSTA: Support OSMO OND for
FRN9813 CSTA Consultation and V9R0.12.0
compound services
FRN10608 MOP for V9 SLES12 update V9R0.12.9
Solution Test OSB V9 with
RQ00039409 OpenScape Enterprise V9 V9R0.4.0
FRN10002 solution
OSV V9 TSA, Security Checklist
FRN10010 V9R0.4.0
and PSA
Wave Evolution - Basic
Phone(WE1): Solution test and
RQ00039390 V9R0.4.0
release for OpenScape Voice
FRN10018 solution V9
Solution Test OpenScape Voice
RQ00039231 V9R0 and OSCC-E Concierge V9R0.4.0
FRN10031 V3R1 (with CC)
Solution Test OpenScape Voice
RQ00039230 V9R0 and OSCC-E Concierge V9R0.4.0
FRN10032 V3R1 (w/o CC)
Test UC V9 with OSV V7R1,
FRN10045 V9R0.4.0
V8R1 and V9
SLES 12 - Image Installation and
carryover of OSV Installation, V9R0.4.0
FRN10082 backup and restore from USB
Black Duck Scan - OpenScape
FRN10088 V9R0.4.0
Voice V9
PMT (Pstack Matching Tool) for
FRN10108 V9R0.4.0
JIRA and OSV
MTLS Load Run in Support of
FRN10110 V9R0.4.0
JITC
Solution Test HCIP V1R6 with
FRN10127 V9R0.4.0
OSV V9 solution
FRN10136 Upgrade OpenScape Voice V9R0.4.0

V7R1 and V8R1 to V9
Migration of OSV V7R1 and
FRN10137 V9R0.4.0
V8R1 to OSV V9
Test the Upgrade Sequence to
OpenScape Enterprise Solution V9R0.4.0
FRN10140 V9
Carry Over of FRN9491 :
Interoperability with Best Effort V9R0.4.0
FRN10143 DTLS-SRTP
Legal Entity Renamed to Unify
Software and Solutions GmbH & V9R0.4.0
FRN10152 Co. KG
Solution test Mediatrix SW
version V2.0 R34.6xx with
RQ00039489 V9R0.4.0
OpenScape Enterprise V9, V8
FRN10168 and V7
Performance Test for
FRN10220 V9R0.4.0
OpenScape Voice V9
Regression Test OS Voice V9
with the OpenStage V3R4 & V9R0.4.0
FRN10240 Desk Phone V3R4 Families
ETSI / EENA NG112 Emergency
FRN10334 V9R0.4.0
Communications Plugtest
OSV needs to support SLES 12
FRN10387 V9R0.4.0
SP1 (Service Pack 1)
Merge Unicode Display and
FRN4453 RQ00037967 V9R0.4.0
Display Fields
Test and release OS FM V9 with
FRN8992 V9R0.4.0
OSV V9 Solution
OS Voice sending an Agent
FRN9367 RQ00038408 V9R0.4.0
Header
Notification of encrypted calls on
RQ00038523,R
behalf of Network EPs and 3rd V9R0.4.0
FRN9418 Q00038830
Party Device EPs
Enabling OSV SIP Challenge 401
FRN9682 RQ00039008 V9R0.4.0
per Message Type
Busy on busy for ONS incoming
FRN9855 RQ00039064 V9R0.4.0
call
CSTA SDK Support for FRN9855
Busy on busy for ONS incoming V9R0.4.0
FRN9896 call
FRN9906 OSV on SLES 12 V9R0.4.0
Solution Test OS SBC V9 with
RQ00039302 OpenScape Enterprise V9 V9R0.4.0
FRN9919 solution
Modify SIP header during
FRN9931 RQ00039145 V9R0.4.0
transfer to voicemail
Blocking of incoming numbers
FRN9932 RQ00039158 V9R0.4.0
within OSV
CSTA monitoring and Release or
RQ00039351 Deflect of Network Interfaces V9R0.4.0
FRN9962 (SIP TRUNKS)
CSTA SDK Support for FRN9962
CSTA monitoring and Release or
V9R0.4.0
Deflect of Network Interfaces
FRN9965 (SIP TRUNKS)
OSV V9 to support
RQ00039505 Lenovo(former IBM) x3550 M5 V9R0.6.0
FRN10096 server
JITC - Enhance Malicious Call
FRN10593 V9R0.6.11
Trace to support DoD Call

Tracing Requirements
JITC - JITC Certification with the
FRN10787 V9R0.6.11
MicroAutomation PSAP Solution
FRN9643 RQ00038476 MLPP - DoD UCR2013 V9R0.6.11
FRN9644 AS-SIP Features V9R0.6.11
FRN9645 PRACK Support for JITC V9R0.6.11
AS-SIP Basic Call Support - Part
FRN9647 V9R0.6.11
1
FRN9648 LSC Failover & Survivability V9R0.6.11
FRN9649 SCIP Phone Support V9R0.6.11
FRN9650 LSC Cybersecurity V9R0.6.11
Support OS Voice V9 JITC
FRN9941 RQ00039283 V9R0.6.11
Certification for Media Server
FRN9969 V9R0.6.11
2
FRN9970 V9R0.6.11
3
Step 2 of FRN5593 : PBI: OSV
FRN10144 RQ00034702 V9R0.8.0
Installation from USB
OS Solution V9 interworking with
FRN10236 RQ00039406 V9R0.8.0
MS Skype for Business (SfB)
Test OSV V9 with ESXi V5.5,
FRN10211 RQ00039643 V9R0.8.3
and ESXi V6
Test of the MLPP feature
interactions in a non JITC V9R0.8.3
FRN10219 environment
Carry Over of FRN 9989: OS
Voice 200K DNs in a Virtualized V9R0.8.3
FRN10244 configuration - Vodafone / MOJ
FRN7092 RQ00036629 Encryption Licensing V9R0.8.3
OSV: Testing of Domain Based
FRN8762 RQ00035007 V9R0.8.3
Routing
Enhanced SIEL ID
FRN10197 RQ00039262 V9R0.9.0
Reporting/Display
Emergency LIN in PIDF-LO NAM
FRN10372 RQ00039878 V9R1.13.0
field
Execute CIS-Security Tests on a
FRN10586 V9R1.15.0
hardened OSV
OSV V9R1 TSA, Security
FRN10444 V9R1.15.1
Checklist and PSA
FRN10445 V9R1.15.1
Voice V9R1
Upgrade OpenScape Voice
FRN10512 V9R1.15.1
V7R1, V8R1 and V9 to V9R1
FRN10523 V9R1.15.1
OpenScape Voice V9R1
Update to PSR15552 for
FRN10561 V9R1.15.3
Telefonica
Fallback Routing keeping the
FRN10307 RQ00039800 V9R1.18.0
modified number
CAC Enhancement for Video
FRN8243 RQ00035720 V9R1.18.0
(TIAS consideration)
Single Load Line (SLL) concept
FRN10386 V9R1.19.0
for OSV
LSC Management and
FRN9651 RQ00036829 V9R1.19.0
Accounting
FRN10472 Support IPsec with strongSwan V9R1.20.0

JITC Certification Test General
Dynamics Sectera vIPer V9R1.21.0
FRN10646 Universal Secure Phone
FRN10807 T-Metrics Attendant for LSC V9R1.21.0
T-Metrics ACD for OS Voice
FRN10808 V9R1.21.0
LSC/ESC
AS-SIP Call Transfer &
FRN9646 V9R1.21.0
Conference (REFER Method)
Support ELA Voice Only (IPT)
FRN10417 V9R1.21.2
Licenses
Migration of OSV V7R1, V8R1
FRN10513 V9R1.22.0
and V9 to OSV V9R1
Use VMXNET3 NICs for
VMWARE virtualized V9R1.22.0
FRN10619 environments for OSV
OSV Audit Subsystem
FRN10188 V9R1.22.2
Improvements for JITC Support
Carry Over of FRN10608 : MOP
FRN10788 V9R1.22.2
for V9R1 SLES12 update
V9R1 JITC IA Findings
FRN10576 V9R1.22.3
Resolution
FRN10667 JITC regression for OSV V9R1 V9R1.22.3
Updated Lenovo x3550 M5
RQ00039505 configuration ( incl. new CPU v4) V9R1.22.4
FRN10623 for OSV V9
Emergency Call Preemption of
RQ00040507 existing calls on Carrier V9R2.23.0
FRN10635 connections
Call completed elsewhere
RQ00040323 indication for Direct Station V9R2.23.0
FRN10665 Selection pickup
FRN10754 V9R2.23.0
V8R1 and V9R1 to V9R2
FRN10755 V9R2.23.0
V9R1 to OSV V9R2
ESRP (Emergency Services
FRN10308 RQ00039877 V9R2.23.1
Routing Proxy) on OSV - Step 1
ESRP (Emergency Services
FRN10587 V9R2.23.1
Routing Proxy) on OSV - Step 2
Solution Test of V9R2 ESInet
FRN10645 V9R2.23.1
Solution (ESRP + BCF)
Offer demo capabilities for single
FRN10515 V9R2.24.3
load line ready OSV
Offer demo capabilities for single
load line OSV through OSV- V9R2.24.3
FRN10516 Assistant
FRN10752 V9R2.24.6
Voice V9R2
OSV V9R2 TSA, Security
FRN10753 V9R2.24.6
Checklist and PSA
Support activating/deactivating
CFVM and changing ring V9R2.24.6
FRN10771 duration using CSTA
Make timers for Circuit Routing
configurable including setting the V9R2.24.6
FRN10791 alternative number
OSV: Enhancement to
differentiate Circuit ATC and V9R2.24.6
FRN10820 OSMO client for consultation
FRN10815 OSV - Support of IOS Push V9R2.24.8

Notification - Extended SIP
Registration Duration
FRN10756 V9R2.24.10
Include Euskara language in
supported OSV/OMS language.
V9R2.24.10
Add support for all missing langs
FRN10885 (OSV/Assistant only).
Support feature interaction for
Circuit Routing configuration
(FRN10791) and OSMO Client V9R2.24.12
Profile (FRN4863) Override
FRN10900 functionality
DISA Linux Account and Role
FRN10470 V9R3.26.0
Management
FRN10474 Cluster wide syslog management V9R3.29.0
FRN10579 V9R3.29.0
Voice V9R3
OSV V9 R3 TSA, Security
FRN10580 V9R3.29.0
Checklist and PSA
FRN10581 V9R3.29.0
V8R1 and V9R2 to V9R3
IPV6: OSV Management and
RQ00031606 Application Interfaces (Phase V9R3.29.0
FRN10653 Two of Four)
IPV6: OSV Management and
RQ00031606 Application Interfaces (Phase V9R3.29.0
FRN10654 Three of Four)
FRN10582 V9R3.29.2
V9R2 to OSV V9R3
Support MS Skype for Business
FRN10564 RQ00040317 V9R3.30.0
Media Bypass (OSV)
FRN10583 V9R3.30.0
JITC Certification Test of the CP
Phone 200, 400 & 600 V1.3 V9R3.30.0
FRN10651 models with MLPP
VMware vSphere esxi V6.5
FRN10783 V9R3.30.0
Support
FRv2: Integration of Gemma +
new DB with OSV, MS on one
FRN10691 Server V9R3.30.0
FRv2: Gemma: Generate Call
Detail Records (CDRs) according
FRN10693 to NENA V9R3.30.0
FRv2: Gemma: Generate Call
Detail Records (CDRs) according
FRN10694 to California IFB V9R3.30.0
FRv2: OSV: Support Call
Features according to NENA and
California IFB (FS1) with Phone
FRN10695 and IWS V9R3.30.0
FRv2: OSV: Support Hook Flash
FRN10696 for CAMA Trunks V9R3.30.0
FRv2: OSV: Support Conference
FRN10697 Features according to NENA V9R3.30.0
FRv2: Solution and Component
FRN10699 Documentation (OSV, Gemma) V9R3.30.0
FRv2: Solution and Component
HiSAT, Blackduck scan, IFMDB
FRN10700 (OSV, Gemma) V9R3.30.0

FRv2: OSV provide Call Detail
Records (CDRs) data towards
FRN10701 Gemma (via CSTA) V9R3.30.0
FRv2: Gemma: Database
FRN10703 replacement V9R3.30.0
FRv2: Gemma: Screen Layout
according to NENA and
FRN10704 California IFB V9R3.30.0
FRv2: Gemma: Integration of
FRN10705 Soft Client V9R3.30.0
FRv2: Gemma: Support of
FRN10706 Muliline handling V9R3.30.0
FRv2: Gemma: Integration of IRR
FRN10707 feature V9R3.30.0
FRv2: Gemma: Integration of
FRN10709 TDD/TTY feature V9R3.30.0
FRv2: Soft Client: Gemma
FRN10710
integration V9R3.30.0
FRv2: Soft Client: Support of
distiguish ringing (upto 12
FRN10712 different rings) V9R3.30.0
FRv2: Test Redundancy test
(Geo separated and local) active
FRN10714 - active V9R3.30.0
FRv2: Test Performance test
FRN10715 FRv2 V9R3.30.0
FRv2: Test CDR generation and
handover to CDR collector eCAts
FRN10716 according to NENA V9R3.30.0
FRv2: Test ALI database access
FRv2: Test Call Features
California IFB (FS1) with Phone
FRN10720 and IWS V9R3.30.0
FRv2: Test with Audiocodes
FRN10721 Gateway (CAMA-SIP) V9R3.30.0
FRv2: Test Security verification
FRv2: OSV: ALI query to de-
FRN10724 reference ANI/pANI V9R3.30.0
FRv2: OSV: Insert ALI location
response in to CSTA event
towards Gemma based on
FRN10726 EndPoint Configuration V9R3.30.0
FRv2: OSV: support ALI re-Bid
requirements and configuration
According to NENA and
FRv2: OSV: Interworking of ALI
re-Bid requests between OSV
FRN10728 and Gemma V9R3.30.0
FRv2: OSV: 911 Connection
Continuity Check and Call
FRN10796 Recovery Mechanism V9R3.30.0
FRv2: OSV: Distinctive Audible
FRN10806 Ringing per PSAP device V9R3.30.0
FRv2: Add the MUTE
functionality to the keypad (St
FRN11015 Francis) V9R3.30.0

OSV Enhancement to support
FRN11094 Circuit Parallel Ringing on hunted V9R3.33.4
calls for Circuit ATC
FRN10838 RQ00040724 Auto Answer only on ACD Calls V9R3.33.5
Enhance CSTA to send Group
Pickup notification status to
FRN10978 OSMO/Circuit ATC and support V9R3.34.2
CSTA Group Pickup Call service
requests
FRN10825 QoS data in CDRs V9R3.34.4
Extend OSV route selection
RQ00041610 beyond using just 3 available V9R3.34.15
routes
Increase Emergency Calling
RQ00041724 Table Department Quantity to V9R4.43.0
2000
Change of SIP implementation
FRN11090
for Call Pickup Group 1 V9R4.43.0
1DECT phone doesn’t receive pickup notification after re-added to CPU group. In order to fix this the DECT phone
apart from the addition to CPU group on OSV side, needs also to unassign and then assign again the CPU feature
on each DECT user. Resolved Reported Problems / Symptoms
GSI Flow
Description Fix Version/s
Ticket
NA16577334 SIPSM Pstack - setCisDisplayInfoFromPAI OSV V9R4.48.1
NA16580335 CSTA SystemStatus has entered overload, causing lost heartbeat OSV V9R4.48.0
connection with OSCC application
NA16566226 Periodic Audit Stops Monitoring The Endpoints After Few Weeks or OSV V9R4.48.0
node restarts
PRB000047990 UCaaS: cascaded MLHG Circuit Agent Status isn’t correct and can’t be OSV V9R4.48.0
changed
NA16553886 OSV responds with "503 Service Unavailable - SIPSM in overload, new OSV V9R4.48.0
call rejected." since updated to V9R4.43.3
PRB000047657 Circuit user outgoing external calls do not appear in call history OSV V9R4.48.0
NA16530347 Error when loading information about certain subscribers in CMP OSV V9R4.48.0
NA16485304 multiple ONS reoffer after 486 Busy here OSV V9R4.48.0
PRB000047990 UCaaS: cascaded MLHG Circuit Agent Status isn’t correct and can’t be OSV V9R4.45.6
changed
PRB000047657 Circuit user outgoing external calls do not appear in call history OSV V9R4.45.6
NA16530347 Error when loading information about certain subscribers in CMP OSV V9R4.45.6
NA16485841 Hung CSTA context causes OSCC Agents do not receive any calls OSV V9R4.45.6
anymore
NA16537047 HG Simultaneous parallel Alerting Model is not working for all the OSV V9R4.45.6
members
NA16486742 : OSV V9R4: After The Upgrade : If An User Dials 911, Emergency OSV V9R4.45.6
Operator Unable To Callback The Caller through Node2
NA16536643 Alarms are reported for process PSR when machine is rebooting OSV V9R4.45.5
NA16521536 Wrong expiration date for certificate, when using a self-signed for 30 OSV V9R4.45.5
years
PRB000047583 Call is transferred to Voicemail but Circuit client keeps ringing, since OSV V9R4.45.5
new Destination in Diverted event is the ONS, instead of VM number
NA16525082 Call Pickup notification to ATC subscriber doesn't contain the Display OSV V9R4.45.5
name for pickup group subs
NA16544025 Transfered user missing in callog OSV V9R4.45.5

GSI Flow
Ticket
NA16443229 No display of HG when 1000 members are part of it OSV V9R4.45.5
NA16487599 RM reports duplicate o-line in SDP in a Forward scenario OSV V9R4.45.5
NA16439119 OSV is unable to find Authentication data of endpoint if SSP challenges OSV V9R4.45.5
Re-Invite for a call with a restricted Caller ID
NA16391205 Inbound calls to Genesys fails due to user-to-user extra OSV V9R4.45.5
character(space)
NA16478439 Registration doesn’t expire, if phone is unplugged and the phone is OSV V9R4.45.4
registered via SBC
NA16335737 During SST, OSV sends dummy SDP with two m-lines for SRTP, if the OSV V9R4.45.4
SRTP Media Mode of the subscriber is configured with SRTP only
NA16451397 MLHG Loss of communication alarms for OSCC controlled MLHGs OSV V9R4.45.4
when changes are done in "Authentication" tab via the OSV Assistant
NA16523702 OSV V9R3.34.21 Node1 “submgtSchedule” rolling pstacks OSV V9R4.45.4
NA16475842 CLONE - OSV Soap import for CLINPOOL does not work correct OSV V9R4.45.4
NA16389474 Filesystem backup: /log is flooded with hiq_backup.sh_xxxx files OSV V9R4.45.4
NA16511890 OSV generates invalid SIP UPDATE Messages for Secondary OSV V9R4.45.3
Line/DSS Keys (400 Bad Request)
NA16417117 Wrong SIP Header in case of blind transfer OSV V9R4.45.3
NA16527964 only the first 1000 LIN_POOLs are in the export file when taking SOAP- OSV V9R4.45.3
EXPORT
NA16526268 OSV does not send a re-INVITE after receiving 491 Request Pending OSV V9R4.45.3
NA16318771 During SST scenario, OSV releases the call, since collision is detected OSV V9R4.45.3
by sipsm
NA16301441 E1 QSIG on incoming SETUP Calling Name PAI is not shown. OSV V9R4.45.3
NA16474304 Wrong display showing periodic audit enabled when reboot is OSV V9R4.45.1
performed
PRB000047198 System is overwhelmed with solxxxxx.log files OSV V9R4.45.1
NA16478137 ASC recorder only records silence after call was transferred to ASC OSV V9R4.45.1
monitored agent.
NA16389430 Alarm is falsely reported concerning cdr account OSV V9R4.45.0
NA16232330 CDR file transfer to an SFTP Server (SPUSH) stops working after some OSV V9R4.45.0
hours since the OSV was updated to V9 R3.34.5
NA16503872 Enhanced Subscruber Rerouting fails, since DID pool number is not OSV V9R4.43.3
used
NA16335737 During SST, OSV sends dummy SDP with two m-lines for SRTP, if the OSV V9R4.43.3
SRTP Media Mode of the subscriber is configured with SRTP only
NA16389474 Filesystem backup: /log is flooded with hiq_backup.sh_xxxx files OSV V9R4.43.3
NA16417117 Wrong SIP Header in case of blind transfer OSV V9R4.43.3
NA16380496 IRM reports duplicate o-line despite the fact that the SDP answer is
OSV V9R4.43.1
identical to the previous SDP answer
PRB000047198 System is overwhelmed with solxxxxx.log files OSV V9R4.43.1
NA16422093 Ghost call if one of the devices of a DN with multiple contacts is
OSV V9R4.43.1
forwarded
NA16462109 UCaaS T&I: Periodic Endpoint Audit has stopped and cannot be
OSV V9R4.43.1
disabled
NA16277043 Hanging call in UC Call Control Window for MLHG agent in
OSV V9R4.43.1
simultaneous ringing.
NA16402920 Numbering Plan from HD Remote DN is used instead of HD "Home
OSV V9R4.43.0
Base" for call routing during an active hot desking session
NA16397738 Callleg towards ASC stays alive if a call to a DN with voice recording is
OSV V9R4.43.0
released quickly after it was initiated

GSI Flow
Ticket
NA16462109 UCaaS T&I: Periodic Endpoint Audit has stopped and cannot be
OSV V9R4.43.0
disabled
NA16357238 No external incoming or outgoing calls are possible after VM move OSV V9R4.43.0
NA16310468 Upgrade from OSV V8R1.47.2 to V9R3.34.12 via toolkit fails on Node2 OSV V9R4.43.0
NA16374772 CLONE - ModifyEndpoint description in mp2.dat and "OpenScape
OSV V9R4.42.0
Voice V9 SOAP Interface" Guide is wrong
NA16422609 OSV doesn’t remove ICE attributes, although ICE Support is disabled
OSV V9R4.42.0
on subscriber side
NA16400403 No MOH when agent puts the call on hold, if the call is distributed via
OSV V9R4.42.0
MLHG (parallel alerting model) and the agent is silence monitored
NA16400350 RapidStat Error OSV node2: "DNS different than static singaling IP..." OSV V9R4.42.0
NA16379573 SnapshotDevice Request Timeout should be configurable using new
OSV V9R4.42.0
RTP parameter(hiQ/CSTA/NG911RebidTimeout)
NA16376621 TIAS faulty set to 0 when max calls are limited and TIAS flag is set on
OSV V9R4.42.0
CAC
NA16334296 On Simplex RtpDumpLog is full with checkDbAudit.jar messages OSV V9R4.42.0
NA16331632 Registered Endpoint Contact has expired but it is not deleted from
OSV V9R4.42.0
Contacts (entry remains in EPT_CONTACT_DEVICE_T)
NA16290331 IRM reports duplicate o-line in SDP which is generated by the OSV
OSV V9R4.42.0
itself
PRB000047038 CSTA error code InvalidConnectionID on call transfer OSV V9R4.42.0
IRM reports duplicate o-line despite the fact that the SDP answer is
NA16380496 OSV V9R4.41.4
identical to the previous SDP answer
Ghost call if one of the devices of a DN with multiple contacts is
NA16422093 OSV V9R4.41.4
forwarded
Hanging call in UC Call Control Window for MLHG agent in
NA16277043 OSV V9R4.41.4
simultaneous ringing.
UCaaS T&I: Periodic Endpoint Audit has stopped and cannot be
NA16462109 OSV V9R4.41.4
disabled
NA16357238 No external incoming or outgoing calls are possible after VM move OSV V9R4.41.4
Callleg towards ASC stays alive if a call to a DN with voice recording is
NA16397738 OSV V9R4.41.2
released quickly after it was initiated
Numbering Plan from HD Remote DN is used instead of HD "Home
NA16402920 OSV V9R4.41.2
Base" for call routing during an active hot desking session
No MOH when agent puts the call on hold, if the call is distributed via
NA16400403 OSV V9R4.41.2
MLHG (parallel alerting model) and the agent is silence monitored
IRM reports duplicate o-line in SDP which is generated by the OSV
NA16290331 OSV V9R4.41.2
itself
SnapshotDevice Request Timeout should be configurable using new
NA16379573 OSV V9R4.41.1
RTP parameter(hiQ/CSTA/NG911RebidTimeout)
NA16334296 On Simplex RtpDumpLog is full with checkDbAudit.jar messages OSV V9R4.41.1
Registered Endpoint Contact has expired but it is not deleted from
NA16331632 OSV V9R4.41.1
Contacts (entry remains in EPT_CONTACT_DEVICE_T)
OSV doesn’t remove ICE attributes, although ICE Support is disabled
NA16422609 OSV V9R4.41.1
on subscriber side
CLONE - ModifyEndpoint description in mp2.dat and "OpenScape
NA16374772 OSV V9R4.41.1
TIAS faulty set to 0 when max calls are limited and TIAS flag is set on
NA16376621 OSV V9R4.41.1
CAC
PRB000047038 CSTA error code InvalidConnectionID on call transfer OSV V9R4.41.1
NA16400350 RapidStat Error OSV node2: "DNS different than static singaling IP..." OSV V9R4.41.1
NA15574256 OSB Endpoint remains in inaccessible state after inbound call OSV V9R4.41.0
NA15970624 processes fail health check during FS backup due to high disk I/O OSV V9R4.41.0

GSI Flow
Ticket
NA16245367 Several ovl errors regarding sipsm lost messages OSV V9R4.41.0
NA16258237 SecMgr issue with code delivered in OSV-11172 and OSV-10886 OSV V9R4.41.0
OSV doesn’t respond to the CallRerouting invoke with a return result
NA16266693 OSV V9R4.41.0
when path replacement is enabled on OSV
JoinCall being rejected with CSTAErrorCode "resourceBusy" due to a
NA16359155 OSV V9R4.41.0
preceding call context not being fully released
sipsm pstack in "cSmNetworkInterfaces::getFQDN" due to a bad URI
NA16369043 OSV V9R4.41.0
for the SIP endpoint/E911 Manager received by ldp
Redsky in Simplex Mode: ldp provides information from non existing
NA16369088 OSV V9R4.41.0
2nd RedSky E911 Manager SIP Endpoint to sipsm
NA16371334 Database FileSpec is greater than the valid one for that configuration OSV V9R4.41.0
NA16033168 Inaccesibility of endpoints in case of unavailable EP name OSV V9R4.40.0
NA16258237 CMP sporadically does not show PAC or DC entries OSV V9R4.40.0
NA16280282 Not possible to modify an Emergency Calling subnet OSV V9R4.40.0
OSV does not update SIP call leg with new SDES crypto key received
NA16311812 OSV V9R4.40.0
from MS
NA16339169 Live Upgrade to V9R3.34.19 fails as node2 processes cannot startup OSV V9R4.40.0
NA16340874 ASC recorder only records silence after call was transferred. OSV V9R4.40.0
NA16348301 OSV Upgrade from V7R1.51.5 to V9R3.34.16 fails OSV V9R4.40.0
NA16358450 Upgrade V7 -> V9 fails OSV V9R4.40.0
PRB000047043 UCaaS: MLHG Call shows wrong number format in call log OSV V9R4.40.0
CLONE - ModifyEndpoint description in mp2.dat and "OpenScape
NA16374772 OSV V9R4.39.6
sipsm pstack in "cSmNetworkInterfaces::getFQDN" due to a bad URI
NA16369043 OSV V9R4.39.6
for the SIP endpoint/E911 Manager received by ldp
Redsky in Simplex Mode: ldp provides information from non existing
NA16369088 OSV V9R4.39.6
2nd RedSky E911 Manager SIP Endpoint to sipsm
NA16245367 Several ovl errors regarding sipsm lost messages OSV V9R4.39.6
NA15574256 OSB Endpoint remains in inaccessible state after inbound call OSV V9R4.39.6
JoinCall being rejected with CSTAErrorCode "resourceBusy" due to a
NA16359155 OSV V9R4.39.5
preceding call context not being fully released
NA16371334 Database FileSpec is greater than the valid one for that configuration OSV V9R4.39.4
NA16340874 ASC recorder only records silence after call was transferred. OSV V9R4.39.4
NA16358450 Upgrade V7 -> V9 fails OSV V9R4.39.4
OSV doesn’t respond to the CallRerouting invoke with a return result
NA16266693 OSV V9R4.39.4
when path replacement is enabled on OSV
NA16280282 Not possible to modify an Emergency Calling subnet OSV V9R4.39.4
PRB000047043 UCaaS: MLHG Call shows wrong number format in call log OSV V9R4.39.3
NA16348301 OSV Upgrade from V7R1.51.5 to V9R3.34.16 fails OSV V9R4.39.3
OSV does not update SIP call leg with new SDES crypto key received
NA16311812 OSV V9R4.39.3
from MS
NA00000000 No signaling of an incoming MLHG call to a Pickup Group member OSV V9R4.39.2
NA16033168 Inaccesibility of endpoints in case of unavailable EP name OSV V9R4.39.1
NA16307355 Sporadically exception and error "Subscriber does not exist on OSV OSV V9R4.39.1
NA16339169 Live Upgrade to V9R3.34.19 fails as node2 processes cannot startup OSV V9R4.39.1

GSI Flow
Ticket
Wrong destination numbering plan is used when calling NDAL in case
NA16323453 OSV V9R4.39.0
of basic subscriber rerouting (BSR)
OSV doesn't correctly tear down B-side if A side hangs up while a Re-
NA00000000 OSV V9R4.39.0
Invite transaction is pending
NA16313115 OSV does not send SIPQ Alert and Connect to A side OSV V9R4.39.0
NA16287730 OSV marks an incoming external call as conference call OSV V9R4.39.0
Conference participant is disconnected from large conference when
NA16267137 OSV V9R4.39.0
large conference initiator is silence monitored
OSV PSAP: RapidStat errors: "DNS different than static signaling IP"
NA16266832 OSV V9R4.39.0
and "Communication maybe broken, no response received in 10 sec"
NA16272842 OSV/GEMMA - Automatic ANI/ALI Did Not Work OSV V9R4.39.0
NA16256537 External Calls towards OSEE fails after SSP media renegotiation OSV V9R4.39.0
NA16255527 ldp stopped processing ANI/ALI requests OSV V9R4.39.0
Feature Alternative Calling Identity (ACID) is not working after OSV
NA16232230 OSV V9R4.39.0
upgrade from V7 to V9
CDR file transfer to an SFTP Server (SPUSH) stops working after some
NA16232330 OSV V9R4.39.0
hours since the OSV was updated to V9 R3.34.5
OSV drops some call legs when an error occurs during path
NA16223563 OSV V9R4.39.0
replacement.
NA16207999 Access denied for user srx by PAM account configuration OSV V9R4.39.0
OSV doesn’t increment the SDP version by one, although
NA16206791 OSV V9R4.39.0
Srx/Sip/sdpSessionMaintainer is set to RtpTrue
Due to uncommitted transaction /home runs out of disk space see also
NA16199000 OSV V9R4.39.0
OSV-7257
NA15961813 OSV V9 R2.24.13 sporadically both OSV nodes stopped sending CDRs OSV V9R4.39.0
NA16164750 DNMP11 extremely high heap size when using FQDN for Media Server OSV V9R4.39.0
NA16266922 180 Ringing not delivered OSV V9R4.39.0
NA16160321 NMT Import err --> import errors regarding Destination "d_IntFallback": OSV V9R4.39.0

6 Hardware and software compatibility
6.1 Hardware revisions

Server model Revision
IBM xSeries 346 Not Supported
IBM System x3650T Not Supported
IBM System x3550 M2 Not Supported
• Not Supported for new installations
Fujitsu RX-200 S6
• Supported only for Upgrades from existing installations
• Supported for new installations
Fujitsu RX-200 S7 • Supported for Upgrades from existing installations
• Supported for Migrations from any supported hardware platform
• Not Supported for new installations
IBM System x3550 M3
• Supported only for Upgrades from existing installations
IBM System x3550 M4 • Supported for Upgrades from existing installations
Lenovo x3550 M5 • Supported for Upgrades from existing installations
Lenovo SR530 • Supported for Upgrades from existing installations
For details on the each system’s configuration, please consult the OpenScape Voice V9 Installation &
Upgrade Guide.
6.2 Firmware releases

The following table specifies the minimal firmware versions required depending on the server model. Servers
may come from the factory with newer firmware versions; such servers don’t need to be downgraded, unless
otherwise noted.
Server model Unit Version Alt. Version Build Id

Main BIOS V6.1.10.3031 none not available
Fujitsu RX200 S6
iRMC 5.72A none not available
Main BIOS R2.23.0 none not available
Fujitsu RX200 S7
iRMC 6.55A none not available
UEFI (BIOS) 1.20 none not available
IBM System x3550 M3
IMM 1.45 none not available
UEFI (BIOS) 1.71 none not available
IBM System x3550 M4
IMM2 4.31 none not available
UEFI 1.11 none not available
Lenovo x3550 M5
UEFI 1.11 none not available
Lenovo SR530
The official firmware version is listed in the Version column. However, depending on the method used to get
the firmware in a running system (BIOS, RSA, ASU), the same firmware may return a different number, listed
in the Alternative Version column. The Build Id can also be used for additional confirmation.

6.3 Loadware releases
Not applicable for this product.
6.4 Software releases

This release note contains information pertinent to the OpenScape Voice Server software only. Additional
software products are required to install and operate the OpenScape Voice Server. These products are listed
in the following table, which also includes the respective versions required to use with the current OpenScape
Voice Server software and the location of their respective Release Notes in G-DMS.
Product Software Version Release Date¹ G-DMS Note

OpenScape Voice Server V9 R4.48.2 2019-12-20 See Section 1.3.3
OpenScape Voice Server Image 2 V9 R4.48.0 2019-12-20 See Section 1.3.1
OpenScape Voice USB Service System V2 R1.15.0 2019-08-07 INF-19-000269
OpenScape Voice Server vApps 3 V9 R3.30.0 2018-05-03 INF-18-000221
OpenScape Voice Installation Wizard V9 R4.3.0 (9.4-3.0) 2019-04-16 INF-19-000181
OpenScape Voice Basic Traffic Tool V8 R0.10.0 (1.10.12) 07/09/2014 INF-14-000413
OpenScape CLM (windows version) V1 R13.0.0 11/11/2013 INF-14-000071
OpenScape Applications V9 Latest s/w available in SWS - -
OpenScape Voice Trace Manager V8R0.4.3 07/14/2016 INF-16-000322
OpenScape Voice Server Toolkit V1.09-66 2019-08-07 INF-19-000268
OpenScape Voice Web CDC Tool V1R1.34.0 03/21/2018 INF-18-000176
OpenScape Voice Number Modification
V7 R1.4.0 07/09/2014 INF-14-000398
Tool
Notes:
¹ Items recently released are marked with a star ().
2 The OpenScape Voice Server Images are comprised of OpenScape Voice V9 R4.48.0 and OpenScape
Applications V9R4.27.0; however, administrators should update their systems to the latest HF level
available in SWS.
3 When performing an upgrade on an Integrated Simplex, the source system must have a smaller or equal
OpenScape Applications version compared to the target system. In case you want to upgrade to a higher
version of OSV and the OpenScape Applications version is lower than the one you have, perform steps
described in Chapter 7 of OpenScape Voice V9, Service Manual: Installation and Upgrades, Installation
Guide
4At least ESXi 5.5 and the vSphere Web Client 5.5 are required because the OSV vApp is built with VM
hardware version 10. Review the VMware vSphere 5.5 Documentation Center before proceeding;
• The vSphere Web Client has specific browser requirements. Review the “vSphere Web Client
Software Requirements”
• The Client Integration Plug-in provides access to a virtual machine's console in the vSphere Web
Client, and provides access to other vSphere infrastructure features. Refer the “Install the Client
Integration Plug-In in the vSphere Web Client” section
See Sections 2 and 4 for an important workarounds related to image installation, upgrades or migrations.
6.5 Operating systems (including security alerts)

Operating System Name Operating System Version
Server
SLES 12 SP4
SUSE Linux Enterprise Server (SLES) Note: the operating system for the OpenScape
Voice Server is included on the OSV image

6.6 Compliant products (compatibility matrix)
Hardware and software products that have been tested together with the OpenScape Voice Server, including
third-party products, are listed in the compatibility matrix, which also includes the respective versions required
to use with the current OpenScape Voice Server software.
The up-to-date Large Scale Common Compatibility Matrix can be found in the following link:
https://nuxeo.unify.com/nuxeo/site/proxy/nxdoc/view/raw/c9a42b9d-82ac-48a3-86bf-87e521f00374

7 Service information
7.1 Management information base

Product forwards SNMP traps according to a MIB:
7.2 License management

The OpenScape Voice Server is certified for the following:
CLS: CSC: Other Licensing: If you are using others, please describe below:
7.2.1 License activation

For the detailed description of licensing concepts, please refer to the latest customer documentation.
A license file must be purchased by the customer through the sales channels. This XML file is specific for the
type of system and requires the MAC address of the node’s administration interface (bond0). The MAC
address can be retrieved by logging on as root user and using the ifconfig command. In duplex configurations,
licenses are required for both nodes.
The type of system (name and version) is identified by parameters HiQ/Main/ProductType and
HiQ/Main/ProductVersion which are pre-configured at installation time based upon the node.cfg file. Licenses
will not be activated if those parameters are not set correctly.
The CLM tool can be used in a computer connected to OpenScape Voice to install the license files, if the
computer was previously defined as a License Server in the node.cfg file during the OpenScape Voice Server
installation. If CLM is not available, an alternative method is to copy the XML file into directory
/opt/unisphere/srx3000/cla/import in both nodes.
After the license files are installed in both nodes, the license will be activated in 5 minutes if installed in a
running system that had no previous license. The current licensing state can be determined using the CLI
options 6>1>1>10>1, or from the main view of the communication processor in Assistant.
Note: If an invalid license file is installed inadvertently, it's not necessary to re-install the server. The system
can accept a new valid license file.
7.2.2 Open source software

The product contains Open Source Software developed by third parties and licensed under an Open Source
Software License. Such software files are protected by copyright. Your rights to use the Open Source
Software beyond the OpenScape Voice application are governed by the relevant Open Source Software
license conditions.
Your compliance with such license conditions will entitle you to use the Open Source Software as foreseen in
the relevant license. In the event of conflicts between Unify Software and Solutions GmbH & Co.KG license
conditions and the Open Source Software license conditions, the Open Source Software conditions shall
prevail with respect to the Open Source Software portions of the software.
Open Source Software is licensed free of royalties, i.e. no fees are charged for exercising the licensed rights,
whereas fees may be charged for reimbursement of costs incurred by Unify Software and Solutions GmbH &
Co.KG to provide or distribute the software. The license conditions can be found in the source code or at the
following Internet websites:
- GNU General Public License (GPL)
- GNU Lesser General Public License (LGPL)
- ASF Apache License
- OSI Common Development and Distribution License
- PERL Artistic License
- Vovida Software License
- OpenSSL License
If programs embedded with the OpenScape Voice product are licensed under the GPL or LGPL conditions
and these programs are not already delivered in source code form together with OpenScape Voice, you can
request the corresponding source code from Unify Software and Solutions GmbH & Co.KG by contacting your
sales representative.

Warranty
Unify Software and Solutions GmbH & Co.KG gives no warranty for Open Source Software programs
embedded with OpenScape Voice if such programs are used in any manner other than originally intended by
Unify Software and Solutions GmbH & Co.KG. In such cases, warranty, if any, shall be provided by the
authors of the Open Source Software as described in the license conditions referred above.
Unify Software and Solutions GmbH & Co.KG specifically disclaims any warranties for defects caused by
altering any Open Source Software program or its application or configuration within OpenScape Voice.
Technical support, if any, will only be provided for unmodified software.
You have no warranty claims against Unify Software and Solutions GmbH & Co.KG in the event that the Open
Source Software infringes the intellectual property rights of a third party.
7.3 Remote serviceability

This product is certified for: SIRA: HiSPA: RTPatch: Other
Type of Installation Transfer time via SIRA/HiSPA/SSDP Installation Time

Initial Installation Cluster Image Installation 1.15 hours (Cluster)
Delta Installation N/A N/A
Hints for remote serviciability: None
7.4 Product and diagnostics structure in G-DMS/ SWS and GSI Flow
7.4.1 Product Structure
Release Notes, MOPs and other service documentation for OpenScape Voice and related products can be
found in G-DMS. Binary files are distributed via SWS. The following table illustrates how the products are
organized in G-DMS/SWS. The first two lines of the table identify the top level structure that is common for all
OpenScape Voice products. The remaining lines identify the specific location under the top level structure for
each product and version currently being supported or recommended.
Main Category Communication Systems

Product Family OpenScape Voice
Product Product Version Product Item Number
OpenScape Voice Server OpenScape Voice Server V9 P30152-P1610-A2-29 (V9 R4.48.0 Images)
OpenScape Voice Server OpenScape Voice Server V9 P30152-P1610-A2-29 (V9 R4.48.0 Images)
OpenScape Voice Installation Wizard OpenScape Voice Installation Wizard V9 INF-19-000181
OpenScape Voice Recovery Software OpenScape Voice USB Service System INF-18-000046
OpenScape Voice Basic Traffic Tool OpenScape Voice Basic Traffic Tool P30152-P1591-A7-1 (V8 R0.10.0)
Main Category Applications
Product Family OpenScape
Product Product Version Product Item Number
OpenScape Applications OpenScape Applications V9 P30152-P1616-A1-20 (V9 R4.16.0)
7.4.2 Diagnostics Structure

Problems from customer sites must be reported by opening tickets in the GSI Flow system. The following
table illustrates how to specify the correct product information in the ticket. The first line of the table identifies
the Product Family that is common for all OpenScape Voice products. The remaining lines identify the other
parameters for each product and version currently being supported or recommended.

Product Group OpenScape Voice
Product Type Product Version Software Version
OpenScape Voice Server V9 P30152-P1610-A2-29 (V9 R4.48.0 Images)

OpenScape Voice Install Wizard V9 INF-19-000181

OpenScape Voice USB Service System V2 INF-19-000269
Product Group OpenScape Applications
Product Type Product Version Software Version
OpenScape Applications OpenScape Applications V9 P30152-P1616-A1-20 (V9 R4.16.0)
7.5 Diagnostics requirements

Before opening a new case in GSI FLOW, technicians must observe the OpenScape Voice Checklist
published in G-DMS and collect all information required by BLS and GVS for diagnosis as described in that
document.
For general information regarding the escalation process, technicians should also read the information
published in the OpenScape Voice V9R0 Service Guidelines.

8 Documentation reference
Documents Hyperlinks Remarks
E-Docu Start E-Docu See for OpenScape Voice
Technical documentation
Product E-Docu
Installation and Startup
Operating Manual
Quick Reference Guide
Administrator Manual OpenScape Voice V9, Administrator Documentation
Sales Info
C-SWS Munich Start SWS Main Page
Compatibility
See at Product on SWS
Information

9 Attachment
The following documents are published together in the following G-DMS INF-17-000339.
• OpenScapeVoice_Single_Load_Line.docx

10 Appendix A. OSV Single Load Line (SLL)
Starting with V9R2 OSV supports a single load line (SLL) concept. For more information please read the
document: OpenScapeVoice_Single_Load_Line.docx that is attached together with the following G-DMS
INF-17-000339.
Also read following important updates in the Documentation:
• OpenScape Voice V9, Service Manual , Service Documentation
A new chapter 2.1.6.2 How to Enable/Disable Demo Features in OSV has been created.
Chapter 2.1.1.1 How to Activate the OpenScape Voice license has been updated:
• OpenScape Voice V9, Administrator Documentation
New chapter 3.2.1 SLL Features has been created.

OpenScape Voice Server V9R4.48.2 Release Notes V1.0 Internal

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenScape Voice Server V9R4.48.2 Release Notes V1.0 Internal

Uploaded by

Copyright:

Available Formats

Release Notes

Release Notes Version: V1.0 Document Owner: Giachalis Aristeidis

Product Name: OpenScape Voice Server

Software Release is identified by Version: V9 R4.48.2

Production Version: V9.00.01.ALL.12 (SMR4) with up to PS48E02

Export Control Classification Data AL: 5D002C1A ECCN: 5D002ENCR

Field Trial: eeQA: Limited Availability: General Availability:

DECLARATION DATE: Date : Dec 20, 2019

DECLARED BY: Corresponding PL-Development : Ilias Konstantopoulos

DELIVERABLES: Full Release: Delta Release:

Release Note page 2 (of 39) [OpenScape Voice Server V9 R4.48.2]

1.1 History of change (Release Notes)

Version Date Changes Author

1.2 Release notes history

1.3 Product version history

SW Version Production Version Contents Release Date G-DMS Note Remarks

1.3.2 OpenScape Voice Server Images for Virtual Appliance (vApp)

SW Version Production Version Contents Release Date G-DMS Note Remarks

1.3.3 OpenScape Voice Server patchsets

Release Note page 3 (of 39) [OpenScape Voice Server V9 R4.48.2]

1.3.4 OpenScape Voice Server MOPs

Document Number Release Date Released with G-DMS Note Title

Release Note page 4 (of 39) [OpenScape Voice Server V9 R4.48.2]

2.1.2 Regarding FQDN & DNS-SRV configuration

2.1.3 Installing new servers

- Change/set the value for Srx/Service/CALEA/VideoTreatment to 0 (default is 1).

• Simplex: approximately 70 minutes (includes Applications)

• Cluster: approximately 50 minutes

• All needed software is listed in chapter 6.4.

2.2 Upgrade / Update

2.2.1 Updating the V9 patchset level

Release Note page 5 (of 39) [OpenScape Voice Server V9 R4.48.2]

2.2.1.1 Update via “Common Repository” Method

2.2.1.2 Manual Rolling Upgrade

Release Note page 6 (of 39) [OpenScape Voice Server V9 R4.48.2]

Release Note page 7 (of 39) [OpenScape Voice Server V9 R4.48.2]

Bring Node A to state 3 and back to state 4. Same for node B.

2.4 Security Considerations

2.4.2 Operating system specific

2.5 Special settings and instructions

Release Note page 8 (of 39) [OpenScape Voice Server V9 R4.48.2]

2.5.2 Parm changes

2.5.3 Transport protocol in the OpenScape Voice Solution

2.5.4 Signaling protocol changes

2.5.5 Upgrading OSV within an OSCC-E V3 environment

Release Note page 9 (of 39) [OpenScape Voice Server V9 R4.48.2]

NA16077994 SA_down to survival authority is quicker than normal (1 second)

NA16245639 Cluster outage during network flapping

NA16354310 LicenseManager pstack in V9R3.34.14 - getRemainingDays

NA16379047 V9R3.34.9 SipSM pstack in cSipDialogBase

NA16413990 V9R3.34.12 CSTASM Pstack

NA16425746 EZIP update results to RSA_ENABLED to NO

NA16486030 V9R4.39.05 license pstack in pthread_join

NA16504192 OSV cancels the Invite to the external destination

NA16552441 SNORT blacklists IPSL PC during performance test

NA16555708 DB-Error 3 when creating OSMO subscriber

NA16573597 cdm pstack, failed healthcheck after Communication link failure

Release Note page 10 (of 39) [OpenScape Voice Server V9 R4.48.2]

NA16577334 SIPSM Pstack - setCisDisplayInfoFromPAI

NA16581787 Slow but steady sipsm memory leak observed at customer

NA16014361 license restoration during toolkit upgrade failed at node1

NA16590114 sipsm pstacks - continously written pstacks

NA16594485 rolling acarscan pstack in node2 followed by NRF

NA16600873 OSV is not sending ACK for the 200ok received.