Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Scroll export button
scopecurrent
template-id0fa09813-8b86-460a-aa1d-ef450a80e9ce
quick-starttrue
add-onScroll PDF Exporter

...

Note

Note:

  • The support starts from WMS 6.03.20230630.3. 
  • The feature works only if there is an x-hoppers license available on the PBX.

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

Starting from WMS 6.03.20230630.3, it is possible to record in-store conversations and listen them via CDR-View. The recording starts when user unmutes himself in the conference and begins talking.

...

  1. Add the following key to the file: 

    Code Block
    # vi  /etc/systemd/system/pbx-data-engine.service.d/override.conf
    
    [Service]
    ExecStart=
    ExecStart=/usr/sbin/pbx_data_engine.py --conf_recording


  2. 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.

Note

Current limitations:

  • Recording is not automatically stopped if user forgets to mute the headset.
  • For a new user who joins the conference, recording is automatically started even if the user is muted, and the recording file of about 3 seconds is saved on the PBX.

...

Warning

Important: Make sure you've also set up recording of the in-store conversations (see the "Record in-store conversations (listen in CDR-View)" section of this guide.

...

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:

    Code Block
    [
      {
        "store_veesion_id": "test-store-wildix",
        "name": "Store1",
        "audio_conf_id": "2",
        "location": "Odesa",
        "xbees_channel_id": "f6d17593-98b6-471d-941a-cd03153f",
        "user": "12345"
      }
    ]
    
    


    Where:

    • store_veesion_id (optional): ID of the store on the Veesion side. Applicable if there is Veesion integration. 
    • name: name of the store 
    • audio_conf_id: ID of the audio broadcast channel in x-hoppers where the communication takes place
    • location: location of the store
    • xbees_channel_id: ID of the x-bees conversation, copied in step 2, where the content will be posted.
    • user: user, on behalf of whom the content will be posted (applicable for Veesion integration)

...