Equisys technical notes

Technical guidance, explanations and fixes for our products

INFO: Changes in Brooktrout driver version 6.6.0 update



ID: ZTN1939

This Zetafax technical note applies to:

  • Zetafax 2012 Platform Feature Pack


The Brooktrout 6.6.0 driver update contains a number of fixes and enhancements, including support for Windows Server 2012.  It is intended for use on Zetafax 2012 systems with the Zetafax 2012 Platform Feature Pack installed.

The update is recommended for any Zetafax Server installed on Windows Server 2012, and configured with Brooktrout fax boards or the Zetafax FoIP Connector (SR140 Edition) with an earlier version of the Dialogic drivers.

This document details the changes in the release.

More information

The release includes the following changes:

  • Support for Windows Server 2012
    • The Brooktrout drivers have now been certified by Dialogic for use on Windows Server 2012 (64-bit), including use with Brooktrout fax boards and Brooktrout SR140 software (as used by the SR140 Edition of the Zetafax FoIP Connector).
  • SIP over TCP
    • SIP over TCP, which is supported on SR140 and IP-enabled Dialogic® Brooktrout® TR1034 Fax Boards, provides more reliable transport over SIP trunks as compared to SIP over UDP.  The default transport protocol for SIP will remain as UDP; an optional configuration parameter (available in the Dialogic configuration settings) allows users to enable TCP support.
      When TCP support is enabled, users will be able to receive inbound SIP messages using either the UDP or TCP transport protocols. For outbound SIP calls, users will be able to selectively use either the UDP or TCP transport protocol to transmit the SIP messages for a call.
  • Support for SIP OPTIONS request
    • Support for the SIP OPTIONS for SR140 has been added to the SIP stack to transmit a 200 OK message in response to a SIP OPTIONS request.  In prior Brooktrout SDKs, the SIP response to an OPTIONS message was 501 (Not Implemented).  This new feature allows flexibility in multiple fax server deployments, including more efficient routing of traffic when a fax server is not available.
  • User Configurable SIP Codes
    • With SDK 6.6, those using SR140 have the ability to configure SIP response codes with three new parameters in the callctrl.cfg configuration file (ip_reject_call_not_answered, sip_reject_unsupported_media, and sip_reject_t38_renegotiation).
      This feature would, for example, allow a gateway or SBC to reroute incoming calls based on the message received (versus simply rejecting the call if all channels are busy).
      Each parameter added to the callctrl.cfg configuration file will indicate the SIP Response Code to be transmitted back to the originator of the call when a SIP call is rejected for one of the following reasons:
      • Inbound SIP INVITE rejected due to all channels busy
      • Inbound SIP INVITE rejected due to unsupported media types
      • Inbound SIP T.38 INVITE rejected due to Fax Transport Protocol set to G.711 pass-through only mode
  • SIP Early Media
    • SDK 6.6 adds support to SR140 for SIP Early Media as defined in RFC 3261, which allows the network to provide in-band tonal call progress signaling.
      Early media is supported in the inbound direction (i.e., media stream coming into the SR140), with the inbound media stream occurring in response to an INVITE originated by the SR140 (i.e., an outbound call).
      This feature also adds support for RFC 3264 (An Offer/Answer Model with Session Description Protocol (SDP)) and for RFC 3262 (Reliability of Provisional Responses in Session Initiation Protocol (SIP)).
      Support for SIP early media increases the probability that SR140-based solutions will interoperate with SIP trunks and devices that are SIPconnect compliant.


HOWTO: Upgrade to the latest Brooktrout Drivers

Last updated: 13th May 2013 (NT/MW)

Equisys Logo, Document Management and Expense Management for Business Central

Replaced by script