Set SIP network mode
Configures simultaneous Ethernet and Wi-Fi network operation rules for the monitor.
Rules:
- Ethernet and Wi-Fi cannot both use static IP or DHCP at the same time.
- If Ethernet uses static IP, Wi-Fi must use DHCP, and vice versa.
- Wi-Fi must be connected to a network with a different IP range than Ethernet.
- Even if Ethernet is disconnected, its settings must differ from Wi-Fi's to ensure correct operation.
The endpoint POST /api/intercom/sipnet
accepts JSON with:
net
: Interface used for DNS resolution (0 = Ethernet, 1 = Wi-Fi)fixed_net
: If true, multicast and SIP calls are bound to thenet
interface.
Default in test build: {"net":0,"fixed_net":1}
.
Example behaviors:
{"net":0,"fixed_net":1}
: DNS via Ethernet, SIP/multicast via Ethernet, Wi-Fi for third-party apps.{"net":1,"fixed_net":1}
: DNS via Wi-Fi, SIP/multicast via Wi-Fi, Ethernet for third-party apps.{"net":0,"fixed_net":0}
: DNS via Ethernet, SIP/multicast via Wi-Fi (Wi-Fi has higher priority).{"net":1,"fixed_net":0}
: DNS and all traffic via Wi-Fi.
- application/json
Request Body required
- net integer required
Interface used for DNS resolution (0 = Ethernet, 1 = Wi-Fi)
- fixed_net integer required
Bind SIP/multicast calls to the
net
interface (0 = no, 1 = yes)
Responses
- 200
- 400
- 401
OK
- Missed json body or wrong param.
Response sample:
"error": "Wrong JSON body"
- Required field is not provided.
Response sample:where
"error": "Wrong JSON body: no value for `param`"
param
- is a required field that was not provided - Field was of the wrong type.
Response sample:where
"error": "Wrong JSON body: value `param` was of the wrong type"
param
- is a field of the wrong type
- application/json
- Schema
- Example (from schema)
- Base
- Missed param
- Wrong param type
Schema
- error string
Error information
{
"error": true
}
{
"error": "Wrong JSON body"
}
{
"error": "Wrong JSON body: no value for `param`"
}
{
"error": "Wrong JSON body: value `param` was of the wrong type"
}
Unauthorized request. Log In
- application/json
- Schema
- Example (from schema)
- Log In
Schema
- error string
Error information
{
"error": "Log In"
}
{
"error": "Log In"
}
Loading...