Q.

How many lines/calls can TerraPBX MediaGateway handle?

A.

The answer depends on: Type of call, system load, system specs, codec translations. However, the maximum amount of lines (a call will use a minimum of two lines, while IVR could use only 1) is currently 512. Which means, around 200-250 calls with PCM audio in and out. For IVR sessions 400 or more IVR calls at a time are attainable.

Q.

How well does TerraPBX scale?

A.

Since routing is handling which TerraPBX to go through, TerraPBX will scale linearly - i.e. each new TerraPBX gives you upto 512 more lines.

Q.

How do I handle incoming DID traffic?

A.

TerraPBX acts as a session border control gateway in this case. You must add the incoming DID provider's IP to the configuration. Also, in order for TerraPBX to treat incoming call as DID translation, you simply mark the IP as DidRouted true in configuration (though, should use configuration tool). Once TerraPBX is handling incoming traffic, you can be assured that this call will not gain system level access, perform external forwards, or other security breaks, as all calls in and out of Terra maintain correct From user.

Q.

Can TerraPBX communicate with other Sip Providers?

A.

Yes. TerraPBX can do Proxy Authentication, you have to setup the gateway in the routing (database) as well as any credentials needed.

Q.

What kind of billing can TerraPBX do?

A.

TerraPBX can handle 1 second or higher call clock rates.

Q.

What IVR systems are possible with TerraPBX?

A.

TerraPBX uses a flexible IVR system which leverages the power, ease of use, and speed of Python Interpreter. The basic built in scripts include: CallingCard, AutoAttendant, CallBack, VoiceMail

Q.

How Do I Install TerraPBX?

A.

Installation

Q.

How do I setup IVR?

A.

First, each TerraPBX is cabable of handling any type of IVR. All that is required is setting up IVR Gateways in routing. Check Routing

Q.

I changed the configuration but it has not taken affect.

A.

Config file gets reloaded every five minutes, or on next restart (depending on type of setting change - i.e. listening IP address will require restart).

Q.

Why would I want to configure multiple database connects?

A.

In case there is any system/network failure during the time Terra is trying to write important records to the database, you will want a backup solution. This backup database could be reachable from a separate NIC, or just a separate server form the main database. The REMWAVE solution is all about redundancy.

Q.

Remwave TerraPBX Service unexpectedly shutdown/crashed?

A.

If for whatever reason, the service failed internally, TerraPBX will write a minidump crash to the C:\ directory. The filename will determine which version of Terra was running that caused this crash. Old reports will get written over. In the future, we hope to set up a quality control agent with various reporting settings (what information to send, where to send, etc). Right now, the minidump contains the Full Process heap for the application. So, will possibly be very large depending on what was happening at the time of failure. This information is vital in helping Remwave locate & correct the issue in a timely manor. Please report the dump and send along the file (as well as any pertinent TerraPBX log files). If the dump file is too big, or you do not wish to give up a dump of the memory, setting the system environment variable: TERRA_MINIDUMP to MiniDumpNormal will cause only a partial dump - which at least gives a little insight into the problem. Note, changing this environment variable will require a system restart for services to pick the change up.

Q.

What does the SipProxy do?

A.

Visit the SipProxy wiki page to find out.

Q.

What OS does Calamar run on?

A.

Calamar runs on every platform where Java VM does. Calamar only needs a decent CPU, medium amount of RAM, and a reliable network. On Windows, REMWAVE has a SipProxy service helper to start/stop/monitor Calamar service. On Linux, we can provide some startup/shutdown init.d scripts On Solaris, we also have SCM scripts available.

Q.

Does the SipProxy scale?

A.

Yes. REMWAVE has developed a UDP SIP load balancer tool which will do load balancing on configured Sip Proxy's. This makes SIP dialog's sticky to go to the same SipProxy, which is essential for branching/forking operations that the Proxy has to do. Currently, the load balancer tool requires all Proxy's and the tool itself reside on UNIX/LINUX systems (due to Window's lacking some useful UDP features) - however, if you need a Window's based solution, you can contact REMWAVE for an estimate on needed work. Please visit ItspAdvancedUsage#LoadBalancing for more information.

Q.

How does Calamar SipProxy compare to other Sip Proxies?

A.

Please visit SipProxy#Comparison page for listing of differences.