Webex for Cisco BroadWorks

Configuration Guide
Release 43.8
Document Version 1
Table of Contents

1 Summary of Changes ................................................................................................................... 1

1.1 Changes for Release 43.8, August 2023 .................................................................................... 1
1.2 Changes for Release 43.7, July 2023 ......................................................................................... 1
1.3 Changes for Release 43.6, June 2023........................................................................................ 1
1.4 Changes for Release 43.5, May 2023......................................................................................... 1
1.5 Changes for Release 43.4, April 2023 ........................................................................................ 1
1.6 Changes for Release 43.3, March 2023 ..................................................................................... 1
1.7 Changes for Release 43.2, February 2023 ................................................................................. 1
1.8 Changes for Release 43.1, January 2023 .................................................................................. 2
1.9 Changes for Release 42.12, December 2022 ............................................................................ 2
1.10 Changes for Release 42.11, November 2022 ............................................................................ 2
1.11 Changes for Release 42.10, October 2022 ................................................................................ 2
1.12 Changes for Release 42.9, September 2022 ............................................................................. 2
1.13 Changes for Release 42.8, August 2022 .................................................................................... 2
1.14 Changes for Release 42.7, July 2022 ......................................................................................... 2
1.15 Changes for Release 42.6, June 2022........................................................................................ 3
1.16 Changes for Release 42.5, May 2022......................................................................................... 3
1.17 Changes for Release 42.4, April 2022 ........................................................................................ 3
1.18 Changes for Release 42.3, March 2022 ..................................................................................... 3
1.19 Changes for Release 42.2, February 2022 ................................................................................. 3
1.20 Changes for Release 42.1, January 2022 .................................................................................. 3
2 Changes for Configuration Files ................................................................................................. 4
2.1 Changes for Configuration Files for Release 43.8 ...................................................................... 4
2.2 Changes for Configuration Files for Release 43.7...................................................................... 4
2.3 Changes for Configuration Files for Release 43.6...................................................................... 4
2.4 Changes for Configuration Files for Release 43.5 ...................................................................... 4
2.5 Changes for Configuration Files for Release 43.4 ...................................................................... 5
2.6 Changes for Configuration Files for Release 43.3 ...................................................................... 6
2.7 Changes for Configuration Files for Release 43.2 ...................................................................... 6
2.8 Changes for Configuration Files for Release 43.1 ...................................................................... 7
2.9 Changes for Configuration Files for Release 42.12.................................................................... 7
2.10 Changes for Configuration Files for Release 42.11.................................................................... 8
2.11 Changes for Configuration Files for Release 42.10.................................................................... 8
2.12 Changes for Configuration Files for Release 42.9 ...................................................................... 9
2.13 Changes for Configuration Files for Release 42.8 ...................................................................... 9
2.14 Changes for Configuration Files for Release 42.7 .................................................................... 10
2.15 Changes for Configuration Files for Release 42.6 .................................................................... 10
2.16 Changes for Configuration Files for Release 42.5 .................................................................... 10
2.17 Changes for Configuration Files for Release 42.4 .................................................................... 10

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE iii

 2.18 Changes for Configuration Files for Release 42.3.................................................................... 11
2.19 Changes for Configuration Files for Release 42.1.................................................................... 13
3 Introduction ................................................................................................................................... 14
4 Installation ..................................................................................................................................... 15
4.1 Localized Client Download ......................................................................................................... 15
4.2 Android Client .............................................................................................................................. 15
4.3 iOS Client..................................................................................................................................... 15
4.4 Desktop Client ............................................................................................................................. 15
5 Device Management .................................................................................................................... 16
5.1 Device Management Tags ......................................................................................................... 16
5.2 Partial Match Enhancements for Device Type Selection ......................................................... 17
5.3 Client Configuration .................................................................................................................... 18
5.4 Deployment of config-wxt.xml .................................................................................................... 18
5.5 Configuration File (config-wxt.xml)............................................................................................. 18
5.6 System Default Tags .................................................................................................................. 19
5.7 Cisco BroadWorks Dynamic Built-in System Tags .................................................................. 19
6 Custom Tags................................................................................................................................. 22
6.1 Common Features ...................................................................................................................... 32
6.1.1 Change Basic SIP Server Settings ................................................................................... 32
6.1.2 SIP Over TLS and Secure Real-time Transport Protocol ............................................... 34
6.1.3 3GPP SIP Headers for SRTP ........................................................................................... 37
6.1.4 Force TCP, TLS or UDP Usage and Keepalives ............................................................ 37
6.1.5 Configurable Timeout for Opening SIP Socket................................................................ 39
6.1.6 Dynamic SIP Proxy Discovery .......................................................................................... 40
6.1.7 Preferred-Port Usage for SIP ............................................................................................ 45
6.1.8 SIP Failover and Failback ................................................................................................. 45
6.1.9 SIP SUBCSRIBE and REGISTER Refresh and SUBSCRIBE Retry ............................ 49
6.1.10 Use P-Associated-URIs in REGISTER ............................................................................ 49
6.1.11 SIP P-Early Media (PEM) Header .................................................................................... 50
6.1.12 SIP UPDATE Support ....................................................................................................... 50
6.1.13 Legacy SIP INFO FIR ........................................................................................................ 51
6.1.14 SIP rport Management for NAT Traversal ....................................................................... 51
6.1.15 SIP Session ID ................................................................................................................... 52
6.1.16 Incoming Call Rejection Behavior ..................................................................................... 52
6.1.17 Real-Time Transport Protocol Port Range....................................................................... 53
6.1.18 ICE Support (Webex Calling only) .................................................................................... 53
6.1.19 RTCP MUX ........................................................................................................................ 54
6.1.20 Transfer Call ....................................................................................................................... 54
6.1.21 N-Way Conference Calls and Participants ....................................................................... 55
6.1.22 Call Pull............................................................................................................................... 56
6.1.23 Call Park/Retrieve .............................................................................................................. 56

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE iv

 6.1.24 Call Statistics ...................................................................................................................... 57
6.1.25 Call Auto Recovery / Seamless Call Handover ............................................................... 57
6.1.26 Call Recording .................................................................................................................... 58
6.1.27 Voicemail, Visual Voicemail, Message Waiting Indicator................................................ 59
6.1.28 Voicemail Transcription for Webex Calling ...................................................................... 60
6.1.29 Call Settings ....................................................................................................................... 61
6.1.30 Settings Portal and Web-based Call Settings .................................................................. 62
6.1.31 Call Center / Call Queue Login/Logout............................................................................. 65
6.1.32 XSI Root and Paths ........................................................................................................... 66
6.1.33 XSI Event Channel ............................................................................................................ 66
6.1.34 Codec Configuration .......................................................................................................... 67
6.1.35 SIP-URI Dialing .................................................................................................................. 69
6.1.36 Call History Across All Devices ......................................................................................... 69
6.1.37 Disable Video Calls ............................................................................................................ 69
6.1.38 Emergency (911) Calling - Location Reporting with E911 Provider ............................... 70
6.1.39 PAI as Identity .................................................................................................................... 71
6.1.40 Disable Screen Sharing ..................................................................................................... 72
6.1.41 Spam Call Indication .......................................................................................................... 72
6.1.42 Noise Removal for PSTN/Mobile Calls ............................................................................ 72
6.1.43 QoS DSCP Marking........................................................................................................... 73
6.1.44 Primary Profile .................................................................................................................... 73
6.1.45 Block List (Webex Calling only)......................................................................................... 75
6.1.46 Media Adaptation and Resilience Implementation (MARI) ............................................. 76
6.2 Desktop Only Features ............................................................................................................... 78
6.2.1 Forced Logout .................................................................................................................... 78
6.2.2 Call Pickup.......................................................................................................................... 78
6.2.3 Boss-Admin (Executive-Assistant) Support ..................................................................... 79
6.2.4 Escalate SIP Calls to Meeting (Webex Calling only) ....................................................... 80
6.2.5 Desk Phone Control Calling – Auto Answer .................................................................... 80
6.2.6 Auto Answer with Tone Notification .................................................................................. 81
6.2.7 Desk Phone Control – Mid Call Controls – Conference .................................................. 81
6.2.8 Call Pickup Notification with BLF ...................................................................................... 81
6.2.9 Remote Control Event Package ....................................................................................... 82
6.2.10 Call Queue Agent CLID Selection .................................................................................... 82
6.2.11 Survivability Gateway (Webex Calling only) .................................................................... 82
6.2.12 Shared-Line Appearance .................................................................................................. 83
6.2.13 Virtual Lines (Webex Calling only) .................................................................................... 83
6.3 Mobile Only Features.................................................................................................................. 84
6.3.1 Emergency Calling............................................................................................................. 84
6.3.2 Push Notifications for Calls................................................................................................ 85
6.3.3 Single Alerting .................................................................................................................... 87
6.3.4 Click to Dial (Call Back) ..................................................................................................... 87

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE v

 6.3.5 MNO Support ..................................................................................................................... 88
7 Early Field Trial (BETA) Features.............................................................................................. 92
7.1 Simultaneous Calls with the Same User ................................................................................... 92
8 Custom Tags Mapping between Webex for Cisco BroadWorks and UC-One ................. 93
9 Appendix A: TLS Ciphers .......................................................................................................... 99
10 Appendix B: DM Tag Provisioning Script ............................................................................ 100
10.1 Desktop...................................................................................................................................... 101
10.2 Mobile ........................................................................................................................................ 103
10.3 Tablet ......................................................................................................................................... 106
10.4 System Tags ............................................................................................................................. 108
11 Acronyms and Abbreviations.................................................................................................. 109

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE vi

1 Summary of Changes

This section describes the changes to this document for each release and document version.

1.1 Changes for Release 43.8, August 2023

This version of the document includes the following changes:
▪ Added section Simultaneous Calls with Same User in BETA.

1.2 Changes for Release 43.7, July 2023

This version of the document includes the following changes:
▪ Moved section 6.3.5.6 MNO Mobility - In-call Widget out of BETA.

1.3 Changes for Release 43.6, June 2023

This version of the document includes the following changes:
▪ Moved section 6.1.46 Media Adaptation and Resilience Implementation (MARI) out of
BETA.
▪ Added section MNO Mobility - In-call Widget in BETA.
▪ Updated section 5.4 Deployment of config-wxt.xml - added recommendation to keep the
config template up-to-date with the latest Webex application release version.

1.4 Changes for Release 43.5, May 2023

This version of the document includes the following changes:
▪ Added section 6.1.45 Block List (Webex Calling only).
▪ Updated section 6.1.44 Primary Profile.

1.5 Changes for Release 43.4, April 2023

This version of the document includes the following changes:
▪ Updated section 6.2.8 Call Pickup Notification with BLF.
▪ Added section 6.2.13 Virtual Lines (Webex Calling only).
▪ Added section Media Adaptation and Resilience Implementation (MARI) in BETA.

1.6 Changes for Release 43.3, March 2023

This version of the document includes the following changes:
▪ Added section 6.1.44 Primary Profile.
▪ Updated section 6.2.12 Shared-Line Appearance.

1.7 Changes for Release 43.2, February 2023

This version of the document includes the following changes:

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 1

 ▪ Updated section 6.2.12 Shared-Line Appearance.
▪ Added 6.2.11 Survivability Gateway (Webex Calling only).
▪ Updated section 6.1.4 Force TCP, TLS or UDP Usage and Keepalives.

1.8 Changes for Release 43.1, January 2023

This version of the document includes the following changes:
▪ Updated section 6.2.12 Shared-Line Appearance.

1.9 Changes for Release 42.12, December 2022

This version of the document includes the following changes:
▪ Added section 6.2.12 Shared-Line Appearance.
▪ Updated section 6.1.31 Call Center / Call Queue Login/Logout
▪ Added section 7 Early Field Trial (BETA) Features.
▪ Updated section 6.3.5.2 Mid-Call Controls.
▪ Updated section 6.1.8.3 Enforce IP Version – added prefer-ipv4 and prefer-ipv6 modes.

1.10 Changes for Release 42.11, November 2022

There were no changes to this document for this release.

1.11 Changes for Release 42.10, October 2022

This version of the document includes the following changes:
▪ Added section 6.1.43 QoS DSCP Marking.

1.12 Changes for Release 42.9, September 2022

This version of the document includes the following changes:
▪ Updated section 6.1.38 Emergency (911) Calling - Location Reporting with E911 Provider.
▪ Updated section 6.2.8 Call Pickup Notification with BLF.

1.13 Changes for Release 42.8, August 2022

This version of the document includes the following changes:
▪ Added section 6.1.42 Noise Removal for PSTN/Mobile Calls.
▪ Added section 6.2.10 Call Queue Agent CLID Selection.

1.14 Changes for Release 42.7, July 2022

This version of the document includes the following changes:
▪ Added section 6.2.9 Remote Control Event Package.
▪ Added section 6.3.5.4 Notification for Native Calls.
▪ Added section 6.3.5.5 Move Native Call to Converged Meeting.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 2

 1.15 Changes for Release 42.6, June 2022
This version of the document includes the following changes:
▪ Added section 6.2.4 Escalate SIP Calls to Meeting.
▪ Added section 6.1.42 Noise Removal for PSTN/Mobile Calls.

1.16 Changes for Release 42.5, May 2022

This version of the document includes the following changes:
▪ Added section 6.1.41 Spam Call Indication.
▪ Added section 6.1.28 Voicemail Transcription for Webex Calling.
▪ Added section 6.1.8.3 Enforce IP Version.
▪ Added section 4.1 Localized Client Download.

1.17 Changes for Release 42.4, April 2022

This version of the document includes the following changes:
▪ Added section 6.1.40 Disable Screen Sharing.
▪ Added section 6.3.2.1 MWI.
▪ Added section 6.3.2.2 Ring Splash.

1.18 Changes for Release 42.3, March 2022

This version of the document includes the following changes:
▪ Updated section 6.1.38 Emergency (911) Calling - Location Reporting with E911 Provider.
▪ Updated section 6.1.8.2 SIP Failback.
▪ Updated section 6.1.6 Dynamic SIP Proxy Discovery.
▪ Added section 6.1.5 Configurable Timeout for Opening SIP Socket.
▪ Updated section 6.1.35 SIP-URI Dialing.
▪ Added section 6.3.5.2 Mid-Call Controls.

1.19 Changes for Release 42.2, February 2022

There were no changes to this document for this release.

1.20 Changes for Release 42.1, January 2022

This version of the document includes the following change:
▪ Updated section 6.1.30 Settings Portal and Web-based Call Settings.
▪ Added section 6.1.39 PAI as Identity.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 3

2 Changes for Configuration Files

2.1 Changes for Configuration Files for Release 43.8

▪ Added new tag <multiple-calls-per-user> in the <config><services><calls> section.
<config>
<services><calls>
<multiple-calls-per-user enabled="%ENABLE_MULTIPLE_CALLS_PER_USER_WXT%"/>

The following %TAG% was added:

▪ %ENABLE_MULTIPLE_CALLS_PER_USER_WXT%

2.2 Changes for Configuration Files for Release 43.7

There were no updates in the configuration files for this version.

2.3 Changes for Configuration Files for Release 43.6

▪ [Mobile only] Added new attributes widget-enabled in tags <hold>, <transfer-call> and
<escalate-to-webex-meeting> under section <config><services><calls>
<config>
<services><calls>
<hold xsi-enabled="%ENABLE_XSI_HOLD_CALLS_WXT%" widget-
enabled="%ENABLE_WIDGET_HOLD_CALLS_WXT%"/>
<transfer-call enabled="%ENABLE_TRANSFER_CALLS_WXT%" xsi-
enabled="%ENABLE_XSI_TRANSFER_CALLS_WXT%" widget-
enabled="%ENABLE_WIDGET_TRANSFER_CALLS_WXT%"
type="%TRANSFER_CALL_TYPE_WXT%"/>
<escalate-to-webex-meeting
enabled="%ENABLE_CALLS_ESCALATE_TO_WEBEX_MEETING_WXT%" widget-
enabled="%ENABLE_WIDGET_CALLS_ESCALATE_TO_WEBEX_MEETING_WXT%"/>

The following %TAG%s were added:

▪ %ENABLE_WIDGET_HOLD_CALLS_WXT%
▪ %ENABLE_WIDGET_TRANSFER_CALLS_WXT%
▪ %ENABLE_WIDGET_CALLS_ESCALATE_TO_WEBEX_MEETING_WXT%

2.4 Changes for Configuration Files for Release 43.5

▪ [Webex Calling only] Added <call-block> tag under <config><services><calls> section
<config>
<services><calls>
<call-block enabled="%ENABLE_CALL_BLOCK_WXT%"/>

The following %TAG% was added:

▪ %ENABLE_CALL_BLOCK_WXT%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 4

 2.5 Changes for Configuration Files for Release 43.4
▪ [Webex Calling only] For each <line> tag added lineType attribute. Also added
<external-id> tag under each <line> tag.
<config><protocols>
<sip>
<lines multi-line-enabled="%ENABLE_MULTI_LINE_WXT%">
...
<line lineType="%BW-MEMBERTYPE-1%">
<external-id>%BWUSEREXTID-1%</external-id>
...
</line>
<line lineType="%BW-MEMBERTYPE-2%">
<external-id>%BWUSEREXTID-2%</external-id>
...
</line>
...
<line lineType="%BW-MEMBERTYPE-10%">
<external-id>%BWUSEREXTID-10%</external-id>
...
</line>

▪ [BETA] Added <audio-quality-enhancements> section under

<services><calls><audio> and <video-quality-enhancements> section under
<services><calls><video>
<config>
<services><calls>
<calls>
<audio>
<audio-quality-enhancements>
<mari>
<fec enabled="%ENABLE_AUDIO_MARI_FEC_WXT%">
<x-ulpfecuc>8000</x-ulpfecuc>
<payload>111</payload>
<max_esel>1400</max_esel>
<max_n>255</max_n>
<m>8</m>
<multi_ssrc>1</multi_ssrc>
<non_seq>1</non_seq>
<feedback>0</feedback>
<order>FEC_SRTP</order>
</fec>
<rtx enabled=”%ENABLE_AUDIO_MARI_RTX_WXT%”>
<mari-rtx>90000</mari-rtx>
<payload>112</payload>
<time>180</time>
<data-flow>1</data-flow>
<order>RTX_SRTP</order>
</rtx>
</mari>
</audio-quality-enhancements>
...
<video>
<video-quality-enhancements>
<mari>
<fec enabled="%ENABLE_VIDEO_MARI_FEC_WXT%">
<x-ulpfecuc>8000</x-ulpfecuc>
<payload>111</payload>
<max_esel>1400</max_esel>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 5

 <max_n>255</max_n>
<m>8</m>
<multi_ssrc>1</multi_ssrc>
<non_seq>1</non_seq>
<feedback>0</feedback>
<order>FEC_SRTP</order>
</fec>
<rtx enabled="%ENABLE_VIDEO_MARI_RTX_WXT%">
<mari-rtx>90000</mari-rtx>
<payload>112</payload>
<time>180</time>
<data-flow>1</data-flow>
<order>RTX_SRTP</order>
</rtx>
</mari>
</video-quality-enhancements>

▪ [Desktop only] Removed hardcoded value for the first line label name under
corresponding <line> section under <protocols><sip>.
<config>
<protocols><sip>
<lines multi-line-enabled="%ENABLE_MULTI_LINE_WXT%">
…
<line>
<label>%BWAPPEARANCE-LABEL-1%</label>
…

The following %TAG%s were added:

▪ %ENABLE_AUDIO_MARI_FEC_WXT%
▪ %ENABLE_AUDIO_MARI_RTX_WXT%
▪ %ENABLE_VIDEO_MARI_FEC_WXT%
▪ %ENABLE_VIDEO_MARI_RTX_WXT%

The following system level %TAG%s were added:

▪ %BW-MEMBERTYPE-X%
▪ %BWUSEREXTID-X%

2.6 Changes for Configuration Files for Release 43.3

There were no updates in the configuration files for this version.

2.7 Changes for Configuration Files for Release 43.2

Added <device-owner-restriction> tag under section <services><calls>.
<config>
<services><calls>
<device-owner-restriction enabled="%ENABLE_DEVICE_OWNER_RESTRICTION_WXT%"/>

The following %TAG% was added:

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 6

 ▪ %ENABLE_DEVICE_OWNER_RESTRICTION_WXT%

2.8 Changes for Configuration Files for Release 43.1

There were no updates in the configuration files for this version.

2.9 Changes for Configuration Files for Release 42.12

▪ [Desktop only] Added section <lines> under <protocols><sip>, with <personal> and 10
<line> subsections. The following tags are deprecated and replaced by ones for each
line:
- The <service-uri> tag under section <config><services><calls><conference>
- The <center-number> tag under section <config><services><voice-mail>
- The <credentials> section under <config><protocols><sip>

<config>
<protocols><sip>
<lines multi-line-enabled="%ENABLE_MULTI_LINE_WXT%">
<personal>
<line-port>%BWDISPLAYNAMELINEPORT%</line-port>
<primary-lineport>%BWLINEPORT-PRIMARY%</primary-lineport>
</personal>
<line>
<label>My Line</label>
<name>%BWNAME-1%</name>
<phone-number>%BWE164-1%</phone-number>
<extension>%BWEXTENSION-1%</extension>
<voice-mail-number>%BWVOICE-PORTAL-NUMBER-1%</voice-mail-number>
<conference-service-uri>sip:%BWNETWORK-CONFERENCE-SIPURI-
1%</conference-service-uri>
<credentials>
<username>%BWLINEPORT-1%</username>
<password>%BWAUTHPASSWORD-1%</password>
<auth>
<auth401>
<default>
<username>%BWAUTHUSER-1%</username>
<password>%BWAUTHPASSWORD-1%</password>
</default>
<realm id="%BWHOST-1%">
<username>%BWAUTHUSER-1%</username>
<password>%BWAUTHPASSWORD-1%</password>
</realm>
</auth401>
<auth407>
<default>
<username>%BWAUTHUSER-1%</username>
<password>%BWAUTHPASSWORD-1%</password>
</default>
<realm id="%BWHOST-1%">
<username>%BWAUTHUSER-1%</username>
<password>%BWAUTHPASSWORD-1%</password>
</realm>
</auth407>
</auth>
</credentials>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 7

 </line>
…

▪ [Mobile only] The url and branding-enabled attributes of the <services><call-center-

agent> tag are removed (deprecated).
<config>
<services>
<call-center-agent enabled="%ENABLE_CALL_CENTER_WXT%"/>

▪ [Mobile only] Added <mobility-persona-management> and <calling-line-id-delivery-

blocking> tags under section <services><dialing>.
<config>
<services><dialing>
<calling-line-id-delivery-blocking
enabled="%ENABLE_CLID_DELIVERY_BLOCKING_WXT%"/>
<mobility-persona-management
enabled="%ENABLE_MOBILITY_PERSONA_MANAGEMENT_WXT%"/>

The following %TAG%s were added:

▪ %ENABLE_MULTI_LINE_WXT% [Desktop only]
▪ %ENABLE_CALLS_ESCALATE_TO_WEBEX_MEETING_WXT% [Mobile only]
▪ %ENABLE_CLID_DELIVERY_BLOCKING_WXT%
▪ %ENABLE_MOBILITY_PERSONA_MANAGEMENT_WXT%

The following %TAG%s were deprecated:

▪ %CALL_CENTER_URL_WXT% [Mobile only]
▪ %CALL_CENTER_BRANDING_ENABLED_WXT% [Mobile only]

2.10 Changes for Configuration Files for Release 42.11

▪ [Mobile only] Added <noise-removal> tag under section <services><calls>.
<config>
<services><calls>
<noise-removal enabled="%ENABLE_NOISE_REMOVAL_WXT%"/>

The following %TAG% was added:

▪ %ENABLE_NOISE_REMOVAL_WXT% [Mobile only]

2.11 Changes for Configuration Files for Release 42.10

▪ Added <outgoing-calls> tag under section <services><call-center-agent>.
<config>
<services>
<call-center-agent>
<outgoing-calls enabled="%ENABLE_CALL_CENTER_AGENT_OUTGOING_CALLS_WXT%">

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 8

 ▪ Added <audio-quality-enhancements> tag under sections <calls><audio> and
<calls><video>.
<config>
<services>
<calls>
<audio>
<audio-quality-enhancements>
<qos
enabled="%ENABLE_AUDIO_QOS_WXT%" type="dscp" value="%AUDIO_QOS_VALUE_WXT%"/>
</audio-quality-enhancements>
...
<video>
<video-quality-enhancements>
<qos
enabled="%ENABLE_VIDEO_QOS_WXT%" type="dscp" value="%VIDEO_QOS_VALUE_WXT%" /
>
</video-quality-enhancements>

The following %TAG%s were added:

▪ %ENABLE_CALL_CENTER_AGENT_OUTGOING_CALLS_WXT% [Desktop only]
▪ %ENABLE_AUDIO_QOS_WXT%
▪ %AUDIO_QOS_VALUE_WXT%
▪ %ENABLE_VIDEO_QOS_WXT%
▪ %VIDEO_QOS_VALUE_WXT%

2.12 Changes for Configuration Files for Release 42.9

There were no updates in the configuration files for this version.

2.13 Changes for Configuration Files for Release 42.8

▪ [Desktop only] The url and branding-enabled attributes of the <services><call-center-
agent> tag are removed (deprecated).
<config>
<services>
<call-center-agent enabled="%ENABLE_CALL_CENTER_WXT%"/>

▪ [Desktop only] Added <noise-removal> tag under section <services><calls>.

<config>
<services><calls>
<noise-removal enabled="%ENABLE_NOISE_REMOVAL_WXT%"/>

The following %TAG% was added:

▪ %ENABLE_NOISE_REMOVAL_WXT% [Mobile only]

The following %TAG%s were deprecated:

▪ %CALL_CENTER_URL_WXT% [Desktop only]
▪ %CALL_CENTER_BRANDING_ENABLED_WXT% [Desktop only]

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 9

2.14 Changes for Configuration Files for Release 42.7
▪ [Desktop only] Added new tag <remote-control-events> under section
<services><calls>.
<config>
<services><calls>
<remote-control-events enabled="%ENABLE_REMOTE_CONTROL_EVENTS_WXT%"/>

The following %TAG% was added:

▪ %ENABLE_REMOTE_CONTROL_EVENTS_WXT% [Desktop only]

2.15 Changes for Configuration Files for Release 42.6

▪ Added <transcription> tag under section <services><voice-mail>.
<config>
<services>
<voice-mail>
<transcription enabled="%ENABLE_VOICE_MAIL_TRANSCRIPTION_WXT%"/>

The following %TAG%s was added:

▪ %ENABLE_VOICE_MAIL_TRANSCRIPTION_WXT%

2.16 Changes for Configuration Files for Release 42.5

▪ Added <enforce-ip-version> tag under section <protocols><sip><transports>.
<config>
<protocols><sip>
<transports>
<enforce-ip-version>%SIP_TRANSPORTS_ENFORCE_IP_VERSION_WXT%</enforce-ip-
version>

▪ Added <spam-indication> tag under section <services><calls>.

<config>
<services><calls>
<spam-indication enabled="%ENABLE_CALLS_SPAM_INDICATION_WXT%"/>

▪ Added <screen-share> tag under section <services>.

<config>
<services>
<screen-share enabled="%ENABLE_SCREEN_SHARE_WXT%"/>

The following %TAG%s were added:

▪ %SIP_TRANSPORTS_ENFORCE_IP_VERSION_WXT%
▪ %ENABLE_CALLS_SPAM_INDICATION_WXT%
▪ %ENABLE_SCREEN_SHARE_WXT%

2.17 Changes for Configuration Files for Release 42.4

▪ [Mobile only] Added the <ring-splash> tag under section <services>.
<config>
<services>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 10

 <ring-splash enabled="%ENABLE_RING_SPLASH_WXT%"/>

The following %TAG% was added:

▪ %ENABLE_RING_SPLASH_WXT% [Mobile only]

2.18 Changes for Configuration Files for Release 42.3

▪ [Desktop only] Added <busy-lamp-field> tag under section <services><calls>.
<config>
<services><calls>
<busy-lamp-field enabled="%ENABLE_BUSY_LAMP_FIELD_WXT%">
<display-caller enabled="%ENABLE_BLF_DISPLAY_CALLER_WXT%"/>
<notification-delay time="%BLF_NOTIFICATION_DELAY_TIME_WXT%"/>

▪ [Desktop only] Added <user-location-prompting> tag under section

<services><emergency-dialing>.
<config>
<services><emergency-dialing><redsky>
<user-location-
prompting>%EMERGENCY_REDSKY_USER_LOCATION_PROMPTING_WXT%</user-location-
prompting>

▪ Added new attribute enable-backup-service to the <protocols><sip><proxy-discovery>

tag.
<config>
<protocols><sip>
<proxy-discovery enabled=”%USE_PROXY_DISCOVERY_WXT%”
tcp=”%USE_TCP_FROM_DNS_WXT%” udp=”%USE_UDP_FROM_DNS_WXT%”
tls="%USE_TLS_FROM_DNS_WXT%" enable-backup-
service="%PROXY_DISCOVERY_ENABLE_BACKUP_SERVICE_WXT%">

▪ Added new attribute enable-srv-backup to the <protocols><sip><proxy-

discovery><record-name> tag.
<config>
<protocols><sip>
<proxy-discovery>
<record-name enable-srv-
backup="%PROXY_DISCOVERY_ENABLE_SRV_BACKUP_WXT%">%SBC_ADDRESS_WXT%</record-
name>

▪ [Desktop only] Added <failback> tag under section <protocols><sip>.

<config>
<protocols><sip>
<failback enabled="%SIP_FAILBACK_ENABLED_WXT%"
timeout="%SIP_FAILBACK_TIMEOUT_WXT%" use-random-
factor="%SIP_FAILBACK_USE_RANDOM_FACTOR_WXT%"/>

▪ [Desktop only] Added new attribute bypass-os-cache to the <protocols><sip><proxy-

discovery> tag.
<config>
<protocols><sip>
<proxy-discovery enabled=”%USE_PROXY_DISCOVERY_WXT%”
tcp=”%USE_TCP_FROM_DNS_WXT%” udp=”%USE_UDP_FROM_DNS_WXT%”
tls="%USE_TLS_FROM_DNS_WXT%" enable-backup-
service="%PROXY_DISCOVERY_ENABLE_BACKUP_SERVICE_WXT%"

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 11

 bypass-os-cache="%PROXY_DISCOVERY_BYPASS_OS_CACHE_WXT%">

▪ Added <connect-timeout> tag under sections <protocols><sip><transports><tcp> and

<protocols><sip><transports><tls>.
<config>
<protocols><sip>
<transports>
…
<tcp>
<connect-timeout>%SIP_TRANSPORTS_TCP_CONNECT_TIMEOUT_WXT%</connect-
timeout>
</tcp>
<tls>
<connect-timeout>%SIP_TRANSPORTS_TLS_CONNECT_TIMEOUT_WXT%</connect-
timeout>
</tcp>

▪ [Mobile only] Added new attribute enable-bwks-mobility-dependency to the

<services><dialing><native> tag.
<config>
<services><dialing>
<native enabled="%ENABLE_DIALING_NATIVE_WXT%" enable-bwks-mobility-
dependency="%DIALING_NATIVE_ENABLE_BWKS_MOBILITY_DEPENDENCY_WXT%"/>

▪ [Mobile only] Added new section <xsi-call-control> under section <services><calls>.

<config>
<services><calls>
<xsi-call-control enabled="%ENABLE_XSI_CALL_CONTROL_WXT%">
<deployment type="%XSI_CALL_CONTROL_DEPLOYMENT_TYPE_WXT%"/>
<deviceTypes>
<deviceType>%DEPLOYMENT_DEVICE_TYPE_1_WXT%</deviceType>
<deviceType>%DEPLOYMENT_DEVICE_TYPE_2_WXT%</deviceType>
<deviceType>%DEPLOYMENT_DEVICE_TYPE_3_WXT%</deviceType>

▪ [Mobile only] Added new tag <hold> under <services><calls>.

<config>
<services><calls>
<hold xsi-enabled="%ENABLE_XSI_HOLD_CALLS_WXT%"/>

The following %TAG%s were added:

▪ %ENABLE_BUSY_LAMP_FIELD_WXT% [Desktop only]
▪ %ENABLE_BLF_DISPLAY_CALLER_WXT% [Desktop only]
▪ %BLF_NOTIFICATION_DELAY_TIME_WXT% [Desktop only]
▪ %EMERGENCY_REDSKY_USER_LOCATION_PROMPTING_WXT% [Desktop only]
▪ %PROXY_DISCOVERY_ENABLE_BACKUP_SERVICE_WXT%
▪ %PROXY_DISCOVERY_ENABLE_SRV_BACKUP_WXT%
▪ %SIP_FAILBACK_ENABLED_WXT% [Desktop only]
▪ %SIP_FAILBACK_TIMEOUT_WXT% [Desktop only]
▪ %SIP_FAILBACK_USE_RANDOM_FACTOR_WXT% [Desktop only]
▪ %PROXY_DISCOVERY_BYPASS_OS_CACHE_WXT% [Desktop only]

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 12

 ▪ %SIP_TRANSPORTS_TCP_CONNECT_TIMEOUT_WXT%
▪ %SIP_TRANSPORTS_TLS_CONNECT_TIMEOUT_WXT%
▪ %DIALING_NATIVE_ENABLE_BWKS_MOBILITY_DEPENDENCY_WXT% [Mobile only]
▪ %ENABLE_XSI_CALL_CONTROL_WXT% [Mobile only]
▪ %XSI_CALL_CONTROL_DEPLOYMENT_TYPE_WXT% [Mobile only]
▪ %DEPLOYMENT_DEVICE_TYPE_1_WXT% [Mobile only]
▪ %DEPLOYMENT_DEVICE_TYPE_2_WXT% [Mobile only]
▪ %DEPLOYMENT_DEVICE_TYPE_3_WXT% [Mobile only]
▪ %ENABLE_XSI_HOLD_CALLS_WXT% [Mobile only]

2.19 Changes for Configuration Files for Release 42.1

▪ Added <use-pai-as-calling-identity> tag under section <protocols><sip>.
<config>
<protocols><sip>
<use-pai-as-calling-identity
enabled="%USE_PAI_AS_CALLING_IDENTITY_WXT%"/>

▪ Added target and sso-enabled attributes to the <services><userportal-settings> tag.

<config>
<services>
<userportal-settings target="%USER_PORTAL_SETTINGS_TARGET_WXT%" sso-
enabled="%USER_PORTAL_SETTINGS_SSO_ENABLED_WXT%">

▪ Added "Email Vm Messages" to the list of Call Settings Web View services under
section <services><web-call-settings><service-settings>.
<config>
<services>
<web-call-settings>
<service-settings>
<service name="Email Vm Messages"
visible="%WEB_CALL_SETTINGS_EMAIL_VM_VISIBLE_WXT%"/>

The following %TAG%s were added:

▪ %USE_PAI_AS_CALLING_IDENTITY_WXT%
▪ %USER_PORTAL_SETTINGS_TARGET_WXT%
▪ %USER_PORTAL_SETTINGS_SSO_ENABLED_WXT%
▪ %WEB_CALL_SETTINGS_EMAIL_VM_VISIBLE_WXT%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 13

3 Introduction

The purpose of this document is to provide a description of the configuration of the Webex for
Cisco BroadWorks client.
The configuration file config-wxt.xml is provided in two versions – one for mobile (Android and
iOS) and one for desktop (Windows and MacOS).
The clients are configured using a configuration that is not visible to the end user. The config-
wxt.xml provides server-specific information, such as server addresses and ports and runtime
options for the client itself (for example, options visible in the Settings screen).
The configuration files are read by the client when it starts, after being retrieved from Device
Management. The information from the configuration files is stored encrypted, thus making it
invisible and inaccessible to the end user.

NOTE: The XML properties should not contain spaces (for example, <transfer-call
enabled="%ENABLE_TRANSFER_CALLS_WXT%"/> instead of <transfer-call enabled =
"%ENABLE_TRANSFER_CALLS_WXT%"/>).

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 14

4 Installation

The Webex for Cisco BroadWorks clients can be installed from the following:
https://www.webex.com/webexfromserviceproviders-downloads.html

4.1 Localized Client Download

The following localized versions of the Webex for Cisco BroadWorks clients can be downloaded
as follows:
https://www.webex.com/ko/webexfromserviceproviders-downloads.html
https://www.webex.com/fr/webexfromserviceproviders-downloads.html
https://www.webex.com/pt/webexfromserviceproviders-downloads.html
https://www.webex.com/zh-tw/webexfromserviceproviders-downloads.html
https://www.webex.com/zh-cn/webexfromserviceproviders-downloads.html
https://www.webex.com/ja/webexfromserviceproviders-downloads.html
https://www.webex.com/es/webexfromserviceproviders-downloads.html
https://www.webex.com/de/webexfromserviceproviders-downloads.html
https://www.webex.com/it/webexfromserviceproviders-downloads.html

4.2 Android Client

The Android client is installed as an application (Android application package [APK]), which keeps
the settings- and configuration-related data inside its private area.
There is version control based on the Google Play procedures. A standard Google Play
notification is provided (that is, Android automatically indicates that there is a new version of
software available).
When the new version is downloaded, the old software is overwritten; however, user data is kept
by default.
Note that the user is not required to select any options for installation or un-installation.

4.3 iOS Client

The iOS client is installed as an application, which keeps the settings-related data inside its
“sandbox” and the configuration file data is stored encrypted.
There is version control based on the Apple App Store procedures. The App Store icon is
highlighted to indicate that there is a new version of software available.
When the new version is downloaded, the old software is overwritten; however, user data is kept
by default.
Note that the user is not required to select any options for installation or un-installation.

4.4 Desktop Client

Information about the installation and version control of the desktop client (Windows and MacOS)
can be found on the following: https://help.webex.com/en-us/nw5p67g/Webex-Installation-and-
Automatic-Upgrade.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 15

5 Device Management

5.1 Device Management Tags

Webex for Cisco BroadWorks uses the Device Management Tag Sets shown in the following
figure. The System Default and custom tag sets are required to provision specific device/client
settings. This tag set provides flexibility in managing the client’s network/service connectivity
settings as well as feature activation controls.
This custom tag set is provisioned by a system administrator through the System → Resources
→ Device Management Tag Sets option. The administrator must add new tag sets:
▪ Mobile: Connect_Tags
▪ Tablet: ConnectTablet_Tags
▪ Desktop: BroadTouch_Tags
Create each individual tag and set its value. Section references provide detailed descriptions for
each tag. The custom tags are separated in groups based on the functionality and are discussed
later in this document.

Figure 1 Desktop Device Management Tag Sets

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 16

 Figure 2 Mobile Device Management Tag Sets

5.2 Partial Match Enhancements for Device Type Selection

To allow increased flexibility when selecting functionality packages for user groups or individual
users, the device profile type is selected based on a (first) partial match. This allows customers to
use different device types.
The general Device Management procedure specifies that the Cisco BroadWorks Application
Server provides a Device Profile Type. It is named “Business Communicator – PC” for desktop,
“Connect - Mobile” for mobile, and “Connect – Tablet” for tablet. A Device Profile can be created
and assigned to the user. The Application Server then builds a configuration file and stores it on
the Profile Server.
At login, the client queries the assigned device list via Xsi and searches for the corresponding
device type profile. The client chooses the first profile that starts with the corresponding device
type name. Then the device profile configuration data (configuration file) associated with this
device profile is used to enable and disable various features.
This allows the same client executable to be used with various device profile types, so the service
provider can change feature packages for individual users or groups of users by just changing the
device profile type in DM for a user or group of users.
For example, the service provider could have any number of device profile types based on user
roles, such as “Business Communicator – PC Basic”, “Business Communicator – PC Executive”,
or “Business Communicator – PC Assistant” and change the functionality available for individual
users by changing the device profile type for them.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 17

Note that it is not expected to have multiple matching device profile types in the received device
list XML but only one.

5.3 Client Configuration

The Webex for Cisco BroadWorks version of the client uses the config-wxt.xml file for
configuration of its calling functionality. There is a separate configuration procedure for Webex
that is not covered in this document.

5.4 Deployment of config-wxt.xml

Add the corresponding config-wxt.xml file to the “Connect – Mobile”, “Connect – Tablet”, and
“Business Communicator – PC” device profiles. Webex for Cisco BroadWorks uses the same
device profiles as UC-One so to make it easier for deployment.

NOTE 1: A config file must exist for each device profile.

NOTE 2: It is HIHGLY RECOMMENDED the templates to be kept up-to-date with the latest release of
the Webex app

5.5 Configuration File (config-wxt.xml)

New custom tags, with _WXT suffix, are used to differentiate the new Webex for Cisco
BroadWorks configuration deployment from legacy clients. However, there are still some (system)
tags that are shared between UC-One and Webex.
Some of the Cisco BroadWorks System Custom Tags are also used in the config-wxt.xml
configuration file. For more information on each of the following tags, see section 5.7 Cisco
BroadWorks Dynamic Built-in System Tags.
▪ %BWNETWORK-CONFERENCE-SIPURI-x%
▪ %BWVOICE-PORTAL-NUMBER-x%
▪ %BWLINEPORT-x%
▪ %BWAUTHUSER-x%
▪ %BWAUTHPASSWORD-x%
▪ %BWE164-x%
▪ %BWHOST-x%
▪ %BWNAME-x%
▪ %BWEXTENSION-x%
▪ %BWAPPEARANCE-LABEL-x%
▪ %BWDISPLAYNAMELINEPORT%
▪ %BWLINEPORT-PRIMARY%
▪ %BWE911-PRIMARY-HELDURL%
▪ %BWE911-CUSTOMERID%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 18

▪ %BWE911-SECRETKEY%
▪ %BWE911-EMERGENCY-NUMBER-LIST%
▪ %BW-MEMBERTYPE-X%
▪ %BWUSEREXTID-X%

5.6 System Default Tags

As the system administrator, you can access the System Default tags through the System →
Resources → Device Management Tag Sets option. The following System Default tags must be
provisioned when the VoIP Calling package is installed.
Tag Description
%SBC_ADDRESS_WXT% This should be configured as the fully qualified domain name
(FQDN) or IP address of the session border controller (SBC)
deployed in the network.
Example: sbc.yourdomain.com

%SBC_PORT_WXT% If the SBC_ADDRESS_WXT is an IP address, then this

parameter should be set to the SBC port.
If the SBC_ADDRESS_WXT is an FQDN, then it can be left
unset.
Example: 5075

5.7 Cisco BroadWorks Dynamic Built-in System Tags

In addition to the default system tags and the custom tags that must be defined, there are existing
Cisco BroadWorks System Tags that are typically used and are part of the recommended Device
Type Archive File (DTAF). These tags are listed in this section. Depending on the installed
solution package, not all system tags are used.
Tag Description
%BWNETWORK-CONFERENCE- This is the server URI used to enable N-Way conferencing.
SIPURI-x%

%BWVOICE-PORTAL-NUMBER-x% This number is used for voicemail. The client dials this number
when retrieving voicemail.

%BWLINEPORT-x% SIP username used in SIP signaling, for example, in

registration.

%BWHOST-x% This is the domain portion of the provisioned line port for the
device assigned to the user. It is retrieved from the user’s
profile.
Typically used as the SIP domain.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 19

 Tag Description
%BWAUTHUSER-x% This is the authentication user name. If the subscriber has
been assigned authentication, this is the provisioned user ID
on the Authentication page regardless of the selected
authentication mode of the device type.
The SIP username, typically used in 401 and 407 signaling.
Can be different from the default SIP username.

%BWAUTHPASSWORD-x% This is the user’s authentication password. If the subscriber

has been assigned authentication, this is the provisioned
password on the Authentication page regardless of the
selected authentication mode value of the device type.
The SIP password used in SIP signaling.

%BWE164-x% This tag provides the user’s phone number in international

format.

%BWNAME-x% This is the subscriber’s first name and last name in the user’s
profile. The first and last names are concatenated together.
In case of multi-line configuration, if no line label configured
and if not empty, used as display name for the line in the line
selector.

%BWEXTENSION-x% The subscriber’s extension is retrieved from the extension

provisioned in the user’s profile. If an extension has not been
provisioned, the tag is replaced with the subscriber’s phone
number (DN).

%BWAPPEARANCE-LABEL-x% This is the line label configured. Used as line name, if it is not
empty.

%BWDISPLAYNAMELINEPORT% This is the line/port of the first private line, as opposed to a

shared line (Shared Call Appearance).
This is the line port provisioned on the device assigned to the
user. This is retrieved from the user’s profile.
Used to identify the primary line of the user.

%BWLINEPORT-PRIMARY% The primary line port is provisioned on the device that is

assigned to the user. This tag does not include the domain
portion of the provisioned line port. It is retrieved from the
user’s profile.

%BWE911-PRIMARY-HELDURL% Specifies the URL to the RedSky Emergency Location

Platform supporting the HELD protocol.

%BWE911-CUSTOMERID% The customer ID (HeldOrgId, CompanyID) used for the

RedSky HTTPS request.

%BWE911-SECRETKEY% The secret to authenticate the RedSky HTTPS request.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 20

 Tag Description
%BWE911-EMERGENCY-NUMBER- The list of emergency numbers supported by RedSky.
LIST% To use this tag, the %RESERVEDBW911-EMERGENCY-
NUMBER-LIST% reserved custom tag must be added to the
tag set used by the device type. The “reserved” tag must
contain the emergency numbers defined on BroadWorks
under AS_CLI/System/CallP/CallTypes > in a comma
separated format such as 911, 0911, 933.
NOTE: The Webex client does not support wildcards in
emergency numbers; therefore, only exact emergency
numbers should be added to the “reserved” custom tag.
The following example shows how the reserved tag
functionality is meant to be used:
1) The native tag %BWE911-EMERGENCY-NUMBER-LIST%
is added to the template file of the device
2) The reserved custom tag %RESERVEDBW911-
EMERGENCY-NUMBER-LIST% is added to the tag set used
by the device with value 911, 0911, 933
3) When the file is rebuilt, the %RESERVEDBW911-
EMERGENCY-NUMBER-LIST% native tag is resolved to
911, 0911, 933
This is the type for each line. It can be one of "Virtual Profile",
%BW-MEMBERTYPE-X% "User" or "Place".

%BWUSEREXTID-X% This is the external ID for given line (Webex Calling only)

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 21

6 Custom Tags

This section describes the custom tags used in Webex for Cisco BroadWorks. It lists all the
custom tags used for both Desktop and Mobile/Tablet platforms.
Note, however, that some settings described in this section are supported only for the specific
release of the client. To determine if a setting does not apply to an older client version, see the
appropriate release-specific configuration guide.
Tag Used in Used Default Section
Desktop in Value
Mobile
/Tablet
%ENABLE_MULTI_ Y N false For more information, see section
LINE_WXT% 6.2.12 Shared-Line Appearance.

%ENABLE_CALLS_ N Y false For more information, see section 6.2.4

ESCALATE_TO_WE Escalate SIP Calls to Meeting (Webex
BEX_MEETING_WX Calling).
T%
%ENABLE_CLID_D N Y false For more information, see section
ELIVERY_BLOCKIN 6.3.5.3 Outgoing Calling Line Identity
G_WXT% (CLID).
%ENABLE_MOBILIT N Y false For more information, see section
Y_PERSONA_MAN 6.3.5.3 Outgoing Calling Line Identity
AGEMENT_WXT% (CLID).
%ENABLE_REJECT Y Y true For more information, see section
_WITH_486_WXT% 6.1.16 Incoming Call Rejection
Behavior.
%REJECT_WITH_ N Y decline For more information, see section 6.3.2
XSI_MODE_WXT% _false Push Notifications for Calls.

%REJECT_WITH_ N Y busy For more information, see section 6.3.2

XSI_DECLINE_REA Push Notifications for Calls.
SON_WXT%
%ENABLE_TRANSF Y Y false For more information, see section
ER_CALLS_WXT% 6.1.20 Transfer Call.

%ENABLE_CONFE Y Y false For more information, see section

RENCE_CALLS_ 6.1.21 N-Way Conference Calls and
WXT% Participants.
%ENABLE_NWAY_ Y Y false For more information, see section
PARTICIPANT_LIST 6.1.21 N-Way Conference Calls and
_WXT% Participants.
%MAX_CONF_PAR Y Y 10 For more information, see section
TIES_WXT% 6.1.21 N-Way Conference Calls and
Participants.
%ENABLE_CALL_S Y Y false For more information, see section
TATISTICS_WXT% 6.1.24 Call Statistics.

%ENABLE_CALL_ Y Y false For more information, see section

PULL_WXT% 6.1.22 Call Pull.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 22

 Tag Used in Used Default Section
Desktop in Value
Mobile
/Tablet
%PN_FOR_CALLS_ N Y false For more information, see section 6.3.2
CONNECT_SIP_ON Push Notifications for Calls.
_ACCEPT_WXT%
%ENABLE_VOICE_ Y Y false For more information, see section
MAIL_TRANSCRIPT 6.1.28 Voicemail Transcription for
ION_WXT% Webex Calling.
%ENABLE_MWI_ Y Y false For more information, see section
WXT% 6.1.27 Voicemail, Visual Voicemail,
Message Waiting Indicator.
%MWI_MODE_WXT Y Y empty For more information, see section
% 6.1.27 Voicemail, Visual Voicemail,
Message Waiting Indicator.
%ENABLE_VOICE_ Y Y false For more information, see section
MAIL_WXT% 6.1.27 Voicemail, Visual Voicemail,
Message Waiting Indicator.
%ENABLE_VISUAL Y Y false For more information, see section
_VOICE_MAIL_WXT 6.1.27 Voicemail, Visual Voicemail,
% Message Waiting Indicator.
%ENABLE_FORCE Y N false For more information, see section 6.2.1
D_LOGOUT_WXT% Forced Logout.
%FORCED_LOGOU Y N empty For more information, see section 6.2.1
T_APPID_WXT% Forced Logout.
%ENABLE_CALL_F Y Y false For more information, see section
ORWARDING_ALW 6.1.29.1 Call Forwarding Always.
AYS_WXT%
%ENABLE_BROAD Y Y false For more information, see section
WORKS_ANYWHE 6.1.29.2 BroadWorks Anywhere.
RE_WXT%
%ENABLE_BROAD Y Y true For more information, see section
WORKS_ANYWHE 6.1.29.2 BroadWorks Anywhere.
RE_DESCRIPTION_
WXT%
%ENABLE_BROAD Y Y false For more information, see section
WORKS_ANYWHE 6.1.29.2 BroadWorks Anywhere.
RE_ALERT_ALL_LO
CATIONS_WXT%
%BROADWORKS_ Y Y false For more information, see section
ANYWHERE_ALER 6.1.29.2 BroadWorks Anywhere.
T_ALL_LOCATIONS
_DEFAULT_WXT%
%ENABLE_BROAD Y Y false For more information, see section
WORKS_ANYWHE 6.1.29.2 BroadWorks Anywhere.
RE_CALL_CONTRO
L_WXT%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 23

 Tag Used in Used Default Section
Desktop in Value
Mobile
/Tablet
%BROADWORKS_ Y Y false For more information, see section
ANYWHERE_CALL_ 6.1.29.2 BroadWorks Anywhere.
CONTROL_DEFAUL
T_WXT%
%ENABLE_BROAD Y Y false For more information, see section
WORKS_ANYWHE 6.1.29.2 BroadWorks Anywhere.
RE_DIVERSION_IN
HIBITOR_WXT%
%BROADWORKS_ Y Y false For more information, see section
ANYWHERE_DIVER 6.1.29.2 BroadWorks Anywhere.
SION_INHIBITOR_D
EFAULT_WXT%
%ENABLE_BROAD Y Y false For more information, see section
WORKS_ANYWHE 6.1.29.2 BroadWorks Anywhere.
RE_ANSWER_CON
FIRMATION_WXT%
%BROADWORKS_ Y Y false For more information, see section
ANYWHERE_ANSW 6.1.29.2 BroadWorks Anywhere.
ER_CONFIRMATIO
N_DEFAULT_WXT
%
%ENABLE_EMERG N Y false For more information, see section 6.3.1
ENCY_DIALING_W Emergency Calling.
XT%
%EMERGENCY_DI N Y 911, For more information, see section 6.3.1
ALING_NUMBERS_ 112 Emergency Calling.
WXT%
%ENABLE_USE_RP Y Y false For more information, see section
ORT_WXT% 6.1.14 SIP rport Management for NAT
Traversal.
%RPORT_USE_LO Y Y false For more information, see section
CAL_PORT_WXT% 6.1.14 SIP rport Management for NAT
Traversal.
%USE_TLS_WXT% Y Y false For more information, see section 6.1.2
SIP Over TLS and Secure Real-time
Transport Protocol.
%SBC_ADDRESS_ Y Y empty For more information, see section 5.6
WXT% System Default Tags.

%SBC_PORT_WXT Y Y 5060 For more information, see section 5.6

% System Default Tags.

%USE_PROXY_DIS Y Y false For more information, see section 6.1.6

COVERY_WXT% Dynamic SIP Proxy Discovery.

%USE_TCP_FROM Y Y true For more information, see section 6.1.6

_DNS_WXT% Dynamic SIP Proxy Discovery.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 24

 Tag Used in Used Default Section
Desktop in Value
Mobile
/Tablet
%USE_UDP_FROM Y Y true For more information, see section 6.1.6
_DNS_WXT% Dynamic SIP Proxy Discovery.

%USE_TLS_FROM_ Y Y true For more information, see section 6.1.6

DNS_WXT% Dynamic SIP Proxy Discovery.

%DOMAIN_OVERRI Y Y empty For more information, see section 6.1.6

DE_WXT% Dynamic SIP Proxy Discovery.

%PROXY_DISCOV Y Y true For more information, see section 6.1.6

ERY_ENABLE_BAC Dynamic SIP Proxy Discovery.
KUP_SERVICE_WX
T%
%PROXY_DISCOV Y Y true For more information, see section 6.1.6
ERY_ENABLE_SRV Dynamic SIP Proxy Discovery.
_BACKUP_WXT%
%PROXY_DISCOV Y N false For more information, see section 6.1.6
ERY_BYPASS_OS_ (Windows Dynamic SIP Proxy Discovery.
CACHE_WXT% only)
%SIP_TRANSPORT Y Y 5000 For more information, see section 6.1.5
S_TCP_CONNECT_ Configurable Timeout for Opening SIP
TIMEOUT_WXT% Socket.
%SIP_TRANSPORT Y Y 10000 For more information, see section 6.1.5
S_TLS_CONNECT_ Configurable Timeout for Opening SIP
TIMEOUT_WXT% Socket.
%SOURCE_PORT_ Y Y 5060 For more information, see section 6.1.7
WXT% Preferred-Port Usage for SIP.

%SIP_FAILBACK_E Y N true For more information, see section

NABLED_WXT% 6.1.8.2 SIP Failback.

%SIP_FAILBACK_TI Y N 900 For more information, see section

MEOUT_WXT% 6.1.8.2 SIP Failback.

%SIP_FAILBACK_U Y N false For more information, see section

SE_RANDOM_FAC 6.1.8.2 SIP Failback.
TOR_WXT%
%SIP_TRANSPORT Y Y dns For more information, see section
S_ENFORCE_IP_V 6.1.8.3. Enforce IP Version.
ERSION_WXT%
%USE_ALTERNATI Y Y false For more information, see section
VE_IDENTITIES_ 6.1.10 Use P-Associated-URIs in
WXT% REGISTER.
%TCP_SIZE_THRE Y Y 18000 For more information, see section 6.1.4
SHOLD_WXT% Force TCP, TLS or UDP Usage and
Keepalives.
%SIP_REFRESH_O Y N false For more information, see section
N_TTL_WXT% 6.1.8.4 DNS TTL Management.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 25

 Tag Used in Used Default Section
Desktop in Value
Mobile
/Tablet
%ENABLE_SIP_UP Y Y false For more information, see section
DATE_SUPPORT_ 6.1.12 SIP UPDATE Support.
WXT%
%ENABLE_PEM_S Y Y false For more information, see section
UPPORT_WXT% 6.1.11 SIP P-Early Media (PEM)
Header.
%ENABLE_SIP_SE Y Y false For more information, see section
SSION_ID_WXT% 6.1.15 SIP Session ID.

%ENABLE_FORCE Y Y false For more information, see section

_SIP_INFO_FIR_ 6.1.13 Legacy SIP INFO FIR.
WXT%
%SRTP_ENABLED_ Y Y false For more information, see section 6.1.2
WXT% SIP Over TLS and Secure Real-time
Transport Protocol.
%SRTP_MODE_ Y Y false For more information, see section 6.1.2
WXT% SIP Over TLS and Secure Real-time
Transport Protocol.
%ENABLE_REKEYI Y Y true For more information, see section 6.1.2
NG_WXT% SIP Over TLS and Secure Real-time
Transport Protocol.
%RTP_AUDIO_POR Y Y 8000 For more information, see section
T_RANGE_START_ 6.1.17 Real-Time Transport Protocol
WXT% Port Range.
%RTP_AUDIO_POR Y Y 8099 For more information, see section
T_RANGE_END_W 6.1.17 Real-Time Transport Protocol
XT% Port Range.
%RTP_VIDEO_POR Y Y 8100 For more information, see section
T_RANGE_START_ 6.1.17 Real-Time Transport Protocol
WXT% Port Range.
%RTP_VIDEO_POR Y Y 8199 For more information, see section
T_RANGE_END_ 6.1.17 Real-Time Transport Protocol
WXT% Port Range.
%ENABLE_RTCP_ Y Y true For more information, see section
MUX_WXT% 6.1.19 RTCP MUX.

%ENABLE_XSI_ Y Y true For more information, see section

EVENT_CHANNEL_ 6.1.33 XSI Event Channel.
WXT%
%CHANNEL_HEAR Y Y 10000 For more information, see section
TBEAT_WXT% 6.1.33 XSI Event Channel.

%XSI_ROOT_WXT Y Y empty For more information, see section

% (uses 6.1.32 XSI Root and Paths.
original
URL)

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 26

 Tag Used in Used Default Section
Desktop in Value
Mobile
/Tablet
%XSI_ACTIONS_PA Y Y /com.br For more information, see section
TH_WXT% oadsoft 6.1.32 XSI Root and Paths.
.xsi-
actions
/
%XSI_EVENTS_PA Y Y /com.br For more information, see section
TH_WXT% oadsoft 6.1.32 XSI Root and Paths.
.xsi-
events/
%ENABLE_CALLS_ Y Y false For more information, see section
AUTO_RECOVERY 6.1.25 Call Auto Recovery / Seamless
_WXT% Call Handover.
%EMERGENCY_CA N Y cs-only For more information, see section 6.3.1
LL_DIAL_SEQUENC Emergency Calling.
E_WXT%
%ENABLE_CALL_PI Y N false For more information, see section 6.2.2
CKUP_BLIND_WXT Call Pickup.
%
%ENABLE_CALL_PI Y N false For more information, see section 6.2.2
CKUP_DIRECTED_ Call Pickup.
WXT%
%WEB_CALL_SETT Y Y empty For more information, see section
INGS_URL_WXT% 6.1.30 Settings Portal and Web-based
Call Settings.
%USER_PORTAL_ Y Y empty For more information, see section
SETTINGS_URL_ 6.1.30 Settings Portal and Web-based
WXT% Call Settings.
%ENABLE_CALL_ Y Y false For more information, see section
CENTER_WXT% 6.1.31 Call Center / Call Queue
Login/Logout.
%WEB_CALL_SETT Y Y externa For more information, see section
INGS_TARGET_ l 6.1.30 Settings Portal and Web-based
WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_CFA_VISIBLE 6.1.30 Settings Portal and Web-based
_WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_DND_VISIBL 6.1.30 Settings Portal and Web-based
E_WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_ACR_VISIBL 6.1.30 Settings Portal and Web-based
E_WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_CFB_VISIBLE 6.1.30 Settings Portal and Web-based
_WXT% Call Settings.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 27

 Tag Used in Used Default Section
Desktop in Value
Mobile
/Tablet
%WEB_CALL_SETT Y Y true For more information, see section
INGS_CFNR_VISIB 6.1.30 Settings Portal and Web-based
LE_WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_CFNA_VISIBL 6.1.30 Settings Portal and Web-based
E_WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_SIMRING_VI 6.1.30 Settings Portal and Web-based
SIBLE_WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_SEQRING_VI 6.1.30 Settings Portal and Web-based
SIBLE_WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_RO_VISIBLE_ 6.1.30 Settings Portal and Web-based
WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_ACB_VISIBLE 6.1.30 Settings Portal and Web-based
_WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_CW_VISIBLE 6.1.30 Settings Portal and Web-based
_WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_CLIDB_VISIB 6.1.30 Settings Portal and Web-based
LE_WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_PA_VISIBLE_ 6.1.30 Settings Portal and Web-based
WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_BWA_VISIBL 6.1.30 Settings Portal and Web-based
E_WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_CC_VISIBLE_ 6.1.30 Settings Portal and Web-based
WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_BWM_VISIBL 6.1.30 Settings Portal and Web-based
E_WXT% Call Settings.
%WEB_CALL_SETT Y Y true For more information, see section
INGS_VM_VISIBLE_ 6.1.30 Settings Portal and Web-based
WXT% Call Settings.
%USE_MEDIASEC_ Y Y false For more information, see section 6.1.3
WXT% 3GPP SIP Headers for SRTP.

%ENABLE_DIALING N Y false For more information, see section 6.3.4

_CALL_BACK_WXT Click to Dial (Call Back).
%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 28

 Tag Used in Used Default Section
Desktop in Value
Mobile
/Tablet
%DIALING_CALL_B N Y 10 For more information, see section 6.3.4
ACK_TIMER_WXT% Click to Dial (Call Back).

%ENABLE_EXECU Y N false For more information, see section 6.2.3

TIVE_ASSISTANT_ Boss-Admin (Executive-Assistant)
WXT% Support.
%PN_FOR_CALLS_ N Y 35 For more information, see section 6.3.2
RING_TIMEOUT_S Push Notifications for Calls.
ECONDS_WXT%
%ENABLE_CALL_R Y Y false For more information, see section
ECORDING_WXT% 6.1.26 Call Recording.

%ENABLE_SINGLE N Y false For more information, see section 6.3.3

_ALERTING_WXT% Single Alerting.

%ENABLE_CALL_P Y Y false For more information, see section

ARK_WXT% 6.1.23 Call Park/Retrieve.

%CALL_PARK_AUT Y Y 10 For more information, see section

O_CLOSE_DIALOG 6.1.23 Call Park/Retrieve.
_TIMER_WXT%
%ENABLE_RTP_IC Y Y false For more information, see section
E_WXT% 6.1.18 ICE Support (Webex Calling
only).
%RTP_ICE_MODE_ Y Y icestun For more information, see section
WXT% 6.1.18 ICE Support (Webex Calling
only).
%RTP_ICE_SERVIC Y Y empty For more information, see section
E_URI_WXT% 6.1.18 ICE Support (Webex Calling
only).
%RTP_ICE_PORT_ Y Y 3478 For more information, see section
WXT% 6.1.18 ICE Support (Webex Calling
only).
%SIP_REFRESH_O Y N false For more information, see section
N_TTL_USE_RAND 6.1.8.4 DNS TTL Management.
OM_FACTOR_WXT
%
%ENABLE_CALLS_ Y N false For more information, see section 6.2.4
ESCALATE_TO_WE Escalate SIP Calls to Meeting.
BEX_MEETING_
WXT%
%ENABLE_DESKP Y N false For more information, see section 6.2.5
HONE_CONTROL_ Desk Phone Control Calling – Auto
AUTO_ANSWER_ Answer.
WXT%
%ENABLE_DIALING N Y true For more information, see section 6.3.5
_VOIP_WXT% MNO Support
Call with Native Dialer.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 29

 Tag Used in Used Default Section
Desktop in Value
Mobile
/Tablet
%ENABLE_DIALING N Y false For more information, see section 6.3.5
_NATIVE_WXT% MNO Support
Call with Native Dialer.
%SIP_URI_DIALING Y Y true For more information, see section
_ENABLE_LOCUS_ 6.1.35 SIP-URI Dialing.
CALLING_WXT%
%ENABLE_SIP_VID Y Y true For more information, see section
EOCALLS_WXT% 6.1.37 Disable Video Calls.

%ENABLE_LOCUS_ Y Y true For more information, see section

VIDEOCALLS_WXT 6.1.37 Disable Video Calls.
%
%VIDEOCALLS_AN Y Y Desktop For more information, see section
SWER_WITH_VIDE - true 6.1.37 Disable Video Calls.
O_ON_DEFAULT_
WXT% Mobile /
Tablet -
false
%EMERGENCY_ Y Y false For more information, see section
DIALING_ENABLE_ 6.1.38 Emergency (911) Calling -
REDSKY_WXT% Location Reporting with E911 Provider.
%EMERGENCY_RE Y Y 0 For more information, see section
DSKY_USER_REMI 6.1.38 Emergency (911) Calling -
NDER_TIMEOUT_ Location Reporting with E911 Provider.
WXT%
%EMERGENCY_RE Y Y -1 For more information, see section
DSKY_USER_MAN 6.1.38 Emergency (911) Calling -
DATORY_LOCATIO Location Reporting with E911 Provider.
N_WXT%
%EMERGENCY_RE Y Y once_p For more information, see section
DSKY_USER_LOCA er_logi 6.1.38 Emergency (911) Calling -
TION_PROMPTING n Location Reporting with E911 Provider.
_WXT%
%ENABLE_AUTO_ Y N false For more information, see section 6.2.6
ANSWER_WXT% Auto Answer with Tone Notification.

%ENABLE_CALLS_ Y Y false For more information, see section

SPAM_INDICATION 6.1.41 Spam Call Indication.
_WXT%
%ENABLE_NOISE_ Y Y false For more information, see section
REMOVAL_WXT% 6.1.42 Noise Removal for PSTN/Mobile
Calls.
%ENABLE_AUDIO_ Y Y false For more information, see section
MARI_FEC_WXT% 6.1.46.2 Forward Error Correction (FEC)
and Packets Retransmission (RTX).
%ENABLE_AUDIO_ Y Y false For more information, see section
MARI_RTX_WXT% 6.1.46.2 Forward Error Correction (FEC)
and Packets Retransmission (RTX).

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 30

 Tag Used in Used Default Section
Desktop in Value
Mobile
/Tablet
%ENABLE_VIDEO_ Y Y false For more information, see section
MARI_FEC_WXT% 6.1.46.2 Forward Error Correction (FEC)
and Packets Retransmission (RTX).
%ENABLE_VIDEO_ Y Y false For more information, see section
MARI_RTX_WXT% 6.1.46.2 Forward Error Correction (FEC)
and Packets Retransmission (RTX).
%ENABLE_CALL_B Y Y false For more information, see section
LOCK_WXT% 6.1.45 Block List (Webex Calling only).

%ENABLE_WIDGET N Y true For more information, see section

_HOLD_CALLS_WX 6.3.5.6 MNO Mobility - In-call Widget.
T%
%ENABLE_WIDGET N Y true For more information, see section
_TRANSFER_CALL 6.3.5.6 MNO Mobility - In-call Widget.
S_WXT%
%ENABLE_WIDGET N Y true For more information, see section
_CALLS_ESCALAT 6.3.5.6 MNO Mobility - In-call Widget.
E_TO_WEBEX_ME
ETING_WXT%
%ENABLE_MULTIP Y Y false For more information, see section 7.1
LE_CALLS_PER_U Simultaneous Calls with Same User.
SER_WXT%

For more information about mapping the custom tags used in Webex for Cisco BroadWorks to the
ones used by UC-One, see section 8 Custom Tags Mapping between Webex for Cisco
BroadWorks and UC-One.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 31

 6.1 Common Features

6.1.1 Change Basic SIP Server Settings

The client is commonly configured to use a SIP network, which is done by modifying the config-
wxt.xml file. Typically, the following parameters must be changed:
▪ SIP domain. This is used as the domain part of own SIP URI (own SIP URI is also sometimes
called line port) in general in SIP headers and in Xsi calls. The user part of own SIP URI
comes from SIP credentials configuration (parameter <username> under <credentials>).
▪ SIP server URI or IP address of the SIP proxy server if DNS resolving should fail. Note that in
order to use TLS, IP addresses cannot be used in the proxy parameter as TLS certificate
validation will fail. For more information on the proxy port, see the DM tag
%SOURCE_PORT_WXT%. Note that the DNS TTL management feature cannot be used
when an IP address is used in the proxy address parameter. In general, it is not
recommended to use an IP address in this field for these reasons.
Other parameters can also be changed to enable various features for calling. However, the
previous settings enable basic functionality for the following:
▪ Registering on the SIP network.
▪ Making audio or video calls.
▪ Performing DNS-based proxy discovery, which allows using several proxies.
Once SIP registration is enabled, enabling SIP SUBSCRIBE for MWI must be done via separate
configuration parameters. For more information on voicemail, see section 6.1.27 Voicemail,
Visual Voicemail, Message Waiting Indicator.
Note that basic SIP configuration is always needed for MWI even when SIP calls are disabled.
MWI relies on SIP NOTIFYs.
The setup of the SIP servers follows this basic scheme:
▪ The proxy address contains the SIP server URI.
▪ Only one proxy can be defined.
▪ The DNS proxy discovery provides support for many proxies, which require the proper set up
of the DNS.
In addition, SIP timers are exposed in the configuration file (not recommended to modify them).
<config>
<protocols>
<sip>
<timers>
<T1>500</T1>
<T2>4000</T2>
<T4>5000</T4>
</timers>

▪ T1 – the amount of time, in milliseconds, for a network round trip delay.

▪ T2 – the maximum amount of time, in milliseconds, before retransmitting non-invite requests
and invite responses.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 32

▪ T4 – the maximum amount of time, in milliseconds, for a message to remain in the network.
Each line has own SIP authentication credentials. Separate credentials can be used for 401 and
407 signaling if needed.
<config>
<protocols><sip>
<lines multi-line-enabled="%ENABLE_MULTI_LINE_WXT%">
<line>
<label>%BWAPPEARANCE-LABEL-1%</label>
<name>%BWNAME-1%</name>
<phone-number>%BWE164-1%</phone-number>
<extension>%BWEXTENSION-1%</extension>
<voice-mail-number>%BWVOICE-PORTAL-NUMBER-1%</voice-mail-number>
<conference-service-uri>sip:%BWNETWORK-CONFERENCE-SIPURI-
1%</conference-service-uri>
<credentials>
<username>%BWLINEPORT-1%</username>
<password>%BWAUTHPASSWORD-1%</password>
<auth>
<auth401>
<default>
<username>%BWAUTHUSER-1%</username>
<password>%BWAUTHPASSWORD-1%</password>
</default>
<realm id="%BWHOST-1%">
<username>%BWAUTHUSER-1%</username>
<password>%BWAUTHPASSWORD-1%</password>
</realm>
</auth401>
<auth407>
<default>
<username>%BWAUTHUSER-1%</username>
<password>%BWAUTHPASSWORD-1%</password>
</default>
<realm id=”%BWHOST-1%”>
<username>%BWAUTHUSER-1%</username>
<password>%BWAUTHPASSWORD-1%</password>
</realm>
</auth407>
</auth>
</credentials>
</line>
…
</lines>
<proxy address="%SBC_ADDRESS_WXT%" port="%SBC_PORT_WXT%" />
<domain>%BWHOST-1%</domain>
<preferred-port>%SOURCE_PORT_WXT%</preferred-port>

The following example and table provide information on the most typical DM tags used for SIP
configuration.
Tag Default if Supported Description
Omitted Values
%BWLINEPORT-1% empty string Typically SIP username.
For more information, see section 5.7 Cisco
BroadWorks Dynamic Built-in System Tags.
Example: johndoe

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 33

 Tag Default if Supported Description
Omitted Values
%BWAUTHPASSWORD empty string Typically SIP password.
-1% For more information, see section 5.7 Cisco
BroadWorks Dynamic Built-in System Tags.
Example: secretpassword
%BWE164-1% empty phone Default phone number for the user in
number international format.
For more information, see section 5.7 Cisco
BroadWorks Dynamic Built-in System Tags.
Example: 12345678
%SBC_ADDRESS_WXT empty string For more information, see section 5.6 System
% Default Tags.
Example: sbcexample.domain.com
%SBC_PORT_WXT% 5060 number For more information, see section 5.6 System
Default Tags.
Example: 5060
%BWHOST-1% empty string Typically used as the SIP domain.
For the list of Cisco BroadWorks tags, see
section 5.7 Cisco BroadWorks Dynamic Built-in
System Tags.
Example: exampledomain.com
%SOURCE_PORT_WXT 5060 number Typically used for the preferred-port parameter.
% For more information, see section 6.1.7
Preferred-Port Usage for SIP.
Example: 5061

NOTE: It is strongly advisable for the SIP port to be different from 5060 (for example, 5075) due to
known issues with using the standard SIP port (5060) with mobile devices.

6.1.2 SIP Over TLS and Secure Real-time Transport Protocol

The client can be configured to use SIP signaling over TLS and Secure Real-time Transport
Protocol (SRTP) for media encryption. However, these features must be enabled in the
configuration as shown in the following example. Note also that when dynamic SIP proxy
discovery is used, DNS SRV priorities override static parameters such as this one
(%USE_TLS_WXT%), and non-TLS transport is used if it has a higher priority in DNS SRV. For
more information on dynamic SIP proxy discovery, see section 6.1.6 Dynamic SIP Proxy
Discovery.
When dynamic proxy discovery is not used, enabling TLS for SIP takes it into use.
For details on SIP port and transport protocol recommendations when SIP ALGs are used in the
network, see the Webex for Cisco BroadWorks Solution Guide.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 34

Note that the certificate used must be valid. Furthermore, the certificate chain must be intact so
that the intermediate certificate is also linked. It is recommended that a widely used certificate be
employed so that is already present, by default, on the devices. It is also possible to add
certificates locally on the desktop machine either manually or by using bulk provisioning, although
this is not typically done.
To enable the related SRTP for media encryption, there is a separate setting.
In addition to RTP, RTCP traffic can be secured with the same mechanisms as RTP using the
preceding configuration.
For SIP/TLS ciphers, see Appendix A: TLS Ciphers.
The SRTP is used to provide security for the media stream in three different aspects:
▪ Confidentiality (data is encrypted)
▪ Authentication (assurance of the identity of the other party or parties)
▪ Integrity (measures against, for example, replay attacks)
The current version of the media framework supports AES 128 Counter Mode for protection and
Hash Message Authentication Code (HMAC)-SHA-1 for authentication. The master key size is 16
bytes and master salt is 14 bytes.
The media framework supports both the full (80-bit) and short (32-bit) authentication tag. The
client exchanges the keys inside the SDP as part of SIP signaling, both sides of the call send the
key they use to the other side.
SRTP can be enabled using the configuration shown in the following example. The current
implementation uses only the SDP secure RTP profile and supports multiline SDP for Audio
Visual Profile (AVP) and Secure Audio Visual profile (SAVP) entries. The SRTP implementation
has been tested successfully in its usual deployment configuration with various SBCs.
Interoperability Testing (IOT) with endpoints that only support encryption using the AVP profile is
not supported.
Multiline SDP procedures related to SRTP is implemented, so that multiple m-lines are always
used. Separate m-lines for AVP and SAVP are used.
Note, however, careful consideration must be given to the SBC configuration; particularly
ensuring that the incoming “m=” line, associated with RTP/SAVP in the SDP, is not removed
because in certain cases SRTP calls may be blocked.
Several different network configurations are however possible, in some deployments the SBC is
not involved with the media traffic while in other deployments each client RTP media leg towards
the SBC is separately encrypted and negotiated via the SBC. In some deployments, the SBC
does not allow multiple SDP lines.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 35

The SBC can also modify the order of the SDP m-lines at call setup, putting the AVP (non-
encrypted) or SAVP (encrypted) m-line first. Therefore, clients that select the first working m-line
are made to prefer either encrypted or unencrypted traffic. The various SRTP configuration
options are as follows:
▪ Mandatory – At call setup, the initial SDP includes only the SAVP m-line when offering and
the client accepts only the SAVP m-line in the SDP when answering, therefore only SRTP
calls are possible.
▪ Preferred – At call setup, the initial SDP includes both the AVP and SAVP m-lines, but SAVP
is first when offering, indicating the order of preference. When answering, the client selects
SAVP if available even if is not the first m-line (as per SIP specifications the order of the m-
lines is not changed when answering).
▪ Optional – At call setup, the initial SDP includes both the SAVP and AVP m-lines when
offering but AVP is first indicating the order of preference. When answering, the client selects
the first m-line, AVP or SAVP.
▪ SRTP not enabled – There is no SAVP m-line in the initial SDP when offering. When
answering, SAVP is not accepted, therefore only RTP calls are possible.
▪ Transport – Automatically select the SRTP mode based on transport protocol. If TLS is used,
mandatory SRTP mode is enabled. If TCP or UDP is used, no SRTP is utilized.
SRTP versus RTP is symmetric in both directions of the call, that is, sending and receiving
profiles are the same.
<config>
<protocols><sip>
<secure>%USE_TLS_WXT%</secure>

<config>
<protocols><rtp>
<secure enabled="%SRTP_ENABLED_WXT%" mode="%SRTP_MODE_WXT%" rekey-
always="%ENABLE_REKEYING_WXT%"/>

The Secure Real-Time Control Protocol (SRTCP) is also used if SRTP is enabled.
In some deployments, re-keying for SRTP is not supported. Therefore, there is a configuration
parameter for enabling/disabling SRTP re-keying. However, new keys are always taken into use
when received in an updated SDP according to rfc3264. Configurability only pertains to sending
new keys.
Tag Default if Supported Description
Omitted Values
%USE_TLS_WXT% false true, false When set to “false”, SIP TLS is deactivated.
When set to “true”, SIP TLS is activated.
Please note that if 6.1.6 Dynamic SIP Proxy
Discovery is used, this parameter is ignored.
%SRTP_ENABLED_ false true, false When set to “false”, SRTP is deactivated.
WXT% When set to “true”, SRTP is activated.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 36

 Tag Default if Supported Description
Omitted Values
%SRTP_MODE_ optional mandatory, Defines how preferred SRTP is at call setup.
WXT% preferred, The default value is “optional”.
optional,
transport
%ENABLE_REKEYI true true, false Enables SIP (SDP) re-keying for SRTP.
NG_WXT%

NOTE: If ICE support is enabled (see 6.1.18 ICE Support (Webex Calling only)), re-keying will always be
performed (%ENABLE_REKEYING_WXT% value from the configuration is ignored).

6.1.3 3GPP SIP Headers for SRTP

Newer 3GPP specifications require additional SIP headers to use Secure Real-time Transport
Protocol (SRTP). For more information, see 3GPP TS 24.229 as well as the following:
https://tools.ietf.org/html/draft-dawes-dispatch-mediasec-parameter-07
The headers required by this specification may break SIP calling in deployments where this
specification is not used. Therefore, these headers are recommended to be used only in
environments where the server side supports them.
Only enabling the usage of the headers is configurable. No further configurability exists for
individual headers. All headers are either enabled or disabled.
<config>
<protocols><sip>
<use-mediasec enabled="%USE_MEDIASEC_WXT%"/>

The following tag controls this capability.

Tag Default if Supported Description
Omitted Values
%USE_MEDIASEC_ false true, false Enables 3GPP SIP headers for SRTP
WXT% negotiation.

6.1.4 Force TCP, TLS or UDP Usage and Keepalives

The Webex for Cisco BroadWorks client can be configured to use either TCP, TLS or UDP for
both SIP signaling and RTP media. Note that the client defaults to TCP. Note as well that without
TCP keepalive, SIP TCP connections are closed after a period of inactivity.
The following example depicts this configuration node.
<config>
<protocols><sip>
<transports>
<tcp-size-threshold>%TCP_SIZE_THRESHOLD_WXT%</tcp-size-threshold>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 37

The following tag, controls whether the client uses TCP or UDP.
Tag Default if Supported Description
Omitted Values (Bytes)
%TCP_SIZE_THR 0 0 Forces TCP to be used. The decision to use TCP
ESHOLD_WXT% or UDP for the client is up to the service provider;
however, the recommendation is to use TCP with
the default value “0”.
0 1 through Forces UDP to be used when the message size is
99,000 below the value specified here.
This defaults to TCP when the message size is
greater than the set value. To use UDP, 1500 is
the default recommendation.
0 100000 Forces UDP to be used.

The same configuration node also has parameters for UDP, TCP and TLS keepalive, depicted in
the following example.
<config>
<protocols><sip>
<transports>
<udp>
<keepalive enabled="true">
<timeout>20</timeout>
<payload>crlf</payload>
</keepalive>
</udp>
<tcp>
<keepalive enabled=”false”>
<timeout>0</timeout>
<payload></payload>
</keepalive>
</tcp>
<tls>
<keepalive enabled="false">
<timeout>0</timeout>
<payload></payload>
</keepalive>
</tls>
</transports>

The possible parameters are:

▪ Enabling TCP or TLS keepalive, possible values - true/false, the default is “false” if the node
is missing. Note that when this feature is enabled, TCP keepalives are sent even if UDP
transport is being used for SIP.
▪ Enabling UDP keepalive, possible values - true/false, the default is “false” if the node is
missing. Note that when this feature is enabled, UDP keepalives are sent even if TCP
transport is being used for SIP. Additionally, even if TCP is used for SIP, the client also
accepts traffic over UDP as per RFC 3261.
▪ Timeout specifies the maximum time of inactivity in seconds after which the keepalive
message is sent. No value means the keepalive is disabled for the protocol.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 38

▪ Payload for the keepalive messages, possible values (no value means keepalive is disabled
for the protocol):
- Crlf
- Null (not to be used)
- Custom string (not to be used)
<config>
<protocols><sip>
<transports>
<tcp-size-threshold>%TCP_SIZE_THRESHOLD_WXT%</tcp-size-threshold>
<udp>
<keepalive enabled="true">
<timeout>20</timeout>
<payload>crlf</payload>
</keepalive>
</udp>
<tcp>
<keepalive enabled="false">
<timeout>0</timeout>
<payload></payload>
</keepalive>
</tcp>

The keepalives can be used for NAT traversal purposes to keep NAT bindings open with little
extra traffic.
The server IP address and port for keepalives are determined using the normal procedures for
SIP proxy discovery. Note that SIP ports and selection of transport protocol obtained via SIP
dynamic proxy discovery override any static port or transport configuration. For more information
on dynamic proxy discovery, see section 6.1.6 Dynamic SIP Proxy Discovery.

6.1.5 Configurable Timeout for Opening SIP Socket

Previously, the timeout for opening a SIP socket was hardcoded to 5 seconds for TCP and 10
seconds for TLS. These timeouts are now configurable.
<config>
<protocols>
<sip>
<transports>
<udp>
…
</udp>
<tcp>
…
<connect-
timeout>%SIP_TRANSPORTS_TCP_CONNECT_TIMEOUT_WXT%</connect-timeout>
</tcp>
<tls>
<connect-
timeout>%SIP_TRANSPORTS_TLS_CONNECT_TIMEOUT_WXT%</connect-timeout>
</tcp>
</transports>

The following tags control the socket connection timeout (in milliseconds).

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 39

 Tag Default if Supported Description
Omitted Values
%SIP_TRANSPORTS_ 5000 <integer> - The socket connection timeout when TCP
TCP_CONNECT_TIME the timeout in transport is used.
OUT_WXT% milliseconds
%SIP_TRANSPORTS_ 10000 <integer> - The socket connection timeout when TLS
TLS_CONNECT_TIME the timeout in transport is used.
OUT_WXT% milliseconds

6.1.6 Dynamic SIP Proxy Discovery

To enable SIP dynamic proxy discovery functionality, see the following example.
<config>
<protocols><sip>
<proxy-discovery enabled="%USE_PROXY_DISCOVERY_WXT%” tcp=”%USE_TCP_FROM_DNS_WXT%"
udp="%USE_UDP_FROM_DNS_WXT%" tls="%USE_TLS_FROM_DNS_WXT%">
<record-name>%SBC_ADDRESS_WXT%</record-name>
<domain-override>%DOMAIN_OVERRIDE_WXT%</domain-override>
</proxy-discovery>

It is possible to control which transport protocols entries from DNS SRV are used when many are
available following the procedures provided in this section.
Tag Default if Supported Description
Omitted Values
%USE_PROXY_DI false true, false Enables dynamic SIP proxy discovery for audio
SCOVERY_WXT% and video calls.
The recommended value is “true”.
%SBC_ADDRESS_ empty String This Cisco BroadWorks tag is typically used for
WXT% the record-name parameter. It should be a valid
URL – should not be an IP address.
For more information, see section 5.6 System
Default Tags.
Example: sbc.domain.com
%DOMAIN_OVER empty String This custom tag is used for the domain-override.
RIDE_WXT% For more information, see the following section.
Example: other.domain.com
%USE_TCP_FRO true true, false If this parameter value is “false”, then the DNS
M_DNS_WXT% SRV results for this transport protocol (TCP) are
discarded.
If “true”, then the results from DNS SRV for this
transport protocol (TCP) are used. Depending on
the SRV priorities, another transport may still be
elected.
%USE_UDP_FRO true true, false If this parameter value is “false”, then the DNS
M_DNS_WXT% SRV results for this transport protocol (UDP) are
discarded.
If “true”, then the results from DNS SRV for this
transport protocol (UDP) are used. Depending on
the SRV priorities, another transport may still be
elected.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 40

 Tag Default if Supported Description
Omitted Values
%USE_TLS_FROM true true, false If this parameter value is “false”, then the DNS
_DNS_WXT% SRV results for this transport protocol (TLS) are
discarded.
If “true”, then the results from DNS for this
transport protocol (TLS) are used. Depending on
the SRV priorities, another transport may still be
elected.
%PROXY_DISCOV true, true Enables/disables the DNS backup service. If
ERY_ENABLE_BA false enabled, then A/AAAA resolution is performed for
CKUP_SERVICE_ the SIP proxy address. It is taken into account
WXT% only when SRV/NAPTR service discovery is
enabled.
%PROXY_DISCOV true, true If set to “true” and NAPTR service discovery fails
ERY_ENABLE_SR false or returns no results, then SRV service discovery
V_BACKUP_WXT is performed for the configured host. If set to
% “false”, then no SRV discovery is performed.
%PROXY_DISCOV true, false Allows for the bypass of the OS DNS cache.
ERY_BYPASS_OS false
_CACHE_WXT%

DNS allows the client to get the IP address, port, and transport protocol for the SIP proxy as per
RFC 3263.
DNS SRV, Naming Authority Pointer (NAPTR) and A-record queries are supported. At login, the
3-step flow is as follows:
1. Perform a NAPTR query using the <record-name> field above to obtain the server URIs with
the transport protocols if they exist. The value for the <record-name> parameter should be
the full domain that DNS is to resolve and cannot be an IP address.
2. Resolve items found in the NAPTR query using an SRV-query to obtain the final server URI
and port. The domain part used in the SRV-query is taken from the result of the NAPTR
query to find the final server URI (and port). The port received from DNS SRV-query is used
when the DNS SRV entries are available. Note that the port, only from the configuration file,
applies to the static proxy in the configuration file, and not to the URIs resolved using SRV.
See the following examples for the usage of the various record names.
If no NAPTR is found, then the client tries an SRV-query with the record-name taken from
<domain> parameter unless there is <domain-override> parameter present in which case
<domain-override> is used and automatically tries to find separate entries for TCP, UDP, and TLS
(_sip_protocol [UDP, TCP, or TLS]). Note that the Stream Control Transmission Protocol (SCTP) is
not supported. If SRV queries do not yield any results, proxy discovery fails, and the end user is
presented with an error indicating that calls are not available. In this case, there is no SIP
registration. However, even if all SRV queries fail or if the servers received there do not work, as a
fallback, the client still checks if the configured static proxy works, only with A-queries to the URI
specified in <proxy address> in order to see if it yields an IP address that provides a working SIP
registration. Port and transport in this last resort case come from tcp-threshold and <secure>
parameters.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 41

3. Resolve found URIs using the A-record query. The received final IP addresses are tried in the
order in which they are received to get a working connection to the SIP proxy. This order can
be defined by the service provider in the DNS. The first SIP proxy URI, with a successful A-
record lookup, is selected and is used until it no longer works, or the client logs out. In the A-
query step, only one IP address is used at a time even if many are received. However, all
SRV entries are resolved until logout or loss of the network.
Important Notes

NOTE 1: If DNS proxy discovery results in transport protocol selection in the SRV step by receiving a
working SIP proxy URI for a transport protocol, it overrides the tcp-threshold parameter typically used to
select UDP or TCP in the configuration file. The same also applies to configuration of SIP/TLS. TCP or
UDP is used depending on the priority in DNS.

NOTE 2: Items received via SRV are prioritized over the static proxy in the configuration file. The NAPTR
order is not looked at; only SRV priority counts. When SRV results in several items with equal transport
protocol, priority, and weight, any one received is selected at random. NAPTR weights are not supported
in this release but SRV weights are supported. SRV priority is looked at first, and for items with equal
priority, weight is looked at to determine the likelihood in which a certain server is tried next.

NOTE 3: The optional domain-override parameter allows A-record name other than the one in the SIP
domain configuration parameter to be resolved with SRV when NAPTR results are omitted. See the
following examples for the usage of the domain-override parameter.

NOTE 4: The client uses operating system primitives for DNS operations and, typically, DNS responses
are cached to honor the TTL of the DNS response.

NOTE 5: The DNS type (service) for NAPTR records must follow RFC 3263 procedures, otherwise, DNS
resolution may fail. For example, it is required to use SIPS+D2T for SIP over TLS.

NOTE 6: The client supports only certain prefixes for NAPTR services. The following lists the supported
prefixes:

SIP+D2U -> _sip._udp

SIP+D2T -> _sip._tcp

SIPS+D2T -> _sips._tcp

SIPS+D2T -> _sips._tls

If the NAPTR response contains a record with prefix that does not match the service type, then this
record is ignored.

Example 1: Using DNS proxy discovery without domain-override configuration parameter

The following is an example of a configuration using SIP proxy discovery when only SIP over TCP
is used and NAPTR query in step 1 returns results.
<config>
<protocols><sip>
<proxy address="domain.com" port="5060"/>
<proxy-discovery enabled="true" >

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 42

 <record-name>record-domain.com</record-name>
<domain-override>override-domain.com</domain-override>
</proxy-discovery>
<domain>sip-domain.com</domain>

This results in the following steps in the protocol level.

1. NAPTR query for record-domain.com, answer:
record-domain.com.
28591 IN NAPTR 100 10 "S" "SIP+D2T" "" _sip._tcp.test.sip.record-domain.com.
2. SRV query for _sip._tcp.test.sip.record-domain.com (received in the NAPTR
query), answer
_sip._tcp.test.sip.record-domain.com. 28635 IN SRV
10 10 5061 test.sipgeo.record-domain.com.
3. A-record query for test.sipgeo.record-domain.com, answer:
test.sipgeo.record-domain.com. 16 IN A 1.2.3.4

As a result, the SIP registration takes place over TCP using port 5061 (received in the SRV step)
and towards the IP address 1.2.3.4.

Example 2: Using domain-override parameter in configuration file

The following is a second example of a configuration using SIP proxy discovery where the SIP
domain is different from the proxy domain, and only SIP over UDP, is used and NAPTR query
does not return results.
<config>
<protocols><sip
<proxy address="domain.com" port="5060"/>
<proxy-discovery enabled="true">
<record-name>record-domain.com</record-name>
<domain-override>override-domain.com</domain-override>
</proxy-discovery>
<domain>sip-domain.com</domain>

This results in the following steps at the protocol level.

1. NAPTR query for record-domain.com, no answer.
2. SRV query for _sip._tcp.override-domain.com (from configuration file), answer
_sip._tcp.override-domain.com. 28635 IN SRV
10 10 5061 test.override-domain.com.
3. A-record query for test.override-domain.com, answer:
test.sipgeooverride-domain.com. 16 IN A 4.3.2.1

As a result, the SIP registration takes place over UDP using port 5061 (received in the SRV step)
and towards the IP address 4.3.2.1.

Example 3: Using SRV priorities

The following is another example of a configuration using SIP proxy discovery when only SIP
over TCP is used and NAPTR query in step 1 returns results, but several NAPTR and SRV
records with different priorities are received. In this case, only SRV priority matters in this release
event although several NAPTR records with varying priorities are also received.
<config>
<protocols><sip>
<proxy address="domain.com" port="5060"/>
<proxy-discovery enabled="true">

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 43

 <record-name>record-domain.com</record-name>
<domain-override>override-domain.com</domain-override>
</proxy-discovery>
<domain>sip-domain.com</domain>

This results in the following steps at the protocol level.

1. NAPTR query for record-domain.com, answer:
record-domain.com.
28591 IN NAPTR 100 10 "S" "SIPS+D2T" "" _sip._tcp.test.sip.record-domain.com.
28591 IN NAPTR 120 10 "S" "SIPS+D2U" "" _sip._udp.test.sip.record-domain.com.

2. SRV query for _sip._tcp.test.sip.record-domain.com (received in the NAPTR

query), answer
_sip._tcp.test.sip.record-domain.com. 28635 IN SRV
10 10 5061 test.sipgeo.record-domain.com.

SRV query for _sip._udp.test.sip.record-domain.com (received in the NAPTR query),

answer
_sip._udp.test.sip.record-domain.com. 28635 IN SRV
20 10 5062 test.sipgeo.record-domain.com.

3. A-record query for test.sipgeo.record-domain.com, answer:

test.sipgeo.record-domain.com. 16 IN A 1.2.3.4

As a result, the SIP registration takes place over TCP using port 5061 (received in the SRV step)
and towards the IP address 1.2.3.4 that would support both UDP and TCP.

Example 4: Using DNS proxy discovery with NAPTR when service does not match service type
The following is an example of a configuration using SIP proxy discovery when SIP over TCP and
TLS is used and NAPTR query in step 1 returns results.
<config>
<protocols><sip>
<proxy address="domain.com" port="5060"/>
<proxy-discovery enabled="true" tcp="true" udp="false" tls="true">
<record-name>record-domain.com</record-name>
<domain-override>override-domain.com</domain-override>
</proxy-discovery>
<domain>sip-domain.com</domain>

This results in the following steps in the protocol level.

1. NAPTR query for record-domain.com, answer:
record-domain.com.
28591 IN NAPTR 100 10 "S" "SIPS+D2T" "" _sip._tls.test.sip.record-domain.com.
28591 IN NAPTR 100 10 "S" "SIP+D2T" "" _sip._tcp.test.sip.record-domain.com.

2. For the first record we have service type "SIPS+D2T" and the prefix is
"sip._tls.". Since this prefix doesn’t match the service type (see Note 6 above)
it will be ignored.

3. SRV query for _sip._tcp.test.sip.record-domain.com (received in the NAPTR

query), answer
_sip._tcp.test.sip.record-domain.com. 28635 IN SRV
10 10 5061 test.sipgeo.record-domain.com.

3. A-record query for test.sipgeo.record-domain.com, answer:

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 44

 test.sipgeo.record-domain.com. 16 IN A 1.2.3.4

As a result, the SIP registration takes place over TCP using port 5061 (received in the SRV step)
and towards the IP address 1.2.3.4.

6.1.7 Preferred-Port Usage for SIP

There have been some cases when another software package has been running on the same
machine as the client, occupying the default SIP port. To configure the client to use another port
for SIP, the preferred-port parameter can be used. The client tries to use the configured port
value specified in the preferred-port parameter, but if it is taken, the client incrementally tries port
values above the configured value. For example, if the value of the preferred-port is “6000” and
that port is taken, the client tries 6001, 6002, 6003, and so on until it finds an unused port. Once
an unused port is found, it uses that for its own SIP communication.
Tag Default if Supported Description
Omitted Values
%SOURCE_PORT_WXT% 5060 number Specifies preferred local SIP port for
communication.
Example: 5060

6.1.8 SIP Failover and Failback

SIP failover and failback follow the Cisco BroadWorks procedures. For this, more than one proxy
(typically the SBC) must be configured.
On the client side, the proxy should be resolved to multiple IP addresses. This can be achieved
by either:
▪ SIP Proxy Discovery is enabled and the DNS server has NAPTR and/or SRV records for the
SBC FQDN (see section 6.1.6 Dynamic SIP Proxy Discovery), OR
▪ The SIP proxy address is provided as an FQDN and it is resolved to multiple IP addresses
(see section 6.1.1 Common Features
▪ Change Basic SIP Server Settings).
Operating system DNS cache is used to avoid unnecessary DNS traffic. There is no
hard-coded limit for the maximum number of IP addresses in the list.
At sign-in, if multiple IP addresses are resolved, they are ordered by priority. The client starts
using the first available IP address.

6.1.8.1 SIP Failover

SIP failover may be triggered by either a socket error, a request timeout error, or a definitive error
response from server as follows:
▪ Socket error – if the socket between the client and the server gets broken or is closed, as in
the case of network connectivity loss, the client reacts immediately and triggers a failover.
▪ Timeout (for example, when the SBC hangs) – based on the SIP T1:
- SIP INVITE – if the INVITE request times out, the client registers to the next available
SBC (IP) and retries the INVITE.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 45

 - Another SIP request – the client tries to register to the next available SBC (IP).
▪ Definitive error response received from server:
- The following SIP error responses from the server to a SIP REGISTER trigger a failover:
o 5xx
o 6xx
- The following SIP 4xx responses to SIP REGISTER do not cause failover:
o 401 Unauthorized
o 403 Forbidden
o 404 Not Found
o 407 Proxy Authentication Required
o 423 Interval Too Brief
- Furthermore, 4xx error responses to SIP INVITE do not trigger failover, but 5xx and 6xx
do.
When a failover is triggered, the client takes the next available IP address from the list. SIP T1
timer defines how long a proxy on the list is tried before moving to the next one, typically 32
seconds value is used (64*T1). If all IP addresses fail, then the client displays a user interface
error for SIP connectivity. If a VoIP call is in progress when the failover occurs, the call is
terminated.
The SIP failover logic relies on several configuration parameters:
▪ SIP Failover Timers – SIP timers T1, T2, and T4 are exposed in the configuration file, but it is
not recommended to modify them.
<config><protocols><sip>
<timers>
<T1>500</T1>
<T2>4000</T2>
<T4>5000</T4>
</timers>

- T1 – the amount of time, in milliseconds, for a network round trip delay.

- T2 – the maximum amount of time, in milliseconds, before retransmitting non-invite
requests and invite responses.
- T4 – the maximum amount of time, in milliseconds, for a message to remain in the
network.
▪ SIP Proxy Address and SIP Proxy Discovery
- See section 6.1.1 Common Features
- Change Basic SIP Server Settings.
- See section 6.1.6 Dynamic SIP Proxy Discovery.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 46

 6.1.8.2 SIP Failback
If the client is connected to a proxy that is not first by priority, it tries to reconnect to the IP with
the highest priority. The time for the failback is based on the DNS TTL management configuration
(see section 6.1.8.4 DNS TTL Management). If a call is in progress when the failback timer is
reached, the client waits until all calls are completed and triggers the failback procedure. Note
that this is only valid for desktop clients since the SIP connection is active only while on a call on
mobile.
Tag Default if Supported Description
Omitted Values
%SIP_FAILBACK_ENABL true true, false Enables/disables SIP failback.
ED_WXT%

%SIP_FAILBACK_TIMEOU 900 Over 60 The SIP failback timeout in seconds.

T_WXT%

%SIP_FAILBACK_USE_R false true, false Adds a random period [0-10]% of the SIP
ANDOM_FACTOR_WXT% failback.

6.1.8.3 Enforce IP Version

Webex client can be configured how to order the list of resolved hosts through the DNS and then to
iterate through them in case of SIP failover. In all the modes, the priority and weight is respected.
Supported configurations are:
- dns - uses all the addresses returned by the DNS queries
- ipv4 - filters out the IPv6 addresses
- ipv6 - filters out the IPv4 addresses
- prefer-ipv4 – orders the IPv4 addresses before the IPv6
- prefer-ipv6 – orders the IPv6 addresses before the IPv4

The default value (dns) is recommended to be used, unless environment/network configuration

requires different mode.

With “dns” configuration, the IPv4 addresses are prioritized over the IPv6 ones, for given host. If there
are two hosts with both IPv4 and IPv6 addresses, the order will be IPv4(host1), IPv6(host1),
IPv4(host2), IPv6(host2).
In “prefer-ipv4” mode, the IPv4 addresses are ordered before the IPv6 addresses (the order within
IPv4 and IPv6 groups remains)
Example: IPv4(host1), IPv4(host2), IPv6(host1), IPv6(host2).

With “prefer-ipv6” mode, the order is the opposite - the IPv6 addresses are placed before the IPv4
addresses
Example: IPv6(host1), IPv6(host2), IPv4(host1), IPv4(host2).

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 47

 Tag Default if Supported Description
Omitted Values
%SIP_TRANSPORTS_EN dns ipv4 Controls the order of IPv4/IPv6
FORCE_IP_VERSION_WX ipv6 addresses used by the Webex client to
T% connect the SIP session.
dns
prefer-ipv4
prefer-ipv6

6.1.8.4 DNS TTL Management

A separate configuration parameter has been added for managing the way DNS resolving is
redone when the TTL of the DNS record of the currently used server expires. The parameter in
the following table, when enabled, forces the client to redo DNS operations once the TTL of the
DNS SRV or A-record of the currently used server expires.
After the DNS resolving is redone, this parameter also forces the client to reconnect to the top
priority server received if it is different from the currently used server, even in the case when the
current connection is working fully. However, reconnection is only done after ongoing calls have
finished.
If the TTLs for servers A and SRV records are different, the smaller value is chosen.
When this parameter is disabled, DNS operations are not redone when TTL expires, but rather
every 15 minutes.
This parameter only works for SIP.
Note that the DNS TTL management feature cannot be used when an IP address is used in the
proxy address parameter.

NOTE: This is a desktop-only feature, since the mobile clients have SIP connection only while on a call.

<config>
<protocols><sip>
<refresh-on-ttl enabled="%SIP_REFRESH_ON_TTL_WXT%"
use-random-factor="%SIP_REFRESH_ON_TTL_USE_RANDOM_FACTOR_WXT%"/>

Tag Default if Supported Description

Omitted Values
%SIP_REFRESH_ON_T false false, true When set to “false”, DNS TTL management
TL_WXT% is disabled for SIP.
When set to “true”, DNS TTL management is
enabled for SIP.
%SIP_REFRESH_ON_T false false, true If enabled, adds а random period between
TL_USE_RANDOM_FAC 0-10% to the DNS TTL.
TOR_WXT%"

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 48

 NOTE: It is highly recommended to enable the DNS TTL random factor to prevent spikes of requests to
the DNS and potentially spikes of reconnection attempts to the Application Server.

6.1.9 SIP SUBCSRIBE and REGISTER Refresh and SUBSCRIBE Retry

Communicator supports configuring the refresh intervals for SIP SUBSCRIBE and REGISTER.
For SIP SUBSCRIBE, there is a separate parameter for the refresh interval (in seconds) and how
long the client waits before it retries SIP SUBSCRIBE if there are errors (in seconds). The
recommended maximum value for the subscription-retry-interval is 2000000 seconds while any
negative, 0, or empty value results in 1800 seconds being used. Any negative value in for
subscribe refresh leaves out the Expires header and thus creates a one-off SUBSCRIBE.
The SIP REGISTER refresh timer proposed by the client can be configured in seconds, but
according to SIP specifications, the server can override the value. Currently, the client
remembers the value proposed by the server for subsequent refreshes instead of always using
the configured value.
Finally, the expires-value for SIP sessions (for SIP INVITE and SUBSCRIBE) can also be
configured (in seconds).
<config>
<protocols><sip>
<subscription-refresh-interval>10800</subscription-refresh-interval>
<subscription-retry-interval>60</subscription-retry-interval>
<registration-refresh-interval>300</registration-refresh-interval>
<session>
<expires-value>3600</expires-value>
</session>

6.1.10 Use P-Associated-URIs in REGISTER

The following parameter is used when registering and handling the related 200 OK response.
If the parameter is set to “false”, then the client does not use the P-Associated-URI and uses the
identity from its own SIP URI instead.
<config>
<protocols><sip>
<use-alternative-identities>%USE_ALTERNATIVE_IDENTITIES_WXT%</use-alternative-
identities>

If the parameter is set to “true”, then the client takes its own identity from the last
P-Associated-URI header for all outgoing SIP requests (INVITE, SUBSCRIBE, CANCEL, INFO,
and REFER) from the 200 OK response in the REGISTER. In addition, these URIs are not shown
as contacts in the contact list.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 49

 Tag Default if Supported Description
Omitted Values
%USE_ALTERNATIVE false true, false Enables use of alternative identities in SIP
_IDENTITIES_WXT% REGISTER.
If set to “true”, then the client takes its own
identity from the last P-Associated-URI header
for outgoing SIP requests.
If set to “false”, then its own identity for outgoing
SIP requests is taken from its own SIP URI.

6.1.11 SIP P-Early Media (PEM) Header

The SIP P-Early Media (PEM) header can be used in, for example, IMS environments inside a
trust domain to allow the network to authorize multiple SIP early media dialogs for instance in
cases where another network allows all early media.
The configuration parameter enables advertising PEM support in SIP signaling. The actual early
media handling logic is the same for both PEM and non-PEM cases, acting on supported PEM
header values.
<config>
<protocols><sip>
<support-p-early-media>%ENABLE_PEM_SUPPORT_WXT%</support-p-early-media>

Tag Default if Supported Description

Omitted Values
%ENABLE_PEM_SUP false true, false Set to “true” to enable client advertising PEM
PORT_WXT% support in SIP signaling.
Set to “false” to disable client advertising PEM
support in SIP signaling.

6.1.12 SIP UPDATE Support

SIP UPDATE is needed in, for example, some IMS deployments, instead of the alternative re-
INVITE. It allows a client to update parameters of a session such as the set of media streams and
their codecs but has no impact on the state of a SIP dialog.
Typical use cases are related to early media when, for example, using ringback tone and pre-alert
simultaneously.
SIP UPDATE is currently only supported when received in pre-dialog use cases (early media)
and not during active dialog, for example, for call hold/resume where re-INVITE is still used.
It is not possible to add video to audio using SIP UPDATE (media change) in this release.
Additionally, the client does not support full IMS long call flow with resource reservation.
<config>
<protocols><sip>
<support-update enabled="%ENABLE_SIP_UPDATE_SUPPORT_WXT%"/>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 50

 Tag Default if Supported Description
Omitted Values
%ENABLE_SIP_UPDATE false true, false When set to “false”, SIP UPDATE support is
_SUPPORT_WXT% disabled.
When set to “true”, SIP UPDATE support is
enabled.

6.1.13 Legacy SIP INFO FIR

This client supports the legacy way of requesting video keyframes via SIP INFO media control
request. That is needed because some of the devices have problems responding to RTCP-FB
FIR and occasionally RTCP does not get thru to remote endpoint, which may lead to no-video or
one-way-video. For more information, see RFC 5168.
<config>
<protocols><sip>
<force-sip-info-fir enabled="%ENABLE_FORCE_SIP_INFO_FIR_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_FORCE_SIP_INF false true, false When set to “false”, SIP INFO FIR support
O_FIR_WXT% is disabled.
When set to “true”, SIP INFO FIR support is
enabled.

6.1.14 SIP rport Management for NAT Traversal

The client can be configured to use the SIP rport mechanism for NAT traversal. Note that,
typically, it cannot be the only solution for NAT traversal and SBC is mainly used for this purpose.
For a description of the rport specification, see RFC 3581.
For more information on SIP port and transport protocol recommendations when SIP Application
Layer Gateways (ALGs) are used in the network, see the Webex for Cisco BroadWorks Solution
Guide.
Note that the “rport” string is always present in outgoing SIP requests regardless of configuration.
The parameter only affects the usage of IP address and port received from the server in the SIP
“received” and “rport” headers. When the feature is enabled, the values from “received” and
“rport” headers are used in the SIP Contact header of SIP requests (even when the “received”-
header is missing in REGISTER response).
The Preferred-port parameter is related in that it otherwise defines the port used in the SIP
Contact header. For more information on SIP port allocation, see section 6.1.7 Preferred-Port
Usage for SIP.
There is a separate configuration parameter use-local-port that forces local port of the client
socket to be set in the Contact header. This is used for some SBCs that detect the client has a
real IP (from the Contact header) and the SBC tries to establish a separate socket to the client for
its requests. In most cases, a firewall sits between the SBC and the client, and it denies the
incoming connections to the client.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 51

 NOTE: In IPv6 environments, all the addresses are real, and the SBC tries to establish a connection
to the listening client address (from the Contact header).

<config>
<protocols><sip>
<use-rport enabled="%ENABLE_USE_RPORT_WXT%" use-local-
port="%RPORT_USE_LOCAL_PORT_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_USE_RPORT false true, false Enables rport for audio and video calls.
_WXT%

%RPORT_USE_LOCAL_ false true, false Controls whether the local port of the
PORT_WXT% client’s socket is to be added in the SIP
Contact header.

6.1.15 SIP Session ID

When enabled, on initial registration, a local Session ID is generated. The Session ID is used for
the lifetime of the connection/session for that device, for all out of call dialogs, REGISTER,
SUBSCRIBE, NOTIFY, and so on. Same Session ID is used until the binding is lost. When the
registration binding is lost (DNS lookup, connection reset, phone reset, and so on), a new local
Session ID is generated.
The value of the Session ID can be used to find the full set of dialogs associated with that device.
<config>
<protocols><sip>
<sip-sessionid enabled="%ENABLE_SIP_SESSION_ID_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_SIP_SESSIO false true, false Controls usage of the SIP session ID.
N_ID_WXT%

6.1.16 Incoming Call Rejection Behavior

The client offers the flexibility to reject a call with 486 or 603.
Note that if the client is configured to reject a call with 603 Decline, then the Call Forward Busy
and Call Forward No Answer services may not work as expected.
<config>
<services><calls>
<reject-with-486 enabled="%ENABLE_REJECT_WITH_486_WXT%"/>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 52

 Tag Default if Supported Description
Omitted Values
%ENABLE_REJECT_WITH_4 true true, false Controls the SIP error code and reason
86_WXT% used to reject incoming SIP calls. If
enabled, 486 Temporarily Unavailable is
used. Otherwise, 603 Decline is used.

6.1.17 Real-Time Transport Protocol Port Range

The client can be configured to use a defined port range for Real-Time Transport Protocol (RTP)
streams, which also applies for SRTP. This configuration is done by setting the port range limit
values for both audio and video streams with the tags shown in the following example.
<config>
<protocols><rtp>
<preferred-audio-port-start>%RTP_AUDIO_PORT_RANGE_START_WXT%</preferred-audio-port-
start>
<preferred-audio-port-end>%RTP_AUDIO_PORT_RANGE_END_WXT%</preferred-audio-port-end>
<preferred-video-port-start>%RTP_VIDEO_PORT_RANGE_START_WXT%</preferred-video-port-
start>
<preferred-video-port-end>%RTP_VIDEO_PORT_RANGE_END_WXT%</preferred-video-port-end>

Tag Default if Supported Description

Omitted Values
%RTP_AUDIO_PORT_RAN 8000 number Start of the audio port range.
GE_START_WXT%
%RTP_AUDIO_PORT_RAN 8099 number End of the audio port range.
GE_END_WXT%
%RTP_VIDEO_PORT_RAN 8100 number Start of the video port range.
GE_START_WXT%
%RTP_VIDEO_PORT_RAN 8199 number End of the video port range.
GE_END_WXT%

NOTE: Port ranges should be set so that they never overlap.

6.1.18 ICE Support (Webex Calling only)

The client supports Interactive Connectivity Establishment (ICE) negotiation that enables media
path optimization between endpoints (in a peer-to-peer manner). This is done to reduce data
latency, decrease packet loss, and reduce the operational costs of deploying the application.
Note that the current implementation supports STUN server, while TURN is not supported.
When ICE support is enabled, re-keying for SRTP will always be performed (see section 6.1.2
SIP Over TLS and Secure Real-time Transport Protocol).
<config>
<protocols><rtp>
<ice enabled=”%ENABLE_RTP_ICE_WXT%” mode=”%RTP_ICE_MODE_WXT%”
service-uri=”%RTP_ICE_SERVICE_URI_WXT%” port=”%RTP_ICE_PORT_WXT%”/>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 53

 Tag Default if Supported Description
Omitted Values
%ENABLE_RTP_ICE_WXT false true, false Enable / Disable ICE support.
%
%RTP_ICE_MODE_WXT% icestun icestun ICE support mode. Currently the only
supported value is “icestun”.
%RTP_ICE_SERVICE_URI (empty) valid STUN STUN server URI.
_WXT% server URI
or (empty)
%RTP_ICE_PORT_WXT% 3478 Number (0- STUN server port.
65535)

6.1.19 RTCP MUX

RTCP MUX is configurable. This feature makes the client use the same port for RTP and RTCP.
In SIP/SDP signaling level, the line a=rtcp-mux is added to the SDP. In addition, different modes
are possible:
▪ Backward-compatibility mode (that is, line a=rtcp-mux does not appear in SDP)
▪ Multiplexing mode (the a=rtcp-mux line will appear twice in the SDP: once in the m=audio
section, and a second time in the m=video section)
Video and audio do not use the same port.
<config>
<protocols><rtp>
<mux enabled=”%ENABLE_RTCP_MUX_WXT%”/>

Note that RTCP MUX cannot be used with SRTP calls.

Tag Default if Supported Description
Omitted Values
%ENABLE_RTCP_MU true true, false To enable RTPC MUX, set to “true”.
X_WXT% To disable RTCP MUX, set to “false”.

6.1.20 Transfer Call

The Webex for Cisco BroadWorks client supports attended (consultative), semi-consultative, and
Direct (blind) call transfer.
Semi-consultative call transfer allows the caller to complete the transfer before the call is picked
up by the remote callee. The semi-consultative completion button is enabled for the caller only
after the ringing is started on the callee side and the corresponding SIP notification (180 Ringing)
is received on the caller side. Blind transfer is called “Transfer Now” in the UI.

NOTE: The SIP 180 Ringing may not be triggered in some environments, for some numbers, or in some
cross-server communication scenarios.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 54

 <config>
<services>
<calls>
<transfer-call enabled=”%ENABLE_TRANSFER_CALLS_WXT%” xsi-
enabled=”%ENABLE_XSI_TRANSFER_CALLS_WXT%” type=”%TRANSFER_CALL_TYPE_WXT%”/>

Tag Default if Supported Description

Omitted Values
%ENABLE_TRANSFE false true, false When set to “true”, call transfer is enabled.
R_CALLS_WXT%
When set to “false”, call transfer is disabled.
%ENABLE_XSI_TRAN false true, false Enables transfer option(s) for the XSI calls.
SFER_CALLS_WXT%
%TRANSFER_CALL_T full talk-first, Specifies the transfer types available for the
YPE_WXT% blind, full user in the BroadWorks config.

6.1.21 N-Way Conference Calls and Participants

The following custom tag can be used to control the availability of the Ad Hoc (N-Way)
conference call through SIP in the Webex for Cisco BroadWorks client. In addition, the N-way
owner can see the full list of participants via SIP SUBSCRIBE/NOTIFY and conference event
package. The owner’s client learns the URI to send the SIP SUBSCRIBE to via preceding SIP
Contact header of the 200 OK message sent in response to the INVITE to the conference URI
while for participants the same information is in a preceding call-info NOTIFY.
The Cisco BroadWorks system setting (maxConferenceParties) is used to set the maximum
number of conference parties. For a given call, it indicates the number of active simultaneous
parties a user can have or add through the “Add participants” mid-call control option or through
the Cisco BroadWorks N-way Calling feature.
This information is retrieved from the Application Server (AS) using the following command line
interface (CLI) command.
AS_CLI/SubscriberMgmt/Policy/CallProcessing/Conferencing> get

Example output:
maxConferenceParties = 6
conferenceURI =

Once the value for the maxConferenceParties is obtained, (which has a range of 4 through 15),
the %MAX_CONF_PARTIES_WXT% tag should be set accordingly.
<config>
<services><calls>
<conference enabled=”%ENABLE_CONFERENCE_CALLS_WXT%”>
<service-uri>sip:%BWNETWORK-CONFERENCE-SIPURI-1%</service-uri>
<subscribe-conference-info enabled=”%ENABLE_NWAY_PARTICIPANT_LIST_WXT%”/>
<max-nway-participants>%MAX_CONF_PARTIES_WXT%</max-nway-participants>
</conference>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 55

 Tag Default if Supported Description
Omitted Values

%ENABLE_CONFERENC false true, false Controls if the Conference option should be

E_CALLS_WXT% enabled for the user.
%ENABLE_NWAY_PART false true, false Set to “true” to enable N-way owner participant
ICIPANT_LIST_WXT% list.
Set to “false” to disable N-way owner
participant list.
%MAX_CONF_PARTIES 10 Number Specifies the maximum N-way participant
_WXT% between 4 number, enforced by the client, for example,
and 15 10. Server side has its own limits.
(empty) Empty value disables client-side enforcing of
N-way participant limit.

6.1.22 Call Pull

The Call Pull feature can be enabled using a single configuration parameter, as shown in the
following example.
<config>
<services><calls>
<call-pull enabled=”%ENABLE_CALL_PULL_WXT%”/>

Tag Default if Supported Description

Omitted Values
%ENABLE_CALL_PULL_WX false true, false Enables Call Pull.
T%

6.1.23 Call Park/Retrieve

The Group Call Park feature allows ongoing VoIP calls to be transferred to a Call Park server,
which allows the caller to do something else and to be retrieved by the same user or another
user. An ongoing call will be parked against the first available extension within the Call Park
Group.
Call retrieval can be performed by the user parking the call in the dialog for a configurable
number of seconds immediately after parking the call. Or the parked call can be retrieved by the
user or another user by selecting the call retrieval option and entering the number or extension.
<config>
<services><calls>
<call-park enabled=”%ENABLE_CALL_PARK_WXT%”
timer=”%CALL_PARK_AUTO_CLOSE_DIALOG_TIMER_WXT%”/>

Tag Default if Supported Description

Omitted Values
%ENABLE_CALL_PARK_ false true, false Enables Call Park/Retrieve.
WXT%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 56

 Tag Default if Supported Description
Omitted Values
%CALL_PARK_AUTO_CLOS 10 Number Specifies the number of seconds the
E_DIALOG_TIMER_WXT% between 5 successful Call Parked dialog is visible
and 30 for the user before being closed
automatically.

6.1.24 Call Statistics

Reporting End-of-Call Statistics in Session Initiation Protocol (SIP) BYE message enables
sending call statistics to a remote end when a call terminates. The call statistics are sent as a
new header in the SIP BYE message or in the corresponding 200 OK response to the BYE
message. The statistics include Real-time Transport Protocol (RTP) packets sent or received,
total bytes sent or received, total number of packets that are lost, delay jitter, round-trip delay,
and call duration.
<config>
<services><calls>
<call-statistics enabled=”%ENABLE_CALL_STATISTICS_WXT%”/>

Tag Default if Supported Description

Omitted Values
%ENABLE_CALL_STATISTIC false true, false Set to “true” to enable capturing of calling
S_WXT% metrics.
Set to “false” to disable capturing of
calling metrics.

6.1.25 Call Auto Recovery / Seamless Call Handover

The client has support for call auto recovery at switching networks while the user has an ongoing
VoIP call. Call auto recovery works in both directions – Cellular Data-to-WiFi and WiFi-to-Cellular
Data, as well as while switching between WiFi networks. The call is tried to be recovered within a
one-minute timeframe and then stops. If there are more than one ongoing VoIP calls, just the
active one is recovered.
In Cellular Data-to-WiFi transition, the client will keep the ongoing VoIP calls on cellular data until
terminated or cellular data network is lost.
<config>
<services><calls>
<auto-recovery enabled=”%ENABLE_CALLS_AUTO_RECOVERY_WXT%”/>

Tag Default if Supported Description

Omitted Values
%ENABLE_CALLS_AUTO false true, false Controls if the auto recovery mechanism
_RECOVERY_WXT% should be enabled for the user.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 57

 6.1.26 Call Recording
The Call Recording feature is supported by the client and depends on server-side availability of
the feature, as well as configuration option. The feature depends on enabled XSI event channel
(see section 6.1.33 XSI Event Channel) and Application Server (AS) configured to send X-
BroadWorks-Correlation-Info SIP header (see the Webex for Cisco BroadWorks Solution Guide).
If the feature is disabled, there are no recording buttons and options for the user. Note that call
recording operates on a per user, not per call basis – that means that if one of the participants on
a call supports call recording, then the call can be recorded.
If the call recording feature is enabled, there is always a visual indication when the call is being
recorded. The following call recording modes are supported by Cisco BroadWorks:
Always
▪ Call recording will be started automatically at call establishment.
▪ User is NOT able to stop/pause the call recording.
Always with Pause/Resume Support
▪ Call recording will be started automatically at call establishment but the user will be able to
pause and resume the call.
▪ Possible user interactions:
- Recording is in progress – Pause Recording action.
- Recording is on pause – Resume Recording action.
On Demand
▪ After the call is established, call recording starts on the server.
▪ If the user presses the Start Recording option during the call, the call recording will be stored
and it will keep the call from its startup. Otherwise, if no start recording is initiated from the
user, the call recording will be deleted on the server.
▪ Possible user interactions:
- No recording has started yet – Start Recording action.
- Recording is in progress – Pause Recording action.
- Recording is on pause – Resume Recording action.
On Demand with User Initiated Start
▪ User can start, stop, pause, and resume call recording at any time, several times during a
call.
▪ There will be separate call recordings for each call recording startup.
▪ Possible user interactions:
- No recording has started yet – Start Recording action.
- Recording is in progress – Stop and Pause Recording action.
- Recording is on pause – Stop and Resume Recording action.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 58

The call recording mode assigned to the user can be selected from the Control Hub.
<config>
<services><calls>
<record enabled=”%ENABLE_CALL_RECORDING_WXT%”/>

Tag Default if Supported Description

Omitted Values
%ENABLE_CALL_RECOR false true, false Enables Call Recording controls.
DING_WXT%

6.1.27 Voicemail, Visual Voicemail, Message Waiting Indicator

The following custom tags can be used to control the availability of the Cisco BroadWorks
Voicemail and Visual Voicemail in the Webex for Cisco BroadWorks client. Note that a Cisco
BroadWorks system tag (%BWVOICE-PORTAL-NUMBER-1%) is used with voicemail.
Visual Voicemail (VVM) is supported for audio only. Supported formats are wav, ulaw, and mov
containing H264 video (played as audio only). It allows users to view incoming voicemails in a list
view and individual items can be played. This feature is based on Xsi, but notifications of new
voicemail are provided over SIP; therefore, SIP must be enabled for the notifications to work. In
addition, SIP SUBSCRIBE for Message Waiting Indicator (MWI) configuration is needed for the
notifications to arrive and MWI must be enabled for Visual Voicemail to work. For more
information on SIP configuration, see section 6.1.1 Common Features
Change Basic SIP Server Settings.
For Cisco BroadWorks release and patch requirements for Visual Voicemail, see the
Webex for Cisco BroadWorks Solution Guide.
Visual Voicemail must be separately enabled in the configuration.
The following settings are needed on the CommPilot portal to have Visual Voicemail:
▪ Voice messaging enabled
▪ “When message arrives, use unified messaging” option enabled
▪ “Use Phone Message Waiting Indicator” option enabled
Not having the Visual Voicemail service assigned on the Cisco BroadWorks side for the user
automatically disables the configuration for the service.
Note that disabling SIP registration also disables MWI for new voicemails. See the table that
follows for more information on enabling MWI.
To show voicemail message information in the UI, the client needs to receive SIP MWI
notifications from the server (that is, the voicemail event package). See the table that follows for
subscription options. Note also that MWI is needed for Visual Voicemail notifications to work.
Note that if SIP subscription to voicemail event package fails, the client keeps retrying when
configured to do so. For more information on SIP SUBSCRIBE retry configuration, see section
6.1.9 SIP SUBCSRIBE and REGISTER Refresh and SUBSCRIBE Retry.
<config>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 59

<services><calls>
<mwi enabled=”%ENABLE_MWI_WXT%” type=”%MWI_MODE_WXT%”/>
<voice-mail enabled=”%ENABLE_VOICE_MAIL_WXT%” visual-
voicemail=”%ENABLE_VISUAL_VOICE_MAIL_WXT%”>
<center-number>%BWVOICE-PORTAL-NUMBER-1%</center-number>
</voice-mail>

Tag Default if Supported Description

Omitted Values
%ENABLE_VOICE_MAI false true, false Set to “true” to enable Voicemail support.
L_WXT% Set to “false” to disable Voicemail support.
%ENABLE_VISUAL_VO false true, false When set to “false”, VVM is disabled.
ICE_MAIL_WXT% When set to “true”, VVM is enabled.
Note that voice-mail enabled=false before
the actual VVM attribute is still used for
backward compatibility.
%BWVOICE-PORTAL- empty number The client calls this number typically
NUMBER-1% specified using an existing Cisco
BroadWorks system tag when dialing
voicemail.
%ENABLE_MWI_WXT false true, false Set to “true” to enable MWI.
% Set to “false” to disable MWI.
%MWI_MODE_WXT% empty implicit, Set to “explicit” to send SIP SUBSCRIBE for
explicit MWI event package when MWI is enabled.
Using “implicit” does not send a SIP
SUBSCRIBE for MWI event package when
MWI is enabled.
If left empty, MWI is disabled.

6.1.28 Voicemail Transcription for Webex Calling

With this feature, voicemail messages are converted to text and displayed in the visual voicemail
message view in the Webex Calling desktop and mobile apps.
The feature should be enabled for a user only if:
1. The app is running in Webex Calling deployment.
2. The Visual Voicemail feature is enabled for the user.
3. The feature is enabled in the config (the enabled attribute in the <services><voice-
mail><transcription> tag should be set to “true”).
Tag Default if Supported Description
Omitted Values
%ENABLE_VOICE_MAIL_TR false true, false [Webex Calling Only] Controls the
ANSCRIPTION_WXT% availability of voicemail transcription only
if Visual Voicemail is enabled.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 60

 6.1.29 Call Settings

6.1.29.1 Call Forwarding Always

The following custom tag can be used to control the availability of the Cisco BroadWorks Call
Forwarding Always service in the Webex for Cisco BroadWorks client.
<config>
<services><supplementary-services>
<call-forwarding-always enabled=”%ENABLE_CALL_FORWARDING_ALWAYS_WXT%”/>

Tag Default if Supported Description

Omitted Values
%ENABLE_CALL_FORWAR false true, false Set to “true” to enable the Call
DING_ALWAYS_WXT% Forwarding Always service.
Set to “false” to disable the Call
Forwarding Always service.

6.1.29.2 BroadWorks Anywhere (Single Number Reach)

The following custom tags control the availability of the BroadWorks Anywhere and the availability
of its settings in the Webex for Cisco BroadWorks client. Note that the name of this feature inside
the client is Single Number Reach.
<config>
<services><supplementary-services>
<broadworks-anywhere enabled=”%ENABLE_BROADWORKS_ANYWHERE_WXT%”>
<description enabled=”%ENABLE_BROADWORKS_ANYWHERE_DESCRIPTION_WXT%”/>
<alert-all-locations
enabled=”%ENABLE_BROADWORKS_ANYWHERE_ALERT_ALL_LOCATIONS_WXT%”
default=”%BROADWORKS_ANYWHERE_ALERT_ALL_LOCATIONS_DEFAULT_WXT%”/>
<call-control enabled=”%ENABLE_BROADWORKS_ANYWHERE_CALL_CONTROL_WXT%”
default=”%BROADWORKS_ANYWHERE_CALL_CONTROL_DEFAULT_WXT%”/>
<diversion-inhibitor
enabled=”%ENABLE_BROADWORKS_ANYWHERE_DIVERSION_INHIBITOR_WXT%”
default=”%BROADWORKS_ANYWHERE_DIVERSION_INHIBITOR_DEFAULT_WXT%”/>
<answer-confirmation
enabled=”%ENABLE_BROADWORKS_ANYWHERE_ANSWER_CONFIRMATION_WXT%”
default=”%BROADWORKS_ANYWHERE_ANSWER_CONFIRMATION_DEFAULT_WXT%”/>
</broadworks-anywhere>

Tag Default if Supported Description

Omitted Values
%ENABLE_BROADWORKS_ false true, false Enables BroadWorks Anywhere (BWA) on
ANYWHERE_WXT% configuration level.
%ENABLE_BROADWORKS_ true true, false Controls if the Description of the BWA
ANYWHERE_DESCRIPTION location should be available for the user.
_WXT%
%ENABLE_BROADWORKS_ false true, false Set to “true” to make Alert All Locations for
ANYWHERE_ALERT_ALL_L the BWA service available for the user.
OCATIONS_WXT% Set to “false” to make Alert All Locations
for the BWA service unavailable for the
user.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 61

 Tag Default if Supported Description
Omitted Values
%BROADWORKS_ANYWHE false true, false Controls if the application should enable
RE_ALERT_ALL_LOCATION the Alert All Locations state, at adding
S_DEFAULT_WXT% second or every subsequent new BWA
location.
%ENABLE_BROADWORKS_ false true, false Controls if the Call Control of the BWA
ANYWHERE_CALL_CONTR location should be available for the user.
OL_WXT%
%BROADWORKS_ANYWHE false true, false Controls the default state of the Call
RE_CALL_CONTROL_DEFA Control for the BWA location.
ULT_WXT%
%ENABLE_BROADWORKS_ false true, false Controls if the Diversion Inhibitor of the
ANYWHERE_DIVERSION_I BWA location should be available for the
NHIBITOR_WXT% user.
%BROADWORKS_ANYWHE false true, false Controls the default state of the Diversion
RE_DIVERSION_INHIBITOR Inhibitor of the BWA location.
_DEFAULT_WXT%
%ENABLE_BROADWORKS_ false true, false Controls if the Answer Confirmation of the
ANYWHERE_ANSWER_CO BWA location should be available for the
NFIRMATION_WXT% user.
%BROADWORKS_ANYWHE false true, false Controls the default state of the Answer
RE_ANSWER_CONFIRMATI Confirmation of the BWA location.
ON_DEFAULT_WXT%

6.1.30 Settings Portal and Web-based Call Settings

The Webex for Cisco BroadWorks client provides access to a settings (Self Care) portal, where
the user can configure some of the application and service settings.
Furthermore, the client provides the option to use the Call Settings Web View (CSWV) instead.
That allows the user to control more of the server-based call settings. Separate tags can be used
to control whether specific services should be visible in the web-based call settings.

NOTE: It is advisable to hide the settings that are already visible in the application like Call Center (see
section 6.1.31 Call Center / Call Queue Login/Logout) and BroadWorks Anywhere (see section 6.1.29.2
BroadWorks Anywhere). The Remote Office service is also advisable to be hidden because it has been
succeeded by the BroadWorks Anywhere service.

The following custom tag can be used to configure the URL for the settings (Self Care or CSWV)
portal. If the tag is empty, the link to the settings portal is not visible for the user in the application.
<config>
<services>
<web-call-settings target=”%WEB_CALL_SETTINGS_TARGET_WXT%”
<url>%WEB_CALL_SETTINGS_URL_WXT%</url>
<branding-enabled=”%WEB_CALL_SETTINGS_BRANDING_ENABLED_WXT%”>
<service-settings>
<service name=”Call Forwarding Always”
visible=”%WEB_CALL_SETTINGS_CFA_VISIBLE_WXT%”/>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 62

 <service name=”Call Forwarding Busy”
visible=”%WEB_CALL_SETTINGS_CFB_VISIBLE_WXT%”/>
<service name=”Call Forwarding Not Reachable”
visible=”%WEB_CALL_SETTINGS_CFNR_VISIBLE_WXT%”/>
<service name=”Call Forwarding No Answer”
visible=”%WEB_CALL_SETTINGS_CFNA_VISIBLE_WXT%”/>
<service name=”Do Not Disturb” visible=”%WEB_CALL_SETTINGS_DND_VISIBLE_WXT%”/>
<service name=”Anonymous Call Rejection”
visible=”%WEB_CALL_SETTINGS_ACR_VISIBLE_WXT%”/>
<service name=”Simultaneous Ring Personal”
visible=”%WEB_CALL_SETTINGS_SIMRING_VISIBLE_WXT%”/>
<service name=”Sequential Ring”
visible=”%WEB_CALL_SETTINGS_SEQRING_VISIBLE_WXT%”/>
<service name=”Automatic Callback”
visible=”%WEB_CALL_SETTINGS_ACB_VISIBLE_WXT%”/>
<service name=”Call Waiting” visible=”%WEB_CALL_SETTINGS_CW_VISIBLE_WXT%”/>
<service name=”Calling Line ID Delivery Blocking”
visible=”%WEB_CALL_SETTINGS_CLIDB_VISIBLE_WXT%”/>
<service name=”Personal Assistant”
visible=”%WEB_CALL_SETTINGS_PA_VISIBLE_WXT%”/>
<service name=”Call Center – Standard”
visible=”%WEB_CALL_SETTINGS_CC_VISIBLE_WXT%”/>
<service name=”BroadWorks Anywhere”
visible=”%WEB_CALL_SETTINGS_BWA_VISIBLE_WXT%”/>
<service name=”BroadWorks Mobility”
visible=”%WEB_CALL_SETTINGS_BWM_VISIBLE_WXT%”/>
<service name=”Remote Office” visible=”%WEB_CALL_SETTINGS_RO_VISIBLE_WXT%”/>
<service name=”Voice Messaging User”
visible=”%WEB_CALL_SETTINGS_VM_VISIBLE_WXT%”/>
</service-settings>
<userportal-settings> <url>%USER_PORTAL_SETTINGS_URL_WXT%</url></userportal-
settings>
</web-call-settings>

Tag Default if Supported Description

Omitted Values
%WEB_CALL_SETTINGS_ external external, Controls the admin portal mode.
TARGET_WXT% csw Set to “external” to open configured
setting portal URL in an external browser.
Set to “csw” to open the CSW portal in an
embedded browser using the extra
parameters section <services><web-call-
settings> to form the POST request.
%WEB_CALL_SETTINGS_ empty URL string URL for the settings portal.
URL_WXT% Example: https://settings.webex.com
%WEB_CALL_SETTINGS_CF true true, false Controls whether the Call Forwarding
A_VISIBLE_WXT% Always option should be visible for the
user in the web-based settings.
%WEB_CALL_SETTINGS_DN true true, false Controls whether the Do Not Disturb
D_VISIBLE_WXT% (DND) option should be visible for the user
in the web-based settings.
%WEB_CALL_SETTINGS_AC true true, false Controls whether the Anonymous Call
R_VISIBLE_WXT% Rejection (ACR) option should be visible
for the user in the web-based settings.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 63

Tag Default if Supported Description
Omitted Values
%WEB_CALL_SETTINGS_CF true true, false Controls whether the Call Forwarding
B_VISIBLE_WXT% Busy (CFB) option should be visible for
the user in the web-based settings.
%WEB_CALL_SETTINGS_CF true true, false Controls whether the Call Forwarding Not
NR_VISIBLE_WXT% Reachable (CFNR) option should be
visible for the user in the web-based
settings.
%WEB_CALL_SETTINGS_CF true true, false Controls whether the Call Forwarding No
NA_VISIBLE_WXT% Answer (CFNA) option should be visible
for the user in the web-based settings.
%WEB_CALL_SETTINGS_ true true, false Controls whether the Simultaneous Ring
SIMRING_VISIBLE_WXT% Personal (SIMRING) option should be
visible for the user in the web-based
settings.
%WEB_CALL_SETTINGS_ true true, false Controls whether the Sequential Ring
SEQRING_VISIBLE_WXT% (SEQRING) option should be visible for
the user in the web-based settings.
%WEB_CALL_SETTINGS_RO true true, false Controls whether the Remote Office (RO)
_VISIBLE_WXT% option should be visible for the user in the
web-based settings.
%WEB_CALL_SETTINGS_ true true, false Controls whether the Automatic Callback
ACB_VISIBLE_WXT% (ACB) option should be visible for the user
in the web-based settings.
%WEB_CALL_SETTINGS_ true true, false Controls whether the Call Waiting (CW)
CW_VISIBLE_WXT% option should be visible for the user in the
web-based settings.
%WEB_CALL_SETTINGS_ true true, false Controls whether the Calling Line ID
CLIDB_VISIBLE_WXT% Delivery Blocking (CLIDB) option should
be visible for the user in the web-based
settings.
%WEB_CALL_SETTINGS_PA true true, false Controls whether the Personal Assistant
_ (PA) option should be visible for the user
VISIBLE_WXT% in the web-based settings.
%WEB_CALL_SETTINGS_B true true, false Controls whether the BroadWorks
WA_VISIBLE_WXT% Anywhere (BWA) option should be visible
for the user in the web-based settings.
%WEB_CALL_SETTINGS_CC true true, false Controls whether the Call Center option
_ should be visible for the user in the web-
VISIBLE_WXT% based settings.
%WEB_CALL_SETTINGS_ true true, false Controls whether the BroadWorks Mobility
BWM_VISIBLE_WXT% (BWM) option should be visible for the
user in the web-based settings.
Currently the recommended value is
“false” due to interoperability issues
between Webex for Cisco BroadWorks
and BroadWorks Mobility.
%WEB_CALL_SETTINGS_VM true true, false Controls whether the Voice Management
_VISIBLE_WXT% (VM) option should be visible for the user
in the web-based settings.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 64

 Tag Default if Supported Description
Omitted Values
%WEB_CALL_SETTINGS_BR false true, false Controls whether to use the new Call
ANDING_ENABLED_WXT% Settings WebView branding. Enable if the
server-side CSWV version is 1.8.6 or
above. Otherwise, keep it false.
%WEB_CALL_SETTINGS_EM true true, false Controls whether email/voicemail
AIL_VM_VISIBLE_WXT% messages options are visible in the web-
based settings.
%USER_PORTAL_SETTINGS empty URL string Specifies the URL to the user settings
_URL_WXT% portal. To enable the feature and present
the Access User Portal button in the UI,
this custom tag should be not be empty.
For example: https://settings.webex.com.
%USER_PORTAL_SETTINGS external external, Specifies if the URL should be opened in
_TARGET_WXT% internal an embedded or external browser.
%USER_PORTAL_SETTINGS false true, false Applicable only when embedded browser is
_SSO_ENABLED_WXT% configured
(USER_PORTAL_SETTINGS_TARGET_
WXT=internal). When enabled, HTTP
POST request is used, and BroadWorks
short-lived token is added as part of the
BODY. When disabled, the URL is opened
with HTTP GET.

NOTE 1: The Call Settings WebView URL should always have a trailing “/” configured. For example:
http(s)://<XSP-FQDN>/<CSW-Context-Path>/

NOTE 2: The Call Settings WebView application minimum version that is supported is 1.7.5.

For installation on Cisco BroadWorks Release 21.0, see the additional steps described in the Webex For
Cisco BroadWorks Solution Guide.

6.1.31 Call Center / Call Queue Login/Logout

The Webex app provides access to the Call Center (Call Queue) agent settings. If a user is
provisioned for Call Center, this feature enables the user to log into a call center and view the
available call queues, as well as join/unjoin queues and set the Automatic Call Distribution (ACD)
status.
Starting with Desktop Release 42.8 and Mobile Release 42.12, the Call Center (Call Queue)
agent is no longer based on the Call Settings Web View (see section 6.1.30 Settings Portal and
Web-based Call Settings). The Call Center (Call Queue) agent configuration is accessible
through footer of the Desktop and Settings of the Mobile Webex app.
<config>
<services>
<call-center-agent enabled=”%ENABLE_CALL_CENTER_WXT%”/>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 65

 Tag Default if Supported Description
Omitted Values
%ENABLE_CALL_CENTER_ false true, false Enables Call Center support.
WXT%

6.1.32 XSI Root and Paths

The Webex for Cisco BroadWorks client uses the following tags to control the XSI Root, Actions
and Events path if they need to be configured to differ from the ones used for sign-in.
The main reason to change the XSI Root is to implement load balancing at the configuration
level, although it is recommended to use load balancing at the HTTP layer instead.
The Events and Actions paths are typically changed due to branding requirements in order to
remove the com.broadsoft domain reference from the URL paths of the XSI HTTP requests
performed by the client.
<config>
<protocols><xsi>
<paths>
<root>%XSI_ROOT_WXT%</root>
<actions>%XSI_ACTIONS_PATH_WXT%</actions>
<events>%XSI_EVENTS_PATH_WXT%</events>
</paths>

Tag Default if Supported Description

Omitted Values
%XSI_ROOT_WXT% Continues to URL string The XSI root for all XSI operations.
use the Example: https://domain.com/
original one
used for
configuration
fetch.
%XSI_ACTIONS_PATH_ /com.broadso string Specifies the XSI Actions path.
WXT% ft.xsi-actions/ It should start and end with “/” and
contain only the actions context.
Example: /com.domain.xsi-actions/
%XSI_EVENTS_PATH_ /com.broadso string Specifies the XSI Events path.
WXT% ft.xsi-events/ It should start and end with “/” and
contain only the events context.
Example: /com.domain.xsi-events/

6.1.33 XSI Event Channel

The XSI Event channel is used for various services such as:
▪ XSI mid-call controls
▪ Call Settings status notifications
▪ Call Recording

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 66

XSI Events heartbeat is used to keep the XSI Event channel open and the heartbeat interval can
be specified using the following parameter.
<config>
<protocols><xsi>
<event-channel enabled=”%ENABLE_XSI_EVENT_CHANNEL_WXT%”>
<heartbeatInterval> %CHANNEL_HEARTBEAT_WXT%</heartbeatInterval>

Tag Default if Supported Description

Omitted Values
%ENABLE_XSI_EVENT_ true true, false Controls whether the XSI Event channel is
CHANNEL_WXT% enabled. It should be set to “true” to
receive, for example, mid-call control
service-related events.
The recommended value is “true”.
%CHANNEL_HEARTBEAT_ 10000 number This is the XSI Event channel heartbeat (in
WXT% milliseconds).
The default is “10000”.

6.1.34 Codec Configuration

Webex for Cisco BroadWorks offers a variety of audio and video codecs. The respective lists of
codecs are located under config/services/calls/ in the audio/codecs and video/codecs sections.
The priority of each codec can be changed via the XML-attribute priority, which is a value
between 0.0 (lowest) and 1.0 (highest).
<video><codecs>
<codec name=”H264” payload=”109” resolution=”CIF” framerate=”25”
bitrate=”768000” priority=”1.0”>
<packet-mode>0</packet-mode>
</codec>

The client supports H.264 as video codec. Video resolution attribute can be used to set one of the
following available values: SUBQCIF, QCIF, CIF, 4CIF, VGA, and HD.
If the bit rate is not entered in the configuration, the default bit rate values are used. Default bit
rate values, per resolution and frame rate, are listed in the following table.
Resolution Video Size * FPS Default Bit Rate Values per
(Frames Per Second) Resolution and FPS
SUBQCIF 128 x 96 15 128000
QCIF 176 x 144 30 192000
CIF 352 x 288 15 384000
CIF 352 x 288 30 768000
VGA 640 x 460 15 2000000
4CIF 704 x 576 25 2000000

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 67

 Resolution Video Size * FPS Default Bit Rate Values per
(Frames Per Second) Resolution and FPS
HD 960 x 720 30 2000000

* Maximum advertised video resolution. The actual video resolution during a call between two
Webex for Cisco BroadWorks clients depends on the capabilities of both clients – it will be the
lower of the two and will be the same on both clients.

Video resolution for a video call is negotiated during session setup and is based on the
capabilities of the two endpoints. Video call resolution is the same on both endpoints. That is, if
the Webex for Cisco BroadWorks endpoints have different capabilities (and therefore support
different resolutions), then the lower resolution is negotiated for the call. Video resolution may
change during a call if the network conditions deteriorate. In this case, the two mobile endpoints
may be using different video resolutions.
The packetization mode can be configured to be SingleNAL (0) or Non-interleaved (1). The
template uses SingleNAL by default (<packet-mode>0</packet-mode>).
Multiple telephone event configuration is also supported. During codec negotiation, the client
sends all the configured codecs, including multiple telephone events. After the audio codec is
selected, it searches for telephone events in the offer. If the offer has the telephone event with the
sample rate of the negotiated audio codec, then this telephone event is selected. Otherwise, the
first telephone event in the list is used. If there are no telephone events in the offer at all, in-band
dual-tone multi-frequencies (DTMFs) are used.
Example configured codecs:
<codec name=”telephone-event” payload=”100” in-band=”false” />
<codec name=”telephone-event” payload=”101” clockrate=”48000” in-band=”false” />

If an audio codec with sample rate of 48kbps is negotiated, the telephone event with payload 101
is used.
Webex for Cisco BroadWorks officially supports the following codecs:
▪ Audio
- OPUS
- G.722
- G.729
- PCMU (G.711U)
- PCMA (G.711A)
- iLBC
▪ Video
- H.264

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 68

 6.1.35 SIP-URI Dialing
Currently SIP-URI dialing through BroadWorks is not available and by default all SIP-URI calls
are routed through Locus, also known as “Free Calling”. In some environments, this is not
desirable and such calls should be blocked.

NOTE: This applies only if Locus calling is disabled. Only in this case will SIP URI dialing blocking work.

The following configuration provides this option.

<config>
<services>
<calls>
<sip-uri-dialing enable-locus-
calling="%SIP_URI_DIALING_ENABLE_LOCUS_CALLING_WXT%"/>

Tag Default if Supported Description

Omitted Values
%SIP_URI_DIALING_ENABL true true, false Controls whether the SIP-URI should be
E_LOCUS_CALLING_WXT% routed through Locus (true) or blocked
(false).

6.1.36 Call History Across All Devices

The client provides the ability to store and retrieve the call history from the server instead of
storing it locally. This way the call history is unified across all devices.

NOTE: Unified call history should be enabled at the same time on the client and server side in order to avoid
missing call history or duplicated records.

Tag Default if Supported Description

Omitted Values
%ENABLE_UNIFIED_CALL_ false true, false Controls if the application should use
HISTORY_WXT% Unified Call History or client-side (local)
one.

NOTE: If VOIP calling is disabled, the only meaningful value for emergency dial sequence
(%EMERGENCY_CALL_DIAL_SEQUENCE_WXT%) is cs-only.

6.1.37 Disable Video Calls

Release 41.9 added the ability to disable video calls. There are separate configuration options to
control this feature for BroadWorks-backed and Locus (free) VoIP calls.
When the feature is enabled and the feature tag is set to “false”:
▪ the user will not see the “Accept incoming calls with my video on” setting

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 69

▪ all incoming video calls if accepted, will be audio ones
▪ the user will not be able to escalate a call to video and video escalations will be automatically
rejected
When video calls are enabled, a new configuration property is added to control the default value
of the “Accept incoming calls with my video on” setting. By default, this feature is turned ON for
Desktop and turned OFF for Mobile and Tablet.
Tag Default if Supported Description
Omitted Values
%ENABLE_SIP_VIDEOCALL true true, false Controls the availability of SIP video calls
S_WXT% through BroadWorks.

%ENABLE_LOCUS_VIDEO true true, false Controls the availability of Locus (free)

CALLS_WXT% video calls.

%VIDEOCALLS_ANSWER_ Desktop - true, false Controls the default value of the “Accept
WITH_VIDEO_ON_DEFAULT true incoming calls with my video on” setting.
_WXT% Mobile /
Tablet -
false

6.1.38 Emergency (911) Calling - Location Reporting with E911 Provider

The Desktop and Tablet Webex client supports E911 location reporting using RedSky, Intrado, or
Bandwidth as an E911 emergency call provider for the Webex for BroadWorks deployment. The
E911 provider provides a per-device location support (for Webex desktop and tablets apps and
HELD-capable MPP devices) and a network that routes emergency calls to Public Safety
Answering Points (PSAPs) around the US, its territories (Guam, Puerto Rico, and Virgin Islands),
and Canada only. The service is enabled on a per-location basis.
Tag Default if Supported Description
Omitted Values

%EMERGENCY_DIALING_ false true, false Enables E911 provider Emergency

ENABLE_REDSKY_WXT% Location Platform.

%BWE911-PRIMARY- empty string Specifies the URL to the E911 provider

HELDURL% Emergency Location Platform supporting
the HELD protocol.

%BWE911-CUSTOMERID% empty string The customer ID (HeldOrgId, CompanyID)

used for the E911 provider HTTPS request.

%BWE911-SECRETKEY% empty string The secret to authenticate the E911

provider HTTPS request.

%BWE911-EMERGENCY- empty CSV string The list of emergency numbers supported

NUMBER-LIST% by E911 provider.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 70

 Tag Default if Supported Description
Omitted Values
%EMERGENCY_REDSKY_U 0 (user will number [0 - The timeout in minutes that will be used to
SER_REMINDER_TIMEOUT_ not be 43200] remind the user to update the emergency
WXT% prompted location if the current one is not entered or
again) is invalid.
The suggested value if decided to enable:
1440 (one day).

%EMERGENCY_REDSKY_ -1 (user number [-1 - The times that the user is allowed to close
USER_MANDATORY_LOCAT can cancel 100] the location dialog before location becomes
ION_WXT% the dialog mandatory (that is, they cannot close the
always) location window).
Possible values:
▪ N = -1 (user can cancel the dialog
always)
▪ N = 0 (user is not allowed to cancel the
dialog - mandatory location always)
▪ N > 0 (user is allowed to cancel the
dialog N times before it becomes
mandatory)

%EMERGENCY_REDSKY_U aggressiv once_per_lo Defines the E911 location prompting

SER_LOCATION_PROMPTIN e, gin behavior. The “aggressive” value will show
G_WXT% once_per_ the dialog to the user on each network
login change to an unknown location, while the
“once_per_login” value will show the dialog
only once, preventing further popup and
distractions for the user.

NOTE: BWE911-*** tags are “Dynamic Built-in System Tags”. For more information, see section 5.7
Cisco BroadWorks Dynamic Built-in System Tags.

6.1.39 PAI as Identity

For incoming calls, this new parameter controls the priority of SIP From and P-Asserted-Identity
(PAI) headers, and what should be used as a calling line identity. If there is an X-BroadWorks-
Remote-Party-Info header in the incoming SIP INVITE, it is used with priority over the SIP From
and PAI headers. If there is no X-BroadWorks-Remote-Party-Info header in the incoming SIP
INVITE, this new parameter determines if the SIP From header is priority over the PAI header or
vice versa.
If enabled attribute of the <use-pai-as-calling-identity> tag is set to “true”, the PAI header is used
with priority over the From header. This calling party identity is used to resolve the contact and
present it to the user.
For outgoing calls, this logic is not applied. In the 18X, 200 OK responses, the connected line
identity is received, so the Webex application always uses the SIP PAI header with priority.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 71

 Tag Default if Supported Description
Omitted Values
%USE_PAI_AS_CALLING_ID false true, false Controls whether the calling identity,
ENTITY_WXT% presented to the user should be taken from
the SIP From or SIP P-Asserted-Identity
headers. Set to “true” to use the PAI
header with priority.

6.1.40 Disable Screen Sharing

Release 42.5 adds the ability to control the availability of the screen sharing. When the screen
sharing is disabled:
▪ the user will not see the option to initiate screen sharing in 1-1 calls
▪ the incoming screen sharing requests are rejected and user will see an informative message
By default, this feature is enabled.
Tag Default if Supported Description
Omitted Values
%ENABLE_SCREEN_SHARE true true, false Specifies if screen sharing should be
_WXT% enabled for the user.

6.1.41 Spam Call Indication

When the feature toggle (per deployment type) is enabled, and the feature is enabled in the
config file, the Webex app processes the new parameter indicating the spam call verification
status, if they are received as part of the NewCall Push Notification or call history records.
Tag Default if Supported Description
Omitted Values
%ENABLE_CALLS_SPAM false true, false Controls the availability of the spam call
_INDICATION_WXT% indication in the incoming call screen and
call history for Webex Calling only.

6.1.42 Noise Removal for PSTN/Mobile Calls

This feature provides a better calling experience to calling users when they talk to non-Webex
users on PSTN or mobile devices. When this feature is enabled, users are shown the Noise
Removal indicator and can choose to turn it on or off.
Tag Default if Supported Description
Omitted Values
%ENABLE_NOISE_REMO false true, false Enables the local noise removal for remote
VAL_WXT% (incoming) media.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 72

 6.1.43 QoS DSCP Marking
QoS DSCP marking is supported with the Webex app calling media RTP packets (Audio and
Video). DSCP determines traffic classification for network data. This can be used to determine
which network traffic requires higher bandwidth, has a higher priority, and is more likely to drop
packets.

NOTE: Recent versions of the Microsoft Windows operating system do not allow applications to directly
set DSCP or UP on outgoing packets, instead requiring the deployment of Group Policy Objects (GPO) to
define DSCP marking policies based on UDP port ranges.

Tag Default if Supported Description

Omitted Values
%ENABLE_AUDIO_QOS_ true true, false Enables QoS for audio calls.
WXT%
%AUDIO_QOS_VALUE_ 46 0-63 Specifies the QoS value for the selected
WXT% QoS type for the audio calls.
Note: Default value is used, if no value is
provided, or the value couldn't be parsed
successfully.
%ENABLE_VIDEO_QOS_ true true, false Enables QoS for video calls
WXT%
%VIDEO_QOS_VALUE_ 34 0-63 Specifies the QoS value for the selected
WXT% QoS type for the video calls.
Note: Default value is used, if no value is
provided, or the value couldn't be parsed
successfully.

6.1.44 Primary Profile

With the integration of the Shared lines (6.2.12 Shared-Line Appearance), if user’s line is shared
with another user, there may be multiple profiles of the same type configured for the user. To
select the correct profile to sign in the Phone services, the Cisco BroadWorks has been
enhanced to indicate whether a user owns a device i.e. it is assigned the Primary Line/Port for a
device - for more information about the Cisco BroadWorks update, check Owner Flag In Device
List To Support Webex Client Shared Lines.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 73

 Primary Line/Port configuration for Identity/Device Profile in the admin portal

At login, the Webex application checks how many devices are available for the given type. If there
is just a single profile configured (user's line is not shared with another user), Phone services will
not check for the primary flag and will sign in using the single profile available. If there are
multiple profiles configured for the given platform (Desktop, Mobile or Tablet), the device that the
user owns will be used.

Starting with Release 43.2, a new configuration option (device-owner-restriction) is added to

control whether the primary profile restriction should be applied. It can be used to allow the
Webex application to use a non-primary Line/Port profile to sign in the Phone services. This
config option is applied for all the configurations, regardless the number of profiles configured for
the user (If the device ownership restriction is enabled and there is no device with Primary
Line/Port for the corresponding platform, Phone services will not connect).

Same restriction applies to the devices user can pair with in the Desktop Webex app. User can
see and pair only with devices he is owning. This prevents pairing with devices of another user
that has shared or virtual line assigned. The value of the same configuration parameter applies to
this restriction too.

<config>
<services><calls>
<device-owner-restriction enabled="%ENABLE_DEVICE_OWNER_RESTRICTION_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_DEVICE_OW true true, false Controls the device owner restriction – if the
NER_RESTRICTION_WX Phone Services should use the primary
T% profile for the given device

NOTE: It is recommended owner's restriction to be enabled. If disabled, the Phone services will use the
first profile found to sign in and some problems may occur if there are multiple profiles configured for the
user of the same type.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 74

 6.1.45 Block List (Webex Calling only)
Starting with 43.5 the Webex app introduces user defined block list of phone numbers. If the
feature is enabled, user can specify incoming calls from specific numbers to be blocked on the
server side and not delivered on any of the user's devices. User can see these blocked calls in
the call history.
User can configure the block list from two places - Calling Preferences and Call History. In the
Preferences, user can see the list of blocked numbers and edit it. In the Call History, user can see
the call history records for the calls blocked by the user defined block list. These records have
Blocked indication if the number is in the user defined block list and user will have the option to
unblock the number directly for given record. Block option is also available.
Rules for the numbers added to the user-defined block list:
◼ Number format
- Blocking from the Calling Preferences apply E.164 format restriction locally in the Webex app
- Blocking from the Call History is allowed for all the Webex Calling records
- The Cisco BroadWorks may allow or reject requests for new numbers added in the block list
based on the number format
◼ Internal numbers - incoming calls from internal numbers will be delivered to the user, even if they
are part of the user-defined block list
The user defined block list is configured on the Cisco BroadWorks and is applied to all the WxC
devices for the user.This feature works together with the admin defined block list, which is not
configurable by the user and can be controlled only by the administrators through the Control
Hub. There are NO call history records for the incoming calls blocked by the admin defined block
list.
The user defined block list is applied after the STIR/SHAKEN, admin defined block list and the
anonymous call rejection policies.
<config>
<services><calls>
<call-block enabled="%ENABLE_CALL_BLOCK_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_CALL_BLOCK true true, false Enables the user defined block list
_WXT% Set to “true”, to see the block list in the
Calling Preferences and Call History

NOTE: This feature depends on the Cisco BroadWorks Call Block service being assigned to the user.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 75

 6.1.46 Media Adaptation and Resilience Implementation (MARI)

6.1.46.1 Rate Adaptation

The Webex application has already integrated adaptive media quality techniques to ensure that
audio is not affected by any video packet loss, and to ensure that video can leverage video rate
adaptation to manage the amount of bandwidth used during times of congestion.
Rate adaptation or dynamic bit rate adjustments adapt the call rate to the variable bandwidth
available, down-speeding or up-speeding the video bit rate based on the packet loss condition.
An endpoint will reduce bit rate when it receives messages from the receiver indicating there is
packet loss; and once the packet loss has decreased, up-speeding of the bit rate will occur.
There are no configurable settings to control the usage of the rate adaptation mechanism.

6.1.46.2 Forward Error Correction (FEC) and Packets Retransmission (RTX)

Starting with Release 43.4, the Webex App adds to the media adaptation mechanism the support
for Forward Error Correction (FEC) and Packets Retransmission (RTX) for both audio and video
media.
FEC provides redundancy to the transmitted information by using a predetermined algorithm. The
redundancy allows the receiver to detect and correct a limited number of errors, without the need
to ask the sender for additional data. FEC gives the receiver an ability to correct errors without
needing a reverse channel (such as RTCP) to request retransmission of data, but this advantage
is at the cost of a fixed higher forward channel bandwidth (more packets sent).
The endpoints do not use FEC on bandwidths lower than 768 kbps. Also, there must also be at
least 1.5% packet loss before FEC is introduced. Endpoints typically monitor the effectiveness of
FEC and if FEC is not efficient, it is not used.
FEC consumes more bandwidth than retransmission but has less delay. RTX is used when small
delay is allowed and there are bandwidth constraints. In case of large delay and enough
bandwidth, FEC is preferable.
The Webex App dynamically selects RTX or FEC depending on negotiated bandwidth and delay
tolerance for a given media stream. FEC results in higher bandwidth utilization due to redundant
video data, but it doesn’t introduce additional delay to recover lost packets. Whereas RTX doesn’t
contribute to higher bandwidth utilization, because the RTP packets are retransmitted only when
the receiver indicates packet loss in RTCP feedback channel. RTX introduces packet recovery
delay due to the time it takes for the RTCP packet to reach the receiver from the sender and for
the retransmitted packet to reach the receiver from the sender.
FEC is required to be enabled to have RTX enabled.
<config><services><calls>
<audio>
<audio-quality-enhancements>
<mari>
<fec enabled=”%ENABLE_AUDIO_MARI_FEC_WXT%”>
<x-ulpfecuc>8000</x-ulpfecuc>
<payload>111</payload>
<max_esel>1400</max_esel>
<max_n>255</max_n>
<m>8</m>
<multi_ssrc>1</multi_ssrc>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 76

 <non_seq>1</non_seq>
<feedback>0</feedback>
<order>FEC_SRTP</order>
</fec>
<rtx enabled=”%ENABLE_AUDIO_MARI_RTX_WXT%”>
<mari-rtx>90000</mari-rtx>
<payload>112</payload>
<time>180</time>
<data-flow>1</data-flow>
<order>RTX_SRTP</order>
</rtx>
</mari>
...
<video>
<video-quality-enhancements>
<mari>
<fec enabled="%ENABLE_VIDEO_MARI_FEC_WXT%">
<x-ulpfecuc>8000</x-ulpfecuc>
<payload>111</payload>
<max_esel>1400</max_esel>
<max_n>255</max_n>
<m>8</m>
<multi_ssrc>1</multi_ssrc>
<non_seq>1</non_seq>
<feedback>0</feedback>
<order>FEC_SRTP</order>
</fec>
<rtx enabled="%ENABLE_VIDEO_MARI_RTX_WXT%">
<mari-rtx>90000</mari-rtx>
<payload>112</payload>
<time>180</time>
<data-flow>1</data-flow>
<order>RTX_SRTP</order>
</rtx>
</mari>

Tag Default if Supported Description

Omitted Values
%ENABLE_AUDIO_MARI_FEC_WXT% false true, false Enables FEC for Audio calls
%ENABLE_AUDIO_MARI_RTX_WXT% false true, false Enables RTX for Audio calls
(requires enabled audio FEC)
%ENABLE_VIDEO_MARI_FEC_WXT% false true, false Enables FEC for Video calls
%ENABLE_VIDEO_MARI_RTX_WXT% false true, false Enables RTX for Video calls
(requires enabled video FEC)

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 77

 6.2 Desktop Only Features

6.2.1 Forced Logout

This feature allows Cisco BroadWorks to track online client instances with the same device type
and only allow one of them to be online at any one time. When Cisco BroadWorks notifies the
client to log out, the SIP connection is terminated, and the client indicates that calling is not
connected.
This feature is needed in some deployments where similar clients can be otherwise online at the
same time, causing side effects. One example is a user with a desktop machine at work and at
home, where the incoming calls would only be received by one of the clients, depending on which
SIP registration is active.
Forced logout is based on SIP, the client sends a SIP SUBSCRIBE to the call-info event package
with a special appid-value in the From header, regardless of the bsoft-call-info parameter value.
When Cisco BroadWorks detects multiple client instances online with the same appid, it sends a
special SIP NOTIFY to the older client instance, causing it to log out. For example, Desktop
clients would have an identical appid-value although there is no restriction about the usage of this
identifier on the client side. The appid-value is configured by the service provider.
Note that in order to use forced logout, the SIP Call-Info subscription must be enabled.
For information about the Cisco BroadWorks patches and releases needed for this feature, see
the section on Cisco BroadWorks Software Requirements in the Webex for Cisco BroadWorks
Solution Guide.
See the following example for configuration details (SIP is the only supported control protocol in
this release).
<config>
<services>
<forced-logout enabled="%ENABLE_FORCED_LOGOUT_WXT%" control-protocol="SIP"
appid="%FORCED_LOGOUT_APPID_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_FORCED_ false true, false Enables forced logout.
LOGOUT_WXT%
%FORCED_LOGOUT_ empty string Appid used on the server side for correlation.
APPID_WXT% This can be any string.
Example: “123abc”

6.2.2 Call Pickup

Call Pickup is a multiuser service that allows selected users to answer any ringing line within their
call pickup group. A call pickup group is defined by the administrator and is a subset of the users
in the group who can pick up each other’s calls.
The following pickup cases are supported:
▪ Blind call pickup

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 78

▪ Directed call pickup (which enables a user to answer a call directed to another phone in their
group by dialing the respective feature access code followed by the extension of the ringing
phone).
<config>
<services><calls>
<call-pickup blind="%ENABLE_CALL_PICKUP_BLIND_WXT%"
directed="%ENABLE_CALL_PICKUP_DIRECTED_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_CALL_PICKU false true, false Set to “true” to enable Blind Call Pickup.
P_BLIND_WXT%
%ENABLE_CALL_PICKU false true, false Set to “true” to enable Directed Call Pickup.
P_DIRECTED_WXT%

6.2.3 Boss-Admin (Executive-Assistant) Support

The Boss-Admin, known as Executive-Assistant feature on Cisco BroadWorks, allows an
assistant to operate on behalf of an executive to screen, answer, and place calls as the
“executive”. One assistant can have many executives and it is possible to:
▪ Select the desired role when making a call.
▪ Answer an incoming call on behalf of an executive and then push the call to the executive. In
addition to that, all usual call management options are available.
▪ See that an incoming call is actually for the executive.
Executive and Executive-Assistant are two interrelated Cisco BroadWorks services that together
deliver the following functionality:
▪ A user with the Executive service can define a pool of assistants who manage their calls. The
assistants have to be selected among the users in the same group or enterprise who have
the Executive-Assistant service assigned.
▪ A user with the Executive-Assistant service can answer and initiate calls on behalf of their
executives.
▪ Both the executive and their assistants can specify which calls should be forwarded to the
assistants, how assistants should be alerted about incoming calls, and which of the calls
forwarded to the assistants should be presented to the executive for screening.
<config>
<services>
<executive-assistant enabled="%ENABLE_EXECUTIVE_ASSISTANT_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_EXECUTIVE_ false true, false Set to “true” to enable the Boss-Admin
ASSISTANT_WXT% feature.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 79

 NOTE: The feature Boss-Admin (Executive-Assistant) support is not available in combination with
Shared-Lines.

6.2.4 Escalate SIP Calls to Meeting (Webex Calling only)

The client provides the functionality to escalate an ongoing SIP call to a meeting via Webex
Calling. By using this functionality instead of a standard ad-hoc conference, the user will be able
to use video as well as screen sharing during the meeting.
<config>
<services><calls>
<escalate-to-webex-meeting
enabled="%ENABLE_CALLS_ESCALATE_TO_WEBEX_MEETING_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_CALLS_ESCAL false true, false Set to “true” to enable the Escalate to
ATE_TO_WEBEX_MEETIN Webex Meeting menu option.
G_WXT%

6.2.5 Desk Phone Control Calling – Auto Answer

Auto answer enables the user to use Desk Phone Control (DPC) for outgoing calls on the client to
manage MPP phones with zero touch answer.
The selected MPP phone will carry the audio/video for the outgoing DPC call.
Auto answer can work on the primary and non-primary provisioned devices. If the user has more
than one registered desk phone that can be paired with, only the selected/paired device shall
auto-answer.

NOTE: Auto answer will not affect incoming calls while in DPC mode, so that the desk phone rings for
incoming calls.

<config>
<services><calls>
<deskphone-control auto-answer="%ENABLE_DESKPHONE_CONTROL_AUTO_ANSWER_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_DESKPHONE true true, false When set to “true”, enables desk phone
_CONTROL_AUTO_ANS control auto answer.
WER_WXT%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 80

 6.2.6 Auto Answer with Tone Notification
This feature enables automatic incoming call answer support for local devices, if this is indicated
in the incoming call request.
Tag Default if Supported Description
Omitted Values
%ENABLE_AUTO_ANSW false true, false When set to “true”, enables automatic
ER_WXT% incoming call answer if this is requested
from the backend.

6.2.7 Desk Phone Control – Mid Call Controls – Conference

This feature enables Conference and Merge options for Xsi calls.
Tag Default if Supported Description
Omitted Values
%ENABLE_XSI_CONFER false true, false When set to “true”, enables Conference
ENCE_CALLS_WXT% and Merge options for Xsi calls.

6.2.8 Call Pickup Notification with BLF

Call pickup notification is a desktop feature that provides the ability for users to use the Call Pick
up feature when members are not physically close to each other and cannot hear the ringing of
their colleague's phone.
The desktop Webex application displays a notification in the upper right screen if a member in
their Busy Lamp Field (BLF) list has a ringing call. The notification of a ringing call has an option
to pick up the other member's call and a tooltip to display who is calling (using Direct Call Pickup).
The Direct Call Pickup service must be assigned for the notification to work.
Starting with Release 43.4, the list of BLF-monitored users is available in the Multi Call Window
(MCW) for Calling (available only for Windows). Integration of the BLF list in the MCW includes:
1. Monitor the incoming calls with option to pick-up the call or ignore the alert.
2. See the full list of the BLF users.
3. Monitor the presence of the users – rich presence is available only for the users with
Webex Cloud entitlement. Basic (telephony) presence is available only for the
BroadWorks-only users.
4. Start a call with a BLF user.
5. Start a chat with a BLF user – available only for users with Webex Cloud entitlement.
6. Add a BLF user as a contact.

<config>
<services>
<calls>
<busy-lamp-field enabled="%ENABLE_BUSY_LAMP_FIELD_WXT%">
<display-caller enabled="%ENABLE_BLF_DISPLAY_CALLER_WXT%"/>
<notification-delay time="%BLF_NOTIFICATION_DELAY_TIME_WXT%"/>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 81

 Tag Default if Supported Description
Omitted Values
%ENABLE_BUSY_LAMP_ false true, false Enables the Busy Lamp Field monitoring
FIELD_WXT% and ringing notification for other users with
ability to pick up the calls.
%ENABLE_BLF_DISPLAY true true, false Enables displaying the caller display
_CALLER_WXT% name/number in the ringing notification.
%BLF_NOTIFICATION_D 0 0-60 Controls how many seconds the ringing
ELAY_TIME_WXT% notification should be delayed before it is
displayed to the user.

6.2.9 Remote Control Event Package

For Click to Dial clients like the BroadWorks Receptionist thin client and Go integrator where the
Webex app is the calling device, when receiving a call or handling hold/resume the Webex app
now honors the remote control event package.
Tag Default if Supported Description
Omitted Values
%ENABLE_REMOTE false true, false When set to “true”, specifies that the remote
_CONTROL_EVENT control should be enabled for the user.
S_WXT%

6.2.10 Call Queue Agent CLID Selection

When agents make calls to their customers, they want the customers to see the appropriate
Calling Line ID (CLID) rather than their personal/corporate CLID. For example, if agent Mary
Smith is joined to the Technical Support call queue, then when calling customers, Mary wants the
customers to see her CLID as Technical Support, not Mary Smith.
Admins in Control Hub or CommPilot can specify for a Call Queue one or more DNIS numbers to
be used for outgoing CLID. Agents then have the option to select one of the DNIS numbers to be
used as their CLID when making outgoing calls. The Webex app provides the ability for agents to
select which DNIS to use as their CLID.
Tag Default if Supported Description
Omitted Values
%ENABLE_CALL_CE false true, false Enables outgoing calls (CLID selection) on behalf
NTER_AGENT_OUT of the Call Center queue.
GOING_CALLS_WXT
%

6.2.11 Survivability Gateway (Webex Calling only)

Starting with Release 43.2, Webex application adds support for Survivability call mode. if the feature is
enabled and there is no Webex Cloud connectivity, the Webex application can run in survivability
mode. In this mode there is limited calling functionality available for the user.
Local Survivability Gateway is deployed by the customer.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 82

 NOTE: This feature provides confidence in migration from On-premises to Cloud calling solutions.

<config>
<protocols>
<sip>
<survivability-gateway enabled="%ENABLE_SURVIVABILITY_GATEWAY_WXT%" fallback-
time="%SURVIVABILITY_FALLBACK_TIME_WXT%">%BWSURVIVABILITYGATEWAY%</survivability-
gateway>

Tag Default if Supported Description

Omitted Values
%ENABLE_SURVIVABILI false true, false Enables the survivability mode support.
TY_GATEWAY_WXT%
%SURVIVABILITY_FALLB 30 >=30 Specifies the fallback time (survivability
ACK_TIME_WXT% gateway to SSE)

6.2.12 Shared-Line Appearance

Starting with Release 42.12, Webex application adds support for multiple lines. A Webex user
can have a primary line and up to 9 share lines with other users.

Administrator should set up the Shared Call Appearances for each shared line.

Webex client will detect line configuration update within 12h timeframe and will request the user
to restart the application. Re-login of the user will apply the line updates immediately.

Tag Default if Supported Description

Omitted Values
%ENABLE_MULTI_LI false true, false Enables multiple lines support (if configured). If
NE_WXT% disabled (set to "false"), just the first line
configured will be used by the application.

NOTE 1: The feature Boss-Admin (Executive-Assistant) support is not available in combination with
Shared-Lines.

6.2.13 Virtual Lines (Webex Calling only)

For Webex Calling deployment only, the Webex App supports multi-line configuration using virtual
lines. Functionally, the configuration with virtual lines matches the multi-line using shared lines – having
the ability to see the virtual lines configured for the user and to use them for incoming and outgoing
calls. A maximum of 10 combined virtual lines and shared lines can be configured.
Release 43.4 extends the virtual lines support and adds the Call Park and Call Park Retrieve.
The following depicts the changes of the config template related to the virtual lines support.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 83

<config>
<protocols>
<sip>
<lines multi-line-enabled="%ENABLE_MULTI_LINE_WXT%">
...
<line lineType="%BW-MEMBERTYPE-1%">
<external-id>%BWUSEREXTID-1%</external-id>
...
</line>
<line lineType="%BW-MEMBERTYPE-2%">
<external-id>%BWUSEREXTID-2%</external-id>
...
</line>
...
<line lineType="%BW-MEMBERTYPE-10%">
<external-id>%BWUSEREXTID-10%</external-id>
...
</line>
<protocols>

6.3 Mobile Only Features

6.3.1 Emergency Calling

Webex for Cisco BroadWorks supports Native Emergency Calling.
When the feature is enabled, at initiating an outgoing VoIP call, the application analyzes the
dialed number and compares it against the list of emergency numbers configured. If the number
is identified as an emergency one, the application executes the configured dial behavior. It is
configurable using the dial-sequence tag.
Supported modes are:
▪ cs-only – The client places emergency calls only through the cellular network if the network is
available.
▪ cs-first – Upon initiating an emergency call, the client checks the network type to which the
current device is connected. If the cellular network is available, the client places that call over
the cellular network. If the cellular network is not available but a cellular data/WiFi network is
available, the client places the call over the cellular data/WiFi network as a VoIP call. Also, if
the emergency call is placed through the cellular network, the client suggests to the user to
retry the emergency call as VoIP.
▪ voip-only – The client places emergency calls only as VoIP if the cellular data/WiFi network is
available.
▪ cs-voip – The client analyzes if the device can initiate it as native circuit-switched (CS) call
(without taking into account if the CS network is available or not). If the device can start a
native call, the emergency number is dialed as an emergency CS call. Otherwise, the call is
dialed as VoIP.

NOTE: If VOIP calling is disabled, the only meaningful value for emergency dial sequence
(%EMERGENCY_CALL_DIAL_SEQUENCE_WXT%) is cs-only.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 84

There is an emergency calls disclaimer message displayed to the user at sign in. It is not
controlled through the configuration options.
Tag Default if Supported Description
Omitted Values
%ENABLE_EMERGENCY_DIALI false true, false Set to “true” to enable emergency
NG_WXT% calls detection.
The default value is empty.
%EMERGENCY_CALL_DIAL_ cs-only cs-only, cs- Controls the dial-sequence mode for
SEQUENCE_WXT% first, voip- emergency calls.
only, cs-
voip
%EMERGENCY_DIALING_NUM “911,112” CSV list CSV list of emergency numbers.
BERS_WXT% Example: 911,112

6.3.2 Push Notifications for Calls

When an incoming call is received, the mobile client receives a push notification (PN) first. There
is a config parameter that can be used to control when the SIP REGISTER session to be
established:
1. When the push notification is received, OR
2. When the call is accepted by the user.
The second approach is recommended. However, compared to first case, it adds some delay
before the call is established.
According to the iOS 13 requirements, the VoIP PNs should be used only for incoming calls. The
rest of the call-related events should use regular PNs.
To meet this requirement, new PN registration API is introduced and it requires corresponding
patch to be applied on the Application Server. If the backend is not configured to support the iOS
13 PNs, the configuration parameter can be used to enforce usage of the legacy push
notifications, where all the call related events are delivered through VoIP PNs.
There is a Push Notification sent by the Application Server (AS) when a ringing call is accepted
by the callee on another location, closed by the caller, or, for example, redirected to Voicemail.
With the iOS 13, this type of Push Notification is now a regular one and it has some restrictions. It
may be delayed by the Apple Push Notification Service (APNS) or even not delivered at all. To
handle missing or delayed Call Update PNs, a configurable ringing timeout is added to control the
maximum ringing time. If the maximum ringing time is reached, the ringing is stopped for the
callee and the call is treated as missed. On the caller side, the call may remain in ringing state
until the ring-no-answer policy configured on the Application Server (AS) is executed.
To keep the application behavior consistent, the configurable ringing timer applies to both Android
and iOS.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 85

A separate configuration option is added to specify the call decline behavior when an incoming
call is received as a Push Notification. The client can be configured to ignore the call or to
respond to the server through Xsi with decline set to “true” or “false”, in which case, the assigned
Cisco BroadWorks call treatment services will be applied. If “decline_false” is configured, the call
continues ringing until the originator abandons or the no-answer timer expires, and the associated
call treatment services start. If “decline_true” is configured, the decline reason specifies the call
processing. If the decline reason is set to “busy”, the server immediately forces the busy
treatment service. If “temp_unavailable” is configured, the temporary unavailable treatment
service is applied.
<config>
<services>
<push-notifications-for-calls enabled="true"
connect-sip-on-accept="%PN_FOR_CALLS_CONNECT_SIP_ON_ACCEPT_WXT%"
ring-timeout-seconds="%PN_FOR_CALLS_RING_TIMEOUT_SECONDS_WXT%"/>
<calls>
<reject-with-xsi mode="%REJECT_WITH_XSI_MODE_WXT%"
declineReason="%REJECT_WITH_XSI_DECLINE_REASON_WXT%"/>

Tag Default if Supported Description

Omitted Values
%PN_FOR_CALLS_ false true, false Controls when the SIP REGSITER session is
CONNECT_SIP_ON_ established – upon receiving a Push Notification
ACCEPT_WXT% for incoming call or upon accepting it.
%PN_FOR_CALLS_ 35 [0-180] Controls the maximum incoming call ringing
RING_TIMEOUT_ time for calls received through PN. If no CallUpd
SECONDS_WXT% PN is received within the given period, the call
will be treated as missed.
%REJECT_WITH_ decline_ ignore, Specifies the call decline behavior.
XSI_MODE_WXT% false decline_true,
decline_false
%REJECT_WITH_ busy busy, Specifies the call decline reason, if the reject
XSI_DECLINE_REAS temp_unavai mode is set to “decline_true”.
ON_WXT% lable

6.3.2.1 MWI
With the MWI feature enabled, the Mobile Webex client subscribes for the MWI Push Notification to
receive updates with the voicemail of the user and notify him.
To reduce the number of notifications and to avoid unnecessary distraction, the MWI Push Notifications
are suppressed in some cases. For instance, when the user is listening to the Voicemail messages or
is marking them as read from within the Mobile Webex client (unread number is decreasing). There is
no configurable option to control this.
For more information about MWI, check section 6.1.27 Voicemail, Visual Voicemail, Message
Waiting Indicator.

6.3.2.2 Ring Splash

BroadWorks services (like DND) can send ring reminders when incoming is redirected. The
Webex Mobile client can be configured to enable the Ring Splash Push Notifications and present
them to the user when they are triggered by the BroadWorks.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 86

config>
<services>
<ring-splash enabled="%ENABLE_RING_SPLASH_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_RING_SPLASH_WX false true, false Enables Ring Splash in the
T% BroadWorks config.

6.3.3 Single Alerting

The Mobile Single Alert feature is intended for fixed-mobile convergence (FMC) / Mobile Network
Operator (MNO) deployments leveraging the BroadWorks Mobility service. Without it, when
logged into the Webex client and receiving an incoming call, the user will receive concurrently two
calls – a native one and a Push Notification (VoIP) call. When the feature is enabled, the
application will disable Mobility alerting on the user's BroadWorks Mobility location when logging
in and enable the alerting when logging out. An important precondition for using this feature is for
the user to have the BroadWorks Mobility service assigned and exactly one location configured.
<config>
<services><calls>
<single-alerting enabled="%ENABLE_SINGLE_ALERTING_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_SINGLE_ false true, false Set to “true” to enable Single Alerting.
ALERTING_WXT%

6.3.4 Click to Dial (Call Back)

The outbound Click to Dial ensures that the end user can have a call on their personal Circuit
Switched mobile phone and deliver their business DN as the calling line ID.
The Mobile Webex client supports Click to Dial (Call Back) calls using the BroadWorks Anywhere
service. The BroadWorks Anywhere locations in the Webex application are called Single Number
Reach (SNR) locations.
When the feature is enabled, users can select the SNR location from the device pairing menu.
When paired with SNR location, all outgoing calls are initiated using Click to Dial (Call Back) calls.
To prevent double alerting, Push Notifications for incoming calls are disabled.
When a user initiates a Click to Dial call, they will see the outgoing call screen with information to
expect incoming call on the selected SNR location. This screen is closed automatically based on
configurable timer.
At disconnecting from an SNR location, the application registers again for Push Notifications for
incoming calls.
<config>
<services>
<dialing>

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 87

 <call-back enabled="%ENABLE_DIALING_CALL_BACK_WXT%"
timer="%DIALING_CALL_BACK_TIMER_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_DIALING_ false true, false Set to “true” to enable Click to Dial (Call Back)
CALL_BACK_WXT% calls.
%DIALING_CALL_ 10 [3-20] Controls the number of seconds before the
BACK_TIMER_WXT% Call Back screen is automatically closed.

6.3.5 MNO Support

6.3.5.1 Call with Native Dialer

This feature adds support for Mobile Network Operator (MNO) deployments leveraging the
BroadWorks Mobility (BWM) service. It is assumed that the user has the BroadWorks Mobility
service assigned to them and has at least one location configured.
The user’s ability to initiate calls through the native dialer is controlled by the native configuration
tag. If enabled, the application will launch the native dialer and make the call. Furthermore, the
availability of VoIP calling is controlled by the voip tag – based on the deployment requirements
VoIP calls may be enabled or disabled.
If VoIP and Native calling are enabled, the user will be able to choose which option to use.
The <dialing-mode> tag controls if users can select how incoming and outgoing calls are to be
started/received. Requires both the native and VoIP calling to be enabled.
<config>
<services>
<dialing>
<voip enabled="%ENABLE_DIALING_VOIP_WXT%"/>
<native enabled="%ENABLE_DIALING_NATIVE_WXT%"/>
<dialing-mode enabled="%ENABLE_DIALING_MODE_WXT%"
default="%DIALING_MODE_DEFAULT_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_DIALIN true true, false Set to “true” to enable VoIP call option.
G_VOIP_WXT%
%ENABLE_DIALIN false true, false Set to “true” to enable Native call option.
G_NATIVE_WXT%
%ENABLE_DIALING false true, false Enables the dialing mode selection by the user,
_MODE_WXT% through the Call Settings in Preferences.

%DIALING_MODE_ voip voip, native Specifies the default dialing mode selected when the
DEFAULT_WXT% dialing mode is enabled in Preferences.

%DIALING_NATIVE_ false true, false Controls whether the availability of the Native calling
ENABLE_BWKS_MO should depend on the BroadWorks Mobility service
BILITY_DEPENDEN assignment and Mobility Location being configured
CY_WXT% for the user.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 88

NOTE 1: At least one of the voip and native calling should be enabled.

NOTE 2: If just the native calling is enabled, in MNO deployments, it is recommended to disable the single-alerting
to prevent the client from disabling the BWM alerting.

NOTE 3: If both native and voip callings are enabled, in MNO deployments, it is recommended to enable the
single-alerting to prevent double alerting.

6.3.5.2 Mid-Call Controls

This feature allows the Mobile Webex client to control via XSI native calls on the mobile device
that are anchored on BroadWorks. The XSI Call Controls is available only if:
- BroadWorks Mobility (BWM) service is assigned to the user
- There is just a single BMW Mobile Identity configured.
- Native dialing mode is selected by the user (for more information check section 6.3.5.1
Call with Native Dialer)
- There is a call anchored on BroadWorks, going through the BMW service
- There is ongoing cellular call on the mobile device
Tag Default if Supported Description
Omitted Values
%ENABLE_XSI_CA false true, false Enables XSI call control for MNO environment.
LL_CONTROL_WXT
%
%XSI_CALL_CONT MNO_Ac MNO_Acce Controls the XSI MNO deployment type used by
ROL_DEPLOYMEN cess ss, the application. The possible values are
T_TYPE_WXT% MNO_Netw MNO_Access which shows all XSI calls with the
ork device types defined in the node below and
MNO_Network which shows all XSI calls.

%DEPLOYMENT_DE “” string The device type name(s) that should be used in the
VICE_TYPE_1_WXT MNO_Access deployment type.
%,
%DEPLOYMENT_DE
VICE_TYPE_2_WXT
%,
%DEPLOYMENT_DE
VICE_TYPE_3_WXT
%

%ENABLE_XSI_HOL true true, false Controls if the Call Hold action should be available
D_CALLS_WXT% for the user for XSI mobile calls.

6.3.5.3 Outgoing Calling Line Identity (CLID) – Dual Persona

With Mobile Release 42.12, the Webex app allows users to select their Calling Line Identity
(CLID) presented to the remote party upon initiating an outgoing call.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 89

If user is configured with Cisco BroadWorks Mobility, typical configuration for Mobile Network
Operator (MNO) deployments, and Native calling is enabled, user can select which identity to be
presented to the people they are calling. User can choose their business or personal identity.
There is also an option to hide own identity and the call to be presented as Anonymous.
For VoIP calls, user also has an option to control his CLID. The available option in this case is
only to control whether to hide his identity or not.
Persona management and CLID blocking are controlled through separate config options.
<config>
<services>
<dialing>
<calling-line-id-delivery-blocking
enabled="%ENABLE_CLID_DELIVERY_BLOCKING_WXT%"/>
<mobility-persona-management
enabled="%ENABLE_MOBILITY_PERSONA_MANAGEMENT_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_CLID_DELIVERY_B false true, false Enables the calling line ID delivery
LOCKING_WXT% blocking. It applies to all the outgoing
types of calls for the user.
%ENABLE_MOBILITY_PERSON false true, false Enables the personal management for
A_MANAGEMENT_WXT% Native calls when the deployment type
configured as MNO_Access or
MNO_Network. (BroadWorks Mobility
is used for the native calls and all the
native calls are anchored on
BroadWorks)

6.3.5.4 Notification for Native Calls

For users deployed with MNO, this feature adds a notification banner for native calls, which can
be controlled through the Webex app. This notification relies on push notification, send by the
Application Server once the call is established.
Tag Default if Supported Description
Omitted Values
%ENABLE_PN_MOBILE_CALL_ true true, false Enables the subscription for the
INFO_WXT% MOBILE_CALL_INFO push
notification.

6.3.5.5 Move Native Call to Converged Meeting

For users deployed with MNO, this feature allows for a native voice call to be escalated to a
meeting for both parties of a 1:1 call (even if the other party is not a Webex user). If the remote
user is a Webex user, once in a meeting, the parties will have the ability to:
▪ Initiate Webex in Meeting Chat
▪ Add Video (note that audio will continue in the native call)
▪ Share screen / content

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 90

▪ Trigger Meetings recording

Tag Default if Supported Description

Omitted Values
%ENABLE_CALLS_ false true, false Enables Power Up (Invite and Meet, Video Meet
ESCALATE_TO_WE actions).
BEX_MEETING_WX
T%

6.3.5.6 MNO Mobility - In-call Widget

Release 43.7 of the Android Webex app (Mobile and Tablet) officially introduces a new call
control widget (bubble), providing additional call control for native calls anchored on Cisco
BroadWorks, using the Mobility service. The widget will be displayed on top of the Native UI and
will allow the user the following actions:
▪ Hold/Resume
▪ Consultative/Blind Transfer – places the user in the transfer dialog in the Webex app
▪ Video Meeting - moves the parties into a Webex Meeting
▪ End call

<config>
<services><calls>
<hold xsi-enabled="%ENABLE_XSI_HOLD_CALLS_WXT%" widget-
enabled="%ENABLE_WIDGET_HOLD_CALLS_WXT%"/>
<transfer-call enabled="%ENABLE_TRANSFER_CALLS_WXT%" xsi-
enabled="%ENABLE_XSI_TRANSFER_CALLS_WXT%" widget-
enabled="%ENABLE_WIDGET_TRANSFER_CALLS_WXT%" type="%TRANSFER_CALL_TYPE_WXT%"/>
<escalate-to-webex-meeting
enabled="%ENABLE_CALLS_ESCALATE_TO_WEBEX_MEETING_WXT%" widget-
enabled="%ENABLE_WIDGET_CALLS_ESCALATE_TO_WEBEX_MEETING_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_WIDGE true true, false Controls the availability of the Hold action in the
T_HOLD_CALLS_W Call Widget.
XT%
%ENABLE_WIDGE true true, false Controls the availability of the Transfer action in the
T_TRANSFER_CAL Call Widget.
LS_WXT%
%ENABLE_WIDGE true true, false Controls the availability of the Video Meeting action
T_CALLS_ESCALA in the Call Widget.
TE_TO_WEBEX_M
EETING_WXT%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 91

7 Early Field Trial (BETA) Features

7.1 Simultaneous Calls with Same User

Adding support for simultaneous calls with the same user on single device.
This feature is useful for some deployments, where the presented identity of the call is not the
same as the connected identity. This leads to the inability to initiate an attended transfer back to
the original party. By enabling this feature, user will be able to handle multiple simultaneous calls
with the same remote party.
<config>
<services><calls>
<multiple-calls-per-user enabled="%ENABLE_MULTIPLE_CALLS_PER_USER_WXT%"/>

Tag Default if Supported Description

Omitted Values
%ENABLE_MULTIP false true, false Specifies if the Webex app can have just a single
LE_CALLS_PER_U or multiple WxC calls with the same user.
SER_WXT%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 92

8 Custom Tags Mapping between Webex for Cisco BroadWorks and UC-
One

The following table lists the Webex for Cisco BroadWorks custom tags, matching their legacy custom
tags for UC-One.

Webex for Cisco BroadWorks Desktop Legacy Tag Mobile Legacy Tag
Tag
%ENABLE_REJECT_WITH_ %ENABLE_REJECT_WITH_48 %ENABLE_REJECT_WITH_48
486_WXT% 6_DESKTOP% 6_MOBILE%
%REJECT_WITH_XSI_MODE_ N/A %REJECT_WITH_XSI_MODE_
WXT% MOBILE%
%REJECT_WITH_XSI_DECLIN N/A %REJECT_WITH_XSI_DECLIN
E_REASON_WXT% E_REASON_MOBILE%
%ENABLE_TRANSFER_CALL %ENABLE_TRANSFER_CALL %ENABLE_TRANSFER_CALL
S_WXT% S% S_MOBILE%
%ENABLE_CONFERENCE_CA N/A %ENABLE_CONFERENCE_CA
LLS_WXT% LLS_MOBILE%
%ENABLE_NWAY_PARTICIPA %ENABLE_NWAY_PARTICIPA N/A
NT_LIST_WXT% NT_LIST_DESKTOP%
%MAX_CONF_PARTIES_WXT %MAX_CONF_PARTIES% N/A
%
%ENABLE_CALL_STATISTICS N/A N/A
_
WXT%
%ENABLE_CALL_PULL_WXT %ENABLE_CALL_PULL_DESK %ENABLE_CALL_PULL_MOBI
% TOP% LE%
%PN_FOR_CALLS_CONNECT N/A %PN_FOR_CALLS_CONNECT
_SIP_ON_ACCEPT_WXT% _SIP_ON_ACCEPT_MOBILE%
%ENABLE_MWI_WXT% %DESKTOP_MWI_ENABLE% %ENABLE_MWI_MOBILE%
%ENABLE_MWI_WXT% %DESKTOP_MWI_ENABLE% %ENABLE_MWI_MOBILE%
%MWI_MODE_WXT% %DESKTOP_MWI_MODE% %MWI_MODE_MOBILE%
%ENABLE_VOICE_MAIL_WXT N/A N/A
%
%ENABLE_VISUAL_VOICE_M %ENABLE_VISUAL_VOICE_M N/A
AIL_WXT% AIL%
%ENABLE_FORCED_LOGOUT %ENABLE_FORCED_LOGOUT N/A
_WXT% %
%FORCED_LOGOUT_APPID_ %FORCED_LOGOUT_APPID% N/A
WXT%
%ENABLE_CALL_FORWARDI N/A N/A
NG_ALWAYS_WXT%
%ENABLE_BROADWORKS_ N/A N/A
ANYWHERE_WXT%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 93

 Webex for Cisco BroadWorks Desktop Legacy Tag Mobile Legacy Tag
Tag
%ENBLE_BROADWORKS_AN N/A N/A
YWHERE_DESCRIPTION_
WXT%
%ENABLE_BROADWORKS_A N/A N/A
NYWHERE_ALERT_ALL_LOC
ATIONS_WXT%
%BROADWORKS_ANYWHER N/A N/A
E_ALERT_ALL_LOCATIONS_D
EFAULT_WXT%
%ENABLE_BROADWORKS_A N/A N/A
NYWHERE_CALL_CONTROL_
WXT%
%BROADWORKS_ANYWHER N/A N/A
E_CALL_CONTROL_DEFAULT
_WXT%
%ENABLE_BROADWORKS_A N/A N/A
NYWHERE_DIVERSION_INHIB
ITOR_WXT%
%BROADWORKS_ANYWHER N/A N/A
E_DIVERSION_INHIBITOR_DE
FAULT_WXT%
%ENABLE_BROADWORKS_A N/A N/A
NYWHERE_ANSWER_CONFI
RMATION_WXT%
%BROADWORKS_ANYWHER N/A N/A
E_ANSWER_CONFIRMATION
_DEFAULT_WXT%
%ENABLE_EMERGENCY_DIA N/A N/A
LING_WXT%
%EMERGENCY_DIALING_NU N/A N/A
MBERS_WXT%
%ENABLE_USE_RPORT_WXT %USE_RPORT_IP% %ENABLE_USE_RPORT_MOB
% ILE%
%RPORT_USE_LOCAL_PORT N/A %RPORT_USE_LOCAL_PORT
_WXT% _MOBILE%
%USE_TLS_WXT% %USE_TLS% N/A
%SBC_ADDRESS_WXT% %SBC_ADDRESS% %SBC_ADDRESS%
%SBC_PORT_WXT% %SBC_PORT% %SBC_PORT%
%USE_PROXY_DISCOVERY_ %USE_PROXY_DISCOVERY% %USE_PROXY_DISCOVERY_
WXT% MOBILE%
%USE_TCP_FROM_DNS_ %USE_TCP_FROM_DNS% N/A
WXT%
%USE_UDP_FROM_DNS_ %USE_UDP_FROM_DNS% N/A
WXT%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 94

 Webex for Cisco BroadWorks Desktop Legacy Tag Mobile Legacy Tag
Tag
%USE_TLS_FROM_DNS_WXT %USE_TLS_FROM_DNS% N/A
%
%DOMAIN_OVERRIDE_WXT% %DOMAIN_OVERRIDE% %DOMAIN_OVERRIDE%
%SOURCE_PORT_WXT% %SOURCE_PORT% %SOURCE_PORT%
%USE_ALTERNATIVE_IDENTI %USE_ALTERNATIVE_IDENTI N/A
TIES_WXT% TIES%
%TCP_SIZE_THRESHOLD_ %TCP_SIZE_THRESHOLD% N/A
WXT%
%SIP_REFRESH_ON_TTL_WX %SIP_REFRESH_ON_TTL% N/A
T%
%ENABLE_SIP_UPDATE_SUP %ENABLE_SIP_UPDATE_SUP %ENABLE_SIP_UPDATE_SUP
PORT_WXT% PORT_DESKTOP% PORT_MOBILE%
%ENABLE_PEM_SUPPORT_ %ENABLE_PEM_SUPPORT_ N/A
WXT% DESKTOP%
%ENABLE_SIP_SESSION_ID_ N/A N/A
WXT%
%ENABLE_FORCE_SIP_INFO N/A N/A
_FIR_WXT%
%SRTP_ENABLED_WXT% %USE_SRTP% %SRTP_ENABLED_MOBILE%
%SRTP_MODE_WXT% %SRTP_PREFERENCE% %SRTP_MODE_MOBILE%
%ENABLE_REKEYING_WXT% %ENABLE_RE_KEYING_DESK %ENABLE_RE-
TOP% KEYING_MOBILE%
%RTP_AUDIO_PORT_RANGE %RTP_AUDIO_PORT_RANGE %RTP_AUDIO_PORT_RANGE
_START_WXT% _START% _START%
%RTP_AUDIO_PORT_RANGE %RTP_AUDIO_PORT_RANGE %RTP_AUDIO_PORT_RANGE
_END_WXT% _END% _END%
%RTP_VIDEO_PORT_RANGE %RTP_VIDEO_PORT_RANGE %RTP_VIDEO_PORT_RANGE
_START_WXT% _START% _START%
%RTP_VIDEO_PORT_RANGE %RTP_VIDEO_PORT_RANGE %RTP_VIDEO_PORT_RANGE
_END_WXT% _END% _END%
%ENABLE_RTCP_MUX_WXT %ENABLE_RTCP_MUX% %ENABLE_RTCP_MUX%
%
%ENABLE_XSI_EVENT_CHAN %ENABLE_XSI_EVENT_CHAN N/A
NEL_WXT% NEL%
%CHANNEL_HEARTBEAT_ %CHANNEL_HEARTBEAT% %CHANNEL_HEARTBEAT_
WXT% MOBILE%
%XSI_ROOT_WXT% %XSI_ROOT% %XSI_ROOT%
%XSI_ACTIONS_PATH_WXT% N/A %XSI_ACTIONS_PATH_MOBIL
E%
%XSI_EVENTS_PATH_WXT% N/A %XSI_EVENTS_PATH_MOBIL
E%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 95

 Webex for Cisco BroadWorks Desktop Legacy Tag Mobile Legacy Tag
Tag
%ENABLE_CALLS_AUTO_ N/A %ENABLE_CALLS_AUTO_
RECOVERY_WXT% RECOVERY_MOBILE%
%EMERGENCY_CALL_DIAL_ N/A %EMERGENCY_CALL_DIAL_
SEQUENCE_WXT% SEQUENCE_MOBILE%
%ENABLE_CALL_PICKUP_BLI N/A N/A
ND_WXT%
%ENABLE_CALL_PICKUP_ N/A N/A
DIRECTED_WXT%
%WEB_CALL_SETTINGS_URL N/A %WEB_CALL_SETTINGS_URL
_WXT% %
%USE_MEDIASEC_WXT% %USE_MEDIASEC_MOBILE% %USE_MEDIASEC_DESKTOP
%
%ENABLE_CALL_CENTER_ %ENABLE_CALL_CENTER_ N/A
WXT% DESKTOP%"
%WEB_CALL_SETTINGS_TAR N/A N/A
GET_WXT%
%WEB_CALL_SETTINGS_CFA N/A %WEB_CALL_SETTINGS_CFA
_ _VISIBLE%
VISIBLE_WXT%
%WEB_CALL_SETTINGS_DN N/A %WEB_CALL_SETTINGS_DN
D_VISIBLE_WXT% D_VISIBLE%
%WEB_CALL_SETTINGS_AC N/A %WEB_CALL_SETTINGS_AC
R_VISIBLE_WXT% R_VISIBLE%
%WEB_CALL_SETTINGS_CFB N/A %WEB_CALL_SETTINGS_CFB
_VISIBLE_WXT% _VISIBLE%
%WEB_CALL_SETTINGS_CFN N/A %WEB_CALL_SETTINGS_CFN
R_VISIBLE_WXT% R_VISIBLE%
%WEB_CALL_SETTINGS_CFN N/A %WEB_CALL_SETTINGS_CFN
A_VISIBLE_WXT% A_VISIBLE%
%WEB_CALL_SETTINGS_SIM N/A %WEB_CALL_SETTINGS_SIM
RING_VISIBLE_WXT% RING_VISIBLE%
%WEB_CALL_SETTINGS_ N/A %WEB_CALL_SETTINGS_SE
SEQRING_VISIBLE_WXT% QRING_VISIBLE%
%WEB_CALL_SETTINGS_RO_ N/A %WEB_CALL_SETTINGS_RO_
VISIBLE_WXT% VISIBLE%
%WEB_CALL_SETTINGS_ACB N/A %WEB_CALL_SETTINGS_ACB
_VISIBLE_WXT% _VISIBLE%
%WEB_CALL_SETTINGS_CW N/A %WEB_CALL_SETTINGS_CW
_VISIBLE_WXT% _VISIBLE%
%WEB_CALL_SETTINGS_CLI N/A %WEB_CALL_SETTINGS_CLI
DB_VISIBLE_WXT% DB_VISIBLE%
%WEB_CALL_SETTINGS_PA_ N/A %WEB_CALL_SETTINGS_PA_
VISIBLE_WXT% VISIBLE%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 96

 Webex for Cisco BroadWorks Desktop Legacy Tag Mobile Legacy Tag
Tag
%WEB_CALL_SETTINGS_BW N/A %WEB_CALL_SETTINGS_BW
A_VISIBLE_WXT% A_VISIBLE%
%WEB_CALL_SETTINGS_CC_ N/A %WEB_CALL_STANDARD_SE
VISIBLE_WXT% TTINGS_CC_VISIBLE%
%WEB_CALL_SETTINGS_BW N/A %WEB_CALL_SETTINGS_BW
M_VISIBLE_WXT% M_VISIBLE%
%WEB_CALL_SETTINGS_VM_ N/A %WEB_CALL_SETTINGS_VM_
VISIBLE_WXT% VISIBLE%
%ENABLE_DIALING_CALL_BA N/A N/A
CK_WXT%
%DIALING_CALL_BACK_TIME N/A N/A
R_WXT%
%ENABLE_EXECUTIVE_ASSI %ENABLE_EXECUTIVE_ASSI N/A
STANT_WXT% STANT_DESKTOP%
%PN_FOR_CALLS_RING_TIM N/A %PN_FOR_CALLS_RING_TIM
EOUT_SECONDS_WXT% EOUT_SECONDS_MOBILE%
%ENABLE_CALL_RECORDIN %ENABLE_CALL_RECORDIN %CALL_RECORDING_MOBILE
G_WXT% G_DESKTOP% %
%ENABLE_SINGLE_ALERTIN N/A %ENABLE_SINGLE_ALERTIN
G_WXT% G%
%ENABLE_CALL_PARK_WXT %ENABLE_CALL_PARK_ N/A
% DESKTOP%
%CALL_PARK_AUTO_CLOSE N/A N/A
_DIALOG_TIMER_WXT%
%ENABLE_RTP_ICE_WXT% N/A N/A
%RTP_ICE_MODE_WXT% N/A N/A
%RTP_ICE_SERVICE_URI_W N/A N/A
XT%
%RTP_ICE_PORT_WXT% N/A N/A
%SIP_REFRESH_ON_TTL_US N/A N/A
E_RANDOM_FACTOR_WXT%
%ENABLE_CALLS_ESCALATE N/A N/A
_TO_WEBEX_MEETING_WXT
%
%ENABLE_DIALING_VOIP_ N/A N/A
WXT%
%ENABLE_DIALING_NATIVE_ N/A N/A
WXT%
%ENABLE_DESKPHONE_CO N/A N/A
NTROL_AUTO_ANSWER_
WXT%
%SIP_URI_DIALING_ENABLE_ N/A N/A
LOCUS_CALLING_WXT%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 97

 Webex for Cisco BroadWorks Desktop Legacy Tag Mobile Legacy Tag
Tag
%ENABLE_UNIFIED_CALL_ N/A N/A
HISTORY_WXT%
%WEB_CALL_SETTINGS_BRA N/A N/A
NDING_ENABLED_WXT%
%USER_PORTAL_SETTINGS_ N/A N/A
URL_WXT%
%ENABLE_DEVICE_OWNER_ N/A N/A
RESTRICTION_WXT%
%ENABLE_AUDIO_MARI_FEC N/A N/A
_WXT%
%ENABLE_AUDIO_MARI_RTX N/A N/A
_WXT%
%ENABLE_VIDEO_MARI_FEC N/A N/A
_WXT%
%ENABLE_VIDEO_MARI_RTX N/A N/A
_WXT%
%ENABLE_CALL_BLOCK_WX N/A N/A
T%
%ENABLE_WIDGET_HOLD_C N/A N/A
ALLS_WXT%
%ENABLE_WIDGET_TRANSF N/A N/A
ER_CALLS_WXT%
%ENABLE_WIDGET_CALLS_E N/A N/A
SCALATE_TO_WEBEX_MEETI
NG_WXT%
%ENABLE_MULTIPLE_CALLS N/A N/A
_PER_USER_WXT%

NOTE: N/A indicates that there was no corresponding custom tag controlling the feature in UC-One. Having N/A
for both Desktop and Mobile Legacy tags indicates that the Webex for Cisco BroadWorks tag is new and controls
either new functionality or an existing feature, that was not controlled through a custom tag in UC-One.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 98

9 Appendix A: TLS Ciphers

The Webex for BroadWorks client uses CiscoSSL, which is based on OpenSSL with additional
security hardening.

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 99

10 Appendix B: DM Tag Provisioning Script

The number of custom DM tags has increased with each release, as many customers prefer tags
for the new configuration parameters. To offer mechanisms for provisioning those custom DM
tags more easily, this section contains a script that can be run on the Application Server (AS) side
to assign values to the custom DM tags. This script is especially intended for new deployments
where most of the custom DM tags are intended to be used.
Note that this script is only valid for new deployments where custom DM tags are being created.
To modify existing custom DM tags, the command in the following script must be changed from
“add” to “set”.
Script template with only a few custom tags set (in a real deployment, you would need to populate
a bigger list of custom tags). Note that the following example is for mobile. For desktop, use the
BroadTouch_tags tag set instead of Connect_Tags. For tablet, use the ConnectTablet_Tags tag
set instead of Connect_Tags.
%% ********************************* Connect_Tags - read file *********************************
%%
%% Instructions:
%% -------------------
%% - This read file can be used to create, add and set Webex for BroadWorks
%% client custom tags
%% - Use %% to comment out any steps not required based on deployment specific
%% service requirements:
%% Step 1 -- for new deployments only, create initial tag set label
%% Step 2 -- add a new custom tag (an entry is required for each new tag)
%% Step 3 -- set value for an existing custom tag (entry required for each applicable tag)
%% Step 4 -- display and visually verify tag settings
%%
%% - Edit, modify file as needed respecting command syntax. Save file (e.g. WxT_Tags.txt)
%% - SFTP read file to AS under directory /tmp
%% - Login to AS, bwcli (login as admin)
%% - Execute the following command from bwcli: AS_CLI> r /tmp/ WxT_Tags.txt
%% - Verify results
%%
%% ----------------------------------------------------------------------------------------------------------------------------
%% Step 1: Create Connect tag set label - Connect_Tags
%% ----------------------------------------------------------------------------------------------------------------------------
quit all;System;DeviceTagSet
add Connect_Tags
%% ----------------------------------------------------------------------------------------------------------------------------
%% Step 2: Add WxT for BWKS custom tags
%% EXAMPLE – for all mobile tags see the list below------------------------------------------------------
quit all;System;DeviceTagSet;Tags
add tagSetName Connect_Tags %ENABLE_TRANSFER_CALLS_WXT% true
%% ----------------------------------------------------------------------------------------------------------------------------
%% Step 3: Set Connect custom tags (if tag already exists)
%% EXAMPLE – for all mobile tags see the list below
set tagSetName Connect_Tags %ENABLE_TRANSFER_CALLS_WXT% isOverridable true
tagvalue false
%% ----------------------------------------------------------------------------------------------------------------------------
%% Step 4: Verify custom tags have been correctly defined and set
%% ----------------------------------------------------------------------------------------------------------------------------
quit all;System;DeviceTagSet;Tags
get tagSetName Connect_Tags
quit all

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 100

The following lists all custom tags used by Webex for Cisco BroadWorks, with example (default or
recommended) values. Note that some of the tags require values specific to the corresponding
deployment (like server addresses). That is why these tags are added at the end of the script but
left empty, and additional set commands should be added to specify them.

10.1 Desktop
add tagSetName BroadTouch_tags %ENABLE_REJECT_WITH_486_WXT% true
add tagSetName BroadTouch_tags %ENABLE_TRANSFER_CALLS_WXT% false
add tagSetName BroadTouch_tags %ENABLE_XSI_TRANSFER_CALLS_WXT% false
add tagSetName BroadTouch_tags %ENABLE_XSI_CONFERENCE_CALLS_WXT% false
add tagSetName BroadTouch_tags %ENABLE_BUSY_LAMP_FIELD_WXT% false
add tagSetName BroadTouch_tags %ENABLE_BLF_DISPLAY_CALLER_WXT% true
add tagSetName BroadTouch_tags %BLF_NOTIFICATION_DELAY_TIME_WXT% 0
add tagSetName BroadTouch_tags %ENABLE_REMOTE_CONTROL_EVENTS_WXT% false
add tagSetName BroadTouch_tags %ENABLE_CALLS_SPAM_INDICATION_WXT% false
add tagSetName BroadTouch_tags %ENABLE_NOISE_REMOVAL_WXT% false
add tagSetName BroadTouch_tags %TRANSFER_CALL_TYPE_WXT% full
add tagSetName BroadTouch_tags %ENABLE_CONFERENCE_CALLS_WXT% false
add tagSetName BroadTouch_tags %ENABLE_NWAY_PARTICIPANT_LIST_WXT% false
add tagSetName BroadTouch_tags %MAX_CONF_PARTIES_WXT% 10
add tagSetName BroadTouch_tags %ENABLE_CALL_STATISTICS_WXT% false
add tagSetName BroadTouch_tags %ENABLE_CALL_PULL_WXT% false
add tagSetName BroadTouch_tags %ENABLE_MWI_WXT% false
add tagSetName BroadTouch_tags %ENABLE_VOICE_MAIL_WXT% false
add tagSetName BroadTouch_tags %ENABLE_VISUAL_VOICE_MAIL_WXT% false
add tagSetName BroadTouch_tags %ENABLE_CALL_FORWARDING_ALWAYS_WXT% false
add tagSetName BroadTouch_tags %ENABLE_BROADWORKS_ANYWHERE_WXT% true
add tagSetName BroadTouch_tags %ENABLE_BROADWORKS_ANYWHERE_DESCRIPTION_WXT% false
add tagSetName BroadTouch_tags %ENABLE_BROADWORKS_ANYWHERE_ALERT_ALL_LOCATIONS_WXT% false
add tagSetName BroadTouch_tags %BROADWORKS_ANYWHERE_ALERT_ALL_LOCATIONS_DEFAULT_WXT% false
add tagSetName BroadTouch_tags %ENABLE_BROADWORKS_ANYWHERE_CALL_CONTROL_WXT% false
add tagSetName BroadTouch_tags %BROADWORKS_ANYWHERE_CALL_CONTROL_DEFAULT_WXT% false
add tagSetName BroadTouch_tags %ENABLE_BROADWORKS_ANYWHERE_DIVERSION_INHIBITOR_WXT% false
add tagSetName BroadTouch_tags %BROADWORKS_ANYWHERE_DIVERSION_INHIBITOR_DEFAULT_WXT% false
add tagSetName BroadTouch_tags %ENABLE_BROADWORKS_ANYWHERE_ANSWER_CONFIRMATION_WXT%
false
add tagSetName BroadTouch_tags %BROADWORKS_ANYWHERE_ANSWER_CONFIRMATION_DEFAULT_WXT%
false
add tagSetName BroadTouch_tags %ENABLE_USE_RPORT_WXT% false
add tagSetName BroadTouch_tags %RPORT_USE_LOCAL_PORT_WXT% false
add tagSetName BroadTouch_tags %USE_TLS_WXT% false
add tagSetName BroadTouch_tags %SBC_PORT_WXT% 5075
add tagSetName BroadTouch_tags %USE_PROXY_DISCOVERY_WXT% false
add tagSetName BroadTouch_tags %USE_TCP_FROM_DNS_WXT% true
add tagSetName BroadTouch_tags %USE_UDP_FROM_DNS_WXT% true
add tagSetName BroadTouch_tags %USE_TLS_FROM_DNS_WXT% true
add tagSetName BroadTouch_tags %PROXY_DISCOVERY_ENABLE_BACKUP_SERVICE_WXT% true
add tagSetName BroadTouch_tags %PROXY_DISCOVERY_ENABLE_SRV_BACKUP_WXT% true
add tagSetName BroadTouch_tags %PROXY_DISCOVERY_BYPASS_OS_CACHE_WXT% false
add tagSetName BroadTouch_tags %SIP_TRANSPORTS_TCP_CONNECT_TIMEOUT_WXT% 5000
add tagSetName BroadTouch_tags %SIP_TRANSPORTS_TLS_CONNECT_TIMEOUT_WXT% 10000
add tagSetName BroadTouch_tags %SOURCE_PORT_WXT% 5060
add tagSetName BroadTouch_tags %USE_ALTERNATIVE_IDENTITIES_WXT% false
add tagSetName BroadTouch_tags %SIP_FAILBACK_ENABLED_WXT% true
add tagSetName BroadTouch_tags %SIP_FAILBACK_TIMEOUT_WXT% 900
add tagSetName BroadTouch_tags %SIP_FAILBACK_USE_RANDOM_FACTOR_WXT% false
add tagSetName BroadTouch_tags %SIP_TRANSPORTS_ENFORCE_IP_VERSION_WXT% dns
add tagSetName BroadTouch_tags %TCP_SIZE_THRESHOLD_WXT% 18000
add tagSetName BroadTouch_tags %SIP_REFRESH_ON_TTL_WXT% false

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 101

 add tagSetName BroadTouch_tags %SIP_REFRESH_ON_TTL_USE_RANDOM_FACTOR_WXT% true
add tagSetName BroadTouch_tags %ENABLE_SIP_UPDATE_SUPPORT_WXT% false
add tagSetName BroadTouch_tags %ENABLE_PEM_SUPPORT_WXT% false
add tagSetName BroadTouch_tags %ENABLE_SIP_SESSION_ID_WXT% false
add tagSetName BroadTouch_tags %ENABLE_FORCE_SIP_INFO_FIR_WXT% false
add tagSetName BroadTouch_tags %SRTP_ENABLED_WXT% false
add tagSetName BroadTouch_tags %SRTP_MODE_WXT% false
add tagSetName BroadTouch_tags %ENABLE_REKEYING_WXT% true
add tagSetName BroadTouch_tags %RTP_AUDIO_PORT_RANGE_START_WXT% 8000
add tagSetName BroadTouch_tags %RTP_AUDIO_PORT_RANGE_END_WXT% 8099
add tagSetName BroadTouch_tags %RTP_VIDEO_PORT_RANGE_START_WXT% 8100
add tagSetName BroadTouch_tags %RTP_VIDEO_PORT_RANGE_END_WXT% 8199
add tagSetName BroadTouch_tags %ENABLE_RTCP_MUX_WXT% true
add tagSetName BroadTouch_tags %ENABLE_XSI_EVENT_CHANNEL_WXT% true
add tagSetName BroadTouch_tags %CHANNEL_HEARTBEAT_WXT% 10000
add tagSetName BroadTouch_tags %XSI_ACTIONS_PATH_WXT% /com.broadsoft.xsi-actions/
add tagSetName BroadTouch_tags %XSI_EVENTS_PATH_WXT% /com.broadsoft.xsi-events/
add tagSetName BroadTouch_tags %ENABLE_CALLS_AUTO_RECOVERY_WXT% true
add tagSetName BroadTouch_tags %USE_MEDIASEC_WXT% false
add tagSetName BroadTouch_tags %ENABLE_SCREEN_SHARE_WXT% true
add tagSetName BroadTouch_tags %ENABLE_CALL_CENTER_WXT% false
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_TARGET_WXT% external
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_CFA_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_CFB_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_CFNR_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_CFNA_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_DND_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_ACR_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_SIMRING_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_SEQRING_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_ACB_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_CW_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_CLIDB_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_PA_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_CC_VISIBLE_WXT% false
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_BWA_VISIBLE_WXT% false
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_BWM_VISIBLE_WXT% false
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_RO_VISIBLE_WXT% false
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_VM_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_BRANDING_ENABLED_WXT% false
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_EMAIL_VM_VISIBLE_WXT% true
add tagSetName BroadTouch_tags %USER_PORTAL_SETTINGS_URL_WXT%
add tagSetName BroadTouch_tags %USER_PORTAL_SETTINGS_TARGET_WXT% external
add tagSetName BroadTouch_tags %USER_PORTAL_SETTINGS_SSO_ENABLED_WXT% false
add tagSetName BroadTouch_tags %ENABLE_CALL_PICKUP_BLIND_WXT% false
add tagSetName BroadTouch_tags %ENABLE_CALL_PICKUP_DIRECTED_WXT% false
add tagSetName BroadTouch_tags %ENABLE_SIP_VIDEOCALLS_WXT% true
add tagSetName BroadTouch_tags %ENABLE_LOCUS_VIDEOCALLS_WXT% true
add tagSetName BroadTouch_tags %VIDEOCALLS_ANSWER_WITH_VIDEO_ON_DEFAULT_WXT% true
add tagSetName BroadTouch_tags %EMERGENCY_DIALING_ENABLE_REDSKY_WXT% false
add tagSetName BroadTouch_tags %EMERGENCY_REDSKY_USER_REMINDER_TIMEOUT_WXT% 0
add tagSetName BroadTouch_tags %EMERGENCY_REDSKY_USER_MANDATORY_LOCATION_WXT% -1
add tagSetName BroadTouch_tags %EMERGENCY_REDSKY_USER_LOCATION_PROMPTING_WXT%
once_per_login
add tagSetName BroadTouch_tags %ENABLE_FORCED_LOGOUT_WXT% false
add tagSetName BroadTouch_tags %ENABLE_EXECUTIVE_ASSISTANT_WXT% false
add tagSetName BroadTouch_tags %ENABLE_CALL_RECORDING_WXT% false
add tagSetName BroadTouch_tags %ENABLE_CALL_PARK_WXT% false
add tagSetName BroadTouch_tags %CALL_PARK_AUTO_CLOSE_DIALOG_TIMER_WXT% 10
add tagSetName BroadTouch_tags %ENABLE_CALLS_ESCALATE_TO_WEBEX_MEETING_WXT% false
add tagSetName BroadTouch_tags %ENABLE_DESKPHONE_CONTROL_AUTO_ANSWER_WXT% true

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 102

 add tagSetName BroadTouch_tags %ENABLE_RTP_ICE_WXT% false
add tagSetName BroadTouch_tags %RTP_ICE_MODE_WXT% icestun
add tagSetName BroadTouch_tags %RTP_ICE_PORT_WXT% 3478
add tagSetName BroadTouch_tags %SIP_URI_DIALING_ENABLE_LOCUS_CALLING_WXT% true
add tagSetName BroadTouch_tags %ENABLE_UNIFIED_CALL_HISTORY_WXT% false
add tagSetName BroadTouch_tags %RTP_ICE_SERVICE_URI_WXT% true
add tagSetName BroadTouch_tags %FORCED_LOGOUT_APPID_WXT% true
add tagSetName BroadTouch_tags %XSI_ROOT_WXT% true
add tagSetName BroadTouch_tags %SBC_ADDRESS_WXT% true
add tagSetName BroadTouch_tags %SBC_PORT_WXT% true
add tagSetName BroadTouch_tags %MWI_MODE_WXT% true
add tagSetName BroadTouch_tags %ENABLE_VOICE_MAIL_TRANSCRIPTION_WXT% false
add tagSetName BroadTouch_tags %WEB_CALL_SETTINGS_URL_WXT% true
add tagSetName BroadTouch_tags %DOMAIN_OVERRIDE_WXT% true
add tagSetName BroadTouch_tags %ENABLE_AUTO_ANSWER_WXT% false
add tagSetName BroadTouch_tags %USE_PAI_AS_CALLING_IDENTITY_WXT% false
add tagSetName BroadTouch_tags %ENABLE_CALL_CENTER_AGENT_OUTGOING_CALLS_WXT% false
add tagSetName BroadTouch_tags %ENABLE_MULTI_LINE_WXT%false
add tagSetName BroadTouch_tags %ENABLE_AUDIO_QOS_WXT% true
add tagSetName BroadTouch_tags %AUDIO_QOS_VALUE_WXT% 46
add tagSetName BroadTouch_tags %ENABLE_VIDEO_QOS_WXT% true
add tagSetName BroadTouch_tags %VIDEO_QOS_VALUE_WXT% 34
add tagSetName BroadTouch_tags %ENABLE_DEVICE_OWNER_RESTRICTION_WXT% true
add tagSetName BroadTouch_tags %ENABLE_AUDIO_MARI_FEC_WXT% false
add tagSetName BroadTouch_tags %ENABLE_AUDIO_MARI_RTX_WXT% false
add tagSetName BroadTouch_tags %ENABLE_VIDEO_MARI_FEC_WXT% false
add tagSetName BroadTouch_tags %ENABLE_VIDEO_MARI_RTX_WXT% false
add tagSetName BroadTouch_tags %ENABLE_CALL_BLOCK_WXT% false
add tagSetName BroadTouch_tags %ENABLE_MULTIPLE_CALLS_PER_USER_WXT% false

10.2 Mobile
add tagSetName Connect_Tags %ENABLE_REJECT_WITH_486_WXT% true
add tagSetName Connect_Tags %ENABLE_TRANSFER_CALLS_WXT% false
add tagSetName Connect_Tags %ENABLE_CALLS_SPAM_INDICATION_WXT% false
add tagSetName Connect_Tags %ENABLE_NOISE_REMOVAL_WXT% false
add tagSetName Connect_Tags %TRANSFER_CALL_TYPE_WXT% full
add tagSetName Connect_Tags %ENABLE_XSI_TRANSFER_CALLS_WXT% false
add tagSetName Connect_Tags %ENABLE_CONFERENCE_CALLS_WXT% false
add tagSetName Connect_Tags %ENABLE_NWAY_PARTICIPANT_LIST_WXT% false
add tagSetName Connect_Tags %MAX_CONF_PARTIES_WXT% 10
add tagSetName Connect_Tags %ENABLE_CALL_STATISTICS_WXT% false
add tagSetName Connect_Tags %ENABLE_CALL_PULL_WXT% false
add tagSetName Connect_Tags %ENABLE_MWI_WXT% false
add tagSetName Connect_Tags %ENABLE_VOICE_MAIL_WXT% false
add tagSetName Connect_Tags %ENABLE_VISUAL_VOICE_MAIL_WXT% false
add tagSetName Connect_Tags %ENABLE_CALL_FORWARDING_ALWAYS_WXT% false
add tagSetName Connect_Tags %ENABLE_BROADWORKS_ANYWHERE_WXT% true
add tagSetName Connect_Tags %ENABLE_BROADWORKS_ANYWHERE_DESCRIPTION_WXT% false
add tagSetName Connect_Tags %ENABLE_BROADWORKS_ANYWHERE_ALERT_ALL_LOCATIONS_WXT% false
add tagSetName Connect_Tags %BROADWORKS_ANYWHERE_ALERT_ALL_LOCATIONS_DEFAULT_WXT% false
add tagSetName Connect_Tags %ENABLE_BROADWORKS_ANYWHERE_CALL_CONTROL_WXT% false
add tagSetName Connect_Tags %BROADWORKS_ANYWHERE_CALL_CONTROL_DEFAULT_WXT% false
add tagSetName Connect_Tags %ENABLE_BROADWORKS_ANYWHERE_DIVERSION_INHIBITOR_WXT% false
add tagSetName Connect_Tags %BROADWORKS_ANYWHERE_DIVERSION_INHIBITOR_DEFAULT_WXT% false
add tagSetName Connect_Tags %ENABLE_BROADWORKS_ANYWHERE_ANSWER_CONFIRMATION_WXT% false
add tagSetName Connect_Tags %BROADWORKS_ANYWHERE_ANSWER_CONFIRMATION_DEFAULT_WXT% false
add tagSetName Connect_Tags %ENABLE_USE_RPORT_WXT% false
add tagSetName Connect_Tags %RPORT_USE_LOCAL_PORT_WXT% false
add tagSetName Connect_Tags %USE_TLS_WXT% false

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 103

 add tagSetName Connect_Tags %SBC_PORT_WXT% 5075
add tagSetName Connect_Tags %USE_PROXY_DISCOVERY_WXT% false
add tagSetName Connect_Tags %USE_TCP_FROM_DNS_WXT% true
add tagSetName Connect_Tags %USE_UDP_FROM_DNS_WXT% true
add tagSetName Connect_Tags %USE_TLS_FROM_DNS_WXT% true
add tagSetName Connect_Tags %PROXY_DISCOVERY_ENABLE_BACKUP_SERVICE_WXT% true
add tagSetName Connect_Tags %PROXY_DISCOVERY_ENABLE_SRV_BACKUP_WXT% true
add tagSetName Connect_Tags %SIP_TRANSPORTS_TCP_CONNECT_TIMEOUT_WXT% 5000
add tagSetName Connect_Tags %SIP_TRANSPORTS_TLS_CONNECT_TIMEOUT_WXT% 10000
add tagSetName Connect_Tags %SOURCE_PORT_WXT% 5060
add tagSetName Connect_Tags %USE_ALTERNATIVE_IDENTITIES_WXT% false
add tagSetName Connect_Tags %SIP_TRANSPORTS_ENFORCE_IP_VERSION_WXT% dns
add tagSetName Connect_Tags %TCP_SIZE_THRESHOLD_WXT% 18000
add tagSetName Connect_Tags %ENABLE_SIP_UPDATE_SUPPORT_WXT% false
add tagSetName Connect_Tags %ENABLE_PEM_SUPPORT_WXT% false
add tagSetName Connect_Tags %ENABLE_SIP_SESSION_ID_WXT% false
add tagSetName Connect_Tags %ENABLE_FORCE_SIP_INFO_FIR_WXT% false
add tagSetName Connect_Tags %SRTP_ENABLED_WXT% false
add tagSetName Connect_Tags %SRTP_MODE_WXT% false
add tagSetName Connect_Tags %ENABLE_REKEYING_WXT% true
add tagSetName Connect_Tags %RTP_AUDIO_PORT_RANGE_START_WXT% 8000
add tagSetName Connect_Tags %RTP_AUDIO_PORT_RANGE_END_WXT% 8099
add tagSetName Connect_Tags %RTP_VIDEO_PORT_RANGE_START_WXT% 8100
add tagSetName Connect_Tags %RTP_VIDEO_PORT_RANGE_END_WXT% 8199
add tagSetName Connect_Tags %ENABLE_RTCP_MUX_WXT% true
add tagSetName Connect_Tags %ENABLE_XSI_EVENT_CHANNEL_WXT% true
add tagSetName Connect_Tags %CHANNEL_HEARTBEAT_WXT% 10000
add tagSetName Connect_Tags %XSI_ACTIONS_PATH_WXT% /com.broadsoft.xsi-actions/
add tagSetName Connect_Tags %XSI_EVENTS_PATH_WXT% /com.broadsoft.xsi-events/
add tagSetName Connect_Tags %ENABLE_CALLS_AUTO_RECOVERY_WXT% true
add tagSetName Connect_Tags %USE_MEDIASEC_WXT% false
add tagSetName Connect_Tags %ENABLE_SCREEN_SHARE_WXT% true
add tagSetName Connect_Tags %ENABLE_CALL_CENTER_WXT% false
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_TARGET_WXT% external
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_CFA_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_CFB_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_CFNR_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_CFNA_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_DND_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_ACR_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_SIMRING_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_SEQRING_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_ACB_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_CW_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_CLIDB_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_PA_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_CC_VISIBLE_WXT% false
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_BWA_VISIBLE_WXT% false
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_BWM_VISIBLE_WXT% false
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_RO_VISIBLE_WXT% false
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_VM_VISIBLE_WXT% true
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_BRANDING_ENABLED_WXT% false
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_EMAIL_VM_VISIBLE_WXT% true
add tagSetName Connect_Tags %USER_PORTAL_SETTINGS_URL_WXT% true
add tagSetName Connect_Tags %USER_PORTAL_SETTINGS_TARGET_WXT% external
add tagSetName Connect_tags %USER_PORTAL_SETTINGS_SSO_ENABLED_WXT% false
add tagSetName Connect_Tags %ENABLE_EMERGENCY_DIALING_WXT% false
add tagSetName Connect_Tags %EMERGENCY_CALL_DIAL_SEQUENCE_WXT% cs-only
add tagSetName Connect_Tags %EMERGENCY_DIALING_NUMBERS_WXT% 911,112
add tagSetName Connect_Tags %PN_FOR_CALLS_CONNECT_SIP_ON_ACCEPT_WXT% false
add tagSetName Connect_Tags %REJECT_WITH_XSI_MODE_WXT% decline_false

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 104

 add tagSetName Connect_Tags %REJECT_WITH_XSI_DECLINE_REASON_WXT% busy
add tagSetName Connect_Tags %ENABLE_DIALING_CALL_BACK_WXT% false
add tagSetName Connect_Tags %DIALING_CALL_BACK_TIMER_WXT% 10
add tagSetName Connect_Tags %ENABLE_CALL_RECORDING_WXT% false
add tagSetName Connect_Tags %PN_FOR_CALLS_RING_TIMEOUT_SECONDS_WXT% 35
add tagSetName Connect_Tags %ENABLE_SINGLE_ALERTING_WXT% false
add tagSetName Connect_Tags %ENABLE_CALL_PARK_WXT% false
add tagSetName Connect_Tags %CALL_PARK_AUTO_CLOSE_DIALOG_TIMER_WXT% 10
add tagSetName Connect_Tags %ENABLE_RTP_ICE_WXT% false
add tagSetName Connect_Tags %RTP_ICE_MODE_WXT% icestun
add tagSetName Connect_Tags %SIP_URI_DIALING_ENABLE_LOCUS_CALLING_WXT% true
add tagSetName Connect_Tags %RTP_ICE_PORT_WXT% 3478
add tagSetName Connect_Tags %ENABLE_DIALING_VOIP_WXT% true
add tagSetName Connect_Tags %ENABLE_DIALING_NATIVE_WXT% false
add tagSetName Connect_Tags %ENABLE_DIALING_MODE_WXT% true
add tagSetName Connect_Tags %DIALING_MODE_DEFAULT_WXT% true
add tagSetName Connect_Tags %DIALING_NATIVE_ENABLE_BWKS_MOBILITY_DEPENDENCY_WXT% false
add tagSetName Connect_Tags %ENABLE_XSI_CALL_CONTROL_WXT% false
add tagSetName Connect_Tags %XSI_CALL_CONTROL_DEPLOYMENT_TYPE_WXT% MNO_Access
add tagSetName Connect_Tags %DEPLOYMENT_DEVICE_TYPE_1_WXT% true
add tagSetName Connect_Tags %DEPLOYMENT_DEVICE_TYPE_2_WXT% true
add tagSetName Connect_Tags %DEPLOYMENT_DEVICE_TYPE_3_WXT% true
add tagSetName Connect_Tags %ENABLE_XSI_HOLD_CALLS_WXT% true
add tagSetName Connect_Tags %ENABLE_CALLS_ESCALATE_TO_WEBEX_MEETING_WXT% false
add tagSetName Connect_Tags %ENABLE_UNIFIED_CALL_HISTORY_WXT% false
add tagSetName Connect_Tags %RTP_ICE_SERVICE_URI_WXT% true
add tagSetName Connect_Tags %XSI_ROOT_WXT% true
add tagSetName Connect_Tags %SBC_ADDRESS_WXT% true
add tagSetName Connect_Tags %SBC_PORT_WXT% true
add tagSetName Connect_Tags %MWI_MODE_WXT% true
add tagSetName Connect_Tags %ENABLE_VOICE_MAIL_TRANSCRIPTION_WXT% false
add tagSetName Connect_Tags %WEB_CALL_SETTINGS_URL_WXT% true
add tagSetName Connect_Tags %DOMAIN_OVERRIDE_WXT% true
add tagSetName Connect_Tags %ENABLE_SIP_VIDEOCALLS_WXT% true
add tagSetName Connect_Tags %ENABLE_LOCUS_VIDEOCALLS_WXT% true
add tagSetName Connect_Tags %VIDEOCALLS_ANSWER_WITH_VIDEO_ON_DEFAULT_WXT% false
add tagSetName Connect_Tags %EMERGENCY_DIALING_ENABLE_REDSKY_WXT% false
add tagSetName Connect_Tags %EMERGENCY_REDSKY_USER_REMINDER_TIMEOUT_WXT% 0
add tagSetName Connect_Tags %EMERGENCY_REDSKY_USER_MANDATORY_LOCATION_WXT% -1
add tagSetName Connect_Tags %EMERGENCY_REDSKY_USER_LOCATION_PROMPTING_WXT% once_per_login
add tagSetName Connect_Tags %USE_PAI_AS_CALLING_IDENTITY_WXT% false
add tagSetName Connect_Tags %ENABLE_CLID_DELIVERY_BLOCKING_WXT% false
add tagSetName Connect_Tags %ENABLE_MOBILITY_PERSONA_MANAGEMENT_WXT% false
add tagSetName Connect_Tags %ENABLE_RING_SPLASH_WXT% false
add tagSetName Connect_Tags %ENABLE_PN_MOBILE_CALL_INFO_WXT% true
add tagSetName Connect_Tags %ENABLE_AUDIO_QOS_WXT% true
add tagSetName Connect_Tags %AUDIO_QOS_VALUE_WXT% 46
add tagSetName Connect_Tags %ENABLE_VIDEO_QOS_WXT% true
add tagSetName Connect_Tags %VIDEO_QOS_VALUE_WXT% 34
add tagSetName Connect_Tags %ENABLE_DEVICE_OWNER_RESTRICTION_WXT% true
add tagSetName Connect_Tags %ENABLE_AUDIO_MARI_FEC_WXT% false
add tagSetName Connect_Tags %ENABLE_AUDIO_MARI_RTX_WXT% false
add tagSetName Connect_Tags %ENABLE_VIDEO_MARI_FEC_WXT% false
add tagSetName Connect_Tags %ENABLE_VIDEO_MARI_RTX_WXT% false
add tagSetName Connect_Tags %ENABLE_CALL_BLOCK_WXT% false
add tagSetName Connect_Tags %ENABLE_WIDGET_HOLD_CALLS_WXT% true
add tagSetName Connect_Tags %ENABLE_WIDGET_TRANSFER_CALLS_WXT% true
add tagSetName Connect_Tags %ENABLE_WIDGET_CALLS_ESCALATE_TO_WEBEX_MEETING_WXT% true
add tagSetName Connect_Tags %ENABLE_MULTIPLE_CALLS_PER_USER_WXT% false

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 105

 10.3 Tablet
add tagSetName ConnectTablet_Tags %ENABLE_REJECT_WITH_486_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_TRANSFER_CALLS_WXT% false
add tagSetName ConnectTablet_Tags %TRANSFER_CALL_TYPE_WXT% full
add tagSetName ConnectTablet_Tags %ENABLE_XSI_TRANSFER_CALLS_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_CALLS_SPAM_INDICATION_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_NOISE_REMOVAL_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_CONFERENCE_CALLS_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_NWAY_PARTICIPANT_LIST_WXT% false
add tagSetName ConnectTablet_Tags %MAX_CONF_PARTIES_WXT% 10
add tagSetName ConnectTablet_Tags %ENABLE_CALL_STATISTICS_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_CALL_PULL_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_MWI_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_VOICE_MAIL_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_VISUAL_VOICE_MAIL_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_CALL_FORWARDING_ALWAYS_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_BROADWORKS_ANYWHERE_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_BROADWORKS_ANYWHERE_DESCRIPTION_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_BROADWORKS_ANYWHERE_ALERT_ALL_LOCATIONS_WXT%
false
add tagSetName ConnectTablet_Tags %BROADWORKS_ANYWHERE_ALERT_ALL_LOCATIONS_DEFAULT_WXT%
false
add tagSetName ConnectTablet_Tags %ENABLE_BROADWORKS_ANYWHERE_CALL_CONTROL_WXT% false
add tagSetName ConnectTablet_Tags %BROADWORKS_ANYWHERE_CALL_CONTROL_DEFAULT_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_BROADWORKS_ANYWHERE_DIVERSION_INHIBITOR_WXT% false
add tagSetName ConnectTablet_Tags %BROADWORKS_ANYWHERE_DIVERSION_INHIBITOR_DEFAULT_WXT%
false
add tagSetName ConnectTablet_Tags %ENABLE_BROADWORKS_ANYWHERE_ANSWER_CONFIRMATION_WXT%
false
add tagSetName ConnectTablet_Tags %BROADWORKS_ANYWHERE_ANSWER_CONFIRMATION_DEFAULT_WXT%
false
add tagSetName ConnectTablet_Tags %ENABLE_USE_RPORT_WXT% false
add tagSetName ConnectTablet_Tags %RPORT_USE_LOCAL_PORT_WXT% false
add tagSetName ConnectTablet_Tags %USE_TLS_WXT% false
add tagSetName ConnectTablet_Tags %SBC_PORT_WXT% 5075
add tagSetName ConnectTablet_Tags %USE_PROXY_DISCOVERY_WXT% false
add tagSetName ConnectTablet_Tags %USE_TCP_FROM_DNS_WXT% true
add tagSetName ConnectTablet_Tags %USE_UDP_FROM_DNS_WXT% true
add tagSetName ConnectTablet_Tags %USE_TLS_FROM_DNS_WXT% true
add tagSetName ConnectTablet_Tags %SIP_TRANSPORTS_TCP_CONNECT_TIMEOUT_WXT% 5000
add tagSetName ConnectTablet_Tags %SIP_TRANSPORTS_TLS_CONNECT_TIMEOUT_WXT% 10000
add tagSetName ConnectTablet_Tags %PROXY_DISCOVERY_ENABLE_BACKUP_SERVICE_WXT% true
add tagSetName ConnectTablet_Tags %PROXY_DISCOVERY_ENABLE_SRV_BACKUP_WXT% true
add tagSetName ConnectTablet_Tags %SOURCE_PORT_WXT% 5060
add tagSetName ConnectTablet_Tags %USE_ALTERNATIVE_IDENTITIES_WXT% false
add tagSetName ConnectTablet_Tags %SIP_TRANSPORTS_ENFORCE_IP_VERSION_WXT% dns
add tagSetName ConnectTablet_Tags %TCP_SIZE_THRESHOLD_WXT% 18000
add tagSetName ConnectTablet_Tags %ENABLE_SIP_UPDATE_SUPPORT_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_PEM_SUPPORT_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_SIP_SESSION_ID_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_FORCE_SIP_INFO_FIR_WXT% false
add tagSetName ConnectTablet_Tags %SRTP_ENABLED_WXT% false
add tagSetName ConnectTablet_Tags %SRTP_MODE_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_REKEYING_WXT% true
add tagSetName ConnectTablet_Tags %RTP_AUDIO_PORT_RANGE_START_WXT% 8000
add tagSetName ConnectTablet_Tags %RTP_AUDIO_PORT_RANGE_END_WXT% 8099
add tagSetName ConnectTablet_Tags %RTP_VIDEO_PORT_RANGE_START_WXT% 8100
add tagSetName ConnectTablet_Tags %RTP_VIDEO_PORT_RANGE_END_WXT% 8199
add tagSetName ConnectTablet_Tags %ENABLE_RTCP_MUX_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_XSI_EVENT_CHANNEL_WXT% true

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 106

 add tagSetName ConnectTablet_Tags %CHANNEL_HEARTBEAT_WXT% 10000
add tagSetName ConnectTablet_Tags %XSI_ACTIONS_PATH_WXT% /com.broadsoft.xsi-actions/
add tagSetName ConnectTablet_Tags %XSI_EVENTS_PATH_WXT% /com.broadsoft.xsi-events/
add tagSetName ConnectTablet_Tags %ENABLE_CALLS_AUTO_RECOVERY_WXT% true
add tagSetName ConnectTablet_Tags %USE_MEDIASEC_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_SCREEN_SHARE_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_CALL_CENTER_WXT% false
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_TARGET_WXT% external
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_CFA_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_CFB_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_CFNR_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_CFNA_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_DND_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_ACR_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_SIMRING_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_SEQRING_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_ACB_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_CW_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_CLIDB_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_PA_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_CC_VISIBLE_WXT% false
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_BWA_VISIBLE_WXT% false
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_BWM_VISIBLE_WXT% false
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_RO_VISIBLE_WXT% false
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_VM_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_BRANDING_ENABLED_WXT% false
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_EMAIL_VM_VISIBLE_WXT% true
add tagSetName ConnectTablet_Tags %USER_PORTAL_SETTINGS_URL_WXT% true
add tagSetName ConnectTablet_Tags %USER_PORTAL_SETTINGS_TARGET_WXT% external
add tagSetName ConnectTablet_Tags %USER_PORTAL_SETTINGS_SSO_ENABLED_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_EMERGENCY_DIALING_WXT% false
add tagSetName ConnectTablet_Tags %EMERGENCY_CALL_DIAL_SEQUENCE_WXT% cs-only
add tagSetName ConnectTablet_Tags %EMERGENCY_DIALING_NUMBERS_WXT% 911,112
add tagSetName ConnectTablet_Tags %PN_FOR_CALLS_CONNECT_SIP_ON_ACCEPT_WXT% false
add tagSetName ConnectTablet_Tags %REJECT_WITH_XSI_MODE_WXT% decline_false
add tagSetName ConnectTablet_Tags %REJECT_WITH_XSI_DECLINE_REASON_WXT% busy
add tagSetName ConnectTablet_Tags %ENABLE_DIALING_CALL_BACK_WXT% false
add tagSetName ConnectTablet_Tags %DIALING_CALL_BACK_TIMER_WXT% 10
add tagSetName ConnectTablet_Tags %ENABLE_CALL_RECORDING_WXT% false
add tagSetName ConnectTablet_Tags %PN_FOR_CALLS_RING_TIMEOUT_SECONDS_WXT% 35
add tagSetName ConnectTablet_Tags %ENABLE_SINGLE_ALERTING_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_CALL_PARK_WXT% false
add tagSetName ConnectTablet_Tags %CALL_PARK_AUTO_CLOSE_DIALOG_TIMER_WXT% 10
add tagSetName ConnectTablet_Tags %ENABLE_RTP_ICE_WXT% false
add tagSetName ConnectTablet_Tags %RTP_ICE_MODE_WXT% icestun
add tagSetName ConnectTablet_Tags %SIP_URI_DIALING_ENABLE_LOCUS_CALLING_WXT% true
add tagSetName ConnectTablet_Tags %RTP_ICE_PORT_WXT% 3478
add tagSetName ConnectTablet_Tags %ENABLE_DIALING_VOIP_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_DIALING_NATIVE_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_DIALING_MODE_WXT% true
add tagSetName ConnectTablet_Tags %DIALING_MODE_DEFAULT_WXT% true
add tagSetName ConnectTablet_Tags %DIALING_NATIVE_ENABLE_BWKS_MOBILITY_DEPENDENCY_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_XSI_CALL_CONTROL_WXT% false
add tagSetName ConnectTablet_Tags %XSI_CALL_CONTROL_DEPLOYMENT_TYPE_WXT% MNO_Access
add tagSetName ConnectTablet_Tags %DEPLOYMENT_DEVICE_TYPE_1_WXT% true
add tagSetName ConnectTablet_Tags %DEPLOYMENT_DEVICE_TYPE_2_WXT% true
add tagSetName ConnectTablet_Tags %DEPLOYMENT_DEVICE_TYPE_3_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_XSI_HOLD_CALLS_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_CALLS_ESCALATE_TO_WEBEX_MEETING_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_UNIFIED_CALL_HISTORY_WXT% false
add tagSetName ConnectTablet_Tags %RTP_ICE_SERVICE_URI_WXT% true

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 107

 add tagSetName ConnectTablet_Tags %XSI_ROOT_WXT% true
add tagSetName ConnectTablet_Tags %SBC_ADDRESS_WXT% true
add tagSetName ConnectTablet_Tags %SBC_PORT_WXT% true
add tagSetName ConnectTablet_Tags %MWI_MODE_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_VOICE_MAIL_TRANSCRIPTION_WXT% false
add tagSetName ConnectTablet_Tags %WEB_CALL_SETTINGS_URL_WXT% true
add tagSetName ConnectTablet_Tags %DOMAIN_OVERRIDE_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_SIP_VIDEOCALLS_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_LOCUS_VIDEOCALLS_WXT% true
add tagSetName ConnectTablet_Tags %VIDEOCALLS_ANSWER_WITH_VIDEO_ON_DEFAULT_WXT% false
add tagSetName ConnectTablet_Tags %EMERGENCY_DIALING_ENABLE_REDSKY_WXT% false
add tagSetName ConnectTablet_Tags %EMERGENCY_REDSKY_USER_REMINDER_TIMEOUT_WXT% 0
add tagSetName ConnectTablet_Tags %EMERGENCY_REDSKY_USER_MANDATORY_LOCATION_WXT% -1
add tagSetName ConnectTablet_Tags %EMERGENCY_REDSKY_USER_LOCATION_PROMPTING_WXT%
once_per_login
add tagSetName ConnectTablet_Tags %USE_PAI_AS_CALLING_IDENTITY_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_RING_SPLASH_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_PN_MOBILE_CALL_INFO_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_AUDIO_QOS_WXT% true
add tagSetName ConnectTablet_Tags %AUDIO_QOS_VALUE_WXT% 46
add tagSetName ConnectTablet_Tags %ENABLE_VIDEO_QOS_WXT% true
add tagSetName ConnectTablet_Tags %VIDEO_QOS_VALUE_WXT% 34
add tagSetName ConnectTablet_Tags %ENABLE_DEVICE_OWNER_RESTRICTION_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_AUDIO_MARI_FEC_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_AUDIO_MARI_RTX_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_VIDEO_MARI_FEC_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_VIDEO_MARI_RTX_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_CALL_BLOCK_WXT% false
add tagSetName ConnectTablet_Tags %ENABLE_WIDGET_HOLD_CALLS_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_WIDGET_TRANSFER_CALLS_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_WIDGET_CALLS_ESCALATE_TO_WEBEX_MEETING_WXT% true
add tagSetName ConnectTablet_Tags %ENABLE_MULTIPLE_CALLS_PER_USER_WXT% false

10.4 System Tags

The following lists the system tags used by Webex for BroadWorks.
%BWNETWORK-CONFERENCE-SIPURI-x%
%BWVOICE-PORTAL-NUMBER-x%
%BWLINEPORT-x%
%BWHOST-x%
%BWAUTHUSER-x%
%BWAUTHPASSWORD-x%
%BWE164-x%
%BWNAME-x%
%BWEXTENSION-x%
%BWAPPEARANCE-LABEL-x%
%BWDISPLAYNAMELINEPORT%
%BWLINEPORT-PRIMARY%
%BWE911-PRIMARY-HELDURL%
%BWE911-CUSTOMERID%
%BWE911-SECRETKEY%
%BWE911-EMERGENCY-NUMBER-LIST%
%BW-MEMBERTYPE-X%
%BWUSEREXTID-X%

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 108

11 Acronyms and Abbreviations

This section lists the acronyms and abbreviations found in this document. The acronyms and
abbreviations are listed in alphabetical order along with their meanings.
ACB Automatic Callback
ACD Automatic Call Distribution
ACR Anonymous Call Rejection
AES Advanced Encryption Standard
ALG Application Layer Gateway
API Application Programming Interface
APK Application Package
APNS Apple Push Notification Service
ARS Automatic bit Rate Selection
AS Application Server (Cisco BroadWorks)
AVP Audio Visual Profile
BW BroadWorks
BWA BroadWorks Anywhere
BWKS BroadWorks
BWM BroadWorks Mobility
BYOD Bring Your Own Device
CC Call Center
CFB Call Forwarding Busy
CFNA Call Forwarding No Answer
CFNR Call Forwarding Not Reachable
CIF Common Intermediate Format
CLI Command Line Interface
CLID Calling Line Identity
CLIDB Calling Line ID Delivery Blocking
CRLF Carriage Return Line Feed
CS Circuit-Switched
CSWV Call Settings Web View
CW Call Waiting
DB Database
DM Device Management
DND Do Not Disturb
DNS Domain Name System

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 109

DPC Desk Phone Control
DTAF Device Type Archive File
ECACS Emergency Call Address Change Service
FMC Fixed-Mobile Convergence
FQDN Fully Qualified Domain Name
HMAC Hash Message Authentication Code
ICE Interactive Connectivity Establishment
iLBC internet Low Bitrate Codec
IM Instant Messaging
IM&P Instant Messaging and Presence
IOT Interoperability Testing
IP Internet Protocol
JID Jabber Identifier
M/O Mandatory/Optional
MNO Mobile Network Operator
MTU Maximum Transmission Unit
MUC Multi-User Chat
MWI Message Waiting Indicator
NAL Network Abstraction Layer
NAPTR Naming Authority Pointer
NAT Network Address Translation
OTT Over The Top
PA Personal Assistant
PAI P-Asserted-Identity
PEM P-Early Media
PLI Picture Loss Indication
PLMN Public Land Mobile Network
PN Push Notification
QCIF Quarter Common Intermediate Format
QoS Quality of Service
RO Remote Office
RTCP Real-Time Control Protocol
RTP Real Time Protocol
SaaS Software as a Service
SAN Subject Alternative Name
SASL Simple Authentication and Security Layer

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 110

SAVP Secure Audio Video Profile
SBC Session Border Controller
SCA Shared Call Appearance
SCF Session Continuity Function
SCTP Stream Control Transmission Protocol
SDP Session Definition Protocol
SEQRING Sequential Ring
SIMRING Simultaneous Ring
SIP Session Initiation Protocol
SNR Signal to Noise Ratio
SNR Single Number Reach
SRTCP Secure Real-Time Control Protocol
SRTP Secure Real-time Transport Protocol
SSL Secure Sockets Layer
STUN Session Traversal Utilities for NAT
SUBQCIF Sub Quarter CIF
TCP Transmission Control Protocol
TLS Transport Layer Security
TTL Time To Live
TURN Traversal Using Relay NAT
UDP User Datagram Protocol
UI User Interface
UMS Messaging Server (Cisco BroadWorks)
URI Uniform Resource Identifier
UVS Video Server (Cisco BroadWorks)
VGA Video Graphics Array
VoIP Voice Over IP
VVM Visual Voicemail
WXT Webex
XMPP Extensible Messaging and Presence Protocol
XR Extended Report
Xsp Xtended Services Platform
Xsi Xtended Services Interface

WEBEX FOR CISCO BROADWORKS CONFIGURATION GUIDE PAGE 111