# Migration information

The CG 6060C 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 6060C board.

## Hardware differences

CG 6000/C, CG 6100C, or CG 6500C board | CG 6060C board
DSP C5420 100 MIPS each. Each chip has two cores | DSP C5441 133 MIPs each. Each chip has four cores.
48 DSPs for 96 cores max (9600 MIPS) | 8 DSPs for 32 cores max (4256 MIPS)
CPU speed at 233 MHz — 500 MHz | PPC CPU at 333 MHz
10/100Base-T Ethernet | 10/100Base-T Ethernet
No echo cancellation hardware | Proprietary echo cancellation chip
Status LEDs for each trunk: CG 6000 – red and yellow CG 6000C - red, yellow, and green CG 6100C - green CG 6500C - green | Green 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 a 32-bit 33 MHz or 64 MHz PCI bus.
Hot Swap monitor (hsmon) displays messages based on whether the board handles are flipped or if the board is physically extracted (CompactPCI only). | Hot Swap monitor (hsmon) does not differentiate between physical extraction of the board and the board handles being flipped when it displays messages. For more information, refer to the Dialogic® NaturalAccess™OAM API System Developer's Manual.

## Software differences

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

- System configuration file

- Board keyword file

- Booting sequence

- Board information

### System configuration file

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

Product name | Trunks
CG_6060C | Generic name that can be used to refer to any of the CG 6060C board variants.
CG_6060C_4 | 4 trunks
CG_6060C_8 | 8 trunks
CG_6060C_16 | 16 trunks

The following example shows a CG 6060C board configured using no call control:

[CG 6060C]
Product = CG_6060C
Number = 0
Bus = 2
Slot = 9
File = c6060nocc.cfg

### Board keyword file

The CG 6060C board keyword file differs from the board keyword files of the CG 6000/C, CG 6100C, and CG 6500C boards in the following ways:

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

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

Software | Setting
Generic ISDN | DLMFiles[x] = c6060igen
Fusion | DLMFiles[x] = cg6060fusion
ISDN Management | DLMFiles[x] = c6060imgt.dlm
DPNSS | DLMFiles[x] = c6060dpnss.dlm
NaturalFax | DLMFiles[x] = cg6060fax.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] = cg6060fusion
DLMFiles[1] = c6060igen

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

### Booting sequence

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

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

- CG 6060C boards download the run file, cg6060core.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 6060C boards, the OAM utility, oammon, logs boot-specific information to CG_6060Cboot_<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 "CG6060CPCI"
2:10 - log cg6x6x boot info to file C:\WINNT\system32\CG_6060Cboot_2_10.txt
Tue Mar 22 16:20:48 - OAMEVN_ALERT WARNING Board 0 "CG6060CPCI"
Writing at SDRAM 0xfda3068 for 903872 bytes ...
Tue Mar 22 16:20:56 - OAMEVN_STARTBOARD_DONE Finished INFO Board 0 "CG6060CPCI"
Board is started.

### Board information

- The ID for the CG 6060C board is 0x6061. For example, pciscan displays the following information:

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

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

#define OAM_PRODUCT_NO_CG6060C 0x631

- CG 6060C 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 CG6060C 4256 244094764 384 0..383 64-67
Total port count=384

- The subsystem ID for a CG 6060C board is 0x6061 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 6060C 6061 2:10 15-137 31.0 C 32 16

- CG 6060/C 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 6060/C 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 6060C board. For information on using msppsamp or tpktsamp, refer to the Fusion Developer’s Manual.

- The CG 6060C 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 settings for the CG 6060C board are based on the board variant. For more information, refer to Configuring the T1 or E1 interface.

- CG 6060C 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).