Polycom ReadiVoice Release Note
  1. Manuals
  2. Brands
  3. Polycom Manuals
  4. Software
  5. ReadiVoice
  6. Release note
Polycom ReadiVoice Release Note

Polycom ReadiVoice Release Note

Polycom readivoice network: release note
Hide thumbs Also See for ReadiVoice:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Reference Manual, Operator's Manual
ReadiVoice
Release Notes
v2.56.0

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the ReadiVoice and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Polycom ReadiVoice

Summary of Contents for Polycom ReadiVoice

  • Page 1 ReadiVoice Release Notes v2.56.0...
  • Page 2 The information in this document is the sole intellectual property of Polycom, Inc., and may not be copied, transcribed, distributed, or used for any other purpose without prior written permission from Polycom, Inc.

  • Page 3: Table Of Contents

    Introduction... 5 What’s New in ReadiVoice v2.56.0... 5 Windows Operator Production Availability ... 5 Multiple Subscriber Access Numbers ... 6 Other Enhancements and Changes in ReadiVoice v2.56.0... 7 Moderator API Changes... 7 CAPI Changes... 8 Configuration and Implementation Changes... 9 SNMP changes...
  • Page 4 Routing Interface Changes... 21 ReadiVoice v2.53.0... 22 Larger System Configurations... 22 Intelligent Network Call Routing Interfaces ... 23 Other Enhancements and Changes in ReadiVoice v2.53.0... 24 Automatic Gain Control ... 24 Upgrading to ReadiVoice v2.56.0 ... 24 10 Software Versions ... 25 11 Known Limitations...

  • Page 5: Introduction

    Multiple Subscriber Access Numbers PSPI Call ACM Applications Accessing CDR Data Note: ReadiVoice v2.56.0 is only available for ReadiVoice PSTN systems. ReadiVoice IP on InnoVox 4000 media servers is supported with ReadiVoice v2.53.x. This section describes each new feature in detail. Section 3 describes the enhancements to existing features.

  • Page 6: Multiple Subscriber Access Numbers

    ReadiVoice systems simultaneously. In addition, since it’s a native Windows program, the Windows Operator offers enhanced performance. Note: ReadiVoice v2.56.0 is expected to be the final release in which the Java Operator is supported.Please contact your Polycom account manager if you have questions concering the phase out of the Java Operator.

  • Page 7: Other Enhancements And Changes In Readivoice V2.56.0

    3 Other Enhancements and Changes in ReadiVoice v2.56.0 3.1 Moderator API Changes Note: ReadiVoice v2.56.0 is a transition release that supports the Conferencing API (CAPI), the Java Moderator API (MAPI), the XML-API, and Application Control Modules (ACM). ReadiVoice v2.60.0 will support only CAPI.

  • Page 8: Capi Changes

    CastorMessageSender SET_CONF_USER_DATA CONF_INFO CAPI Changes to address ACM Billing Code requirements. ReadiVoice v2.56.0 Release Notes Polycom, Inc. Description This fix alters ACM MAPI clients that were receiving CURRENT_CONF_INFO events: It adds a new XBOOL type and a new CCI enum value to MAPI. If an ACM application was receiving...

  • Page 9: Configuration And Implementation Changes

    = 120 Conferencing API—Check Script Change In ReadiVoice v2.55.0, CAPI introduced a new Application user type. To further support this user type, ECR 1-5998401 in ReadiVoice v2.56.0 implements a change to the output of the ReadiVoice “check” script so that the script more accurately reflects the Application sessions and Moderator sessions currently active on the system.

  • Page 10: Snmp Changes

    DESCRIPTION "Specifies a number of applications logged into the system" ::= { sysOperatorInfo 6 } The ReadiVoice SNMP MIB can be found in file: /web/snmp/srconf/mgr/conferencenow.mib 3.5 Database Changes See section 2.2 Multiple Subscriber Access Numbers (1-1XERY/1-6028520) 3.6 PSPI Changes AddSubAndANString See section 2.2 Multiple Subscriber Access Numbers (1-1XERY/1-6028520)

  • Page 11: Readivoice V2.55.0

    Notes: We recommend that you first certify and implement your current MAPI or XML-API clients or ACM applications. Then you can migrate them to CAPI and roll them out in a subsequent release. The ReadiVoice v2.55.0 CAPI user documentation includes detailed CAPI migration and implementation documentation, as well as transition examples.

  • Page 12: Multi-Language Prompts

    In ReadiVoice v2.55.x, almost every unique call for a .wav file calls a unique .wav file. To support this redesign, ReadiVoice engineering created a new prompt naming scheme and replicated those .wav files that are used in multiple call flows into multiple .wav files.

  • Page 13: Blast Dial Enhancement

    A list of the final output files that were not able to be created due the first two conditions If your ReadiVoice systems use custom prompt sets, you may have to edit, or possibly re-record, a subset of your custom .wav files before upgrading your systems. The ReadiVoice Custom Prompt Conversion Guide contains the information you need to prepare your custom prompt sets for the upgrade.
  • Page 14 Call Flow ReadiVoice v2.56.0 Release Notes 3725-70002-009G2 Polycom, Inc. Page 14 Confidential and Proprietary...

  • Page 15: External Id B Field

    Feature Description ReadiVoice v2.55.0 implements a new External ID B field. This field has been added to the Subscriber database and has many of the properties of the existing External ID field (i.e., it has a maximum length of 30 characters and it is written into CDRs for the subscriber’s conferences).

  • Page 16: Moderator Api Changes

    5.2 Moderator API Changes Note: ReadiVoice v2.55.0 and v2.56.0 are transition releases that supported the Conferencing API (CAPI), the Java Moderator API (MAPI), the XML-API, and Application Control Modules (ACM). ReadiVoice v2.60.0 will support only CAPI. MAPI EVENT SET_CONF_SECURITY_NUM.java ReadiVoice v2.56.0 Release Notes Polycom, Inc.
  • Page 17 MAPI EVENT DIAL_FAIL_REASON.java BIG_CONF_INFO.java CONFERENCE_END.java CONF_STARTED.java Several MAPI events have been modified to provide more consistent data type representation of ReadiVoice internal and database types. MAPI EVENT ACM_CDR.java ACM_GET_DTMF.java ACM_HEARTBEAT.java ACM_HEARTBEAT_ACK.java ACM_OPTION.java BIG_CONF_INFO.java CALL_FAILED.java CONFERENCE_END.java 3725-70002-009G2 Confidential and Proprietary Description...

  • Page 18: Configuration And Implementation Changes

    External ID B Field in CDR Database (ECR 1-5345819) The subscriber_info table has a new ExternalIdB field. A new index, called SI_ExternalIdB, has also been added. The details have been described in section 3.3.2. ReadiVoice v2.56.0 Release Notes Polycom, Inc. Member variable...

  • Page 19: Cdr Changes

    Conferencing API’s New ‘Application’ User Type (ECR 1-5487601) We have added a new user type into ReadiVoice, as part of CAPI development. The new user type is called Application Type. The description of this new user type can be found in CAPI development documentation.

  • Page 20: Pspi Changes

    The InnoVox chassis now supports monitoring of power supplies and fans from the redundant VMS cards in the chassis. Software was added to log failures and notify ReadiVoice whenever a monitored component has failed, and to identify the specific component that has failed down to the power supply or fan number.

  • Page 21: Readivoice V2.53.1

    6 ReadiVoice v2.53.1 ReadiVoice v2.53.1 was a maintenance release that addressed defects identified since the release of ReadiVoice v2.53.0. 6.1 Database Changes The Informix 9.3 installation package 0009 has been modified to pick up new settings in the onconfig.* files.

  • Page 22: Readivoice V2.53.0

    SS7 (AT&), SS7 DMS 500, and SS7 DMS 100 were recompiled against the new version (v1.3.1.7) of the D7 libraries 7 ReadiVoice v2.53.0 ReadiVoice v2.53.0 is a feature release. The following table identifies its new features and indicates on which InnoVox media servers the features are available. Feature/Enhancement...

  • Page 23: Intelligent Network Call Routing Interfaces

    Assigning Translation Numbers Because ReadiVoice v2.56.0 supports a larger number of ports and a larger number of conferences, you should reassess the number of translation numbers you have available to your ReadiVoice systems. To do so, use the following formula: # of translation numbers = max # of conferences * # of access classes Where the number of translation numbers does not exceed the number of ports.

  • Page 24: Other Enhancements And Changes In Readivoice V2.53.0

    The software upgrade from ReadiVoice v2.5x.x to ReadiVoice v2.56.0 is a simple update procedure; however, Polycom Global Services may also use the roll out of ReadiVoice v2.56.0 as an opportunity to perform InnoVox 4000 card upgrades, which are required to take full advantage of new ReadiVoice v2.55.0 features.

  • Page 25: Software Versions

    10 Software Versions The table below shows the software versions of the bridge binaries, server software, and ReadiVoice packages included in this release. For each, it also indicates in which ReadiVoice release the current version was introduced. Software Module/Component Platform...

  • Page 26: Known Limitations

    Improperly configured sockcap, or a sockcap that cannot communicate with the configured cards for an extended length of time may core. This does not effect conferencing, only logging 1-6172109 During security scan performed with Nessus tool ReadiVoice processes core. 1-6299765 1-5556809 Windows Operator;...

  • Page 27: Innovox V4.21.0

    There is an issue with bridges containing 3210 PMODs that results in talker updates not being accurately displayed on the GUIs for large conferences (over 15 participants). 11.3 ReadiVoice v2.53.1 The following tables describe the known limitations for ReadiVoice v2.53.1. Windows Operator Issues Defect 1-5560053...
  • Page 28 Windows operator required stop/start to function properly Moderator Issues Defect When doing "add participants" via the dial out on the Polycom Web 1-5576417 Moderator, and entering a name for the dialed out participant, the dial out correctly adds the participant to the conference list and correctly shows their name shows them "In Menus".

  • Page 29: Innovox V4.13.0

    Even if subscriber reset the termination timer, both participant and subscriber will not be able to join the conference. 12 Resolved Issues 12.1 ReadiVoice v2.56.0 The following table summarizes the defects addressed since ReadiVoice v2.55.0. Defect or Description ECR # 1-6202165...
  • Page 30 The ability should exist to disable this icon. ReadiVoice v2.56.0 Release Notes Polycom, Inc. Resolution Fixed Windows operator had several fixes introduced, as the result it operates properly and no longer requires restarts.
  • Page 31 The fix was implemented by ignoring subscriber entries in the participant list which have a status of 'Disconnected' Fixed Fixed RV2560 has been validated with 6/22/05 patch set. Fixed ReadiVoice v2.56.0 Release Notes Page 31 Polycom, Inc.
  • Page 32 MAPI: Participant type is overwritten by 1-6191263 an old value. Windows Operator: auto link to edit 1-4281834 subscriber provisioning screen ReadiVoice v2.56.0 Release Notes Polycom, Inc. Resolution Fixed Fixed an incompatibility between pre 2550 MAPI clients and 2550+ MAPI backend regarding the treatment of LONG/ULONG/UINT data types.
  • Page 33 New Files: IU_AddPhoneNum.sp IU_AssignNumToSub.sp New Table : PSPIAccNumHolder All NIC interfaces are listed with their duplex status. Warning message is displayed if not all network interfaces are set to FULL DUPLEX ReadiVoice v2.56.0 Release Notes Page 33 Polycom, Inc.
  • Page 34 ReadiVoice v2.56.0 Release Notes Polycom, Inc. Resolution MAPI change: ACM_CHAN_ENTER now has a...
  • Page 35 DESCRIPTION "Specifies a number of applications logged into the system" ::= { sysOperatorInfo 6 } The ReadiVoice SNMP MIB can be found in file: /web/snmp/srconf/mgr/conferencenow.mib The "activate" configuration parameter has been set to 1. The parameter can be found in odprocrc.defaults configuration template file.
  • Page 36 1-5811201 Conference continuation is toggled to the correct value only after the first caller calls in to a MAPI started conference ReadiVoice v2.56.0 Release Notes Polycom, Inc. Resolution Added timeout = 120 to odprocrc.defaults and odproc creator script for session timeout (in seconds).
  • Page 37 If the operator does not have a voice path the application will prompt the operator to establish one. modified modules: opinterface, operator GUI client modified modules: operator GUI client modified modules: operator GUI client Fixed ReadiVoice v2.56.0 Release Notes Page 37 Polycom, Inc.
  • Page 38 1-5598008 Win Op; Hyperlink is needed from the subscriber ID column to the provisioning page ReadiVoice v2.56.0 Release Notes Polycom, Inc. Resolution Bell interval changed to one second. New configuration setting has been added to allow further tuning of the bell interval.
  • Page 39 Once this is done the only way to dial out and join a participant to conference is via the RV APIs (MAPI/CAPI). ReadiVoice v2.56.0 Release Notes Page 39 Polycom, Inc.
  • Page 40 1-3710603 Capability for using * as well as # key as the prefix for activating In-Conference ACM application ReadiVoice v2.56.0 Release Notes Polycom, Inc. Resolution The Green Alarm button is deactivated immediately after the Blue Alarm request is issued.
  • Page 41 1-4934061 /rahome/etc/vbootp.db is world readable SNMP - HP OpenView access to the 1-5136516 ReadiVoice, Informix, and Veritas MIBs Duplicate dates with snmp log files, ex. 1-5486347 log files from November 1 and Jan 11th have the same time stamp.

  • Page 42: Innovox V4.21.0

    Due to a software bug, there were instances when Callers dialing into a conference were receiving a 503 error message from ReadiVoice. This occurred because the associated resource allocation request was being ignored. The code was fixed to avoid this issue.
  • Page 43 Most NETI messages were changed to use RESRCHNDL instead of board/span/ts to make searching the logs easier and more consistent. 3725-70002-009G2 Confidential and Proprietary Resolution Fixed Fixed Fixed Fixed Fixed Fixed Fixed Fixed ReadiVoice v2.56.0 Release Notes Page 43 Polycom, Inc.
  • Page 44 Lost events from bridge: A problem existed where events from the bridge were sometimes lost causing ReadiVoice to lose sync with the bridge. Potentially this might cause zero-participant conferences. A fix was added to ensure reliable delivery of events from the bridge to ReadiVoice.

  • Page 45: Readivoice V2.53.1

    With IV4200, this information will be listed in a consistent manner to aid in troubleshooting. 12.3 ReadiVoice v2.53.1 The following table summarizes the defects addressed since ReadiVoice v2.53.0. Defect or ECR # 1-4889403 CDR Purge process is too slow, and cannot catch up once behind.
  • Page 46 The reserved pool holds one port per conference on the new version of code 1-5471301 Upgrade to D7 1.3.1.7 SS7 routing interfaces that use the SS7 network and D7 software now utilize the D7 version 1.3.1.7. 1-5546026 stop/start of opinterface leaves opinterface and wcapimsock log with wrong permissions;...
  • Page 47 BIS module modified to consistently report the IP address of the lowest slot ID. database access layer. Bridge scripts SS7 Routing modules: SS7( AT&T) SS7 DMS 500 SS7 DMS 100 tcp_routing module Bridge scripts Bridge scripts ReadiVoice v2.56.0 Release Notes Polycom, Inc.

  • Page 48: Innovox V4.13.0

    This defect leads to a communication failure with the IP card. A patch 1-5456958 was received from Motorola to address this issue. 12.5 Resolved in ReadiVoice v2.53.0 The following table summarizes the defects addressed since ReadiVoice v2.52.0. Defect or ECR # 1-5277505...

  • Page 49: Resolved In Innovox V4.12.0

    For PSTN bridges and VoIP development bridges, the PTI 4401 switch card may be used. For VoIP bridges, the PTI 4411 switch card is recommended for production usage. ReadiVoice v2.56.0 Release Notes Page 49 Resolution Operator needs to place subscriber...

  • Page 50: Resolved In Readivoice V2.52.0

    12.7 Resolved in ReadiVoice v2.52.0 The following table summarizes the defects addressed since ReadiVoice v2.50.0. Defect or ECR # 1-4888653 Operator GUI is showing incorrect line state 1-4024451 Odproc core dumps when subscription is used a second time in an environment using fixed access, private numbering, translation numbers with prefix.
  • Page 51 Moderator and CSC Call Router Opqueue manager, mplex, TCP routing interface Bridge scripts Call router Bridge scripts SNMP agent SIP User Agent Bridge scripts BIS, Bridge scripts Bridge scripts Odsoundplay sysx_creator.pl Bridge scripts, BIS ReadiVoice v2.56.0 Release Notes Polycom, Inc.
  • Page 52 1-20YK Subscriber is required to press “2” unnecessarily to change entry/exit types. 1-3791750 ReadiVoice IP: The SIP ‘Invite to Hold’ capability is not compatible with some SIP applications. ReadiVoice v2.56.0 Release Notes Polycom, Inc. Description...

  • Page 53: Resolved In Innovox V4.10.0

    Ctrlproc was modified to address this issue. The timing has been changed to eliminate this problem. Additional RPC added for channels to address missed notification. ReadiVoice v2.56.0 Release Notes Polycom, Inc.

Table of Contents