background image

 
  

 

Motivation: The 

current 

COMMON-ISDN-API specification defines paper formats 

ISO A4, ISO B4 and ISO A3 at standard resolution (R8 x 3.85) and high 
resolution (R8 x 7.7). Support for B4 and A3 is even optional. 

 

The following document proposes a COMMON-ISDN-API extension 
that enables FAX document transmission and reception with paper 
formats ISO A4, ISO B4 and ISO A3 and these resolutions as specified 
in T.30: 

 

R8 x 3.85 

 

R8 x 7.7 

 

R8 x 15.4 

 

R16 x 15.4 

 

200 x 200 

 

300 x 300 

 

400 x 400 

 

The page format and resolution information is passed via appropriate 
fields in the SFF page header. 
To reduce the additions required in a CAPI application in order to make 
use of the extension, the new functionality is added directly to the 
existing SFF format. This means that there is a possibility of conflict 
with future official extensions of the COMMON-ISDN-API. To prevent 
incompatibilities, support for FAX paper formats and resolutions must be 
enabled explicitly so as to turn off any future CAPI extension that would 
cause incompatibility. 

 

Specifically, it has to be enabled by the application for a designated 
controller through a manufacturer request command 9 (Options request) 
with bit 6 (Enable FAX paper formats and resolutions) set. It will stay 
active until either the application releases the COMMON-ISDN-API or 
issues another options request with bit 6 not set. 

 

An application can determine whether the COMMON-ISDN-API 
supports FAX paper formats and resolutions by examining the CAPI 
profile and searching the manufacturer string for "Eicon" or by 
examining the CAPI profile and trying the manufacturer command 9 
described below. 

 
 

Changes since the first version from 12.1.2001: 

 

Added support for resolutions 300 x 600, 400 x 800, 600 x 1200, 600 
x 600 and 1200 x 1200 dpi. 

 
 

Summary of Contents for COMMON-ISDN-API

Page 1: ...Proprietary Extension for COMMON ISDN API Version 2 0 Extension for Fax Paper Formats and Resolutions October 2007 Dialogic Corporation...

Page 2: ...ne or more patents or other intellectual property rights owned by third parties Dialogic Corporation or its subsidiaries do not provide any intellectual property licenses with the sale of Dialogic pro...

Page 3: ...f conflict with future official extensions of the COMMON ISDN API To prevent incompatibilities support for FAX paper formats and resolutions must be enabled explicitly so as to turn off any future CAP...

Page 4: ...supported 8 31 reserved 4 bytes B1 protocol support bit field 0 64 kbit s with HDLC framing always set 1 64 kbit s bit transparent operation with byte framing from the network 2 V 110 asynchronous op...

Page 5: ...208 X 25 DTE DTE 3 X 25 DCE 4 T 30 for fax group 3 5 T 30 for fax group 3 with extensions 6 reserved 7 Modem 8 31 reserved 24 bytes reserved for COMMON ISDN API use 4 bytes Private options bit field 0...

Page 6: ...c The purpose of the parameter manufacturer specific is to exchange manufacturer specific infor mation Manufacturer specific information for MANUFACTURER_REQ word manufacturer command Manufacturer spe...

Page 7: ...ve Codec 9 Options request This information element appears in Manufacturer Specific Manufacturer Command Parameters The purpose of the parameter manufacturer command parameters is to specify command...

Page 8: ...ocument header Parameter Type Comment SFF_Id dword Magic value identification of SFF Format coded as 0x66666653 SFFF Version byte Version number of SFF document coded 0x01 reserved byte Reserved for f...

Page 9: ...aper formats and resolutions are enabled 0x00 98 lpi 3 85 lines per millimeter 0x01 196 lpi 7 7 lines per millimeter 0x02 0x7f reserved 0x80 reserved 0x81 100 lpi 0x82 reserved 0x83 200 lpi 0x84 reser...

Page 10: ...extPage dword Byte offset to next page header or 0x00000000 Coded as 0x00000001 if last page B 2 3 Page data Page data are coded line by line data describes each pixel row Lines are coded as records o...

Reviews: