CHANNEL MANAGER. Activ! Voice - MITEL Channel Manager (rev c) - draft

Transcription

1 ACTIV! VOICE - MITEL CHANNEL MANAGER VPI 160 Camino Ruiz, Camarillo, CA (Voice) (Fax)

2 Contents Overview Scenarios Single Site Call Recording with a Single SRC (Figure 1)... 3 Dual SRC s (Figure 2) Resilient Mitel 3300 s Single SRC (Figure 3)... 5 Resilient MN3300 s and Dual SRC s (Figure 4)... 6 Multiple MN330 s with Single SRC (Figure 5)... 7 Hot Desking (Figure 6) Initial Setup Creating the Initial.INI file Configuration File (SRCSetting.ini)... 9 Example of a SRCSetting.ini file supporting dual SRC s Verifying DHCP Options of the Mitel 3300 IP (ICP) Integrated Communications Platform Configuration Configuration (VPConfig) VPConfig > Channel Manager > Mitai Server (Tab) VPConfig > Channel Manager > Database (Tab) VConfig > Channel Manager > Software RTP (Tab) Troubleshooting Verifying Event Center Logging Typical example of a revoked or an unapproved SRC Tunnel Certificate Typical example of a successful or approved SRC Tunnel Certificate Verifying Approved MSL Certificates Verifying the.ini file Example of a populated SRC Tunnel Certificate within the.ini file for a single SRC Revision History Copyright 2008 Voice Print International, Inc. The information contained herein is subject to change without notice. As the registered end user, you are free to make and use as many copies of this manual as you like, so long as it is used for internal purposes only and is not transmitted in any manner whatsoever to any individual, organization or corporate entity not specifically named in your End User License Agreement. Voice Print International, Inc., shall not be liable for technical or editorial errors or omissions contained herein. Other product names mentioned in this document may be trademarks of their respective companies and are hereby acknowledged. Mitel Networks Corporation (MITEL ) 2 TOC

3 Syst em x3550 Syst em x3550 Activ! Voice - MITEL Channel Manager (rev c) - draft Overview The Activ! Voice Mitel Channel Manager is a call recording solution that utilizes the Mitel Secure Recording Connector (SRC) to record Mitel voice streams positioned on the LAN. IP phones register with the Mitel 3300 IP Communications Platform (ICP) through the SRC; then, the SRC mirrors the voice streams of any enabled IP phone set to the RTP (Real Time Protocol) of the Activ! Voice system. Scenarios Figures 1 through 6 describe various scenario configurations supported by VPI. Single Site Call Recording with a Single SRC (Figure 1): PSTN MiTAI Link to 3300 ICP Controller 3300 ICP Controller Mitel SRC Server LAN ` Activ! Voice Recorder 192 Channel Capacity (Per Server) SRC voice stream according to configured policies Search and Playback Figure 1 This is a single site solution with extensions on a single SRC. All recorded extensions must pass via the SRC; VPI Servers then connect to this SRC for the call RTP stream. The VPI Server will also need to connect to the MiTAI Server to gain call details. If the SRC fails then the telephony for those users is lost. The problem can be countered utilizing a Fault Resilient SRC Server. Overview/Scenarios 3

4 Syst em x3550 Syst em x3550 Syst em x3550 Activ! Voice - MITEL Channel Manager (rev c) - draft Dual SRC s (Figure 2): PSTN MiTAI Link to 3300 ICP Controller 3300 ICP Controller Mitel SRC Server LAN ` Activ! Voice Recorder 192 Channel Capacity (Per Server) Mirrored voice stream according to configured policies Search and Playback Figure 2 This configuration shows resiliency with a second SRC Server on a second Mitel Standard Linux Server. Mitel IP sets are configurable for a primary and secondary SRC. If the primary SRC fails then the call is dropped and the IP sets are re-homed to the secondary SRC. The set will not re-home back to its primary SRC until it or the 3300 is re-booted. This configuration requires two sets of licenses for each SRC. The VPI Voice Server will need to connect to both SRC s and the MiTAI Server to collect call data. 4 Scenarios

5 Syst em x3550 Syst em x3550 Activ! Voice - MITEL Channel Manager (rev c) - draft Resilient Mitel 3300 s Single SRC (Figure 3): PSTN MiTAI Link to 3300 ICP Controller 3300 ICP Controller 2 nd 3300 ICP Controller for Failover Mitel SRC Server LAN ` Activ! Voice Recorder 192 Channel Capacity (Per Server) SRC voice stream according to configured policies Search and Playback Figure 3 All IP sets reside on one 3300 unless it fails over to the 2nd In this instance the SRC will failover too. This is a feature of the 3300 and Mitel IP set resiliency and not the SRC. Recording will continue as no extension numbers have changed. If the SRC fails, calls will be lost until it is re-instated. An important point is that 1 SRC can handle multiple 3300 s. Scenarios 5

6 Syst em x3550 Syst e m x3550 Syst em x3550 Activ! Voice - MITEL Channel Manager (rev c) - draft Resilient MN3300 s and Dual SRC s (Figure 4): PSTN MiTAI Link to 3300 ICP Controller 3300ICP Controller 2 nd 3300ICP Controller for Failover Mitel SRC Server LAN ` Activ! Voice Recorder 192 Channel Capacity (Per Server) Mirrored voice stream according to configured policies Search and Playback Figure 4 The SRC s can be programmed with a primary and secondary 3300 Controller. If one SRC fails, the 3300 can be programmed to re-home the IP sets to the secondary SRC. This configuration requires two sets of licenses for each SRC. 6 Scenarios

7 Syst em x3550 Syst em x3550 Syst em x3550 Syst em x3550 Activ! Voice - MITEL Channel Manager (rev c) - draft Multiple MN330 s with Single SRC (Figure 5): PSTN MiTAI Link to 3300 ICP Controller 3 X MN3300 with users that need to be recorded subscribed on each MN3300 controller. Mitel SRC Server LAN Search and Playback ` Activ! Voice Recorder 192 Channel Capacity (Per Server) SRC voice stream according to configured policies Figure 5 The SRC can handle multiple Controllers whether for resiliency or to increase capacity. An SRC can handle 350 concurrent calls and 1000 licenses per Server. Scenarios 7

8 Hot Desking (Figure 6): Figure 6 A user with Hot Desking can register at any location as long as the IP set is connected to an SRC, calls will be recorded. MiTAI provides the call information to the local SRC. 8 Scenarios

9 Mitel Initial Setup Creating the Initial.INI file Configuration File (SRCSetting.ini) Use the Windows Notepad application to edit the default configuration file. The default file name is called SRCSetting.ini but in actuality the name of the file can be any name deemed appropriate to the editor. The name just needs to match the Secure Connector Options within the Channel Manager > Mitel Server Tab. The file needs to reside within the C:\clogger directory of the Activ! Voice Server. The initial file must contain at least the following information (example for a single SRC): [general] version=0 [ca_list] count=1 ca.0= [ ] address= state=0 cn=vpicalllogger [tunnels] count=1 tunnel.0=1000 Count indicates how many MSL servers are hosting. First IP address. See NOTE 1. IP address. State should equal zero. Unique name for MSL Server IP. Tunnel Count equals one. One Tunnel. [1000] ca= :6810 listen= :1000 connect_to= :6810 ssl_in=0 ssl_out=1 use_cert=1 Port 6810 must be entered after the MSL Server IP separated by a colon). Port 6810 must be entered after the MSL Server IP separated by a colon). NOTE 1: Wherever the IP is used you have to substitute the address of the Mitel Standard Linux (MSL) server that is hosting the Mitel Certificate Services. For the purposes of this example, we will assume that the MSL server resides at address NOTE 2: Please reference Mitel MiSSL Tunnel Developer Guide for additional information on the MSL Initial Setup. Initial Setup 9

10 Example of a SRCSetting.ini file supporting dual SRC s: [general] version=0 [ca_list] count=2 ca.0= ca.1= [ ] address= state=0 cn=vpicalllogger-1-src1 Count indicates how many MSL servers are hosting. First IP address. Secondary IP address. First IP address. State should equal zero. Unique name for first MSL Server IP. [ ] address= state=0 cn=vpicalllogger-1-src2 [tunnels] count=2 tunnel.0=1000 tunnel.1=2000 [1000] ca= :6810 listen= :1000 connect_to= :6810 ssl_in=0 ssl_out=1 use_cert=1 [2000] ca= :6810 listen= :5000 connect_to= :6810 ssl_in=0 ssl_out=1 use_cert=1 Second IP address. State should equal zero. Unique name for second MSL Server IP. Tunnel Count equals two (for both MSL Server IP addresses). First Tunnel. Second Tunnel. Port 6810 must be entered after the MSL Server IP separated by a colon). Port 6810 must be entered after the MSL Server IP separated by a colon). Port 6810 must be entered after the MSL Server IP separated by a colon). Port 6810 must be entered after the MSL Server IP separated by a colon). 10 Initial Setup

11 Verifying DHCP Options of the Mitel 3300 IP (ICP) From Internet Explorer, launch the System Administration Tool from the 3300 IP ICP interface. From the System Configuration pane choose IP Network Configuration > DHCP > DHCP Options. DHCP Options 11

12 From DHCP Options, highlight the Mitel ID option and then select Change from the upper right hand side of the ICP. From the DHCP Options dialog window; make certain the SRC IP address in the Call Server Address Mitel Tag entry box, matches the entry in the SRCSetting.ini configuration file of each Activ! Voice Server. NOTE: Multiple Servers need to be separated by a comma (i.e., , ). Log out of the ICP. 12 DHCP Options

13 Integrated Communications Platform Configuration From Internet Explorer, launch the MSL login page. Login to the MSL application: Go to Configuration > ICP s, and verify the ICP or multiple ICP s are configured for each SRC to the PBX. Log out of the MSL. ICP Config 13

14 Configuration (VPConfig) The following instructions apply to each Activ! Voice Server (depending on your environment). For multiple Activ! Voice Servers be certain that they all point the same PBX (see Mitai Server Setup below). VPConfig > Channel Manager > Mitai Server (Tab): Start the Voice Print Server Configuration application (VPConfig) and then change to the Channel Manager Tab: Mitai Server Setup: Enter the IP Address of the Mitel Switch and Fallback IP address (for fail over configurations). Log Mitai Events: Checking this checkbox will log trace events to the Event Center log file. This should be checked initially to verify the validity of the installation. Time Intervals: To keep communication open to the Mitel switch, be certain that the following default settings are set: Secure Connector Options: Based on the Initial Setup, and the creation of the Configuration.INI file, type the path or search explicitly for the.ini file and be certain to check the Enable checkbox, otherwise Voice Print will not be able to communicate with the MSL and a Certificate will not be approved. NOTE: The INI Password should be left blank. Logging: This is a critical entry! If it is not included, then Activ! Voice will not initiate! Type the path F:\Event Log\ verbatim in the Directory box to properly log events to the Event Center log file. Select the Apply button when your changes are complete. 14 VPConfig

15 VPConfig > Channel Manager > Database (Tab): To store additional data fields, enter the Database Fields (as shown in the screen shot below) and use the add column button to add a compatible DB field for storing the selected data item. Database Mappings MiSRC Phone/Device MAC Address MiSRC Phone/Device IP MiSRC Phone/Device Port MiSRC RTP Destination IP MiSRC RTP Destination Port MiSRC RTP Codec DB Field PHONEMAC PHONEIP PHONEPORT DESTIP DESTPORT CODEC Select the Apply button when your changes are complete. VPConfig 15

16 VConfig > Channel Manager > Software RTP (Tab): Activ! Voice uses a standard network as the Real Time Protocol (RTP) recording device. VPConfig will show this Configuration Tab within the Channel Manager called Software RTP. RTP Setup: Destination IP Address: Enter the IP Address of the Activ! Voice Logger. The NIC will both listen and stream the RTP data. Time Intervals: Idle Timeout: (integer) default 5 Time value in seconds after each a channel is declared idle and stops recording InterPacket Sleep: (integer) default 100 Time value in milliseconds between polling RTP receive ports. Designed to improve performance in the future. Apply/Cancel Buttons: Select these buttons prior to exiting the Software RTP Tab. 16 VPConfig

17 Troubleshooting Verifying Event Center Logging Check the Event Center Log to make certain the Mitel Key is valid. If not, check the MSL for a valid Certificate. Typical example of a revoked or an unapproved SRC Tunnel Certificate: INFO: 200, (Channel Manager) MiTAI Link Established and Ready. TRACE: 200, (Mitel SRC Link) Initializing MiSSL Tunnel library TRACE: 200, (Mitel SRC Link) Generating SRC Tunnel Certificate Request(s) TRACE: 200, (Mitel SRC Link) Sending SRC Tunnel Certificate Request(s) NOTIFY: 200, (Mitel SRC Link) SRC Tunnel Certificate Request(s) are pending approval! Please check the SRC Server(s). Recording cannot proceed until the Certificate(s) have been approved. INFO: Event Center, (Notify) Pop-up Acknowledged, Voice Print Server (Mitel SRC Link): SRC Tunnel Certificate Request(s) are pending approval! Please check the SRC Server(s). Recording cannot proceed until the Certificate(s) have been approved. Typical example of a successful or approved SRC Tunnel Certificate: TRACE: 200, (Mitel SRC Link) Retrieving SRC Tunnel Certificate(s) TRACE: 200, (Mitel SRC Link) Starting SRC Tunnel(s) TRACE: 200, (Mitel SRC Tnl 0) Connecting to SRC Tunnel. IP: , Port: 1000 INFO: 200, (Mitel SRC Tnl 0) Connected to SRC Tunnel TRACE: 200, (Mitel SRC Tnl 0) Sending Register SRC Command... INFO: 200, (Mitel SRC Link) SRC Tunnel: 0, Link is UP.06/30/08 10:11:47a INFO: 200, (Mitel SRC Tnl 0) SRC Server Register Reply, Version: , Protocol: 1.0, Max Taps: 12, Max G.729: 0, Current Sets: 3 INFO: 200, (Channel Manager) SRC Link is UP. Troubleshooting 17

18 Verifying Approved MSL Certificates From Internet Explorer, launch the MSL login page. Login to the MSL application: Go to Security > Certificate Management, and verify that the Approved Certificates match the Call_Logger ID. If not, stop Activ! Voice and verify the.ini file for accuracy, then restart Activ! Voice. Log out of the ICP. 18 Troubleshooting

19 Verifying the.ini file If the SRC Tunnel Certificate is revoked or unapproved, then you will have to manually edit the private_key= and state= entries of the INI file for each SRC. Change the following.ini file entries, save, and then restart Activ! Voice. state=0 Reset the value to 0 private_key= Completely erase these entries along with the encrypted key(s). Example of a populated SRC Tunnel Certificate within the.ini file for a single SRC: [general] version=0 [ca_list] count=1 ca.0= [ ] address= state=4 cn=vpicalllogger private_key=erxzc8b6ynnffx+kamxubmkkfv9jdrkzae3pqedpy/aaaiv8bnp9tuvhddyoeftgixtfdgawquu zjriq3n1bwpyfodimn/4bqn1/wnlzcyvos5jqnnjutpw+xmh8i/dqllzx+yxtyatolxrrpwxllznmdnv91hkn6s13onwtg FErR2Y99PbKD7P+MHHXiKc1MAdL/7ACCh5EsSvcc3l0J3CxGOi5d0NaUSJwkAbH8qsKuObQA5ExnXkHI8mHBw/ zfcrsf5blk4vvzvbahnc3m08fg2kd0qzfyk4q3awrhtas/9pltmem/jt9ix9lwezuane2vuiklv4dr8vmoi+kqi+ja7xm/ FBiRtajOWDKsZJd7G2VjuVZ5Dm+QInl1y1lzxjHVKnxdbWgaXHW8mk8/QXBsMHK7DF/GYmUuE9T/s5jQnNjUXTyd= [tunnels] count=1 tunnel.0=1000 [1000] ca= listen= :1000 connect_to= :6810 ssl_in=0 ssl_out=1 use_cert=1 Troubleshooting 19

20 Revision History Rev Level: Date: Description: Rev A: 06/27/08 Initial Release. Rev B: 07/02/08 Page 3: Added the following (in bold): Creating the Initial.INI file Configuration File (SRCSetting.ini): The initial file must contain at least the following information (example for a single SRC): NOTE 3: Please reference Mitel MiSSL Tunnel Developer Guide for additional information on the Initial Setup. Rev C: 08/12/08 Pages 3-8. Added Scenario diagrams to the Overview Section. Added an INI file example for Dual SRC s. Page 12. Change the statement: From the DHCP Options dialog window; make certain the SRC IP address in the Call Server Address Mitel Tag entry box, matches the entry in the SRCSetting.ini configuration file of each Activ! Voice Server. NOTE: Multiple Servers need to be separated by a comma (i.e., , ). Page 13. Added ICP Configuration. Page 14. Added the statement for VPConfig: The following instructions apply to each Activ! Voice Server (depending on your environment). For multiple Activ! Voice Servers be certain that they all point the same PBX (see Mitai Server Setup below). 20 Revision History