Virtualization

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

ScopTEL CentOS 6.X BootDisk Installation Guide

  • Previous versions of ScopTEL were either based on CentOS versions 4 or 5
  • However these versions have limited lifecycle support and it was necessary for ScopServ International to Release an installation ISO based on CentOS version 6.X

centoscycle

  • Refer to the official ScopServ Documentation to install CentOS el6
ScopTEL-CentOS6_-BootDisk-Installation-Guide
Read More

How to Configure Server to Server SIP Trunking

Server to server SIP trunks are very useful and easy to configure.

DNIS is used to send and receive calls between servers

Usage Cases Implementing DNIS:

  • SIP TIE trunks:
    • A private network is created to dial extensions between systems using Access Codes
  • Tandem Dialing:
    • PSTN resources available to a remote server are shared to the local server
  • PSTN re-routing to a networked ScopTEL Server
ScopTEL - How to set up a Server to Server SIP Trunk
Read More

How to Install a ScopTEL Virtual Machine Into the Mediatrix Sentinel SBC

The Mediatrix Sentinel appliance is a Gateway Appliance with several advanced
features (some of which are activated by licensing).
• Eight Gateway modules are supported per Sentinel and external Gateways are also
supported.
• FXO/FXS modules supported
• ISDN modules supported
• DSP modules are supported for RTP CODEC support.
• Hardware transcoding is not yet supported
• SBC is supported by license. Licensing is per channel based
• Embedded Firewall
• Embedded Router supporting static routes
• Enbedded NAT Router
• Embedded DHCP server
• VLAN Support
• QoS support
• 2 Network interfaces (Uplink, Lan1) with each interface supporting a unique MAC
address for bridging to Virtual Machine network interfaces.
• 1 dedicated network interface for emergency management
• Additional Information is available on the Mediatrix Wiki
http://wiki.media5corp.com/wiki/index.php?title=Category:Mediatrix_Sentinel

ScopTEL - Mediatrix Sentinel ScopTEL VM Installation
Read More

How to Configure a Mediatrix ISDN Gateway with ScopTEL

ISDN Gateways are very practical for adding ISDN interfaces to the ScopTEL server when SIP trunks are not used but additional features can be added to Legacy PBX’s using ISDN Gateways and leveraging ScopTEL to:

  • Add or replace existing voicemail servers
  • Add conference bridging
  • Add ACD (Automatic Call Distribution/Contact Center)
  • Add CDR (Call Detailed Reports) via ScopSTATS
  • Add Contact Center Reporting via ScopSTATS
  • Add Call Recording via ScopSTATS
  • Add VoIP phones and other mobility features
ScopTEL - Mediatrix ISDN Gateway Configuration
Read More

Unable to boot ScopTel on Hyper-V after installation

ISSUE

After the installation is complete, the virtual machine reboot and crashes with a Kernel Panic during the loading process.

 

ERROR

 Scanning logical volumes

Reading all physical volumes. This may take a while...
No volume groups found
Activating logical volumes
Volume group "VolGroup00" not found
Trying to resume from /dev/VolGroup00/LogVol01
Unable to access resume device (/dev/VolGroup00/LogVol01)
Creating root device.
Mounting root filessystem.
mount: could not find filesystem '/dev/root'
Setting up other filessystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init!

 

SOLUTION

Add the original ScopTel ISO, as a DVD drive in Hyper-V.

Boot the Hyper-V system, and at the boot prompt, type “linux rescue”.

Follow the prompts to mount the existing ScopTel installation, and get to the shell.

Run the following command to make the installed system the root (/) environment:

chroot /mnt/sysimage

 

 

View the contents of the /etc/grub.conf file to note the exact version of the installed kernel, which will be used in the next command:

cat /etc/grub.conf

 

 

Run the following command, replacing “VERSION” with the version you noted from the output of the grub.conf file:

mkinitrd /boot/initrd-VERSION.el5.img VERSION.el5 --preload hv_storvsc 
--preload hv_vmbus --preload hv_utils -f

 

For example, if the grub.conf file noted that the kernel was “/vmlinux-2.6.18-348.12.1.el5,” the version number is 2.6.18-348.12.1. The mkinitrd command would then be the following:

mkinitrd /boot/initrd-2.6.18-348.12.1.el5.img 2.6.18-348.12.1.el5 --preload hv_storvsc 
--preload hv_vmbus --preload hv_utils -f

Type “exit” twice to reboot, and your system should boot normally

Read More

Installing the ScopTEL packages on OpenVZ

Installing ScopTEL IP PBX on  OpenVZ

The ScopTEL PBX software has an unique problem when you are trying to set it up inside an OpenVZ Virtual Machine. If you install ScopTEL PBX and run the registration program it will fail. That’s because the registration process requires that it has access to the MAC address on eth0 in order to work. But there is a way around it. You can make the eth0 device appear within the VE as follows:

[note color=#ddd]vzctl set $VEID --netif_add eth0 --save[/note]

This command build a line in your OpenVZ configuration file that looks like this:

[note color=#ddd]NETIF="ifname=eth0,mac=XX:XX:XX:XX:XX:XX,
host_ifname=veth101.0,host_mac=YY:YY:YY:YY:YY:YY"[/note]

Initially the values of eth0 (XX) match the Ethernet hardware card and the values of veth101.0 (YY) is random. The important point is that the XX values is the MAC number that ScopServ will see when you register your application.

You can check your virtual device from within the VE as follows:

[note color=#ddd]ifconfig -a

eth0      Link encap:Ethernet  HWaddr FF:12:34:56:78:90 
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)[/note]

When you see the eth0 device in your Virtual Machine and are happy with the MAC number then you can go ahead and register your application and it will actually work.

 

This article is based on informations available from http://openvz.org/Asterisk_G729

Read More