Meeting Exchange 4.1 Service Pack 2 Release Notes for the S6200/S6800 Servers

Size: px

Start display at page:

Download "Meeting Exchange 4.1 Service Pack 2 Release Notes for the S6200/S6800 Servers"

Della Parrish
5 years ago
Views:

1 Meeting Exchange 4.1 Service Pack 2 Reease Notes for the S6200/S6800 Servers The Meeting Exchange S6200/S6800 Media Servers are SIP-based voice and web conferencing soutions that extend Avaya s conferencing appications incuding reservation-ess, attended, event, mobie, and web conferencing- to support various IP network impementations. These products offer fexibe, comprehensive, conferencing soutions in a pure IP environment. The S6200 is a software media server, which when combined with the S6800 configuration aows for connection to an externa hardware media server for additiona capabiities. New Features The 4.1 Service Pack 2 reease of the Meeting Exchange Suite introduces severa new features. New Hardware Support The foowing hardware is supported in the 4.1 Service Pack 2 reease: Convedia (S6800) firmware AudioCodes TP-260 reease version F5.00A.024 EPV Leader PIN Expiration Requirements This reease introduces EPV support for Leader PIN expiration, incuding: The abiity to set an expiration period on Leader PINs. EPV sending a notification message of the pending expiration of Leader PINs. The abiity for moderators to change an expired Leader PIN. Dupicate Passcode / Reservation Group Requirements Support for reservation groups in the cbuti program. Mapping DNIS/DDI to reservation groups. More ports on the S6200 The port capacity on the S6200 has increased from 240 to 600 for a singe server. A two to four server soution supports up to 2000 ports Issue 5 February

2 Meeting Exchange 4.1 Service Pack 2 Reease Notes for the S6200/S6800 Servers Large Conference Support The previous reease supported arge conferences. However ony 125 of the participants coud be active participants (engaged in discussion). Participants beyond the 125 were abe to isten but not speak in the conference ca. This reease supports up to 2,000 active participants. SNMP Support This reease uses SNMP to process aarms for notification and restart of faied processes. Externa NFS server (S6800 ony) In the previous reease the NFS functionaity was a oca process on the same server as the appication. In this reease, NFS is unbunded from the appication and resides on a server dedicated to ony NFS functionaity. The benefits of this approach are: The recording is unaffected when an appication fais and switches to a redundant server. The dedicated NFS server aows greater capacity. Dayight Savings Time - United States and Canada As of 2007, Dayight Savings Time dates in the United States and Canada have changed. This requires updates to servers used for scheduing conference cas in these countries. Pease contact Avaya Support for assistance as shown from the foowing ur: 2 February 2008

3 S6200 Resoved Issues S6200 Resoved Issues Tabe 1 provides a ist of the issues resoved in the current reease. Tabe 1: S6200 Resoved Issues RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS Operator transaction ogs: FastDia The system does not record modifications to FastDia ists in the transaction og fies. Wrong Time of Day message payed incorrecty Message #230 shoud ony be payed if the code entered is vaid for a conference on the day it is entered but it was entered at the wrong time of day. However, the message is aso payed if the code entered is vaid for a conference schedued for the foowing day. Invaid conference code prompt is not interruptibe in Fex mode Entering an incorrect conference code when diaing into a conference in Fex mode causes the system to pay an incorrect entry annunciator. Participants must isten to the entire annunciator before the system aows them to enter the correct conference code. Administrator can enter 0 in the Fex Min Dia Out Digits and Fex Max Dia Out Digits fieds on the Configuration settings for Fex cas An Administrator may enter a 0 in the Fex Min Dia Out Digits and Fex Max Dia Out Digits fieds on the Configure Conference Scheduer screen. The minimum vaid setting for both fieds is 1. Workaround: Set these fieds to a number equa to or greater than 1. Off-Bridge Record wi not dia if the Dia String contains %P. For Off-Bridge Record, the dia string parameter '%P' instructs the system to dia the Conference Code in pace of this vaue. This works for Moderators in the Parent Conference of Unattended, On-Demand and FLEX Conferences. Since there is no Conferee Code in Attended or ANY Sub-Conference, Moderators of these conferences are not abe to dia digits using this string. Setting of ON for DRP: Auto-gen fiename causes errors in the daiy og report. However, the DRP name is generated propery and works correcty. You can disregard the error messages. 1 of Issue 6 February

4 Meeting Exchange 4.1 Service Pack 2 Reease Notes for the S6200/S6800 Servers Tabe 1: S6200 Resoved Issues RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS Conferences booked through a CRS aow Auto Extend Duration and Ports. When the system is configured to use a CRS, users are aowed to schedue conferences with auto extend ports and auto extend duration even when the software media server is not configured to use these features. The system wi not disconnect cas when the SIP phone is disconnected for any reason incuding network interruptions. Foowing network interruptions, the ca remains active in the conference. Workaround: If this situation occurs, use Bridge Tak to cear or disconnect the ca or the conference. Hep Lines reeased by operators may not return to the main conference. When mutipe Bridge Tak operators access ines from the Hep conference by using the Get Next Hep button and then reease the ines back into a conference, some channes may not return to the conference. Instead, the ines remain in the hep conference. NRP Operator is not avaiabe in DCBSched When you enabe the NRPOper on the Repace variabe w/ product name and then re-initiaized the media server, the operator is avaiabe in NRP Mode in Bridge Tak s Conference Scheduer, but is not avaiabe through Schedue Conference in DCBSched. Timed assistance fais to PLAY_MSG when ca branding is set to ENTER When a channe dias in using a number set to ENTER in the ca branding tabe, the caer does not hear the annunciator message or disconnect. The dbdisp utiity shows that the channe is in the Enter Queue, but Bridge Tak does not dispay this channe in an enter conference. Cbuti is not vaidating fieds. Whie the cbuti does not vaidate fieds, it can not process entries that it does not understand. Administrators must be cautious and enter vaid vaues. Specificay: Msg must be within the range of avaiabe annunciators. PS (prompt set) may not exceed 20. Function must be set to DIRECT, SCAN, ENTER, HANGUP, AUTOVL, or FLEX. The system repaces any other entry with NULL (for not branded). No error is thrown. The exception to this is an entry of VLINK, which causes an unknown database error of 6 4 February 2008

5 S6200 Resoved Issues Tabe 1: S6200 Resoved Issues RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS Unabe to search or print conferences schedued for the foowing year Conference scheduers, such as Bridge Tak, that do not accept a year in the date fied of a query, use date from the bridge. Uness searching for a conference in the current year, the system is unabe to find the conference record. Moderator Diaing *0 in ODO intercept conference affects CDR Moderator diaing *0 in an ODO intercept conference does not togge hep, rather it affects the caed channe s phone number in the CDR. A usua entry may ook ike this: :49: test spct 15:47:11 odo After the moderator dias *0 a coupe of times, the CDR entry ooks ike this: :24: *00*0 test spct 16:23:26 odo The system may not correcty interpret ABCD# sent as DTMF. Automatic conference recording setting has no effect Systems configured with both DRP and auto-gen fiename set to On do not record the conference, but do pay a prompt saying the conference is being recorded. Database transaction ogs can grow rapidy on a 1,500 port system. The DB transaction og is reset when a fu DB backup is aunched. Pease ensure that backups are schedued frequenty to avoid fiing the system. The system may pay, Someone has entered the conference, twice. The system pays the entry message whenever someone enters a conference room. On systems with mutipe MPC cards, if the system pays the message and then if it routes the caer to another card, the system wi pay the entry message again. When in ecture mode the user og does not dispay which annunciator was payed. When user presses *5 for ecture mode, the og fie does not record what annunciator (segment) number is payed. Other * commands dispay which segment is being payed. FLEX: Stop Recording information pays to whoe conference When the moderator presses *2 to record conference, a participants hear the message, To stop recording, press *2. Ony the moderator shoud hear the message. 3 of Issue 6 February

6 Meeting Exchange 4.1 Service Pack 2 Reease Notes for the S6200/S6800 Servers Tabe 1: S6200 Resoved Issues RNDCS RNDCS Participants remain in sub-conference after moderator presses *93. Moderators and participants sometimes remain in a sub-conference after the moderator uses the *93 DTMF to return a participants to the main conference. Unattended conferences with music seected do not pay the first person message in the sub-conference. The system does not pay the message, You are the first person in the conference when a participant is the first person in a sub-conference started from an unattended (on-demand) conference with M1 seected. If the conference is booked without music, the participant hears the first person message RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS Incorrect music source payed into the conference. After aocating FDAPI music channes, the wrong music source is payed into the conference. Ony anaog music heard when the music source is diaed after the conference starts. If a music source is diaed after the conference begins, then some participants are not heard in the conference. Dia out via TLS does not work in this reease. Dia out via TCP and UDP function as designed. The system does not reject cas when the software media server is down. When the software media sever is down, cas into the bridge remain in proceeding 100 status. Normay, the server woud reject the ca. For Fex fow, the system does not appy the message tone setting. When the Entry/Exit is set to Tone & Message the conference moderator ony hears the tone when a participant enters or exits a conference When the setting is Tone, the moderator hears nothing. The Audio Consoe and Bridge Tak may not detect sound. The Audio Consoe appication may not dispay correct icon and Bridge Tak may not dispay an asterisk (*) to refect that someone is taking. Caers connecting through B2BUA are getting disconnected from the conference due to Session Refresh Timer 4 of 6 6 February 2008

7 S6200 Resoved Issues Tabe 1: S6200 Resoved Issues RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS Dia out works but there is no audio in the subconference after the dia out and participant answers. Issue with B2BUA where the ANI of the phone is not passed if caing the STBY system and forwarded onto the ACTV Loss of Audio on ink ines with goba conferences. Happens particuary during or after a oad testing Caer hung in ANNUN CONF The audio woud cut out every 8 seconds for 80 miiseconds. Tak bit data was not being accuratey refected in Bridge Tak. Searching for a reservation via dcbsched caused a core fie tobe generated. Pressing # # # when istening to introductory annunciator did not send caer to the Enter queue. A recording that is paused via Audio Consoe cannot be restarted. Workaround: Stop the recording then restart it without using the Pause feature. Annunciators recorded by operators were ony avaiabe from the server to which they were recorded. With NFS, the recordings can be copied to a media servers. See Meeting Exchange Enterprise Configuring the S6200 Servers, Document SSH version has been updated to accomodate 2007 Dayight Savings Time change. When using Name Record Payback, the recorded name woud not pay back in its entirety. Invaid conference code prompt is not interruptibe in Fex mode Entering an incorrect conference code when diaing into a conference in Fex mode causes the system to pay an incorrect entry annunciator. Participants must isten to the entire annunciator before the system aows them to enter the correct conference code. Audio took a ong time to recover after an MPC faiover DIALPLACE API commands coud fai after a arge number were issued. 5 of Issue 6 February

8 Meeting Exchange 4.1 Service Pack 2 Reease Notes for the S6200/S6800 Servers Tabe 1: S6200 Resoved Issues RNDCS RNDCS RNDCS RNDCS QQ RNDCS RNDCS RNDCS Music woud sometimes pay momentariy into a conference when an Auto Virtua Link Line was added regardess of the music setting. Core fies were being deeted after 7 days. Core fies are now saved for 365 days. Bridge Tak sessions that were dropped did not aways cear competey. This resuted in users being unabe to og into the appication. When a moderator did an ODO, their conference entry time woud be isted as the time they returned after the ODO rather than their actua conference start time. Static woud sometimes pay into the conference when caer s name was stated as a resut of Name Record/Payback functionaity. Incorrect name woud sometimes pay into conference when Name Record/Payback feature was used with Entry Messages. The SavedRoster directory was saved to the wrong ocation. It is now pointed at /usr3/ipcb/usr2/roster. 6 of 6 8 February 2008

9 6800 Resoved Issues 6800 Resoved Issues This section describes issues with the hardware media server that are fixed in this reease. Tabe 2: 6800 Resoved Issues RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS Bridge Contro API event fieds are missing the conference ID. BCAPI events for Conferences and Participants expect to have a conference ID set in the conference ID fied. When running the API against this version of MX, many times the event fieds have a missing or nu conference ID. Operator Tak Events are not reported in the operator ogs The operator transaction ogs, avaiabe by seecting fie management > view > op trans ogs, do not dispay the whether operator tak is on or off. Sometimes the system ignores DTMF on ines routed through a Cisco Gateway Users experience a deay when using DTMF to request a sub-conference After pressing *93, it may take up to 2 seconds before an annunciator is payed. If you then seect a room whie the annunciator is paying, the message continues for another 2 seconds before the room number is acknowedged. No error message sent to indicate that the standby server faiure not having message for support to repace card System sometimes pays the conference entry message twice. The system pays, Someone has entered the conference. two times even though ony a singe caer has entered the conference. No audio when a ca is routed to MPC port 2. Workaround: The instaer wi configure the system so that the MPC card is on the same VLAN, rather than pacing port 1 in VLAN one and port 2 in VLAN two. Conference recordings do not stop when the conference ends Conference recordings started with the BCAPI continue to record after the conference coses. 1 of Issue 6 February

10 Meeting Exchange 4.1 Service Pack 2 Reease Notes for the S6200/S6800 Servers Tabe 2: 6800 Resoved Issues RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS Participants in the enter conference hear the anaog music source athough it is disabed When no other music source is estabished, the anaog music source pays in the enter conference even though the anaog music is disabed in the FDAPI menu. Workaround: Anaog music is the fie music_source1. Edit music_source1 so that it contains a few seconds of sience when you want do not want audio to pay in the enter queue, or when that music source is seected. Avaya 4602 SIP Phone compatibiity issues The foowing probems have been noticed when an Avaya 4602 SIP phone is configured to tak to the bridge directy: 70% of the time participants do not hear audio. Athough the system paces the participant into a conference, a DTMF is ignored. Fex management messages are payed 2-3 times Navigating the Account Management menu for a Fex conference prior to entering the conference may resut in annunciator messages being repeated 2-3 times. On a segmented network, there are probems with faiover to a card without ethernet connectivity On a segmented network, the system attempts unsuccessfuy to connect to an MPC that does not have Ethernet connectivity. Despite not being abe to connect, the system does not reease the fauty MPC and attempts to connect to another free MPC. Workaround: Manuay cause the faiover by pacing the card out of service and then returning the card to service. Conference oses audio when the system is under oad. Once the conference oses audio, the same conference PIN code can not be used again unti the system is re-booted. Intermittent probem with faiover Repeated faiovers resut in the wrong number of MPC cards being paced in use. Msdispatcher was trying to buid conferences on an MPC card that was out of service. The MPC was not responding to BYE messages. Latest reease of support Convedia firmware ( )addresses this issue. Audio took a ong time to recover after an MPC faiover 2 of 3 10 February 2008

11 S6200 Operationa Issues Tabe 2: 6800 Resoved Issues RNDCS RNDCS RNDCS When an MPC faiover took pace, taker data no onger worked for conferences that were active at time of the faiover. When an operator opened the ine isten diaog window and cosed it without istening to a ine, caers woud experience dead air for up to 30 seconds as the MPC faied over. When caers entering # after stating their name, the # was not sent to the appication server. This caused a deay in conference entry and resuted in users thinking they had entered an invaid code.. 3 of 3 S6200 Operationa Issues This section describes known system issues with the S6x00 media server. Tabe 3: S6200 Operationa Issues od BR Number MR Number RNDCS RNDCS Q&A fag can remain ON even when a participants hang up from a conference. Conference Cear does not cear a attributes. Workaround: Open Q&A and cose then cose Q&A. Seect "yes" to end the Q&A. p_dersrvtnbycnum can not find the Confirmation Number p_dersrvtnbycnum expects a compete, tweve digit confirmation number to ocate a reservation. Currenty, this procedure does not add the extra digits to entries that are ess than tweve digits. For exampe, the procedure wi not find a reservation when passed a vaue of 123. However, when passed a vaue of , the procedure ocates and then deetes the reservation. 1 of Issue 6 February

12 Meeting Exchange 4.1 Service Pack 2 Reease Notes for the S6200/S6800 Servers Tabe 3: S6200 Operationa Issues od BR Number MR Number RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS RNDCS If a user disconnects from a ca during the NRP request, some CDR fieds may be bank or contain incorrect information. If the first person to join the conference drops the ine, these fieds are bank: CrossRef, ConfirmNum, ConferenceName. If the second or ater person to join the conference drops the ine, the conferenceentrytime fied dispays 00:00 GMT. Moderator can not dia out or start off-bridge recording Moderator can not dia out or start off-bridge recording when auto extend ports = on. The system does not record the prompts 244 and 246 in the User Transaction og when they are payed during a bast dia, even though they can be heard in the conference. If conference Recording is paused and then stopped, the conference is paced in a mode from which Recording and Payback cannot be initiated. When the music source changes after the conference starts, participants hear unexpected audio. When Anaog music is set to ON in FDAPI and externa music sources are diaed, participants diaing in may not be heard in the conference. Occasionay, if the music source is changed, a repetitive sound may be heard payed in the conference, but the participant may not be heard. The first entry on a dia ist may fai to connect when using Bridge Tak to Re-bast the dia ist. System pays the wrong message into a conference that is started after a conference ends whie sti recording. The system pays the conference recording stopped message to the new conference if the previous conference was hung up whie recording or whie a payback was in process. The system does not record the phone number for an operator diaed channe in the User transaction og. Timed assistance fais to PLAY_MSG if the ca branding is set to SCAN. When ODO is disabed on the system, the system does not pay an error message to a participant attempting to perform an outdia. Roster recordings cannot exceed 1,999 participants FDAPI ink ines cannot be disconnected via the audio path diaog box uness they are part of an active conference. 2 of 3 12 February 2008

13 Avaya Communications Manager Interoperabiity Issues Tabe 3: S6200 Operationa Issues od BR Number MR Number RNDCS RNDCS RNDCS RNDCS For a dia in channe, the defaut music channe pays regardess of which music channe has been assigned to the conference. The moderator is not abe to move from a secured main conference to a secured subconference. A software error is generated in ogs when NRP is set to individua for an on demand conference. NRP functionaity is not affected. A recording that is paused via Audio Consoe cannot be restarted. Workaround: Stop the recording then restart it without using the Pause feature. 3 of 3 Avaya Communications Manager Interoperabiity Issues The Avaya Communications Manager sends an INVITE message over TCP with a request URI that does not specify the transport. When S6x00 generates the response message, it copies the request URI to the response's contact header. The request URI specifies the defaut transport as UDP. The Avaya Communications Manager then fais to send the ACK message because it tries to send the message over UDP, which is not avaiabe on the ca manager. Workaround: Configure S6x00 so that the contact parameter overwrites the defaut contact so that the Avaya Communications Manager is abe to send the ACK message back to S6x Issue 6 February

14 Meeting Exchange 4.1 Service Pack 2 Reease Notes for the S6200/S6800 Servers S6800 Media Server Operationa Issues This section describes known issues specific to the S6500 and S6800 media server configurations. Tabe 4: Operationa Issues for the S6800 Media Servers MR Number RNDCS RNDCS RNDCS Systems connecting to a CopperComm Gateway, which ony uses in-band DTMF, do not hear audio The *8 command does not correcty report the roster when the number of participants exceeds 999. When there are more than 999 participants in a conference, the *8 command causes the system to pay a message saying, "There are 999 participants in the conference." On systems using the defaut ca fow, the 726th person who tries to enter a conference is paced into the pending queue indefinatey. Subsequent caers enter the conference without a probem. On systems using the Fex ca fow, the 51st person who tries to enter a conference is paced into the pending queue indefinitey. Subsequent caers enter the conference without a probem. Workaround: Bridge Tak operators can pace the caer into the conference. 14 February 2008

Bridge Talk Release Notes for Meeting Exchange 5.0

Bridge Talk Release Notes for Meeting Exchange 5.0 Bridge Tak Reease Notes for Meeting Exchange 5.0 This document ists new product features, issues resoved since the previous reease, and current operationa issues. New Features This section provides a brief