net.Console X700 (WCE7)


This resource allows you to define a net.Console X700 receptionist application on your SOP.

Release notes

Version 1.6.1 - Early deployment
  • Bugfix: Added support of foreign protocols in JxBrowser (M20916)
  • Dependency:
    • netConsole module v3.9.3 or higher

Version 1.6.0 - Early deployment
  • Feature: Added possibility to annotate the call with extra informations (M13662)
  • Dependency:
    • netConsole module v3.8.0 or higher

Version 1.5.0 - General deployment
  • Bugfix: Fix unsupported value in Direct receptionist extension
  • Dependency:
    • net.Console module v3.2.3+

Version 1.4 - General deployment
  • Feature: added the possibility to change the display of line 1 (M0003682)
  • Dependency:
    • net.Console module v3.2.3+

Version 1.3 - General deployment
  • Feature: added possibility to override preferences by providing a property file on an external url.
  • Feature: added optionial list of voicemailboxes to be added to the net.Console
  • Feature: added Startup URL
  • Dependency:
    • net.Console module v3.2+

Version 1.2 - General deployment
  • New version for net.Console 2.0

Version 1.1 - General deployment
  • Error tab removed from the list of possible resources

Version 1.0 - General deployment

Version 0.0 - General deployment
  • Feature: New version for net.Console 2.0

Resource configuration interface

GUI unavailable.

Desktop Application parameters

Application tabs

The applications tabs can offer 3 types of information

  • Static: A static view can be compared with a classic Bookmark. When the tab is clicked upon, the net.Console will display the website configured in the URL field.
  • Directory: A web application can be triggered by clicking on a contact in a Directory. A number of sources of information can be passed on to the web application:
    • first name: <fn>
    • last name: <ln>
    • user defined fields 1 through 10: <user_1> to <user_10>
    • Example: Triggering a calendar to find out if the contact is in a meeting : http://your_agenda_webapplication/first=<fn>&last=<ln>
  • caller ID: A web application can be trigger by an incoming call. The caller ID will be used as a parameter to the web application. The exact parameter name that can be used in a query is <ext> .
    • Example: Looking up a name for an incoming calling number : http://your_CRM_webapplication/extnumber=<ext>

Each tab has its own label which will be displayed when hovering over the tab icon in the net.Console.

net.Console Queues

The net.Console works with 3 queues of which usually only 2 will be used.
  • Queue 1 : Select the main queue with all new incoming calls . ALERT!Make sure you choose a queue starting with "AQA" and not a parameter containing the queue.
  • Queue 3 : Select the personal queue of the receptionist ALERT!Make sure you choose a queue starting with "AQA" and not a parameter containing the queue.

Have a look at AppNoteNetConsoleSetup for more information regarding queue configuration.

Short name configuration

Typing a full name can sometimes be too time consuming. The net.Console has the ability to accept a shortname as input.

A shortname is a abbreviated version of the first name and last name. The first name prefix length and last name prefix length determine how many characters will be selected to be part of the short name. The separator distinguishes the first name from the last name.

  • first name prefix length = 1
  • last name prefix length = 2
  • separator = none
  • John Doe will become "jdo"
  • Jack Russel will become "jru"
  • Peter Jackson will become "pja"

By applying the shortname system, a receptionist can simply type "pja" and the directory will only show contacts where the first name begins with "p" and the last name with "ja". Prefix lengths can be changed to correspond with specific company conventions.


The timers will determine how many seconds will have to pass before the net.Console takes a certain action when there are calls in the corresponding state. 60 seconds is a good average for all timers.

Additional settings

  • Pending channels display. When "yes", the channel will be displayed in the pending channels display as long as the destination phone does not pick up. When "no", the channel will not be displayed.
  • Direct receptionist extension. This option identifies the receptionist by his/her extension and creates the link between the net.Console and his/her phone.
  • Global property override url: This give the possibility to have a centralized document where the configuration of several net.Consoles is stored.
  • Voicemails extensions: It give the ability to supervise several extensions' voicemails
  • Line 1 display: The net.Console will use this string in order to customize the information displayed in the Line 1 overview area. Specific strings will be replaced by a variable content. Recommended value is DN (CN). If left blank, the default is DN (CN) | CI
    • DN stands for "Display Name". It will be replaced by the last known caller name.
    • CN stands for "Caller Number" . It will be replaced by the last known caller number.
    • CI stands for "Contact Information". It will be replaced by the Caller name corresponding to the caller number as found in the database. In case of no result the initial Caller name will be shown which is the Caller number if nothing else specified.
  • Call Types: This option allows the receptionist to set a flag on a call in net.Console. This flag can be retrieved afterwards from reportCDR. Flags are comma separated values like "sales,technical". Empty flag is also allowed (",sales,technical").
  • Call Info: This option allows the receptionist to set arbitrary information on a call in net.Console. The information could be also retrieved from reportCDR.
  • Web browser foreign protocols : Use the desktop instead of the web browser when dealing with foreign protocols. Define protocols in a comma separated values list like "DynamicsNAV,mailto".
Copyright © Escaux SA