3CX / Digistar

JorgeWillianSantos

Bronze Partner
Advanced Certified
Joined
Dec 19, 2023
Messages
38
Reaction score
7
Hello! I'm integrating 3CX with a Digistar PBX. Both communicate via IP-based communication. The current configuration already allows for the following interconnection:

Extension to extension (3CX -> Digistar / Digistar -> 3CX)

Outbound call to Digistar extension (Outbound Call -> 3CX -> Digistar)

The only functionality that isn't working is outbound calls originating from a Digistar extension.

Digistar -> Dials 99999.. -> 3CX IP-BASED -> Carrier connected to 3CX

Example: Extension 9000 in Digistar dials external number 5561999998888. The call needs to go out through the carrier connected to 3CX.

Is this type of functionality possible in 3CX? If so, how do I do it?
 
Hello,

What does not work exactly, any errors anything on screen of originating phone, anything in log 3CX, any CDR details of 3CX outbound rules set okay???
So many questions.

Paulo
 
You want Trunk to Trunk communication.
All depends on information received on incomming trunk and what information is passed onto the outgoing trunk.
You will need to know exactly the information of the trunks (SIP trace).
All 3CX outgoing calls will pass the outbound rules, these need to be set correctly to pass the call.
Note that the call is not originating from an internal phone, don't filter on this.

Paulo
 
Sorry for the lack of detail, here's more information:

When an outgoing call is made via Digistar, 3CX sends the call to extension 1000, which is the extension configured in the SIP Trunk routing.

3CX responds as follows when an outgoing call is made:

-----------------------

09/07/2025 10:43:57-[Flow] Call (C:3): has built target endpoint: Extn:1000 for call from L:3.1 Line:10001<<9799]
-----------------------
09/07/2025 10:43:57-[Flow] Target endpoint for 1000 is Extn:1000
-----------------------
09/07/2025 10:43:57-[Flow] Building target endpoint to 1000 from "9799" <sip:[email protected]:5060
-----------------------
09/07/2025 10:43:57-CM503010): Call(C:3): Making route(s) from Line:100019799 to <sip:[email protected]:5060/UDP
-----------------------
09/07/2025 10:43:57-Remote SDP is set for leg L:3.1 Line:10001<<9799]
-----------------------
09/07/2025 10:43:57-(CM505003): Provider:[BRASILIA] Device Info: Device Not Identified: User Agent not matched; Capabilities: reinvite, replaces, able-no-sdp, recvonly) UserAgent: PBX contact: [sip:10001 @3CX.PRIVATE.IP:5060]

-----------------------
-----------------------


09/07/2025 10:43:57-[CM500002): Call(C:3): Info on incoming INVITE from Line:100019799:
Invite-IN Recv Req INVITE from IP.DIGISTAR:5000 tid-03e63e30dd9e18d8da501afaee5ead01 [email protected]:

INVITE sip:[email protected] SIP/2.0
Via: SIP/2.0/UDP IP.DIGISTAR-5060;branch=z9hG4bK03e63e30dd9e18d8da501a6aee5ad01;sport=5060
Max-Forwards: 70
Contact: <sip:[email protected]:5060
To: <sip:[email protected]>
From: "9799" <sip:[email protected]>;tag=1715342977
Call-ID: [email protected]
CSeq: 16718030 INVITE

-----------------------
-----------------------
-----------------------


9799: Digistar Extension

061984849090:
Dialed External Number(Just a example)

1000:
3CX Extension

3CX.PRIVATE.IP:
3CX PBX Private IP

IP.DIGISTAR:
Digistar PBX IP

FQDN.my3cx.com.br:
3CX FQDN
 
The outbound call Route is already set to accept the type of call sent which is the default shown in the image: 0xx9xxxxxxxx

Here's an example of how I set up the rule:

I also tested it by leaving the "extension calls" field blank, and it didn't work.

I put it the rule in the top aswell to force the call through it.

1752074943194.png
 
Last edited:

Latest Posts

Forum statistics

Threads
111,977
Messages
590,097
Members
164,906
Latest member
Nari