DND and Auto Answer provisioning
Preview: The new call-handling features are in testing. The portal controls described here are prepared for a future deployment; they are not yet part of the verified live portal release. Updated app builds and platform validation are also required. This page documents the intended settings and provisioning format.
The same provisioning format covers Android, iPhone, Windows and macOS. It configures call handling inside the softphone, rather than PBX-wide DND.
App controls
Users find Do Not Disturb under Settings > Preferences. Auto Answer is at the bottom of an account’s Advanced SIP settings. Mobile apps open Settings from the main menu.
Read the mobile DND guide, mobile Auto Answer guide, desktop DND guide and desktop Auto Answer guide for user-facing setup.
Planned portal controls
Once deployed, Advanced > Call handling will provide separate controls for DND and Auto Answer:
| Control | Effect |
|---|---|
| Feature availability | Makes the feature available or disables it, including retained personal settings. |
| Default settings | Supplies the initial DND policy or Auto Answer options. |
| Allow user overrides | Allows personal changes, or locks the supplied policy. |
The settings use the portal’s existing draft and publish workflow. Published policy is applied during provisioning and when supported existing BYO accounts refresh their project settings. Hosted accounts receive the policy during initial sign-in; the BYO project-refresh mechanism does not apply to Hosted accounts.
Editable defaults apply until the user saves a personal choice for that feature. Later default changes preserve that choice. Use administrator defaults, where offered, removes the personal override for that feature. Locking a feature preserves personal values so they can return when it is unlocked.
Personal device-wide DND only applies to accounts whose administrator permits DND overrides. It cannot bypass a locked account policy. DND still takes priority over Auto Answer.
Provisioning format
The portal policy is stored at settings.provisioning.callhandling. External JSON provisioning can also supply callhandling on an account. Account settings may refine editable project defaults, but cannot relax a project lock or availability restriction.
{
"version": 1,
"dnd": {
"available": true,
"allowOverride": true,
"enabled": false,
"rules": [
{
"name": "Weeknights",
"enabled": true,
"days": 31,
"start": 1320,
"end": 480,
"allDay": false,
"callers": "all",
"numbers": []
}
]
},
"autoAnswer": {
"available": true,
"allowOverride": true,
"enabled": false,
"delay": 3,
"route": "system",
"headsetOnly": false,
"tone": true
}
}In this example, manual DND starts off, but the enabled weeknight rule still rejects matching calls. Auto Answer starts off.
Schedule days use a Monday-first bitmask: Monday is 1, Tuesday 2, Wednesday 4, Thursday 8, Friday 16, Saturday 32 and Sunday 64. Add the desired days; 31 means Monday through Friday and 127 means every day. Times are minutes after midnight in the device’s local time. An earlier end time continues into the next day.
The caller selector is all, unknown, or selected. Selected-caller rules require at least one entry in numbers. Limits are 50 rules and 100 caller entries per rule. Auto Answer delay is an integer from 0 to 30 seconds; routes are system, speaker, or headset.
Omitting a feature retains its existing local behaviour. The JSON account fields appInitiatedAutoAnswerEnabled and autoAnswerTimeoutInSeconds are also accepted for compatible external provisioning. This does not add an Acrobits XML importer or SIP-header-triggered auto-answer.
Conditions still apply
Provisioning does not bypass the foreground-app, unlocked-device, microphone, single-call or headset requirements. Automatic answering remains audio-only. Verify the published policy and real incoming calls on each supported platform before rolling out the controls to users.