Telephony

Product Bulletin: Voice Operator Panel is now fully supported by ScopTEL in the Automatic Provisioning System

ScopServ is very pleased to announce that we now fully support Voice Operator Panel in the Automatic Provisioning System.

Minimum software release: scopserv-telephony25-6.9.8.1.20200423

VOP is a very feature rich SIP Softphone with very advanced capabilities including presence, drag and drop, custom directories, CRM integration. VOP is also very easy to mass deploy.

For full product details see http://www.voiceoperatorpanel.com/

Refer to our official documentation:

ScopTEL Voice Operator Panel Provisioining
Read More

How to install ScopTEL on CentOS7

Use this document to install a clean copy of ScopTEL on CentOS7

Module 1 - ScopTEL - CentOS7_-BootDisk-Installation-Guide
Read More

Press Release: ScopTEL Introduces Context Sensitive Help into the Web-GUI

ScopTEL is a constantly evolving product with new features added almost daily.

This constant evolution makes updating documentation very difficult.

So ScopServ is very pleased to announce that we have added Context Sensitive Help to each and every ScopTEL server able to install scopserv-core-6.2.0.2.20200318 and scopserv-server-6.4.0.0.20200318

This package adds the help button to each object in ScopTEL Server, Network, Telephony with the exception of Vendor specific Automatic Provisioning details.

Just click on a help button to launch the help window.

 

Read More

VoIP.ms Interoperability With ScopTEL Announcement

ScopServ International Inc. is pleased to announce their SIP interoperability with VoIP.ms

https://voip.ms/en/company/about

Founded in 2007, VoIP.ms was built by a group of IT and business professionals who believed there was a better way to bring Internet phone services to companies who, like them, had a desire for high-calibre communications solutions.

Being strictly Bring-Your-Own-Device, VoIP.ms does away with the limitations and costly hand-holding that come along with some telephony providers. This allows us to give unlimited focus to maintaining a widely-accessible and feature-rich service.

With offices in Canada, and Mexico, and access points across the globe, VoIP.ms has developed into a truly international business that serves over 75,000 clients, worldwide.

The following documentation includes the interoperability configurations required for ScopTEL to interoperate with a voip.ms SIP trunk.

 

ScopTEL-VoIP.ms_SIP-T_Interop_Requirements

 

Read More

How To Configure ScopTEL with NAT (Network Address Translation)

ScopTEL includes a SBC that does a very good job of handling NAT’d extensions and trunks when the peer supports RPORT.

This article covers the recommended configuration for ScopTEL and NAT.

  • ICE/STUN/TURN are not mandatory and aren’t recommended
  • There are mandatory settings when ScopTEL is not exposed directly to the Internet on its public interface and its sitting behind a third party NAT router. This article does not cover third party router configurations or port forwarding requirements.
  • The default ports used for ScopTEL SIP traffic are:
  • udp/5060 (used for UDP SIP signalling traffic)
  • tcp/5060 (used for TCP SIP signalling traffic)
  • tcp/5061 (used for TLS/SRTP SIP signalling traffic)
  • udp/10000-20000 (used for UDP SIP RTP traffic)
  • tcp/10000-2000 (used for SIP SRTP traffic)

 

ScopTEL - Configuring ScopTEL for NAT
Read More

ScopTEL Reserved Call Parking

  • The purpose of Call Parking is to put a call on hold and resume the call from another extension.
  • Legacy Phone systems used to have what were called Square Line Appearances aka Shared Line Appearances. The point of Square Line Appearances was to assign POTS lines to DSS/programmable keys on a phone. If the POTS line received a call the DSS key would blink to show Ringing and the phone would ring for an audible warning. All phones in such an environment would have the same Line Appearances appearing but not necessarily ringing on their DSS keys. If by example extension 221 answered a call on Line 1 and wanted another extension to pick it up they would press the hold button on their phone and tell another extension to press the blinking held line on their phone to retrieve the call. This pre-dates transfer and was never considered a function of a PBX. PBX’s typically use Trunks like ISDN PRI services or in today’s technology use SIP Trunks. These trunks have no concept of Lines in the way that old POTS lines worked. Call Parking was invented to place a call on hold and resume the call somewhere else without having to transfer the caller to another extension.
  • Reserved Parking in an advanced way to Park calls which is especially useful to break up Call Parking configurations into departments. With Reserved Parking each department gets their own Call Park extension and Parking Lots.
ScopTEL - Reserved Parking
Read More

Managing Tenants

A Tenant is a segregated dial plan Container with segregated Reporting structures. Each Tenant can be regarded as its own Customer container without requiring a unique physical installation for each Customer. This feature allows public IP addresses and FQDN’s and hardware to be optimized and shared for multiple Customers saving money on memory, CPU’s, dedicated storage space, and rack space.

Examples:

  • Extension 100 is required for two customers to exist on the same hosted or CPE installation of ScopTEL without creating a VM Container for each Customer. Each Customer can be regarded as a Tenant. Each unique Tenant|Name can support its own Extension 100
ScopTEL - Managing Tenants
Read More

Configuring BLF for Pickup Groups

Configuring BLF for Pickup Groups

Background and Pre-Requisites for Pickup Groups with BLF lights
A configured Pickup Group puts more than one extension into a Group ID
A Feature Code or the BLF button itself can be used to answer any ringing Extension in the configured Group ID
For each new Pickup Group ScopTEL automatically assigns a Hint (BLF) which can be added as a BLF context to a supported SIP Phone.
This document will explain how to provision a phone to support one or more Busy Lamp Field buttons for Extensions|Pickup Groups
Pre-Requisites:
A phone that supports BLF keys which is also included by https://blog.scopserv.com/2019/04/supported-sip-devices-in-the-scoptelautomatic-provisioning-system/
Not all Cisco phones support BLF so you must reference https://blog.scopserv.com/2017/07/scoptel-cisco-sip-phone-integration/
scopserv-telephony25-6.6.6.0.5.20190520.el6.scopserv.noarch or higher
The following phones support APS BLF Key|BLF|BLF Mode|Pickup Group drop list configuration
Yealink, Astra, Grandstream, Panasonic, Snom
Polycom phones must be configured with either Speed Dial|Buddy Watch|True or BLF with the Extensions|Pickup Groups|Group ID|Hint
(BLF)|<context> manually entered into the Destination/Extension field

ScopTEL - Configuring BLF for Pickup Groups
Read More

How to Manage Automatic Call Distribution (ACD) Queues | Contact Centers

Automatic Call Distribution queues put callers into a queue and typically play Music on Hold or custom announcement messages to keep them informed or relaxed while they wait for an agent to become available.

  • Studies prove that a caller listening to Music on Hold will stay on hold longer than a caller hearing a ring back tone
  • Agents are typically employees of a contact center that login to one or more queues in order to answer callers.
Module 15 - ScopTEL - Managing ACD
Read More

ScopTEL- AdHoc Conference Feature Management

  • ScopServ is very pleased to announce the addition of a new Feature Code known as ‘AdHoc Conference’
  • The purpose of the feature is to allow users with no Admin GUI access to the ScopTEL management interface to create Conference Bridges on the fly.
  • A phone user with access to the AdHoc Conference (Admin) Feature Code by virtue of their extensions’ Class of Service can create virtually unlimited Conference Bridge applications any time one is needed by dialing some codes from their phone.
  • The Admin creator must set the ADMIN PIN code and optionally create USER PIN codes to restrict access to any of their Conference application Extension Numbers.
  • Users Dial the AdHoc Conference (User) Feature Code by virtue of their extensions’ Class of Service then dial the Conference Bridge Extension and the Admin defined PIN code to enter the bridge
  • Anyone with the Admin password of any Conference Bridge extension and a valid Class of Service applied to their extension can use the Conference PIN change Feature Code to quickly change PIN’s on an existing Conference Bridge application
  • The Conference PIN change Feature Code must be carefully safeguarded by Class of Service since it can be used to modify the USER PIN of any existing Conference Bridge application
  • AdHoc Conferences have a limited time to live set to a default of 30 days after which they are automatically deleted.

 

ScopTEL- AdHoc Conference Feature Management
Read More