Installation

How to Configure Class of Service Objects

The Class of Service Manager is used to create objects used to assign permissions or restrictions to Outgoing Lines, Incoming Lines, Extensions, Feature Codes, or Applications.

Great care should be taken when configuring Class of Service objects.

Please refer to https://blog.scopserv.com/2012/06/important-security-settings-when-using-class-of-service-cos/ before configuring Class of Service objects.

 

Module 8 - ScopTEL - Class of Service Configuration
Read More

Performance Tuning Recommendations for ScopServ HTTPD Server Properties.

Performance tuning your HTTPD server settings can avoid things like high memory usage and swap file usage.

 

apachetuning

 

Memory Limit (PHP): Default 128 MB
Maximum amount of memory a script may consume
ScopServ recommends the default setting.  Only increase this value if a commit fails to complete due to memory exhaustion.

Minimum number of idle child server processes: Default 10
This directive sets the desired minimum number of idle child server processes. An idle process is one which is not handling a request. If there are fewer spareservers idle then specified by this value, then the parent process creates new children at a maximum rate of 1 per second. Setting this parameter to a large number is almost always a bad idea.

ScopServ recommends adjusting the value for this setting to the following:
Virtualized server 5
Dedicated server with 1-2GB RAM 10
Dedicated server with 2-4GB RAM 20
Dedicated server with 4+ GB RAM 25

Maximum number of idle child server processes: Default 20
This directive sets the desired maximum number of idle child server processes. An idle process is one which is not handling a request. If there are more than MaxSpareServers idle, then the parent process will kill off the excess processes.
This value should be set as double the value that is set in ‘Minimum number of idle child server processes’.

Maximum number of connections that will be processed simultaneously: Default 256
This directive sets the limit on the number of simultaneous requests that will be served. Any connection attempts over the specified limit will be queued. Once a process is freed at the end of a different request, the queued connection will then be served.
For virtualized servers it is recommended to set this value at 150. For all dedicated servers the recommended value for this setting is 256.

Limit on the number of requests that an individual child server will handle during its life: Default 4000
This directive sets the limit on the number of requests that an individual child server process will handle. After the number of requests reaches the value specified, the child process will die. When this value is set at 0, then the process will never expire.

ScopServ recommends adjusting the value for this setting to the following:
Virtualized server, 300
Dedicated server with 1-4GB RAM 500
Dedicated server with 4+GB RAM 1000

Read More

How to Manage Schedules

Schedules are used to manage Incoming Lines, Auto Attendants/IVR’s, ACD, Overhead and Multicast Paging Applications, and even Class Of Service objects.

Module 12 - ScopTEL - Managing Schedules
Read More

Introduction to ScopTEL Queues and Agents

Did you know ScopTEL included a FREE Professional Contact Centre?

Presentation ScopServ ACD English V3

 

ScopTEL also includes a FREE Professional Reporting engine

ScopSTATS_Manuel_2016-en-1

 

Need to set up a Call Centre? Refer to this documentation.

Module 15 - ScopTEL - Managing ACD

 

Additional User documentation

ScopTEL ACD Pause Code Usage

 

For additional information on Skills Based Routing refer to https://blog.scopserv.com/2012/06/how-to-implement-skill-based-routing-acd-on-scoptel-pbx/

 

 

 

Read More

How to Configure Outgoing Lines and Interface Groups

This document explains dialing plan configuration for Outgoing Lines.

 

Module 6 - ScopTEL - Interface Groups and Outgoing Lines
Read More

Introduction to PSTN Interfaces and Gateways

FXO/FXS ports, BRI/PRI T1/E1, SIP are all examples of PSTN Interfaces.

These can be card based or gateways or native protocols in ScopTEL.  If you are confused or looking for additional information then  please read this introductory documentation.

 

Module 5 - ScopTEL - PSTN Interfaces and Gateways
Read More

ScopTEL Cisco SIP Phone Integration

ScopTEL Cisco SIP Phone Integration

ScopTEL is able to support Cisco Phone integration by using the ScopTEL Automatic Provisioning System.

Please refer to this document for minimum prerequisite information and additional details.

 

ScopTEL - Cisco SIP Phone Integration
Read More

CentOS 5 Official Support Closure

As previously advised in the ScopServ blogs and ScopNEWS, CentOS 5 has now officially reached its End Of Life date. As a result, CentOS has officially shutdown their official repositories for CentOS EL5.

centoscycle

From now, if you are updating your existing ScopTEL EL5 packages this may cause errors similar to the following:

[root@pstn ~]# scopserv_yum update

==== scopserv_yum ====

— Executing yum…

Loaded plugins: fastestmirror

Loading mirror speeds from cached hostfile

* centos-extras: mirror.netaddicted.ca

* centos-os: centos.mirror.iweb.ca

* centos-updates: centos.mirror.iweb.ca

* scopserv: us.mirrors.scopserv.com

http://mirror.netaddicted.ca/CentOS/5.11/extras/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found

Trying other mirror.

http://mirror2.evolution-host.com/centos/5.11/extras/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found

Trying other mirror.

http://centos.mirror.ca.planethoster.net/5.11/extras/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found

Trying other mirror.

http://centos.bhs.mirrors.ovh.net/ftp.centos.org/5.11/extras/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found

Trying other mirror.

http://centos.westmancom.com/5.11/extras/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 404: Not Found

Trying other mirror.

centos-extras                                                                                     | 2.1 kB     00:00

 

This does not mean your installation is broken, it simply means that the official CentOS EL5 mirrors have been shut down. ScopServ has released a new scopserv-server package that uses vault.centos.org to maintain existing dependencies.  This package will be automatically installed via scopserv_yum update and if the scopserv-server package is updated you will not see this error the next time you do scopserv_yum update.

Here are the options to resolve the error (pick one):

  1. Update your packages using the ScopTEL GUI
  2. From a bash prompt execute ‘scopserv_yum update’ (omitting quotes)
  3. ‘rpm –Uvh http://download.scopserv.com/dist/packages/scopserv-server/scopserv-server-5.1.6.11.20170601-1.nodist.scopserv.noarch.rpm’ (omitting quotes)

Since CentOS 5 is officially End Of Life ScopServ highly recommends that you upgrade your installation to CentOS 6.

A failure to do so will put your installation at risk since CentOS EL5 is no longer supported.

Please follow the official instructions to upgrade your installation at

https://blog.scopserv.com/2016/12/scoptel-centos-6-x-bootdisk-installation-guide/

ScopServ will not be responsible for any liabilities caused by a failure to upgrade to a supported Operating System.  Additionally, ScopServ will be announcing an End Of Life date for ScopServ EL5 packages and support in the near future.

Read More

Avertissement Produit – Migration obligatoire du journal des files d’attente suite à la mise à jour de ‘scopserv-reports’ et ‘scopserv-realtime’ de la version 5 à la version 6 

Très Important

  • Les paquetages ‘scopserv-reports’ et ‘scopserv-realtime’ version 5 utilisent une méthode de transport plus ancienne et un fichier texte queue_log pour générer des rapports téléphoniques alors que ceux de version 6 sont hautement optimisés; nouveau transport par WebSockets et traitement des données ACD dans des tables SQL.
  • Mettre à jour les paquetages ‘scoperv-reports’ et ‘scopserv-realtime’ de version 5 vers la version 6 nécessitera l’exécution manuelle d’un script de migration du journal des files d’attentes sinon les nouvelles données pourraient ne pas être traitées.
  • Référez-vous immédiatement au bulletin ci-dessous avant la mise à jour des paquetages ‘scopserv-reports’ et ‘scopserv-realtime’ prévue le 31 janvier 2017.
  • Il est fortement recommandé de redémarrer votre serveur afin d’éviter des fuites de mémoire après avoir effectué une mise à jour des paquetages!
ScopTEL-scoptel-reports_scopserv-realtime_Release-5to6-queuelog_migration_fr

 

Read More

ScopTEL Version 5 to Version 6 scopserv-reports scopserv-realtime post upgrade mandatory Queue Log Migration Product Bulletin

  • Importance HIGH!
  • Official Release date is January 31st 2017
  • ScopServ scoptel-reports and scoptel-realtime release 5 packages use an older transport method and a flat queue_log file to generate Telephony Reports while the release 6 versions are highly optimized using a new WebSockets Transport and process raw ACD data to SQL tables.
  • Upgrading scoperv-reports and scopserv-realtime release 5 packages to release 6 scopserv-reports and scopserv-realtime packages will require you to manually execute the Queue Log Migration script else post upgrade reporting data will not be processed!
  • Please refer immediately to the this official Product Bulletin prior to the scopserv-reports and scopserv-realtime packages release date scheduled for January 15th 2017.
  • It is highly recommended you reboot your server to kill processes which might leak memory after updating the packages!
ScopTEL-scoptel-reports_scopserv-realtime_Release-5to6-queuelog_migration-el56
Read More