Registers a device with JTAPI.

JTapiNonTriggeringSubscribe will register a device dynamically. The specific Cisco Unified Communications Manager node to which the device is registered is decided by the specified DevicePoolName, which is described in mceadmin. Note that the device pool described by DevicePoolName is a Cisco Unified Application Environment configuration; it is completely distinct from device pools as defined by Cisco Unified Communications Manager.

If a device has successfully been registered with JTapiNonTriggeringSubscribe, then later that device can be unregistered with JTapiUnsubscribe.

The JTapiNonTriggeringSubscribe action is a way for an application to register a device at application run-time. However, one can also specify devices for permanent JTAPI registration via the mceadmin web interface. he following information is meant to help determine if you should use the mceadmin 'static' mechanism, or the JTapiNonTriggeringSubscribe dynamic mechanism: if you know that you need to always monitor a phone in order to catch certain interesting events which occur non-deterministically, then use the static mechanism available via mceadmin. If instead you only need to monitor a phone for a specific, deterministic amount of time, then this dynamic mechanism is probably more ideal because there is a maximum number of concurrent JTAPI registrations possible for a given Cisco Unified Communications Manager cluster. By registering a device only as you need it, an application which does not have extremely high usage patterns could help keep the total number of registrations below this maximum concurrent amount, but still be able to control any device in the deployment as needed.

If the application server is restarted, then all registrations created via JTapiNonTriggeringSubscribe will be lost and are not automatically re-created upon startup of the application server.

No description.

No description.

No description.