Forwarding incoming calls from one trunk via another different trunk

[Victor Manuel]

We want that incoming calls from one sip-t are forwarding via another different sip-t (to the same original destination number, no numbering manipulation). We don't know how to config the inbound rute, we have tryied the following,
- DID incoming: (.*)
- Destination: external number: /1
but sintax is not supported and red error message appears (incorrect number format).
We want to do this because all calls from another system (which is in sip-t with opur 3CX) are routed to our 3CX system, and when this calls arrives must be done via local lines on our 3CX system.
Do you know how to configure the behaviour that we want to achieve?
Thanks in advance and BR

 

[Wendelspanswick]

We want that incoming calls from one sip-t are forwarding via another different sip-t (to the same original destination number, no numbering manipulation). We don't know how to config the inbound rute, we have tryied the following,
- DID incoming: (.*)
- Destination: external number: /1
but sintax is not supported and red error message appears (incorrect number format).
We want to do this because all calls from another system (which is in sip-t with opur 3CX) are routed to our 3CX system, and when this calls arrives must be done via local lines on our 3CX system.
Do you know how to configure the behaviour that we want to achieve?
Thanks in advance and BR

I hope I'm proved wrong but I don't think that the 3CX platform supports trunk to trunk transfers, it was something we tried to get working about 3 years ago and we discussed it with 3CX support.
There doesn't seem to be a way of translating an incoming trunk to go out on another trunk.

 

[leejor]

I think that that this would only be possible via a "dummy" extensions forwarding rules. Send the incoming calls to an extension that is set up to forward back out on a given route. DID parameters would have to be used to sent to the extension. 3CX is designed to send incoming calls to an internal destination. It was not designed to tandem calls through, so you must re-direct the call using the features of an extension or other internal destination.

 

[Wendelspanswick]

I think that that this would only be possible via a "dummy" extensions forwarding rules. Send the incoming calls to an extension that is set up to forward back out on a given route. DID parameters would have to be used to sent to the extension. 3CX is designed to send incoming calls to an internal destination. It was not designed to tandem calls through, so you must re-direct the call using the features of an extension or other internal destination.

That works but it restricts you to one fixed destination for your outbound route.
Our scenario is we have a large site with a 3CX linked to the original ISDX system that used to serve the whole site but now covers about 60% of it.
The 3CX has its own SIP trunks and the ISDX has its own ISDN30 trunks, 3CX users can dial ISDX extensions and vice versa.
3CX users can dial out using a code so they go over the link to the ISDX where the number is then translated and sent out to any external destination via the ISDN30.
Unfortunately there is no way to replicate this in the other direction i.e. ISDX users dial out using a code so they go over the link to the 3CX which then translates the number and sends it out to ANY destination via the SIP trunks.
This would give us reliance and overflow routes if one link becomes busy.

 

[leejor]

You can if you connect the two using a 3CX Bridge trunk (probably set as Master). Incoming digits are treated more like those dialled by an extension, so with the correct prefix, calls could go back out on a trunk.

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

 

[Wendelspanswick]

You can if you connect the two using a 3CX Bridge trunk (probably set as Master). Incoming digits are treated more like those dialled by an extension, so with the correct prefix, calls could go back out on a trunk.

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

Would the 3CX Bridge work with a Patton gateway as that is how the 3CX connects to the ISDX as it has no IP capability.