Page Comparison

...

x-hoppers licenses can be ordered in Wildix Partner Community. The following licenses are available:

...

...

7 - Volume+ button

8 - Speaker

...

LED indicators overview

Multi-Сharger overview

Multi-Сharger consists of 6 chargers connected in parallel with a 5V/ 4A power supply and can simultaneously charge up to 6 headsets.

...

Before headsets can be assigned to specific users, they need to be registered to W-AIR Base Station. 

...

1. Put the Headset in the registration mode by pressing Call, Volume+ and Volume- buttons at the same time for more than 5 seconds. When the Headset is in registration mode, the LED indicator blinks with short blue flashes and a voice prompt announces “Registering”.

2. The Headset connects to the Base Station. When the Headset is subscribed, the voice prompt announces “Headset subscribed”.

...

1. Go to WMS -> Devices -> W-AIR devices

2. Choose the headset and click Assign to user

3. Enter user extension and click Save.  

...

...

• Retail Mode: On

• Audio feedback: Voice

• Silent charging: On

• Silent mode: Off

...

...

1. Choose the headset on the W-AIR devices tab -> click Assign to user

2. Select “unknown” in the Extension field and click Save.  

...

...

1. Click Add number

2. Enter *Wairhotline*

...

3. Add the below Dialplan applications:

   • Set -> Language -> choose language

   • Play sound -> click Browse (three dots) and choose the sound to be played on joining the broadcast or create it dynamically using TTS, for example Welcome to x-hoppers, joining the broadcast

   • Conference -> enter the conference room ID number. This can be any number, e.g. 1, 2, 3, etc. 

...

3. • , etc. 

...

...

• A user should dial the feature code for Conference access (98 by default) + the conference room number. Example: 981 for conference 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.

...

...

curl -X POST --header 'Authorization: Bearer {token}'

https://{pbx domain}/api/v1/Originate -d

'channel=Local/999@myDialplan&application=System&async=true' -d

'variable=dst=777,dept=Sales,msg=help required at checkouts'

...

• 999 (you can set a custom number) = the Dialplan rule that processes the request. 

• dst = the rule in the outgoing Dialplan of users that should receive the announcement

• dept =  department name

• msg = the announcement: a text prompt or a path to an audio file stored on the PBX

...

...

3. Create a Dialplan rule with dst number (this can be any number that is not occupied by a user or by another real destination, e.g. 111 or 777) in the outgoing users Dialplan(s). If users have different Dialplans, the rule with dst number should be created in each of them (or it can be added as an included procedure). Configuration:

   • Set :: Language :: en (this one is needed for TTS processing)

   • Set(sound=${SHELL(/usr/sbin/data_engine_cli GetSound ${CALLERID(num)})})

   • Play sound :: ${sound}

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

Modifying the timeout of broadcast mute

...

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

...

Additionally, on the product web page you can place a Kite button, letting customers contact clerks or back office via chat, audio or video call. 

...

...

We provide SDK (REST APIs), which can be used to set up call generation when someone scans the code. So for this part, you need a web developer, who would configure the relevant POST and CURL requests for each QR code.

...

...

On the Dialplan side, you need to configure the call to be sent to the broadcast with clerks. The call should be accompanied with notification via our Text-to-speech feature, to inform clerks which page was scanned/ where in the store assistance is required. QR codes require separate Dialplan entries. 

...

Dialplan entries. 

...

It is possible to configure recording of in-store conversation, with possibility to listen to it in CDR-View, as well as post x-hoppers broadcast content to x-bees channel.

...

Record in-store conversations (listen in CDR-View)

...

1. create directory /etc/systemd/system/pbx-data-engine.service.d

   Code Block
   # mkdir /etc/systemd/system/pbx-data-engine.service.d

2. Add the following key to the file:

   Code Block
   # nano-tiny /etc/systemd/system/pbx-data-engine.service.d/override.conf [Service] ExecStart= ExecStart=/usr/sbin/pbx_data_engine.py --daemon --mode calls presence -cr

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

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

Once enabled, the recording of in-store conversations get displayed in the CDR-View. Recording starts when a user unmutes themselves in the conference and starts talking.

Post content to x-bees channel

...

It is possible to transcribe the content of x-hoppers conference (everything that was said during the day) and post it to x-bees conversation (both the transcription and the audio recording of each piece of the conversation). The transcription is posted on behalf of the users that were talking at a given moment.

How to configure

1. Create x-bees conversation with all the users that are participating in the x-hoppers conference and also needed managers.

2. Copy x-bees conversation ID (available in the URL of the conversation)

3. Add the following data to the /rw2/etc/pbx/x-hoppers.json file:

...

When the feature is enabled, whatever is told in the conference is automatically transcribed and displayed in x-bees conversation, so managers could monitor what was discussed in the conference.

How to increase volume for noisy environments

...