Genesys Outbound: D/300 JCT E1 with Alcatel 4400

[Paul Bluefield]

Hi All,
Does anyone have any experience of integrating a Intel Dialogic D/300 JCT E1 with an Alcatel 4400? I've been trying to work out how it is done but I'm not getting anywhere!

I've installed the D/300 and connected it to the PCM2 card on the 4400. The D/300 is now showing Link On / Protocol error. CRC is set off on the switch.

The Dialogic provider say that when using Springware boards (inc. D/300) the application (CPD Server) must specify the Global Call protocol files to use but unlike GVP there is nowhere to specify this in Genesys Outbound.

Genesys are saying you don't configure anything in CPD.

So if you don't configure anything anywhere why isn't it working!

Any ideas?

[anon]

I don't know if this is true its what an Alcatel rep told me this morning, but he was saying the 4400 switch does the call detection functions.

[kerrickter]

Hi,

The Global ID is part of the properties that are supposed to be defined in the Dialogic Explorer application inlcuded with the dialogic drivers.

[IanDS]

What type of CAS has been configured on the PCM2 side. I havent done this in a while but it was pretty easy, once I knew what the PCM config and the bits being sent where.

[aizham]

Hi Paul,

Do you manage to settle your problem? I aa facing the same thing here with my outbound dialer. I don't know where to specify the Global Call Protocol.

Regards

[bcyk]

try below steps and hope they help....



[u]Step 0: E1 cabling and Dialogic D/300 JCT board[/u]
    - ensure that cabling is correct
    - for RJ-45, check TX+, TX-, RX+ and RX- are properly wired according to Dialogic manual
      ( should they be 1:TX+, 2:TX-, 4:RX+ and 5:RX- ? don't remember)

    - install Dialogic D/300 JCT board and drives (including global call)


[u]Step 1: PBX E1 protocols collection and extensions configuration[/u]
    - for line-side E1, CAS/FXS is expected
    - FXS? imagine that each channel is defined as "analogue" type in digital trunk
    - E1 channels at PBX side must be configured as FXS and with extension numbers
    - collect PABX side E1 protocol
      e.g., ccs, hdb3 and optional "CRC"

[u]Step 2: Dialogic Springware configuration[/u]
    - in most case, default values should work
      (a quick-and-dirty way: changing properties at PBX side and try!)
    - The springware parameter file is named "SPANDTI.PRM" under sub-folder of
      Dialogic program files
    - T1/E1 parameters can be altered in SPANDTI.PRM
      e.g., CRC ENABLE SWITCH is parameter type 0FH
            000F 00          ; turn CRC off (default)
            000F 01          ; turn CRC on

            PROTOCOL TYPE is parameter type 13H
            00H = standard CAS (default)
            01H = PRI ISDN
            02H = No signaling

    - edit and save changes if necessary
    - Open Dialogic Configuration Manager (DCM) program
    - In [MISC] tab, set parameterFile to SPANDTI.PRM

[u]Step 3: E1 link connectivity test[/u]
    A. Check the E1 RJ-45 port indicator at the D/300 JCT board
      - Green LED indicates powered up and receiving signal from external T-1 sources
        ** it is what is expected
      - Yellow LED indicate loss of frame synchronization at far end external network
        --> could be caused by caling pin assignment or protocol
      - Red LED indicate loss of frame synchronization on incoming line from external network
        --> mostly cabling issue

    B. make call using Dialogic Test program
      - standard Dialogic board installation disk includes a set of demo program
      - generic or Global Call demo programs should be under C:\Program Files\Dialogic\
      - DlgcTest.exe program will be briefly covered
        - pick the first channel of the E1 --> dxxxB1C1
        - pick the country specific *fxs* file (the FXS is required for line-side digital trunk)
            e.g., P_pdk_us_ls_fxs
        - make an outbound call to a real phone extension
        - if the dialed phone rings, done!
          DlgcTest.exe messages example
<timestamp> 372  OnInit: Global Call Lib Started

<timestamp> 580  InitChannel: Done Init [:N_dtiB1T6:P_pdk_us_ls_fxs_io] [GCDevH=5] [NetDevH=4]

<timestamp> 620  InitMedia: Done Init [dxxxB1C1] [MediaDevH=7]

<timestamp> 680  EventProcessorThread: STARTED

<timestamp> 983  handleGC_CallEvent [:N_dtiB1T6:P_pdk_us_ls_fxs_io]  Got GCEV_UNBLOCKED

<timestamp> 985  handleGC_CallEvent [:N_dtiB1T6:P_pdk_us_ls_fxs_io]  Calling gc_ResetLineDev

<timestamp> 997  handleGC_CallEvent [:N_dtiB1T6:P_pdk_us_ls_fxs_io]  Got GCEV_RESETLINEDEV

<timestamp> 999  handleGC_CallEvent [:N_dtiB1T6:P_pdk_us_ls_fxs_io]  Wait for call...

<timestamp> 1269  OnDial: gc_MakeCall: DestNum=5610  OrigNum=<nnnnnnn>

<timestamp> 1013  handleGC_CallEvent [:N_dtiB1T6:P_pdk_us_ls_fxs_io]  Got GCEV_ALERTING

<timestamp> 1094  handleGC_CallEvent [:N_dtiB1T6:P_pdk_us_ls_fxs_io]  Got GCEV_DROPCALL



[u]Step 4: Genesys CME Dialer ports configuration[/u]
    - use Outbound wizard will be the easiest way!
      - OCS wizard collects a set of data and applies to CME

    - manual configuration need some times
    - CPDServer application -> [Options] tab -> general folder
        option 'location' = 'cpd_ports'
    - [/Configuration/Resources/Switches/Alcatel4400/DNs/cpd_ports] folder will be
      created if using OCS wizard; otherwise, create the 'cpd_ports' folder manually
      Note: the Alcatel4400 is the switch object name; it is EXAMPLE here only

    - if OCS wizard is used, following folders should be present
      'regular' and 'recording' in 'cpd_ports' folder

The Regular folder contains the main voice channels (dxxx) and T1 (dt1) channel information.
The Recording folder is optional and contains voice channels dedicated for recording purposes.

Under 'regular', there should have a folder called dtiB1.
    Under this folder, there are 30 folders called dtiB1T1 to dtiB1T30.
    Each dtiB1Txx folder will be the extension that is the dialling port associated to that channel

Under the 'regular' folder, another 8 folders called dxxxB1 to dxxxB8 should be presented (or configured manually if not by OCS wizard)
    In dxxxB1 folder, four folders called dxxxB1C1, dxxxB1C2, dxxxB1C3 & dxxxB1C4 should be present
    The same for dxxB2-dxxxB7 folders, dxxxBnC1, dxxxBnC2, dxxxBnC3 and dxxxBnC4, where n=2...7
    In dxxxB8 folder, there will have only two sub-folders - dxxxB8C1 & dxxxB8C2.
    All dxxxBnCn folders remain empty

Genesys OCS deployment guide gives examples on these folder structures.


Configurations for OCS applications can then be started and tested.



regards