Skip to end of metadata
Go to start of metadata

Overview

The built-in applications, and their associated hard and soft keys on the D4X, D50, D6X, & D70 can now be redirected to user defined applications as of firmware version 2_7_1.

The built-in application names below are the actual names passed into the Javascript application's digium.app.foreground event as the params.eventData.app string. The built-in applications which can be redirected are as follows...

phonemenu

Shows all phone settting screens. Mapped to the check key (dpad.select) and Menu key (fn.menu D70 only). This application is not normally redirected, but it can be in cases where minimal phone setting access is desired, or in cases where phone setting access is completely disabled, and a simple disabled screen is shown.

contacts

Shows contents of the contact file /nvdata/contact_lists/serialized_contacts.xml. Mapped to soft key 2 when conferencing or transferring a call, and the Contacts key (fn.dir D70 only).

status

Shows status screen when <appconfig id=”status”> has the <full_application/> tag, else status is simply toggled between active and DND. Mapped to soft key 3 on the account info
screen, and the status key (fn.status D70 only).

Please note that if the status app is redirected that the <auto_start/> tag should NOT be included in the <appconfig> tag for the status app, otherwise the built-in status app will
be automatically loaded and consume memory, even though it will never be executed. All that is required to ensure the redirected status app be executed (instead of the status being toggled), is: <appconfig id=”status”><full_application/></appconfig>

voicemail

Shows the voicemail application when the account's visual_voicemail=”1” element is set, else dials the number in the accounts voicemail=”” element to access voicemail. Mapped to the message key (fn.msg on all phone models).

Other applications

While forward, parking, and queues are also built-in applications, they are not hard mapped to any keys, and if they are not listed in any key maps or <appconfig> tags, they will not be listed or executed.

How to Redirect

Any single application can be redirected to a replacement app, or all of them can be redirected to a singe user application if so desired. To enable redirection a new
<appredirect> tag group has been added to the configuration.

The id=”” element in the <redirect> tag below is the application name normally executed (and the name passed into the application as the params.evenData.app string). The app=”” element is the name of the actual app executed. The actual app executed must also have a corresponding <appconfig> tag in the configuration, as it normally would, so that it gets loaded and can be executed. In the case below, the account's visual_voicemail=”1” element would also need to be set so that the voicemail app is executed, instead of a number being dialed.

Redirection Phone Config Example

The following configuration excerpt shows how all the internal apps can be redirected to a single user application. It also has the applications mapped to soft keys. In this case however the application's foreground function must detect which application is being executed by comparing the params.eventData.app string.

 

Redirection App Config Example

The following is an example of a my_apps.js Javascript app, and how to handle the app name passed in from the app redirect.

 

 

  • No labels