/mcpThe bit rate and packetSize that are exposed on interface CiscoRTPInputProperties and CiscoRTPOutputProperties will not be a constant for this codec, so application logic should not rely on these values if codec (payloadType) is iSac. Interface Changes See CiscoIsacMediaCapability, on page 415 Message Sequences iSac Codec, on page 1057 Backward Compatibility This feature is backward compatible. Java Socket Connect Timeout The Java Socket Connect Timeout enhancement enables the configuration of a timeout in seconds by using the Cisco Unified JTAPI specification and prevents connection delays to the CTIManager when the primary CTI Manager. The default is 15 seconds. If the default of 15 seconds is unacceptable to the application, the default JAVA API of zero (0) sets the behavior to the normal JAVA Socket Connect API. The values range from 5 through 180 seconds. Zero defaults to Java behavior of the socket connect without any time-out for connection. Interface Changes See CiscoJtapiProperties, on page 435. Message Sequences See CiscoJtapiProperties, on page 1128. Backward Compatibility This feature is backward compatible. Join Across Lines In this version, this feature allows applications to conference two calls that are on different addresses of the same terminal. It will also let applications add participants to a conference using a noncontroller. Join across lines is not supported on CTI-supported phones that run SIP. You can disable join across lines feature by turning off Join Across Lines Policy service parameter, while you can disable Conference Chaining and feature to allow noncontroller adding participant to conference by disabling the “Advanced Ad Hoc Conference Enabled” and “Non-linear Ad Hoc Conference Linking Enabled” service parameters. Cisco Unified JTAPI Developers Guide for Cisco Unified Communications Manager, Release 15 and SUs 110 Features Supported by Cisco Unified JTAPI Java Socket Connect Timeout