3cx v15.5 - act as MASTER BRIDGE for an old PBX?

[ANJOTI]

Hi,

we have a customer who is implementing (99% finished) 3CX on the main office but many branch-offices has a small and old PBX (analog) today running E1 phisically (R2D/ ISDN/ T1) from TELCO and we are concentrating a new E1 30ch (SIP) on the 3CX at the main office.

These old PBX at branch-offices can talk SIP and here come a question:

- Could we set a 'SIPTrunk' on the old PABX pointing to 3CX IP at the main office? Should we just create an extension? But if so, can this extension handle multiple calls coming from old pbx at branch office (and vice-versa)? Or should we use another option?

Keep in mind that 3CX and old pbx should co-exist for a while (01 year or more for each branch-office) and the main goal is keep all sites able to dial to main office and share E1 rates when dial out.

 

[eddv123]

Interesting.

Now normally based on a standard analogue PBX I would say no:

https://www.3cx.com/community/threads/sip-trunk-to-analog.55257/

But if it has VoIP capability then you have a much better chance of achieving this. And I think a SIP trunk would be the way to go.

Can you provide more information as to it's VoIP/SIP capabilities? Does it have a VoIP card in built or something like that?

 

[ANJOTI]

Hi @eddv123,

tks for you time and answer this thread; now should we add a 'SIPTrunk' on the 3CX server side and pointing it to old PBX or the reverse??

tks a lot

 

[eddv123]

Can you provide more information as to it's VoIP/SIP capabilities? Does it have a VoIP card in built or something like that?

Can you answer my last. This should just be a simple SIP trunk to the other end, however I don't know what is at the other end, please advise.

 

[ANJOTI]

Hi @eddv123 I still havent this info, I will talk with IT team on the branch-office to get more infor about the old pbx.

* As my understanding, we should add SipTrunk at 3CX server side.

 

[eddv123]

Most likely yes that is all that would be required but you want all these details first. One thing I have learnt from installing onsite is never assume anything and always check.

 

[ANJOTI]

for sure, tks for advice!

 

[leejor]

If the other PBX can register to a SIP provider, then create a Master Bridge trunk in 3CX, and use this as a guide...

https://www.3cx.com/docs/

 

[ANJOTI]

Hi @leejor,

tks for quick reply, as we know that other PBX can use a SIP card to talk up to 04 ch simultaneous.

Sorry but description is only in PT-BR and I will try to translate here:

VoIP card 04ch
##############
This card made available communications using Voice over IP

Technical Details
##############
- Support 04 SIP VoIP authentication
- Support 11 extensions registering to 01 SIP server
- Protocol SIP (Session Inition Protocol)
- CODECS: G.711 lei U, G.711 lei A, G.723, G.726 and G.729
- status LEDs.
- Set up using PC software

 

[ANJOTI]

Sorry to be a 'novice', but in that way the old pbx can talk/dial simultanously 04 or 11 ch?

 

[leejor]

- Support 04 SIP VoIP authentication - Support 11 extensions registering to 01 SIP server

I'm not familiar with the particular hardware so anything i say, is speculation. This information would not appear to not be be a hardware limitation (number of channels per trunk) but how many "fields" of information (trunks, or extensions) can be created, or are supported by the software, associated with the card.

You may very well be limited to four concurrent conversations, or, with one registration (to 3CX) you may be able to have more than four. You probably won't know until you try and set it up.