Html |
---|
<div id="fb-root"></div>
<script>(function(d, s, id) {
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = 'https://connect.facebook.net/en_US/sdk.js#xfbml=1&version=v2.11';
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script> |
Html |
---|
<div class="fb-like" data-href="#" data-layout="button_count" data-action="recommend" data-size="large" data-show-faces="true" data-share="true"></div> |
Html |
---|
<div class="lang-box-pdf">
<div>
<div class="google-lang">
<div id="google_translate_element">
</div>
<script type="text/javascript">
function googleTranslateElementInit() {
new google.translate.TranslateElement({pageLanguage: 'en', includedLanguages: 'de,es,fr,it,nl', autoDisplay: false}, 'google_translate_element');
}
</script>
<script type="text/javascript" src="//translate.google.com/translate_a/element.js?cb=googleTranslateElementInit"></script>
</div>
<div class="pdf-button">
<a href="https://confluence.wildix.com/spaces/flyingpdf/pdfpageexport.action?pageId=73302154" alt="Convert to .pdf" title="Convert to .pdf"><img src="https://confluence.wildix.com/download/attachments/14549012/pdf-button-download-wildix-documentation.png"></a>
</div>
</div>
</div> |
Scroll export button | ||||||||
---|---|---|---|---|---|---|---|---|
|
Info |
---|
Here is a technical guide for the implementation of the InterACT solution from ISI-Com, a multichannel contact center, in addition to the PBX from the Wildix brand.This document is an installation guide for the PBX integrator and cannot in any way replace the manufacturer's document. You MUST systematically check this information with the manufacturer. It is possible that the tests carried out below may not be compliant with your version of PBX or with different architectures. Created: May 2020 Permalink: https://confluencewildix.wildixatlassian.comnet/wiki/x/ioBeBVwDOAQ |
Table of Contents | ||
---|---|---|
|
...
In the dedicated interface, ISI-COM selects Wildix as the SIP trunk provider and then provides the relevant data, including the connection IP address, the necessary codecs, etc.
API declaration in order to link InterACT and Wildix
Declaration of users' workstations. This step requires to specify for each of them the login/password pair used.
Wildix Configuration
The setup includes the creation of Wildix dialplans, the creation of the SIP trunk between the two solutions, and the management of music on hold.
...
The trunk group will contain the SIP trunk that will be created below. Leave the trunk group empty for now.
Creation of the dialplan all_users:
This dialplan allows to group all Wildix internal users who can thus be reached from InterAct. It is particularly useful for multiple-sites customers
Note |
---|
You should consider updating this dialplan if new sites are created. |
...
X. to reach internal users on the dialplan users all (previously created)
Creation of the dialplan main_isicom:
This dialplan receives incoming calls from the operator and forwards them to the Wildix-Interact trunk.
This dialplan is of course to be included in the "main" dialplan.
...
Warning |
---|
Be careful, the default DTMF mode on the Interact side is: SIP-INFO |
Add the SIP trunk to the trunk group
Now that the SIP trunk is available, we can add it to the trunk group.
Management of the music on hold
...
By convention, the value shown in the SIP header "Music" by InterAct is the default entry point number, otherwise known as the number on which InterAct was called.
Macrosuite divider macro | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Button macro | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|