Unified Cloud Communication and Collaboration


AnoxTech's technology is carefully architected to comply with the most recent and the most advanced new standards for Telecom and Internet services, namely with SIP, IMS and Web Service standards. Our platform contains multiple service backend as Application Servers on top of a Middleware which enables user and access management, service provisioning and integration.

This page represents the high-level view on available ANOX Tech components, both client- and serverside, outlining groups of components, and particular components, where applicable.

This list is not enumerating all the components, but only the major ones.

Download Components List Document

Client-side components

Browser: Flash-based

ANOX Tech's Flash-related client-side components for the Web are mostly dependent on ANOX Tech's Flash servers. Those servers include ANOX FlashPeer and ANOX Flash2SIP servers. All Flash-based components are fully operable on all Flash-target platforms (no OS specifics kept as principle).

All Flash components are able to operate in Flash-proprietary and Tunnel modes. Tunnel mode allows for real-time communication and binary exchange on any NAT/Firewall target-network configuration. It appears as yet another HTTP instance, and allows target administrators to continue running their security sub-systems (no modifications), as well as needs no special configuration interventions on target network, for users to utilize real-time comms (differing from any other comms platforms).

Flash A/V One-on-One
  • Peer 2 peer flash communication (audio/video)
  • Switching to offline mode with Call-2-Phone (Flash2SIP)
  • Callback to a phone (SIP or PSTN/GSM)
  • Display of contact-data through generic XML pull
  • Picture display through Flash remote source
  • Includes QoS sub-module, with bandwidth measurement and real-time adjustments or fixed bit-rates, depending on administrative settings.
  • Resizable and full-screen windows in “real-time stretch mode”

This component is a fully web-based (Flash) soft-phone, allowing:

  • Dialing external numbers (PSTN/GSM numbers)
  • Peer2Peer dialing (VoIP2VoIP)
  • Callback dialing
  • In-band, analogue and SIP-based DTMF
  • Permanent or temporary registration of the soft-phone to a SIP server, allowing receiving of the calls directly in the web-page
  • QoS sub-module, including bandwidth measurement
  • Advanced IP-Centrex (business-phone) features and call management

This component's primary function is to record an audio/video stream originating from a local PC, and storing it on-server, to be used or sent, immediately or at the later time. It's allowing for:

  • Recording of audio-stream / audio-message (or note)
  • Recording of video-stream / video-message (or note)
  • Sending such recording as embedded multimedia content within internal IM (chat) session
  • Sending such recording as embedded multimedia content on foreign-network IM (chat) sessions, such as sending to Microsoft Live users, or users on other external services.
  • Storing and sending such recording as e-mail, through sending in-line link within an e-mail message, to a Dictaphone online player, together with reference to appropriate recording and including authorization credentials.
  • Auto-url generation.
  • Playback with in-page player (Flash-based).

Possibility to be used as:

  • Standalone
  • E-mail voice/video attachment (email-voicemail with video)
  • Embedded message video attachment (including foreign messengers such as MSN, ICQ, Yahoo, etc.)
  • Within a portal
Web-Cast Streamer

Allows webcasting (sending of a stream to multiple/unlimited viewers).

  • Capture of a webcam or any analogue source and streaming over the Net
  • Full audio-video broadcast (preferred mode: unicast, for DRM and firewall issues)
  • Moderator functions (cast leader)
  • QoS sub-module, including bandwidth measurement
  • Resizeable and full-screen windows

Web-Cast streamer is a Web- /Net-Cast type of application that might be easily deployed in companies to create and broadcast webinars or other web-broadcast events. Some of its usage includes, thus:

  • Webinars
  • Trade-Fair broadcasts
  • CEO addresses to the Company
  • Training Sessions
  • Etc.

Differing from other net-cast streamers, ANOX Tech's Web-cast does not require special hardware, nor special network configuration. Anyone with a webcam (or multiple web-cams) may broadcast any event on the Net, with three types of authenticationconfigurations:

  • Closed event (only for invited UCC-users)
  • Semi-open event (users don't need to be UCC users, but must receive an invitation, via e-mail or other)
  • Open/public event (users don't need to authenticate, enough to just provide a nickname)
Web Audio/Video-Conference

In-page web-based audio-video conference component. All users may hear/see each other, directly on the web-page Includes:

  • Peer-2-Peer Flash audio-video multi-source / multi-broadcast
  • QoS sub-module, including realtime bandwidth measurement
  • Moderator functions
  • Resizeable and full-screen windows
  • User-dictated arrangement of windows
  • All-time real-time muxing of all audios, for improved bandwidth and 100% sync of conversations; muxing dependent on mute-commands by moderators, or selfmute commands by participants
  • Allows real-time and ad-hoc inclusion of conference-participants
Web Audio/Video Panel Conference

A mix of Web-Cast and A/V Video-Conference (above), adding more control for (smaller) professional-event management. Predicted for smaller events or larger conferences.

Participants are always treated as “viewers” (similar to Web-Cast principle), until are being invited to step “on the panel”. Once on the panel, all other participants may see/hear them, similarly to how they see/hear the Moderator/Leader.

Moderator is all the time in control whom and what all the participants are seeing/hearing.

Participants may “raise hand” to post questions and/or ask for participation in “the panel”.

All audios of all users on the panel are muxed, providing the “in-the-same-room” feeling, while videos (if present) are received depending on viewer preference, if videobroadcast of panel-user is allowed by the Moderator.


Click-2-dial (mini) variant of Web-Phone. Used for click-2-dial applications. Same as Web-phone except for allowing only temporary registrations, and fully interfaceless (interface resides entirely in HTML/JS, for easy customization).

Predicted for customer-support on-web-portal implementations, customer-lead generation, sales departments or simply dial-in-office implementations, etc.

Live Video and VoD Streamer

Client-side Flash component displaying either live video or VoD sources. See streamer server for more details.

Predicted for corporate VoD (Video-on-Demand) broadcasts of training videos or similar...

Multi File-Upload / Transfer

Client-side Flash component used for file-uploads and (implicitly) file-transfers to other UCC users. Can be used in real-time (real-time transfer) or in offline mode (upload for personal storage reasons or upload as “offline content” - to be downloaded later by other user).

Supports multi-transfer (more files selected at once).

Features real-time progress (directly on the web-page, within component)

Desktop/Screen Share

Desktop/Screen Share (DS Share) component is also web-based, exclusively Flashusing component, allowing for real-time sharing of user's:

  • Entire desktop
  • Selected application
  • Selected window

Real-time movements, screen-refresh etc. is broadcast to other user (or group of users), who are also viewing it simply in their web-environment. It is predicted for use of:

  • Sharing presentations (such as PowerPoint) and viewing other remote documents
  • Customer/technical support
  • Sharing screens for other purposes

Browser: dHTML / AJAX - based

All components in this group are overall browser-compatible, for all major browsers of 4th generation (IE6, IE7, IE8, IE9, Firefox, Google Chromium, Safari, Opera 7+), regardless of underlying OS.

All Web-based components are assuming full HTTP compliance, and are allowing the mentioned functionalities within browsers, without use of any binary plug-ins (by default). All components are, thus, fully operational on any NAT/Firewall target network configuration, simply because of the fact that they are fully W3C-compliant.

HTTP Presence Module

This module is designed with accessibility and portability in mind. It provides real-time (AJAX-updated) view on presence/status of online/offline users within a presence/messaging system.

Presence module works in cooperation with ANOX Presence/Messaging Servers, and in this mode is able to automatically display status of users registered on:

  • Internal Messaging (HTTP, SIP or XMPP based – 3 internal variants)
  • Foreign Professional Messaging servers (NEC Business ConnecT, IBM Lotus Same-Time, etc.), through use of plug-ins
  • Foreign Public Messaging servers (MSN, ICQ, Yahoo, Jabber/XMPP, etc.), through use of generic XMPP service

Refresh intervals are customizable. There is also an option of auto-refresh adjustments (common algorithms for activity/inactivity and adaptation of pull-frequencies depending on activity levels).

Presence/message sub-module allows:

  • Human interaction (such as IM/chat, see below)
  • System-messages (similar to WebOS or localOS messages: for example – file transfers, special requests, friendship sub-protocol, event notification, capabilities notification and other helper functions, etc.)
HTTP Chat and Group Chat

Chat and group chat modules are used for real-time chat within pure HTTP environment. Update intervals are customizable and auto-resolvable (see 1.2.1 – similar to presence methods).

This module is commonly used in:

  • 1:1 communication (two humans)
  • 1:many communication (webcasting text-support, online events)
  • many:many communication (phone and A/V conferencing)

Both modules assume also usage of History, and provide interfaces for browsable and searchable history. There is also a possibility for implicit History functionality (all dialogs saved always), which is particularly popular in corporate applications. History (both shorter- and longer-term) might be sent automatically also as a copy to user's e-mail.

Client-side chat/group-chat module also implements:

  • Customizable filters
  • Moderator functions (in event mode)
HTTP Multi-window / Tabular windows

Virtual windows module, with broadcast of windows events (internal). This module is operating on level of browser (JS) memory, and is not dependent on either browser or OS (DOM-window model, with event broadcast). Each window may be popped-out and popped-in, with preserving of the user-loginsession- status and window-state.

Directory search (Built-in and foreign directories)

Directory-search component is prepared for display and search of built-in (local) and foreign directories.
Both browsing and search are operating locally (smart background caching via AJAX) and instantly.
Larger foreign directories might be queried in “paging” mode also remotely, to avoid caching of large data-structures.

Structures of local and foreign directories are prepared for browsing/searching, and as such – DirSearch operates on (using ANOX IAM plug-ins):

  • Any DBMS via Config-Wizard
  • Any LDAP and alike (AD) structure
  • SAP Business One, SAP R3
  • Microsoft Exchange
  • Etc.
Communications Contact-Sheet

This component is a wrapper for multiple other communication and collaboration modules, including:

  • A/V comms (voice-video 1:1)
  • Web-Phone
  • Chat, File-transfer, Screen share, History
  • E-mail and SMS
  • NetDrive / Shared files (persistent)
  • Wall
  • Etc.
HTTP File Transfer (Internal and to foreign messengers)

HTTP File Transfer is a real-time file-transfer module via “mediator web service”, allowing direct transfer of files ultimately even between two firewalled entities / users. There is no limitation to the file-sizes.

HTTP FT can transfer files also to foreign networks (such as within MSN messaging, for example). Thus, files can be sent from ANOX module and received on MSN even when MSN transfer would fail because of firewall/NAT restrictions on target network.

HTTP FT transfers maybe be kept in History (implicit or explicit, same as described within Chat/Group-chat module)

HTTP FT transfer might be used in conjunction with Flash-based file-transfer client-side component, to improve end-user's GUI experience.

The Wall (Corporate Project-Oriented “Social Network”)

The Wall module is positioned in between Google Wave and Facebook's Wall, with special intention of enabling corporate project-related social networking and blogging, with rich text/attachment possibilities and group/project centric.

It is -like every blog- actually a time-independent non-real-time chat with rich multimedia capabilites.


NetDrive is file-storage, file-sharing and corporate collaboration module, allowing for easy FTP-like access to online storage without need of FTPclients (it's fully HTTPbased), and without any network/firewall restrictions.

NetDive exports sub-modules for publishing of certain files/file-types, with various privilege levels such as: Web (visible for all), Group, Private, etc.

Embedded viewers for common file-formats (documents, graphics, etc.) NetDrive can be used as start-point for any collaboration application, and is a collaboration-application on it's own.

It's internal API exposes certain folders as “special folders” (similarly to paradigms in any modern OS), for example - “Recordings” (for video-dictaphone files), etc.

Sharing is intuitive, and allows for browsing of files that are needed and available, instead of exploring entire network. Search is possible also on shared documents.

NetDrive assumes also “FileOpen”, “FileSave” and alike dialogs and APIs (for human- or application- interaction)

Corporate Address Book (Internal and foreign pass-through)

Corporate Address Book (CAB) is a module that displays and pre-caches contact information from local (ANOX Tech) or foreign data-sources (CRM, generic DBMS, LDAP/AD or other).
It is optimized for usage with ANOX pass-trough IAM plug-ins.

Most typical usage would be embedding into:

  • Soft-phones / Web-phones
  • Conference applications
  • E-mail correspondence
  • Etc.
Teleconference (phone-conference) real-time HTTP client

Teleconference HTTP module is AJAX-based remote real-time teleconference-room management. Allows real-time display and interaction (over the Web) with users in a teleconference.

Teleconference adds to “classic” conference-management modules a possibility of calling-in (inviting by dialing) other participants, in addition to all the possibilities of a “reservationless plus” conference-paradigm.

Exposed functionalities are:

  • Phone-presence in the conference room
  • Mute/kick out participants
  • Invite participants (dialing or e-mail)
  • Manage recordings
  • Embed web-phone as management-tool (optional)

Binary Client-Side Components

Binary client-side components are compiled binaries (for a specific target-platform), available most commonly as LIBs or DLLs.

Created in C/C++, with exposed client-side APIs.


Web-Helper is a resident client-side application that stays in System-tray (Windows) or is otherwise constantly present, and allows web-based-applications to interact with deeper OS-dependent functions.

These functions are including:

  • Automatic startup with system-boot
  • Preserving (safely) log-in credentials on a local PC
  • Additional communication encryption (if opted for)
  • Regular checking of keyboard/mouse/other-input activities on the local PC, in order to update status to, for example, “away”, if devices not used
  • Interaction with other binary applications and OS-message-cycle (_WM in MS Windows case, for example).
  • Etc.

Web-helper is currently available for MS Windows. Apple OSX and Linux client versions are scheduled soon.

CliGen (Generic SIP and HTTP/XML wrapper client)

“CliGen” stands for “Generic Client”, and is an of Agent, residing in end user's system (Windows), with purpose of allowing easy-to-create interfaces for all kinds of communication clients utilizing SIP or web-service technologies.

Regardless of it's compiled character, end user Graphical User Interfaces are created in DOM/JS (browser-platform), thus rapidly implemental and customizable (HTML-based interface to binary client).

Container and runtime for DOM/JS is also spawned by CliGen and controllable (custom browser window)

CliGen is used by all ANOX binary client-side applications (Business Communicator, CMA – Call Management Application, Moderator Consoles, Consumer messengers, etc.)

Full CliGen documentation, including Programmer's Guide and Client-API is available in a separate document (cligen.pdf)

Screen Capture

Screen Capture is a browser plug-in (there is also a standalone implementation separately available) for selecting and sending over the Web, in real-time – screens from a local PC.

Includes sending of entire desktop and selection and sending of DC (Device Context) of a particular application. For example, if MS PowerPoint is open, user can choose to send over immediately a snapshot of currently open PowerPoint page.

This plug-in is OS-dependent (Windows).
For multi-platform implementation (including Windows, too), see Desktop/Screen-Share Flash client (above).

BFT (Big File Transfer – Peer2Peer)

BFT is an OS-dependent plug-in and standalone app, allowing sending of huge files between two PCs (tested with files of >2GB). It was created for particular purpose of facilitating media companies in secure online transfer of large media files.

MiniSET / MicroSET / NanoSET (embedded setup)

MiniSET and other variants (names are suggesting the sizes and capabilities of this component) are used to create auto-setup or attended setup of applications that need some options while setting-up/downloading.
MiniSET is described in a separate document (MiniSET.pdf).

Mobile (Smart-phone and Tablet) Components

All above mentioned Flash and Web components are available for mobile devices (smart-phones and tablets), currently supporting the following platforms:

  • Apple iPhone (iOS)
  • Apple iPad (iOS)
  • Android-based smart-phones
  • Android-based tablets

When implemented for mobile context both Flash and Web components are re-packed as Adobe Air/Flex applications. This ensures the handling, as well as look-and-feel of local/native apps, but also significantly reduces development time and maintenance of those apps, because of single-core-code-path. Only GUI elements need to be changed for each target platform and adapted to particular device-displays, while core of the applications stays in the same code-path.

Additionally, because iOS does not support Flash at this time, this provides the only possible way, with such a single-code-path approach, to create apps also running on Apple devices.

Hence, all the above mentioned components are available also in Flex/Air implementation, plus all the Web/dHTML/JS applets are reconstructed as well in Flex/Air. Around this – a GUI wrapper is positioned, being the only element to change/adapt for various devices supported.

Limited display capabilities (screen-sizes) of various mobile devices, as well as mobile-OS limitations are dictating also some adapted behavior in these particular environments, and determining (especially on smart-phones) changes in display/render appearance. While this is adapted for smaller resolutions, no compromise was needed in terms of functionality of each component. Compromise is still, however, needed sometimes in terms of multi-threading, simply because of limited support on OS-side in some cases.