LCR

[Bicaros]

Hello
I have a problem with the configuration of the LCR to make calls from the HiPath 4000 V5 (MINE) to the outside via a HiPath 3800 (ADMIN).
Indeed it is a linear networks of a HP 4000 V5 with two HP 3000 product 2 card where the HP 4000 is located in the middle of the two HP 3000. However the ISDN to go outside is located on one of the HP 3000 at the end, so that, for an outgoing call from the HP 4000 or the second HP 3000 come out outside, it must go through the HP 3000, which has the ISDN.
How to configure the LCR to make this possible?
Currently calls between the 3 Hp pass properly, and the HP that has the ISDN also can go outside with the LCR "0C00Z" and "0CZ". But the second HP 3000 and HP 4000 can't exit outward through the HP that has the ISDN.
How to configure the LCR to make this possible?

 

[sbcsu]

Hi,
I notice from the KDS file that there is only 1 trunk group on the 3K
It is Trk Grp 1 set to CorNet-NQ
Where is the outgoing ISDN ?

 

[Bicaros]

Dear sbcsu,
The DIUT2 card has two ports: one with the lines 8001 to 8030 configured CORNET-NQ, and second daughter with the 8031 to 8062 lines configured for ISDN!

 

[sbcsu]

Hi,
Yes, so it has, however when I look at that KDS it shows 'No Port' on the DIUT2 8-2 but 8-1 shows the link CorNet-NQ

 

[Bicaros]

It is rather DIUT2 7-1-1 to 7-1-30 for CORNET-NQ, and 7-2-1 to 7-2-30 for ISDN.
I can't send you the KDS hereabouts, the download fails.

 

[sbcsu]

Well where is it at now ?
Have you been able to get a loan of an ISDN tester and put it towards the 3K ?
You could do some traces within the 4K if you are familiar with that ?

 

[Bicaros]

Hello sbcsu,
Everything is going well now and everything works properly!
We away bundles of cornet-NQ (1) that of the ISDN (16) on the H3K, and it works! This is because the bundles were side-by-side one another on H3K (ADMIN), that that does not work!
Thanks for all your support, thank you very much! The forum got much help to learn! Thanks for the correction made at the level of the H4K!
God bless you richly!

Kind regards

 

[sbcsu]

That is great news Bicaros,
God Bless and Thank You

 

[Bicaros]

Hello
I had a concern for reboot caused by disconnection in the several IP yesterday on my H4K post network, and I no longer have the hand by the WBM to administer from the's

http://192.0.2.5;

H4k even ping 192.0.2.5 spends more, Start-HISTA regere defective DD error (F09: AREA/DEVICE <:A1H1E:> IS DEFECTIVE)! I have the restart the H4K from the SD card! How to retrieve the DD and have the hand on the system from WBM (-

http://192.0.2.5)?

the "Expert Mode" works (192.0.2.3).


<COPY-DDRSM:UNIT=A1,MASTERID=1,MASTERAR=E&F,SLAVEID=6,SLAVEAR=E&F,REPLY=N;
COPY-DDRSM:UNIT=A1,MASTERID=1,MASTERAR=E&F,SLAVEID=6,SLAVEAR=E&F,REPLY=N;
H500: AMO DDRSM STARTED
F09: AREA/DEVICE <:A1H1E:> IS DEFECTIVE

AMO-DDRSM-111 DEVICE DOUBLE RECORDING SERVER MODULE
COPY NOT COMPLETED;


DISPLAY-DDSM;
H500: AMO DDSM STARTED
CONTROLLER: 1
TYPE: HD SS-NO : <STDH4> SIZE : 3346 MB ( 53550*64KB) GRAN : 512
AREA: A NAME : A1H1A STATUS : D E F E C T
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H1E STATUS : D E F E C T
CONFIGURED LOGICAL NAMES:
DS:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 200 MB (3200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H1F STATUS : D E F E C T
CONFIGURED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 62 MB (992 *64KB) A-GRAN: 4096
AREA: G NAME : A1H1G STATUS : D E F E C T
CONFIGURED LOGICAL NAMES:
:CGD:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 150 MB (2400 *64KB) A-GRAN: 4096
AREA: H NAME : A1H1H STATUS : D E F E C T
CONFIGURED LOGICAL NAMES:
MS:,SY:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 70 MB (1120 *64KB) A-GRAN: 4096
AREA: I NAME : A1H1I STATUS : D E F E C T
CONFIGURED LOGICAL NAMES:
:SCR:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 2047 MB (32767*64KB) A-GRAN: 4096
AREA: J NAME : A1H1J STATUS : D E F E C T
CONFIGURED LOGICAL NAMES:
:GLA:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 200 MB (3200 *64KB) A-GRAN: 4096
AREA: K NAME : A1H1K STATUS : D E F E C T
CONFIGURED LOGICAL NAMES:
IAG:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 616 MB (9868 *64KB) A-GRAN: 4096
CONTROLLER: 6 IS ACTIVE LOAD DEVICE, LOAD AREA IS: DS:
TYPE: HD SS-NO : <CF1G3> SIZE : 1183 MB ( 18932*64KB) GRAN : 512
AREA: A NAME : A1H6A STATUS : I N S E R V I C E
AREA-SZ: 0 MB (2 *64KB) A-GRAN: 512
AREA: E NAME : A1H6E STATUS : I N S E R V I C E
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
DS:
ACTIVATED LOGICAL NAMES:
DS:
AREA-SZ: 200 MB (3200 *64KB) A-GRAN: 4096
AREA: F NAME : A1H6F STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
BDA:,BD:,:TMD:,AS:,:AMD:,MP:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 62 MB (992 *64KB) A-GRAN: 4096
AREA: G NAME : A1H6G STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:CGD:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 150 MB (2400 *64KB) A-GRAN: 4096
AREA: H NAME : A1H6H STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
MS:,SY:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 70 MB (1120 *64KB) A-GRAN: 4096
AREA: I NAME : A1H6I STATUS : D E F E C T
AREA-DATA IN DATABASE AND ADMINISTRATION AREA ARE EQUAL
CONFIGURED LOGICAL NAMES:
:MOD-SCR:
NO LOGICAL NAMES ACTIVATED
AREA-SZ: 701 MB (11217*64KB) A-GRAN: 4096

AMO-DDSM -111 DISK STATUS
DISPLAY COMPLETED;


Best Regard