Configure the Action button

The Action button can be found as the red button located at the top-right of the phone. It allows phone users to quickly access the designated service, such as emergency service or custom service. You can associate the button with a service for users.

1

Access the phone administration web page.

2

Select Voice > Phone.

3

Navigate to the Action Button section and configure the following parameters to associate the Action button with a service.

Table 1. Parameters for the Action button
ParameterDefault and optionsDescription
Action Button Function

Default: Off

Options: Off, Emergency Call, Custom

You can configure the button with a specific service.

  • Off: When set to Off, the Action button on the phone will not function.
  • Emergency Call: Users can use the Action button to place an emergency call, if configured.
  • Custom: Users can use the Action button to access the custom service, if configured.

When you set the field to Emergency Call, make sure that you enter the phone number or URI of the emergency service in the Action Button Service Destination field. When set to Custom, make sure that you enter the URL of the service.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Action_Button_Function ua="na">Custom</Action_Button_Function>
Action Button Service Name

Default: Empty

Optionally specify a name for the service associated with the Action button. This name will be displayed in the on-screen message when the user presses the button, indicating which service will be triggered.

If you don't specify a name, the default name will be Emergency call, Silent emergency call, or Custom action based on your selection in the Action Button Function field.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Action_Button_Service_Name ua="na">Panic alert</Action_Button_Service_Name>
Action Button Service Destination

Default: Empty

Provide the phone number or the URI for emergency call, or the URL for the custom service.

If you enable the Action button without setting a valid service destination, the user on the phone will see a message prompting for configuration. After the user closes this notification, the warning icon will persist in the header of the phone screen until the button is properly configured or disabled.

If you enter a service URL, the URL must start with http:// or https://. For example, https://10.11.20.159/path/service.xml.

Phone numbers cannot be used as destinations for Custom services. If you configure the Action Button as Custom and enter a phone number as the service destination, an alert message will display on the phone indicating that the button is unconfigured.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Action_Button_Service_Destination ua="na">https://10.11.20.159/path/service.xml</Action_Button_Service_Destination>
Service Trigger

Default: Single Press

Options: Single Press, Long Press, Press 3 times

Choose how users can place an emergency call or initiate a custom service using the phone's Action button.

Single Press: Press the Action button to trigger the associated call or service.

Long Press: Press the Action button down for at least 2 seconds to trigger the associated call or service.

Press 3 times: Press the Action button three times with intervals of less than 2 seconds between each press to trigger the associated call or service.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Service_Trigger ua="na">Single Press</Service_Trigger>
Dial Out Delay

Default: 5

Options: 0 - 30

Set the timeout period, in seconds, for the phone to initiate an emergency call or a custom action after the Action button is pressed.

Set it to 0 if you prefer the phone to place the call or initiate an action immediately upon detecting the trigger, as specified by a single press, long press, or triple presses on the button.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Dial_Out_Delay ua="na">5</Dial_Out_Delay>
Silent Emergency Call

Default: Disabled

Options: Enabled, Disabled

This setting works only when the Action Button Function is set to Emergency Call.

Silent emergency call is designed for discreet assistance in dangerous situations. It enables users to seek help without making any noise.

  • When enabled, users are able to place one-way calls with the Action button.

    After the silent emergency call is placed, only the other party can end the call. To avoid drawing attention during the ongoing call, the screen on phone 9841 will freeze, while the screen on phone 9851, 9861, and 9871 will be turned off.

  • When disabled, the emergency call functions as a two-way call, similar to other outgoing calls.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Silent_Emergency_Call ua="na">Disabled</Silent_Emergency_Call>
4

When done, click Submit All Changes.

Configure your phone for power saving (Office Hours)

Three power-saving options are available on the phone to reduce power consumption during periods of inactivity.

Display-Off Mode

In Display-Off Mode, the phone turns off the screen to save power outside of the designated working hours. When the Office Hours feature is enabled, the phone goes into Display-Off Mode after working hours. You can light up the display by pressing any key on the phone. The display remains on until the phone has been in idle for a designated length of time, then it turns off automatically.

Deep Sleep Mode

In Deep Sleep Mode, the phone automatically powers down during the designated periods. You can choose to enable Deep Sleep Mode exclusively for non-workdays, or for both non-workdays and non-working hours on workdays. To wake up the phone, press the Select button on the Navigation Cluster.

When the phone is in Deep Sleep Mode, the Action button on the top-right of the device isn't accessible.

By default, the Office Hours feature is enabled on your phone. The default office hours are set to 7:00 to 19:00 from Monday to Friday. The phone turns off the screen outside of the designated hours. You can customize working hours, workdays, and the power-saving mode outside of office hours.

1

Access the phone administration web page.

2

Select Voice > User.

3

Customize working hours and workdays to reflect the business hours of your users.

Table 2. Parameters for Office Hours
ParameterDefault and optionsDescription
Office Hours Enabled

Default: True

Options: False, True

Set this field to True to enable the Office Hours feature for Cisco Desk Phone 9800 Series.

The Office Hours feature is designed to minimize power usage during inactivity periods on the phone. You can configure the phone to automatically turn off the screen (Display-Off Mode) or power off (Deep Sleep Mode) outside of the designated working periods.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Office_Hours_Enabled ua="na">True</Office_Hours_Enabled>
Work Days

Default: Monday through Friday

Customize the workdays by specifying the desired days.

During non-workdays, the phone will automatically turn off the screen. By default, workdays are set from Monday to Friday.

This setting also applies to Deep Sleep Mode, if enabled. If you choose to enable Deep Sleep Mode exclusively for non-workdays, the phone will power off during those days. If you enable Deep Sleep Mode for all days, the phone will power off during both non-workdays and non-working hours on workdays.

Set working hours for workdays using the Working Hours Start and Working Hours End fields.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Work_Days ua="na">Monday|Tuesday|Wednesday|Thursday|Friday</Work_Days>
Working Hours Start

Default: 07:00

Set the start time for working hours using the 24-hour format. Outside of the specified working hours, the phone will automatically turn off the screen, or enter Deep Sleep Mode only when Deep Sleep Enabled is set to All Days.

Examples: 09:00 for 09:00 am; 17:30 for 05:30 pm

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Working_Hours_Start ua="na">06:00</Working_Hours_Start>
Working Hours End

Default: 19:00

Set the end time for working hours using the 24-hour format. Outside of the specified working hours, the phone will automatically turn off the screen, or enter Deep Sleep Mode only when Deep Sleep Enabled is set to All Days.

Examples: 09:00 for 09:00 am; 17:30 for 05:30 pm

Ensure that the interval between the start and end time longer than 60 minutes.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Working_Hours_End ua="na">21:00</Working_Hours_End>
4

To customize the settings for non-working hours, configure the following parameters in the Outside Office Hours Deep Sleep section.

You can set up the idle timeout for Display-Off Mode and customize the Deep Sleep Mode settings as needed.

Table 3. Parameters for Outside Office Hours
ParameterDefault and optionsDescription
Deep Sleep Enabled

Default: False

Options: False, Non-work Day Only, All Days

Enable or disable Deep Sleep Mode on the phone. When enabled, this feature automatically powers off the phone outside of the designated office hours.

This option works only when the Office Hours is enabled.

When set to False, the phone will not enter Deep Sleep Mode.

When set to Non-work Day Only, the phone will power off exclusively on non-workdays. For the specified workdays, the phone will turn off the screen outside of the specified working hours.

When set to All Days, the phone will power off during both non-workdays and non-working hours on workdays.

Set working hours for workdays using the Working Hours Start and Working Hours End fields.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Deep_Sleep_Enabled ua="na">Non-work Day Only</Deep_Sleep_Enabled>
Enable Audible Alert

Default: False

Options: False, True

Enable or disable the phone to play audio tone to alert the user before it enters Deep Sleep Mode.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Enable_Audible_Alert ua="na">False</Enable_Audible_Alert>
Phone On Time Before Working Hour Start (mins)

Default: 60

Options: 0 - 360

Set the timeout period for the phone to wake up from Deep Sleep Mode before the time specified in the Working Hours Start field. If you want the phone to wake up until working hours start, set it to 0.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Phone_On_Time_Before_Working_Hour_Start__mins_ ua="na">12</Phone_On_Time_Before_Working_Hour_Start__mins_>
Phone Off Time After Working Hour End (mins)

Default: 60

Options: 0 - 360

Set the timeout period for the phone to automatically power off after the time specified in the Working Hours End field. If you want the phone to enter Deep Sleep Mode immediately after working hours, set it to 0.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Phone_Off_Time_After_Working_Hour_End__mins_ ua="na">12</Phone_Off_Time_After_Working_Hour_End__mins_>
Random Early Wakeup (mins)

Default: 60

Options: 0 - 60

Set the time interval for the phone to wake up before its regular schedule. It helps distribute the load of connection and registration requests when a large number of phones power on simultaneously.

The actual wakeup time is calculated as: Working Hours Start - Phone On Time Before Working Hour Start - Random Early Wakeup

Example

If the following values are set:

  • Working Hours Start: 8:00 am
  • Phone On Time Before Working Hour Start: 30 mins
  • Random Early Wakeup: 60 mins

the phone can randomly wake from Deep Sleep Mode at anytime between 6:30 am 7:30 am.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Random_Early_Wakeup__mins_ ua="na">60</Random_Early_Wakeup__mins_>
Random Delay to Sleep (mins)

Default: 10

Options: 0 - 10

Set a time interval for the phone to enter Deep Sleep Mode after its scheduled power-off time.

The actual sleep time is calculated as: Working Hours End + Phone Off Time After Working Hour End + Random Delay to Sleep

Example

If the following values are set:

  • Working Hours End: 5:00 pm
  • Phone Off Time After Working Hour End: 30 mins
  • Random Delay to Sleep: 10 mins

the phone can randomly power off at anytime between 5:30 pm and 5:40 pm.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Random_Delay_to_sleep_mins_ ua="na">10</Random_Delay_to_sleep_mins_mins_>
Idle Timeout (mins)

(for Deep Sleep Mode)

Default: 30

Options: 1 - 60

This setting applies to the following two scenarios:

  • Before the phone enters a scheduled Deep Sleep Mode

    Ten minutes before the scheduled deep sleep, a message pops up to notify the user that the phone will power off in ten minutes, and a countdown starts. When it times out, the phone powers off.

    During the countdown period, if there is any activity such as an incoming call, firmware upgrade, or provisioning resync, the countdown will restart. For example, if you have set this field to 20, the countdown will restart in 20 minutes after the activities are completed.

  • After being manually awakened from Deep Sleep Mode

    For example, if you have set this field to 20, after being idle for 20 minutes, a message pops up to notify the user that the phone will power off in ten minutes, and a countdown starts. When it times out, the phone powers off.

    During the countdown period, if there is any activity such as an incoming call, firmware upgrade, or provisioning resync, the countdown will restart in 20 minutes after the activities are completed.

If a user interacts with the phone during the countdown period, such as answering or declining calls or pressing keys, the phone will not enter Deep Sleep Mode for the rest of the day.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Idle_Timeout__mins_ ua="na">52</Idle_Timeout__mins_>
LED Indicator In Display Off Mode

Default: Enabled

Options: Enabled, Disabled

This field is available in the Outside Office Hours Display Off section.

This setting determines whether to turn off the Front Arc LED when the phone enters Display Off Mode. When set to enabled, the Front Arc LED is off during non-working hours. When set to disabled, the Front Arc LED remains illuminated after the phone enters Display Off Mode.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<LED_Indicator_In_Display_Off_Mode ua="na">Enabled</LED_Indicator_In_Display_Off_Mode>
Idle Timeout (mins)

for Display-Off Mode

Default: 5

Options: 1 - 60

This field is available in the Outside Office Hours Display Off section.

Set the timeout period in minutes for the phone to automatically turn off the screen after being awakened during Display-Off Mode.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Display_Off_Idle_Timeout__mins_ ua="na">5</Display_Off_Idle_Timeout__mins_>
5

When done, click Submit All Changes.

Enable hoteling on a phone

When you enable the hoteling feature of BroadSoft on the phone, the user can sign in to the phone as a guest. After the guest sign out of the phone, the user will switch back to the host user.

You can also enable hoteling service from the server. For more information, see Cisco BroadWorks Partner Configuration Guide.

When you enable hoteling:

  • For 9841, 9851, and 9861 phones A phone with multiple lines displays Hoteling softkey on the phone home screen for each line that has hoteling enabled.

    for 9871 A phone with multiple lines displays Guest in softkey on the phone home screen for each line that has hoteling enabled. You see this line when you press More (…) next to the line.

  • A phone with single line displays Guest in softkey on the phone home screen.

Before you begin

On the server:

1

Access the phone administration web page.

2

Select Voice > Ext [n] (where [n] is the extension number).

3

In the Call Feature Settings section, set Enable Broadsoft Hoteling parameter to Yes.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Enable_Broadsoft_Hoteling_1_ua="na">Yes</Enable_Broadsoft_Hoteling_1>

Options: Yes and No

Default: No

4

Set the amount of time (in seconds) in Hoteling Subscription Expires paramter that specifies how often the phone sends the SUBSCRIBE message.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Hoteling_Subscription_Expires_1_ua="na">3600</Hoteling_Subscription_Expires_1>

Valid values: An integer from 10 through 86400

Default: 3600

When the parameter is set to 0, the default 3600 is used.

5

Click Submit All Changes.

Phone settings sync

DND and call forward status sync

You can configure the settings on the phone administration web page to enable status synchronization of Do Not Disturb (DND) and call forward between the phone and the server.

There are two ways to synchronize the feature status:

  • Feature Key Synchronization (FKS)

  • XSI Synchronization

FKS uses SIP messages to communicate the feature status. XSI Synchronization uses HTTP messages. If both FKS and XSI synchronization are enabled, FKS takes precedent over XSI synchronization. See the table below for how FKS interacts with XSI synchronization.

Table 4. Interaction Between FKS and XSI Synchronization

Feature Key Sync

XSI DND Enabled

XSI CFWD Enabled

DND Sync

CFWD Sync

Yes

Yes

Yes

Yes (SIP)

Yes (SIP)

Yes

No

No

Yes (SIP)

Yes (SIP)

Yes

No

Yes

Yes (SIP)

Yes (SIP)

No

Yes

Yes

Yes (HTTP)

Yes (HTTP)

No

No

Yes

No

Yes (HTTP)

No

Yes

No

Yes (HTTP)

No

No

No

No

No

No

Enable DND and Call Forward status sync with Feature Key Sync (FKS)

When you enable the Feature Key Synchronization (FKS), the settings of call forward and do not disturb (DND) on the server are synchronized to the phone. The changes in DND and call forward settings made on the phone will also be synchronized to the server.

When FKS is enabled on a line, the line get the DND and Call Forward settings from the server and doesn't sync with the settings on Voice > User tab.

1

Access the phone administration web page.

2

Select Voice > Ext [n] (where [n] is the extension number).

3

In the Call Feature Settings section, set the Feature Key Sync field to Yes.

4

Click Submit All Changes.

Enable call forward status sync via XSI service

When call forward sync is enabled, the settings related to call forward on the server are synchronized to the phone. The changes in call forward settings made on the phone will also be synchronized to the server.

Before you begin

  • Configure the XSI host server and the corresponding credentials on the Voice > Ext (n) tab.

    • When using Login Credentials for XSI server authentication, enter XSI Host Server, Login User ID, and Login Password in the XSI Line Service section.

    • When using SIP Credentials for XSI server authentication, enter XSI Host Server and Login User ID in the XSI Line Service section, and Auth ID and Password in the Subscriber Information section.

  • Disable Feature Key Sync (FKS) in Call Feature Settings section from Voice > Ext (n) .

1

Access the phone administration web page.

2

Select Voice > Ext [n] (where [n] is the extension number).

3

In the XSI Line Service section, set the CFWD Enable parameter to Yes.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<CFWD_Enable_1_ ua="na">Yes</CFWD_Enable_1_>

Options: Yes and No

Default: No

4

Click Submit All Changes.

Enable DND status sync via XSI service

When do not disturb (DND) sync is enabled, the DND setting on the server is synchronized to the phone. The changes in DND setting made on the phone will also be synchronized to the server.

Before you begin

  • Configure the XSI host server and the corresponding credentials on the Voice > Ext (n) tab.

    • When using Login Credentials for XSI server authentication, enter XSI Host Server, Login User ID, and Login Password in the XSI Line Service section.

    • When using SIP Credentials for XSI server authentication, enter XSI Host Server and Login User ID in the XSI Line Service section, and Auth ID and Password in the Subscriber Information section.

  • Disable Feature Key Synchronization (FKS) in Call Feature Settings section from Voice > Ext (n).

1

Select Voice > Ext [n] (where [n] is the extension number).

2

In the XSI Line Service section, set the DND Enable parameter to Yes.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<DND_Enable_1_ ua="na">Yes</DND_Enable_1_>

Options: Yes and No

Default: No

3

Click Submit All Changes.

Configure conference settings for phones

The following sections provide information on how to configure the conference service for your phones.

Enable conference service

Enable the conference service for your phones so that users can initiate or join multiple-way calls using their phone lines.

1

Access the phone administration web page.

2

To enable conference service for the phone do the following:

  1. Select Voice > Phone.

  2. Under Supplementary Services, choose Yes for the Conference Serv parameter.

    You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

    <Conference_Serv ua="na">Yes</Conference_Serv>

    Options: Yes and No

    Default: Yes

3

Specify the conference bridge URL for your desired line:

  1. Select Voice > Ext(n)

  2. Enter the Conference Bridge URL in this format:

    user@IPaddress:port
4

Click Submit All Changes.

Enable Webex calendar service

If you want to enable the phone to have the ability to join Webex calendar meetings, do the following:

Before you begin

Your phone has been registered to Webex Calling.

1

Access the phone administration web page.

2

Select Voice > Phone.

3

In the Webex section, set the field Calendar Enable.

Set Yes or No to enable or disable the Webex calendar service on the phone.

Options: Yes|No; Default: Yes

You can also configure the parameters in the configuration file (cfg.xml) by entering the strings in this format:

<Webex_Calendar_Enable ua="na">Yes</Webex_Calendar_Enable>

4

Click Submit All Changes.

Enable call recording with SIP REC

You can enable call recording on a phone so that your user can record an active call. The recording mode configured on the server controls the display of the recording softkeys for each phone. In the Programmable Softkeys section, by default, the following strings are added in the Connected Key List and Conferencing Key List fields. crdstart;crdstop;crdpause;crdresume

Table 5. Recording Mode and Recording Softkeys
Recording Mode in ServerRecording Softkeys Available on the Phone

Always

No softkeys available.

Your user can't control recording from the phone. Recording starts automatically when a call is connected.

Always with Pause/Resume

PauseRec

ResRec

When call is connected, user can pause the recording and resume the recording.

On Demand

Record

PauseRec

ResRec

When a call is connected, recording starts automatically but the recording is not saved until the user presses the Record softkey. Your user sees a message when recording state changes.

On Demand with User Initiated Start

Record

PauseRec

StopRec

ResRec

The recording only starts when your user presses the Record softkey. Your user sees a message when recording state changes.

Never

No recording softkeys are available, hence user will not be able to record calls.

1

Access the phone administration web page.

2

Select Voice > Phone.

3

In the Supplementary Services section, click Yes or click No to enable or disable the Call Recording Serv parameter.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Call_Recording_Serv ua="na">Yes</Call_Recording_Serv>

Options: Yes and No

Default: No

4

Click Submit All Changes.

Configure multicast paging

You can set up multicast paging to allow users to send paging messages to other phones. The page can go to all phones or a group of phones in the same network. Any phone in the group can initiate a multicast paging session. The page is received only by the phones that are set to listen for the paging group.

A phone can be added to up to10 paging groups. Each paging group has a unique multicast port and number. The phones within a paging group must subscribe to the same multicast IP address, port, and multicast number.

You configure the priority for the incoming page from a specific group. When a phone is active and an important page must be played, the user hears the page on the active audio path.

When multiple paging sessions occur, they are answered in chronological order. After the active page ends, the next page is automatically answered. When do not disturb (DND) applies to all lines on a phone instead of a specific line, the phone ignores any incoming paging.

You can specify a codec for the paging to use. The supported codecs are G711a, G711u, G722, and G729. If you don't specify the codec, paging uses G711u by default.

You can also enable phones to receive pages from a server to optionally display an image or other UI elements. With this feature, an XML service can be invoked during a multicast paging. To enable this feature, configure the parameter XML Application Service URL and add "xmlapp=yes" in the paging group scripts from Voice > Phone. For more information about the parameters, see XML applications configuration for phones on BroadWorks and Parameters for multiple paging group.

You can also configure the parameters in the phone configuration file with XML(cfg.xml) code. To configure each parameter, see the syntax of the string in Parameters for multiple paging group.

Before you begin

  • Make sure that your network supports multicast so that all devices in the same paging group are able to receive paging.
  • For Wi-Fi networks, enable and properly configure the access point for multicast.
  • Make sure that all the phones in a paging group are in the same network.
1

Access the phone administration web page.

2

Select Voice > Phone.

3

Go to the Multiple Paging Group Parameters section.

4

Enter multicast paging scripts as defined in the following table of Parameters for multiple paging group.

5

Click Submit All Changes.

Parameters for multiple paging group

The following table defines the function and usage of the multiple paging group parameters in the phone administration page.

It also defines the syntax of the string that is added in the phone configuration file (cfg.xml) to configure a parameter.

Table 6. Multiple paging group parameters
ParameterDescription
Group 1 Paging Script – Group 10 Paging Script

Enter a string to configure the phone to listen for and initiate multicast paging. You can add a phone to up to 10 paging groups. Enter the script in this format:

  • Multicast paging:

    pggrp=<multicast-address>:<port>;<name=group_name>;<num=multicast_number>; <listen=boolean_value>;<pri=priority_level>;<codec=codec_name>;

    Example script:

    pggrp=224.168.168.168:34560;name=Group_1;num=800;listen=yes;pri=1;

  • Multicast paging with XML application support:

    pggrp=<multicast-address>:<port>;<name=group_name>;<num=multicast_number>; <listen=boolean_value>;<pri=priority_level>;<codec=codec_name>;<xmlapp=boolean_value>;<timeout=seconds>

    Example script:

    pggrp=224.168.168.168:34560;name=Group_1;num=800;listen=yes;pri=1;xmlap- p=yes;timeout=3600;

  • Multicast IP address (multicast-address) and port (port)—Enter the multicast IP address and the port specified on your paging server. The port number must be unique for each group and an even number within 1000 and 65534.

    Make sure that you set the same multicast IP address and port for all the phones within a paging group. Otherwise, the phones can't receive paging.

  • Paging group name (name)—Optionally enter the name of the paging group. The name helps you identify the paging group the phone is in when you have multiple paging groups.
  • Multicast number (num)—Specify the number for the phone to listen for multicast paging and initiate a multicast paging session. Assign the same multicast number to all the phones within the group. The number must comply to the dial plan specified for the line to initiate a multicast.
  • Listen status (listen)—Specify whether the phone listens for paging from this group. Set this parameter to yes to make the phone listen for the paging. Otherwise, set it to no, or don't include this parameter in the script.
  • Priority (pri)—Specify priority between paging and phone call. If you don't specify the priority or don't include this parameter in the script, the phone uses priority 1. The four priority levels are:

    0: Paging takes precedent over phone call. When the phone is on an active call, an incoming paging places the active call on hold. The call resumes when the paging ends.

    1: When the phone receives an incoming paging on an active call, the user hears the mix of the paging and the call.

    2: The user is alerted with the paging tone when receiving an incoming paging on an active line. The incoming paging isn't answered unless the active call is put on hold or ends.

    3: The phone ignores the incoming paging without any alert when the phone is on an active call.

  • Audio codec (codec)—Optionally specify the audio codec for the multicast paging to use. The supported codecs are G711a, G711u, G722, and G729. If you don't specify the codec or don't include the codec parameter in the script, the phone uses G711u codec.
  • XML application (xmlapp)—Specify whether the phone contacts the XML application server when it receives audio over paging group. Set this parameter to Yes to make the phone invoke the XML application from multicast paging. Otherwise, set it to no.

    Make sure that the parameter XML Application Service URL in XML services is configured, see XML services for details.

    In the XML URL, the macro MCASTADDR must be configured to distinguish it from the normal multicast paging. For example, http(s)://<url>?mcast=$MCASTADDR

  • Timeout—Optionally specify the timeout (in seconds) for the XML application messages that display on the phone screen. If the parameter is not configured, the XML application messages disappear along with the paging.

    Typically, the XML application ends after the timeout is reached, in regardless of the paging call. If the paging call is still active, only the XML application ends.

    A new paging closes the XML application of the last paging, if the XML application is not closed when the last paging ended.

In the phone configuration file with XML(cfg.xml), enter a string in this format:

<Group_1_Paging_Script ua="na">pggrp=224.168.168.168:34560;name=Group_1; num=800;listen=yes;pri=1;codec=g722;xmlap- p=yes;timeout=3600;</Group_1_Paging_Script>

Default: Empty

Configure a phone to answer pages automatically

The paging feature enables a user to directly contact another user by phone. If the phone of the person being paged has been configured to answer pages automatically, the phone does not ring. Instead, a direct connection between the two phones is automatically established when paging is initiated.

You can also configure the parameters in the phone configuration file with XML(cfg.xml) code.

Before you begin

1

Access the phone administration web page.

2

Select Voice > User.

3

In the Supplementary Services section, choose Yes for the Auto Answer Page parameter.

You can configure this parameter in the phone configuration XML file (cfg.xml) by entering a string in this format:

<Auto_Answer_Page ua="na">Yes</Auto_Answer_Page>

Options: Yes and No

Default: Yes

4

Click Submit All Changes.