Private Branch Exchange (PBX) has been a critical part of business communication for decades. They serve to share resources, specifically telephone lines, without having to install a separate line for each employee and for each desk. The term PBX may sound old-fashioned, but companies still use it as the backbone of their voice communication.

The basic structure of PBX consists of lines and stations. The lines are only connections to the traditional telephone network provided by a provider. Stations are the endpoints of those lines, such as telephones, faxes, or dataphones. Without PBX, the company would have to contract and install a separate line for each station, and calls between users in the same office would be charged as local calls as if you were calling to another point in the same city.

The PBX system serves the company so that all users can share telephone lines and thus save costs and be able to make free internal calls by dialing an extension number. With a PBX, instead of one line for each user, you can buy as many lines as simultaneous calls are going to be made. 

That is: if there are 200 employees but no more than 10 people are going to call at the same time, they can share 10 lines. Without PBX it would be necessary to contract one line per user. Thus the number of lines to buy depends on the needs of the business, the volume of calls, etc.

PBX was a huge solution to companies. Just imagine you have to promote 1,000 telephonic lines to people to reach the person they need to talk to. It’s impossible.

With modern technology, enterprises are not forced to have obsolete hardware over time, becoming in a cycle of administration problems that never end. As the problem rises more and more with rigid PBX, these modern systems allow companies to have virtual PBXs as software.

What are the challenges enterprises have with the traditional PBX process?

  •  Enterprise communications present unique challenges with a large deployment over geographically dispersed areas and locations, complex company infrastructures, and demand for the highest standards of quality, security, and reliability.
  • A highly manual and tedious process with a clear possibility and expected opportunity for human error. Especially when it comes to massive geographical locations.
  • Functions in PBX and Teams/S4B have varying requirements and infrastructure like AD, making the process and mapping complex.
  • Continual adjustments and tweaks in PBX configuration from the original intent, making the process, and mapping difficult.
  • Capabilities in PBX and Teams/S4B are different in name and action, making the process and mapping convoluted.

The 10 steps to migrate your Traditional PBX to Teams/S4B using Asignet’s patented Robotic Process Automation

  1. Geolocalize all buildings

By geolocalizing all buildings we are able to tie addresses to buildings and them to cities. This is important because all the reports made for any flaws are instantly recognizable by its location in seconds.

  1. Tie the WAN routers to the buildings to report each IP address router and in which building is located.
  2. Scan the routers and all devices connected to them

By the use of our patented RPA technology, the robot scans and reads all the configurations through the network the routers, access points, switches, laptops, desktop computers, voice gateways, and servers, to memorize the information and put it into the extended CMDB. The most critical information is the LAN IP ranges of the buildings.

  1. Scan all the existing PBXs, gateways, trunks and extensions

The robot scan all the existing IP PBX like Cisco Call Manager and TDM like Nortel/Avaya in these locations, and also if Teams/S4B exists. Then we tie the IP devices.

  1. Scan the domain controller user login activity

The robot scan LDAP -the domain controller user login activity- to identify which user works in which building base on LAN IP ranges. The objective is to know which user in the building we are going to migrate.

  1. Control the Traffic and Active Devices in Routers and PBXs

The robot collects the SNMP information from WAN routers and CDR information from PBXs to identify active devices, consumption, and traffic.

  1. Scan to identify existing user licenses

The robot scan the Office 365 licenses and Teams/S4B infrastructure to identify the existing user licenses, which ones are available, and will assign the licenses to the corresponding people.

  1. Tie the area code to each building

We tie the area code to each building to allow identifying the dial plan for each user. Not an easy task out of the US, as they use different “dialing plans” (different number of digits depending on the city) so customization by the city is mandatory.

  1. Map the existent user DID and actual voice policy from PBX

We obtain the user DID from PBX and actual voice policy from the Extended CMDB to migrate to Teams/S4B through the robot scan.

  1. Migrate the user of each building to Teams/S4B

We migrate the user of each building to Teams/S4B partition automatically impacting Teams/S4B platform and AudioCodes SBC (if necessary) and then send a Welcome email to the user and video training to learn how to use the platform.

About Asignet

Asignet is the technology and automation leader of Telcom & IT Lifecycle Expenses Management utilizing its patented RPA Robot process automation platform. The Asignet platform builds and monitors telecom, SaaS, Cloud, IT billing, inventory, and usage, helping global enterprises to optimize, secure, and manage all IT assets and its expenses.

Contact us for more information.