I guess the question is if you are interfacing with a PBX or key phone system on each end.
The way that the calls are routed from one Quintum to another could be bundled in two categories:
1) Stand alone operation: Each gateway operating on its own, and sending calls to the outside based on the “static routes”.That is a table on each gateway that tells the gateway where to send the calls based on the prefix of each call and the I.P. of the far end gateway. Easy to setup, each gateway is independent of the others, but every time that something changes, you need to update each gateway.
2)Use one of the units as the gatekeeper. The remote units “register” to the main unit,or gatekeeper. You make the gatekeeper the routing hub of your small network. Changes and monitoring are done on the gatekeeper.
If the gatekeeper dies, so does your network.
On a private network, with all the units on internal I.P. address, any of the two configurations will work fine.
The only trouble with Quintum is when the remote gateways change I.P. adddress a lot, meaning several times a day , like gateways running on ADSl services.
Start asigning each unit a I.P. address, a mask and a default gateway.
Once you could telnet into each unit, verify data conectivity by telenting into each unit and ‘pinging” the I.P of the other unit.
Once you get to that point, write to my adrress and i will give you more instructions in how to make the first calls betwen units.
Information that you will need:
On the DX2030 T1 or E1 interface.
If T1, it is cas signaling, or PRI??
T1 is ESF , SF, AMI or B8ZS??
If PRI T1, what protocol?? NAtional ISDN is the most comon one.
Connected to PBX equipment or Provider???
On the analog interfaces, do you have analog lines from the phone company or extensions from the PBX equipment???