Document conversion: text alternative not unicode, Easyconfig: service name length not restricted, Fax over ip: message wait indication and avaya – Kofax Communication Server 9.2.0 User Manual

Page 38: Japanese and other characters rotated, Kcs client applications fail to start after update

Advertising
background image

Known Issues

38

Kofax Communication Server Release Notes

Document Conversion: Text Alternative Not Unicode

When you are using TWS or TC/LINK document conversion for Word or Excel documents

with Unicode characters, the text alternative is not Unicode. (SPR00121081)

EasyConfig: Service Name Length Not Restricted

In EasyConfig, if you are using non-English characters, such as Japanese symbols, it is

possible to configure longer service names than what can be saved correctly. (SPR00113538)
Note The service names can be only 8 bytes long. Japanese symbols require up to 3 bytes per

symbol, therefore, only 2 symbols are possible.

Fax over IP: Message Wait Indication and Avaya

Although both Avaya Communication Manager and KCS Fax over IP support message wait

indication signaling using the SIP NOTIFY method, message wait indication does not work.

(SPR00119076)

Fax over IP: SIP Calls Can Fail with Large Messages

FoIP SIP calls via TCP or TLS can fail if SIP messages are received in multiple network

packets. In such case, KCS FoIP processes an incomplete SIP message. The following or

similar errors are written to the FoIP trace file (SPR00176917):

Error reading SIP message, Sip2XML read error, bad SIP message

Workaround: Use SIP via UDP.

Japanese and Other Characters Rotated

Japanese, Chinese, and other characters may appear rotated by 90 degrees. (SPR00113545)

Workaround: Fonts beginning with the at sign (@), such as @Arial Unicode MS, support

vertical writing of certain languages. Use fonts without the at sign, such as Arial Unicode MS.

KCS Client Applications Fail to Start After Update

If you update only KCS client applications on a computer that also includes KCS server

components, the client software fails to start because of obsolete shared modules.

(SPR00176011)

Mixing components from the latest and older KCS releases is not supported, even if they are

installed on different computers.

Workaround: Always update all KCS components to the latest release. Update server

components before updating the client applications.

Advertising