x-hoppers Custom Settings

Create multiple broadcasts

To set up multiple x-hoppers broadcasts, create separate Dialplans:

Each x-hoppers Dialplan should contain both Wairhotline and wair strings described in x-hoppers Admin Guide.

Control x-hoppers headsets charging behaviour

By default, there is only LED indication while charging x-hoppers headsets. You have the option to set headsets to have both LED indication and audio while charging and configure them to be disconnected without possibility to receive calls while charging.

• Access the following file via SSH as root

  nano-tiny /rw2/etc/provision.conf

• Add the following parameter to the section [wildixair]

  WairSilentcharging =on|off|deactivated

Where "on" implies that only LED indication is used while charging; "off" suggests normal mode with LED indication and audio while charging; "deactivated" means headset is disconnected and can’t receive calls while charging. 

Enable battery level announcement

In case of using voice authentication feature, the battery level announcement is played by default. If you don’t use this feature, but want to notify users on the battery level, you can configure it via Dialplan. Add the following applications to *Wairhotline* called number:

1. Set -> battery_level -> ${CURL(http://127.0.0.1:5060/v1/wair_battery_level/?ua=${BASE64_ENCODE(${SIP_HEADER(User-Agent)})})}

2. Custom application -> ExecIf($["${battery_level}"=""]?Set(battery_level=unavailable))

3. Play sound -> Battery level is ${battery_level}

Enable unmuted announcement

You have the option to enable the logic of notifying a user that a headset is unmuted. By default, it is disabled. Once enabled, a user is notified when he is unmuted and talking, as soon as the specified timeout is reached. Example: the timeout is 60 seconds; user hears a beep in case he has been talking for 60 seconds and the headset was unmuted. There are no alerts in case the headset is unmuted, but no talking is detected. To enable the feature:

• Access the following file via SSH as root

  /etc/systemd/system/pbx-data-engine.service.d/override.conf

• Add the following line to the file

  Environment='XHOP_UNMUTE_ANNOUNCE_TIMEOUT=X'

Where ‘X’ is a value in seconds.

• By default, the user is notified with a beep. To set up a custom alert, use the following parameter:

  Environment='XHOP_UNMUTE_ANNOUNCE_SOUND=00000/u_unmuted'

Where ‘u_unmuted’ is the name of the file placed in the 00000 folder on the PBX. 

Increase volume for noisy environments

In case of noisy environment, you can increase x-hoppers volume. To do this:

• Access the following file via SSH as root:

nano-tiny /etc/callweaver/confbridge.conf

• Add the following parameter to the section [default_bridge]

default_listening_volume=6 

Where 6 is the preferred volume. The maximum value is 10. The default value is is 0.

Join a broadcast from other devices

Wildix desk phones can also join a broadcast, as long as they are connected to the same PBX. To connect to a broadcast, use one of the options:

• Dial the feature code for broadcast access (98 by default) + the broadcast room number. Example: 981 for the broadcast room number 1

• Alternatively, a Dialplan can be configured so that when users dial a certain number, e.g. 333, the call is automatically put into the broadcast

Modify the timeout of broadcast mute

Users have possibility to mute the broadcast by double-pressing the Push-to-talk button. By default, the broadcast gets muted for 60 seconds. If user wants to unmute the broadcast before the 60-second timeout, user can double-press the Push-to-talk button again. The default timeout can be customized. To do this:

1. Add the following line to the file /etc/systemd/system/pbx-data-engine.service.d/override.conf: 

# nano-tiny /etc/systemd/system/pbx-data-engine.service.d/override.conf
[Service]
Environment='XHOP_UNHOLD_TIMEOUT=120' 

Where 120 is the custom timeout. If you want to disable the timeout, set the value to 0:

Environment='XHOP_UNHOLD_TIMEOUT=0' 

2. Reload systemd and restart the service to apply the changes:

# systemctl daemon-reload
# systemctl restart pbx-data-engine