Dialogic DSI SPCI Network Interface Boards - Manual

Dialogic DSI SPCI Network Interface Boards

Dialogic DSI SPCI Network Interface Boards – Manual, read for free online in PDF format. We hope this helps you resolve any issues you may have. If you have further questions, please contact us through the contact form.

1 Page 1
2 Page 2
3 Page 3
4 Page 4
5 Page 5
6 Page 6
7 Page 7
8 Page 8
9 Page 9
10 Page 10
11 Page 11
12 Page 12
13 Page 13
14 Page 14
15 Page 15
16 Page 16
17 Page 17
18 Page 18
19 Page 19
20 Page 20
21 Page 21
22 Page 22
23 Page 23
24 Page 24
25 Page 25
26 Page 26
27 Page 27
28 Page 28
29 Page 29
30 Page 30
31 Page 31
32 Page 32
33 Page 33
34 Page 34
35 Page 35
36 Page 36
37 Page 37
38 Page 38
39 Page 39
40 Page 40
41 Page 41
42 Page 42
43 Page 43
44 Page 44
45 Page 45
46 Page 46
47 Page 47
48 Page 48
49 Page 49
50 Page 50
51 Page 51
52 Page 52
53 Page 53
54 Page 54
55 Page 55
56 Page 56
57 Page 57
58 Page 58
59 Page 59
60 Page 60
61 Page 61
62 Page 62
63 Page 63
64 Page 64
65 Page 65
66 Page 66
67 Page 67
68 Page 68
69 Page 69
70 Page 70
71 Page 71
72 Page 72
73 Page 73
74 Page 74
75 Page 75
76 Page 76
77 Page 77
78 Page 78
79 Page 79
80 Page 80
81 Page 81
82 Page 82
83 Page 83
84 Page 84
85 Page 85
86 Page 86
87 Page 87
88 Page 88
89 Page 89
90 Page 90
91 Page 91
92 Page 92
93 Page 93
94 Page 94
95 Page 95
96 Page 96
97 Page 97
98 Page 98
99 Page 99
100 Page 100
101 Page 101
102 Page 102
103 Page 103
104 Page 104
105 Page 105
106 Page 106
107 Page 107
108 Page 108
109 Page 109
110 Page 110
111 Page 111
Page: / 111

Table of Contents:

  • Page 2 – Copyright and Legal Notice
  • Page 3 – Contents
  • Page 5 – Tables
  • Page 6 – Revision History; Current software and documentation supporting Dialogic
  • Page 7 – Introduction; Related Documentation
  • Page 8 – Specification; Product Identification; Table 1: SPCI Network Interface Board Capability; SPCI2S; License Buttons; Run Modes
  • Page 9 – Run Modes supported; Table 3: Protocol Dimensioning; Capacity
  • Page 10 – Installation
  • Page 11 – Hardware configuration; Board Option Switch / Link Settings; Geographic Addressing; Software Installation for Windows; The Development Package for Windows; Installing Development Package for Windows; driver is correctly loaded.
  • Page 12 – Table 4: Files Installed on a System Running Windows; Name; installing the package.; Starting the Windows; Select the Control Panel (Start
  • Page 13 – Net start Septel; Clearing Windows
  • Page 14 – Removing Development Package for Windows; Software Installation for Linux; Installing Development Package for Linux
  • Page 15 – Table 5: Files Installed on a System Running Linux; Device Drivers from Source Code; clean
  • Page 16 – remove; Verifying Device Driver Loading; Software Installation for Solaris; Installing the Development Package for Solaris
  • Page 17 – Installation of DKseptel was successful.; Table 6: Files Installed on a System Running Solaris; Solaris 9 - Interface Name Checking; To use the package under Solaris 9, interface name checking; Solaris 10 - Additional Commands; can impact the system performance.
  • Page 18 – The system has to be rebooted to force the change to take effect.; Removing the Development Package for Solaris; and the user should reboot the system:
  • Page 19 – Configuration and Operation; Overview; the flexibility of the protocol stack,; System Structure; Table 7: Typical Telephony Systems Configurations; Small System; Number of boards
  • Page 20 – ISUP; ssds; Software Environment; Table 8: Host Processes and Utilities
  • Page 21 – System Configuration; System Configuration File Syntax
  • Page 22 – An example; Generating a System Configuration File; ) and details any operating system specific differences in
  • Page 23 – These REDIRECT commands are always required:
  • Page 24 – Protocol Configuration; Protocol; Protocol Configuration using the s7_mgt utility; Board Information Diagnostics; Protocol Configuration Using Individual Messages
  • Page 26 – board hardware parameters is generated in this format following; Table 9: Board Diagnostics – Hardware Parameters; Parameter
  • Page 27 – Watchdog Timer; Using the CT bus
  • Page 28 – Switching Model
  • Page 29 – Dynamic Operation; Program Execution; timeslot; Example Code - Building and Sending SC_LISTEN
  • Page 32 – Program Execution under Windows; gctload
  • Page 33 – Program Execution under Linux; mtpsl act 0 0; gctload –x
  • Page 34 – Program Execution under Solaris; Developing a User Application
  • Page 35 – yourself with the example programs and how they are built.; upe; exchanging messages with the MTP3 module. It loops back any MTP-; mtpsl; is an example of how to send messages to MTP3 to activate and; ctu
  • Page 36 – Message Reference; Software Environment Programmer's Manual; General Configuration Messages
  • Page 37 – MTP Interface Messages; documented in the MTP Interface messages section.; Event Indication Messages; asynchronously by different modules within the stack.; Message Summary Table; Table 10: Message Summary; Mnemonic
  • Page 39 – SSD Reset Request; When using s7_mgt, this message is generated by s7_mgt and must not be; module and set up its run-time parameters.; Parameter Description:
  • Page 40 – Status Response; On error, the following value can be found in the status message; Board Reset Request
  • Page 41 – operating software for the board.; Board Status Indication; download operation or failure during the procedure.; The type of board to be reset. This must be set to 2 for DSI SPCI Boards.
  • Page 42 – No status values indicating errors are defined.; Synopsis; sequence or on detection of a board status event.; Format
  • Page 43 – Description; Board Configuration Request; provide protocol configuration parameters.
  • Page 44 – PARAMETER AREA; check the status for success.
  • Page 45 – CT bus clocking mode; Primary Master, A Channel; Secondary Master, B Channel; Slave, initially A Channel
  • Page 47 – Data Rate; Serial Port
  • Page 48 – Value
  • Page 49 – General Module Identification Message; of the code file running on a live system.; Major revision identifier for the object being queried.
  • Page 50 – text; Read Board Info Request Message; DSI SS7 Boards, but only the parameters relevant to the
  • Page 52 – The DSI SPCI Board hardware revision number.; swa; The switch should be set to 8.; swb; appears when the -o3 feature of ssds is used.; esn
  • Page 53 – Hardware Control Messages; LIU Configuration Request
  • Page 54 – The line coding technique taken from the following table:; The frame format taken from the following table:
  • Page 55 – fixed values must be used.; faw; x9f for E1 operation and set to zero for T1.
  • Page 57 – LIU Control Request; from the following table:
  • Page 58 – The diagnostic loop back mode taken from the following table:
  • Page 59 – LIU Read Configuration Request; This message is sent to the DSI SPCI Board to read back the current
  • Page 60 – LIU Read Control Request; from the DSI SPCI Board.
  • Page 61 – LIU State Request; area of the message.
  • Page 62 – The current state of the LIU from the following table:; LIU CT bus Initialization Request
  • Page 63 – corresponding bit is set in
  • Page 64 – mode
  • Page 65 – CT bus Listen Request
  • Page 66 – For the SPCI2S, valid values for the LIU identifiers are 2 and 3.; interface and 1 to 24 for a T1 interface.
  • Page 67 – Fixed Data Output Request; the number of LIUs fitted.
  • Page 68 – is transmitted. The valid range for; is 1 to 31 for an E1 interface and; pattern; Reset Switch Request; board configuration.
  • Page 69 – CT bus Connect Request
  • Page 71 – local stream
  • Page 72 – source stream
  • Page 73 – The
  • Page 74 – Configure Clock Request; the local and bus reference clocks.
  • Page 75 – If the DSI SPCI Board is configured to be Slave to the CT bus, then it
  • Page 76 – automatically switches to use it as the clock reference.; then no signal is driven onto the bus.
  • Page 77 – Configure Clock Priority Request; mode, based on the last valid clock that was recovered.
  • Page 80 – s7_mgt Completion Status Indication
  • Page 81 – command line option specifying the module_id of the; Notification Module; to which the message is sent. For example:; The result of initial configuration coded as follows:; Clock Event Indication
  • Page 83 – LIU Status Indication; Message issued by the board to notify of changes of LIU status.; len; The status field in the message header is coded as follows:
  • Page 84 – Error Indication; occurring within the protocol software.
  • Page 85 – The Error Code
  • Page 86 – MTP2 Level 2 State Indication; by the user parts to determine destination accessibility.; just been entered. It is coded as follows:
  • Page 87 – MTP2 Q.752 Event Indication; The Event Code
  • Page 89 – MTP3 Q.752 Event Indication; given in the following table:; link
  • Page 91 – CONFIGURATION COMMAND Reference; Physical Interface Parameters
  • Page 92 – CT Bus Clocking Mode; Primary Master, Clock set A; Secondary Master, Clock set B; Slave, initially using Clock set A; causes the board to drive the CT_NETREF1 clocks on the CT bus when
  • Page 93 – Protocols selected to Run on the Board
  • Page 95 – number of boards supported.
  • Page 96 – result in a number of CT bus channels being not used.; SCBUS_LISTEN Command
  • Page 97 – MTP Parameters; MTP Global Configuration; Point Code
  • Page 98 – MTP Link Set
  • Page 99 – than the total number of signaling links supported.
  • Page 100 – Blink
  • Page 102 – MTP User Part; The service indicator.; ISUP Parameters; Global ISUP Configuration; The global configuration parameters for the ISUP module.
  • Page 103 – to the maximum number of circuit groups supported.; ISUP Circuit Group Configuration; all the circuits on a single E1 or T1 interface.
  • Page 104 – circuit group. Bit zero must always be set as it represents the
  • Page 105 – TUP Parameters; Global TUP Configuration; The global configuration parameters for the TUP module.
  • Page 106 – TUP Circuit Group Configuration; The configuration parameters for a group of TUP circuits.
  • Page 107 – This field is reserved for future use and must be set to zero.
  • Page 108 – Host Utilities
  • Page 109 – Protocol Configuration Using; Syntax
  • Page 110 – Enable diagnostic tracing.; Example
Loading the manual

March 2009

U03HSP

www.dialogic.com

Dialogic

®

DSI SPCI Network Interface Boards

Programmer's Manual


"Loading the manual" means you need to wait until the file loads and becomes available for online reading. Some manuals are very large, and the time they take to appear depends on your internet speed.

Summary

Page 2 - Copyright and Legal Notice

2 Copyright and Legal Notice Copyright © 1993-2009 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 furnished for informational u...

Page 3 - Contents

Dialogic ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 3 Contents Revision History ........................................................................................................... 6 1 Introduction .............................................................................

Page 5 - Tables

Dialogic ® DSI SPCI Network Interface Boards Programmer's Manual Issue 5 5 8 Host Utilities ................................................................................................... 108 8.1 ssds ..................................................................................................

Other Dialogic Models

All Dialogic Other