4 Configuration and Operation

4.3Protocol Configuration

The Development Package contains a protocol configuration utility, s7_mgt which performs initialization of all the software modules running on the signaling board. It reads the protocol configuration data from a text file called config.txt and provides a quick and flexible method of configuring the protocol modules without the need to write software for that purpose.

Alternatively, the protocol stack may be configured by sending individual configuration messages documented in the per-module Programmer’s Manuals to each protocol module. This approach is of particular use if the application needs to reset the board and run a new configuration without stopping the application program. It is described in section 4.3.2 Protocol Configuration Using Individual Messages.

4.3.1Protocol Configuration using the s7_mgt utility

The default configuration file used by s7_mgt is config.txt. The -k option allows the user to specify an alternative filename if required. For example:

s7_mgt -kmyconfig.txt

The format of the configuration commands is described in Appendix A.

s7_mgt can optionally be configured to send a message to a nominated module on completion of the configuration sequence. This option is activated using the –i option to specify the receiving module_id. For example:

s7_mgt –i0xef

To assist problem diagnosis, run s7_mgt using the –d option, and additional diagnostic output will be generated. For example:

s7_mgt –i0xef -d

See section 4.4 Board Information Diagnostics, for diagnostic output format.

4.3.2Protocol Configuration Using Individual Messages

As an alternative to using the s7_mgt configuration utility it is possible to carry out the protocol configuration by building and sending messages directly to the board. This approach does mean that it is necessary to write some application code to handle the configuration but has the advantage that the application can, if required, re-configure the board without re starting the application.

All communication with the board is in the form of sending and receiving messages. The configuration sequence is described in the following section. The application must allocate a message structure using the library function getm() and send it to the board using the library function GCT_send(). The application must periodically call the library function GCT_receive() or GCT_grab() in order to receive messages from the board. GCT_receive() will block until a message is available whilst GCT_grab() will return immediately. Once the application has finished processing the received message, it must release the message structure back to the system by calling the library function relm(). The library functions are all described in the Software Environment Programmer's Manual.

24

Page 23 Page 25
Page 24
Image 24
Dialogic DSI SPCI Network Interface Boards manual Protocol Configuration using the s7mgt utility
Page 23 Page 25

DSI SPCI Network Interface Boards specifications

Dialogic DSI SPCI Network Interface Boards are highly advanced and versatile communication solutions tailored for the demands of modern telephony and multimedia applications. These boards are designed to efficiently process voice, data, and signaling, making them an essential component for businesses looking to enhance their communication capabilities.

One of the standout features of the Dialogic DSI SPCI boards is their ability to handle multiple telephony protocols. This flexibility allows users to connect to various network types, whether PSTN, VoIP, or legacy systems, ensuring seamless interoperability. The boards support industry-standard protocols such as ISDN, SS7, and SIP, enabling integrated communication across diverse platforms.

The technology behind the Dialogic DSI SPCI boards incorporates state-of-the-art digital signal processing (DSP). This powerful DSP architecture provides efficient encoding and decoding of voice and video signals, leading to enhanced call quality and reduced latency. Moreover, the DSP technology supports advanced codecs, ensuring that voice communication is clear and intelligible, even over bandwidth-limited connections.

Another significant characteristic of these boards is their scalability. Organizations can start with a single board and expand their telecommunication capabilities as their needs grow. This scalability makes them suitable for a wide range of applications, from small businesses to large enterprises, allowing for easy integration into existing infrastructures.

In addition to their powerful processing capabilities, Dialogic DSI SPCI boards also prioritize reliability and robustness. They are designed with a focus on fault tolerance, ensuring that telephony services remain uninterrupted even in the event of hardware failure. This resilience is critical for mission-critical applications where downtime can lead to significant revenue loss.

Furthermore, the boards feature extensive application development support. Developers can leverage the Dialogic API and various development kits to create custom telephony applications that meet specific business requirements. This programmability opens the door to innovative solutions, such as interactive voice response (IVR) systems, automated call distribution (ACD), and customer relationship management (CRM) integration.

In summary, Dialogic DSI SPCI Network Interface Boards are a cornerstone for organizations looking to innovate their telecommunication systems. With their support for multiple protocols, advanced DSP technology, scalability, reliability, and development support, these boards empower businesses to optimize their communication strategies and adapt to the evolving landscape of digital interaction.
Top Page Image Contents