
Dialogic
®
Brooktrout
®
Product Series SDK 6.7.0 Release Notes 30
Known Issues and Limitations
This section lists the known issues/limitations on the product. These are classified in functional categories. The notation
"brkt~nnnn" or “IPYnnnnn”is used to reference a specific issue in Dialogic’s change request tracking database.
Installation, packaging and configuration
IPY90652, IPY55491 – The Brooktrout system software may have dependencies on multiple versions of Windows
system dll’s (such as msvcrt80.dll) due to the use of pre-built libraries. Developer created install packages are
expected to use the Microsoft side by side assembly feature of Windows to handle this. Installing the Brooktrout
SDK or msi files will install the needed redistributable files automatically. Details on how to determine which re-
distributable files are installed by the msi file can be found in the SDK Developer Guide. Developers may also use
the Brooktrout merge modules to add the needed redistributable files to their own installers. Alternately, the needed
Microsoft redistributable can be installed manually using this link:
http://www.microsoft.com/downloads/details.aspx?familyid=766a6af7-ec73-40ff-b072-
9112bab119c2&displaylang=en
IPY54089 - If an application built using the Bfv API library uses ACE, that ACE library's symbols may conflict
with those of the ACE library embedded in the Bfv API. This can cause runtime problems.
IPY54300 - Sun Ultra 25 Server has unreliable PCI-Express Slots, labeled PCIE0, PCIE1. The failure mode was that
the Dialogic cards fail to be recognized in the server for Solaris SPARC 9 and 10. Sun have resolved this issue.
Patch 124412-01 is available on Sunsolve (OBP 4.25.7 ). Link to patch:
http://sunsolve.sun.com/search/document.do?assetkey=1-21-124412-01-1
IPY56463 – SR140 IPv6 with CUCM or Cisco router. If using IPv6 and CUCM or a Cisco Router be aware that
Cisco does not support link-local IPv6 addresses.
IPY56106, IPY56192 – SR140 IPv6. If using IPv6, the local IPv6 address must be configured in the sip_ContactV6
parameter.
IPY56207 – SR140 Linux loopback. If using Linux and IPv6, in order to make a loop-back call use the IPv6
address instead of [::1]. If using Linux and IPv4, in order to call the address 127.0.0.1 you must not specify an
address in the sip_Contact parameter.
Call Control
IPY53972 – If caller ID is enabled on FXS loop start lines, the “number of rings” parameter must be set to 2 or
greater in order to detect the caller ID.
IPY54298 – On single-span digital TR1034 models, using R2 signaling, an MFR2 call might be dropped when all
channels receive or originate calls simultaneously. The dropped calls will return with "Misc error: Channel not in
connected state" errors.
IPY54142 - When using H.323, fast-start and no tunneling. With certain remote devices the connect message will
not be sent when the remote end has disabled tunneling and is configured for fast-start. The symptom is inbound
calls not sending the connect message to the remote end. The workaround is to enable tunneling on the remote end.
IPY57181- Cisco Cube will fail to re-invite the SR140 to T.38 when the SR140 is configured to support multiple
audio codecs for G.711 when using SIP (Cisco bug id CSCsi10343). The workaround is to select only one of the
audio codecs.
Fax
IPY80657, IPY54862 – When receiving a V.34 fax using MMR compression over the wire, 1200x1200 resolution,
and either A3 or B4 page width, an error can occur if the received fax data is stored on the host in MH compression.
To prevent an error from this rare case, the data should be stored onto the host using either MR or MMR
compression. Use the API function BfvFaxSetReceiveFmt to set the compression.
Comentarios a estos manuales