Connecting 3cx to existing PABX

[za-shic]

We have a customer with an Alcatel Lucent OmniPCX PABX and they want to migrate to a 3CX. However they intend doing this in stages until all users are accommodated on the 3CX.
The OmniPCX has 4 x E1 PRI links (2 for incoming, 2 for outgoing traffic). Once all users are are on the 3CX, the E1 links will be transferred across to the 3CX.
How can we link the 3CX to the OmniPCX to ensure a reasonable level of transparency between the two systems during the interim period?

Any help will be appreciated.

Mail [email protected]

 

[leejor]

About all you can do, is allow calls (in a limited manner) between the two systems. You can't share trunking, as it's not possible , with PRI, to have access to/from both PBX's. Even passing calls between the two, requires that the old PBX has Analogue phone lines ( OR sip VoIP).

You will probably have to do all of your testing, get the bugs worked out, connect and test the PRI's during "off" hours when they can be removed from the current PBX, and then, at some point, do a "flash' cut, perhaps on a Friday night. Test over the weekend but leave the current system in place, if major problems arise come Monday morning.

 

[jasit]

actually if you look at the patton smart nodes 4970 4 port you can work with Patton support to setup dial rules between the two systems, you will need to use a cross over cables (not Ethernet, but ones for pri ports).

 

[leejor]

Something you have to consider if you can share trunks, how do you transfer a call from one PBX to the other, if needed. If people have two phones on their desk, most will continue to use the older set as it is more familiar, and "just easier".
If you make use of voicemail, messages could be on either system.

I've found that it is a lot less confusing, to "go cold turkey" after everyone is familiar with use of the new sets, and feature operation, and you have done extensive testing during off hours. Put the old phones under the desk (out of sight) just in case, you have to cut back, hopefully not.

 

[craigreilly]

.

 

[RichardCrabb1]

Connecting PBX’s to 3CX is something that we have done a few times now, and it is possible. Essentially there is an ISDN gateway that will connect the ISDN lines, the ISDN PBX and the SIP 3CX. DDI numbers are mapped at the gateway either to 3CX or to the OmniPCX, dependant on whether the extensions sit on 3CX or OmniPCX. Calls from 3CX to OmpniPCX are made via a “bridge” to the gateway, and then hence to the OmniPCX. In the other direction a gateway is configured on the 3cx for calls from OmniPCX to 3CX. The CLIs will be incorrect to map with extensions on 3CX, and each DDI needs to be setup. What we did was to setup a short code on the ISDN PBX to call the 3CX, but use this as a diversion so a given extension could be diverted to 3CX by using the DDI configured on the 3CX gateway. So for example a user dials 2310 on the OmniPCX, and it diverts to a DDI on the gateway of 3CX. The phonebook is used to match numbers to internal extensions.
Is that of some help?

Kind regards
Richard Crabb

dorsetphonesystems.com
(Crabb Consultants Ltd trading as Dorset Phone Systems)

Direct: 01935 804102
Office: 01935 808094
mob: 07830 818929

Wickham Farm
Marston Magna
Yeovil
Somerset
BA22 8DT