Yan Ng As far as I know, a board device is a line device. Let me know if I am wrong. You are wrong
↧
Forum Post: RE: GCEV_EXTENSION issue
↧
Forum Post: RE: VMWare Cloud on AWS support for HMP 3.0
Hi, HMP3.0 is not tested and supported in Amazon Web Server (AWS) environment. I hope this answers your question. Thanks, Sunil.
↧
↧
Forum Post: Brooktrout TR1034+E8-8L Problem
I am attempting to install a Brooktrout TR1034+E8-8L analog fax board for FaxMaker on Windows 2008 Server Standard R2. When I try to configure it, or even when I try to run the fdtool to diagnose it, I get the following error. I would greatly appreciate any assistance in troubleshooting and resolving this issue. The SDK version is 6.7.1 11/11/16 13:02:59: BfvFeatureSetQuery Failed: Misc error: Hardware or firmware does not have a required capability. 11/11/16 13:02:59: BfvFeatureSetQuery Failed: Misc error: Hardware or firmware does not have a required capability. 11/11/16 13:03:00: BfvFeatureSetQuery Failed: Misc error: Hardware or firmware does not have a required capability. 11/11/16 13:03:00: BfvFeatureSetQuery Failed: Misc error: Hardware or firmware does not have a required capability. 11/11/16 13:03:00: BfvFeatureSetQuery Failed: Misc error: Hardware or firmware does not have a required capability. 11/11/16 13:03:00: An error occurred while querying the hardware feature for Module 0x2. 11/11/16 13:03:00: Configtool cannot proceed with the hardware configuration because 11/11/16 13:03:00: the licensing restrictions have been exceeded. To proceed, you must 11/11/16 13:03:00: remove/uninstall any modules exceeding the maximum allowed and 11/11/16 13:03:00: restart configtool. The tool will now exit.
↧
Forum Post: RE: Brooktrout TR1034+E8-8L Problem
UPDATE: btver returns the following. Is it possible the board's firmware is corrupt? C:\Program Files (x86)\GFI\FaxMaker\brooktrout\TR1034\Boston\Bin btver -m 2 - Boston Bfv API v6.7.01 (Build 3), compiled with v6.7.1 (Build 3) - Boston Driver v6.7.01 (Build 1) - Boston SDK v6.7.01 (Build 3), compiled with v6.7.01 (Build 3) ------- Firmware Info for module 0x02 -------- FirmType Version Date Comment ============================================================================== Boot Rom: Not available Ctrl Proc: Not available DSP[ 0]: Not available ******************************************************************************
↧
Forum Post: RE: Brooktrout TR1034+E8-8L Problem
This issue is resolved. It turns out that there are two PCIe slots on the motherboard that look identical. However, the one I was trying to us is actually a PCIe16X slot. I moved the board to the slot which is PCIe4X and the board is detected and working properly.
↧
↧
Forum Post: PowerMedia XMS 3.2 Now Available
Download available at: http://www.dialogic.com/en/products/downloads/xms/xms.aspx Full release notes are available at: http://www.dialogic.com/webhelp/XMS/3.2/XMS_ReleaseNotes.pdf The following are new features that have been added : Amazon Web Services (AWS) Qualification -- supports XMS running Amazon Web Services (AWS) for cloud deployments. This release delivers cloud optimization and performance improvements to further validate the XMS on AWS compute images. Oracle Linux 7.2 with UEK 4 -- adds support for the Oracle Linux 7.2 Operating System with Unbreakable Enterprise Kernel (UEK) Release 4. Multiple NIC Media Routing --provides user-defined media routing rules to support multiple NIC interfaces for RTP media traffic routing. This feature provides a method for XMS users to indicate a particular network interface that should be used when establishing SIP and WebRTC calls or media connections. A useful application of this feature is to separate media traffic between two interfaces, such as with a media gateway application supporting local and public network interfaces. Voice Quality Enhancements in Echo Cancellation -- provides additional voice quality enhancements in echo cancellation (EC) by adding an adaptive "bulk delay" echo cancellation. For conferencing providers, voice quality is very important, especially echo cancellation capabilities. NAT and RTP Profile Indications Support -- PowerMedia XMS Release 3.2 supports various combinations of SIP header indications to specify NAT and RTP profiles on SIP calls. This feature supports ICE (Lite), SDES, DTLS, AVPF/SAVPF, and combinations in a SIP INVITE when using Dialogic proprietary Supported header tags. MRB Adaptor Service Startup Control -- provides the ability to enable or disable the MRB Adaptor from the WebGUI or RESTful Management API. Customers can now choose to enable or disable the MRB Adaptor service based on their deployment scenario. JSR 309 Connector Integration with MRB -- introduces integration support for JSR 309 Connector applications to utilize the PowerMedia MRB for media load balancing, media server redundancy, and failover of conferences and bridged calls. MRB for 3PCC REST -- has been updated to provide media load balancing, failover, and high availability features for 3PCC RESTful applications. 3PCC RESTful applications are those that support call signaling for ebRTC or SIP at the application server and use the XMS only for media establishment and media operations. MRB RTP Proxy - - supports a new RTP proxy mode. The MRB RTP proxy provides a single landing point for RTP media sessions that are monitored by the MRB. Enhanced Video Conference Layout Sizing -- This feature provides video conferencing applications greater control over the video sizing of the regions in a conference layout and how the video content of each region gets rendered. Audio/Video Join Enhancement -- updated with a new enhancement to media join functionality between callers and conferences. XMS now provides the ability to separate the audio and video streams so media can be routed separately on the join command. Prior to this release, all connections between multimedia callers or conferences had to include both audio and video streams. WebM Container Support -- enables the ability to record to and playback from the WebM file container using Opus audio and VP8 video (up to 720p) codecs. The WebM container is an open media file format designed for the web and the file structure is based on the Matroska media container. Native Record Support for WebM -- enables the ability to record natively to the WebM container without transcoding. This capability allows applications to record multimedia streams (VP8/Opus) as they are transmitted by the endpoint and reduces the amount of CPU required to record individual caller multimedia streams especially at higher resolutions. MSML pattern Support of Regular Expressions -- adds support for regular expressions in the MSML pattern method. In order to support much more complex digit patterns than the current "moml+digits", this release adds support in MSML for a new pattern format named "perlregex" that permits perl regex compliant regular expressions to be specified. MSML Global Scope Shadow Variables -- this feature implements MSML shadow variables at the global scope in addition to the shadow variables at the local scope. The global scope shadow variables will represent the last local (in scope) shadow variables returned. System Logging -- improves the XMS logging subsystem. The XMS logging subsystem has been updated with the capability to start and stop logging on the fly with ability to change the log level, log file size, and max number of log files collected. Globally Unique Session ID -- adds support for RFC 7329, which defines a globally unique session identifier SIP header for SIP calls. The globally unique session ID feature is supported at both the MRB and XMS to support advanced call tracing for the life of the call through both the MRB and XMS MRF components. SIP 180 Ringing Configuration -- adds support for a WebGUI configurable option to suppress SIP 180 Ringing. This provides a user the ability to enable or disable the sending of a SIP 180 Ringing response from XMS based on the system settings. SIP OPTIONS Ping Enhancements -- includes SIP OPTIONS ping processing enhancements. The SIP OPTIONS ping responses are coordinated between the XMS and MRB to provide consistent responses that take into consideration the system status and resource availability at each network element. SNMP Thresholds -- added improvements to the SNMP alarms. The XMS SNMP subsystem has been updated to allow configuration of separate user-defined thresholds for Warning, Minor, Major, and Critical alarm levels. The new configuration allows users to specify the percent threshold for each of the SNMP alarm levels based on their deployment needs. Fax Session Counter -- has been updated to include fax session resource counter as part of the XMS meters. The fax session resource counter is also available for SNMP alarm reporting through configurable SNMP trap thresholds. SIP Session Counters -- A new set of SIP meters has been added to the WebGUI Monitor Graphs page. These meters track the count of various SIP messages sent and received. They allow monitoring of the number of SIP INVITEs sent and received and track the 200 OKs. HTTP Session Counters - - A new set of HTTP meters has been added to the WebGUI Monitor Graphs page. These meters track the count of various HTTP messages sent and received, such as count of HTTP GET, PUT, POST requests and Error responses. HTTP Client Cache Size - - provides configuration for HTTP client cache size. This new parameter allows users to define the size of the HTTP cache utilized before cached http data is deleted. CDR Improvements -- includes improvements to the XMS Call Data Record (CDR) subsystem. In this release, the WebGUI has been updated with additional configuration options for querying, displaying, and filtering CDR records. The CDR page on the WebGUI now allows users to create and apply user-defined queries of the CDR records to a number of additional filter options. Export Audit Log as .csv -- supports the capability to export the XMS audit log to a .csv file. The audit log on XMS tracks and stores configuration and management access through the WebGUI as audit log entries. NTP Improvement -- now supports the chronyd clock synchronization, which is provided by the Linux 7.x OS. The chronyd provides a number of system timing and synchronization advantages over ntpd and can usually synchronize the system clock faster with better accuracy. Secure MSRP Messaging -- now supports secure MSRP messaging transfers with support for TLS encryption on MSRP socket connections. Users have the ability to select TLS encryption as the preferred transport and preference to accept or reject unencrypted MSRP connections. Language Pack Integration - supports the addition of new variable content language packs from Dialogic through rpm installation. Controlled Introduction Features In addition to general availability of new features and functionality, PowerMedia XMS Release 3.2 also introduces new functionality in a controlled introduction. The controlled introduction features are those that are under development or have a limited scope before being made generally available. These features are available for customers that are looking to perform Proof of Concept (PoC) with the listed functionality. Customers interested in these features should contact their Dialogic Sales Representative or Technical Support Service Engineer for further information on usage. Multitrack Recording -- supports audio recording to dual-track (stereo) .wav files. This multitrack record feature enables applications to record two separate audio sources into different tracks. Individual Party Multitrack Recording -- The individual multitrack transaction recording use case enables applications to record the audio of the caller speaking and the audio that the caller hears in the same file as two different tracks. Two-Party Multitrack Recording -- The two-party recording use case enables applications to record two sources, such as two call parties, as two separate tracks in a single .wav file. The resulting file has each audio source in a separate track, which can be played back together or separated by source. Video Encoder Sharing Support -- PowerMedia XMS Release 3.2 supports video encoder sharing. Video encoder sharing includes Dialogic patented video technology that provides enhanced performance for video conferencing and video mixing applications. Video encoder sharing works by reducing the CPU cycles required to perform the most CPU intensive video function: video encoding. In video conferencing applications, such as for WebRTC video conferencing between browsers, the video conference output can be encoded once and shared among multiple users. Selective Forwarding Unit (SFU) - - supports a Selective Forwarding Unit (SFU) video conferencing approach for certain customer Proof of Concept (POC) scenarios. With the SFU video conference, a video stream from each participant is routed (without transcoding) to the other participants in multimedia conference. VP9 Video Codec - - supports VP9 video codec for WebRTC endpoints. XMS enables full decoding and encoding of VP9-based video sessions between Google Chrome and other VP9 endpoints, as well as transcoding to non-VP9 endpoints. CDR Remote Database -- the CDR subsystem has been updated with the ability to utilize a remote database for CDR storage. This allows users to configure separate CDR storage from the default XMS local storage normally used for CDR storage.
↧
Forum Post: RE: VMWare Cloud on AWS support for HMP 3.0
I'm aware of the documentation regarding current Dialogic support and VM's (i.e. only VMWare ESXi is supported). The question was more about whether Dialogic will in future support the new VMWare Cloud on AWS specifically for HMP 3.0. I have tried installing HMP 3.0 on a AWS XEN based VM and indeed it doesnt even install (it looks like vital virtual hardware doesn't exist in XEN).
↧
Forum Post: RE: HMP Contact: header question
As far as I know, HMP behavior is: - for inbound calls, it copies the To: header from the INVITE in the Contact: header sent in the 200 OK - for outbound calls, it copies the From: heder from the INVITE in the Contact: header used throughout the call If you want to set another thing into Contact: header, you need to build it yourself, and probably set it as persistent header for the duration of the call. Please check www.dialogic.com/.../globalcall_for_ip_hmp_v12.pdf chapter 4.9.8 Configuring Persistent SIP Header Chris
↧
Forum Post: RE: GCEV_EXTENSION issue
Ok, there is a difference between line device and board device in this case. The board device can be part of the line device but its nto the same. A line device can look like this: ":P_nnnn:N_iptBxTy:M_ipmBxCy:V_dxxxBwCz" Where as the board device is just "iptB1" of the IPT virtual board, which is what you need to pass as the device handle to gc_setconfigdata in this case. Jeff
↧
↧
Forum Post: RE: HMP Contact: header question
One correction the Contact header is populated from the "SIP Request URI" field from the incoming INVITE in this case, not the from field. Jeff
↧
Hi in Developer Group
Hi in Developer Group
↧
i have a problem with dialogic card D/600jct 2e1,the device manager find this card but DCM can not find this card and can nat start it in Developer Group
i have a problem with dialogic card D/600jct 2e1,the device manager find this card but DCM can not find this card and can nat start it in Developer Group
↧
can you help me to salve this problem in Developer Group
can you help me to salve this problem in Developer Group
↧
↧
Forum Post: RE: VMWare Cloud on AWS support for HMP 3.0
Hi, Sorry for confusion. As far as I can see this is not in road map. FYI... we have another product XMS and which is supported on AWS. Please see the link for more details. Thanks, Sunil.
↧
Forum Post: ttyds CID assign
I am using /dev/ttydsXX interface to communicate using 30 modems on DIVA E1 single port card. I need to serve only outgoing calls(no incoming calls at all) and control outgoing numbers (CIDs) in such way: /dev/ttyds01 - one defined number by Telco Network Provider as CID , /dev/ttyds02 - next one defined number by Telco Network Provider as CID, to /dev/ttydsXX - next defined XXXXXXXXX number as CID How to achieve that functionality, becouse I tried: AT+iOTelco_Network_Provider_number OK AT #CID=3 OK AT+iQ=o1+iK=o1 on dev/ttyds01 OK and AT+iQ=o1+iK=o2 on dev/ttyds02 OK but no effects. All efforts gives me single the same outgoing number on all ports, besides Telco Network Provider assigned over 30 numbers for me.
↧
Forum Post: Application Freeze
Hi, I'm currently working with the RHEL version of HMP 4.1 and I notice that periodically my application stops responding to events. I've checked out the rtf log that was generated for the last instance of the "application freeze" and the following was reported in the rtf log file:- 11/16/2016 11:43:29.854 27600 4133677696 spwrvoice ERR1 dxmain dxxxB3C3 :::: dx_open() = -1, open(/dev/dlgn) = -1 11/16/2016 11:43:29.854 27600 4133677696 spwrvoice ERR1 dxmain dxxxB3C4 :::: dx_open() = -1, open(/dev/dlgn) = -1 11/16/2016 12:36:10.484 27600 3913284416 srl ERR1 srlib (unreg'd) ==== _sr_putevt_low() FAILED re: ddd=-1, s_ddd_max==1024, s_ddd_vector=0x9926998 The application I have is relatively simple - it processes both inbound and outbound calls and most of the time works as expected but there are the odd times where the application just stalls. I'm unclear on how to read the log file - can anyone help me as to what the above errors mean. The srlib error at 12:36 corresponds to the approximate time that the application then stopped responding. Many Thanks Mike
↧
Forum Post: RE: Application Freeze
Hi Mike, Those ERR1 logging along will not give much useful information. Do you see any errors in /var/log/messages file? Which SU build you are using? Do you see any errors from your applicaiton logs? How frequently you see this issue? Thanks, Sunil.
↧
↧
Forum Post: RE: Application Freeze
Hi Sunil, Thanks for the quick reponse and suggestions. I've checked out the /var/log/messages file but there are no errors in there (the last entry in there was not an error and was at 12:36:05) which was several seconds before the application froze). The HMP build we're using is 4.1.213 (we installed lnxHMP_4.1_213.tgz from the dialogic website onto our RHEL system) The only obvious error reported in the application logs is:- 15-11-2016|19:18:13.783768||0009|DX|dx_open (dxxxB3C2) successfull (result = 0061) 15-11-2016|19:18:13.783784||0009|DX|sr_setparm result = 0x9 15-11-2016|19:18:13.784015||0010|DX|dx_open(dxxxB3C3) failed 15-11-2016|19:18:13.784114||0011|DX|dx_open(dxxxB3C4) failed 15-11-2016|19:18:13.788616||0012|DX|dx_open (dxxxB4C1) successfull (result = 0062). The above is strange as I'm not sure why dxxB3C3 and dxxB3C4 are failing to open. Do you think this could cause the application to freeze after a period of running? I've checked if the application actually used either of these dx devices before it froze but it did not. Thanks, Mike
↧
Forum Post: RE: HMP Contact: header question
Thanks Jeff
↧
Forum Post: RE: Application Freeze
Hi Sunil, I've had a look at the "_sr_putevt_low() FAILED re: ddd=-1, s_ddd_max==1024, s_ddd_vector=0x9926998" error that was reported yesterday and this was at the point where my application attempted to send a custom event - eg. sr_putevt(dxH, APPEVN_AFTER_INBOUND_CLI_CHK, NULL, 0, 0); I have #define APPEVN_AFTER_INBOUND_CLI_CHK1000020 and was just wondering if the value defined for APPEVN_AFTER_INBOUND_CLI_CHK is too large and therefore causing the error to be reported? Not sure if it's relevant but the _sr_putevt_low() FAILED error occurred on the 11th channel of the application. Do you have any feedback on the above? Many Thanks, Michael
↧