Migration information

The CG 6565C board is based on the CG 6000/C, CG 6100C, and CG 6500C boards. Although the boards are very similar, be aware of the hardware and software differences as you migrate from one of these boards to the CG 6565C board.

Hardware differences

Software differences

The software differences between the CG 6000/C, CG 6100C, CG 6500C boards and the CG 6565C board include changes to the:

• System configuration file

• Board keyword file

• Booting sequence

• Board information

System configuration file

The CG 6565C board product names that appear in the system configuration file depend on the number of trunks:

The following system configuration file excerpt describes a CG 6565C board configured using no call control:

 [CG 6565C]
Product = CG_6565C
Number = 0
Bus = 2
Slot = 9
File = c6565nocc.cfg

Board keyword file

The CG 6565C 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 6565C 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 6565C 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 6565C board merges the core file and the run module to create a file named cg6565core.ulm file. The CG 6565C board does not require the following DLMFiles[x] settings:
  
  DLMFiles[0] = cg6krun
  DLMFiles[0] = cg6500run

• In the CG 6565C configuration file, only set the DLMFiles[x] keyword when using the board with the following software:

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:

• HardwareEcho.EchoChipEnabled

• HardwareEcho.Trunk[x].OnOffTimeslots

• HardwareEcho.XLaw

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 NaturalAccess NaturalConference API implements resource management differently than other Natural Access services. For more information, refer to the Dialogic® NaturalAccess™ NaturalConference™ API Developer’s Manual.

Booting sequence

The CG 6565C board booting sequence differs from the CG 6000/C, CG 6100C, and CG 6500C boards in the following ways:

• CG 6565C boards do not require that you run the burnall script to update the flash memory on any CG 6565C boards in the chassis.

• CG 6565C 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 6565C boards, the OAM utility, oammon, logs boot-specific information to CG_6565Cboot_<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 sample oammon output:

Tue Mar 22 16:20:46 - OAMEVN_ALERT ERROR Board 0 "CG6565CPCI"
2:10 - log cg6x6x boot info to file C:\WINNT\system32\CG_6565Cboot_2_10.txt
Tue Mar 22 16:20:48 - OAMEVN_ALERT WARNING Board 0 "CG6565CPCI"
Writing at SDRAM 0xfda3068 for 903872 bytes ...
Tue Mar 22 16:20:56 - OAMEVN_STARTBOARD_DONE Finished   INFO Board 0 "CG6565CPCI"
Board is started.

Board information

• The ID for the CG 6565C board is 0x6566. For example, pciscan displays the following information:

PCI Boards Scanner
Bus Slot ID
--- ---- ------
1    7  0x6566 CG_6565C
1    9  0x6566 CG_6565C
There were 2 PCI board(s) detected

• The OAM API product number is 0x636 and is included in the \nms\include\nmshw.h file:

#define OAM_PRODUCT_NO_CG6565C    0x636

• CG 6565C 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 (Mar 2 2005)
                       MVIP-95
Board  Addr   Type        MIPS    Free memory    Ports   DSP Slots   streams
-----  ----   ----        ----    -----------    -----   ---------   -------
0    2,10   CG6565C     12768      244094764      384   0..383      64-67
Total port count=384

• The subsystem ID for a CG 6565C board is 0x6566 as shown in the following cg6ktool example (use the -A option when you run cg6ktool):

CG family command line tool, V3.00 (Mar 11 2005) Dialogic Corporation
Found  2 board(s)
Board   SubSysID   Bus:Slot   Shelf-Slot    Temp    DSP Cores    Trunks
CG 6565C    6566       2:10        15-137    31.0 C       96         16

• CG 6565C 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 6565C 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 6565C board. For information on using msppsamp or tpktsamp, refer to the Dialogic® NaturalAccess™ Fusion™ VoIP API Developer’s Manual.

• The CG 6565C board 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 6565C board applies to two trunks and must be identical for trunk pairs. For information about the pairings, refer to NetworkInterface.T1E1[x].Impedance.

• CG 6565C 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 monitoring system.

• CG 6565C boards do not support the following Switching service functions:

• swiConfigStreamSpeed

• swiGetStreamsBySpeed

All 32 H.110 streams are automatically configured for maximum capacity (8 Mbit/s or 128 timeslots).