The CG 6565 board is based on the CG 6000/C, CG 6100C, and CG 6500C boards. Although the boards are very similar, be aware of the following hardware and software differences as you migrate from one of these boards to the CG 6565 board.
CG 6000/C,
CG 6100C, or |
CG 6565 board |
DSP C5420 100 MIPS each. Each chip has two cores. |
DSP C5441 133 MIPs each. Each chip has four cores. |
10/100Base-T Ethernet |
10/100/1000Base-T Ethernet |
Ethernet SPEED LED:
|
Ethernet SPEED LED:
|
No echo cancellation hardware |
Proprietary echo cancellation chip |
Status LEDs for each trunk: |
Red and yellow status LEDs for each trunk. For more information, refer to Trunk LEDs. |
CAS signaling processed in the DSP |
CAS signaling processed in the framer |
Agere T81xx |
Proprietary TSI |
As many as 8 DSP cores per HMIC stream |
4 DSP cores per TSI stream |
Each HMIC stream is 8 MHz with 128 timeslots |
Each TSI stream is 8 MHz with 128 timeslots |
Supports a 32-bit 33 MHz PCI bus |
Supports 32-bit or 64-bit, 66 MHz or 100-133 MHz PCI X bus, or 33 MHz or 66 MHz PCI bus. For more information, refer to Configuring the DIP switches. |
Board status LEDs - none |
Board status LEDs were added. For more information, refer to Board LEDs. |
The software differences between the CG 6000/C, CG 6100C, CG 6500C boards and the CG 6565 board include changes to the following:
The CG 6565 board product names that appear in the system configuration file depend on the number of trunks:
Product name |
Trunks |
CG_6565 |
No trunks |
CG_6565_4 |
4 trunks |
CG_6565_8 |
8 trunks |
The following system configuration file excerpt describes a CG 6565 board configured using no call control:
[CG 6565]
Product = CG_6565
Number = 0
Bus = 2
Slot = 9
File = c6565nocc.cfg
For more information, refer to Creating a system configuration file for oamsys.
The CG 6565 board keyword file differs from the board keyword files of the CG 6000/C, CG 6100C, or CG 6500C boards in the following ways:
The CG 6565 board uses framers instead of DSPs for signaling.
You must configure the trunks to perform signaling. Once you configure the trunks, use only channel associated signaling (CAS) to convey signaling information:
NetworkInterface.T1E1[x].SignalingType = CAS
The CG 6565 board does not require DSPs to do signaling. Do not set the following DSP values:
DSP.C5x[0].Files = qtsignal
DSP.C5x[0..1].Files = 8tsignal
The CG 6565 board merges the core file and the run module to create a file named cg6565core.ulm. The CG 6565 board does not require the following DLMFiles[x] settings:
DLMFiles[x] = cg6krun
DLMFiles[x] = cg6500run
In the CG 6565 configuration file, only set the DLMFiles[x] keyword when using the board with the following software:
Software |
Setting |
Generic ISDN |
DLMFiles[x] = c6565igen |
Fusion |
DLMFiles[x] = cg6565fusion |
ISDN management |
DLMFiles[x] = c6565imgt.dlm |
DPNSS |
DLMFiles[x] = c6565.dlm |
NaturalFax |
DLMFiles[x] = cg6565fax.dlm |
When you use only one DLM file, x is always 0 (zero). If using more than one DLM file, number them sequentially starting with 0 (zero). They can appear in any order. For example:
DLMFiles[0] = cg6565fusion
DLMFiles[1] = c6565igen
The following keywords are available to set hardware echo cancellation values:
Note: Do not use hardware echo cancellation in conjunction with software echo cancellation (that is, echo cancellation implemented through programs running on CG board DSPs).
For more information about hardware echo cancellation, refer to Configuring hardware echo cancellation.
All DSP resources must be managed by the CG 6565C resource management scheme. Use the following keywords to set up appropriate resource management:
Resource[x].Definitions and Resource[x].DSPs instead of DSP.C5x[x].Files to specify DSPs and DSP functions.
Resource[x].TCPs instead of TCPFiles[x] to specify TCPs.
The Conferencing API implements resource management differently than other NaturalAccess APIs. For more information, refer to the Dialogic® NaturalAccess™ NaturalConference™ API Developer’s Manual .
The CG 6565 board booting sequence differs from the booting sequence of the CG 6000/C, CG 6100C, and CG 6500C boards in the following ways:
CG 6565 boards do not require that you run the burnall script to update the flash memory on any CG 6565 boards in the chassis.
CG 6565 boards download the run file, cg6565core.ulm, directly into SDRAM when the boards boot up using the OAM API. This file is installed in the \nms\cg\load directory.
On CG 6565 boards, the OAM API utility, oammon, logs boot-specific information to cg6x6xboot_bus_slot.txt. For information about using the oammon utility and generating log files, refer to the Dialogic® NaturalAccess™ OAM System Developer’s Manual.
The following example shows oammon output:
Fri Feb 11 11:51:01 - OAMEVN_ALERT ERROR Board 1 "Name1"
1:9 - log cg6x6x boot info to file C:\WINNT\system32\CG_6565boot_1_9.txt
Fri Feb 11 11:51:01 - OAMEVN_ALERT ERROR Board 1 "Name1"
Writing at SDRAM 0xfa2c580 for 4535720 bytes ...
Fri Feb 11 11:51:01 - OAMEVN_ALERT ERROR Board 1 "Name1"
cg6565core.ulm loaded, version 2.10004, built Feb 11 2005
The ID for the CG 6565 board is 0x6565. For example, pciscan displays the following information:
PCI Boards Scanner
Bus Slot ID
--- ---- ------
1 7 0x6565 CG_6565
1 9 0x6565 CG_6565
There were 2 PCI board(s) detected
The OAM product number is 0x635 and is included in the \nms\include\nmshw.h file:
#define OAM_PRODUCT_NO_CG6565 0x635
CG 6565 boards use the CG 6500C switching model with MVIP-95 DSP streams of 64 to 67 as shown in the following boardinf example:
Natural Access Board Information Demo V.13 (Jan 25 2005)
MVIP-95
Board Addr Type MIPS Free memory Ports DSP Slots streams
------ ----- ----------- ----- ------------ ------ ----------- -------
0 1, 7 CG6565 6384 244076180 120 0..119 64-67
1 1, 9 CG6565 6384 244307880 128 0..127 64-67
Total port count = 248
The subsystem ID for a CG board is 0x6565 as shown in the following cg6ktool example (use the -A option when you run cg6ktool):
CG family command line tool, V3.00 (Dec 10 2004) Dialogic Corporation
Board SubSysID Bus:Slot Shelf-Slot Temp DSP Cores Trunks
CG 6565 6565 1:9 0-0 0.0 C 48 0
CG 6565 6565 1:7 0-0 0.0 C 48 4
CG 6565 boards use C5441 DSPs and not C5420 DSPs for applications. The DSP files have .f41 extensions instead of .f54 extensions. For example, CG 6000/C, CG 6100C, and CG 6500C boards use dtmf.f54, but CG 6565 boards use dtmf.f41. The .f41 files are in the \nms\cg\load directory (or /nms/cg/load for UNIX), which is the same directory that contains .f54 files.
Use f41info to display file resource usage instead of the f54info utility.
The Fusion msppsamp and tpktsamp demonstration programs include the –E option to disable software echo cancellation running on the DSPs. Set this option when using hardware echo cancellation on the CG 6565 board. For information on using msppsamp, refer to the Fusion Developer’s Manual.
The CG 6565 daughterboard includes an echo chip for providing hardware echo cancellation capabilities and to free up DSP resources. For more information, refer to Configuring hardware echo cancellation. To control hardware echo cancellation on a per-timeslot basis, refer to Using echo cancellation control.
Trunk impedance on the CG 6565 board applies to two trunks and must be identical for trunk pairs. For information about the pairings, refer to NetworkInterface.T1E1[x].Impedance.
CG 6565 boards include a temperature monitoring system. If the board temperature becomes too high, oammon generates either a warning or a critical error message. For more information, refer to Temperature and fan monitoring system.
CG 6565 boards do not support the following Switching service functions:
swiConfigStreamSpeed
swiGetStreamsBySpeed
All 32 H.100 streams are automatically configured for maximum capacity (8 Mbit/s or 128 timeslots).