G12 Communications and Edgewater Networks on VoIP Migration Strategy for Large Organizations


Phased Adoption Of IP Voice Services for Enterprise, Medical, Government and Education 

For many organizations hosted PBX or SIP trunking services represent a compelling option for updating or extending the life of existing legacy phone systems. These Voice over IP (VoIP) services offer flexibility, cost savings and innovative features that often result in greater productivity and customer service.

Updating an entire organization’s voice and data system in one fell swoop, however, is a daunting and resource intensive undertaking. In making the cutover from the old system to the new one, organizations can suffer a significant impact to revenues should there be any delays or downtime. In addition, disparate locations, hundreds or thousands of employees and many different phone systems add to the logistical complexity.

G12 Communications understands this complexity and offers organizations looking to update their voice system a phased solution that reduces the impact to its business. Using Edgewater Networks’ EdgeMarc Enterprise Session Border Controllers (ESBC), G12 Communications provides a seamless plug and play transition that can be deployed in phases based on customer needs.

Solution Provider

G12 Communications is a cloud-based provider of unified communication services. Serving enterprise-level customers, medical facilities, city, state and county municipalities, G12 is able to customize its communication services to individual customer needs.

Edgewater Networks, a leading provider of Enterprise Session Border Controllers, enables G12’s service delivery. Based on the size of deployment, Edgewater has a suitable ESBC, whether it is the EdgeMarc 250 for small offices, the EdgeMarc 4550 for up to 90 calls, the EdgeMarc 4601 for environments with 200+ individuals, or the EdgeMarc 5300 for 1000+ employees.

Complete Solution 

With the significant investment most companies make in building their existing IP network, replacing the entire infrastructure can be cost prohibitive and unnecessary. However, many VoIP service providers require that customers purchase additional bandwidth or replace existing access links in order to obtain a complete IP voice-based system.

G12 proposes a different approach. Rather than replacing existing IP access links to add voice services, it places an Edgewater EdgeMarc ESBC as a demarcation point on the existing IP network, enabling the delivery of high quality voice services over existing bandwidth.

With this service delivery, G12 is able to offer customers:

• Redundant SIP trunking

• Parallel phone service capabilities

• End-to-end product delivery

• Cloud-based capabilities

• Custom deployments

Edgewater’s EdgeMarc ESBCs are the ideal devices to enable a hosted PBX system or SIP trunking service. The session border controller functionality in each EdgeMarc provides interoperability, call routing, dial plan manipulation and VoIP survivability. In addition, quality of service features such as prioritization and traffic shaping enable business quality voice. The integrated call quality performance statistics also facilitate problem resolution and provide visibility into the quality of service being delivered.


G12 uses a unique customized process that allows organizations to phase in the deployment of IP-based voice services based on availability, resources and demand schedule. This approach is ideal for many customers as it 1) reduces the potential downtime customers may face should there be a problem in the transition from the old system to the new and 2) reduces the impact on resources.

Each customer is assigned a G12 project manager that acts as a single point of contact. Together, the customer and the project manager assess the existing network and


Case Study

bandwidth requirements before working through different deployment scenarios. Once a plan has been agreed upon the project manager works with G12 engineers to deploy the solution.

In most scenarios, the customer will have an old phone system with outdated phones that are connected to a PRI link. As a result of G12’s unique phased cutover approach the customer has decided to move to G12’s hosted PBX service.

The first step in the process is to replicate the customer’s existing phone services so that changes can be made in stages without network disruption. During the replication, G12 will assume control of the DID inventory.

To demonstrate the process, Company X, illustrated in Image A (page X), will be our example. Company X has six PRIs, which are being delivered to a PBX. To replicate the existing system, G12 deploys a central EdgeMarc 5300 at the customer premise, acting as the demarcation point and main enterprise session border controller for the entire system.

EdgeMarc 4601s are then deployed between the EdgeMarc 5300 and the company’s legacy PBX, converting the SIP trunk coming out of the EdgeMarc 5300 into PRIs. Company X is now receiving their PRIs via the EdgeMarc 4601 and their PSTN access through the G12 SIP trunking service.

Once phone numbers are ported using this set-up, Company X’s service appears to the users exactly the same as it did before. The transition to the new system and IP phones can now be customized to the customer needs, depending on how quickly they are able to make the changes. The customer can determine if they want to deploy a single office, department, or a building on their campus.

With full control of the DID inventory, G12 creates a separate SIP trunk to a new IP PBX or G12’s hosted PBX service, using the same EdgeMarc 5300 that was deployed initially. Now the new system is working alongside the old system. All calls coming in will be routed to the appropriate phone depending on whether they reside on the new IP system or the old legacy PBX.


Case Study

At this point, it is a matter of full deployment based on the customer’s needs. Small cutovers of DIDs can be made from the old system to the new PBX in a seamless fashion. During each phase, new IP-based handsets are deployed and shifted off the old system. This “cap and grow” strategy allows the customer to transition to a more fully featured system while continuing to leverage the investment made in legacy equipment until it has reached the end of its useful life.

G12 and Edgewater Networks – Large SIP Trunking/Hosted Deployment Process












Transitioning from a legacy PBX system to a SIP-based environment can be risky, resource intensive, and expensive. However, using a phased approach, the customer can make the change at their own pace and use the savings from those areas that have been deployed to fund the ongoing transition.


Case Study

With G12’s consultative approach in migrating customers to new voice systems, customers are able to customize their deployments based on their unique environments. Depending on the size of the organization or infrastructure demands, various Edgewater EdgeMarc ESBCs can be deployed to fit the needs of the environment.

In the example provided, the customer had a legacy PRI and an EdgeMarc 4601 was deployed in front of the legacy PBX and then connected to the primary EdgeMarc demarcation point. However, if the customer had no PRI requirements, no T1 requirements, or no traditional TDM requirements, G12 would use an EdgeMarc 4500 Series device or an EdgeMarc 5300, to connect directly to the new IP PBX. The EdgeMarc 250W can also be deployed for small office installations.


Whether the customer is an enterprise, medical organization, government entity, or education facility, G12 Communications and Edgewater Networks are able to customize and execute the optimal unified communications strategy.

Company Contact Information

Edgewater Networks, Inc.

2895 Northwestern Parkway

Santa Clara, CA 95051

Phone: (408) 351-7200

Email: info@edgewaternetworks.com

Web: www.edgewaternetworks.com

G12 Communications

93 S. Jackson St. #19390

Seattle, WA 98104

Phone: (877) 311-8750

Email: sales@G12com.com



No comments yet

Leave a Reply

Copyright 2012 - G12 Communications