DND, Call Forwarding via "standard" dial commands

DND and Call Forwarding can be set and deleted via special dial commands in the PBX. Examples:

  • Extension 304 dials *78 to enable DND. *79 deactivates DND.
  • Extension 301 dials *72302 to set Call Forwarding on extension 302. With *73 the Call Forwarding is deleted again.

The TAPI driver responds to the "DeviceStateChange" events with Custom:DND or Custom:CF or Custom:DEVCF or Custom:DEVDND. The redirection number is taken from the active call, if it starts with the redirection code.
Examples:
ON OFF
Event: DeviceStateChange
Device: Custom:DND304
State: BUSY

Event: DeviceStateChange
Device: Custom:CF301
State: BUSY
Event: DeviceStateChange
Device: Custom:DND304
State: NOT_INUSE

Event: DeviceStateChange
Device: Custom:CF301
State: NOT_INUSE

After opening the TAPI-Line the driver sends an "Action: DeviceStateList" to the PBX, which should then also generate "DeviceStateChange" events. The driver has stored the destination number internally and sends it via TAPI.
Example:
Action: DeviceStateList
ActionID: 5

Response: Success
ActionID: 5
EventList: start
Message: Device State Changes will follow

Event: DeviceStateChange
Device: Custom:DND304
State: BUSY

Event: DeviceStateChange
Device: Custom:CF301
State: BUSY


DND, Call Forwarding and UserInfo via "Special" AMI functions

The official functions of the Asterisk Manager Interface unfortunately do not provide direct actions/events for DND and Call Forwarding. Therefore, own actions and events have been specified:

Please ask your PBX vendor if these functions are supported.


Configuration

Configuration dialog in the TAPI driver: [TAPI-Line Configuration > Asterisk Server > Settings... > TAPI-Functions > DND, CallForward, UserInfo > Settings...]

Configuration dialog in CTI Client: [Options > PhoneDialog (TAPI Device) > Driver Configuration > Asterisk Server > Settings... > TAPI Functions > DND, Call Forwarding, UserInfo > Settings...]