AxonSBC / Configuration
Routing your first call
Understand the AxonSBC workflow before changing call routing.
01Start with the incoming trunk
Identify the incoming and outgoing SIP trunks for the call path. Check that both are enabled and that the incoming trunk permits the intended outgoing trunk. An empty explicit outgoing allowlist rejects all routed calls from that ingress.
02Create the route in draft
Create a routing rule with the intended incoming-number match and outgoing trunk. Use send_as when the outgoing destination must differ from the matched or normalized number. Keep rules in the intended priority order. Configuration edits remain in a shared draft until committed.
03Review and commit
Use Review & commit to inspect the object and field changes. Enter a meaningful commit message, then commit the change. A configuration revision is separate from the application version. Discard draft restores the active configuration without changing routing.
04Verify the call path
Use the simulator to inspect routing and permission decisions, then place an authorized test call. Confirm the destination, two-way audio and call termination. Review the call record. A simulator result alone does not verify a live carrier path.