Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

1. Introduction

Each PrivateServer can reach outer communication devices using its Trunk feature. This means that it's possible to connect PrivateServer to almost anything out there, if that device talks standards protocols as SIP. The outer communication design can be:

  • FROM the PrivateServer TO the other PBX/Device
  • TO the PrivateServer FROM the other PBX/Device
In the former case we are going to use the "register" feature, in the latter we need less standard configuration. For what it was just written, it's common understanding that out first choice of interest is the first case, thus we configure PrivateServer to act AS A CLIENT and set it up to connect to another PBX/Device via CLEAN SIP over UDP TRUNK.

2. Pre-requisites

There is some pre-requisite to be filled in before we even start configuring. The most important one is the network connection.

2.1 Network

It can sound awful or just pedantic, but it's necessary that both the devices (ie PrivateServer and the other one) can "see" each other, and not just in matters of ICMP Pings, but actually via UDP connection. This because the UDP connection will be the transport mean for the SIP Trunk.

2.1 Number Plan

Also this pre-requisite is often disattended or considered of less importance. This attitude is wrong, because without a clear and stated number plan we can really risk number overlapping which would lead to unexpected call routings and very nasty to debug issues. So please before you start just write down the telephone numbers you are providing to the PrivateServer device to be called and consider the impact of calling secure numbers on your own PBX.

3. Specification

 

4. Conclusions

  • No labels