Demo Part 2 Step 1 Internal Outbound

Import: part-2-step-1-internal-outbound.json

Goal

Complete the smallest extension-originated outbound scenario:

• a registered extension starts a call
• numbers beginning with 9 go to the external trunk
• other numbers stay inside the PBX
• the answered destination is bridged back to the original extension leg

Why This Works

• internal is both the registrar and the extension-originated call entrypoint. The same trigger accepts registration and later receives outbound calls from those endpoints.
• outgoing_type keeps the routing split explicit: external trunk destinations on one branch, internal extension destinations on the other.
• dial_external uses the external trunk ref, while dial_internal targets already registered PBX extensions.
• bridge_outgoing runs only after the outbound side has produced a usable leg, so the originating extension is bridged only to a real destination.

How to Test

1. Import the workflow.
2. Activate it.
3. Register one of the internal extensions.
4. Place a call from that extension.
5. Dial a number that starts with 9, or a plain extension number.

Expected Result

Dialed number	Result
starts with 9	workflow uses dial_external and bridges back to the original extension leg
does not start with 9	workflow uses dial_internal and bridges back to the original extension leg

What The Next Example Adds

Part 2 / Step 2 combines this outbound line with the inbound extension front door.