Opening the network plan
In System, open Network, then Interfaces and routes. This panel is reserved for the platform administrator with network rights. Read rights allow consultation; modification also requires write rights. Wait for loading to complete before editing a network card.
The plan is used, for example, to separate a client's Internet and voice networks across two network cards, to create a separate network on a card using a VLAN, or to provide a dedicated address for a carrier connection (SIP trunk) identified by IP. Prepare the addresses, prefixes, gateways, and authorized servers with the network administrator beforehand. A prefix, such as /24, indicates the size of the network.
You select network cards, addresses, and networks. The interface never requires a file name, a Linux command, a routing table, or a firewall rule to be written.
Choosing a section
The sections are In service, Internet access, Interfaces and routes, Ranges, Codecs, and SIP ports and listeners. In service shows the observed network. Drafts share Save and Cancel, with one result per section. Switching sections preserves your entries.
Preparing Internet access
Prepare the public name and addresses with the network administrator.
For network cards, VLANs, routes, and reserved ranges, use Interfaces and routes and Ranges.
A network change may interrupt telephony and your access. Prepare DNS names, addresses, and network rules with the installer before starting.
| Field or choice | Purpose | Possible values | Example |
|---|---|---|---|
| Network scenario | Determines the addresses and controls needed | Scenarios offered by the page | Scenario matching your network |
| Public name | Full name used to reach the service | DNS name, depending on the scenario | telephonie.example.test |
| Interface address | Local address of the server | Address present on the selected interface | Server network address |
| Advertised public address | Address advertised to correspondents | Public address depending on the scenario | Address provided by the installer |
| Media address | Path for voice traffic | Value suited to the scenario | Address planned for audio flows |
| Certificate | Protects encrypted connections | Proposed choice compatible with the name | Certificate covering the public name |
- Select the scenario and fill in its visible fields.
- Save the configuration request.
- Review the preview generated by the agent.
- Run the external accessibility test.
- If the check allows you to proceed, open the application and read the confirmation.
- Check the acceptance of call interruption, then confirm.
- Wait for reconnection and check the final status.
A saved request is not yet applied. A failed test normally blocks the application; the private scenario may allow an unverified application. Each application regenerates the settings and restarts the services, even if the values appear unchanged. A certificate failure can interrupt the operation before any modification.
After changing the public name, explicitly reconfigure the phones: their reprovisioning is not automatic. A successful local WSS connection does not guarantee public access on port 443.
Internal codecs set the audio formats offered. SIP listeners display the ports actually observed, in read-only mode. Old network declarations from a client do not replace the applied configuration of the installation.
Configuring network cards and VLANs
Interfaces and routes displays the detected interfaces, their Connected or Disconnected status, their hardware address, their driver, their speed when known, and their IP addresses. New card detected indicates an added card. A card marked Managed by the system retains its existing management until you take it over in the plan.
On a standard installation, network cards are often already configured by the system, with their addresses and routes. If the plan exactly matches what already exists, applying it only opens telephony on these cards (phone signaling and audio) without touching the machine's network configuration. If an address or route from the plan is missing on a system-managed card, the application is refused: add it first in the machine's network configuration, then apply again.
- Click Configure to add a card to the draft, or Edit interface to review a card already present. In read-only mode, use View interface.
- Check the Role and the addresses carried over from detection.
- Use Add address for a fixed primary or secondary address.
- For a separate network on a physical card, click Add VLAN, then enter its number and role.
| Field | Purpose | Possible values | Example |
|---|---|---|---|
| Role | Defines the card's use; verify before applying | Internet, Carrier, Client, Administration, Unused | Carrier for the voice link |
| DNS servers | Resolves names; optional | IP addresses separated by commas or spaces | DNS address provided by the installer |
| Automatic address | Requests an address via IPv4 DHCP | Enabled or disabled; carried over from detection | Enabled if the network provides the address |
| VLAN number | Identifies the separate network; required for a VLAN | Integer from 1 to 4094; suggested starting from the first available number | 920 in a lab |
| Address and prefix | Adds a fixed address; required for each added line | IPv4 or IPv6 with prefix | 192.0.2.10/24, fictitious example |
| Primary | Distinguishes the primary address from secondary ones | At most one per card; first added address is primary | Enabled for the card's address |
| Advertised address if NAT | Address communicated to correspondents for signaling and audio when the firewall translates the address | IP address without prefix, optional; empty uses the local address | Public address provided by the installer |
| Authorized server networks | Restricts authorized correspondents; visible for Carrier and Client | Network prefixes separated by commas or spaces | 198.51.100.0/24, fictitious example |
The Administration and Unused roles do not provide a telephony address. Only one card can carry the default route for a given address family. Check the carried-over values, especially in the case of an automatic address.
Delete removes an address line from the draft. Remove from plan prepares the card's return to its previous management; this is not the physical removal of the card. Check its dependent VLANs and ranges beforehand. Changes wait for save and apply.
Describing networks and routes
In Networks and routes, first configure a card if the list is empty. Under the correct card, click Add network. For example, a client's phone network may be accessible via a gateway on its voice card.
| Field | Purpose | Possible values | Example |
|---|---|---|---|
| Reachable network | Destination to reach; required per line | Network address with prefix | 198.51.100.0/24, fictitious example |
| Gateway (optional) | Route to a destination not directly connected | IP address reachable on the card; empty for a direct link | 192.0.2.1, fictitious example |
Delete removes a route from the draft. Compare your entry to the Detected routes, which describe the observed state of the machine.
Opening address ranges to clients
A range contains internal addresses reservable by trunks. It can be carried by a card, a VLAN, or a virtual interface created with Add internal interface in Cards. The latter does not create a physical port; its reachability must be planned with the network administrator.
- In Address ranges, click Add range after configuring its interface.
- Enter its bounds and network.
- Enable the relevant clients in Authorized clients.
- Save and apply the plan before preparing the clients' trunks.
| Field | Purpose | Possible values | Example |
|---|---|---|---|
| Name | Identifies the range; required | Text, 1 to 120 characters | Carrier voice |
| Card or interface | Carries the addresses; required | Card, VLAN, or internal interface from the plan | Card dedicated to the carrier |
| Network and prefix | Delimits the network; required | Network address with prefix | 192.0.2.0/24, fictitious example |
| First address | Inclusive start of the range; required | IP belonging to the network | 192.0.2.20 |
| Last address | Inclusive end of the range; required | IP from the same network, greater than or equal to the first | 192.0.2.30 |
| Authorized clients | Opens reservation to selected clients | Toggle per client; none at creation | Client for the connection |
Do not include an address already configured on the card, an address from another range, or the IPv4 network or broadcast address. Reserved addresses shows who uses each address: client, object name when available, and status. No reserved address. means no reservation is listed.
Authorized clients on a card: on a card with the client or carrier role, select the clients allowed to use the PBX's primary address on this card for their trunks and interconnections — for example, a client's voice network where their old PABX is located. No range is required for this use; ranges remain intended for addresses dedicated by trunk. A client only sees the cards opened to them. Removing a client from the list cuts off their calls on this card in both directions as soon as the plan is applied. This setting is part of the network plan: it is applied, confirmed, and rolled back together with it.
Reservation is done in the trunk record. A client's administrator only sees the ranges opened to them. Delete removes a range from the draft; a range still in use cannot be removed without processing its reservations.
The Apply saved plan button is located next to the plan in Interfaces and routes. Nearby text explains its unavailability: read-only access, unsaved modifications, data to refresh, operation in progress, no saved plan, or plan already in service.
Saving then applying
- Use the page's common save command to save the draft. Canceling changes only discards unsaved modifications.
- Click Apply saved plan. The button remains unavailable while there are unsaved modifications, during an operation, or if this revision is already applied.
- In Review plan before applying, review the cards, roles, VLANs, addresses, routes, ranges, and announced deletions.
- Click Apply saved plan, or Cancel to close the summary without applying.
- Wait for Confirmation required within two minutes.
- Check your access, then click Confirm, I am still connected within two minutes of applying.
The audio relay restarts if its addresses change. A restart during a call could cut its audio. In this version, the application automatically waits for ongoing calls to end: no additional option needs to be checked to request this wait.
Without confirmation within the time limit, the previous configuration is automatically restored, with its routes, addresses, and the enabled or stopped state of the affected cards. Only cards managed by the telephony's network plan are reconfigured; cards managed separately by the system are preserved. Reloading does not repeat within the verification loop. Follow the status until Applied or Previous configuration restored. Automatic rollback does not exempt you from checking access and calls after the operation.
After a successful rollback, the saved draft returns to the last applied plan: new addresses and canceled routes do not remain to be reapplied. Reload the data before resuming. A reservation predating a failed first application remains visible and releasable; its range and the necessary card are retained, without the canceled addresses or routes. A more recent draft is not overwritten.
A rollback only concerns addresses carried by the canceled change: trunks whose address was already applied remain ready and continue to make calls. Audio to a phone located on a client network (VLAN or dedicated card) originates from the PBX's address on that network, even if no trunk range is opened there.
During a network plan change (applying, awaiting confirmation, or a rollback to be resumed), other network modifications and the deletion of a trunk with a reserved address are refused with the message "A network plan change is in progress. Wait for it to be confirmed or canceled, then try again.". After an application or rollback, the audio relay restarts and responds before the SIP server: calls resume immediately.
Settings for the public name, certificate, and access scenario have their own workflow: see Preparing the network.
Codecs, ports, and SIP certificate
Codecs defines the internal audio formats offered; save changes with the common button. SIP ports and listeners shows the observed ports and listeners. The provided SIP certificate appears in this section when this certificate mode is selected. HTTPS and notification certificates can be viewed in License and information.
Removing a range
In Ranges, use the deletion option for the range concerned. Read Delete range, then confirm or Cancel. Confirmation removes the range from the draft; the removal takes effect after Save then Apply saved plan.
Checking the result
Review the detected cards and routes. Check the reserved addresses, then the Address applied status in the relevant trunks. Test an incoming and an outgoing call with audio in both directions. If there is silence, compare the network, local address, and advertised address in the call log.
When the machine is behind a router, devices on the same local network as it receive its local address for audio: they do not need the return path via the public address. A device located on another internal network (for example a voice VLAN) that reaches the machine via its public address needs, in turn, the router to also translate the source address on this return path, or direct access to the machine's address on its network. Without one or the other, the call is established but remains without audio.
Trunks to a carrier reached via the Internet always originate from the Internet card, even when a second card (for example a voice VLAN) is opened to the client. If the Internet card's address has no advertised address in the plan, a machine behind a router advertises its public address to the carrier; an advertised address entered in the plan remains the priority.
If this does not work
"The network plan is unavailable.": use Retry and check your rights. "Detected cards are temporarily unavailable." does not indicate that the machine has no cards. Wait for the inventory to return before drawing conclusions.
"The modification could not be saved. Check the addresses and networks entered.": check prefixes, gateways, and range bounds. If the plan has changed or a range is still in use, reload the data and review reservations before resuming. Commands are blocked during an operation or a read failure.
Application refused displays under the status the card concerned and what needs to be corrected, for example an address or route missing from a system-managed card. Correct this point, then apply again; pass the message to the installer if needed. Incomplete rollback: intervention required blocks new modifications. Automatic retry is limited to five attempts, spaced 10, 20, 40, then 80 seconds apart after failures; restarting the service does not reset this counter. Do not consider these states as a validated active configuration.
After manual repair by the installer:
- Check access to the machine, routes, card status, and calls.
- With a platform administrator account authorized to modify the network, click Manually repaired network: unblock modifications, offered only after an incomplete rollback. The button is unavailable during the request or if reading the status fails.
- Wait for processing, then reload the data and compare the draft to the actual state before any new application.
This button acknowledges the repair and unblocks modifications. It does not repair the network, does not modify the cards, and does not mark the failed plan as applied. It therefore does not replace verification of the actual state.
