Installation and Configuration Notes

You will have been provided with a babyTEL demo key by Copia Sales, or have obtained a demo key independently.  Before you start, please check your machine and network connectivity using the babyTEL SIP Validator.

Please go to the following web address and copy an paste the demo key in the field

The steps needed at that web page are as follows:

Answer the questions and pick a telephone number. If this is an outbound only system, pick a number in MA Boston area code 617.

When you have completed the forms you will get an email with your web login password and a Activation code.

Log in at and set your web password. You should now have a phone number, account number, activation code and web password. Activate the account and you will have to enter information for the 911 account for this number. Please set the info so if Fire and Police get a 911 call they know that the number is computer controlled and you are the contact to fix the call being created by the system (should not happen).

Once you have completed the activation screens you will be able to run "OTFCONFIG.exe WB".  The WB selects the configuration 'wizard' for babyTEL.  For details, see the OTFCONFIG topic.  The following steps are needed in OTFCONFIG:

Enter the 11 digit phone number and the sip password as displayed

Right Click the SIP Address and select the machine's IP

Right Click the Media Address and select the machine's IP

Right Click the External IP and select the public IP for this machine

Press update Profile. you should get a positive message.

You can now visit the faxfacts.cfg, testreg.cmd, testsend.cmd, and testrecv.cmd tabs and Save each one.  On the testreg.cmd tab you can save and test. If the test is not successful please contact babyTEL support (877-258-8647,514-201-6550) and they will be able to work with you.

The babyTEL configuration also requires the variable OTF_USE_SIPTO to be set in FAXFACTS.CFG for DID/DNIS support. The OFTCONFIG wizard for babyTEL adds this variable.

If you wish to set a ANI (caller ID) for outbound babyTel calls which is different from your account telephone number, you will need to contact babyTEL support (at the numbers above) to request this option to be set on your account.  They will send you a form to be completed and returned which confirms that you accept their conditions for this option.

Once registration to babyTEL is successful you should be ready to use CopiaFacts FoIP.

Frequently Asked Questions

Should I place CopiaFacts behind a Firewall?

Yes. Placing it behind a firewall will help secure it against unauthorized access.

Can a Firewall interfere with proper SIP connectivity between CopiaFacts and babyTEL?

Yes. Under certain conditions, firewalls can interfere with SIP connectivity. Fortunately, these conditions are the exception and not the rule and are typically avoided by making minor adjustments to the firewall settings.

What type of problems might be caused by a Firewall?

Problems related to firewall settings range from the inability to make or receive calls to not getting any fax connection during the call. Depending on the settings of a firewall, different problems can occur.

What kinds of firewall settings cause problems?

Below, we list three types of firewall settings that must be avoided. If unsure of how to make the recommended changes, refer to the firewall help or contact your firewall provider for assistance.

Inconsistent NAT: Firewalls that do not use a Consistent NAT can block incoming calls. In this situation, the firewall keeps changing the public IP port used to communicate with babyTEL. If a call arrives at that moment, before the SIP device re-registers thus notifying babyTEL of the new IP port, then that call will not reach CopiaFacts. To avoid this, change your firewall setting to enable Consistent NAT.

SIP Aware Firewalls: SIP-aware firewalls can prevent calls from reaching CopiaFacts. If this is the situation, disable the SIP awareness option on the firewall.

Strict Firewalls: In the case of very strict firewalls, such as the ones allowing traffic only on limited well-known IP ports, your calls may be blocked. Modify the rules to allow UDP packets to and from and to ensure incoming packets are redirected.

Firewall Considerations

In most cases, you can use CopiaFacts with babyTEL whether it is placed in a public domain or privately behind a firewall.

Where a firewall is in place, the overall quality of service should not be affected provided the firewall can handle the extra traffic without degrading throughput and introducing significant latency. The other important factor is that the Network Address Translation (NAT) functionality of the firewall must use a Consistent NAT behavior model.

With Consistent NAT, outbound UDP, traffic is consistently assigned the same remapped public IP address and public UDP port pair to each internal private IP address and private UDP port pair. Without Consistent NAT, the remapped port could change from the time CopiaFacts sends a REGISTER message to babyTEL and the time it needs to send the next one. This provides no consistency, and no predictability as to where babyTEL should send an INVITE for a new incoming call.

Unless Consistent NAT is used, a problem may happen where a port change takes place and a call happens at that moment, before babyTEL is notified of the new port number. In this situation, the call will not get to CopiaFacts because babyTEL will have sent the INVITE to the wrong port and the firewall will ignore it.

To ensure this problem does not happen, change the firewall setting to enable Consistent NAT.

If unsure, check with your firewall provider for information on how to accomplish this.

If you have a strict firewall, you will need to open some ports. See example below:

In the above example SIP ports XXXX and port TTTT will be 5060 in most cases. Also RTP ports range YYYYY-ZZZZZ will be equivalent to port range UUUUU-VVVVV, although ports used are dependent on your device and firewall configuration.

In, X should have the value provided with your account.


Source Ports


Destination Ports




CopiaFacts IP address

XXXX (device /configuration dependent, often 5060)



Inside to Outside


CopiaFacts IP address


(CopiaFacts /



10000 - 65535

(RTP / T.38) / UDP

Inside to Outside



CopiaFacts public IP address

TTTT (CopiaFacts /configuration dependent, often 5060)


Outside to Inside


10000 - 65535

CopiaFacts public IP address


(firewall /


dependent, often

equal to YYYYY - ZZZZZ)

(RTP / T.38) / UDP

Outside to Inside