Table of Contents
Advertisement
October 2007
Reliability—You can make changes to co-resident applications without
affecting the status of their link to the switch. This lets contact center
activity continue for other applications in the solution.
Troubleshooting—Diagnosis of issues is limited to LinkPlexer. Other
applications conflicting with the operation of LinkPlexer do not need to be
eliminated.
Application considerations
Applications connected to LinkPlexer 6.0 must cooperate in controlling
common resources:
A race condition can result if two applications attempt to change the state of
the same device at the same time.
One application should control the device, others should only monitor
events at the device. This is particularly applicable to controlling CDNs.
Only one application should attempt to control an individual CDN.
The applications must also be tolerant of receiving events related to resources
with which the application is not previously associated for the following
reasons:
Applications can still get events on devices they have disassociated.
Applications receive messages about resources that other applications are
monitoring.
The impact of receiving these unexpected events can only be determined
through testing the application in a LinkPlexer 6.0 environment.
Limitations
LinkPlexer 6.0 has the following known limitations:
X.25 bandwidth Enhanced Multi-Protocol Controller (EMPC) interface
limited to 19,200 bps. This is actually a CS 2x00/DMS limitation, rather
than a LinkPlexer limitation.
512 invoke IDs
invoke IDs are shared between applications
LinkPlexer supports a maximum of 512 invoke IDs in either direction
LinkPlexer can run out of invoke IDs if switch latency is long
Installation and Configuration Guide
Getting started
21
Advertisement
Table of Contents
