Amatix

Configuration examples

ISDN Extensions

Using the NT operation mode for your HFC-S cards, you can connect ISDN phones to the Amatix InstantPBX. The ISDN phones will operate just like normal extensions.

Here is a configuration example of a HFC-S card used to connect 2 ISDN extensions: 600 and 601

• DEVICETYPE = mISDN
• OPERATIONMODE = NT
• PROTOCOL = P2MP
• OUTMSN = -
• INMSN = 600,601
• FAXMSN = -
• CONTEXT = std-extension
• PREFIX = -

The configuration line of the HFC-S card in the amatix.conf file should be:

mISDN NT P2MP - 600,601 - std-extension -

Direct Inward Dialing (DID)

The P2P ISDN line provides the Direct Inward Dialing facility. In order to use the DID, the protocol of the ISDN controller should be "P2P" and the context "in-did". The Outgoing MSN configuration parameter should be filled with the base number. If your Telco sends only the DID numbers (without the base number), the Outgoing MSN parameter should be set on "-".

Here is a configuration example of a HFC-S card used to connect to the P2P ISDN line having the base number 12345 :

• DEVICETYPE = mISDN
• OPERATIONMODE = TE
• PROTOCOL = P2P
• OUTMSN = 12345
• INMSN = *
• FAXMSN = -
• CONTEXT = in-did
• PREFIX = -

The configuration line of the HFC-S card in the amatix.conf file should be:

mISDN TE P2P 12345 * - in-did -

The "12345-XXX" number will be routed to the extension "XXX". The "12345-0" number will be routed to the "incoming" context.

Outgoing prefix

In order to explicitly select a trunk for the outgoing calls, you should use the trunk's PREFIX configuration parameter. The prefix should be carefully choosed to not overlap the existing dial patterns.

Here is a configuration example of a ZAP card used which routes the numbers starting with "*1" :

• DEVICETYPE = ZAP
• CONTEXT = incoming
• PREFIX = *1

The configuration line of the ZAP card in the amatix.conf file should be:

ZAP incoming *1

The dialed "*123456789" number will be routed through this card to the destination number "23456789" .

Fax (incoming)

In order to receive faxes, you can use the "in-fax" context or define the MSNs asscociated to the virtual FAX machine.
The faxes are stored in TIFF format and can be managed here using a web browser.

Here is a configuration example of a Fritz! PCI card used to receive faxes. By setting the context to "in-fax", all incoming calls arriving on this controller will be sent to the virtual FAX machine.

• DEVICETYPE = CAPI
• OUTMSN = 0
• INMSN = *
• FAXMSN = -
• CONTEXT = in-fax
• PREFIX = -

The configuration line of the Fritz! PCI card in the amatix.conf file should be:

CAPI 0 * - in-fax -

If you want to use your controller for both voice and fax, the defined context will be used to route the voice incoming calls and you have to define the MSNs associated with the FAX. All incoming calls that match the FAXMSNs will be sent to the virtual FAX machine.

Here is a configuration example of a Fritz! PCI card used to receive voice calls and faxes. The calls having the destination "600" and "601" will be routed to the "incoming" context. The calls having the destination "602" will be routed to the virtual FAX machine.

• DEVICETYPE = CAPI
• OUTMSN = 0
• INMSN = 600,601,602
• FAXMSN = 602
• CONTEXT = incoming
• PREFIX = -

The configuration line of the Fritz! PCI card in the amatix.conf file should be:

CAPI 0 600,601,602 602 incoming -

Email Notification

The owner of a mailbox will be notified by email when a new message is stored in the mailbox. This feature will be activated by setting the EMAIL configuration parameter.

Here is a configuration example for the SIP extension "700":

• DEVICETYPE = SIPEXTEN
• NUMBER = 700
• NAME = Intern-700
• EMAIL = user@example.com
• PASSWORD = 1234
• CODECS = alaw,ulaw
• DTMF = rfc2833
• NAT = no
• CONTEXT = std-extension

The configuration line of the SIP extension in the amatix.conf file should be:

SIPEXTEN 700 Intern-700 user@example.com 1234 alaw,ulaw rfc2833 no std-extension

The email notification will be sent to user@example.com.

SIP extensions behind NAT routers

The SIP extensions behind NAT routers should know the external IP address of the router. If they are not able find out the router's external IP address (for exmaple using STUN), the NAT configuration parameter should be set to yes.

Here is a configuration example for the SIP extension "700":

• DEVICETYPE = SIPEXTEN
• NUMBER = 700
• NAME = Intern-700
• EMAIL = user@example.com
• PASSWORD = 1234
• CODECS = alaw,ulaw
• DTMF = rfc2833
• NAT = yes
• CONTEXT = std-extension

The configuration line of the SIP extension in the amatix.conf file should be:

SIPEXTEN 700 Intern-700 user@example.com 1234 alaw,ulaw rfc2833 yes std-extension

NAT router

If the PBX is behind a NAT router and the SIP extensions or trunks are out of your local network, the NAT configuration parameters must be set.

Here is a configuration example for a NAT router having the external IP address "80.90.100.110" and the local network "192.168.1.0/255.255.255.0" :

• DEVICETYPE = NAT
• EXTERNIP = 80.90.100.110
• LOCALNET = 192.168.1.0/255.255.255.0

The configuration line of the NAT router in the amatix.conf file should be:

NAT 80.90.100.110 192.168.1.0/255.255.255.0

NOTE: If RefreshSip service is running, the NAT settings are configured by the service. You sould first deactivate the service using the SERVICES parameter.

PBX administration password

The password of the superuser may be changed by setting the ROOTPASS configuration parameter with the encrypted password. You can encrypt the password using the mkpasswd command like this:

mkpasswd YOURNEWPASSWORD