JTapiTerminalInService indicates that the terminal was successfully registered and is IN-SERVICE.

When a JTapiTerminalInService event occurs, the apps can start call control and other non control actions that require the device to be in registered State. For example, to send data to the device, the device has to be in registered state. So when a JTapiTerminalInService event occurs, the app can initiate a JTapiSendXSIData.

The JTapiNonTriggeringSubscribe is a app initiated action to register a device and the success of the action only indicates that a request has been send successfully. It is not a confirmation that a device has finished the registration process which is a asynchronous action. Hence it is not advisable to call other actions back to back following JTapiNonTriggeringSubscribe that require the device to in registered state. Instead the use has to wait for the JTapiTerminalInService event before invoking any new actions that require the device to be registered.

None.