Book Image

Building Enterprise Ready Telephony Systems with sipXecs 4.0

Book Image

Building Enterprise Ready Telephony Systems with sipXecs 4.0

Overview of this book

Open source telephony systems are making big waves in the communications industry. Moving your organization from a lab environment to production system can seem like a daunting and inherently risky proposition. Building Enterprise Ready Telephony Systems with sipXecs delivers proven techniques for deploying reliable and robust communications systems. Building Enterprise Ready Telephony Systems with sipXecs provides a guiding hand in planning, building and migrating a corporate communications system to the open source sipXecs SIP PBX platform. Following this step-by-step guide makes normally complex tasks, such as migrating your existing communication system to VOIP and deploying phones, easy. Imagine how good you'll feel when you have a complete, enterprise ready telephony system at work in your business. Planning a communications system for any size of network can seem an overwhelmingly complicated task. Deploying a robust and reliable communications system may seem even harder. This book will start by helping you understand the nuts and bolts of a Voice over IP Telephony system. The base knowledge gained is then built upon with system design and product selection. Soon you will be able to implement, utilize and maintain a communications system with sipXecs. Many screen-shots and diagrams help to illustrate and make simple what can otherwise be a complex undertaking. It's easy to build an enterprise ready telephony system when you follow this helpful, straightforward guide.
Table of Contents (17 chapters)
Building Enterprise-Ready Telephony Systems with sipXecs 4.0
Credits
About the Author
About the Reviewer
Preface
Glossary

Connecting two sipXecs servers


Two separate sipXecs servers can be configured to be able to dial each other across the Internet or across a WAN.

To enable calling between two (or more) sipXecs PBXs, there are three steps:

  1. 1. Make sure each PBX can resolve pertinent DNS records for the other's domain (SRV if you are using SRV).

  2. 2. Set up an unmanaged gateway on each PBX pointing to the other PBX.

  3. 3. Set up a dial plan used to select the other PBX.

DNS resolution

Each PBX needs to be able to resolve the other server's SIP domain information. The DNS tests described in Chapter 3 must work for the far-side server's domain name.

For example:

sipXecs system 1 has a SIP domain of: boston.xyzcompany.com.

sipXecs system 2 has a SIP domain of: dallas.xyzcompany.com.

  • System 1 must be able to resolve:

    dig -t SRV _sip._udp.dallas.xyzcompany.com
    dig -t SRV _sip._tcp.dallas.xyzcompany.com
    
  • System 2 must be able to resolve:

    dig -t SRV _sip._udp.boston.xyzcompany.com
    dig -t SRV _sip._tcp.boston.xyzcompany.com
    

There...