Technical Helpweb

Dialogic® Host Media Processing (HMP) Software

Configuring Dialogic® Digital Network Interface Boards (DNI) For PDK Protocols On Dialogic® Host Media Processing (HMP) Software

• Dialogic® DNI300TEPHMP - The Single span boards and Quad Span boards share the same MLM files for configuration while Dual span boards have different versions.
  
• Dialogic® DNI601TEPHMP - Dual span board
  
• Dialogic® DNI1200TEPHMP - The Single span boards and Quad Span boards share the same MLM files for configuration while Dual span boards have different versions.

1. How to configure Quad span (same as Single span) board for pdk_us_mf_io protocol for all spans.
2. How to configure Quad span board for some pdk_us_mf_io spans and some NI2 spans (mixed configuration).
3. How to configure Dual span board for E2 R2MF PDK protocols.

• Dialogic HMP Software 2.0 or Dialogic HMP Software 3.0 installed
• Note: Dialogic HMP Software 2.0 SU 140 was used for testing in this technote. It is recommended to use the most recent Service Update.
• At least one of the DNI boards listed above should be installed.
• Dialogic HMP Software should have a license tied to the serial number of the DNI board.

1. Stop all active applications and stop Dialogic® HMP Software services.
   
2. If Dialogic Configuration Manger (DCM) is not active, start up DCM via NCM.exe.
   
3. Double click on the DNI1200TEPHMP board and click on the Trunk Configuration tab. See screen shot below.
   
   
   
4. Highlight each Trunkx value and change each span to CAS (T1, Group 1) in the pull down menu, as shown below:
   
   
   
5. Select Apply. The following dialog box will come up.
   
   
6. Select OK and then OK again at the dialog box with the Trunk Configuration tab up.
   
7. Double click on the DNI1200TEPHMP board again and go to the Misc tab. You should see the new FCD and PCD files for this board (Select OK to leave this dialog box):
   
   
8. Check the logical ID value from the Physical tab for the DNI board and the HMP Software as shown below:
   
   
   Above dialog box shows the DNI board to have logical ID = 1
   
   
   Above dialog box shows the HMP Software have logical ID = 0.
   
   
   
9. Now go into the ..\Intel\HMP\cfg directory and create a new text file called pdk.cfg. It should contain the following format entry for each span:
   
   b <DNI logical ID> l <span number> f <fcdfilename> p <pcdfilename> v <CDPfilename> m <PDK MLM SYM file for 1200 board>  r <Resource Board’s Logical ID>
   
   The above entry indicates a board number (after “b”) and a span number (after “l”) but if the full board is just one protocol, it can have the format:
   
   b <DNI logical ID> f <fcdfilename> p <pcdfilename> v <CDPfilename> m <PDK MLM SYM file for 1200 board>  r <Resource Board’s Logical ID>
   
   Here is an example below for the current case:
   
   b 1 l 1 f gnetworkonly_hmpqsb_4_cas.fcd p gnetworkonly_hmpqsb_4_cas.pcd v pdk_us_mf_io.cdp m hmp_pdk.mlm.sym r 0
   b 1 l 2 f gnetworkonly_hmpqsb_4_cas.fcd p gnetworkonly_hmpqsb_4_cas.pcd v pdk_us_mf_io.cdp m hmp_pdk.mlm.sym r 0
   b 1 l 3 f gnetworkonly_hmpqsb_4_cas.fcd p gnetworkonly_hmpqsb_4_cas.pcd v pdk_us_mf_io.cdp m hmp_pdk.mlm.sym r 0
   b 1 l 4 f gnetworkonly_hmpqsb_4_cas.fcd p gnetworkonly_hmpqsb_4_cas.pcd v pdk_us_mf_io.cdp m hmp_pdk.mlm.sym r 0
   
   Key Points: Since the above is an ALL CAS configuration, the MLM SYM file selected is hmp_pdk.mlm.sym. Also, because the DNI1200BTEPHMP board does not contain any onboard DSP’s, the value for the “Resource Board’s Logical ID” will be the “HMP Software…” Board’s Logical ID (from DCM) because this is the entity which will contain all of the voice devices used for this protocol.
   After creating this file, save it.
   
   
10. Open a command window and run “pdkmanagerregsetup add” and hit Enter as given below:
    
11. Now start Dialogic services.

1. To do this, follow the same steps as above except in the Trunk Configuration tab (Step 4 above).
2. For the mixed configuration, select some ISDN spans and some CAS spans (the order is not important as long as your pdk.cfg file will match after):
   
   
   
   
3. Now your new FCD and PCD files for the above will be gnetworkonly_hmpqsb_2_ni2_2_cas.fcd and gnetworkonly_hmpqsb_2_ni2_2_cas.pcd.  Therefore, set up your new pdk.cfg as shown below:
   
   b 1 l 3 f gnetworkonly_hmpqsb_2_ni2_2_cas.fcd p gnetworkonly_hmpqsb_2_ni2_2_cas.pcd v pdk_us_mf_io.cdp m hmp_mixed.mlm.sym r 0
   b 1 l 4 f gnetworkonly_hmpqsb_2_ni2_2_cas.fcd p gnetworkonly_hmpqsb_2_ni2_2_cas.pcd v pdk_us_mf_io.cdp m hmp_mixed.mlm.sym r 0
   
   
4. Key Points:In this case, the new MLM SYM file is hmp_mixed.mlm.sym because this download is for ISDN and PDK protocols together, for each board. . In this situation, for the “Resource Board’s Logical ID” we still select the logical ID of the “HMP Software…” board from DCM. Since the DNI1200BTEPHMP board does not have on board DSP’s, the voice devices initialized for the protocol will be from the host based resources.
   
   
5. Since the first two spans were set up as NI2, then pdk.cfg file will be used for spans 3 and 4 listed. In this example, it will also be important to make sure that "pdkmanagerregsetup add" has been executed as well. Once that is done, you can start services and the first two spans will be downloaded for NI2 and the second two for pdk_us_mf_io PDK protocol.

1. In the trunk configuration tab, the protocol must be selected as: R2MF (E1, Group 1)
   
2. The new FCD and PCD files will be: ghmpl1_hmpdsb_2_r2mf.fcd/ghmpl1_hmpdsb_2_r2mf.pcd
   
3. The MLM SYM file for PDK for the DNI601TEPHMP board is: hmp_media_pdk.mlm.sym (All dualspan mlm.sym files will have the word "media" in there).
   
4. For this also, make sure to have run "pdkmanagerregsetup add" as before.
5. Only two lines maximum should be used for the pdk.cfg file - one for each span.
6. Sample pdk.cfg for this will look like the following:
   
   b 2 l 1 f ghmpl1_hmpdsb_2_r2mf.fcd p ghmpl1_hmpdsb_2_r2mf.pcd v pdk_ar_r2_io.cdp m hmp_media_pdk.mlm.sym r 2
   b 2 l 2 f ghmpl1_hmpdsb_2_r2mf.fcd p ghmpl1_hmpdsb_2_r2mf.pcd v pdk_ar_r2_io.cdp m hmp_media_pdk.mlm.sym r 2 
   
   In this case, the logical ID of the DNI601TEPHMP board is 2 and the Resource Board’s Logical ID is also 2 because we would like the board to use the resources on the same board. For this configuration we should not select the “HMP Software…” board’s logical ID value for the Resource Board’s Logical ID. It is also valid for to omit the “r” parameter and it’s value completely for conditions where the resources of the board are used for the protocol. Hence the lines above could also have been written as given below:
   
   b 2 l 1 f ghmpl1_hmpdsb_2_r2mf.fcd p ghmpl1_hmpdsb_2_r2mf.pcd v pdk_ar_r2_io.cdp m hmp_media_pdk.mlm.sym
   b 2 l 2 f ghmpl1_hmpdsb_2_r2mf.fcd p ghmpl1_hmpdsb_2_r2mf.pcd v pdk_ar_r2_io.cdp m hmp_media_pdk.mlm.sym
   
   The protocol selected here is the Argentina R2 PDK protocol.