Dialogic® System Release 6.
Copyright and Legal Notice Copyright © 2005-2012, Dialogic Inc.. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Inc. at the address provided below. All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a commitment on the part of Dialogic Inc. and its affiliates or subsidiaries (“Dialogic”).
Dialogic® System Release 6.
Dialogic® System Release 6.
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.1 CompactPCI for Windows® (sometimes also referred to herein as “System Release 6.1 CompactPCI 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.1 CompactPCI 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.1 CompactPCI for Windows®, which is a document that has been and is intended to be periodically updated throughout the lifetime of the release. Document Rev 57 - June 11, 2012 Updated for Service Update 201. In the Post Release Developments section, added : • PDK Support for Automatic Answer and Reject of Inbound Calls.
Document Revision History Document Rev 54 - November 19, 2010 Updated for Service Update 196. In the Post Release Developments section, added Media Load Support for the Dialogic® DM/V1200A-4E1-cPCI Board. In the Release Issues section, added the following resolved problems: IPY00092028, IPY00092115, IPY00092212. Document Rev 53 - August 3, 2010 Updated for Service Update 195. In the Post Release Developments section, updated the Media Load 2 table in Section 1.
Document Revision History In the Post Release Developments section, added an Important Notice about System Release Update Installation. In the Release Issues section, added the following resolved problems: IPY00080772, IPY00080944, IPY00081061. In the Documentation Updates section, added a note in the Dialogic® System Release 6.1 CompactPCI for Windows® Release Guide that the update install should not be used when upgrading from a Service Update prior to SU 176 to a more recent build.
Document Revision History Document Rev 45 - published February 6, 2009 Updated for Service Update 186. In the Post-Release Developments section, added the Performance Technologies CPC5505-B3M3H1 SBC under Support for Compute Platforms. In the Release Issues section, added the following resolved problems: IPY00078576, IPY00079212, IPY00079365.
Document Revision History Document Rev 42 - published November 25, 2008 Updated for Service Update 179. In the Release Issues section: • Added the following resolved problem: IPY00078854. • Added the following known problem: IPY00079022. Document Rev 41 - published November 11, 2008 Updated for Service Update 178. In the Release Issues section, added the following resolved problems: IPY00045159, IPY00045292, IPY00045395, IPY00045456, IPY00078445, IPY00078519.
Document Revision History Document Rev 39 - published September 3, 2008 Updated for Service Update 175. In the Release Issues section, added the following resolved problems: IPY00044100, IPY00044425, IPY00045132. Document Rev 38 - published August 26, 2008 Updated for Service Update 174.
Document Revision History In the Documentation Updates section: • Added an update to the Dialogic® Global Call API Library Reference for the gc_util_insert_parm_val( ) function (IPY00043078). • Added an update to the Dialogic® Global Call SS7 Technology Guide about opening trunk devices for SS7. • Added that new versions of the Dialogic® Modular Station Interface API Programming Guide and Dialogic® Standard Runtime Library API Library Reference are now available on the online documentation bookshelf.
Document Revision History In the Documentation Updates section: • Added procedures for checking the firmware version and upgrading the firmware for Dialogic® IPT Boards in the Dialogic® System Release 6.1 CompactPCI for Windows® Administration Guide. • Added that a new version of the Dialogic® Global Call Country Dependent Parameters (CDP) for PDK Protocols Configuration Guide is now available on the online documentation bookshelf.
Document Revision History In the Release Issues section: • Added the following resolved problem: IPY00042168. • Added the following known problem: IPY00042226. In the Documentation Updates section, added updates to the Dialogic® System Software Diagnostics Guide because of new features in the Service Update. Document Rev 27 - published February 19, 2008 Updated for Service Update 157. In the Release Issues section, added the following resolved problems: IPY00041407, IPY00041580, IPY00041740, IPY00041855.
Document Revision History In the Release Issues section, added the following resolved problems: IPY00039661, IPY00040536, IPY00040685, IPY00040832, IPY00041078, IPY00041209, IPY00041233.
Document Revision History Document Rev 21 - published September 7, 2007 Updated for Service Update 145. In the Post-Release Developments section, added IP Multicast Client Support. In the Release Issues section, added the following resolved problems: IPY00038981, IPY00039155, IPY00039412, IPY00039586. Also added a resolved problem (no defect number) regarding ipm_GetLocalMediaInfo( ) returning an IP address of “0.0.0.0” after a hot swap.
Document Revision History Document Rev 19 - published July 12, 2007 Updated for Service Update 140. In the Release Issues section, added the following resolved problems: IPY00038060, IPY00038240, IPY00038365, IPY00038572, IPY00038894. Document Rev 18 - published June 29, 2007 Updated for Service Update 139. In the Post-Release Developments section: • Added Troubleshooting Information for RTF Logs. • Added Remote Diagnostics Package. • Added Enhanced Diagnostics Tools.
Document Revision History Technology Guide, Dialogic® IP Media Library API Programming Guide, Dialogic® IP Media Library API Library Reference. Document Rev 16 - published May 29, 2007 Updated for Service Update 135. In the Post-Release Developments section: • Added New Operating System Support for Windows® Server 2003 SP2. • Added Support for Peripheral Hot Swap (PHS) on Additional Compute Platforms (Advantech MIC-3081B with MIC-3369C SBC, and Diversified Technologies PlexSys4 with CPB4612 SBC).
Document Revision History • Added File Management Enhancements for ISDNtrace Tool. • Added New Media Load for DM/V2400A-cPCI Boards. In the Release Issues section, added the following resolved problems: IPY00006707 (PTR 33803), IPY00007470 (PTR 32437), IPY00009499 (PTR 33932), IPY00028633 (PTR 35748), IPY00036347, IPY00036423, IPY00036469, IPY00036504, IPY00036861, IPY00037004.
Document Revision History Document Rev 11 - published January 2, 2007 Updated for Service Update 122. In the Post-Release Developments section, added Modify an Existing SIP Call Using reINVITE for Dialogic® IPT Boards. In the Release Issues section, added the following resolved problems: IPY00033563, IPY00033912, IPY00034036, IPY00035350, IPY00035613, IPY00035806, IPY00035822, IPY00035831.
Document Revision History Document Rev 07 - published September 15, 2006 Updated for Service Update 115. In the Post-Release Developments section: • Added New Diagnostics Management Console. • Added New Runtime Trace Facility (RTF) Manager. In the Documentation Updates section, added documentation update to the Dialogic® System Release 6.1 CompactPCI for Windows® Release Guide about requirements for diagnostic tools. Document Rev 06 - published August 28, 2006 Updated for Service Update 113.
Document Revision History Document Rev 02 - published June 13, 2006 Updated for Service Update 103. In the Post-Release Developments section: • Added Service Update for Dialogic® System Release 6.1 CompactPCI for Windows®. • Added Media Channel Reset Capability (Stuck Channel Recovery). • Added Notification of Layer 1 Alarm Events on SS7 Boards. • Added Global Call Support for Time Slots on Dialogic® SS7 Boards Running in DTI Mode.
1. Post-Release Developments This section describes significant changes to the system release subsequent to the general availability release date. • Service Update for Dialogic® System Release 6.1 CompactPCI for Windows®25 • PDK Support for Automatic Answer and Reject of Inbound Calls . . . . . . . . . . 25 • Status Monitor Tool Support for 16 Span Boards . . . . . . . . . . . . . . . . . . . . . . . 27 • Improvement to Call Progress Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
• Media Channel Reset Capability (Stuck IP Media Channel Recovery) . . . . . . 78 • Dialogic® Global Call API Access to New H.323/Q.931 Message IEs . . . . . . . 83 • On-Demand Full Reset of Dialogic® DM3 Boards . . . . . . . . . . . . . . . . . . . . . . 89 • New Dialogic® Diagnostics Management Console . . . . . . . . . . . . . . . . . . . . . . 90 • New Runtime Trace Facility (RTF) Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 91 • Support for Reporting Billing Type . . . . . . . . . . . .
1.2.1 Feature Implementation With this enhancement to the PDK upon enablement through Global Call, when the gc_DropCall( ) function is called before gc_AnswerCall( ), the protocol will answer and then immediately hang-up the call. This behavior enacts a full disconnect, complete with the sending of a proper signal to the switch to abandon the call. To accomplish this, the CDP_Forced_Release_Enabled parameter is added to the respective Country Dependent Parameter (.cdp) files.
1.3 Status Monitor Tool Support for 16 Span Boards Service Update 199 enhances the Status Monitor tool to support the Dialogic® DMN160TEC and DMT160TEC boards. 1.3.1 Status Monitor GUI Update To support the 16-line Dialogic® DMN160TEC and DMT160TEC boards, the display pane of the Call Status Monitor window now contains three additional tabbed pages, each page representing the status of four lines on the board. This change retains the existing single screen StatusMon GUI.
Media Load Support for the Dialogic® DM/V1200A4E1-cPCI Board 1.5 Service Update 196 adds Media Load 9B (ML9B) support for the Dialogic® DM/V1200A4E1-cPCI board. This media load provides rich conferencing (conferencing plus echo cancellation and Tone clamping). It also disables the network front ends. 1.5.1 Feature Description Predefined sets of features for Dialogic® DM3 Boards are provided in media loads.
1.6 Handling non-2xx Responses to T.38 Switch Service Update 194 introduces Global Call support for RFC3261 compliance for non-2xx responses to re-INVITE requests to switch to or from audio to T.38 fax and back. This feature has been tested on Dialogic® IPT Boards. 1.6.
ipConnect.
case GCEV_CONNECTED: /* received Connect event */ /* in conversation */ ipConnect.version = 0x100; ipConnect.mediaHandle = pline->mediaH; ipConnect.faxHandle = pline->faxH; ipConnect.connectType = IP_FULLDUP; gc_util_insert_parm_ref(&parmblkp, IPSET_FOIP, IPPARM_T38_CONNECT, (sizeof(IP_CONNECT)), (void *)(&ipConnect)); gc_SetUserInfo(GCTGT_GCLIB_CRN, pline->crn, parmblkp, GC_SINGLECALL); gc_util_delete_parm_blk(parmblkp); /* Initiate T.
INT32 switchFromFaxToAudio() { GC_PARM_BLK *parmblkp = NULL; IP_CONNECT ipConnect; ipConnect.version = 0x100; ipConnect.
if( gc_util_insert_parm_ref(&parmblkp, GCSET_CHAN_CAPABILITY, IPPARM_LOCAL_CAPABILITY, sizeof(IP_CAPABILITY), &ipcap) != GC_SUCCESS ) { //error } gc_ReqModifyCall (GCTGT_GCLIB_CRN,pline->crn, parmblkp, EV_ASYNC); gc_util_delete_parm_blk(parmblkp); break; case GCEV_MODIFY_CALL_ACK: // Switch Complete fx_sendfax(); break; case GCEV_MODIFY_CALL_REJ: case GCEV_MODIFY_CALL_FAIL: /* received extension event for media readiness */ gc_util_insert_parm_ref(&parmblkp, IPSET_FOIP, IPPARM_T38_DISCONNECT,(sizeof(IP_CONN
Note: The EVT_NETWORKFAILURE1 event type, which is supported on IPT Boards, is not supported on DM/IP Boards since they have only one network interface. (For information about EVT_NETWORKFAILURE1, see Section 1.25, “Modified Alarm Events for Media LAN Disconnect”, on page 74 of this Release Update.) 1.8.
Event handling in IPML for the network failure alarm is identical to that for QoS alarm events, except that the handler needs to distinguish between alarm-on and alarm-off events. The event that is generated when a network failure is detected is of type IPMEV_QOS_ALARM, and it contains associated data of type IPM_QOS_ALARM_DATA. The eQoSType field of this data structure is QOSTYPE_NETWORKFAILURE, and the eAlarmState may be either ALARM_STATE_ON or ALARM_STATE_OFF.
For more information about the Dialogic® IP Media Library API, see the following documents: • Dialogic® IP Media Library API Programming Guide • Dialogic® IP Media Library API Library Reference For more information about the Dialogic® Global Call API in general, see the following documents: • Dialogic® Global Call API Programming Guide • Dialogic® Global Call API Library Reference For features specific to IP technology, see: • Dialogic® Global Call IP Technology Guide 1.
• Media Load 5E • Media Load 2 • Media Load 1E Media Load 2E Media load 2E is a voice/CSP media load for the DM/V4800BC Board.
Note: This feature does not provide additional CSP streaming encoding algorithms, sampling rates, or sampling sizes; they remain being: • G.711 mu-law PCM, 8 kHz sampling rate, 8-bit resolution (64 Kbps) • G.711 A-law PCM, 8 kHz sampling rate, 8-bit resolution (64 Kbps) • Linear PCM, 8 kHz sampling rate, 16-bit resolution little Endian and big Endian format (128 Kbps) regardless of the coders being used for playing files during the CSP streaming session.
Features Supported Basic Voice; Special Coders FSK V.17 Fax Transaction Record Channel Density 385 385 15 0 Note: Transaction record is not supported. Media load 1E supports the same coders for playback and record as media load 1, and also supports the following special coders concurrent with V.17 fax: • G.711 A-law and mu-law PCM, 8 kHz sampling rate, 8-bit resolution (64 Kbps) with 8- bit reversal • G.
1.10.3 Documentation The online bookshelf provided with Dialogic® System Release 6.1 CompactPCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics. For detailed information about configuring Dialogic® DM/V4800BC Media Boards, see the Dialogic® DM3 Architecture for CompactPCI on Windows® Configuration Guide.
The following configuration options existed in the previous version of DebugAngel, and their default values remain the same. However, changes in the behavior of the AutoRename registry entry provide more options for the processing of multiple files. DebugLevel Enables/disables error or warning debug output. When set to 1, the debug output can be viewed using the Windows DebugView.exe utility. Default is 0. LogFile Specifies the full path and file name of the log file to be used by DebugAngel.
When the limit is reached, the file is truncated and logging is resumed from the beginning of the file. AutoRename=1 The log file name specified in the LogFile registry entry is used. If the file exists when DebugAngel starts, it is backed up and renamed with a .bak extension, to avoid overwriting the original. For example, DebugAngel.log is renamed DebugAngel.log.bak. When MaxFileSize=0, the file is allowed to grow without limit. When MaxFileSize>0, the file is allowed to grow to the specified limit.
AutoRename Options for Multiple Log Files This section explains how the AutoRename options work when there are multiple log files (MaxFiles>1). Note: When MaxFiles is set greater than 1, the value of the AutoRename registry key is automatically set to 3. Furthermore, when MaxFiles>1, AutoRename must be set to either 2 or 3. If MaxFiles>1 and AutoRename is set to either 0 or 1, a warning message is generated and the value of the AutoRename registry key is reset to 3.
MaxFiles log files are saved at any time. The file naming is repeated starting with the number 00 again. See Examples of Multiple Log Files below. Examples of Multiple Log Files With the following settings (and default LogFile name): • AutoRename=2 • MaxFileSize=65536 • MaxFiles=5 The resulting files in C:\Program Files\Dialogic\log\ are: 65,536 DebugAngel.09_26_at_16_29_08.031.log 65,536 DebugAngel.09_26_at_16_33_18.000.log 65,536 DebugAngel.09_26_at_16_44_09.008.log 65,536 DebugAngel.
1.12 File Management Enhancements for PDK Trace Tool With the Service Update, new command line options are provided with the Dialogic® PDK Trace tool to set the output log file size and to create multiple log files. 1.12.1 Feature Description The PDK Trace tool logs information about PDK protocols on Dialogic® DM3 Boards, to aid in the troubleshooting of protocol issues. The tool is described in the Dialogic® System Software Diagnostics Guide.
New and Enhanced Command Line Options Two new command line options, -a and -m, have been added for PDK Trace, and the -f option has been enhanced to allow log file management as follows: -a# Log file array size, specifies the maximum number of log files to maintain (optional). The default value is 1, and the maximum value is 10.
• DD - day of the month (01-31) • YYYY - year (e.g., 2008) • xx - hour (24-hour format, 00-23) • yy - minute (00-59) • zz - second (00-59) Example: If PDK Trace is started on February 17, 2008, at 3:11:27 p.m., with the -f command line option of -f[ExampleLog], the name of the first log file created is: ExampleLog-02172008-15h11m27s.log When this file reaches the maximum size, it is closed and a new log file is created.
1.13.2 SIP_STACK_CFG Data Structure The SIP_STACK_CFG structure definition has been added in the gcip.h file. The new data structure is described below. Note: SIP stack parameters can only be configured once per virtual board (at gc_Start( )) and remain in effect throughout the Global Call application (per process). Dialogic® System Release 6.
SIP_STACK_CFG typedef struct { unsigned long version; /* version set by INIT_SIP_STACK_CFG */ int retransmissionT1; int retransmissionT2; int retransmissionT4; int generalLingerTimer; int inviteLingerTimer; int provisionalTimer; int cancelGeneralNoResponseTimer; int cancelInviteNoResponseTimer; int generalRequestTimeoutTimer; } SIP_STACK_CFG; Description The SIP_STACK_CFG data structure is used to configure selected SIP stack parameters such as timers.
protocol, T4 determines the time that a UAS waits after receiving an ACK message and before terminating the transaction. The default value is 10000. generalLingerTimer After a server sends a final response, the server cannot be sure that the client has received the response message. The server should be able to retransmit the response upon receiving retransmissions of the request for generalLingerTimer milliseconds. The default value is 32000.
1.13.3 Sample Code The following example sets the SIP T1 timer to 64 ms. #include “gclib.h” .. .. #define BOARDS_NUM 1 .. ..
With the Service Update, the ability to disable/enable the sending of the automatic SIP reINVITE message upon media switch can now be configured with the Dialogic® Global Call API to prevent this glare condition. 1.14.1 Feature Description Overview of Use Case A user application can enable and disable the unsolicited GCEV_EXTENSION notification events associated with certain types of transition events, including media streaming connection state changes.
The new parameter IDs are added for the existing IPSET_CONFIG set ID as shown in the following table. Set ID IPSET_ CONFIG Parameter ID Set Send Retrieve SIP/ H.
if (gc_SetConfigData(GCTGT_CCLIB_NETIF,linedevbp, target_datap, 1000, GCUPDATE_IMMEDIATE , &request_id, EV_ASYNC) != GC_SUCCESS) { //print error rcode=FALSE; } gc_util_delete_parm_blk(target_datap); target_datap = NULL; } Re-Enabling Transmission of Automatic re-INVITE on a Line Device EnableFToAReinvite() { GC_PARM_BLK *target_datap = NULL; if ((gc_util_insert_parm_val(&target_datap, IPSET_CONFIG, IPPARM_SIP_FAXTOAUDIO_AUTO_REINVITE_ENABLE, sizeof(int), NULL)) != GC_SUCCESS) { fprintf(stderr, "E%04d(%s):
1.15 IP Multicast Client Support IP Multicast client, which was supported in previous system releases, is now supported in Dialogic® System Release 6.1 CompactPCI for Windows® on Dialogic® DM/IP Boards. IP Multicast is a one-to-many protocol that provides a scalable solution that efficiently uses network resources and bandwidth.
#include #include #include int nMulticastGroupPort = 2500; char *szMulticastGroupAddress = "225.0.0.1"; char *szDeviceName = "ipmB1C1"; void StartMulticastClient(void) { int nDeviceHandle; IPM_MEDIA_INFO MediaInfo; // Open an IP Media Channel nDeviceHandle = ipm_Open(szDeviceName, NULL, EV_SYNC); if (nDeviceHandle == -1) { printf("Failure Opening IP Media Channel %s", szDeviceName); // Perform Error Processing } // Join the IP Media Channel to a Multicast Group.
1.16 Troubleshooting Information for RTF Logs To assist in troubleshooting, a table showing runtime and firmware errors that may appear in Dialogic® Runtime Trace Facility (RTF) logs is now available. You can get a description of errors and the suggested action to resolve the error. To access the table, use this link: • Error Code Table For runtime errors, the table provides the following information: Internal error value The error code detected internally by the library.
Error subclass Provides a bit more specialization with regard to the error class. Whenever possible, if a class could be subdivided into more specific classifications, it was done. The use of the error subclass is the same as that of the error class. Action to be taken The suggested action to resolve the error. 1.17 Remote Diagnostics Package A remote diagnostics package is now available that allows you to run Dialogic® diagnostics utilities remotely from a central site.
Requirements at central site: • SSH client • IP connectivity to managed sites • Java Runtime Environment (JRE) version 1.5 or later Requirements at managed sites: • SSH server • IP connectivity to central site • Dialogic® System Release 6.1 CompactPCI for Windows® installed 1.18 Enhanced Diagnostics Tools The Service Update introduces enhanced versions of the following diagnostics tools: • PSTN Diagnostics (pstndiag) • Status Monitor (statusmon) Notes:1. Java Runtime Environment (JRE) version 1.
Running the PSTN Diagnostics Tool To run the new version of pstndiag, enter the command: • pstndiag -j (The previous version of the tool is still supported and can be run by entering the command pstndiag without the -j.
1.19 New QoS Alarms for RTCP and RTP Inactivity Dialogic® IPT Boards monitor for various Quality of Service (QoS) alarms such as excessive average jitter, percentage of lost packets, and RTP packet latency. With the Service Update, two new QoS alarms for Dialogic® IPT Boards are provided: QOSTYPE_RTCPTIMEOUT QoS alarm for Real Time Control Protocol (RTCP) inactivity QOSTYPE_RTPTIMEOUT QoS alarm for Real Time Protocol (RTP) inactivity Note: The two new QoS alarms are supported on Dialogic® IPT Boards only.
value for some parameters and non-default values for other parameters. The default settings for the two new QoS alarm types are: Time Interval (ms) Debounce On (ms) Debounce Off (ms) QOSTYPE_ RTCPTIMEOUT 0 0 0 QOSTYPE_ RTPTIMEOUT 0 0 0 QoS Type Fault Threshold %Success Threshold %Fail Threshold 250(x100 msec = 25 sec) 0 0 1200(x100 msec = 120 sec) 0 0 Note: Only the fault thresholds are configurable; all other parameters must be set to 0.
value for some parameters and non-default values for other parameters. The default settings for the two new QoS alarm types are: Time Interval (ms) Debounce On (ms) Debounce Off (ms) QOSTYPE_ RTCPTIMEOUT 0 0 0 QOSTYPE_ RTPTIMEOUT 0 0 0 QoS Type Fault Threshold %Success Threshold %Fail Threshold 250(x100 msec = 25 sec) 0 0 1200(x100 msec = 120 sec) 0 0 Note: Only the fault thresholds are configurable; all other parameters must be set to 0.
Minimum Fault Threshold Maximum Fault Threshold RTCP timeout unFaultThreshold 50 1200 250 RTP timeout unFaultThreshold 50 1200 1200 IPM_QOS_THRESHOLD_DATA Structure Parameter Default Fault Threshold Note: Fault threshold unit is 100 msec. Threshold values range from 5 seconds (50 x 100 msec) to 120 seconds (1200 x 100 msec) with a resolution of 1000 msec. The threshold values can be modified at any time.
the expected time, set RTP timeout unFaultThreshold higher than RTCP timeout unFaultThreshold. 1.19.3 Documentation The online bookshelf provided with Dialogic® System Release 6.1 CompactPCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics.
1.22 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 Dialogic® R4 API TPT structure.
conveniently shows the date and time the log was created. The user also has an option to disable logging to STDOUT to help manage trace output. New Command Line Options Currently, the ISDNtrace tool supports the following command line options as described in the Dialogic® System Software Diagnostics Guide: syntax: isdntrace -b# [-f xxxx] [-d#] -b Logical ID of board (required). Use the listboards utility (Linux) or the Dialogic® Configuration Manager (DCM) (Windows) to obtain the board’s logical ID.
Details about these command line options follow: -a This command line option allows the user to specify the maximum number of log files to maintain. The user can specify a log file array size between 1 and 10. By default, the number of log files to be archived is 1. If the user specifies the -f command line option but does not specify this option (or specifies it with an array size of 1), then ISDNtrace creates a single log file that grows without bound (that is, no limit to the log file size).
Alternatively, the user can specify the -f command line option with a log file name specified as in the following example: isdntrace -b0 -f test In this example, if ISDNtrace was started on January 17, 2007 at 03:11:27 pm, the resultant log file name would be: test-01172007-15h11m27s.log It should be noted that since the log file name created by ISDNtrace has a .log extension appended to it, if the user specifies a log file name with a .
---0-------0010 4: 1-------0010000 Hex Dump: 02 01 e6 ce 08 02 82 90 Enqueue Failed Spare Location Extension Bit Cause Value 02 1e 2a 45 08 In order to avoid loss of trace information and provide more robust performance of the ISDNtrace tool, the -s command line option should be specified to disable trace output to STDOUT whenever the capture of trace information for a large amount of calls is being performed, or “enqueue fail” failures occur. 1.23.
for CompactPCI on Windows® Configuration Guide for more information about media loads.
Features Supported Rich Conferencing with Echo Cancellation and Tone Clamping Maximum Conference Size without Bridging Fax Channel Density 250 Mixed: One with conference size of 90, and 10 with conference size of 16 each 30 Media load 9F-MC supports a total of 11 DSP conference resources or DCB devices, each represented in the Audio Conferencing (DCB) API as a device dcbBnDy. It is the last DSP/DCB device with the maximum conference size of 90.
reduces the call duty cycle, making audio degradation less likely even at full 420 channel voice density. 2. The maximum bit rate for standard play/record with this media load is 64 Kbps.
For detailed information about configuring Dialogic® DM/V2400A-cPCI and DM/V4800BC Media Boards, see the Dialogic® DM3 Architecture for CompactPCI on Windows® Configuration Guide. Note: The online bookshelf has not been updated for this feature, so the Dialogic® DM3 Architecture for CompactPCI on Windows® Configuration Guide does not currently include information about media loads 9F, 9F-MC, and 10F. 1.
1.25.2 Supported Boards The following boards support this feature: • Dialogic® IPT Boards 1.25.3 Documentation The online bookshelf provided with Dialogic® System Release 6.1 CompactPCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics. For more information about the Dialogic® IP Media Library API, see the Dialogic® IP Media Library API Library Reference. 1.
1.27 Modify an Existing SIP Call Using re-INVITE for Dialogic® IPT Boards With the Service Update, the user will be able to modify an existing SIP call using reINVITE for the Dialogic® IPT Boards. 1.27.1 Feature Description The ability to modify an existing SIP call using re-INVITE is now supported on Dialogic® IPT Boards. As with the Dialogic® DM/IP Boards, the Dialogic® IPT Boards do not currently support coder changes.
PDK log messages are categorized as error, warning, or info messages. All error, warning, and info messages are displayed in the RTF log. Error and warning messages are also displayed in the Windows® Event Viewer because their occurrence indicates that the PDK download process has been critically impacted. The following are examples of the Warning text that is displayed when a pdk.cfg file is detected and regenerated: In the Windows® Event Viewer: Date: 9/22/2006 Source: PDKManager Time: 2:22.
1.28.3 Documentation The online bookshelf provided with Dialogic® System Release 6.1 CompactPCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics. For more information about RTF, see the Dialogic® System Software Diagnostics Guide. 1.
ipm_ResetChannel( ) function only resets the media channel and does not have any effect on the signaling channel. Modified Dialogic® Global Call API Functionality The gc_ResetLineDev( ) function has been modified to perform ipm_ResetChannel( ) functionality in the background.
ipm_ResetChannel( ) reset an IP Media channel Name: int ipm_ResetChannel(nDeviceHandle, eResetMode, usMode) Inputs: int nDeviceHandle • IP Media device handle eIPM_RESET_MODE eResetMode • reset mode unsigned short usMode • async or sync mode setting Returns: 0 on success -1 on failure Includes: srllib.h ipmlib.h Category: System Control Mode: asynchronous or synchronous Platform: DM/IP Description The ipm_ResetChannel( ) function resets an IP Media channel.
ipm_ResetChannel( ) function successfully initiates the reset operation asynchronously, but subsequently fails to complete successfully, an IPMEV_RESETFAIL event is delivered. Termination Events IPMEV_RESET Indicates successful completion; that is, the supplied IP Media channel has been reset. IPMEV_RESETFAIL Indicates that the reset operation failed.
/* . . Main Processing . . */ /* Application needs to issue reset on IP channel device handle, nDeviceHandle. ASSUMPTION: A valid nDeviceHandle was obtained from prior call to ipm_Open() and session has been started by calling ipm_StartMedia() some time earlier. ipm_Stop() has been issued on the device and stop completion reply does not come within acceptable time duration.
default: printf("Received unexpected event = %d for device = %s\n", nEventType, ATDV_NAMEP(nDeviceID)); break; } } See Also 1.29.4 • ipm_Stop( ) • gc_ResetLineDev( ) Feature Limitations or Restrictions The following restrictions and limitations apply to the feature: • This solution only addresses scenarios where the firmware and host have lost synchronization or entered a bad state. DSP crashes or catastrophic firmware failures are not recoverable without re-download of the board firmware.
1.30.1 Feature Description You now have the ability to access additional fields in the calling party number (CGPN) and called party number (CDPN) IEs within a H.225/Q.931 SETUP message when using H.323 IP call signaling with the Dialogic® IPT Boards. The SETUP message is a standard call signaling message used by a calling H.323 entity to establish a connection with the called entity. This message is currently supported with limited access to information fields in the CGPN and CDPN IEs.
The following definitions are in the gcip_defs.h file: #define IPPARM_ CGPN_TYPE_OF_NUMBER #define IPPARM_ CDPN_TYPE_OF_NUMBER #define IPPARM_ CGPN_NUMBERING_PLAN_ID #define IPPARM_ CDPN_NUMBERING_PLAN_ID #define IPPARM_ CGPN_SCREENING_INDICATOR #define IPPARM_ CGPN_PRESENTATION_INDICATOR 0x13 0x14 0x15 0x16 0x17 0x18 The following data variables are in the gcip.h file: typedef unsigned char typedef unsigned char typedef unsigned char typedef unsigned char 1.30.
1.30.4 Setting Up CPN Fields in the GC_PARM_BLK Data Structure Before calling the gc_MakeCall( ) function, you must set up the CPN fields to be included in the GC_PARM_BLK data structure. The GC_PARM_BLK should include the existing parameter set ID IPSET_CALLINFO and the newly defined parameter IDs described in the New Parameter IDs section, which specifies which CPN fields are to be set in the parameter block structure of a Make Call block.
gc_util_insert_parm_ref(&pParmBlock, IPSET_ CALLINFO, IPPARM_CDPN_NUMBERING_PLAN_ID, sizeof(unsigned char), &cdpn_npi); gc_util_insert_parm_ref(&pParmBlock, IPSET_ CALLINFO, IPPARM_CGPN_SCREENING_INDICATOR, sizeof(unsigned char), &cgpn_si); gc_util_insert_parm_ref(&pParmBlock, IPSET_ CALLINFO, IPPARM_CGPN_PRESENTATION_INDICATOR, &cgpn_pi); /*. .. Continue Main processing. … call gc_MakeCall() */ } 1.30.
Code Examples Specifying CPN Field for Receiving A code example of how to specify the CPN fields for receiving is shown below. This example is just for the Calling Number Type of Number field. The method to specify the other CPN data would be similar.
switch (parmp->parm_ID) { case IPPARM_CGPN_TYPE_OF_NUMBER: printf("\tReceived CPN data Calling Party Type of Number: %d\n", (*(unsigned char*)(parmp->value_buf))); break; case IPPARM_CDPN_TYPE_OF_NUMBER: printf("\tReceived CPN data Called Party Type of Number: %d\n", (*(unsigned char*)(parmp->value_buf))); break; default: printf("\tReceived unknown extension parmID %d\n", parmp->parm_ID); break; } break; } parmp = gc_util_next_parm(parm_blk,parmp); } } 1.30.
new parameter, Run_full_POST_at_download, on the Misc property sheet in the DCM. For NCM users, a new parameter can be used with the NCM_SetValueEx( ) and NCM_GetValueEx( ) functions. The values for the parameter are as follows: • True: enables full POST to be run before board download. • False [default]: disables the full POST feature for Dialogic® DM3 Boards. The user can select a single board.
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.
and also to indicate the type of billing for the call (for example, CHARGE, NO CHARGE, or CHARGE WITH CLEARING FROM INBOUND). This feature is already supported on Dialogic® Springware Boards; however, CHARGE WITH CLEARING FROM INBOUND is a new billing type that is also supported on Springware Boards now. For further information about this feature, see the description of the gc_GetCallInfo( ) function CALLINFOTYPE info_id parameter in the Dialogic® Global Call E1/T1 CAS/R2 Technology Guide. 1.
This feature provides new API functions in the Dialogic® Voice library and in the Dialogic® Continuous Speech Processing (CSP) library that enable the application to recover from the stuck channel and return it to an idle and usable state. Note: Not all stuck channels are recoverable. Also, not all errors are stuck channel errors. See Section 1.37.2, “Restrictions and Limitations”, on page 100 for more information.
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 Platform: DM3 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 Platform: DM3 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.
Implementation Guidelines The following guidelines apply when implementing the media channel reset capability using the 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. Do not use it in place of dx_stopch( ).
• This feature only addresses channels that become stuck while performing play and record, tone generation, or FSK operations. It also addresses channels that become stuck during CSP play or record operations. • 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.
For further information about this feature, see the Dialogic® Global Call SS7 Technology Guide. Dialogic® System Release 6.
Release Issues 2. The table below lists issues that can affect the hardware and software supported in Dialogic® System Release 6.1 CompactPCI 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 Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® Issue Type Defect No. PTR No. SU No.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Known Defect No. PTR No. IPY00006148 36279 SU No. Dialogic® Product(s) or Component(s) Hot Swap Kit Description The procedure for uninstalling the Hot Swap Kit (HSK) and Redundant Host (RH) software is given in the Dialogic® System Release 6.1 CompactPCI for Windows® Software Installation Guide.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Resolved Defect No. IPY00044713 PTR No. -- SU No. 174 Dialogic® Product(s) or Component(s) Board Detection Description Dialogic® IPT Boards do not report the correct serial number in OA&M activities such as in Dialogic® Configuration Manager (DCM). Note: When using the Service Update where this fix is introduced, the IPT Board firmware must be updated by the user prior to board initialization.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00032900 -- 106 Call Control In async mode, detach doesn't work. In sync mode, GCEV_ATTACH fails after a detach is issued. Resolved IPY00092350 -- 199 Conferencing Memory allocation errors occur when using the conferencing APIs.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00045524 -- 189 Device Management The dev_connect( ) function fails when used between M3G and DNI devices. Resolved IPY00091941 -- 201 Diagnostics A power management entry is marked as an ERROR in the system event log.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00044730 -- 176 DM3 Call Control When using Dialogic® DM3 Boards and ISDN protocol, the incorrect number of called subaddress digits is received by the application. An 8-digit called subaddress was initially sent by the switch, but the application received a 6-digit called subaddress.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00037373 -- 135 DM3 Conferencing In a conference with two parties, if party A keeps speaking while party B starts speaking, party B hears breaks from party A while party B is speaking.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00032797 -- 135 DM3 Fax The fax sender cannot wait to receive retry of digital identification signal (DIS) message, and gets Phase E status (EFX_COMMERRTX) transmit communication error.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00038998 -- 143 DM3 Host Runtime Library Bipolar violation alarms are properly detected by the board but are not being reported programmatically via GCAMS. Resolved IPY00092923 -- 199 DM3 Network The LineAdmin Utility does not view all information for DNI boards with more than four network interfaces.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00044614 -- 174 DM3 Voice A potential voice stuck channel condition that could occur on Dialogic® DM/V-B Boards during a record (dx_reciottdata( )) operation was caused by a race condition in the record data stream handling when a stop channel (dx_stopch( )) is issued to terminate the operation.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00042860 -- 168 DM3 Voice Receipt of TDX_RECORD events is delayed after calling dx_stopch( ) on Dialogic® DM/V4800BC Boards configured with the ML1B load at full density and under high load.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00037262 -- 128 DM3 Voice Under certain corner conditions, host CPU utilization increases a large percentage (15% witnessed) after issuing a record on multiple voice channels, and remains that way even after the record completes.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. Resolved IPY00080931 Resolved IPY00100303 Resolved PTR No. SU No. Dialogic® Product(s) or Component(s) Description 201 Fax A memory access violation error occurs when using fax resources and running an application in debug mode. -- 201 Firmware The ml2e_cpciresb and ml5e_cpciresb media loads experienced hung channels.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00079691 -- 189 Global Call IP (SIP) IPT responds to a reINVITE but loses RFC2833 indication on 200_OK. Resolved IPY00079668 -- 189 Global Call IP (SIP) IPT G729AB reINVITE reports IP_CAPABILITY as G729A.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00010129 34274 -- Global Call Protocols Global Call does not provide a way to disable DISCONNECT TONE SUPERVISION with pdk_na_an_io.cdp.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) SU No. Dialogic® Product(s) or Component(s) Defect No. PTR No. Resolved IPY00006748 34587 -- Global Call 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.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. Dialogic® Product(s) or Component(s) SU No. Description Resolved IPY00035831 -- 122 Host Library Segmentation fault occurs in libipm_vsc.so when calling gc_close( ) on Global Call (IP based) line device. Resolved IPY00038849 -- 143 Host Runtime Libraries When opening channels asynchronously with gc_open( ), sequentially one after another channels fail to open.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00037004 -- 127 IP Host IP channels sporadically fail to receive Global Call events resulting from gc_AnswerCall( ), gc_DropCall( ), or gc_Extension( ) calls. Resolved IPY00033102 -- 120 IP Host Supervised transfer fails. Party B gets GCEV_XFER_FAIL with “reason 5800”.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00044779 -- 174 IPT Boards gc_OpenEx( ) fails with error message “IPERR_INTERNAL” following a successful single board stop, removal, re-insertion, and single restart of a Dialogic® IPT Board; meanwhile, a second board was actively processing calls throughout the hot swap process on the former.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00041296 -- 156 IPT Boards Outgoing H.323 calls result in GCEV_TASKFAIL at the Alerting stage. After the call's release, no successful call can be made on that channel (iptB1Tx, ipmB1Cx device) until the board is reset.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Resolved Defect No. IPY00078576 PTR No. -- SU No. 186 Dialogic® Product(s) or Component(s) PDK Description When the Brazil R2 Bidirectional protocol (pdk_br_r2_io) is configured for overlap send and the switch wants “silence” instead of “F” to represent end of DNIS, the ANI digits aren't sent after DNIS communication completes. When the first ANI digit was requested, no digits were sent.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00092283 -- 199 PSTN Call Control The gc_SetConfigData( ) function in asynchronous mode does not return the GCEV_SETCONFIGDATA event when setting CCSET_CALLANALYSIS setID on the GCTGT_CCLIB_CHAN target.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00036504 -- 127 PSTN Call Control Calling gc_MakeCall( ) causes a SETUP message to be sent. If the first response from the other side is CONNECTED, the board responds with CONNECT_ACK, but GCEV_CONNECTED is not sent to the application.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Resolved Defect No. IPY00038545 PTR No. -- SU No. 143 Dialogic® Product(s) or Component(s) Runtime Trace Facility (RTF) Description In RTFManager, the RtfMatrix.xml file was used to map the modules in the RTFConfig file to a family and technology group. But if any changes were made to the RTFConfig file outside of RTFManager, the configuration section would fail.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00041118 -- 154 SIP Call Control The application is unable to make a SIP call using the gc_MakeCall( ) function on the same channels previously used to make an H.323 call.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00080020 -- 190 SNMP OID data type returned by the DLGHWINF, DLGSRPRF, DLGR4DEV, and DLGDS1 agents does not always match the type definitions in their respective MIB files.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Defect No. PTR No. SU No. Dialogic® Product(s) or Component(s) Description Resolved IPY00039334 -- 154 Standard Runtime Library (SRL) An application crash occurred; the stack trace shows SRL library at the top of the stack.
Issues Sorted By Type, Dialogic® System Release 6.1 CompactPCI for Windows® (Continued) Issue Type Resolved Defect No. IPY00037796 PTR No. -- SU No. 135 Dialogic® Product(s) or Component(s) Voice API Description TDX_RESETERR and TFX_FAXRECV events have the same value defined in their respective header files (dxxxlib.h and faxlib.h).
Documentation Updates 3. This chapter contains information on updates and corrections to the documents included in Dialogic® System Release 6.1 CompactPCI for Windows®. Documentation updates are divided into the following categories: • System Release Documentation Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 • Installation and Configuration Documentation Updates . . . . . . . . . . . . . . . . . . 133 • OA&M Documentation Updates . . . . . . . . . . . . . . . . . . . . . . . . . . .
Update to Section 4.1, Installation (IPY00081147) Add the following note after the first paragraph: Note: Due to changes in the Dialogic® Software install process, an update install should not be used when updating to a more recent build from a Dialogic® System Release 6.1 CompactPCI for Windows build prior to Service Update 176. Update install does work when upgrading from Service Update 176 to any more recent build.
Dialogic® System Release Software. If you observe this failure, the following steps can be used to resolve the problem: 1. Change into the Windows System32 directory. 2. Run “regsvr32 atl.dll”. 3. Change into the Dialogic\bin directory. 4. Run “DetectorsProj -service”. This can be done once the Dialogic® System Release Software installation has completed with the above error, before rebooting.
Update to Section 4.3, Starting the Configuration Manager (DCM) In the instructions regarding the Computer Name dialog box for remote DCM, the following note should be added: Note: In order to use remote DCM, the local computer (management node) and remote computer (managed node) must both be running the same Dialogic® software release (for example, System Release 6.1 CompactPCI Windows) and same build number.
CSUMS_SmartScalingPartiesMinNum Number: 0x3b04 Description: Specifies the number of talkers in a conference before scaling mode is enabled. Values: 0 [default] to 0xff (255). Guidelines: Audio conferencing provides a mechanism for audio summation of two or more parties in a conference. There are three possible summing modes, which are controlled by CSUMS parameters 0x3b03 and 0x3b04 in the configuration file. By default, both active talker and scaling are enabled.
• 3: DMS100 and DMS250 • 4: NTT • 7: NET5 • 8: DASS2 • 9: DPNSS • 10: QSIGE1 • 11: QSIGT1 • 12: NI2 3.2.3 Dialogic® IPT Series on Windows® Configuration Guide Update to Section 3.
Update to Chapter 10, Brazil R2 Bidirectional Protocol Parameter Configuration The “Values” section for the CDP_FLAG_APPEND_F parameter should be updated to refer to the CDP_SKIP_A3_AND_A4_PULSE parameter as follows: Values: • 0 [default]: No tone will be sent to the remote end. In this case, A3 or A4 pulse is expected to be received from the remote end. In a case of overlapped sending (see description of CDP_OVERLAP_SENDING_ENABLED parameter), the remote end may also send A1 to request more information.
3. Check the value of the IPTBoardSoftwareVersion parameter, which has a hex value that represents the firmware version. For example, the parameter value “10a0918” translates to firmware version NDB_1.10.9_B24; the last 2 digits represent the build number (i.e., hex 18 is 24 decimal). To determine if a newer firmware version is available in the Dialogic® System Release 6.1 CompactPCI for Windows® Service Update baseline: 1. Open up a DOS CMD prompt. 2. Go to the ..\dialogic\data directory. 3.
Update to Chapter 12, DebugAngel Reference Because of a new feature in the Service Update, the DebugAngel tool has been enhanced to provide more capabilities for managing multiple log files. For more information about this feature, see Section 1.11, “File Management Enhancements for DebugAngel Tool”, on page 40 of this Release Update.
The “log_format” value controls the type of log files that are written. Valid values for this parameter are “text” and “binary”. Once a change has been made to the XML file, it must be reloaded using the rtftool reload command. Converting Binary Format RTF Log Files to Text Format In order for binary log files to be examined, they must be converted into text format. This can be done by using the rtftool export command.
3.3.7 Dialogic® Native Configuration Manager API Programming Guide There are currently no updates to this document. 3.3.8 Dialogic® Native Configuration Manager API Library Reference There are currently no updates to this document. 3.
3.4.2 Dialogic® Audio Conferencing API Library Reference There are currently no updates to this document. 3.4.3 Dialogic® Continuous Speech Processing API Programming Guide There are currently no updates to this document. 3.4.
GC_L2_BLK recvfrmptr; /* Buffer to store received frame */ . . . case GCEV_L2FRAME: /* retrieve signaling information from queue */ if ( gc_GetFrame(ldev, &recvfrmptr) != GC_SUCCESS) to this: L2_BLK l2ie; GC_L2_BLK recvfrmptr; /* Buffer to store received frame */ . . . recvfrmptr.
/* Following use of gc_util_next_parm retrieves the first parameter in a * GC_PARM_BLK, which in this case is PARM_REQTYPE */ my_parmp = gc_util_next_parm( my_blkp, NULL ); /* Retrieve the next parameter after getting the first one */ my_parmp = gc_util_next_parm( my_blkp, my_parmp ); /* This function finds and returns specified parameter, NULL if not found */ my_parmp = gc_util_find_parm( my_blkp, GC_SET_SERVREQ, PARM_ACK ); /* After GC_PARM_BLK is no longer needed, delete the block */ gc_util_delete_parm_
Update to Chapter 3. IP Call Scenarios Add new section, T.38 The following figure App GC/cclib IPML Remote Device Capable of Signaling, Audio and T.
App GC/cclib IPML Remote Device Capable of Signaling, Audio and T.38 FAX Fx_open(dxxxB23C1) gc_SetConfigData(IP_MANUAL_MODE) gc_OpenEx(:N_iptB1T1:M_ipmB1C1) SETUPw/TCS/INVITE to send Origination IP address and RTP Port number gc_MakeCall() Call Connected GCEV_CONNECTED RTP DATA REINVITE/RequestMode to switch to T.38 Fax.
App GC/cclib IPML Remote Device Capable of Signaling and T.38 FAX fx_open(dxxxB23C1) gc_SetConfigData(IP_MANUAL_MODE) gc_OpenEx(:N_iptB1T1:M_ipmB1C1) gc_SetUserInfo(T38 capability only) gc_SetUserInfo(IPSET_FOIP,IPPARM_T38_CONNECT) gc_MakeCall() dev_Connect(ipmB1C1, dxxxB23C1) Ipm_GetLocalMedia(T.38) SETUP with TCS/INVITE to send Origination IP address and UDP Port number Call Connected Ipm_StartMedia(T.38) GCEV_CONNECTED Fx_sndfax() T.38 Data via RTP Dialogic® System Release 6.
App GC/cclib IPML Remote Device Capable of Signaling and T.38 FAX fx_open(dxxxB23C1) gc_SetConfigData(IP_MANUAL_MODE) gc_OpenEx(:N_iptB1T1:M_ipmB1C1) Receive SETUPw/TCS/INVITE with FAX IP address and RTP Port number GCEV_OFFERED (IPSET_FOIP,IPPARM_T38_OFFERED) gc_SetUserInfo(IPSET_FOIP, IPPARM_T38_CONNECT) gc_AnswerCall() dev_Connect(ipmB1C1, dxxxB23C1) Ipm_GetLocalMedia(T.38) Ipm_StartMedia(T.38) Call Connected GCEV_ANSWERED Fx_recvfax() T.38 Data via RTP Dialogic® System Release 6.
App GC/cclib IPML Remote Device Capable of Signaling, Audio and T.38 FAX fx_open(dxxxB23C1) gc_SetConfigData(IP_MANUAL_MODE) gc_OpenEx(:N_iptB1T1:M_ipmB1C1) gc_MakeCall() GCEV_CONNECTED Audio Data gc_SetUserInfo(IPSET_FOIP,IPPARM_T38_CONNECT) gc_Extension(IPSET_SWITCH_CODEC,IPPARM_T38_INITIATE), GCEV_EXTENSIONCMPLT GCEV_EXTENSION(IPSET_SWITCH_CODEC,IPPARM_READY) T.
App GC/cclib IPML Remote Device Capable of Signaling, Audio and T.38 FAX Fx_open(dxxxB23C1) gc_SetConfigData(IP_MANUAL_MODE) gc_OpenEx(:N_iptB1T1:M_ipmB1C1) gc_MakeCall() GCEV_CONNECTED Audio Data GCEV_EXTENSION(IPSET_SWITCH_CODEC,IPPARM_T38_REQUESTED) gc_SetUserInfo(IPSET_FOIP,IPPARM_T38_CONNECT) GCEV_EXTENSION(IPSET_SWITCH_CODEC,IPPARM_READY) Fx_Recvfax() T.38 Data via RTP REINVITE/RequestMode to switch to audio.
App GC/cclib IPML Remote Device Capable of Signaling, Audio and T.38 FAX T.38 Data via RTP Fx_stopch() BYE/Release Complete GCEV_DISCONNECTED gc_SetUserInfo(IPSET_FOIP,IPPARM_T38_DISCONNECT) gc_DropCall() Ipm_Stop() dev_Disconnect(ipmB1C1) GCEV_DROPCALL gc_ReleaseCall() GCEV_RELEASECALL Update to Chapter 4. IP Specific Operations Add a new section, T.38 Fax Server, along with the following information: Dialogic® System Release 6.
gc_Open( ) Open ipmBxCy device Voice Fax Voice or Fax gc_SetUserInfo( ) with IPPARM_T38_CONNECT Association of fax device and voice device gc_MakeCall( ) or gc_AnswerCall( ) Make/Receive Voice Call gc_ReleaseCallEx( ) Release current call gc_MakeCall( ) or gc_AnswerCall( ) Make/Receive fax Call Notified by Global Call voice call is ready Switch to fax or end call Notified by Global Call fax call is ready gc_DropCall( ) Drop current call end gc_SetUserInfo( ) with IPPARM_T38_DISCONNECT Disassociat
Allow: INVITE, CANCEL, ACK, BYE, INFO, REFER, NOTIFY Note that in either case, OPTIONS is not included in the list. • Under Section 4.14.
Update to Section 8.2, Parameter Set Reference New parameter IDs have been added to IPSET_CALLINFO so that you can send and receive CPN fields via Global Call over an IP network. See Section 1.30, “Dialogic® Global Call API Access to New H.323/Q.931 Message IEs”, on page 83 of this Release Update for more details. Update to Section 8.2.4, IPSET_CONFIG New parameter IDs have been added to IPSET_CONFIG so that you can disable/enable the sending of the automatic SIP re-INVITE message upon media switch (e.g.
3.4.11 Dialogic® Global Call ISDN Technology Guide There are currently no updates to this document. 3.4.12 Dialogic® Global Call SS7 Technology Guide Add that the Global Call SS7 binaries are now linked with the dynamic link library in the Dialogic® SS7 DSI Development Package. (IPY00081381) This change requires that Global Call SS7 customers use the Dialogic® SS7 DSI Development Package version 5.0 or later.
• QOSTYPE_RTPTIMEOUT - QoS alarm for Real Time Protocol (RTP) inactivity These alarms and their associated events should be included in the following function and data structure reference pages: ipm_DisableEvents( ), ipm_EnableEvents( ), IPM_QOS_ALARM_DATA, IPM_QOS_SESSION_INFO, IPM_QOS_THRESHOLD_DATA. For further information about these alarms, see Section 1.19, “New QoS Alarms for RTCP and RTP Inactivity”, on page 61 of this Release Update.
IPT Boards. For further information, see Section 1.8, “Media LAN Disconnection Alarm Notification for Dialogic® DM/IP Boards”, on page 33 of this Release Update. A new eQoSType value has been added to the IPM_QOS_ALARM_DATA structure. See Section 1.25, “Modified Alarm Events for Media LAN Disconnect”, on page 74 of this Release Update for more details. 3.4.15 Dialogic® Modular Station Interface API Programming Guide There are currently no updates to this document. 3.4.
Speed control on Dialogic® DM3 Boards using 6 kHz coders The following coders are now supported and should be added to Section 9.1, Speed and Volume Control Overview: • OKI ADPCM 24 kbps (6 kHz 4-bit) • G.711 PCM A-law 48 kbps (6 kHz 8-bit) • G.711 PCM mu-law 48 kbps (6 kHz 8-bit) 3.4.20 Dialogic® Voice API Library Reference Functions not supported The r2_creatfsig( ) and r2_playbsig( ) functions, which were previously provided for backward compatibility only, are no longer supported.
Update to dx_setevtmsk( ) (IPY00038053) The following information should be added to the description of the mask parameter: User defined tones that are associated an optional digit (dx_addtone( )) have digit reporting enabled by default in Dialogic® System Release 6.1 CompactPCI for Windows®. The user defined tones digit reporting can be turned off by using dx_setevtmsk( ) with DM_DIGOFF mask. To reactivate digit reporting, use dx_setevtmsk( ) with DM_DIGITS mask. 3.
Section 4.3.2, Using the Media Server, contains a list of menu options in the section headed “Main Menu [Main_Menu]” which should be corrected as follows: The menu includes a fifth option which is not included in the list. However, the missing option (2 - Fax) is not supported when using a Dialogic® DM/IP or Dialogic® IPT Board.
