Dialogic® System Release 6.
Copyright © 2004-2008, Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Corporation at the address provided below. All contents of this document are subject to change without notice and do not represent a commitment on the part of Dialogic Corporation or its subsidiaries. Reasonable effort is made to ensure the accuracy of the information contained in the document.
About This Publication This section contains information about the following topics: • Purpose • Intended Audience • How to Use This Publication • Related Information Purpose This Release Update addresses issues associated with Dialogic® System Release 6.0 PCI for Windows® (sometimes also referred to herein as “System Release 6.0 PCI Windows”).
About This Publication Related Information See the following for additional information: • For information about the products and features supported in this release, see the Dialogic® System Release 6.0 PCI for Windows® Release Guide, which is included as part of the documentation bookshelf for the release. • For further information on issues that have an associated defect number, you may use the Defect Tracking tool at http://membersresource.dialogic.com/defects/.
Document Revision History This Revision History summarizes the changes made in each published version of the Release Update for Dialogic® System Release 6.0 PCI for Windows®, which is a document that has been and is intended to be periodically updated throughout the lifetime of the release. Document Rev 62 - published January 30, 2008 Updated for Service Update 181. In the Post-Release Developments section: • Added Runtime Control of Single or Double Hookflash on Consultation Drop for FXS/LS Protocol.
Document Revision History In the Documentation Updates section: • Deleted the corrections for the Dialogic® Audio Conferencing API Library Reference and Dialogic® Audio Conferencing API Programming Guide, because these corrections have been incorporated into updated documents that are now on the online documentation bookshelf.
Document Revision History Document Rev 59 - published October 9, 2007 Updated for Service Update 171. In the Post-Release Developments section, added Support for Windows Vista® Operating System. In the Release Issues section • Added the following resolved problems: IPY00039476, IPY00040052. • Added the following known problems: IPY00040083, IPY00040086. Made global changes to reflect Dialogic brand. Document Rev 58 - published September 14, 2007 Updated for Service Update 167.
Document Revision History Document Rev 55 - published August 20, 2007 Updated for Service Update 165. In the Post-Release Developments section, added Global DPD Enabled on Dialogic® Springware Boards. In the Release Issues section: • Added the following resolved problems: IPY00037918, IPY00038545, IPY00038572, IPY00039155, IPY00039331, IPY00039341, IPY00039492. • Eliminated the link to view issues sorted by PTR number. (PTR numbers have been superseded by defect numbers.
Document Revision History In the Release Issues section: • Added the following resolved problems: IPY00037319, IPY00037643, IPY00037789, IPY00037923, IPY00038298, IPY00038407, IPY00038419, IPY00038433, IPY00038435, IPY00038494, IPY00038499, IPY00038524, IPY00038533, IPY00038539, IPY00038611, IPY00038612, IPY00038708, IPY00038836, IPY00038849, IPY00038894, IPY00038979, IPY00038991, IPY00038998. • Revised the information for IPY00036665 (resolved in Service Update 160, not in Service Update 155).
Document Revision History In the Release Issues section, added the following resolved problems: IPY00010514 (PTR 35342), IPY00028248 (PTR 33718), IPY00028516 (PTR 35001), IPY00028549 (PTR 35901), IPY00028555 (PTR 36110), IPY00031590 (PTR 36755). Document Rev 50 - published June 1, 2007 Updated for Service Update 154. In the Post-Release Developments section: • Added Support for PCI Express Boards - Dialogic® Station Interface Boards.
Document Revision History • Added an update to the Media Load table under Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide. Document Rev 48 - published March 22, 2007 Updated for Service Update 144. In the Post-Release Developments section: • Added Support for PCI Express Boards - Dialogic® DM/V-B Products. • Added Support for Dialogic® D/4PCI Board. • Added New Parameter for Adjusting Silence Threshold on Dialogic® DM3 Boards.
Document Revision History In the Release Issues section, added the following resolved problems: IPY00031534, IPY00036044, IPY00036101, IPY00036247, IPY00036248, IPY00036337, IPY00036418, IPY00036949. In the Documentation Updates section: • Added IPY00006024 (PTR 29612) under Dialogic® PBX Integration Board User's Guide. • Added documentation updates to the following document because of new features in the Service Update: Dialogic® System Software Diagnostics Guide.
Document Revision History In the Documentation Updates section: • Deleted the corrections for the Dialogic® System Release 6.0 PCI for Windows® Software Installation Guide because these corrections have been incorporated into an updated document that is now on the documentation bookshelf. • Deleted the relevant corrections for the Dialogic® System Software Diagnostics Guide because these corrections have been incorporated into an updated document that is now on the documentation bookshelf.
Document Revision History Document Rev 39 - published August 22, 2006 Updated for Service Update 118. In the Release Issues section: • Added the following resolved problem: IPY00030001 (PTR 36796). • Added the following known (permanent) problem: IPY00031563 (PTR 36612). Document Rev 38 - published August 7, 2006 Updated for Service Update 116. In the Release Issues section, added the following resolved problems: IPY00034050 (PTR 36636). Also added IPY00034018 (fixed in Service Update 115).
Document Revision History In the Release Issues section: • Added the following resolved problems: IPY00031559 (PTR 36828), IPY00031560 (PTR 36801), IPY00032793, IPY00033009, IPY00033584. • Added three known (permanent) problems regarding Runtime Trace Facility: IPY00032730, IPY00032735, IPY00032742. In the Documentation Updates section: • Added an update to the NCM_ApplyTrunkConfiguration( ) function under Dialogic® Native Configuration Manager API Library Reference.
Document Revision History • Added IPY00006520 (PTR 36259), IPY00006556 (PTR 35326), and IPY00006570 (PTR 35992) under Dialogic® Fax Software Reference. • Added IPY00006537 (PTR 35666), IPY00006580 (PTR 34546), IPY00006581 (PTR 35616), and IPY00006594 (PTR 36685) under Dialogic® Voice API Programming Guide. Document Rev 33 - published June 12, 2006 Updated for Service Update 108. In the Post-Release Developments section, added information about the New Fax Parameter for Modem Receive Level.
Document Revision History In the Post-Release Developments section, added information about the following: • PDK Configuration Property Sheet which is a new property sheet in DCM. • Automatic FCD File Generation, which provides an enhanced way to generate an updated FCD file. • Centralized Logging using Runtime Trace Facility (RTF), which logs OA&M components to the RTF. • New Option for Dialogic® dm3post Utility, which provides an option to run POST on a chassis level.
Document Revision History In the Post-Release Developments section, added PBX Integration Support for Nortel BCM. In the Release Issues section, added the following resolved problems: IPY00006712 (PTR 36790), IPY00006846 (PTR 36711), IPY00028547 (PTR 35670), IPY00031562 (PTR 36766). In the Documentation Updates section: • Added a documentation update to the Dialogic® PBX Integration Board User's Guide because of a new feature in the Service Update.
Document Revision History • Added the following known problems: IPY00006353 (PTR 36792), IPY00006393 (PTR 36758), IPY00006407 (PTR 36806), IPY00031561 (PTR 36775), IPY00032271 (PTR 36699). In the Documentation Updates section: • Added documentation update to the following document because of a new feature in the Service Update: Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide. • Added documentation updates for the Dialogic® Digital Network Interface Software Reference.
Document Revision History Guide, Dialogic® D/42 Series Software API Reference, Dialogic® D/42 Series User’s Guide. • Added documentation update to the Dialogic® Global Call IP Technology Guide about the IP_H221NON.STANDARD data structure. Document Rev 26 - published March 2, 2006 Updated for Service Update 92. In the Post-Release Developments section, added Enhancements to Runtime Trace Facility (RTF) Logging.
Document Revision History Document Rev 24 - published February 2, 2006 Updated for Service Update 89. In the Post-Release Developments section, added Dynamically Retrieving and Modifying Selected Protocol Parameters When Using Dialogic® DM3 Boards.
Document Revision History • Added Support for QSIG NCAS Calls on Dialogic® DM3 Boards. • Added Loop Current Reversal Detection on the Dialogic® DMV160LP Board. • Added Adjusting DTMF Characteristics through the CONFIG File. • Added Single Board Start/Stop for Selected Dialogic® JCT Boards. • Added New Media Load for Dialogic® DMV3600BP Boards. • Revised Mixing ISDN and CAS on Dialogic® DM/V-B Boards section to mention that A-law/Mu-law conversion is supported.
Document Revision History • Added PTR# 33826 under Dialogic® IP Media Library API Programming Guide. • Added PTR# 34119 under Dialogic® Standard Runtime Library API Programming Guide. • Added PTR# 33806 under Dialogic® Voice API Library Reference. Document Rev 19 - published October 17, 2005 Updated for Service Update 71. In the Post-Release Developments section, added Dialogic® Global Call SS7 Enhancements.
Document Revision History Document Rev 17 - published September 2, 2005 Updated for Service Update 65. In the Post-Release Developments section, added New Channel Block Timer for NTT Protocol.
Document Revision History • Added the following resolved problems: 31675, 32313, 32712, 33514, 34160, 35104, 35134, 35170, 35232, 35281, 35321, 35412, 35431, 35438, 35458. In addition, the known problem with the update install from Service Update 58 has been resolved. In the Documentation Updates section: • Added PTR# 32933 under Dialogic® System Release 6.0 PCI for Windows® Release Guide. • Added PTR# 33555/34771 under Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide.
Document Revision History Document Rev 11 - published June 24, 2005 Updated for Service Update 56. In the Post-Release Developments section: • Revised Windows® Hardware Quality Labs (WHQL) Certification section to indicate that WHQL certification for Dialogic® System Release 6.0 PCI for Windows® Service Update is not currently valid; the product is getting recertified. • Added Enhanced Special Information Tone Frequency Detection on Dialogic® DM3 Boards. • Added Enhanced GCAMS on Dialogic® DM3 Boards.
Document Revision History • Added PTR# 29448, 34490, and 35050 under Dialogic® Global Call E1/T1 CAS/R2 Technology Guide. • Added PTR# 34285 and 34840 under Dialogic® Voice API Library Reference. Document Rev 10 - published March 22, 2005 Updated for Service Update 39. In the Release Issues section: • Added the following resolved problems: 34121, 34241, 34345, 34393, 34478 • Added “SU No.” column to the Issues table to show the Service Update number for resolved PTRs.
Document Revision History • Added PTR# 32544, PTR# 32501, and PTR# 32616 to Dialogic® Global Call API Library Reference. • Added PTR# 32481 to Dialogic® Global Call API Programming Guide. • Added PTR# 32379 to Dialogic® Global Call Analog Technology Guide. • Added PTR# 32966 to Dialogic® Standard Runtime Library API Programming Guide and Dialogic® Voice API Programming Guide. • Added PTR# 32681 to Dialogic® Voice API Library Reference and Dialogic® Voice API Programming Guide.
Document Revision History Document Rev 05 - published November 15, 2004 Updated for Service Update 22. In the Post-Release Developments section: • Revised the information about installing the Service Update.
Document Revision History In the Documentation Updates section: • Added documentation updates to the following documents because of new features provided in the Service Update: Dialogic® System Release 6.
Post-Release Developments 1. This section describes significant changes to the system release subsequent to the general availability release date. • Service Update for Dialogic® System Release 6.0 PCI for Windows® . . . . . . . 33 • Runtime Control of Single or Double Hookflash on Consultation Drop for FXS/LS Protocol34 • Analog Call Transfer Support on Dialogic® Springware Boards . . . . . . . . . . . . 38 • Support for Windows Vista® Operating System . . . . . . . . . . . . . . . . . . . . . . . .
• Runtime Control of Double Answer for R2MF. . . . . . . . . . . . . . . . . . . . . . . . . . 94 • Enhanced ISDN Trace Functionality for DPNSS Tracing . . . . . . . . . . . . . . . . . 96 • Notification of Layer 1 Alarm Events on SS7 Boards . . . . . . . . . . . . . . . . . . . . 97 • Global Call Support for Time Slots on Dialogic® SS7 Boards Running in DTI Mode97 • Time Stamp for Tone-On/Off Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
• Mixing ISDN and CAS on Dialogic® DM/V-B Boards . . . . . . . . . . . . . . . . . . . . 225 • Implementation of ROLM Call Waiting LED . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 • Enhanced Special Information Tone Frequency Detection on Dialogic® DM3 Boards 229 • Enhanced GCAMS on Dialogic® DM3 Boards . . . . . . . . . . . . . . . . . . . . . . . . . 233 • Telecom Subsystem Summary Tool (its_sysinfo) . . . . . . . . . . . . . . . . . . . . . . .
Package, Core Runtime Package, ISDN Protocols, Demos, SNMP Component Manager, Global Call Protocols, and Documentation. Note: With the Service Update, the Global Call Protocols Package can now be installed as part of System Release 6.0 PCI Windows. Previously, this package was installed separately. The Development Package and Demos are available in the Developer Edition only, not in the Redistributable Edition. • If you have an existing version of System Release 6.
by default.) CDP file parameters are set on a board basis. Parameter settings are static and apply to all calls (per board). However, some PBXs may require either a single or double hookflash depending on the circumstances of the call.
• data_size = sizeof(int) • data = One of the following values: - GCPV_SINGLE_HKFLASH - single hookflash - GCPV_DBL_HKFLASH - double hookflash - GCPV_DISABLED - not set Once the GC_PARM_BLK has been populated with the desired values, the gc_SetConfigData( ) function can be issued to perform the configuration.
The following guidelines discuss the use of the GCPARM_CONSDROP_HKFLASH_OVERRIDE parameter with regard to the related parameters in the pdk_us_ls_fxs_io.cdp file: • The related parameters in the pdk_us_ls_fxs_io.cdp file are CDP_AllowDblHookflashOnConsultationDrop and CDP_BypassHookflashOnConsultationDrop. Both are disabled by default; the default behavior is that a single hookflash is sent when dropping a consultation call.
1.3 Analog Call Transfer Support on Dialogic® Springware Boards With the Service Update, blind and supervised analog call transfers using the Dialogic® Global Call API are now supported on Dialogic® Springware Boards. Support for analog call transfer is applicable only to standard POTS (“plain old telephone service”) line products.
For further information about call transfers, see the Call State Models chapter of the Dialogic® Global Call API Programming Guide. 1.3.2 Using Global Call with Analog Springware Boards In order to use Global Call with analog Springware Boards: • The Global Call Protocols package must be installed. • The boards must be using the North American Analog Bidirectional PDK protocol, pdk_na_an_io. The Global Call Protocols package is one of the features that can be selected when installing System Release 6.
Other changes to the pdk_na_an_io.cdp file include: SYS_FEATURES parameter now includes feature_transfer and feature_hold: All CHARSTRING_t SYS_FEATURES = “feature_inbound,feature_outbound, feature_DNIS,feature_ANI,feature_transfer,feature_hold” New analog pulse signal: All CAS_SIGNAL_ANALOG_PULSE_t CAS_HOOKFLASH = Hookflash 1.3.4 Documentation The online bookshelf provided with Dialogic® System Release 6.
Dialogic® Boards Supported with Windows Vista® Operating Systems PCI Boards PCI Express Boards D/4PCI D/300JCT-E1 D/4PCIE-4F-W D/480JCT-2T1-EW D/4PCIU D/320JCT D/4PCIE-4S-W D/600JCT-1E1-75-EW D/4PCIUF D/480JCT-1T1 D/41JCT-LS-EW D/600JCT-1E1-120-EW D/41JCT-LS D/480JCT-2T1 D/120JCT-LS-EW D/600JCT-2E1-75-EW D/120JCT-LS D/600JCT-1E1 D/240JCT-T1-EW D/600JCT-2E1-120-EW D/160JCT D/600JCT-2E1 D/300JCT-E1-EW VFX/41JCT-LS-EW D/240JCT-T1 VFX/41JCT-LS D/480JCT-1T1-EW Note: Dialogic® DM3 Boa
When installing System Release 6.0 PCI Windows on Windows Vista, you will be prompted to enter two directory locations (rather than one) for storing Dialogic® System Release Software files: Choose Program File Destination Location This is the directory where non-user-modifiable files in the System Release Software will be installed. The default location is C:\Program Files\Dialogic.
Furthermore, Microsoft has dropped support of Visual Studio .NET 2002 or Visual Studio .NET 2003 on Windows Vista, and has released the Visual Studio 2005 Service Pack 1 update for Windows Vista. Please refer to the following MSDN® pages for more information: • http://msdn2.microsoft.com/en-us/vstudio/aa948853.aspx • http://msdn2.microsoft.com/en-us/vstudio/aa948854.aspx The following table elaborates on version numbers and restrictions. Any development environment prior to these is no longer supported.
started. This is the way Windows Vista User Account Control works; this is not unique to Dialogic® Software under Windows Vista. An example of a consent dialog is: UDD Must Be Set to “Run as Administrator” Dialogic® Diagnostics Software (UDD) works with Windows Vista; however, it lacks the embedded request for administration tokens from the invoker, so execution will fail due to this. In order to correct this problem, the user can manually set the appropriate rights.
RTF Logging With this release, Runtime Trace Facility (RTF) configuration and logging are only available for users who have administrator privileges. The RTF Manager will not run unless this condition is met. In order for user applications to be able to generate RTF logs, the application must be run as an administrator.
New APIs The two new API functions are: • dx_resetch( ) - Call this API to recover the media channel when the channel is stuck and in a recoverable state. If the channel is recovered, a TDX_RESET event is generated to the application, which enables the application to reuse the channel for more media functions. If the channel is not in a recoverable state, a TDX_RESETERR event is sent back to the application indicating that the specific channel is not recoverable.
dx_resetch( ) Name: dx_resetch (chdev, mode) Inputs: int chdev • valid channel device handle int mode • mode of operation Returns: 0 if success -1 if failure Includes: srllib.h dxxxlib.h Category: I/O Mode: asynchronous or synchronous Dialogic® DM3 Platform: Description The dx_resetch( ) function recovers a channel that is “stuck” (busy or hung) and in a recoverable state, and brings it to an idle and usable state.
Errors If the function returns -1, use the Dialogic® Standard Runtime Library (SRL) Standard Attribute function ATDV_LASTERR( ) to obtain the error code or use ATDV_ERRMSGP( ) to obtain a descriptive error message. One of the following error codes may be returned: EDX_BADPARM Invalid parameter EDX_FWERROR Firmware error EDX_NOERROR No error Example #include #include main() { int chdev, srlmode; /* Set SRL to run in polled mode.
} /* Wait for TDX_RESET or TDX_RESETERR events */ } See Also • ec_resetch( ) in the Dialogic® Continuous Speech Processing API Library Reference Dialogic® System Release 6.
ec_resetch( ) Name: ec_resetch (chdev, mode) Inputs: int chdev • valid channel device handle int mode • mode of operation Returns: 0 if success -1 if failure Includes: srllib.h eclib.h Category: I/O Mode: asynchronous or synchronous Dialogic® DM3 Platform: Description The ec_resetch( ) function recovers a channel that is “stuck” (busy or hung) and in a recoverable state, and brings it to an idle and usable state.
Errors If the function returns -1, use the Dialogic® Standard Runtime Library (SRL) Standard Attribute function ATDV_LASTERR( ) to obtain the error code or use ATDV_ERRMSGP( ) to obtain a descriptive error message. One of the following error codes may be returned: EDX_BADPARM Invalid parameter EDX_FWERROR Firmware error EDX_NOERROR No error Example #include #include #include #include #include
/* Wait for TEC_RESET/TEC_RESETERR and TDX_RESET/TDX_RESETERR */ } See Also • dx_resetch( ) in the Dialogic® Voice API Library Reference Dialogic® System Release 6.
1.5.2 Implementation Guidelines The following guidelines apply when implementing the media channel reset capability using the Dialogic® Voice API: • It is recommended that you issue the function in asynchronous mode for more efficient processing. In synchronous mode, the calling thread is blocked until the function completes, which may take up to a minute in worst-case scenarios. • The dx_resetch( ) function is intended for use on channels that are stuck and not responding.
• This feature does not address reset of IP media channels on Dialogic® DM/IP Boards. It only addresses the reset of voice channels on DM/IP Boards. • The reset may not succeed if CPU utilization on the host system is close to 100 percent. It is recommended that the CPU usage be at a reasonable level (less than 70 percent) before you attempt a channel reset. 1.5.4 Documentation The online bookshelf provided with Dialogic® System Release 6.
1.8 Enhanced Special Information Tones on Dialogic® DM3 Boards Using Voice and Global Call APIs With the Service Update, the user has the ability to detect new custom special information tones (SITs) on Dialogic® DM3 Boards using the Dialogic® Voice API and Dialogic® Global Call API. The new custom SITs are detected via the regular API events for detecting call progress analysis outcome, and in particular, SIT tone detection.
#define TID_SIT_NC_INTERLATA #define TID_SIT_RO_INTERLATA #define TID_SIT_IO For more information on modifying tone definitions, see the Dialogic® Voice API Programming Guide. Global Call API For the Global Call API, 15 new custom SITs are allowed and are reported to the application via the GCEV_DISCONNECTED event once any one of them is detected via Global Call.
Voice SIT Global Call Result Value Value Global Call Error Code Value Description TID_SIT_RO_INTERLATA GCRV_REORDER_ INTERLATA (GCRV_RESULT | 0x72) EGC_REORDER _INTERLATA 0x164 Reorder interlata SIT detected TID_SIT_IO GCRV_INEFFECTIVE_ OTHER (GCRV_RESULT | 0x73) EGC_INEFFECTI VE_OTHER 0x165 Ineffective other SIT detected 1.8.
/* Perform system error processing */ exit(1); } /* Get the Tone Information for the TID_CUSTOM_SIT1 tone*/ int result; TONE_DATA tonedata; if ((result = dx_querytone(brdhdl, TID_CUSTOM_SIT1, &tonedata, EV_ASYNC)) == -1) { printf("Cannot obtain tone information for TID_CUSTOM_SIT1 \n"); /* Perform system error processing */ exit(1); } /* Delete the current TID_CUSTOM_SIT1 call progress tone before creating a new definition*/ if ((result = dx_deletetone(brdhdl, TID_CUSTOM_SIT1, EV_ASYNC)) == -1) { printf("Ca
1.8.4 Documentation The online bookshelf provided with Dialogic® System Release 6.0 PCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics.
PCD Files That Do Not Support Enhanced Special Information Tones Feature PCD File (Unsupported) Description PCD File (Unsupported) Description PCD File (Unsupported) Description at_hdsi.pcd HDSI ipvs_evr_2isdn _4ess_311c.pc d DM/IP481-2T1-100BT (DM/IPLINK2T1_NIC, 1 daughterboard, 48 channels) ml2_dsa_r2mf. pcd DMV600A_2E1 (BV+CSP 60 channels PSTN 2 Trunks R2MF protocol) at_hdsi_48_pla y_rec.pcd HDSI ipvs_evr_2isdn _4ess_ml11_3 11c.
PCD Files That Do Not Support Enhanced Special Information Tones Feature PCD File (Unsupported) Description PCD File (Unsupported) Description PCD File (Unsupported) Description be_hdsi_48_pl ay_rec.pcd HDSI ipvs_evr_2isdn _net5_311c.pc d DM/IP601-2E1 (DM/IPLINK-E1_NIC, 1 daughterboard, 60 channels) mn_4xt_r2mf.p cd DMT1200_4E1 (PSTN 4 Trunks R2MF protocol) be_hdsi_72_pl ay_rec.pcd HDSI ipvs_evr_2isdn _net5_ml11_31 1c.
PCD Files That Do Not Support Enhanced Special Information Tones Feature PCD File (Unsupported) Description PCD File (Unsupported) Description PCD File (Unsupported) Description de_hdsi_72_pl ay_rec.pcd HDSI ipvs_evr_2isdn _qsige1_ml11_ 311c.pcd DM/IP601-2E1-100BT (DM/IPLINK-E1_NIC, 1 daughterboard, 60 channels) nl_hdsi_48_pla y_rec.pcd HDSI de_hdsi_96_pl ay_rec.pcd HDSI ipvs_evr_2isdn _qsigt1_311.pc d DM/IP481-2T1 (DM/IPLINK-T1_NIC, 1 daughterboard, 48 channels) nl_hdsi_72_pla y_rec.
PCD Files That Do Not Support Enhanced Special Information Tones Feature PCD File (Unsupported) Description PCD File (Unsupported) Description PCD File (Unsupported) Description fn_isdn_5ess.p cd DM/F240-1T1-PCI T1 w/24 Ch. Fax FN ipvs_evr_isdn_ dms_311.pcd DM/IP241-1T1 (DM/IPLINK-T1_NIC, 1 daughterboard, 24 channels) pt_hdsi_72_pla y_rec.pcd HDSI fn_isdn_dms.pc d DM/F240-1T1-PCI T1 w/24 Ch. Fax FN ipvs_evr_isdn_ dms_ml11_311 .
PCD Files That Do Not Support Enhanced Special Information Tones Feature PCD File (Unsupported) PCD File (Unsupported) PCD File (Unsupported) Description fn3_isdn_dms. pcd DM/F240-1T1-PCI T1 w/24 Ch. Fax FN3 ipvs_evr_isdn_ qsigt1_ml11_3 11.pcd DM/IP241-1T1-100BT (DM/IPLINK-T1_NIC, 1 daughterboard, 23 channels) sg_hdsi_96_pla y_rec.pcd HDSI fn3_isdn_net5. pcd DM/F300-1E1-PCI E1 w/30 Ch. Fax FN3 ipvs_evr_r_311 .pcd DM/IP601-2E1 (DM/IPLINK-E1_NIC, 1 daughterboard, 60 channels) ul2_qsa_cas.
PCD Files That Do Not Support Enhanced Special Information Tones Feature PCD File (Unsupported) Description PCD File (Unsupported) Description PCD File (Unsupported) Description gb_hdsi_48_pl ay_rec.pcd HDSI jp_hdsi_48_pla y_rec.pcd HDSI vfn_isdn_ntt.pc d DM/VF240-1T1-PCI T1 w/24 Ch. Fax VFN gb_hdsi_72_pl ay_rec.pcd HDSI jp_hdsi_72_pla y_rec.pcd HDSI vfn_isdn_qsige 1.pcd DM/VF300-1E1-PCI E1 w/30 Ch. Fax VFN gb_hdsi_96_pl ay_rec.pcd HDSI jp_hdsi_96_pla y_rec.pcd HDSI vfn_isdn_qsigt1 .
PCD Files That Do Not Support Enhanced Special Information Tones Feature PCD File (Unsupported) Description PCD File (Unsupported) Description PCD File (Unsupported) Description hk_hdsi_96_pla y_rec.pcd HDSI ml10_dsa_r2mf .pcd DMV600A_2E1 (BV+CSP 60 channels CONF+EC 60 channels PSTN 2 Trunks R2MF protocol) vfn3_t1.pcd DM/VF240-1T1-PCI T1 w/24 Ch. Fax VFN3 ie_hdsi.pcd HDSI ml10_dsa_ts16 .pcd DMV600A_2E1 (BV+CSP 60 channels CONF+EC 60 channels PSTN 2 Trunks TS16 protocol) za_hdsi.
End user error value The numeric value of the constant that is documented in the library API reference. This is the value that will appear in the RTF log, which you can then search for in the table. Description of the error A textual description of the error. Action to be taken The suggested action to resolve the error. For firmware errors, the table provides the following information: Resource The firmware entity in which the error occurred.
System Release 6.0 PCI for Windows® installed. The central site does not need Dialogic® System Release 6.0 PCI for Windows® installed. Managed Sites System Release Software Central Site Remote Diagnostics Package IP System Release Software The remote diagnostics package is a subset of the system release software. It is designed for managing multiple remote sites from a central site, where the central site does not need the system software release or any Dialogic® boards installed.
1.11 New Parameter for Adjusting Silence Threshold on Dialogic® DM3 Boards With the Service Update, the user has the ability to adjust the silence threshold parameter on Dialogic® DM3 Boards to a value above or below the default value of -43 dBm0 while using play and record functions like dx_play( ), dx_record( ), and ec_reciottdata( ). For instance, its adjustment affects the threshold for silence termination conditions in the R4 API TPT structure.
Dialogic® DISI32-EW Switching Board Provides connectivity for up to 32 station interfaces in a single, full-length PCI Express slot. Includes conferencing, voice play/record, tone detection and generation, and caller ID capabilities. When configuring the system for the PCI Express form factor boards, use the same menu selections and configuration settings that are documented for the PCI version of the boards.
When configuring the system for the PCI Express form factor boards, use the same menu selections and configuration settings that are documented for the PCI version of the boards. Any differences are discussed below.
Media Loads/Features Supported Conferencing Echo Cancellation 30 30 12 30 30 - ML5 30 - - - - - - - 30 - - - ML10 30 30 30 30 30 30 30 30 - 32 32 32 FSK 30 CSP Streaming to CT Bus 30 CSP 30 Enhanced Echo Cancellation‡ 30 TrueSpeech 30 Enhanced Coders 30 Transaction Record UL1 ML Basic Voice Conferencing Tone Clamping Conferencing Only Conferencing Parties Fax Fax Voice Only Dialogic® DMV300BTEPEQ (Single Span Board) Dialogic® DMV600BTEPEQ (Dual Span Bo
1.14 Support for Dialogic® D/4PCI Voice Board With the Service Update, the Dialogic® D/4PCI Voice Board that was supported in older system releases is now supported in Dialogic® System Release 6.0 PCI for Windows®. The D/4PCI Board has 4 voice channels (analog) and does not have CT Bus capabilities. If present in the system, the D/4PCI Board will be detected and displayed in the Dialogic® Configuration Manager (DCM). Its default firmware file cannot be changed or configured.
1.16 File Management Enhancements for ISDNtrace Tool With the Service Update, the user can specify new command line options provided with the Dialogic® ISDNtrace tool to set the output log file size and to create multiple backup log files to be archived. 1.16.1 Feature Description This feature enhances the existing ISDN tracing file management for boards configured with an ISDN load.
-f Enable logging to file, optional Note: A space is used after the -f option but not after -a, -b, -d, -m or -s options.
• yy - current minute in hour (00 - 59) • zz - current second in minute (00 - 59) In the description above, the log file name is what the user specified on the command line. If the user specifies a -f command line option as the last parameter on the command line and does not specify a log file name, then the default log file name of ISDNTRACE will be used. Note: In order to get a default log file name, the -f option has to be used at the end of the command line.
Tue Jan 16 17:30:58 2007 TX Frame: Time = 2428.372 Command=1 SAPI=0x00 TEI=0x00 0x01 0xe6 Receive Ready Hex Dump: 02 01 01 e6 Enqueue Failed Tue Jan 16 17:30:58 2007 RX Frame: Time = 2428.
1.18 Change in ipmedia.log Implementation With the Service Update, the ipmedia.log file is no longer overwritten when the system is restarted. The ipmedia.log file is generated whenever IP Media Services are run. If there is an existing log file when the system is restarted, it is saved and renamed ipmedia.log.bak. If ipmedia.log.bak already exists, it is overwritten (only one backup file is saved). 1.
values are provided that are consistent with previous service updates and system releases to preserve backward compatibility. Pre-Record Beep Tone Characteristics and Default Values Two pre-record beep tones are defined: • A custom customer tone, BEEP_DGSD, defined as 444 Hz for 400 ms, and BEEP_DLGC, defined as 1000 Hz for 400 ms. • The traditional pre-record beep tone, BEEP_DLGC, defined as 1000 Hz. This corresponds to the beep tone definition on Springware Boards and is the default setting.
Record Beep Tone BEEP_DLGC Characteristic Signal Id Default Value 34 Label (blank) Segment Count 1 Segment Signal Type 2 Segment Frequency 1 (Hz) 1000 Segment Amplitude 1 (.25 dbm) -40 Segment Frequency 2 (Hz) 0 Segment Amplitude 2 (.
function is complete, a slight delay occurs before hearing the dial tone. With the Service Update, this delay has been reduced by 12%. 1.21 Enhanced Diagnostics The Service Update provides several new and enhanced diagnostics features. The following sections introduce some of the new features: • PSTN Diagnostics (pstndiag) • Status Monitor (statusmon) • New Dialogic® Diagnostics Management Console • New Runtime Trace Facility (RTF) Manager Note: Java Runtime Environment (JRE) version 1.
The new version of pstndiag includes the following changes: • Faster startup • Changes in the board tree view • Additional features in the lineadmin tool: enabling all supported loopback modes and counters for saturation alarms • Configurable modes of operation for the phone tool: basic, advanced, and expert Note: More detailed information about the new version of pstndiag is planned to be provided in the Dialogic® System Software Diagnostics Guide, which is scheduled to be updated soon. 1.21.
The DMC: • Provides a single portal for launching diagnostic tools: • AppMon • Castrace • Isdntrace • Dlgsnapshot • Dm3post • Debugangel • Getver • its_sysinfo • Pdktrace • Pstndiag • RTF Manager • StatusMon • Supports local and remote execution of tools. Diagnostic tools are launched remotely via the standard remote control methods provided with the operating system, such as SSH or Remote Desktop. • Lists the diagnostic logs available both locally and remotely for viewing.
• Dialogic® D/41JCT-LS-EW and Dialogic® VFX/41JCT-LS-EW Media Boards • Dialogic® D/120JCT-LS-EW Media Board When configuring the system for the PCI Express form factor boards, use the same menu selections and configuration settings that are documented for the PCI version of the boards. Any differences are discussed below.
Dialogic® D/600JCT-1E1-75-EW Media Board Provides up to 30 channels of combined media resources and a single 75-ohm E1 network interface in a single, full-length PCI Express slot. Dialogic® D/600JCT-1E1-120-EW Media Board Provides up to 30 channels of combined media resources and a single 120-ohm E1 network interface in a single, full-length PCI Express slot.
about power budgeting and guidelines for selecting the slot where a board can be installed. 2. The D/120JCT-LS-EW Board can be used with any System Release 6.0 PCI Windows Service Update release; it is not necessary to upgrade to a particular Service Update. 1.23 PDK Trace Supports CAS/R2MF/Tone Tracing With the Service Update, the Dialogic® DM3 PDK Protocol Trace (PDK Trace) tool has new functionality to log CAS, R2MF, and tone-on/tone-off information on supported boards.
1.23.2 Supported Boards The following boards support this feature: • Dialogic® DM/V1200BTEP Media Boards • Dialogic® DM/V600BTEP Media Boards • Dialogic® DM/V3600BP Media Boards 1.23.3 Sample Output Logs The following are examples and explanations of the converted output: R2MF Outbound File Line N/A 1 Level DEBUG Ser Bo... N/A 3 C...
and the bit mask of the newly detected signaling pattern. The bit mask is used to denote which of the ABCD bits are of significance for the pattern being transmitted. CAS TX File Line N/A 1 Level DEBUG Ser Bo... N/A 3 C... 11 SDL CAS Call Un TxRx TX:1001 RX:1001 Data CAS Transition (RX) PreTransition Code: 0x3d PostTransition Code: 0xd This event is logged when a new ABCD bit pattern is transmitted on the channel being traced.
1.23.4 Documentation The online bookshelf provided with Dialogic® System Release 6.0 PCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics. For more information about PDK Trace, see the Dialogic® System Software Diagnostics Guide. Note: The online bookshelf has not been updated for this feature, so the new option is not currently documented in the Dialogic® System Software Diagnostics Guide.
1.24.2 Documentation The online bookshelf provided with Dialogic® System Release 6.0 PCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics. For more information about setting parameters in the CONFIG file, see the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide.
1.26.1 Feature Description The FSK transmit (FM_ParmFSKTxSignalLevel) and receive (FM_ParmFSKRxSignalLevel) signal level parameters are described below. FSK Transmit and Receive Signal Level Number: 0x2a (0x2a04 for transmit) (0x2a00 for receive) Description: Two-way Frequency Shift Keying (FSK) and ETSI FSK allow the exchange of small amounts of data between a telephone and the server using FSK as the transport layer.
For more information about configuration files, configuration parameters, and configuration procedures, see the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide. Note: The online bookshelf has not been updated for this feature, so these new parameters are not currently documented in the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide. 1.
Group B Tone GC Cause Value Description GrpB - User Busy GCRV_BUSY “Line is busy” GrpB - Network Congestion GCRV_CONGESTION “Congestion” GrpB - Normal Clearing GCRV_NORMAL “Normal Clearing” GrpB - UnAssigned Number For DM3 Boards: GCRV_UNALLOCATED For DM3 Boards: “Number not allocated” For Springware Boards: GCRV_NOT_INSERVICE For Springware Boards: “Number not in service” For DM3 Boards: GCRV_SIT_UNKNOWN For DM3 Boards: “Unknown SIT detected” For Springware Boards: GCRV_CEPT For Springw
For features specific to E1 (R2) technology, see the following documents: • Dialogic® Global Call E1/T1 CAS/R2 Technology Guide • Dialogic® Global Call Country Dependent Parameters (CDP) for PDK Protocols Configuration Guide 1.28 Runtime Control of Double Answer for R2MF With this Service Update, a connection method called double answer is now supported for rejecting collect calls on a call-by-call basis. 1.28.
• Dialogic® D/600JCT-2E1 Media Boards 1.28.3 Example Code #include #include #include #include /* * Assume the following has been done: * 1. Opened line devices for each time slot on DTIB1. * 2. Wait for a call using gc_WaitCall() * 3. An event has arrived and has been converted to a metaevent * using gc_GetMetaEvent() or gc_GetMetaEventEx() (Windows) * 4.
For more information about the Dialogic® Global Call API, see the following documents: • Dialogic® Global Call API Library Reference • Dialogic® Global Call API Programming Guide For features specific to E1 (R2) technology, see the following documents: • Dialogic® Global Call E1/T1 CAS/R2 Technology Guide • Dialogic® Global Call Country Dependent Parameters (CDP) for PDK Protocols Configuration Guide 1.
Time Stamp : 2/25/2003, 14:28:26.702 RECEIVE Timeslot 31 UI(COMMAND) Sequence 0(0x03) Number Acknowledge Msg(0x09) Indication Field *128A*32216070#*6#*50*32205505# 1.29.3 Documentation The online bookshelf provided with Dialogic® System Release 6.0 PCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics.
1.32.1 Feature Description To test the various tones from various countries, the Tone-On/Off Call Status Transition (CST) event data have been modified to add a time stamp structure to the end of the TN_INFO structure. The CST event data are obtained by calling sr_getdatalen( ) and sr_getevtdatap( ). A new structure, TN_TIMESTAMP, is in the device header file, dxxxlib.h.
switch(sr_getevttype(ehandle)) { case TDX_CST: datap = (DX_CST *) sr_getevtdatap(ehandle); if (datap->cst_event == DE_TONEON) { tonep = (TN_INFO*)(datap+1); // tone structure starts at end of CST structure tsp = (TN_TIMESTAMP*)(tonep+1); // time stamp structure starts at end of TN_INFO structure. timestamp = tsp->tn_TimeStamp; // get the time stamp } break; . . 1.32.4 Documentation The online bookshelf provided with Dialogic® System Release 6.
int parmValue = 3; // set parameter fx_setparm(DeviceHandle, FC_MDM_RX_LVL, (void*)&parmValue); // get current setting fx_getparm(DeviceHandle, FC_MDM_RX_LVL, (void*)&parmValue); For further information about the fx_setparm( ) and fx_getparm( ) functions, see the Dialogic® Fax Software Reference. 1.
New Parameters The feature is implemented using the Dialogic® Global Call gc_SetConfigData( ) function and the GCTGT_CCLIB_CHAN parameter set. New extension event IDs define the receive raw DPNSS EEM through the GCEV_EXTENSION event. This unsolicited event can be enabled or disabled through gc_SetConfigData( ). The ISDN dm3cc_param.h header file is updated with the following: • New extension ID: DM3CC_EXT_EVT_RAWEEM.
1.34.2 Enabling/Disabling GCEV_Extension Event For the gc_SetConfigData( ) function, the bit mask (EXTENSIONEVT_RAWEEM) is saved for use later during GCEV_EXTENSION event generation. The gc_SetConfigData( ) is set on a channel basis and has the target type set as GCTGT_CCLIB_CHAN. The general procedure is to call the gc_SetConfigData( ) function to implement the change as follows: gc_SetConfigData(GCTGT_CCLIB_CHAN.EXTENSIONEVT_RAWEEM) 1.34.
int gc_err; /* GlobalCall Error Code */ int cclibid; /* Call Control library ID */ long cclib_err; /* Call Control Error Code */ char *msg; /* Error Message */ LINEDEV ldev; /* Line device */ char str[MAX_STRING_SIZE]; GC_IE_BLK gcIEBlk; IE_BLK ie_Blk; memset((unsigned char *)&ie_Blk, 0, sizeof(IE_BLK)); gcIEBlk.gclib = NULL; gcIEBlk.cclib = &ie_Blk; ie_Blk.length = 7; //length of the raw DPNSS EEM data /* EEM(C) = 0x22, EEM(I) = 0x23 */ ie_Blk.data[0] = 0x22; // raw DPNSS EEM data ie_Blk.
return 0; } To Receive Raw EEM and Extract Raw DPNSS Data void process_event(void) { .... .... ....
break; default: sprintf(str, "Unknown PARM ID"); printandlog(0, GC_APICALL, NULL, str, 0); break; } break; default: sprintf(str, "Unknown SET ID"); printandlog(0, GC_APICALL, NULL, str, 0); break; } } } 1.34.5 Documentation The online bookshelf provided with Dialogic® System Release 6.0 PCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics.
The new PDK Configuration property sheet replaces the “Downloading the Protocol and CDP File on a Windows System” procedure documented in the Dialogic® Global Call Country Dependent Parameters (CDP) for PDK Protocols Configuration Guide. With this new feature, it is no longer necessary to set up the pdk.cfg file to download the protocol and CDP file. Note: This procedure only applies to boards having network interfaces, and to trunks that are configured for the CAS or R2MF protocols. 1.
file (other than the default value) to all trunks on the board, highlight PDKTrunk 0. Otherwise proceed to step 4. 3a. From the Variant drop-down menu, select a CDP variant file by highlighting the file and clicking the Set button. Note: If you wish to remove a previously assigned CDP variant file, highlight the variant under that trunk in the window and click the Remove button. 3b. Repeat this step for each additional CDP variant file you wish to assign to all of the trunks on this board.
modified FCD file is automatically created when the PCD file and CONFIG file are downloaded to the board. 1.35.3 Documentation The online bookshelf provided with Dialogic® System Release 6.0 PCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics. For detailed information about configuring DM3 boards, see the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide.
Refer to the “Checking TCP Port Availability” section in the Dialogic® System Release 6.0 PCI for Windows Software Installation Guide. 1.
When in clear channel mode, the time slot 16 mapping is as follows: • NI TS1-NI TS15 map to dtiB1T-dtiB1T15 • NI TS17-NI TS31 map to dtiB1T16-dtiB1T30 • NI TS16 maps to dtiB1T31 Note: The application should expect a GCEV_UNBLOCKED event when gc_open( ) is called on trunks set for clear channel. 1.38.2 Configuring the Software In the CONFIG file, the Signaling Type parameter (0x1602) allows you to configure a trunk for ISDN or clear channel. All trunks are set to Net5 by default.
1.40 PBX Integration Support for Nortel BCM The Service Update adds support for Nortel Business Communications Manager (BCM) when using the Dialogic® D/82JCT-U Board. The level of support is comparable to that provided for the Nortel M7324 telephone as described in the Dialogic® PBX Integration Board User's Guide with the following notable exceptions: • The information in Section 4.5.1, “Nortel Norstar Programming Requirements” does not apply when using the Nortel BCM.
The next table prompts the user about the installation of CallPilot Voice Messaging. Refer to Nortel BCM documentation for the proper configuration of the CallPilot voice mail system.
Selecting “Yes” in the Perform Button Programming field causes a button programming menu to be displayed. Memory keys 00, 01, and 03 must be programmed as follows: Button Programming Menu Button Functionality Memory Button 00 Handsfree/Mute Memory Button 01 Intercom Memory Button 03 Transfer Memory buttons 00 and 01 are automatically programmed if the Handsfree option (in the Capabilities menu) is set to “Standard” and the Intercom Keys option (in the Line Access Menu) is set to “1” respectively.
1.42.
Some examples of commands that can be included in a dm3enum.cfg file are: board 0 b 1 board (1 3) b (1 3) The feature generates a number of log files in the Dialogic\log directory: Dm3enumreate.log Log file for application that starts dynamic protocol configuration enablement Protocol_enmurate_board_#.log Log file of actual dynamic protocol configuration enablement process for boards that use non-PDK protocols Pdkenumerate.
• “lb0pv5:analog_loop_fxs”- An analog protocol that is the fifth protocol variant on logical board 0 Note: All characters in protocol names are lowercase. The protocol ID is assigned by Global Call and the user must obtain the protocol ID prior to accessing any protocol-related data.
Obtaining the {Set ID:Parm ID} Pair for a CAS Signal Each CAS parameter in a DM3 PDK protocol has a unique {set ID:parm ID} pair, in which the set ID represents the component that contains the parameter and parm ID represents an internal ID within that component. The set ID is one of a predefined set of values in the dm3cc_parm.h file, and the parm ID is assigned by the DM3 firmware at download time.
See Section 1.42.1.5, “Sample Code for Getting and Setting CAS Signal Definitions and CDP Variable Values”, on page 120, specifically the GetCASSignalDef( ) function, for example code that demonstrates how to retrieve the definition of a CAS signal, in this case the CAS_WINKREV signal.
The gc_QueryConfigData( ) function is called with the following parameter values: • target_type = GCTGT_PROTOCOL_SYSTEM • target_id = PDK Protocol ID • source_datap = GC_PARM parameter pointer for storing the input CDP variable name • query_id = Query ID, in this case, GCQUERY_PARM_NAME_TO_ID • response_datap = GC_PARM parameter pointer for storing the output {set ID:parm ID} and value type Note: Obtaining the {set ID:parm ID} pair is a prerequisite to retrieving or changing the value of a CDP variable.
• target_datap = GC_PARM_BLKP parameter pointer, as constructed by the utility function gc_util_insert_parm_val( ) for the CDP integer value and gc_util_insert_parm_ref( ) for the CDP string value. • time_out = time interval (in seconds) during which the parameter value must be updated. If the interval is exceeded, the update request is ignored. This parameter is supported in synchronous mode only, and it is ignored when set to 0.
/* Obtain the protocol Name */ t_pParmData = gc_util_find_parm(t_pParmBlk, GCSET_PROTOCOL, GCPARM_PROTOCOL_NAME); if (NULL != t_pParmData) { strcpy(a_pProtName, (const char*)t_pParmData->value_buf); } printf("ObtainProtocolIDAndName(linedev:%d, protocol_id:%d, protocol_name:%s)", a_GCLineDevH, *a_pProtID, a_pProtName); gc_util_delete_parm_blk(t_pParmBlk); return t_result; } int QueryParmID(long a_PDKProtocolID, char *a_pParmName, unsigned short * a_pSetID, unsigned short * a_pParmID, unsigned char * a_pValT
switch (t_ValType) { case GC_VALUE_CAS_TRANS: gc_util_insert_parm_ref(&t_pParmBlk, t_SetID, t_ParmID, sizeof(GC_CASPROT_TRANS), &t_CasTrans); break; case GC_VALUE_CAS_PULSE: gc_util_insert_parm_ref(&t_pParmBlk, t_SetID, t_ParmID, sizeof(GC_CASPROT_PULSE), &t_CasPulse); break; case GC_VALUE_CAS_TRAIN: gc_util_insert_parm_ref(&t_pParmBlk, t_SetID, t_ParmID, sizeof(GC_CASPROT_TRAIN), &t_CasTrain); break; default: /* Process the error here */ return -1; break; } /* Set the CAS_WINKRCV with new value */ t_result
&t_CasTrain); break; default: /* Process the error here */ return -1; break; } /* Get the CAS_WINKRCV with new value */ t_result = gc_GetConfigData(GCTGT_PROTOCOL_SYSTEM, a_PDKProtocolID, t_pParmBlk, 0, &t_RequestID, EV_ASYNC); if (t_result) { /* Process the error */ gc_util_delete_parm_blk(t_pParmBlk); return t_result; } gc_util_delete_parm_blk(t_pParmBlk); return t_result; } typedef struct { char name[50]; int type; void * valuep; } CDP_PARM; int GetCDPVarParms(long a_PDKProtocolID, int a_NumParms, CDP_P
/* Insert new definition for CDP variable signals, dependent on the value data type */ switch (t_ValType) { case GC_VALUE_SHORT: gc_util_insert_parm_val(&t_pParmBlk, t_SetID, t_ParmID, sizeof(unsigned short), 0); break; case GC_VALUE_STRING: gc_util_insert_parm_ref(&t_pParmBlk, t_SetID, t_ParmID, 30, ""); break; case GC_VALUE_ULONG: gc_util_insert_parm_val(&t_pParmBlk, t_SetID, t_ParmID, sizeof(unsigned long), 0); break; case GC_VALUE_UCHAR: gc_util_insert_parm_val(&t_pParmBlk, t_SetID, t_ParmID, sizeof(uns
return -1; } if (!a_CDPVarParms) { /* Process the error */ return -1; } /* Support setting multiple CDP variables in a single gc_SetConfigData() function call */ for (index1 = 0; index1 < a_NumParms; index1 ++) { /* Find the {setID, parmID, valueType} of each CDP variable by its name: e.g., "CDP_ANI_ENABLED" in pdk_ar_r2_io.cdp */ t_result = QueryParmID(a_PDKProtocolID, a_CDPVarParms[index1].
/* Set the CDP parameters with new values */ *a_pRequestID = 0; t_result = gc_SetConfigData(GCTGT_PROTOCOL_SYSTEM, a_PDKProtocolID, t_pParmBlk, 0, GCUPDATE_IMMEDIATE, a_pRequestID, EV_ASYNC); if (t_result) { /* Process the error */ printf("gc_SetConfigData(protocol_id:%d) failed on setting CDP parameters()", a_PDKProtocolID); *a_pRequestID = 0; } else { printf("gc_SetConfigData(protocol_id:%d, req_id:0x%x) succeed on setting CDP parameters", a_PDKProtocolID, *a_pRequestID); } gc_util_delete_parm_blk(t_pParm
t_pCasTrain->PreTrainIntervalNom, t_pCasTrain->PostTrainIntervalNom, t_pCasTrain->PulseIntervalMin, t_pCasTrain->PulseIntervalNom, t_pCasTrain->PulseIntervalMax); } else { printf("Error! Incorrect value_size =%d for {setID:0x%x, parmID:0x%x}", t_pParmData->value_size, t_pParmData->set_ID, t_pParmData->parm_ID); } } else if (t_pParmData->set_ID == PRSET_TSC_VARIABLE) { /* This is a TSC Variable */ switch (t_pParmData->value_size) { case 1: /* Unisgned char data */ memcpy(&t_UCharVal, &t_pParmData->value_buf,
LINEDEV char long } port[120]; LineDev; DevName[50]; ProtocolID; /* GlobalCall line device handle */ void process_event() { METAEVENT metaevent; int evttype; GC_RTCM_EVTDATA * t_pRtcmEvt = NULL; int t_Result = 0; int index = 0; struct channel *pline = NULL; char t_ProtocolName[30]; int t_NumParms = 0; int t_RequesID = 0; CDP_PARM t_CDPVarParms[3] = { {"CDP_IN_WinkStart", GC_VALUE_INT, 0}, {"CDP_OUT_WinkStart", GC_VALUE_INT, 0}, {"CDP_OUT_Send_Alerting_After_Dialing", GC_VALUE_INT, 0} }; /* Populate the
{ break; } printf("Received GCEV_GETCONFIGDATA EVENT on target_type=%d, target_id=0x%x, rquest_id=0x%x", t_pRtcmEvt->target_type, t_pRtcmEvt->target_id, t_pRtcmEvt->request_ID); ProcessRTCMEvent(evttype, t_pRtcmEvt->request_ID, t_pRtcmEvt->retrieved_parmblkp); break; /* RETURN POINT!!!!! */ break; case GCEV_SETCONFIGDATA: t_pRtcmEvt = (GC_RTCM_EVTDATA *) metaevent.
be issued on all channels (time slots) prior to issuing gc_SetConfigData( ) to prevent incoming calls. If there are any active calls present at the time the gc_ResetLineDev( ) or gc_SetConfigData( ) function is issued, they are gracefully terminated internally. The application does not receive GCEV_DISCONNECTED events when calls are terminated in this manner.
• target_datap = GC_PARM_BLKP parameter pointer, as constructed by the utility function gc_util_insert_parm_val( ) • time_out = time interval (in seconds) during which the target object must be updated with the data. If the interval is exceeded, the update request is ignored. This parameter is supported in synchronous mode only, and it is ignored when set to 0.
Specifying the Protocol for a Trunk The protocol used by a trunk can be dynamically configured after devices have been opened using the gc_SetConfigData( ) function. All channels on the affected trunk inherit the newly selected protocol. The gc_SetConfigData( ) function uses a GC_PARM_BLK structure that contains the configuration information. The GC_PARM_BLK is populated using the gc_util_insert_parm_ref( ) function.
The following code example shows how to dynamically configure a T1 trunk to operate with the 4ESS protocol.
int target_type; long target_id; } GC_RTCM_EVTDATA, *GC_RTCM_EVTDATAP; /* /* /* /* used for gc_GetConfigData() in */ asynchronous mode */ Target type */ Target ID */ The addition of the target_type and target_id fields enables applications to easily identify the DM3 protocol object associated with an event. The change is backward-compatible with usage in current applications.
unsigned short unsigned short unsigned short unsigned short unsigned short unsigned short of the pre-pulse (in msec) */ /* The minimum time for the duration of the post-pulse (in msec) */ PrePulseIntervalNom; /* The nominal time for the duration of the pre-pulse. Ignored in DM3: always 0 */ PostPulseIntervalNom; /* The nominal time for the duration of the post-pulse (in msec).
Set ID CCSET_LINE_CONFIG Parm IDs CCPARM_LINE_TYPE CCPARM_CODING_TYPE GCSET_PROTOCOL GCPARM_PROTOCOL_ID GCPARM_PROTOCOL_NAME 1.42.3 PRSET_CAS_SIGNAL (defined in dm3cc_parm.h) The parm ID is dynamically generated. PRSET_TSC_VARIABLE (defined in dm3cc_parm.h) The parm ID is dynamically generated.
• This feature supports the setting and retrieval of multiple CDP variable values in a single API call, but it does not support the mixing of CDP variables with other parameters when setting or retrieving values. • To set the values of the CDP_IN_ANI_Enabled and CDP_OUT_ANI_Enabled parameters in the pdk_us_mf_io.cdp file, the user is required to remove feature_ANI from the SYS_FEATURES section of the CDP file.
1.43.1 Supported Products The line adaptation utility (LineAdapt) is supported on the following analog front-end boards. Springware Boards: • Dialogic® D/41JCT-LS Media Boards (North American version) • Dialogic® D/120JCT-LS Rev. 2 Media Boards (North American version) DM3 Boards: • Dialogic® DMV160LP Media Boards (but not the Dialogic® DMV160LPHIZ high impedance, or HiZ version) • Dialogic® DI0408LSAR2 Switching Boards (this is the Rev. 2 version) 1.43.
1.43.4 Line Adaptation Procedures This section contains the following topics: • Location and Description of the Utility and Component Files • Line Adaptation Procedure • Configuration File Tasks 1.43.4.1 Location and Description of the Utility and Component Files The following list provides a brief description and the location of the line adaptation utility along with its required components and associated files.
• Post-Discovery: Reconfigure and Initialize the Boards, and Test the System for Normal Use Requirements for Line Adaptation You must meet the following requirements for the line adaptation discovery phase. • The analog telephone lines and boards that require adaptation have been identified (referred to as the target boards/lines). • The target boards are configured and able to function. • The telephone lines are attached to the target boards/channels.
PCDFileName (DM3 Boards) Board DMV160LP DMV160LP.PCD DI0408LSAR2 DI0408LSA_REV2_ML2.PCD DI0408LSA_REV2_ML3.PCD DI0408LSA_REV2_ML4.PCD FirmwareFileName (Springware Boards) 4. Save the configuration and repeat the configuration procedure for all target boards. 5. Start the target boards using DCM. Execute the LineAdapt Utility to Discover Optimum Settings Use the following procedure to execute the LineAdapt utility and discover the optimum settings for the target boards: 1. Open a command window. 2.
Note: You can run the utility again later and select individual boards to add to the configuration. For each board selected, the utility displays a prompt for selecting the target channels, similar to the following: Enter the Channels you would like to adapt on # in slot /. ‘A’ for All or ‘Q’ to Quit > 5. To select all channels on the specified board, type A or a and press the Enter key. To select one or more individual channels, type the channel numbers separated by a space (e.
1.43.4.3 Configuration File Tasks The following list describes some important tasks for using the LineAdapt utility and its configuration file. These tasks relate to certain actions that affect the contents of the configuration file. For more information on these actions and their effects, see Discovery, Initialization, and Storage of Optimum Settings in Section 1.43.5, “LineAdapt Utility Command Line Interface”, on page 145.
number only if the same telephone lines are attached to the same port locations on the same type of board. See the following topic on Board and Channel Identification in the LineAdaptOptCoef.xml Configuration File. Note: You must also change other configuration files in which the board is identified.
The #0 and #1 represent the logical ID or board ID. The slot 1/11 and slot 2/3 represent the bus and slot numbers, which identify the unique location of the boards. See the following valid values for the Name and Type parameters. Warning: Do not change the board Name or Type. The optimum settings are specific to the category of board (board name and architecture type). The values for these parameters are only shown to help you identify specific boards.
• LineAdapt Command Line Parameters Prompting Mode and Command Mode The LineAdapt utility can run in either Prompting Mode or Command Mode: Prompting Mode Displays a list of boards and channels and prompts the user to select the adaptation targets. You can invoke the utility in Prompting Mode by running it without any command line parameters. You can also use the -d, -t, and -v parameters in Prompting Mode (see Table 1).
specific slot. If you replace a board with the same type of board in the same slot and attach the trunk cables to the same port locations on the board, you do not need to make any changes to the configuration file or re-adapt for the new board. The same optimum settings apply to the new board. • If you perform discovery with the utility, it always results in board initialization with the optimum settings discovered. • Storage of optimum settings depends upon the command line parameter used.
When the command line does not specify any parameters, it executes the utility in Prompting Mode, which displays a list of boards and channels and prompts the user to select the adaptation targets. You can also use the -d, -t, and -v parameters in Prompting Mode (see Table 1). For operation details, see Execute the LineAdapt Utility to Discover Optimum Settings in Section 1.43.4.2, “Line Adaptation Procedure”, on page 139. -a Adapts all channels on all supported and recognized boards.
channel numbers on the board). If channel targets are not specified (i.e., if the -c parameter is not used), the default is all channels on the board. Syntax example: LineAdapt -b0 -s1 -c1 -c2 -c8-12 This command adapts channels 1 and 2 and channels 8 through 12 on the target board in bus 0, slot 1. The command performs discovery on the specified targets, stores the optimum coefficients in the LineAdaptOptCoef.xml file for initialization with future downloads, and initializes the boards with the settings.
discovered are used to initialize the target boards when the discovery is complete. However, since the settings are not stored, they will not be used to initialize the target boards in the next download or system startup. If the -t parameter is not specified, the utility will discover the optimum coefficients for the specified channels and store them in the LineAdaptOptCoef.xml file for initialization with future downloads. The -t parameter can also be used in Prompting Mode.
1.44.1 Feature Description Currently, bearer channel time slots on DM3 Boards are numbered from 1 to 15 and 17 to 31 for the QSIG protocol. Channel 16 is reserved for signaling. Thus, the QSIG stack will reject any calls with the channel identification information element set to 16, as it assumes that channel 16 is reserved for signaling data.
1.44.2 Documentation The online bookshelf provided with Dialogic® System Release 6.0 PCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics. For more information about configuration files, configuration parameters, and configuration procedures, see the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide.
Application Global Call API IP Signaling IP Network RTP/RTCP IP Signaling CC Lib IP Media Service (IPMEDIA.EXE) IP Media Library IP Media Commands Host NIC DM3 Device Driver Host Computer DI0408LSAR2 Board Note: It is also possible to specify one NIC for RTP/RTCP and, via Global Call, assign a different NIC for signaling and data. See Section 1.46, “Dialogic® DI0408LSAR2 Board Support for Host Systems with Multiple NICs”, on page 159. 1.45.
• Full-duplex communication with all coders. Supported coders are: Frames per Packet Coder Frame Size (milliseconds) VAD G.711 1 20, 30 N/A G.723.1, 5.3 kbps 2, 3 30 Supported G.723.1, 6.3 kbps 2, 3 30 Supported G.729 Annex A 2-4 10 Disabled G.729 Annex A with Annex B 2-4 10 Enabled GSM FR 2, 3 Supported • H.
di0408lsa_REV2_ML3.config. See the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide for more information about media loads and configuration file sets. There are five media loads for the DI0408LSAR2 Board.
• Twelve channels of IP telephony shareable across the system via the CT Bus/SCbus DI0408LSAR2 Devices For the DI0408LSAR2 media loads, device enumeration follows the rules listed below. Note: The scenario below assumes that the DI0408LSAR2 Board is the only board in the system. Call the dx_getfeaturelist( ) function to return information about the features supported on the device. (Refer to the Dialogic® Voice API Library Reference for function details.
– For media load 3: dxxxB6C1 and dxxxB6C2 – For media load 4: dxxxB7C1 and dxxxB7C2 Application control is provided by the fx_ APIs.
Configuring ToS in the CONFIG File With this release, a new parameter for configuring ToS has been added to the DI0408LSAR2 Board CONFIG files that support IP. Previously, this parameter was applicable to DM/IP Boards only. Note: For more detailed information about modifying the CONFIG file and generating a new FCD file, refer to the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide.
This parameter sets the ToS bits in the IP header of transmitted datagrams to improve the mobility of packets. Values are: 0x10: LOWDELAY selects a minimum delay link or circuit for the datagram 0x08: THROUGHPUT selects a high throughput link or circuit for the datagram 0x04: RELIABILITY selects a high reliability link or circuit for the datagram 0x02: MINCOST selects a minimum cost link or circuit for the datagram 0x00: No Priority the datagram has no priority assigned 1.45.
Application IP Network GlobalCall API Host NIC IP Signaling IP Network IP Signaling CC Lib IP Media Library IP Media Service IP Media Commands RTP/RTCP Host NIC DM3 Device Driver Host Computer DI0408LSAR2 Board The IP Media Service uses the specified NIC IP address when establishing RTP media sessions. If no IP address was specified, the selection is done automatically as explained above.
1.47 Support for QSIG NCAS Calls on Dialogic® DM3 Boards With the Service Update, the ability to initiate Non-Call Associated Signaling (NCAS) calls is supported for the QSIG protocol (E1 or T1) on Dialogic® DM3 Boards.
Note the following differences between NCAS implementation on Dialogic® Springware Boards and on DM3 Boards: DM3 Boards Springware Boards Channel used to make NCAS calls for T1 spans 23 (dtiBxT23) 24 (dtiBxT24) Channel used to make NCAS calls for E1 spans 30 (dtiBxT30) 30 (dtiBxT30) Number of simultaneous NCAS calls per D channel 8 (32 total for board with 4 spans) 16 For more information about using NCAS, see the Dialogic® Global Call ISDN Technology Guide.
gc_util_insert_parm_val(pParmBlk, GCIS_SET_BEARERCHNL, GCIS_PARM_TRANSFERRATE, sizeof(int), PACKET_TRANSFER_MODE); The application must also build the Facility IE (e.g., with MWI information) using gc_SetInfoElem( ) before making the call using gc_MakeCall( ). The following diagram illustrates the API sequence for an MWI activation with connect scenario. Successful MWI Activate.
The following diagram illustrates the API sequence for an MWI activation without connect scenario. Successful MWI Activate.Invoke (without Connect) GC libs and protocol stack Application Network gc_Open() dtiBxT23 (T1) or dtiBxT30 (E1) gc_Open return devh gc_SetInfoElem() Build MWI Activate.
The following diagram illustrates the API sequence for an MWI deactivate with connect scenario. Successful MWI Deactivate.Invoke (with Connect) GC libs and protocol stack Application Network gc_Open() dtiBxT23 (T1) or dtiBxT30 (E1) gc_Open return devh gc_SetInfoElem() Build MWI Deactivate.
The following diagram illustrates the API sequence for an MWI deactivate without connect scenario. Successful MWI Deactivate.Invoke (without Connect) GC libs and protocol stack Application Network gc_Open() dtiBxT23 (T1) or dtiBxT30 (E1) gc_Open return devh gc_SetInfoElem() Build MWI Deactivate.
Inbound QSIG NCAS Call Scenarios The following diagram illustrates the API sequence for an MWI interrogate with connect scenario. Successful MWI Interrogate.Result (with Connect) GC libs and protocol stack Application Network gc_Open() dtiBxT23 (T1) or dtiBxT30 (E1) gc_Open return devh gc_WaitCall() Wait for a call on T23 or T30 for COCI gc_WaitCall() return SETUP (Fac IE: MWI Interrogate.Invoke) PROCEEDING GCEV_OFFERED gc_SetInfoElem() Build MWI Interrogate.
The following diagram illustrates the API sequence for an MWI interrogate without connect scenario. Successful MWI Interrogate.Result (without Connect) GC libs and protocol stack Application Network gc_Open() dtiBxT23 (T1) or dtiBxT30 (E1) gc_Open return devh gc_WaitCall() Wait for a call on T23 or T30 for COCI gc_WaitCall() return SETUP (Fac IE: MWI Interrogate.Invoke) PROCEEDING GCEV_OFFERED gc_SetInfoElem() Build MWI Interrogate.
Inbound QSIG NCAS Call Detection Code Example The following code segment demonstrates how to retrieve the call type from the GCEV_OFFERED event triggered by an incoming call to determine if the call is an NCAS call or a standard circuit-switched call. case GCEV_OFFERED: GC_PARM_BLKP gcParmBlkp = NULL; GC_PARM_DATAP t_gcParmDatap = NULL; EXTENSIONEVTBLK *ext_evtblkp = NULL; ext_evtblkp = (EXTENSIONEVTBLK *)meta_event.
For features specific to ISDN technology, see: • Dialogic® Global Call ISDN Technology Guide Note: The online bookshelf has not been updated for this feature, so the Dialogic® Global Call ISDN Technology Guide does not currently indicate that NCAS is supported for QSIG on DM3 Boards. 1.48 Loop Current Reversal Detection on Dialogic® DMV160LP Boards The Service Update adds support for loop current reversal detection on the Dialogic® DMV160LP Media Board. 1.48.
Call Flow Sequence Function Events Received Pre-call - Loop current is off. Application makes outbound call. gc_MakeCall( ) Called (far end) party answers the call. GCEV_EXTENSION(CC_CST_LCON) GCEV_DIALING GCEV_ALERTING GCEV_EXTENSION(CC_CST_LCREV) GCEV_CONNECTED Near end drops the call. gc_DropCall( ) GCEV_EXTENSION(CC_CST_LCOFF) GCEV_DROPCALL Application frees the device for another call.
• CC_CST_LCREV These defines will be part of the GC_PARM_BLK structure that will be associated with the GCEV_EXTENSION event that the application receives. The application parses the GC_PARM_BLK to determine the call status transition reason.
case CC_CST_LCOFF: cout << "LCOFF detected" << endl; break; case CC_CST_LCREV: cout << "LCREV detected" << endl; break; } break; default: cout << "Unknown PARM ID" << endl; break; } break; default: cout << "Unknown SET ID" << endl; break; } } 1.48.3 Updating the CONFIG File After installing the Service Update, the following parameter requires configuration in the dmv160lp.
1.49 Adjusting DTMF Characteristics through the CONFIG File With the Service Update, Dialogic® DM/V-A and DM/V-B Media Boards now support the ability to modify DTMF parameter values. This new functionality is provided through the configuration file set. Changed values take effect at the time the firmware is downloaded to the board using the Dialogic® Configuration Manager (DCM) utility.
Table 2. DTMF Characteristics and Default Values DTMF DTMF 1 DTMF 2 DTMF 3 DTMF 4 DTMF 5 DTMF 6 Characteristic Default Value Signal Id 58977 Label 1 Segment Count 1 Segment Signal Type 2 Segment Frequency 1 (Hz) 697 Segment Amplitude 1 (.25 dbm) -24 Segment Frequency 2 (Hz) 1209 Segment Amplitude 2 (.
Table 2.
Table 2. DTMF Characteristics and Default Values (Continued) DTMF DTMF # DTMF * DTMF comma 1.49.
For more information about configuration files, configuration parameters, and configuration procedures, see the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide. Note: The online bookshelf has not been updated for this feature, so the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide does not currently include information about adjusting DTMF characteristics through the CONFIG file. 1.
Changing a board’s characteristics (e.g., increasing/decreasing the number of devices) is not allowed when performing a single board start/stop operation. No loads or any parameter changes that could impact the density are allowed, otherwise download will fail. If this has to be done, then the entire system has to be stopped and restarted. Addressable unit identifiers (AUIDs) may change for virtual boards (e.g., dxxxB4) and virtual devices (e.g., dtiB2C3) after a single board stop/start.
1.50.2 Stand-Alone Configuration A new feature is supported for system configuration, with each board functioning independently without TDM bus connectivity. Each board is configured as a Primary Master, deriving its clock reference either externally via its first network interface (digital boards) or by using its internal oscillator (analog boards). No inter-board connectivity (i.e., routing or resource sharing) is possible.
1.50.3 Firmware Assert Notification In order to enable the firmware assert notification feature, an application should call brd_Open( ) with new a mode parameter, BRD_FW_ASSERT_ENABLE. (Previously, the mode parameter was documented as reserved for future use.) The new mode parameter is found in devmgmt.h header. The application will need to link with the device management library (libdevmgmt). Each physical board that the application wants firmware assert notification for must be opened with brd_Open( ).
printf("event %x\n", nEvtType); printf("data: %s\n", sr_getevtdatap()); dx_close(nDev); brd_Close(nDev1); } 1.50.4 Documentation The online bookshelf provided with Dialogic® System Release 6.0 PCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics.
1.51.1.1 General Conditions for SIP Call Transfers SIP call transfer uses the REFER method (with NOTIFY support) to reroute a call (a SIP dialog) after the call has been established; in other words, after two endpoints have an established media path. There are two fundamental types of call transfer: • Unattended transfer, which is referred to as “blind transfer” in most other technologies and protocols.
Interoperability Issues The latest standards for the SIP REFER method are defined in IETF RFC 3515, published in April 2003. The current Global Call implementation is compliant with RFC 3515, but many existing implementations of REFER are based on the previous draft of the REFER method and are not fully compliant. The most significant non-compliance issues are: • No initial NOTIFY after sending out 202 accept to REFER request. • No subscription state information in NOTIFY message.
party A’s responsibility to update the application transfer states in this case. This is a common scenario in blind transfer where party A does not care about the transferred call status and drops the primary call immediately after receiving a INVOKE_XFER_ACCEPTED event. When the REFER subscription is terminated, party A rejects subsequent NOTIFY messages.
If the CRNp number is included during the gc_MakeCall( ) on CRNt and the primary call is in the connected state, then a GCEV_XFER_CMPLT event is generated on CRNp once the transferred call is connected. If the CRNp number is not included, there will be no notification to the primary call and/or party A of the transferred call status. The CRNp number must not be included in the gc_MakeCall() if primary call was disconnected prior to making transferred call.
transferred call. Referred-By and Replaces information, if present, is also attached to GCEV_OFFERED events if SIP header access was enabled (by setting the IP_SIP_MSGINFO_ENABLE value in the sip_msginfo_mask field of the IP_VIRTBOARD data structure) when the virtual board was started. At that point, the application may retrieve the typical calling party information on CRNt.
Figure 1. Successful SIP Unattended Call Transfer, Party A Notified with Connection Pre condition: Primary call between A and B is connected (not shown).
Figure 2. Successful SIP Unattended Call Transfer, Party A Notified with Ringing Pre condition: Primary call between A and B is connected (not shown).
Figure 3. Successful SIP Unattended Call Transfer, Party B Terminates REFER Subscription prior to Notification of Transferred Call Status Pre condition: Primary call between A and B is connected (not shown).
Figure 4. Successful SIP Unattended Call Transfer, Party A Clears Primary Call prior to Transfer Completion Precondition: Primary call between A and B is connected (not shown).
Figure 5. Successful SIP Unattended Call Transfer, Party B Clears Primary Call prior to Transfer Completion Pre condition: Primary call between A and B is connected (not shown).
Completion of a successful attended transfer results in the eventual termination of the primary and secondary calls, and the creation of the transferred call between party B and the party C. Transferor or Transferring Endpoint (Party A) SIP does not support or require a transfer initiation process to obtain the rerouting number as in H.323/H.450.2 supervised transfer.
an unattended transfer. In this case, the gc_InvokeXfer( ) call only includes the CRN of the primary call. Transferee or Transferred Endpoint (Party B) This endpoint behaves in the same manner as in unattended transfer with one exception: the INVITE that is sent from Party B to Party C for the transferred call contains a Replaces header that is obtained from the replace parameter in the Refer-To header of the REFER from Party A.
Successful SIP Attended Call Transfer Figure 6 illustrates the basic scenario for successful SIP attended call transfer. The scenario illustrates the use of a gc_InitXfer( ) function call, which is not required in SIP. The GCEV_INIT_XFER completion event in this case contains a dummy rerouting address. Figure 6. Successful SIP Attended Call Transfer Pre condition: Primary call between A and B is connected (not shown). Secondary (consultation) call between A and C is connected (not shown).
Attended Transfer When REFER Is Not Globally Supported If protecting or exposing the Transfer Target is not a concern, it is possible to complete an attended transfer when only the Transferor and one other party support REFER. Note that a 405 Method Not Allowed might be returned instead of the 501 Not Implemented response. Figure 7. SIP Attended Call Transfer, Recovery from REFER Unsupported Pre condition: Primary call between A and B is connected (not shown).
activated such as forking or sequential searching which may result in the triggered INVITE reaching the wrong User Agent. To prevent an incorrect UA answering the INVITE, a Require: replaces header field is included in the Refer-To. This ensures that only the UA which matches the Replaces dialog will answer the INVITE, since any incorrect UA which supports Replaces will reply with a 481 and a UA which does not support Replaces will reply with a 420.
INVOKE_XFER_REJ or INVOKE_XFER_FAIL event with cause. No NOTIFY will be sent from party B to party A if REFER is not accepted by 202 Accepted from party B. The primary call and secondary call, if any, remain in connected state after any transfer failure.
termination event. The original primary call is left connected and in the GCST_CONNECTED state from the perspective of both party A and party B. Figure 10. SIP Call Transfer Failure - No Response from Party B Pre condition: Primary call between A and B is connected (not shown).
GCEV_INVOKE_XFER_FAIL termination event. The original primary call is left connected and in the GCST_CONNECTED state from the perspective of both party A and party B. Figure 12. SIP Call Transfer Failure - REFER Subscription Expires Pre condition: Primary call between A and B is connected (not shown).
Figure 13. SIP Call Transfer Failure - No Response from Party C Pre condition: Primary call between A and B is connected (not shown).
Figure 14. SIP Call Transfer Failure - Party B Drops Transferred Call Early Pre condition: Primary call between A and B is connected (not shown).
Figure 15. SIP Call Transfer Failure - Party C Is Busy When Transfer Attempted Pre condition: Primary call between parties A and B is connected (not shown). Party C has call connected to another party (not shown).
. . INIT_IPCCLIB_START_DATA(&ipcclibstart, 2, ip_virtboard); INIT_IP_VIRTBOARD(&ip_virtboard[0]); INIT_IP_VIRTBOARD(&ip_virtboard[1]); ip_virtboard[0].sup_serv_mask = IP_SUP_SERV_CALL_XFER; /* override supp services default */ ip_virtboard[1].sup_serv_mask = IP_SUP_SERV_CALL_XFER; /* override supp services default */ . .
1.51.3.2 Invoking an Unattended Call Transfer The following code snippet illustrates how to invoke an unattended (blind) transfer on a channel that is in the connected state. In this example, the Refer-To header field of the REFER message that is sent is set to “sip:500@192.168.1.10”, while the Referred-By header field is automatically populated by Global Call. int Gc_InvokeXfer(int channel) { INT32 rc; GCLIB_MAKECALL_BLK t_gclibmakecallblk; GC_MAKECALL_BLK t_gcmakecallblk = {0}; char invokeaddr[] = "192.
/* Invoke transfer */ rc = gc_InvokeXfer(session[primaryChannel].crn, session[secondaryChannel].crn, 0, 0, 0, EV_ASYNC); if(GC_SUCCESS != rc) { printf("GC_APP : [%d] Invoke Xfer failed!!!\n",primaryChannel); return GC_ERROR; } return GC_SUCCESS; } 1.51.3.4 Processing Asynchronous Call Transfer Events The following code snippets illustrate how to handle the asynchronous events that notify applications of the call transfer status as a SIP call transfer proceeds.
case GCEV_REQ_XFER: // Incoming transfer request GC_REROUTING_INFO *pRerouteInfo = (GC_REROUTING_INFO *)metaEvent.extevtdatap; printf("Reroute number = %s\n", pRerouteInfo->rerouting_num); if(NULL != pRerouteInfo->parm_blkp) { // Handle parm blocks } strcpy(session[g_extIndex].rerouting_num,pRerouteInfo->rerouting_num); session[g_extIndex].
if(gc_ResultValue(pEvent, &gcError, &ccLibId, &ccError) { gc_ResultMsg(LIBID_GC, (long) gcError, &GCerrMsg); gc_ResultMsg(ccLibId, ccError, &errMsg); == GC_SUCCESS) printf("Ld 0x%lx, GC (%d) %s, CC (%ld) %s, (%s)\n", evtDev, gcError, GCerrMsg, ccError, errMsg, ATDV_NAMEP(evtDev)); } } 1.51.3.5 Handling a Transfer Request The following code snippet illustrates how party B handles an incoming transfer request (REFER). Party B can either reject the request or accept it.
gc_util_insert_parm_val(&t_pParmBlk, GCSET_SUPP_XFER, GCPARM_PRIMARYCALL_CRN, sizeof(unsigned long), session[channelPrimary].crn); t_gclibmakecallblk.ext_datap = t_pParmBlk; t_gclibmakecallblk.destination = session[channelPrimary].rerouting_addrblk; int frc = gc_MakeCall(session[channelXfer].ldev, &session[channelXfer].crn, NULL, &t_gcmakecallblk, 0, EV_ASYNC); if((GC_SUCCESS != frc) ||(0 == session[channelXfer].
gc_MakeCall( ) at party B can be copied from either element, but must not be a concatenation of both elements because they each contain the same character string.
1.51.4.4 gc_InvokeXfer( ) Variances for IP This function is only available if the call transfer supplementary service was enabled via the sup_serv_mask field in the IP_VIRTBOARD structure when the board device was started. Variance for SIP The application at party A may optionally be notified by a GCEV_INVOKE_XFER_ACCEPTED event that the transfer request has been accepted by the remote party to which it was sent. (This event has no equivalent in H.450.2.
Table 3. gc_InvokeXfer( ) Supported Parameters for SIP (Continued) Parameter numberstr Meaning For attended (supervised) call transfers, this parameter is ignored. Set to NULL. For an unattended (blind) call transfer, the address of party C (the rerouting address, which will be signaled to party B) as a string.
1.52 Early Media With the Service Update, early media when using H.323 on Dialogic® DM/IP Boards is now supported. 1.52.1 Enabling Early Media To enable early media on a board level, add the following PrmEarlyMedia parameter content in the CONFIG file that corresponds to the PCD file in use on your board: [0x40] SetParm=0x400a,1 ! PrmEarlyMedia (0=Disabled, 1=Enabled) After the parameter is added, generate an updated FCD file and start system services on the board.
figure as “FSE”) that can be sent within the messages of the H.225 Setup exchange rather than using the H.245 messages. (This minimizes the number of round-trip message exchanges and avoids the latency of H.245 channel establishment.) As a calling endpoint, the Global Call library enables media after Alerting is received if the called endpoint supports the fastStart mode. As a called endpoint, the Global Call library enables media in a fastStart connection after the application calls gc_AcceptCall( ).
the case of hardware other than an IPT Board, this means that media is not enabled at all until Connect. Figure 17. H.323 Early Media, SlowStart Mode Pre condition: Both line devices are IDLE. Called party has executed gc_WaitCall(). SlowStart is enabled. Tunneling is enabled.
1.52.2.4 SIP SlowStart Mode (Calling UA Answers SDP) When a SIP application sets the optional SlowStart parameter, it specifies that the INVITE message it sends will not contain SDP, so that it is up to the called UA to offer SDP which the calling UA will subsequently answer. In SIP terminology, this is known as delayed offer. Figure 19. SIP Early Media, Calling UA Answers SDP Pre condition: Both line devices are IDLE. Called party has executed gc_WaitCall(). "SlowStart" is enabled.
ipm_ModifyMedia( ) modify properties of active media session Name: int ipm_ModifyMedia(nDeviceHandle, *pMediaInfo, eDirection, usMode) Inputs: int nDeviceHandle • IP Media device handle IPM_MEDIA_INFO *pMediaInfo • pointer to media information structure eIPM_DATA_DIRECTION eDirection • data flow direction unsigned short usMode • async or sync mode setting Returns: 0 on success -1 on failure Includes: srllib.h ipmlib.
Parameter Description eDirection media operation enumeration The eIPM_DATA_DIRECTION data type is an enumeration which defines the following values: • DATA_IP_RECEIVEONLY – receive data from the IP network but do not send data • DATA_IP_SENDONLY – send data to the IP network but do not receive data • DATA_IP_TDM_BIDIRECTIONAL – full duplex data path between IP network and TDM • DATA_IP_INACTIVE – allow RTCP while blocking RTP packets • DATA_IP_NULL – do not modify the direction of the current session; th
EIPM_INV_STATE Invalid state. Initial command did not complete before another function call was made. EIPM_SYSTEM System error Example The following sample code changes the coder from G.711 mu-law to G.711 A-law and also changes the direction. #include #include #include #include typedef long int(*HDLR)(unsigned long); void CheckEvent(); void main() { /* . . Main Processing . .
if (ipm_StartMedia(nDeviceHandle, &MediaInfo, DATA_IP_TDM_BIDIRECTIONAL, EV_SYNC) == -1) { printf("ipm_StartMediaInfo failed for device name = %s with error = %d\n", ATDV_NAMEP(nDeviceHandle), ATDV_LASTERR(nDeviceHandle)); /* . . Perform Error Processing . .*/ } /* . . Continue processing . */ MediaInfo.unCount = 2; MediaInfo.MediaData[0].eMediaType = MEDIATYPE_REMOTE_CODER_INFO; MediaInfo.MediaData[0].mediaInfo.CoderInfo.eCoderType = CODER_TYPE_G711ALAW64K; MediaInfo.MediaData[0].mediaInfo.CoderInfo.
1.53 Global Call SS7 Enhancements The Service Update includes some enhancements to Dialogic® Global Call SS7: • Enhances the robustness against an abrupt Global Call application exit • Brings the gc_MakeCall( ) function timeout behavior in line with the Global Call specification, i.e., specifies the time interval (in seconds) during which the call must be established 1.
dcb_DeleteBridge( ) function deletes a conference bridge. The conference bridging feature uses the TS_BRIDGECDT data structure to provide information about the conference bridge. Notes:1. Since the DI Boards support fixed routing, all resources (player, recorder, etc.) are permanently coupled to the station interface device and cannot be routed to a conference. This means that prompts cannot be played into a conference using resources from these boards.
For further information about CDP files, see the Dialogic® Global Call Country Dependent Parameters (CDP) for PDK Protocols Configuration Guide. 1.56 New Channel Block Timer for NTT Protocol A new channel block timer parameter has been added to the ntt.prm file for the ISDN NTT protocol. The purpose of this timer is to block the first response (i.e., PROCEEDING, ALERTING, or CONNECT) to an incoming call (i.e.
Problematical Sequence T1 Trunk NTT ISDN Network SetUp (CRN=104) Preferred/Channel Number=12 Call Proc. (CRN=104) Exclusive/Channel Number=12 Alerting (CRN=104) Connected State Disconnect (CRN=104) Channel Number=12 Release (CRN=104) Channel Number=12 Release Complete (CRN=104) Channel Number=12 SetUp (CRN=117) Call Proc.
Since not all switches operate this way, setting the channel block timer is optional. When enabled, the channel block timer is started upon the sending or receiving of the final clearing message on a particular channel (clearing message could be RELEASE or RELEASE COMPLETE), and that channel will not be able to accept another call until this timer has expired.
1.57.1 Feature Description The Trunk Configuration property sheet of the Dialogic® Configuration Manager (DCM) contains parameters for configuring the interfaces on a DMV600BTEP or DMV1200BTEP Board. The procedure is described in detail in the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide. Previously, there were five different groups of protocols; now there are only two groups. As before, only protocols within the same group can be used on the same board.
For detailed information about configuring DMV600BTEP and DMV1200BTEP Boards, see the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide. Note: The online bookshelf has not been updated for this feature, so the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide does not currently include information about mixing ISDN and CAS protocols on the same board. 1.
Table 5.
1.59 Enhanced Special Information Tone Frequency Detection on Dialogic® DM3 Boards This release provides the following enhancements to Special Information Tone (SIT) frequency detection on Dialogic® DM3 Boards: • Broader default SIT sequence definitions to allow greater coverage for SIT sequences detected in the field. • Three new SIT sequence definitions in the SIT tone set for DM3 Boards.
Table 6. Special Information Tone Definitions (DM3 Boards) SIT Tone ID 1.59.2 1st Segment Description Freq. Time 2nd Segment Freq. 3rd Segment Time Freq.
Updated example code is provided for this function as follows. #include #include #include
case TID_SIT_NC: break; case TID_SIT_IC: break; case TID_SIT_VC: break; case TID_SIT_RO: break; case TID_SIT_NC_INTERLATA: break; case TID_SIT_RO_INTERLATA: break; case TID_SIT_IO: break; case TID_SIT_ANY: break; } break; default: break; } /* * Set channel on hook */ if ((dx_sethook( ddd, DX_ONHOOK, EV_SYNC )) == -1) { /* handle error */ } } 1.59.3 dx_close( ddd ); Documentation The online bookshelf provided with Dialogic® System Release 6.
1.
Table 8. New Alarms for T1 Technology (DM3 Boards) Alarm 1.60.
environment: the operating system, computer architecture, System Release software, and operational logs. With the Service Update, the its_sysinfo.htm file now includes a Windows® Package Info section at the beginning of the file. For example: WindowsPackageInfo Active System Release Dialogic(R) System Release 6.
Dialogic® D/41JCT-LS Media Boards, and all other JCT Boards that use a continuous speech processing firmware load, function with single echo canceller convergence by default. Therefore it is not necessary to use the ECCH_CONVERGE channel parameter with these boards. 1.63.1 Feature Description Speech-enabled applications that re-enable continuous speech processing and have loud prompts experience bursts of excessive echo in the streamed audio on each play file, causing application malfunction.
5. Repeat for each phone call. Note: Once the ec_setparm( ) is issued with the ECCH_CONVERGE value set to OFF, the addressed voice channel's echo canceller will no longer track changes in the trunk characteristics. At the beginning of each new phone call, the application must set ECCH_CONVERGE to ON to allow the echo canceller to adapt to the connected trunk's characteristics. Failure to do this can result in poor echo cancellation, which affects important voice channel functions. 1.63.1.
1.64 New Features in Dialogic® Global Call Protocols Package A number of new features have been added to the Dialogic® Global Call Protocols Package, which is now part of the System Release software.
1.65 New Operating System Support In addition to the supported operating systems listed in the Release Guide, the following operating system versions are now supported with this Service Update: • Windows Vista® Business, 32-bit edition • Windows Vista® Enterprise, 32-bit edition • Windows Vista® Ultimate, 32-bit edition Note: See Section 1.4, “Support for Windows Vista® Operating System”, on page 40 for information about running System Release 6.
MSMM_CS_IDLE Station interface online; sent when cable is reconnected, alarm is cleared, or station is powered up. MSMM_CS_OUT_OF_SERVICE Loop current to station interface disabled, e.g., for maintenance purposes. The MSEV_CHANSTATE event is disabled by default. Use the ms_setevtmsk( ) function to enable events, for example, ms_setevtmsk(msiB#C#, MSEV_CHANSTATE, MSMM_CS_ALARM | MSMM_CS_IDLE | MSMM_CS_OUT_OF_SERVICE, DTA_SETMSK). Note: The enabling/disabling of the event is local to a process.
if( (t_GetBitMsk & MSMM_CS_IDLE) == MSMM_CS_IDLE ) printf("ms_getevtmsk(dvh:%d, MSEV_CHANSTATE, bitmsk:0x%X) - MSMM_CS_IDLE is set\n", a_DevHdl, t_GetBitMsk); if ( (t_GetBitMsk & MSMM_CS_OUT_OF_SERVICE) == MSMM_CS_OUT_OF_SERVICE ) printf("ms_getevtmsk(dvh:%d, MSEV_CHANSTATE, bitmsk:0x%X) - MSMM_CS_OUT_OFSERVICE is set\n", a_DevHdl, t_GetBitMsk); } } /* Process the SRL event */ long EventHandler (unsigned long temp) { int devh = sr_getevtdev(); long event = sr_getevttype(); unsigned short * evtdata = (unsign
• The Events chapter in the Dialogic® Modular Station Interface API Library Reference, and the Event Handling chapter in the Dialogic® Modular Station Interface API Programming Guide, do not currently include the MSEV_CHANSTATE event. 1.67 Support for ANI Category Digit Retrieval on Dialogic® DM3 Boards The Service Update provides support for ANI category digit retrieval on Dialogic® DM3 Boards. 1.67.
conferences. It provides 128 conferencing resources with echo cancellation and tone clamping. The maximum conference size without bridging is 64 parties. The maximum conference size with bridging is 126 parties per board. Media load ML9B-LC is an addition to the ML9x series of media loads for conferencing. For example, media load ML9B can still be used for applications that require higher overall density without the need for large conference sizes.
For detailed information about configuring DMV3600BP Boards, see the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide. Note: The online bookshelf has not been updated for this feature, so the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide does not currently include information about media load ML9B-LC.
Media Load QSB-U3 The features and channel densities provided by media load QSB-U3 are as follows: Features Supported Enhanced Voice Transaction Record FSK Fax Conferencing with Echo Cancellation and Tone Clamping Channel Density 120 120 120 8 36 There are 120 total voice resources. Any combination of the voice features (enhanced voice, transaction record, and FSK) can be used up to a total of 120.
Media Load QSB-ML10-LC Media Load QSB-ML10-LC is similar to QSB-ML10 but with larger conference sizes (38 parties instead of 18 parties without bridging). QSB-ML10 can still be used for applications that don’t need larger conference sizes. To allow for higher system density, QSB-ML10-LC does not support CSP streaming to CT Bus.
There are 120 total voice resources. Any combination of the voice features (basic voice, transaction record, and FSK) can be used up to a total of 120. In addition to these voice resources, 120 conferencing resources (with echo cancellation and tone clamping) can be used. Note: Conference size is limited to 20 parties without bridging. Conference bridging can be used to effectively expand a conference beyond the maximum size.
1.70.1 Feature Description Predefined sets of features for Dialogic® Boards are provided in media loads. A media load consists of a configuration file set (PCD, FCD, and CONFIG files) and the associated firmware that is downloaded to the board. See the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide for more information about media loads.
For detailed information about configuring DMV600BTEP Boards, see the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide. Note: The online bookshelf has not been updated for this feature, so the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide does not currently include information about media load DSB-U2. 1.71 Call Transfer Support on the Dialogic® DMV160LP Board The Service Update adds support for supervised call transfer on the Dialogic® DMV160LP Media Board.
1) A hookflashes placing B on hold Controller (A) On Hold Held Party(B) 2) A dials C and waits for answer On Hold Controller (A) Held Party(B) 3) A notifies C of transfer 3rd Party (C) 3rd Party (C) 4) A hookflashes & notifies B of transfer (Optional) Controller (A) 5) A hangs up Held Party(B) On Hold 3rd Party (C) 1.71.1.
between the Held party and the Third party prior to the transfer. Once this API is completed, the roles of the held and consultation call are reversed. Note: Depending on the PBX type and configuration, it may not be possible to use the gc_SwapHold( ) function to swap between the held call and the consultation call. For non-US protocols, the gc_SwapHold( ) function can operate correctly if the behavior of the protocol is similar to that of a US counterpart. 1.71.1.
- Party A dials party C, then hangs up - Verify: Party B and party C connected • The held call is dropped by Party B - Party B calls party A - Party A hookflashes (places call with party B on hold) - Party A calls party C (consultation call) - Party C picks up - Party B hangs up - Party C hookflashes - Verify: Party C and party A connected • The consultation call is dropped by Party C - Party B calls party A - Party A hookflashes - Party B calls party C - Party C hangs up - Verify: Party B and Party A are
• Running PBX Expert 1.71.2.1 Updating the CONFIG File The following parameters require configuration in the DMV160LP Board CONFIG file: • Tone_SigId4 (Disconnect Tone Supervision) must be set to a value of 238113 (a fixed tone ID) to enable disconnect tone supervision. The default value is 0x0 (disabled). • BtStartTimeout (Permanent Signal Planning) must be set to a value appropriate for the PBX system being used. The default is 8000 (8 seconds).
1.72 dx_reciottdata( ) Enhancements The Service Update provides the following enhancements to the dx_reciottdata( ) function: • Initial silence compression • Voice activity detector (VAD) with event notification These enhancements are applicable to the following boards: • Dialogic® DM/V, DM/V-A, DM/V-B, DM/VF, and DMV160LP Media Boards • Dialogic® DM/IP Boards 1.72.
Supported Coders These enhancements to the dx_reciottdata( ) function are supported for the following encoding methods and sampling rates: • OKI ADPCM, 6 kHz with 4-bit samples (24 kbps) and 8 kHz with 4-bit samples (32 kbps), VOX and WAVE file formats • Linear PCM, 8 kHz sampling 64 Kbps (8 bits), 8 kHz sampling 128 Kbps (16 bits) • G.711 PCM, 6 kHz with 8-bit samples (48 kbps) and 8 kHz with 8-bit samples (64 kbps) using A-law or mu-law coding, VOX and WAVE file formats • G.
• Dialogic® Voice API Library Reference Note: The online bookshelf has not been updated for this feature. The following observations are worth noting: • The description of the dx_reciottdata( ) function in the Dialogic® Voice API Library Reference does not currently show the RM_ISCR and RM_VADNOTIFY modes. • The Events chapter in the Dialogic® Voice API Library Reference does not currently include the TDX_VAD event.
Value Description 0 Default - No alarm is transmitted on the trunk; all trunk time slots signal Out of Service. 1 TransmitAIS - An Alarm Indication Signal (AIS) alarm is transmitted on the trunk. 2 TransmitRAI - A Remote Alarm Indication (RAI) alarm is transmitted on the trunk. Note: The default behavior also applies if the Initial Alarm State parameter is not used. Behavior is the same in both ISDN and CAS environments.
Whenever a CONFIG file has been modified, a new FCD file must be generated. This procedure is described in detail in the Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide. 1.73.3 Documentation The online bookshelf provided with Dialogic® System Release 6.0 PCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics.
brd_SendAliveEnable( ) function, the board treats it as a host failure. When this occurs, the board takes its network interface out-of-service, thus preventing the network from offering calls to the failed system. The board also releases/drops all active calls and frees associated memory. The network interface is taken out-of-service by sending an Alarm Indication Signal (AIS) toward the network. This is the ITU recommended mechanism for informing the CO or network that the trunk is not available.
The D/4PCIU4S is a 4-port analog loop start media processing board that can support either voice with CSP, or voice with fax, based on the firmware file selected.The firmware file is specified in DCM using the FirmwareFile parameter on the Misc property sheet. The default firmware file is d4u.fwl for voice with fax. For voice with CSP, select the d4ucsp.fwl firmware file. Note: The D/4PCIU4S Board is displayed as D/4PCIU in DCM.
Release Issues 2. The table below lists issues that can affect the hardware and software supported in Dialogic® System Release 6.0 PCI for Windows®. The following information is provided for each issue: Issue Type This classifies the type of release issue based on its effect on users and its disposition: • Known – A minor hardware or software issue. This category includes interoperability issues (i.e.
The following table lists all issues that relate to this release, sorted by Issue Type. For other sort orders, use the following links: • View issues sorted by Service Update Number • View issues sorted by Product or Component • View issues sorted by Defect Number Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® Issue Type Known Defect No. PTR No. IPY00022362 19779 Known SU No.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Known Defect No. PTR No. IPY00008091 31432 SU No. Dialogic® Product(s) or Component(s) Conferencing (DCB) Description The maximum value for the dcb_estconf( ) function numpty parameter is 24.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Known IPY00008850 31245 D/480JCT-2T1 D/600JCT-2E1 When Global Level PCMEncoding is not set to “Automatic”, which is the default, it must be set to match the Board Level PCMEncoding for the Dialogic® D/480JCT-2T1 and D/600JCT-2E1 Boards. Known IPY00021906 21049 D/82JCT-U Call Progress test fails 100% on Dialogic® D/82JCT-U Boards.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Known Defect No. PTR No. IPY00030640 23783 SU No. Dialogic® Product(s) or Component(s) DM/IP Boards Description There is no interoperability between a Dialogic® DM/IP Board and a Siemens IP phone in Fast Start mode. When working in Fast Start mode with the DM/IP Board as the originator, the DM/IP Board sends facility with reason startH245 which the Siemens IP phone does not support.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Known Defect No. PTR No. IPY00019225 25596 SU No. Dialogic® Product(s) or Component(s) DM/IP Boards Description All test files *.c and *.h in the iptmail_r4.dsp and gateway_r4.dsp have an extra carriage return CR added: 0D0D0A (CRCRLF) instead of 0D0A (CRLF) which prevents the Microsoft Development Studio’s editor from proper alignment of the source code with debug info.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Known IPY00007879 31659 DM/IP Boards The default nfrm value for user-defined tones on Dialogic® DM/IP Boards is 10. In situations where the DM/IP Board firmware is being used in a PSTN environment, this value may need to be lowered if you are seeing cadence detection failures.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Known DM/IP Boards To select a coder when using Dialogic® DM/IP Boards with Microsoft NetMeeting, invoke the coder list (Tools>Options>Audio>Advanced) to bring your preferred coder to the top of the priority list. For best results, Microsoft NetMeeting and the DM/IP component should be configured to use the same coder.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Known Defect No. PTR No. IPY00007354 31617 Known SU No. Dialogic® Product(s) or Component(s) Description DM/V Boards When setting CODESET_7_IE or CODESET_6_IE together with USER_USER_IE in the setup message, neither IE is delivered to the remote side. However, when setting USER_USER_IE only, it is delivered to the remote side.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Known Defect No. PTR No. IPY00007996 32189 SU No. Dialogic® Product(s) or Component(s) DM/V-B Boards Description During high density, over 700 channels per chassis, an illegal termination of the system may result in a conditional lockup or hang state. Workaround: Either re-download or reboot the Dialogic Boards if the application terminates abnormally.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Known Defect No. PTR No. IPY00008411 32133 SU No. Dialogic® Product(s) or Component(s) DM3 Network Description Under heavy load with 100% CPU utilization, if the host application were to exit abnormally (i.e. application error, memory exception), specific realtime tasks running on the board may assert. The only way to recover would be to restart the Dialogic® Services.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Known IPY00021978 28889 DMV160LP DTMF termination condition issue. On the Dialogic® DMV160LP Board, when the record operations are set to be terminated on a DTMF, the recorded file may contain between 30 to 50 msec of the terminating DTMF.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. Known Known IPY00030585 25536 SU No. Dialogic® Product(s) or Component(s) Description Global Call on IP When developing applications that use IP technology, Dialogic® Global Call Software does not support synchronous programming models. Unless explicitly stated in the Dialogic® Global Call IP Technology User’s Guide, Global Call functions should be called in asynchronous mode.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. Known SU No. Dialogic® Product(s) or Component(s) HDSI Boards Description A Station Interface Box (SIB) firmware upgrade may be required to support the 25 Hz and 50 Hz ring frequencies provided in the country-specific configuration files. You can use the kernelver utility to retrieve the Dialogic® HDSI Board and SIB firmware versions.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Known IPY00007510 32342 Host Admin CTBB event logs are being made without descriptions appearing in the Application log panel. CTBB event logs should not even appear in the Application log panel. CTBB event logs should only appear in the System log panel with descriptions.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Known Defect No. PTR No. IPY00023978 31618 SU No. Dialogic® Product(s) or Component(s) Host Library Description Applications utilizing a Dialogic® HiZ board may take 15-20 minutes to shut down. Workaround: Tearing down channels in parallel will greatly reduce the shutdown time (less than 30 seconds).
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Known Defect No. PTR No. IPY00022142 23256 SU No. Dialogic® Product(s) or Component(s) Description ISDN cc_SetChanState( ) is only supported on North American T1 PRI protocols. It is not supported on NTT (Japanese) or European E1 protocols since the specs of these protocols do not support SERVICE/SERVICE_ACK messages.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. Known SU No. Dialogic® Product(s) or Component(s) Programming Using External References Description Please refer to the following technotes on the support website for information regarding how to program using external references: http://www.dialogic.com/support/helpweb/dxall/tnotes/ legacy/dlsoft/tn254.htm http://www.dialogic.com/support/helpweb/dxall/tnotes/ legacy/dlsoft/tn253.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Known Defect No. PTR No. IPY00022082 21385 SU No. Dialogic® Product(s) or Component(s) Springware Voice Description Cannot create more than 10 user-defined tone templates on one voice channel. Explanation: This is a limitation of the firmware. The firmware can recognize a total of 20 terminating conditions for an IO event, however only 10 of them can be tones.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. Known (permanent) IPY00006127 33837 SU No. Dialogic® Product(s) or Component(s) Board Download Description The UK country parameter file for the Dialogic® D/41JCT-LS Board is missing from the release.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. Known (permanent) IPY00022342 15033 SU No. Dialogic® Product(s) or Component(s) D/82JCT-U Description “Parm not set correctly” error for board and channel parameters. The problem occurs when the d42_setparm( ) or d42_getparm( ) function is called simultaneously on multiple threads for the same channels on the Dialogic® D82JCT-U Board.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. Known (permanent) IPY00029958 36722 SU No. Dialogic® Product(s) or Component(s) DM3 Driver Description DCM may not detect all boards in systems with D865GBF series motherboard. This problem occurs only with some revisions of the BIOS. Workaround: This problem can be corrected by updating the BIOS to version P25.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. Known (permanent) IPY00022262 27343 SU No. Dialogic® Product(s) or Component(s) Global Call Description When using the us_mf_io ICAPI protocol (and possibly other ICAPI protocols) with Dialogic® Springware Boards and using the dx_ method of call analysis, fax tones may be misinterpreted if the ca_pamd_spdval field is set to PAMD_FULL in the DX_CAP structure.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. Known (permanent) IPY00006578 34616 SU No. Dialogic® Product(s) or Component(s) Host Admin Description Due to security enhancements implemented in Windows® XP SP2 and Windows Server® 2003 SP1, Remote DCM will no longer work with these operating systems.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. Known (permanent) IPY00028427 36079 SU No. Dialogic® Product(s) or Component(s) Host Install Description DCM fails to download the board when the cdp file name is wrong in pdk.cfg. An error message appears in the Event Log, but it doesn't adequately describe the error condition. Workaround: Check the pdk.cfg file for accuracy and check pdk.log in ..\Dialogic\log for errors.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Issue Type Defect No. PTR No. Known (permanent) IPY00007501 30091 JCT Boards A single 400 Hz tone can be erroneously detected as a dual tone defined as 459±40 Hz, 330±40 Hz because the DSP cannot detect dual tones that are less than 60 Hz apart. It is recommended that the dual tone be defined as 459±20 Hz, 330±20 Hz.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. Known (permanent) IPY00032742 PTR No. -- SU No. Dialogic® Product(s) or Component(s) Runtime Trace Facility (RTF) Description ERR1 in RTF log can be ignored when using Dialogic® DISI Switching Boards. When you use DISI Boards in your system, the following prints will appear with an ERR1 label in the RTF log files: 04/13/2006 17:54:50.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. Known (permanent) IPY00030548 24937 SU No. Dialogic® Product(s) or Component(s) Springware Voice Description If you call the dx_reciottdata( ) function and you specify a DX_MAXSIL termination condition, dx_reciottdata( ) ignores this condition and will eventually trigger on another one (DX_MAXTIME) even if there is silence on the line.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. Known (permanent) IPY00037015 PTR No. SU No. -- Dialogic® Product(s) or Component(s) UDD Description Dialogic® Diagnostics Software (UDD) reports download errors when multiple boards are installed in the same system. Workaround: When using UDD to test multiple Dialogic® Springware Boards in the same system, use DCM to disable all boards except the one being tested.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00007803 31782 18 Call Logging The cl_ReleaseTransaction( ) function has no effect on non-call-related transactions; memory keeps increasing. Resolved IPY00036423 -- 142 Conferencing Sometimes a noise is generated when a party leaves a conference; the noise disappears when a party is added to the conference.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00034678 -- 125 CSP For Dialogic® D/41JCT-LS Board CSP application, dx_playiottdata( ) fails after ec_listen( ) to route any timeslot.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00008476 32065 18 D/240JCT-T1 With high call load, a firmware crash occurs on Dialogic® D/240JCT-T1 Boards running NTT protocol. Resolved IPY00012124 28389 -- D/300JCT-E1 Dialogic® D/300JCT-E1 Board crashes with an unstable E1 line.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00008135 29106 -- DCM More than five boards cannot be downloaded and started through the DCM in some dual-processor chassis. Resolved IPY00028262 33199 56 Demos gc_GetCallInfo( ) fails to return the caller ID on a Dialogic® D/4PCIU Board when using the gc_basic_call_model demo.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00041178 -- 178 Diagnostics When Dialogic® System Release 6.0 PCI for Windows® is installed on a partition other than C, the d82diagutil application cannot locate the voxcfg file because it is looking for it on the C drive instead of the drive where the Dialogic® System Release is installed.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00020965 27459 -- DM/IP Boards Application returns “synchronization object time out” error when calling IPML functions. Resolved IPY00020954 26090 -- DM/IP Boards An IP call to a non-existent IP address returns “normal clearing”. Resolved IPY00020951 25615 -- DM/IP Boards In the iptmail_r4.dsp parser in the apppars.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00007472 28620 22 DM/IP Boards Applications should not set the TOS bits through Dialogic® Global Call Software (Parameter = IPPARM_CONFIG_TOS) or Dialogic® IPML Software (Parameter = PARMCH_TOS). This may cause a blue screen.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00015512 29922 -- DM/V-A Boards Download failures of ml2_qsa_net5.pcd and ml2_qsa_qsige1.pcd files on Dialogic® DM/V1200A4E1-PCI Boards. Resolved IPY00015507 29486 -- DM/V-A Boards dx_playiottdata( ) does not return any events. This happens with Dialogic® DM/V960A and DM/V480A Boards.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00037396 -- 148 DM3 Conferencing Static background noise trails voice in conferences with more than six parties.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00037161 -- 154 DM3 Fax With fax on Dialogic® DM/F240-1T1-PCI Boards, when the badscanline percentage exceeds the default value, the library and firmware both seem to send out RTN messages to request page re-send and retraining, but the RTN messages never get to the line.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00028278 35423 84 DM3 Fax Fax sender (Dialogic® DM/F240 Board) cannot wait to receive retry of DIS message and gets Phase E status (EFX_COMMERRTX). Resolved IPY00028196 36256 84 DM3 Fax TIFF (with valid tags) fails on Dialogic® CPi/2400 and DM/F Boards.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00028345 35148 64 DM3 Firmware D-channel fails to come up on a back to back setup. Two spans of NI2 are connected back to back and the D-channel comes up. When the cable is pulled out, the network side doesn’t report the D-channel going down. When the cable is reconnected, the D-channel doesn't come up.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Resolved Defect No. PTR No. IPY00006647 36598 SU No. 98 Dialogic® Product(s) or Component(s) DM3 Firmware Description There is memory corruption on the Dialogic® DMV1200BTEP Board when using ISDN firmware.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00010914 36429 84 DM3 IP If application uses both H.323 and SIP, gc_ResetLineDev( ) called before gc_WaitCall( ) locks up channel on Dialogic® DM/IP241-1T1 Board, Resolved IPY00010900 36349 98 DM3 IP The PARM_TX_ADJVOL_ and PARM_RX_ADJVOL_ parameters in the ipmlib.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00016070 29869 -- DM3 Network After re-download of remote side, the local Layer2 still thinks that Layer1 is down and does not issue SABME request. Resolved IPY00010627 35339 74 DM3 Network Using Dialogic® DMV1200B Boards with NFAS group of 5 spans, you cannot make calls from the 5th span when the NFAS group is on two boards.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Resolved Defect No. PTR No. IPY00007686 31991 SU No. 84 Dialogic® Product(s) or Component(s) DM3 Network Description When configuring inter-board NFAS where the Primary and Secondary D channel are on separate boards, NFAS trunks on the board with the Secondary D channel cannot make or accept calls.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00037493 -- 155 DM3 Voice When running high volume load tests (500+ voice channels) for performing records, the RTF log shows “Buffer is corrupted” errors in the Dialogic® DM3 StreamSink component.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00014104 28121 -- DM3 Voice Need a method to improve call progress analysis on Dialogic® DM3 Boards similar to that for Dialogic® Springware Boards. Resolved IPY00011063 36799 92 DM3 Voice When using Dialogic® DISI32R2 Board, calling ms_estconf( ) causes the following error to be displayed: “Unhandled exception in application.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00015228 31100 -- DMV160LPHIZ The functions cl_StartTrace( ), cl_StopTrace( ) and cl_DecodeTrace( ) are not supported on Dialogic® Analog HiZ boards.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00031588 36770 111 Global Call Problem with gc_HoldCall( ), which sends the SUSPEND message to the network. Resolved IPY00028579 34569 70 Global Call gc_RetrieveCall( ) returns error “function not supported in this state” when using pdk_sw_e1_ntmd_io.cdp.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00016066 29040 -- Global Call GCEV_OFFERED event received on a board device (DTIB1) causes application to crash when using overlap receive. Resolved IPY00015514 30170 -- Global Call A NON RECOVERABLE FATAL ERROR occurs if a call is dropped at the remote-end in the ACCEPTED state.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00008150 33069 18 Global Call gc_MakeCall( ) changes the CRN value after the permanent signal timer expires. Resolved IPY00007743 30029 -- Global Call Sometimes the first gc_MakeCall( ) under T1 ISDN with R4 will not complete successfully.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Resolved Defect No. PTR No. IPY00014904 28798 SU No. -- Dialogic® Product(s) or Component(s) Global Tone Detection Description If you have trouble detecting tones and see “Can't allocate space in suspect list for GTD(x)” in the DebugAngel output, consider the following: • Seeing this message is not necessarily a problem.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00019274 27450 -- HDSI Boards Dialogic® System Release 5.1.1 does not include proper CONFIG/PCD/FCD files for configuration of MSI/1200 (HDSI) to be used with SIB units less than 120 ports. Resolved IPY00008337 33011 22 HDSI Boards Modifications to the ring frequency in the HDSI CONFIG file do not take effect.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00010226 36092 74 Host Admin In the DCM Trunk Configuration tab for Dialogic® DM/V-B Boards, the Media Load and Trunk protocol values listed in the pull-down menu at the bottom do not show the currently selected value at the top when each is highlighted.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00030671 32696 18 Host Drivers After the Driver Verifier finds an obsolete call used in the device driver, a blue screen occurs. Resolved IPY00030669 32557 18 Host Drivers A blue screen occurs during the boot verification tests performed by the Windows® kernel using Verifier.exe.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) PTR No. Resolved IPY00010161 33665 18 Host Install Installation of the Dialogic® System Release Software fails when the Windows® PATH environment variable is not defined. After making all install selections, and “Next” is clicked to begin the copy of files, a pop-up box marked “Severe” appears reporting the following error: “Failed to set the environment variable (path)”. The install then aborts.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00032262 36688 95 Host Library sr_waitevtEx( ) hangs in multi-threaded environment. For example, if you have an application that creates two threads, each thread monitors its own events via sr_waitevtEx( ). The first thread makes a call, synchronously. The second thread makes a call, synchronously.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00010556 35157 56 Host Library Calling ATDV_SUBDEVS( ) on Dialogic® DM3 MSI stations while alarms are being processed on DM3 trunks on span cards can cause a deadlock condition in the application, which can hang the system for 8 seconds.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00016168 28084 -- ISDN When performing ISDN tracing on all spans in a bulk call environment, dual span boards can encounter firmware crashes with just one board running. Resolved IPY00007887 29513 -- ISDN Under heavy load, firmware assert happens in vb_util.c when working with ISDN protocols.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00029931 36809 110 NCM API Throws an exception when attempting to run application from debugger. Resolved IPY00012520 29075 -- NCM API Attempting to add a new device using NCM_AddThirdPartyDevice( ) fails with a name that is subset of an existing device name.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00016065 28992 -- PBX Integration The Called side drops a connection when trying to connect from channel 1 to channel 2 through a PBX.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00030679 33146 18 Protocols When using the pdk_us_mf_io protocol, the GCEV_UNBLOCKED event is not generated when Layer 1 alarms are cleared after the channel is put OOS. Resolved IPY00028595 35538 70 Protocols Basic call control using Korea GDS LS protocol does not work on Dialogic® Springware Boards.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00010372 35035 56 Protocols After sending CAS_HOOKFLASH, there should be some delay before sending DTMF in pdk_sw_e1_necls_io protocol, if CDP_WaitDialToneEnabled = 0 (i.e., do not wait for dialtone). Resolved IPY00010223 34985 56 Protocols pdk_sw_e1_ermx_io.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00008374 32601 18 Protocols The gc_SetChanState( ) function fails to return a completion event or error indication when using the pdk_us_mf_io protocol on a Dialogic® DM/V960A-4T1 Board. Resolved IPY00008220 34972 56 Protocols When using the pdk_us_mf_io protocol, digits from the previous call are returned in ANI.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00006748 34587 56 Protocols The PDK E1 CAS protocol cannot be downloaded on Dialogic® DM3 Boards, and Dialogic® Springware Board channels cannot be opened when using this protocol.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00036337 -- 139 PSTN Call Control 5ESS for Dialogic® DM3 Boards did not support CALLED NUMBER TYPE in the NETWORK_SPECIFIC (0x03), IE.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00033163 -- 124 PSTN Call Control Access violation occurs when running ISDN based application. Resolved IPY00033009 -- 113 PSTN Call Control NCAS does not work on mixed T1/E1 or mixed ISDN/CAS configurations.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00035831 -- 134 SIP Call Control Segmentation fault occurs in libipm_vsc.so when calling gc_close( ) on Dialogic® Global Call (IP based) line device. Resolved IPY00035822 -- 134 SIP Call Control Dialogic® Global Call SIP application does not respond to 407 Proxy Authentication Required messages.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00038539 -- 160 Springware Call Control Interface ID Present enabled in network setup message causes channel on Dialogic® D/480JCT Board using 4ESS protocol to reject call with invalid information element contents.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00030890 32415 70 Springware Fax When an ASCII text file is faxed from a Dialogic® VFX/41JCT-LS Board and the resolution is set to fine, the font size of the received document is reduced by about half of the sent document's font size.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00010734 34753 56 Springware Fax In ECM fax send operation, the Dialogic® VFX/41JCTLS Board sets wrong frame count in PPS message when responding to PPR from remote fax machine. Resolved IPY00010365 35132 56 Springware Fax The operating system hangs when trying to download Dialogic® D/4PCIUF Boards.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00028518 35832 84 Springware Firmware GCEV_DROPCALL event is not returned after calling gc_DropCall( ) if GCEV_DISCONNECT is sent by the firmware due to time-out. Resolved IPY00028458 35154 58 Springware Firmware Dialogic® Springware NI2 firmware sets and sends the interface ID bit and Octet 3.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00008592 32678 18 Springware Firmware Two bytes of corrupt data are observed in the Dchannel trace whenever cc_SetInfoElem( ) is called to set the value for the CALLING_LINE_ID number in a SETUP message.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Resolved Defect No. IPY00036949 PTR No. -- SU No. 139 Dialogic® Product(s) or Component(s) Springware ISDN Firmware Description With Service Update 108 and later, outbound ISDN calls are rejected by the switch due to missing IE (octet 3.1, Extension Bit/Interface Identifier). In Service Update 108, Dialogic® Springware firmware was changed to stop sending octet 3.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00007425 32712 62 Springware PBX If a second call comes in after a first caller disconnects and before the ring off event is generated, the call will not be answered. Resolved IPY00028211 33249 56 Springware Protocols BRI/PCI firmware stops normal operation and error -1, ATDV_LASTERR( ) 3 is returned from dt_listen( ).
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00028588 35746 94 Springware Voice An analog Dialogic® Springware Board kept returning NODIALTONE as result of call progress analysis (CPA) when performing outbound calls. This problem occurred after several outbound calls, which were made previously, experienced line busy.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00008215 28550 18 Springware Voice With the Dialogic® DTI/240SC Board, when the inbound application is to receive a call, the calling (Telco) side receives an error message ‘protocol error’ and the call is dropped. Resolved IPY00008056 33690 22 Springware Voice Turning Silence Compressed Record on via the voice.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00012758 27572 -- UDD Dialogic® Diagnostics Software (UDD) does not work correctly on Dialogic® D/600JCT-2E1 Boards. Resolved IPY00007931 23718 115 UDD Dialogic® D/240JCT and D/480JCT Boards fail Dialogic® Diagnostics Software (UDD) firmware download.
Table 9. Issues Sorted By Type, Dialogic® System Release 6.0 PCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00033029 -- 108 Voice When playing (dx_playiottdata) from multiple offsets of the same file, only the first portion is played. Resolved IPY00032363 -- 108 Voice Random segmentation faults happen due to reading uninitialized memory.
Documentation Updates 3. This chapter contains information on updates and corrections to the documents included in Dialogic® System Release 6.0 PCI for Windows®. Documentation updates are divided into the following categories: • System Release Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 • Installation and Configuration Documentation . . . . . . . . . . . . . . . . . . . . . . . . . 344 • OA&M Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . .
you are using a language other than U.S. English should be deleted (PTR# 36671). The note should simply say: Note: This system release is designed only for U.S. English versions of the Windows® Operating System. Updates to the Features by Product chapter, Dialogic DI/0408-LS-A-R2 Features section The following item belongs under the “Other Supported Features” heading: • fixed routing support The Dialogic DI/0408-LS-A-R2 Features section erroneously mentions support for the DI/0408-LS-A Board.
DM3 board cannot use any of the FrontEnd values in the Derive Primary Clock From parameter. Note: Note: In the Administrative Software section, the following restriction and limitation on the Board Management API is documented: A restriction and limitation of Board Management is that it is supported only on JCT single span and dual span boards under the following protocols: T1 4ESS, T1 5ESS, T1 DMS100, and T1 NI2. (E1 protocols are not supported.
• IMA ADPCM (32.443 Kbps) coder The IMA ADPCM coder (VOX and WAVE file formats) is supported. IMA is an acronym for the Interactive Multimedia Association, which defined and published the ADPCM algorithm. • Enhancement to Multi Frequency (MF) signaling MF tone detection is now supported. Previously, only MF tone generation was supported.
3.2 Installation and Configuration Documentation This section contains updates to the following documents (click the title to jump to the corresponding section): • Dialogic® DM3 Architecture PCI Products on Windows® Configuration Guide • Dialogic® Springware Architecture Products on Windows® Configuration Guide • Dialogic® GDK 5.0 Installation and Configuration Guide for Windows® • Dialogic® Global Call Country Dependent Parameters (CDP) for PDK Protocols Configuration Guide • Dialogic® System Release 6.
PvdDesc PvdRbHigh 510 CreatePvd !User defined PAMD template.
parameters are now applicable to these boards. For information about this feature, including configuration information, see Section 1.45, “IP Support on Dialogic® DI0408LSAR2 Boards”, on page 152 and Section 1.46, “Dialogic® DI0408LSAR2 Board Support for Host Systems with Multiple NICs”, on page 159 of this Release Update.
Update to Section 2.4, Media Loads for new Dialogic® DI Board feature Because of a new feature in the Service Update, Section 2.4.1.1 about features supported on Dialogic® DI Boards should be updated to indicate that conference bridging is supported so a higher number of maximum parties per conference is possible. For further information about this feature, see Section 1.54, “Conference Bridging on Dialogic® DI Boards”, on page 221 of this Release Update. Update to Section 2.4.1.
Group 1 Group 2 4ESS (T1) DPNSS 5ESS (T1) DASS2 NTT (T1) NI2 (T1) DMS (T1) QSIGT1 (T1) QSIGE1 (E1) NET5 (E1) T1CC (T1) CAS (T1) E1CC (E1) R2MF (E1) For further information about this feature, see Section 1.57, “Mixing ISDN and CAS on Dialogic® DM/V-B Boards”, on page 225 of this Release Update.
PciID Description: The PciID parameter is a positive integer or hexadecimal value in which the lower 5 bits specify a board's rotary-switch setting (PCI boards) or the physical slot number location of the board (CompactPCI boards). The rotary-switch setting for PCI boards can be the same for all boards in the system if the value is set to 0. Values: A positive integer or hexadecimal value Guidelines: The PciID parameter is set by the system software and should not be changed by the user.
mode. This parameter should be documented in Section 6.4, [encoder] Parameters. For information about this feature and the new parameter, see Section 1.72, “dx_reciottdata( ) Enhancements”, on page 254 of this Release Update. Update to Section 6.7, [0x3b] Parameters Information about parameters 0x3b03 and 0x3b04 should be added to this section as follows: Note: This information is intended for experienced users of the Dialogic® DM3 conferencing feature.
Parameter 0x3b03, CSUMS_ActTalkerPartiesMinNum Parameter 0x3b04, CSUMS_SmartScalingPartiesMinNum 0 (default 0 (default) Active Talker Detection (default) > Conf_MaxTotalParties 0 (default) Smart Scaling > Conf_MaxTotalParties > Conf_MaxTotalParties No Scaling Summing Mode Conf_MaxTotalParties is the setting for parameter 0x3926 in the configuration file, e.g.
received multiframe, as a guard against mimic framing patterns, before forcing a new frame alignment. The CRC Checking parameter allows you to enable the CRC-6 checking algorithm. This parameter only applies to T1 trunks whose Line Type parameter (0x1601) is set to 1 (dsx1_ESF). For all other Line Types, this parameter is invalid.
• NETREF Two FRU • Using NETREF Two Update for analog line adaptation utility (LineAdapt) Because of a new feature in the Service Update, a configuration utility is now available for tuning the impedance level on analog front-ends to reduce transmitter side line echo due to degraded analog telephone lines that deviate from their designed impedance range. Information about the LineAdapt utility should be added to this document. For information about this utility, see Section 1.
• For boards that support continuous speech processing (CSP), set this parameter to OFF (disabled) and, instead, use the CSPExtraTimeSlot parameter to enable echo cancellation. The guideline should be changed to: • For Dialogic® Springware Boards that support continuous speech processing (CSP), set this parameter to ON (enabled) and also set the CSPExtraTimeSlot parameter to ON. Update to Section 4.
Digital Signaling Description: Allows you to designate E1 time slot 16 for signaling or to choose clear-channel signaling. Values: • TS16_SIG [default]: Designates time slot 16 to be used for signaling. • TS16_CLEAR: Selects clear-channel signaling. Guidelines: To use this parameter, you must also set a value for the Country parameter. Consult the Country Parameter Selection Table in the DCM online help to verify that the value you choose for this parameter can be used for the country selected. 3.2.
see Section 1.35.1, “PDK Configuration Property Sheet”, on page 105 of this Release Update. The following note should be added after the first paragraph of this section (PTR# 36373): Note: If the automatically generated pdk.cfg file is deleted and not present in the %INTEL_DIALOGIC_CFG% directory, then all subsequent attempts to start the Dialogic® services will fail with no discernible error.
The network interface is taken out of service by providing the network with a protocol-specific outof-service condition. Because of a new feature in the Service Update, the network interface is taken out-ofservice by sending an Alarm Indication Signal (AIS) toward the network rather than a protocol-specific out-of-service condition. For information about this feature, see Section 1.74, “Extended Board Management API Support for Dialogic® DM3 Boards”, on page 258 of this Release Update. 3.3.
Settings Value Explanation Default The value of this parameter is to be determined by the system software. Its current value is indicated by the Resolved Equivalent. FrontEnd_1 The Primary Master derives clocking from its own front end network interface. This value only applies when the TDM Bus Type (Resolved) is set to SCbus and the Primary Master FRU (Resolved) is a Dialogic® Springware Board. FrontEnd_2 The Primary Master derives clocking from its own second network interface.
Update to EC_Resource help topic (IPY00041018) The following note for using the EC_Resource parameter is incorrect: • For boards that support Continuous Speech Processing (CSP), set this parameter to OFF (disabled) and, instead, use the CSPExtraTimeSlot parameter to enable echo cancellation. The note should be changed to: • For Dialogic® Springware Boards that support Continuous Speech Processing (CSP), set this parameter to ON (enabled) and also set the CSPExtraTimeSlot parameter to ON.
Update to SCbus Clock Rate (User Defined) parameter help topic The help topic for the SCbus Clock Rate (User Defined) parameter should read as follows: Description: If the bus is running in SCbus mode (the TDM Bus Type parameter is set to SCbus), this parameter determines the clock rate for the SCbus. Settings Value Explanation Default The value of this parameter is to be determined by the system software. Its current value is indicated by the Resolved. 2MHz Not currently supported.
CAS, R2MF, tone-on and tone-off has been added. For more information about this feature, see Section 1.23, “PDK Trace Supports CAS/R2MF/Tone Tracing”, on page 86. Update to Chapter 26, PSTN Diagnostics Tool Reference An enhanced version of the PSTN Diagnostics Tool (pstndiag) is provided in the Service Update. The previous version of the tool is still supported. For information about the new version, see Section 1.21.1, “PSTN Diagnostics (pstndiag)”, on page 81 of this Release Update.
The rtftool utility is a stand-alone program, and it is not necessary to have the Dialogic® System Release installed on the system in order to convert RTF log files from binary to text format. Note: When generating large binary files with RTF, do not split the single large binary file and then use the individual split files with the rtftool utility. Rtftool will not work with chopped binary files. Update to Chapter 29, RTFManager Reference (IPY00037518) Section 29.
Note: For the current configuration of the replaced board to be downloaded to the new board, the replacement board must be installed in the same slot as the board that was removed. Otherwise, the new board will be configured with the default values of the replaced board. • If the Detect Only option has been selected from the System/Device autostart submenu, the Dialogic® System and the boards will have to be manually started using the DCM GUI (or NCM API).
Boards Media Loads Protocols UL3 Group 1: CAS, 4ESS, 5ESS, DMS, NI2, NTT, QSIGT1, QSIGE1, NET5, R2MF, T1CC, E1CC Group 2: DPNSS, DASS2 ML10B Group 1: CAS, 4ESS, 5ESS, DMS, NI2, NTT, QSIGT1, QSIGE1, NET5, R2MF, T1CC, E1CC Group 2: DPNSS, DASS2 ML10 Group 1: CAS, 4ESS, 5ESS, DMS, NI2, NTT, QSIGT1, QSIGE1, NET5, R2MF, T1CC, E1CC Group 2: DPNSS, DASS2 DMV600BTEP UL1 Group 1: CAS, 4ESS, 5ESS, DMS, NI2, NTT, QSIGT1, QSIGE1, NET5, R2MF, T1CC, E1CC Group 2: DPNSS, DASS2 UL2 Group 1: CAS, 4ESS, 5ESS, DM
NCMRetCode ncmRetCode; char buffer[300] = {0}; NCMFamily family; family.name = "DM3"; family.next = NULL; NCMDevice UniqueName; UniqueName.name = "DMV1200BTEP #1 in slot 2/10"; UniqueName.next = NULL; NCMTrunkConfig ncmTruckConfig[4] = {0}; NCMFeatureType ncmFeatureType = {0}; ncmTruckConfig[0].TrunkName = "Trunk1"; ncmTruckConfig[0].TrunkValue = "4ESS(T1, Group 1)"; ncmTruckConfig[0].next = &(ncmTruckConfig[1]); ncmTruckConfig[1].TrunkName = "Trunk2"; ncmTruckConfig[1].
3.3.6 Dialogic® SNMP Agent Software for Windows® Administration Guide Update to Chapter 2, Stopping and Starting the System The following new section is added at the end of Chapter 2, Stopping and Starting the System: Starting the Boardserver When you use SNMP, you must start the Boardserver in one of the following ways: • From the Windows® Control Panel, go to Administrative Tools > Services, select the Boardserver, and click Start.
• Dialogic® ISDN Software Reference • Dialogic® Modular Station Interface API Library Reference • Dialogic® Modular Station Interface API Programming Guide • Dialogic® PBX Integration Board User's Guide • Dialogic® PBX Integration Software Reference • Dialogic® Standard Runtime Library API Library Reference • Dialogic® Standard Runtime Library API Programming Guide • Dialogic® Voice API Library Reference • Dialogic® Voice API Programming Guide 3.4.
Update to Chapter 7, Echo Cancellation Convergence Notification Because of a new feature in the Service Update, information about single echo canceller convergence should be added to Chapter 7, Echo Canceller Convergence Notification. For information about this feature, see Section 1.63, “Single Echo Canceller Convergence”, on page 235 of this Release Update. 3.4.
dt_getstatistics( ) Name: int dt_getstatistics(a_hSrlDevice, a_statisticsList, a_mode) Inputs: int a_hSrlDevice • logical board device handle (for example, dtiB1) TSdtStatisticsList* a_statisticsList • pointer to statistics unsigned short a_mode • synchronous/asynchronous Returns: 0 for success -1 for failure Includes: srllib.h dtilib.h Category: Statistics Functions Mode: synchronous/asynchronous Description The dt_getstatistics( ) function returns the statistics queried.
typedef enum { dtLayer1StatisticsId_Invalid = 0, dtLayer1StatisticsId_LCV = 1, /* dtLayer1StatisticsId_PCV, /* dtLayer1StatisticsId_ES, /* dtLayer1StatisticsId_SES, /* dtLayer1StatisticsId_UAS, /* dtLayer1StatisticsId_BES, /* dtLayer1StatisticsId_LOFC, /* dtLayer1StatisticsId_CSS, /* dtLayer1StatisticsId_SEFS, /* dtLayer1StatisticsId_LES, /* dtLayer1StatisticsId_Max }dtLayer1StatisticsId; Line Coding Violations(LCV) Path Coding Violations(PCV) Errored Seconds(ES) Severely Errored Seconds(SES) Unavailable S
Example /* OS Header Files */ #ifdef WIN32 #include #include #include #else #include #endif #include #include #include #include #include #include #include #include #include #include /* _beginthread, _endthread */ /* Dialogic Header Files */ #include #include #include #include #include
int main(void) { /* Start GlobalCall */ signal(SIGINT,(void (*)(int))sig_hdlr); signal(SIGTERM,(void (*)(int))sig_hdlr); if (gc_Start(NULL) != GC_SUCCESS) { printf("gc_Start(startp = NULL) Failed\n"); exit(0); } OpenBoard(); gc_Close(a_BoardDev); gc_Stop(); return 0; } void sig_hdlr(int temp) { cout << "Inside sig_hdlr -> Resetting repeat flag!!" << endl; repeat=false; } void OpenBoard(void) { TSdtStatisticsList myStatisticsList; int t_NetworkBaordDev=0; char a_DeviceName[120]; strcpy(a_DeviceName,":N_dtiB1
See Also None. In Appendix B - Message Blocks, the following Command Message Blocks were omitted: DTCAS_CLEAR_ALL_TEMPLATE This command clears all templates for a particular channel. The devh handle must be a valid DTI channel device handle. The reply message code, DTCAS_CLEAR_ALL_TEMPLATE_COMPLETE, is received in response to this command.
DTCAS_GET_NEXT_TEMPLATE This command gets the template for a particular channel. The devh handle must be a valid DTI channel device handle. The reply message code, DTCAS_GET_NEXT_TEMPLATE_COMPLETE, is received in response to this command.
DTCAS_GET_TEMPLATE_COMPLETE This reply message is sent in response to a DTCAS_GET_TEMPLATE command. The result code within the reply message block indicates the success or failure of the command. The buffer referenced by the replymsgp argument will contain a valid DTCAS_REPLY_MSG message block if dt_castmgmt( ) completes successfully.
template_id specifies the template identifier result indicates the success or failure of the command. This field set to 0 on success, or one of the following error values if the command fails: • DTCAS_ERR_TEMPLATE_NOT_DEFINED – The template was not found in the template table • DTCAS_ERR_TEMPLATE_TABLE_EMPTY – The template table is empty; no templates are defined • DTCAS_ERR_END_TMPL_TABLE- The next template was not found; no other templates are defined 3.4.
Update to Section 5.7.5, Select Resolution for Fax Transmission (IPY00040796) This section refers to the fx_sendfax( ) sndflag argument resolution settings of DF_TXRESLO and DF_TXRESHI. There are two new values for the sndflag argument, DF_TXRES_300_300 and DF_TXRES_200_400. Refer to the update for Chapter 10, Fax Library Function Reference, for ATFX_RESLN( ), ATFX_WIDTH( ), fx_rcvfax( ), and fx_sendfax( ) functions below. Update to Section 6.
Update to Chapter 10, Fax Library Function Reference, for ATFX_RESLN( ), ATFX_WIDTH( ), fx_rcvfax( ), and fx_sendfax( ) Functions (IPY00040796) There are two additional return values for the ATFX_RESLN( ) function, DF_RES_300_300 and DF_RES_200_400. These values are applicable to Dialogic® DM3 Boards only. Additionally, the function will now return 0 when the resolution is not supported.
Update to gc_DropCall( ) (PTR# 34237) On the gc_DropCall( ) function reference page, the following caution should be added: • With CAS protocols, the GCEV_DROPCALL event may be delayed when gc_DropCall( ) is called. GCEV_DROPCALL is sent to the application only when the channel becomes Idle. This is expected behavior of a CAS protocol. In the Offered state (ringing), there is no way for the receiving side to tell the calling side to stop ringing.
gc_ReleaseCallEx( ) functions to terminate the call completely. If GCEV_TASKFAIL is received, just use gc_ReleaseCallEx( ) to terminate the call; there is no need to use gc_DropCall( ). The last sentence of this paragraph is incorrect and should be deleted. Information about error handling in asynchronous mode, including what to do when GCEV_TASKFAIL is received, appears later on page 226.
Update to GCEV_EXTENSION Because of a new feature in the Service Update, a new event has been added, EXTENSIONEVT_RAWEEM. For further information about the new feature, see Section 1.33, “New Fax Parameter for Modem Receive Level”, on page 99 of this Release Update. 3.4.
CCPARM_CA_PAMD_QTEMP PAMD Qualification Template. Specifies which PAMD template to use. Possible values are: • PAMD_QUAL1TMP – Predefined qualification template. This is the default value. • -1 – No qualification template The CCPARM_CA_PAMD_QTEMP parameter can also be set to a qualification template ID that is defined in the CONFIG file. Setting CCPARM_CA_PAMD_QTEMP to a value of PAMD_QUAL2TMP is not supported.
Call Analog Technology Guide does not currently include any information about call transfer. For information about this feature, see Section 1.3, “Analog Call Transfer Support on Dialogic® Springware Boards”, on page 38 of this Release Update. Update for call transfer support on Dialogic® DMV160LP Board Because of a new feature in the Service Update, call transfer is now supported for Dialogic® DM3 Analog technology (Dialogic® DMV160LP Board only).
Updates to Section 4.10, gc_GetCallInfo( ) Because of a new feature in the Service Update, the gc_GetCallInfo( ) CATEGORY_DIGIT parameter is now supported on Dialogic® DM3 Boards. Section 4.10, gc_GetCallInfo( ), should be updated to indicate this. Because of a new feature in the Service Update, a new billing type has been added to CALLINFOTYPE called “CHARGE WITH CLEARING FROM INBOUND.” In addition, gc_GetCallInfo(CALLINFOTYPE) is now supported on Dialogic® DM3 Boards.
Note: Update to Section 4.18, gc_SetChanState( ) (PTR# 36726) The following note should be added to this section: When a channel is set to out-of-service state, not all protocols send the blocking pattern by default. For such protocols, a parameter in the .cdp file has to be set to the appropriate value so that the blocking pattern is sent when the channel is put out-of-service. Refer to the Dialogic® Global Call Country Dependent Parameters (CDP) for PDK Protocols Configuration Guide for more information.
Cause Value (Decimal) Cause Value (Hex) 14 0x0E Normal clearing 15 0x0F Network alarm 16 0x10 Pickup 17 0x11 Protocol error Description 18 0x12 Redirection 19 0x13 Remote termination 20 0x14 Call rejected 21 0x15 Special Information Tone (SIT) 22 0x16 SIT Custom Irregular 23 0x17 SIT No Circuit 24 0x18 SIT Reorder 25 0x19 Transfer 26 0x1A Unavailable 27 0x1B Unknown cause 28 0x1C Unallocated number 29 0x1D No route 30 0x1E Number changed 31 0x1F Destin
Section 1.46, “Dialogic® DI0408LSAR2 Board Support for Host Systems with Multiple NICs”, on page 159 of this Release Update. Update for early media Because of a new feature in the Service Update, information about early media should be added to Chapter 3, IP Call Scenarios. For information about this feature, see Section 1.52, “Early Media”, on page 213 of this Release Update.
Parameter Name: TcpTimedWaitDelay Value Type: REG_DWORD (DWORD Value) Valid Range: 30 to 300 seconds Also, see the following Microsoft information at these links: • Windows® 2000 http://support.microsoft.com/default.aspx?scid=kb;en-us;120642 • Windows® XP http://support.microsoft.com/default.aspx?scid=kb;en-us;314053 Update to Section 7.2.12, gc_MakeCall( ) Variances for IP (IPY00029956 = PTR# 36646) The following paragraph is added to Section 7.2.12, gc_MakeCall( ) Variances for IP, just before Section 7.
• IPCCLIB_START_DATA data structure reference page In the absence of the INIT_IPCCLIB_START_DATA( ) and INIT_IP_VIRTBOARD( ) functions, the user must manually initialize the IP_VIRTBOARD and IPCCLIB_START_DATA data structures before calling gc_Start( ). Refer to the reference pages for these structures for more details.
should be added in the ISDN-Specific Operations chapter. For information about this feature, see Section 1.47, “Support for QSIG NCAS Calls on Dialogic® DM3 Boards”, on page 161 of this Release Update. Update to Chapter 2, Global Call Architecture for ISDN (IPY00006540 = PTR# 34211) The following information should be appended to the end of Chapter 2: GCEV_EXTENSION Events There are ISDN-specific Global Call events, which will eventually be mapped to GCEV_EXTENSION.
Event GCIS_EXEV_NOTIFYGLOBAL when using Dialogic® Springware Boards Note: When using Dialogic® DM3 Boards, this event is not supported. Description A DROP request has been received; the request was made by sending the SndMsg_Drop message type via the gc_Extension(GCIS_EXID_SNDMSG) function. This event has two different meanings that depend upon the type of call: • Two-party call - the event is a request to disconnect the call. The application should respond by issuing a gc_DropCall( ).
Event GCIS_EXEV_FACILITYNULL when using Springware Boards Note: When using DM3 Boards, this event is not supported. GCIS_EXEV_INFOGLOBAL when using Springware Boards Note: When using DM3 Boards, this event is not supported. GCIS_EXEV_INFONULL when using Springware Boards Note: When using DM3 Boards, this event is not supported. GCIS_EXEV_L2BFFRFULL when using Springware Boards Description An ISDN_FACILITY message was received containing a Dummy (NULL) CRN.
Event GCIS_EXEV_NOUSRINFOBUF when using Springware Boards Description User IE buffer is not ready. Note: When using DM3 Boards, this event is not supported. GCIS_EXEV_NSI when using Springware Boards Note: When using DM3 Boards, this event is not supported. GCIS_EXEV_PLAYTONE when using Springware Boards A Network Specific Indication (NSI) message was received from the network. The application should use gc_GetCallInfo( ) to retrieve the NSI string(s) or look into the extension event data.
Event Description GCIS_EXEV_TONEREDEFINEFAIL when using Springware Boards The request to redefine tone(s) in the firmware tone template table failed. Note: When using DM3 Boards, this event is not supported. GCIS_EXEV_TRANSFERACK when using Springware Boards Note: When using DM3 Boards, this event is not supported. GCIS_EXEV_TRANSFERREJ when using Springware Boards A TRANSFER ACKNOWLEDGE message was received from the network. The indicated network has accepted a request to transfer a call.
Application Device Driver Firmware State Network CONNECTED DISCONNECTED gc_DropCall ( )* Disc GCEV_DISCONNECTED CALL_DISCONNECTED Call_Disconnected (Cause Value = 0) IDLE Firmware Does Nothing Until Release is Sent Release GCEV_DROPCALL gc_ReleaseCall ( )** CALL_CLEAR Rel_Comp ISDN_Block_Ts (Sync Model Only) Call_Dealloc NULL F/W Releases CRN CALL_DEALLOC_ACK Driver Releases CRN Return Notes: * = Application Should Set a "Drop Call" Flag ** = Application should ignore GCEV _DISCONNECTED if "D
Update to Section 4.1.7, Retrieve the Network Call Reference Value (CRV) (PTR# 32418) In Section 4.1.7, Retrieve the Network Call Reference Value (CRV) on page 100, the first note incorrectly references a function called gc_GetCRV( ). There is no such function. The correct function name is gc_GetNetCRV( ). Update to Section 4.4.1, Alarm Handling for DM3 Boards In Section 4.4.
3.4.16 Dialogic® Global Call SS7 Technology Guide There are currently no updates to this document. 3.4.17 Dialogic® IP Media Library API Programming Guide Update to Section 6.1, Introduction to DTMF Handling (PTR# 33826) The fourth paragraph in Section 6.1, Introduction to DTMF Handling (page 21) and the note that follows the fourth paragraph should be ignored. The IPM_RFC2833MUTE_AUDIO parameter that the paragraph refers to is not supported; DTMF audio is always muted when in RFC2833 mode.
In the cc_GetEvtMsk( ) function reference pages, Table 20, Bitmask Values, incorrectly lists CCMSK_TERMINATE as a supported bitmask type. The CCMSK_TERMINATE bitmask type is not supported (PTR# 29203). In the cc_SetEvtMsk( ) function reference pages, Table 24, Bitmask Values, incorrectly indicates the default values for CCMSK_SERVICE_ACK and CCMSK_SETUP_ACK as “Not enabled”. The correct default values are “Enabled.
The cc_GetDLinkState( ) function retrieves the logical data link state (operable or inoperable) of the specified board device for PRI or station device for BRI. In the description of the state_buf parameter for the cc_GetDLinkState( ) function, only two possible data link states are defined: DATA_LINK_UP and DATA_LINK_DOWN. DATA_LINK_DISABLED is not a valid value (PTR# 25745).
requirements, see Section 1.40, “PBX Integration Support for Nortel BCM”, on page 111 of this Release Update. Updates for implementation of ROLM Call Waiting LED Because of enhancements introduced in the Service Update, the d42_indicators( ) function can now return the LED status of the Call Waiting LED for the ROLMphone 400. Table 8, ROLMphone 400 Direct Key Dialing Strings for Feature Keys on pages 44 and 45, and the figure on page 46 should be updated to reflect this.
Update to Section 4.6.5, Setting the Message Waiting Indicator, for Nortel Meridian 1 In Section 4.6.5, Setting the Message Waiting Indicator, the last paragraph (on page 125) should be ignored. The ability to determine the state of the Message Waiting Indicator is not supported for Nortel Meridian 1 systems. 3.4.
Section 1.59, “Enhanced Special Information Tone Frequency Detection on Dialogic® DM3 Boards”, on page 229 of this Release Update. Update to dx_createtone( ) function Because of a new feature in the Service Update, the dx_createtone( ) function can be used with the new custom special information tones (SITs) described in Section 1.8, “Enhanced Special Information Tones on Dialogic® DM3 Boards Using Voice and Global Call APIs”, on page 55 of this Release Update.
DM/V2400A Board). For further information, see Section 1.32, “Time Stamp for ToneOn/Off Events”, on page 97 of this Release Update. New TN_TIMESTAMP data structure Because of a new feature in the Service Update, a new data structure, TN_TIMESTAMP, has been added to provide a time stamp for tone-on/off events. For further information, see Section 1.32, “Time Stamp for Tone-On/Off Events”, on page 97 of this Release Update. 3.4.
For information on running transaction record on a single board, see the technical note posted on the Dialogic® web site at: http://www.dialogic.com/support/helpweb/dxall/tnotes/legacy/dlsoft/tn253.htm Update to Section 10.6, Fixed-Line Short Message Service (SMS) This section erroneously states that SMS is not supported on Dialogic® Springware Boards. SMS is supported on Springware Boards.
event is reported. On both types of boards a DE_TONEOFF event is reported when the tone is no longer present. Update to Section 13.1.9, Guidelines for Creating User-Defined Tones (IPY00006580 = PTR# 34546) The following guideline should be added to this section: • On Dialogic® DM3 Boards, building and adding tones of zero frequency values to a tone template can cause firmware failures. Update to Section 13.1.10.
Dialogic® IP Multicast Client (IPML) Demo Guide 3.5.1 The following note is added to Section 2.1, Hardware Requirements (PTR# 31488): Note: When using a single span Dialogic® DM/IP Board, the demo supports only one board in the system. Dialogic® IP Multicast Server (IPML) Demo Guide 3.5.2 The following note is added to Section 2.1, Hardware Requirements (PTR# 31488): Note: When using a single span Dialogic® DM/IP Board, the demo supports only one board in the system. Dialogic® System Release 6.
