Help: CG6000 isdn loopback test

Bangio · **Posted:** Tue Jun 17, 2008 2:49 am

I need to run isdn (on e1 trunk) test in loopback mode with a CG6000 board, which has two e1/t1 ports. I use CentOS (a RedHat based linux), I installed Natural Access but it seems that isdn doesn't work properly... I'm using this configuration file for the board:

Code:

#==============================================================================
#
#   This file configures the NMS board to run E1 ISDN or DPNSS.
#   
#==============================================================================
#   Boards: CG6000, CG6000C
#==============================================================================

Clocking.HBus.ClockMode                          = STANDALONE
Clocking.HBus.ClockSource                        = OSC
Clocking.HBus.ClockSourceNetwork                 = 1
TCPFiles                                         = isd0 nocc

#
# NOTE: for low density CG 6000 board, please ensure you change
#       the number of trunks, dsps, and resource size accordingly
#

DSPStream.VoiceIdleCode[0..3]                    = 0xD5                                                                                                         
DSPStream.SignalIdleCode[0..3]                   = 0xB                                                                                         
#
#   There are 3 HDLC controller cores per network interface.
#   PRI configurations use only one of the three HDLC cores on each network interface.
#   For PRI, configure Hdlc[x] where x is (network interface * 3)
#
Hdlc[0,3,6,9].Boot                               = YES
Hdlc[0,3,6,9].Hardware.TxTimeSlot                = 16
Hdlc[0,3,6,9].Hardware.RxTimeSlot                = 16

#NetworkInterface.T1E1[0,3].Type                 = E1
#NetworkInterface.T1E1[0,3].Impedance            = G703_120_OHM
#NetworkInterface.T1E1[0,3].LineCode             = HDB3
#NetworkInterface.T1E1[0,3].FrameType            = CEPT
#NetworkInterface.T1E1[0,3].SignalingType        = PRI
#NetworkInterface.T1E1[0,3].D_Channel            = ISDN



NetworkInterface.T1E1[0..3].Type                 = E1
NetworkInterface.T1E1[0..3].Impedance            = G703_120_OHM
NetworkInterface.T1E1[0..3].LineCode             = HDB3
NetworkInterface.T1E1[0..3].FrameType            = CEPT
NetworkInterface.T1E1[0..3].SignalingType        = PRI
NetworkInterface.T1E1[0..3].D_Channel            = ISDN
DSP.C5x[0..31].Libs[0]                           = cg6kliba 
DSP.C5x[0..31].XLaw                              = A_LAW                                                                                 
DSP.C5x[1..31].Files                             = voice tone dtmf echo rvoice callp ptf wave oki ima gsm_ms g726 mf
DSP.C5x[0].Files                                 = qtsignal dtmf voice rvoice wave
Resource[0].Name                                 = RSC1
Resource[0].Size                                 = 60
Resource[0].TCPs                                 = isd0 nocc

IPC.AddRoute[0].DestinationAddress = 192.168.1.160
IPC.AddRoute[0].Interface = 2
IPC.AddRoute[0].Mask = 255.255.255.0
################################################################
# Before modifying this resource definition string refer to the CG6000 
# Installation and Developers Manual.
#################################################################
Resource[0].Definitions         = ( dtmf.det_all & echo.ln20_apt25 & ptf.det_2f & tone.gen & \
    callp.gnc & ptf.det_4f & \
    ( (rvoice.rec_mulaw & rvoice.play_mulaw) | \
    (rvoice.rec_alaw & rvoice.play_alaw) | \
    (rvoice.rec_lin & rvoice.play_lin) | \
    (voice.rec_16 & (voice.play_16_100 | voice.play_16_150 | voice.play_16_200)) | \
    (voice.rec_24 & (voice.play_24_100 | voice.play_24_150 | voice.play_24_200)) | \
    (voice.rec_32 & (voice.play_32_100 | voice.play_32_150 | voice.play_32_200)) | \
    (voice.rec_64 & (voice.play_64_100 | voice.play_64_150 | voice.play_64_200)) | \
    (wave.rec_11_16b & wave.play_11_16b) | \
    (wave.rec_11_8b & wave.play_11_8b) | \
    (oki.rec_24 & (oki.play_24_100 | oki.play_24_150 | oki.play_24_200)) | \
    (oki.rec_32 & (oki.play_32_100 | oki.play_32_150 | oki.play_32_200)) | \
    (ima.rec_24 & ima.play_24) | \
    (ima.rec_32 & ima.play_32) | \
    (gsm_ms.frgsm_rec & gsm_ms.frgsm_play) | \
    g726.rec_32 | g726.play_32) )

DLMFiles[0]         = cg6krun
DLMFiles[1]         = isdngen   # Comment   for DPNSS
#DLMFiles[1]        = dpnss     # Uncomment for DPNSS
DLMFiles[2]        = imgt      # Uncomment if IMGT service is required

DebugMask           = 0x0

and this oamsys.cfg:

Code:

#-------------------------------------------------------
# oamsys.cfg
# This is the default OAM system configuration file,
# used by the oamsys tool. It describes all the NMS
# boards in a chassis.
#
# Each board is has its own section in this file.
# Each is delimited by a user-defined board name in
# square brackets. All board names and numbers must
# be unique.
#
# You will need to modify the bus and slot numbers
# for each board to match your chassis configuration.
# You may also need to add more board sections if you
# have more boards in your chassis.
#----------------------------------------------


[CG6000PCI]
    #-------------------------------------------------------------
    # Product Type
    # Choose ONE of the available product types for board 0.
    # You must have installed hardware support for the desired product family.
    # For an up-to-date list of available product types, run "oamcfg -c?"
    # from a command prompt.
    # The following product types existed at the last update of this file:
    #
    #   AG_2000, AG_2000_BRI, AG_2000_ENM, AG_2000_VTG, AG_2000C,
    #   AG_4000_1E1, AG_4000_1T1, AG_4000_2E1, AG_4000_2T1, AG_4000_4E1, AG_4000_4T1,
    #   AG_4000_E1, AG_4000_T1,
    #   AG_4000C_2E1, AG_4000C_2T1, AG_4000C_4E1, AG_4000C_4T1,
    #   AG_4000C_E1, AG_4000C_T1,
    #   AG_CPCI_Quad_E1, AG_CPCI_Quad_T1, AG_Dual_E1, AG_Dual_T1,
    #   AG_Quad_Connect_E1, AG_Quad_Connect_T1, AG_Quad_E1, AG_Quad_T1,
    #   AG_QuadDual_E1, AG_QuadDual_T1,
    #
    #   CX 2000-16, CX 2000-32, CX 2000C-16, CX 2000C-32, CX 2000C-48, CX_2000
    #
    #   CG_6000, CG_6000_Quad, CG_6000C_Quad
    #   CG_6100C_16 (16 trunks), CG_6100C_8 (8 trunks), CG_6100C (no trunks)
    #   CG_6500C_16 (16 trunks), CG_6500C_8 (8 trunks), CG_6500C (no trunks)
    #   CG_6060_4, CG_6060
    #   CG_6565_8 (8 trunks), CG_6565_4 (4 trunks), CG_6565 (no trunk)
    #   CG_6565C_16 (16 trunks), CG_6565C_8 (8 trunks), CG_6565C (no trunk)
    #
    #   QX 2000/100-4L
    #------------------------------------------------------------
    Product = CG_6000


    #-------------------------------------------------------------
    # Logical board number, physical bus, physical slot
    #
    #------------------------------------------------------------
    Number  = 0
    Bus     = 0
    Slot    = 9


    #-------------------------------------------------------------
    # Detailed board settings are in the following template files.
    # Uncomment ONE of the following board template files,
    # or add a new one.
    #
    # YOU MAY NEED TO MODIFY THE TEMPLATE FILES
    # for your particular application, or board type.
    #------------------------------------------------------------
    #File = c6nocc.cfg      # CG 6000 T1, no call control

    #File = c6wnk.cfg      # CG 6000 T1, Wink-start protocol
    File = cgi6e1.cfg     # CG 6000 E1, ISDN protocol
    
    # file di configurazione nuovo
    #File = cg6k_template.cfg

    #File = agpi2000.cfg   # AG 2000,     Wink and loop start protocols
    #File = agpi2bri.cfg   # AG 2000 BRI, ISDN protocol for Basic Rate Interface
    #File = agpiqe1.cfg    # AG Quad E1,  Wink-start protocol
    #File = agpiqt1.cfg    # AG Quad T1,  Wink-start protocol
    #File = agpi4000.cfg   # AG 4000 T1,  Wink-start protocol

    #File = qxpi2000.cfg   # QX 2000,     Loop-start protocol

    #File = cx2000.cfg     # CX 2000,     Sample file for any CX 2000

    #File = c61nocc.cfg    # CG 6100C E1 (T1), no call control
    #File = c61elc.cfg     # CG 6100C E1 (T1), E line interface card
    #** The following config files are installed with CAS package.
    #File = c61m108.cfg    # CG 6100C E1 (T1), MFC protocol for 10 dsp cores with 8 trunks
    #File = c61m2016.cfg   # CG 6100C E1 (T1), MFC protocol for 20 dsp cores with 16 trunks
    #File = c61mV208.cfg   # CG 6100C E1 (T1), MFC protocol and voice for 20 dsp cores with 8 trunks
    #File = c61mV3616.cfg  # CG 6100C E1 (T1), MFC protocol and voice for 36 dsp cores with 16 trunks
    #** The following config files are installed with ISDN package.
    #File = c61i108.cfg    # CG 6100C E1 (T1), ISDN protocol for 10 dsp cores with 8 trunks
    #File = c61i2016.cfg   # CG 6100C E1 (T1), ISDN protocol for 20 dsp cores with 16 trunks
    #File = c61iV208.cfg   # CG 6100C E1 (T1), ISDN protocol and voice for 20 dsp cores with 8 trunks
    #File = c61iV3616.cfg  # CG 6100C E1 (T1), ISDN protocol and voice for 36 dsp cores with 16 trunks

    #File = c65nocc.cfg    # CG 6500 T1, no call control
    #File = c65cas.cfg     # CG 6500 T1 CAS

    #File = c6565nocc.cfg  # CG 6565 E1, no call control


#------------------------------------------------------
# Uncomment the following section to boot another board
#-------------------------------------------------------
#[Name1]
    #Product = CG_6000C_Quad
    #Number = 1
    #Bus    = 2
    #Slot   = 14
    #File   = c6nocc.cfg

Anyone can help me? Can I test in loopback mode or do I need e real e1 trunk? The utility trunkmon shows that trunks are ok, isdncta initializes the isdn stack on every trunk, but then the demo programs don't work... Where's the problem?

Tim · **Posted:** Tue Jun 17, 2008 5:45 pm

I don't think you need this line when running in stand-alone mode:

Code:

Clocking.HBus.ClockSourceNetwork = 1

Do you know that your ISDNCTA parameters are different for loop-back configuration? One of your trunks must be set-up as the "network side" (use the -B switch), while the other is set-up as the "terminal side" (use the -b switch). From the command prompt, you can see all the switches available by running

Code:

isdncta -?

NMS has a Help Desk for configuration questions. You must subscribe to their site to use it. Start here:
http://www.nmscommunications.com/DevPlatforms/default.htm

Bangio · **Posted:** Wed Jun 18, 2008 6:59 am

Thanks Tim! I didn't set one trunk as TE and the other one as NT. Now isdndemo works.
Another question: if I add the library f_shared (as in many template configuration files) in this field

Code:

DSP.C5x[0..31].Libs[0] = cg6kliba

oamsys doesn't start the board. Why? What's the meaning of f_shared?

Tim · **Posted:** Tue Jun 24, 2008 10:11 am

I don't know what "f_shared" library is for. I'm going to go out on a limb and suggest that it has something to do with NMS Fusion - but that is just a guess. If it is not preventing you from running your application, I suggest you leave it out. If you need to troubleshoot this error, you can post questions on NMS Help Desk

Please not that this forum is for TeleFlow support and development. Have you taken a look at TeleFlow? It performs all the low-level board control, call control, media handling, and gives you, the developer, a rich set of tools to build and deploy complex telephony applications in a fraction of the time. You can download and try it for free at teleflow.org.

Bangio · **Posted:** Mon Jun 30, 2008 7:05 am

Which are the exact mapping between trunks, stream and timeslot? I have 2 ports and 4 slots; I discovered that trunk 1 and trunk 4 are connected each other (in loopback test mode), and trunk 2 and trunk 3 are connected each other. But what about the streams and timeslots? How can I address a trunk using stream:timeslot? This scheme is not clear to me:

Code:

Full duplex connection between the trunk voice information and the DSP resources: 
Trunk 1: 0:0..29 => 17:0..29, 16:0..29 => 1:0..29
Trunk 2: 4:0..29 => 17:30..59, 16:30..59 => 5:0..29
Trunk 3: 8:0..29 => 17:60..89, 16:60..89 => 9:0..29
Trunk 4: 12:0..29 => 17:90..119, 16:90..119 => 13:0..29

Maybe finally I understood: with trunk 4 started as NT and trunk 1 started as TE, I can call from 16:90 to 16:0 and viceversa (using isdnncc demo program). Am I right?

Tim · **Posted:** Wed Jul 09, 2008 5:43 pm

I can't comment on NMS's internal architecture or their "isdnncc" program.

I can tell you that if you put this statement in your CG 6000 board configuration file, it will make the default connections between the trunks and DSP resorces for you.

Code:

SwitchConnections = Yes

Also, if you use TeleFlow, it will take care of the streams and slots for you. TeleFlow provides a "port" entity, which for you would be one channel on one of your E1 trunks. All of your programming then deals with the port, and leaves the low-level details to TeleFlow to keep track of.

I hope this is of use to you.