Trunks without registration

This procedure is only necessary if an unregistered VoIP trunk (e.g., an IP-based trunk without SIP registration credentials).

The goal of this procedure is to route calls that start with a designated root prefix to a specific NethVoice PBX instance. When a call—whether outgoing from the PBX or incoming from a gateway or provider—reaches the NethVoice Proxy, the proxy examines the beginning of the dialed number (the root). If the dial string matches the configured root (for example, 07214055), the proxy automatically forwards the call to the selected NethVoice PBX instance (such as nethvoice1). This ensures that calls with the specified prefix are consistently routed to the correct internal PBX.

1. Prerequisites

• The NethVoice Proxy module must be installed and configured.
• At least one NethVoice instance (e.g., nethvoice1) must be installed and configured.
• The VoIP trunk must be configured within the target NethVoice instance (e.g., nethvoice1) as a Peer/Host Trunk or similar, and it must be an "unregistered" type.

2. Accessing Trunk Routing Rules

1. Access the NethServer 8 administration interface.
2. In the left navigation panel, select your NethVoice Proxy instance (in the example: nethvoice-proxy1).
3. Navigate to the Trunk routing rules section.
   • Note: If you see "No NethVoice application available", you must first install and configure at least one NethVoice instance.

3. Creating the Routing Rule

This rule instructs the NethVoice Proxy to handle calls for a specific prefix and route the traffic directly to the chosen NethVoice instance.

1. Click the Add rule button.
2. The Add rule dialog will appear.
3. Configure the rule:
   • Root: Enter a unique prefix that will act as the trigger for this routing rule.
     • Important: Choose a numerical string that is not part of your internal numbering scheme or standard external prefixes (e.g., 456, as shown in the example). This prefix will be intercepted by the proxy and routed.
   • Destination application: Select the NethVoice instance that contains the VoIP trunk you want to route (e.g., nethvoice1 [10.5.4.1]).
4. Click Save.

4. Verification and PBX Configuration

1. Once saved, the rule will appear in the Trunk routing rules list, and a "Completed" notification will show.

2. The final and crucial step is to configure your NethVoice instance's PBX (FreePBX/Asterisk) to handle calls using this route prefix:

   • For Outgoing Calls: Configure an Outbound Route in your NethVoice PBX. The Dial Pattern should include the configured Root prefix (e.g., 456). This route should be directed to the specific unregistered trunk.
     • The PBX should then strip the 456 prefix before sending the number out to the trunk/provider.
   • For Incoming Calls (from the unregistered trunk): The provider/gateway sending the call to the NethVoice Proxy must prepend the configured Root prefix (456) to the destination number (DID). The PBX, upon receiving the call on the unregistered trunk, can then use an Inbound Route matching that prefix to direct the call internally.