LAN trunks and gateways

Use LAN mode when a SIP trunk or gateway communicates with Exovo over your local network. Examples include a Spectrum SIP gateway with a private IP address and a Patton or Grandstream FXO gateway connected to analog telephone lines.

LAN mode makes calls through that peer advertise the PBX's configured LAN address for SIP signaling and audio. Internet trunks continue to use the public address. This avoids one-way audio or failed hangup signaling when a local device cannot reach the PBX through its public address.

Configure the addresses

1. Open Admin → Connectivity → Network.
2. Set Host IP Address to the PBX host's LAN IPv4 address, for example 172.21.0.111. Use the host's address, rather than a Docker container address or the gateway's address.
3. Keep Static Public IP set to the real public address when using a static public IP. Automatic public-IP detection can also remain enabled when appropriate for your deployment.
4. Save the network settings. Apply the requested SIP/core restart before testing calls.

LAN mode takes its address from Host IP Address. You do not enter a second PBX address on each trunk. On a multi-tenant system, the machine/instance tenant's network settings supply this address.

Enable LAN mode on the peer

1. Open Admin → Trunks and edit the local trunk or gateway.
2. On Options, enable Use the configured LAN address for this SIP peer.
3. Leave the registrar/server address pointing to the peer, for example 172.21.0.20.
4. Leave the peer's port at the port on which that device listens, commonly 5060.
5. Save. Exovo refreshes the gateway configuration to apply the selection.

Enable this option for each local peer that needs it. Leave it off for internet SIP providers. Existing trunks keep their previous behavior until the option is selected; updating Exovo or importing a 3CX backup does not automatically enable LAN mode.

Choose the correct PBX port

The peer's listening port and the PBX port the peer sends calls to are separate settings. Changing LAN mode does not change the peer's listening port.

Local IP-authenticated trunks: have the provider or gateway send inbound SIP to the PBX's LAN address on 5082. Exovo also sends calls through that peer from its LAN profile. Coordinate the PBX port change with the provider before switching an existing trunk. Apply the same trunk allow-list policy used for other IP-authenticated trunks.

Registering FXO gateways: a Patton or Grandstream can continue registering and sending authenticated inbound calls to 5060. With LAN mode enabled, Exovo's outbound calls to the device use the LAN profile on 5082, addressed to the device's configured listening port, commonly 5060. Exovo does not need to register back to the gateway.

Allow 5082 over TCP/UDP between the PBX and local SIP peers as needed. A LAN peer does not require an internet port forward for this connection.

Test the complete call path

• Call in from a mobile. Confirm the greeting is audible, then transfer to a desk phone.
• Confirm audio in both directions.
• Call out through the local peer. Confirm audio in both directions and caller ID.
• Hang up from the remote phone and confirm the Exovo call ends too.
• If internet trunks share the PBX, test one of those as well.

A gateway registration confirms authentication; it does not prove that audio or disconnect signaling is working. If a call fails, check the peer's destination PBX port, the configured Host IP Address, and the local firewall before changing the public-IP setting.