• V20: 3CX Re-engineered. Get V20 for increased security, better call management, a new admin console and Windows softphone. Learn More.

Bridging 3CX with an Asterisk PBX

Status
Not open for further replies.

NickD_3CX

Community Manager
Silver Partner
Advanced Certified
Joined
Jun 2, 2014
Messages
5,572
Reaction score
1,976
Bridging a 3CX Phone System with an Asterisk-based PBX has been a topic of discussion on our forum and on other forums for quite some time now, so we decided to have a closer look at it to see indeed if it can work, and if so, how to get it working.

After some testing we released a sample guide on how we got this to work and published it here:
http://www.3cx.com/docs/bridging-asterisk-pbx/

The purpose of this forum topic is to discuss the guide we published in the link above, as well as share any remarks, improvements or questions regarding it with the rest of the 3CX community.
 
Hi Suggest in case 3CX is connected on ISDN with DDI , manage astersisk to send correct callerid to 3cx for correct mapping out Callerid

Set(RPID="${CALLERID(name)}" <sip:${CALLERID(num)}@ipasterisk>)
SIPAddHeader(Remote-Party-ID: ${RPID}\;party=calling)
 
Can we bridge 3cx PBX to remote site with Asterisk PBX over VPN?

Have it been tested and documented?

Bora
 
I didn't test it but I don't see the reason why it should not work, all you have to make sure is that each PBX can reach the other PBX...
 
3cxBora said:
Can we bridge 3cx PBX to remote site with Asterisk PBX over VPN?

Have it been tested and documented?

Bora

In case of VPN you don't need anything else already documented. In case of traversing over NAT some ports need to be forwarded to the 3CX Phone System which are 5060 UDP and 9000- 9255 UDP. No further config on the PBX end is needed as it will detect that the destination is a public host and will adapt its contact to it accordingly.

On the Asterisk side some change might need to be made to use the public IP in sip:contact and sdp:connection and also a nat needs to be in place. Which ports however are based on the version / type of the asterisk based system, so we can not document this.
 
donbru01 said:
Hi Suggest in case 3CX is connected on ISDN with DDI , manage astersisk to send correct callerid to 3cx for correct mapping out Callerid

Set(RPID="${CALLERID(name)}" <sip:${CALLERID(num)}@ipasterisk>)
SIPAddHeader(Remote-Party-ID: ${RPID}\;party=calling)


Hi,

tried the above mentioned, however, it is still showing my extension number instead of RPID or PAI:(

same => n,Set(CALLERID(num)=${msisdn})
same => n,Set(CALLERID(name)=${msisdn})
;same => n,SipAddHeader(Privacy: id)
same => n,Set(RPID="${CALLERID(name)}" <sip:${CALLERID(num)}@192.168.27.30>)
same => n,SIPAddHeader(Remote-Party-ID: ${RPID}\;party=calling)
same => n,Dial(SIP/99999@99999,16)
same => n,Dial(SIP/3cx-out/402,20)


on local extension 99999 all is correct, the mentioned callerid is presented, however on 3cx extension 402 we receive callerid as 101.

Can you suggest something?
Br,
artsx
 
Status
Not open for further replies.

Getting Started - Admin

Latest Posts

Forum statistics

Threads
141,627
Messages
748,923
Members
144,741
Latest member
Boykins_54
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.