SIP Migration

An InteropNet Labs white paper.

By nobody, NetworkWorld.com
May 11, 2004 09:42 AM ET

. What's this?

Click to see:

Although many enterprises are eager to adopt SIP, they see their legacy PBX systems as a roadblock to the cost savings and enhanced applications that SIP would bring. This paper outlines how to effectively begin a phased migration to SIP without immediately replacing your existing PBX equipment.

It is basically a four-step process that enables an enterprise to migrate to a SIP based multimedia communications system while leveraging the existing investment in the public switched telephone network and not disappointing an installed based of enterprise users accustomed to a high level of voice quality and an extensive set of telephone options. These steps are:

1. Connecting a SIP Proxy to an existing PBX.

2. Migrating users and phones to the SIP Proxy.

Related Content

3. Migrating your PSTN connection from your existing PBX to a SIP-based one.

4. Retiring the PBX and the legacy phones.

Step 1

Since this is the stage at which many enterprises stand at today, in the iLabs we are demonstrating several different methods you can approach this process. In this mode of operation, the legacy PBX serves as the gateway to the traditional PSTN. To connect from the VoIP network to the PSTN, the SIP proxy routes any PSTN calls (as well as any calls to users remaining on the legacy PBX) over a high capacity connection (such as a PRI ISDN line or a T1 line) to the legacy PBX.

The diagram to the right demonstrates these methods. Initially you'll need to establish a connection from your new SIP-based call manager (or Proxy Server) to your legacy PBX-based call manager. You have several options to make this connection. You can use commercial standalone product, such as a SIP device with FXS/FXO ports or with T1 or PRI ISDN lines. Or, you could use a board-level product that installs directly in a SIP proxy server with T1/PRI or FXO/FXS lines. Or, you may be able to make a SIP-based LAN connection between your SIP network and the legacy PBX with a built-in SIP/Ethernet option for the legacy PBX.

Step 2

Now, begins the migration of existing users and services to SIP. For example, you may first migrate all the handsets to SIP by either using SIP Gateway devices or replacing the phones with native SIP handsets. A mixed approach is also common. For example, users who have "feature phones" might need the native SIP handset to keep their capabilities. Phones that didn't have features before can be easily connected to low or high-density SIP gateways.

You'd then want to begin setting up SIP application servers that can perform some of the important features that previously resided in the PBX, such as voice mail and IVR functionality. Some applications, such as multi-party conferencing or paging, may be more difficult to implement in the world of SIP than with a traditional PBX, so be careful to inventory what people are actually doing to allow enough time.

SIP TERMS

SIP Proxy - The SIP Proxy provides the call routing functionality to your new phones. In this example the SIP Proxy is also functioning as a SIP Gateway to the PBX, although they could easily be different devices.

SIP Gateway - A SIP Gateway (sometimes written as ATA, or analog telephone adapter) lets you use legacy telephones on the SIP network as it converts calls from these phones to SIP. Many enterprises have made large investments in handsets and users tend to get attached to them, so this option provides a nice transition without having to re-educate the end-users. These range from low-density 1-port devices up to devices that connect to 24 or more handsets with a single Ethernet connection.