Table of Contents
Advertisement
13 - 10 CA50/UCA Client & Server Developer & User Guide
Planning PBX Integration
The CA50 must be assigned a phone extension. This requires the UCA server to be seeded with extensions that
can be assigned to users at login time. In addition, the UCA server must be seeded with all phone numbers that an
associate would need to call from a CA50.
Prepping the phone extension pool and additional phone book entries is a multi-step process:
Identify all extensions that are currently in use for desk phones, wall phones, etc.
1.
Identify available extensions (new or unused) that can be placed into the phone extension pool.
2.
Adjust call coverage groups and call rollover groups to include the extensions in the pool.
3.
Associate the phone extensions in the pool with the appropriate groups for assignment when an associate logs
4.
in, and for display in the phone book.
NOTE An external application can be developed to use the Phone Extension Web Service to update the UCA
server as part of the customer's process for maintaining the PBX.
Developing User Profile Templates and Associations
The user profile templates define access rights and privileges for various associates who use the CA50. Privileges
are related to an associate's role and the primary association of a profile template is based on role.
Developing Custom Business Applications (optional)
To provide associates with additional capabilities such as price checking, item location, task management, etc.,
custom Web applications can be developed for the CA50 to access over the network. Sample price lookup
applications are provided as examples in the UCA server install.
NOTE For sample business applications see
Identifying Site Specific Settings
As each site is deployed there are settings in the DB that are specific to the network structure at the site. This
includes the UCA server address or host name, PBX address and URLs for any business applications used by the
CA50. Depending upon the network characteristics there are some network timeout settings that may need to be
adjusted. For more information, see the
CacheTimeToLive, BadRFSampleThreshhold, GoodRFSampleThreshhold and MinSignalStrength).
Configuring Site User Lists with Role/Group Assignments
If the built in Device User Authentication is used, the tables must be seeded with the users at the site. Since the
UCA login process depends upon a role and group for the associate logging in, an audit should be performed of the
users at that site (either in the built authentication tables or in the external authentication database that was
integrated).
Configuring a Site Phone Extension Pool
Phone extension setups and needs may vary from site to site. An audit is required to determine exactly how the
PBX at the site is configured. Make any required adjustments to the phone extension pool and appropriately seed
the phone extension pool.
Configuring Additional Phonebook Entries
Similar to the phone extension pool, additional phone book entries must be evaluated at each site to account for
the variations at each site.
Appendix I, Business Applications
Base XML Profile Sample on page 7-25
Supplement.
(WebServiceResponseTimeout,
Advertisement
Table of Contents
Troubleshooting
