Bridging a 3CX install with an Altigen installation

[xecunet]

I have a customer who is trying to bridge a 3CX installation with another Altigen installation. We are able to successfully make calls from the Altigen system to the 3CX system, but when calling to the Altigen system from 3CX the call just rings into the auto-attendant and won't ring to an individual extension.

Has anyone been able to successfully make this work? Any ideas on why the Altigen system isn't accepting calls to a direct extension? DTMF works once the Altigen system accepts the call from 3CX, it just doesn't direct the call prior.

 

[leejor]

have you confirmed exactly what digits are being sent/received? Does the other PBX have any sort of log to determine how it is routing the calls and why? What type of trunk is being used at the far end? Does it only handle routing incoming calls to one destination ?

 

[dan_tx]

I've done exactly this. In fact, we switched from Altigen to 3cx and I had them working together for about 6 months while one department tested out 3cx.

You'll want to setup Altigen like a SIP trunk, and 3CX like one as well.

What I had to do, since 3CX and Altigen saw each other as SIP trunks and I wanted people on the 3cx and Altigen side to still be able to still just dial someones extension, was pretty intensive, but worked perfectly once configured.

On the 3cx side, I had a rule that if someone dialed an Altigen Extension, it would go over the Altigen trunk, and add a prefix to the number, say 99. So somebody dialed 1234 on 3CX, it would go over the altigen trunk and make the dialed number 991234.

Then I had a inbound rule on the Altigen side that said a DID for 1234 was 991234.

It sounds like you might need to set this up.

 

[xecunet]

What about hopping off to make external calls? Also, caller ID doesn't seem to be working between the two systems?

 

[dan_tx]

What about hopping off to make external calls? Also, caller ID doesn't seem to be working between the two systems?

I'm not sure what you mean hopping off to make external calls. The 3cx side will use it's sip trunks to make external calls and Altigen will use it's side to make calls. I couldn't get one to go outbound over the other, but also didn't have a need for it so not sure I tried much.

To get caller ID to work on the 3CX side, I added all the altigen Users to the 3cx Contact list, it also made it so the 3CX users could see the extensions for Altigen.

 

[dan_tx]

Oh, also on the 3cx side, to get caller ID to work for Altigen to show who called, I had to put the users Extension in the Outbound Caller ID field. Then on the Altigen sip trunk in 3cx, have that field be the From: User Part.

I don't have the altigen server, but still have the 3cx test server with the altigen sip trunk and user settings. It's our 3cx test server.

 

[dan_tx]

I had to make some rules for push notification to work, basically removed the spaces in the caller ID for inbound from the altigen server.

Source Pattern:
(Bob) (.*)

Replace Pattern
\1\2

Also on the 3cx sip trunk for altigen, I added the DID's used for each extension.

So for example, lets say an employee that was ext 100 in altigen was moving to 3cx. I'd forward their ext in altigen to goto 9100. I'd have a altigen setup that calling 9100 goes over the to 3cx sip trunk in altigen.
On 3cx I'd have a DID for the altigen sip trunk of 9100 goto ext 100 on the 3cx side.