Needed Hardware for 2600 Extensions

Hardware compatability

Requirements for the project are to find a possible server configuration that should be able to cope with 2600 extensions usage. We must take into account that each extension will use gloCOM and have a deskphone as well.

Since time was a limited resource and the fastest server that we had was the HP DL360 G7, we decided to use that server as a quick testing scenario where we would try to come as close as possible to the technical setup needed for the project. Once we had the minimum needed result numbers, we could now compare to some use cases with our servers and the performance of servers that are new on the market.

G7 specs are as follows:

  • CPU: 2x Intel(R) Xeon(R) CPU L5630 @ 2.13GHz (4 core/8 threads)
  • RAM: 24GB DDR3
  • DISKS: Combined 500GB of space SAS drives
  • OS: Serverware 3.0 with 1 PBXware 5 VPS instance

This server managed to run approximately 750 extensions with a  total of 230 calls, 750 gloCOM connections, 15 SIP registrations per second, and 375 OPTION packets per second. This was all done on one VPS.

Bicom Systems has a production server with about 3700 extensions split between 24 VPSs with maximum number of extensions per VPS at 750. Keeping in mind this server is running older versions of Serverware and PBXware, with much less features than our newly available versions. The configuration of said server is:

  • CPU: 1x Xeon D-1541 with 8 cores
  • RAM: 32GB
  • DISK: 1x 1.6TB SSD
  • OS: Serverware 1.9 with 24 PBXware 4 instances

Now, taking into account the new Xeon CPUs, which perform much better than servers such as the G9 and G10, we came to a possible configuration that will satisfy project needs:

  • CPU: 2x Xeon E5 with 8 cores each
  • RAM: 32GB DDR4
  • Disks: if we consider recording considering you do not go under 1TB, the number of disks would depend on the type of Serverware. We would also recommend a solution with call recordings being stored on a Hard Disk Drive (HDD), while the system and all else that accompanies it be stored on a Solid-State Drive (SSD).

One thing that needs to be mentioned is that we can’t be sure if all of 2600 extensions would be able to coexist on a single PBXware VPS, so it is recommended to start out with one VPS and if you run into issues, split them into other VPSs. This should resolve those issues.

For more information, visit our wiki

Creator Bio:

Eldar Avdic,

UADs & Appliances Manager and Developer. Maintains Bicom Systems’ UAD support and keeping appliances up to date.

Dino Mesic,

UADs & Appliances Engineer and Developer. Develops support for UADs, maintain technical documentation and test new UADs and appliances.

Custom Work: Blink(1)

While requests for customized solutions are common around here, some of them are a little more unique than others. One such request from Fritz Welter at Netinteract was to integrate a customizable call pop-up window in gloCOM. The purpose? To enable call notifications with blink(1), a USB indicator light. (Learn more at https://blink1.thingm.com/about). Interesting.

This was easy enough to do. Blink(1) provides an API that can be reached through the localhost. Any URL can be placed in the call pop-up window in gloCOM, so in this case the user just has to insert the localhost to blink their USB device. gloCOM’s custom URL field opens up endless possibilities to integrate with other third party products like blink(1).

Thanks to Fritz Welter and Netinteract for bringing this to our attention and giving us the opportunity to deliver a solution. With so many customers asking for integration with blink(1), we are happy that Welter can now tell them “yes”.

What about you? What are your customers requesting?

PBXware Now Used in Prisons

Bicom Systems is pleased to announce its business relationship with Wateen Telecom in Pakistan to begin serving prisons.

Wateen Telecom, a converged communications service provider, aims to bring Pakistan into the 21st century and digital revolution.

This case began with a challenge in January of 2014: Wateen needed to supply a telephony system to the inmates of the Punjab Prison System in Pakistan. While similar to a call shop, this situation was unique and had some special requirements and obstacles.

Read about the solution that used PBXware and custom work in our Wateen Case Study.

wateen

WiLogic

Bicom Systems is excited to announce its partnership with WiLogic in California to offer a more advanced and feature-rich VoIP phone system to their customers.

After experiencing rapid growth, WiLogic found themselves in need of a more powerful platform to satisfy customer demands. They found their solution in PBXware.

Since then, WiLogic has obtained and retained more customers than ever thanks to a plethora of VoIP telephony features.

To read more about this business partnership, read our WiLogic Case Study.

Custom Work: IMAP Syncing

imap voicemailAsterisk IMAP Voicemail system too slow? Not a problem!

Our custom workaround speeds things up with one way syncing between the IMAP mailbox and telephone system.

In this solution, voicemails are stored on the file system and monitored for deleted folders or voicemails. As soon as a voicemail is deleted from the email account, it is also deleted from the file system.