NEC Univerge SC8100 Installation Manual
  1. Manuals
  2. Brands
  3. NEC Manuals
  4. Telephone Accessories
  5. Univerge SC8100
  6. Installation manual
NEC Univerge SC8100 Installation Manual

NEC Univerge SC8100 Installation Manual

Mycalls enterprise
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
MyCalls Enterprise Installation Manual
Version 1.3

Advertisement

Table of Contents
loading

Related Manuals for NEC Univerge SC8100

Summary of Contents for NEC Univerge SC8100

  • Page 1 MyCalls Enterprise Installation Manual Version 1.3...
  • Page 2 Document History Revision 1.1 Feb 2008 Initial Release Revision 1.2 Jan 2011 Update for Version 3.0.0.0 Revision 1.3 May 2012 Update for MyCalls 3.5.0.0...

  • Page 3: Table Of Contents

    Table of Contents Description ......................4 Requirements ........................... 5 Telephone System ......................5 PC Specification ......................... 5 Data Storage ........................5 Licensing ............................. 6 Installation Scenarios ........................7 Scenario 1 – A Central MyCalls PC Colleting from Multiple PBX’s ........7 Scenario 2 –...

  • Page 4: Description

    Description MyCalls Enterprise can be used to provide a centralised call management solution for an organisation. This manual is intended to give an installer who has knowledge of MyCalls the ability to install MyCalls enterprise. MyCalls Enterprise works with the SV8100, Aspire, XN120 and SL1100 In an Enterprise installation a mixture of these different PBX’s can be used.

  • Page 5: Requirements

    Requirements Telephone System All SV8100 PBX’s will need to run SV8100 R7 system software or greater. If an Aspire or XN120 will be part of the enterprise then they will need to be run 7.60 system software or greater. An Ethernet connection to the SMDR and P command output will be required.

  • Page 6: Licensing

    Licensing The license for an Enterprise installation will be firstly installed on an SV8100 that has been nominated as the SV8100 that will hold the license for the entire Enterprise. Any licenses relating to the MyCalls Enterprise software will have to be installed on the SV8100 that is holding the license. That will include any additional application users or call recording licenses.

  • Page 7: Installation Scenarios

    The same level of MyCalls software should be used where different types of NEC PBX’s are used. Check with your technical support if you are unsure about the current released versions of MyCalls.

  • Page 8: Scenario 2 - Clustered Installation With A Cluster Server And Node Cluster Clients

    Scenario 2 – Clustered Installation with a Cluster server and Node Cluster Clients In this scenario, a PC is elected as a Cluster Server. This is the PC that holds the configuration and call records database for all the sites. The Cluster server also holds the license for the entire enterprise.

  • Page 9: Scenario 3 - Clustered Install With Group Cluster Clients

    Scenario 3 – Clustered Install with Group Cluster Clients In this scenario there is a cluster server which stores the configuration and call records for the entire enterprise. There are also PC’s that act as Group Cluster Client’s. A Group Cluster Client can collect from up to 10 SV8100’sw and feed back call information to a cluster server.

  • Page 10: Scenario 4. A Cluster Server With Node Cluster Clients And Group Cluster Clients

    Scenario 4. A Cluster Server with Node Cluster Clients and Group Cluster Clients. This scenario is a combination of both clustering methods used in scenario 2 & 3. There is a Cluster server which is responsible for holding the central MyCalls database. There are then a combination of node cluster client and group cluster clients.

  • Page 11: Installation Procedures

    Installation Procedures The following section describes the installation procedures for the different enterprise solutions. Each of the following scenarios can be installed using SQL Express 2005 or SQL 2005. Further information on installing MyCalls with SQL 2005 is documented in the Installing MyCalls with SQL 2005 section of These instructions work on the assumption that only SV8100’s are used in the this manual.
  • Page 12 Once the license has been installed and the Config import has been completed for the first PBX, login to MyCalls as an Enterprise Administrator. From the Configure menu, select Telephone System. Click Create a New PBX. Enter a name of the PBX in the PBX code box, set the Country, the Area code and the International Access code as required.
  • Page 13 Once each PBX has been added, start the config import tool. In the config import, select the general page and from the ‘Assign Configuration to PBX Code’ drop down menu, select the PBX you are going to do the import for. After selecting the correct PBX, complete the import procedure, adding the extensions, DDI’s and trunks as required.

  • Page 14: Scenario 2 - Clustered Installation With A Cluster Server And Node Cluster Clients

    Scenario 2 – Clustered Installation with a Cluster Server and Node Cluster Clients The steps to installing this scenario are summarised as follows:  Make sure that all the PBX’s are programmed for MyCalls. Refer to the MyCalls Installation guide for further details. ...
  • Page 15 Load MyCalls, from the Configure menu, select Telephone System. Click Create a New PBX. Enter a name of the PBX in the PBX code box, set the Country, the Area code and the International Access code as required. Enter a node number, each PBX must have a unique node number with the Enterprise.
  • Page 16 Elect the Cluster Server Start the toolkit.exe application from the c:\program files\NEC Infrontia\MyCalls folder The toolkit application will load. From the toolkit, click the clustering menu.
  • Page 17 Now select the ‘This computer is being used as a cluster server’ option. Once you have selected to be a cluster server, select all the PBX’s in the configuration and reporter boxes. In the Statistics box, ONLY select the PBX’s that are directly connected to the cluster server. DO NOT select statistics for any of the node cluster clients PBX’s.
  • Page 18 Install and Configure Node Cluster Clients Repeat the installation procedure of MyCalls, carrying out a complete installation. Once the installation has completed, cancel the license check and DO NOT do a config import, instead start the toolkit application from the c:\program files\NEC Infrontia\MyCalls folder.
  • Page 19 In the toolkit click Clustering. In the upper section of the Clustering Configuration select ‘This computer is being used as a node cluster client.’ At the lower section on the configuration screen, enter the name of the PC acting as the cluster server in the ‘Cluster Server’ box. In the Cluster SQL Server box, enter the name of the PC that is hosting the MyCalls database followed by \kss.
  • Page 20 Each of the MyCalls services will all stop and then start. Click OK at each prompt. The PC is now configured as a node cluster client. Do the config import for the PBX you selected in the node cluster configuration. Be sure to select the correct PBX in the General page before importing the config.
  • Page 21 Again this procedure is similar to that from scenario 2. On the Group Cluster Client PC, firstly carry out a complete installation of MyCalls. Once the installation has completed, start the toolkit application from the C:\Program Files\NEC Infrontia\MyCalls folder. The toolkit application will load.
  • Page 22 From the toolkit, click the clustering menu. From the Clustering configuration screen select ‘This Computer is being used as a group cluster client.’ At the lower section of the configuration screen, enter the name of the Cluster Server PC in the Cluster Server box. In the Cluster SQL Server box, enter the Cluster Server PC followed by \KSS.
  • Page 23 Each of the MyCalls services will all stop and then start. Click OK at each prompt. The group cluster client in now configured. Ensuring that each PBX is configured, carry out the configuration import for each PBX. Before you start the configuration import, make sure the correct PBX is selected in the general page.

  • Page 24: Scenario 4 - A Cluster Server With Node Cluster Clients And Group Cluster Clients

    Scenario 4 - A Cluster Server with Node Cluster Clients and Group Cluster Clients. This scenario is a combination of Scenario 2 and 3, the installation steps are summarised as follows.  Install and Elect the Cluster Server  Install the MyCalls Enterprise license on the SV8100 that will hold the license. ...

  • Page 25: Scenario 6 - Mycalls Call Centre And Enterprise (Non-Netlink)

    Scenario 6 – MyCalls Call Centre and Enterprise (Non-Netlink) When MyCalls Call Centre is used in a Non Netlink configuration then the procedure for installing MyCalls is no different and can be used in any of the installations scenarios 1-4. The main difference to the whole setup is how the Call Centre licensing works.

  • Page 26: Using Mycalls With Sql 2005

    Using MyCalls with SQL 2005 By default, MyCalls comes with SQL Express 2005. SQL Express 2005 will store up to approximately 16,000,000 call records. Once with limit has been reached it will be necessary to purge historic data from MyCalls. With SQL 2005, there are no limits on the amount of data that can be stored. SQL 2005 is therefore ideal for organisations that have the requirement to store over 16,000,000 calls within MyCalls.
  • Page 27 From the list of components, make sure everything is selected and click next. At the collector screen, leave the name as Local Collector and click next.
  • Page 28 At the database server screen, select the option to ‘Select the SQL Server to connect to or click Browse to see a list of all SQL Servers.’ Click the Browse button and select the database server from the list provided. If the database if going to be installed on to a default instance on the SQL server then you should select (local) from the list of database servers.

  • Page 29: Installing Mycalls And The Mycalls Database On Separate Pc's

    Installing MyCalls and The MyCalls Database on Separate PC’s It may be a requirement to install MyCalls and the MyCalls database on separate PC’s. If there is a PC that is used as a corporate SQL Server running several instances of SQL database, then it might be worth keeping the MyCalls application on a separate server.
  • Page 30 Click next until you are prompted to enter a server name. The server name will be the PC name of the computer that will have MyCalls installed on. Enter the name and click next. The MyCalls database will be installed and ready for use. On the PC that will be the MyCalls server, start the MyCalls installation and choose a custom installation type.
  • Page 31 At the Call Collector Name prompt DO NOT change the name from local collector and click next. At the database configuration screen, choose to Select the SQL Server and click browse. When you click browse, select the PC name that the MyCalls Database is installed on. If the MyCalls database was installed into a named instance, then select the PC name followed by \instancename.

  • Page 32: Testing The Connection To The Mycalls Database

    Testing The Connection to the MyCalls Database To test the connection to the MyCalls Database, start the toolkit application from c:\program files\necinfrontia\MyCalls folder. When the toolkit loads, click on Configuration and test from the client menu. The client and configuration and test screen will load. Click the Test Connections button and MyCalls will verify if it can connect its services.

  • Page 33: Adding An Sv8100 Or Aspire

    When adding an Aspire, you will need to create two connections, one for P Events and one for SMDR. From the Start/Programs/NEC Infrontia/MyCalls/ menu launch the Collector Configuration application. At the login prompt, enter the User name ‘installer’ and password ‘Installer’ note: the password has a capital ‘I.’...
  • Page 34 Locate the connection that you have just created and click on ‘Edit Telephone System Template.’ From the drop down menu select ‘NEC Infrontia European Aspire/XN120, Line/DID presented, Use Computer Date 6 Digit DDI’ for SV from the drop down menu. On Aspire select ‘NEC Infrontia European Aspire/XN120, Line/DID presented, Use Computer Date’...
  • Page 35 You will be ask if you wish to overwrite the current template, click yes and then OK. The connection for the SMDR has now been created. There is a similar procedure for creating a connection to the P Events. Start by creating a connection for the P Events and giving it a meaningful name relating to the PBX and the connection type.
  • Page 36 Locate the connection that you have just created and click on ‘Edit Telephone System Template.’ From the drop down menu select ‘NEC Infrontia Aspire/SV8100 Events’ from the drop down menu. You will be ask if you wish to overwrite the current template, click yes and then OK.

  • Page 37: Adding An Xn120

    Once the connections are successfully created, you should see calls from the newly added PBX in the call records view. Adding an XN120 or SL1100 Adding an XN120 or SL1100 using the collector configuration application is very similar to adding an Aspire.
  • Page 38 Select the connection that you have just created and click ‘Edit Telephone System Template.’ From the drop down menu under Predefined Templates, select ‘NEC Infrontia European Aspire/XN120, Line/DID presented, Use Computer Date 6 Digit DDI.’ When prompted, choose to overwrite the current template then click OK to save the changes. Close the Collector configuration application when you have finished.

  • Page 39: Using Mycalls Enterprise

    Using MyCalls Enterprise Real Time Windows When creating real time windows, you can select which PBX’s they will be for. If you are in a clustered mode, you will only be able to create real time windows for PBX’s you have checked statistics for in the toolkit.

  • Page 40: Reporting - Clustering Mode

    Once you have selected to filter by a PBX you can choose which PBX’s to include in the report. Reporting - Clustering Mode A cluster server should be able to report against all PBX’s that have been selected for reporting in the toolkit clustering configuration.
  • Page 41 NEC Philips Unified Solutions has prepared this document for use by its employees and customers. The information contained herein is the property of NEC Philips Unified Solutions and shall not be reproduced without prior written approval from NEC Philips Unified Solutions. All brand names and product names on this document are trademarks or registered trademarks of their respective companies.

Table of Contents