Avaya to 3CX and 3CX to outside

[Manny783]

We have successfully setup a SIP trunk between Avaya IP 500 and 3CX, and we can call one another extensions without problems.

We would like now to take it a bit further and use the 3CX to dial out outside on behalf of the Avaya IP 500. For example, on our 3CX we have an outbound rule by which any number starting with 3 goes outside. We have configured a short code in the Avaya that sends a 3 + a mobile number to the 3CX, but the problem is that the 3CX does not send it outside, it just sees the call coming from the trunk with the 3 in front and does not send it outside

Any way of achieving that? Any help would be much appreciated!

 

[Wendelspanswick]

Hi Manny

See this:
https://www.3cx.com/community/threa...ia-another-different-trunk.59089/#post-248234

and

https://www.3cx.com/community/threa...-3rd-party-pbx-via-the-3cx.60477/#post-255270

 

[leejor]

Why does it fail? Check the 3CX Activity Log, on the incoming bridge call. Perhaps all digits are not being sent, or there are restrictions on the outbound rules so they cannot be used.

 

[Manny783]

No, no, when the connection Bridge between Avaya vs 3CX everything works fine, but unfortunately we need to use a "SIP trunk" and not a Bridge

Thank you so far for all your great answers!

 

[Manny783]

As you all know, in a SIP trunk you only have the options to End Call, Extension, Voicemail to extension, forward to outside number or send FAX; is there an option or a tricky way so that any incoming call on that trunk will be directected outside?

I tried to put asterisk (*) on the field for the option "Forward to Outside Number", but it didn't work

 

[leejor]

That is why there is the Bridge Trunk option. It would be a security concern if a "regular" trunk could initiate an outside call on their own. Why are you restricted to only using a SIP trunk?

 

[dan_tx]

That is why there is the Bridge Trunk option. It would be a security concern if a "regular" trunk could initiate an outside call on their own. Why are you restricted to only using a SIP trunk?

My guess is they require modifying certain pentameters between the two PBX's that the Bridge Trunk does not allow you to edit. You can edit almost all the fields in Sip Trunk, but not in Bridge.

 

[leejor]

A bridge trunk , in many ways, is treated much the same as an extension. It is assumed you have control over what is being sent (the other end). It is more flexible than a DID trunk as you are actually "dialling" across the trunk. With a SIP trunk, the incoming call is routed based on DID rules, or a default destination.

 

[Manny783]

That is why there is the Bridge Trunk option. It would be a security concern if a "regular" trunk could initiate an outside call on their own. Why are you restricted to only using a SIP trunk?

That explains it, if it’s a security concern and a limitation of the “SIP Trunk” in the 3CX that we understand.

Just to give you the whole picture, we are able to create a “Bridge” between 3CX and Avaya IP 500, and through the “Bridge” (with credentials on both ends configured) the 3CX can call out on behalf of the Avaya, but our issue is that we have a remote site with an ancient Siemens HiPath 4000 that does not support “Bridge”, and we were emulating the “SIP Trunk” between 3CX vs Avaya and see if the 3CX could dial out on behalf of the Avaya, because if it did then we could configure the remote site (which by its nature of being remote is harder for us to configure than our local Avaya) with the “SIP Trunk” and replicate the config in the HiPath 4000.

Thanks for all your help fellows, now we know that a 3CX “SIP Trunk” cannot dial out on behalf of any PBX, and that this feature only works when a “Bridge” connection (with credentials configured) is used. Shame that Siemens 4000 does not support Bridge…

 

[Manny783]

Guys, have heard that a kind of physical gateway/PBX box linked to 3CX can potentially do this job, receive calls through a "SIP Trunk" and forward them, is that possible? Anybody has tried?

 

[leejor]

If the other PBX is able to register a SIP trunk to a provider, then with the 3CX trunks set to Master, it should be able to register as if 3CX were a provider. Did you try using Bridge trunk at he 3CX end? If 3CX uses a Generic SIP trunk, then it has to register to the far end (in this case a PBX), which is not a normal set-up.