Requirements
The following are the Vivocha requirements:
- Vivocha is a web application
- Cloud: the architecture and the physical placement of servers are transparent to the user.
- Accessible to everyone through the Internet.
- Vivocha works with standard web protocols (HTTP e HTTPS).
If you have any Proxy or Firewall your system must allow your network to have a free access on the following domain:
*.vivocha.com | vivocha |
d3btqb6knwd3a4.cloudfront.net | static assets |
fonts.googleapis.com | not required - fonts, fallback |
maps.googleapis.com | not required - maps |
www.google-analytics.com | usage stats |
s3.amazonaws.com | static assets |
The web pages requirements are:
- It must be based on Javascript code, running on the user's browser.
- The user's browser must allow the execution of Javascript code.
The Vivocha Activation Code (VAC) must be present in every page in which Vivocha’s features are to be used.
Vivocha Activation Code<script type="text/javascript"> (function(){ var t = document.createElement("script"); t.type="text/javascript"; t.async=true; t.src="//www.vivocha.com/a/ACCOUNT/api/vivocha.js"; var n=document.getElementsByTagName("script")[0]; n.parentNode.insertBefore(t,n); })(); </script>
The Form Sharing requirements are:
- Forms must be compliant with the HTML standards.
- Can be limited/disabled through specific CSS classes (optional).
Test your browser and network here: http://websocketstest.com/
The Browser requirements are:
The Vivocha Web client supports several browsers. There are some Vivocha features that are not supported by all browsers.
Officially supported browser are:
- Microsoft Internet Explorer 9+;
- Mozilla Firefox (latest version);
- Google Chrome (latest version);
- Apple Safari (latest version);
Feature Limitations:
The following table describes the feature limitations and known issues with the supported browsers.
- Real time stats: available on modern browsers (IE9+);
- Dissuasion timer (graphical component): available on modern browsers (IE9+);
- Browser notification: available on Google Chrome and Mozilla Firefox ONLY.
- Others: other limitations could be applied if the browsers technology doesn't support the feature like:
- Graphics components;
- Performances updates;
- New particular browser-linked features;
- etc.
To have the best experience with Vivocha, and to ensure that all the console/widgets features will work properly, we highly reccomend to use modern browsers like Google Chrome or Mozilla Firefox, to update the browser regularly, and do not install any browser extensions.
Warning
Starting from Vivocha rel 4.3 (http://tech.vivocha.com/post/115856337168/vivocha-4-3) the platform is not more fully compatible with IE8.
The IE limitations are:
- Some contact apps could not work;
- Is not possible to use the Telephony features;
- Is not possible to use the Video-chat capabilities;
The new Telephony/Video features are natively supported in all the browsers that support WebRTC like the last version of Google Chrome or Mozilla Firefox.
Computer / Hardware:
Suggested | Minimum |
---|---|
Full HD Monitor | HD Ready monitor |
Speakers | Speakers |
Headphone with noise cancellation microphone | Headphone with noise cancellation microphone |
Full HD Webcam (compatible with selected OS) | Webcam (compatible with selected OS) |
The computer hardware must allow the execution of the browser without slowing down due to inadequacy of cpu and / or ram.
Network ( for each agent ):
CHAT | 10 kbit/s |
CHAT + Contact Apps (Co-Browsing, etc..) | 100 kbit/s |
VOICE + VIDEO | 300 kbit/s |
The latency of the network must be under 20 milliseconds.
Supported Operating Systems:
- Microsoft Windows 7 +;
- Apple OS X - 10.8 +;
Cookie:
Profiling:
vvcu | 3 years (renewed every visited page) | unique identifier of the user, used for reports and for the creation of a contact |
vvct | 30 minutes (renewed every visited page) | unique identifier of the visit, which is used for the report and for the creation of a contact |
Technical:
vvc_vp / vp | session | number of page views used for the rule of proactivity |
vvc_wv_ID /wv_ID | session | number of views of the widget used for the rule of proactivity |
Session:
vvc_host / host | session | primary node on which is connected the chat (may change during the contact), used to restore the chat while browsing |
vvc_mediaid / mediaid | session | configuration widget, used to represent the chat used to restore the chat while browsing |
vvc_contactid /contactid | session | id of contact, used to restore the chat while browsing |
vvc_nick / nick | session | nickname of the user, used to restore the chat while browsing |