GICI - Link

[CIF]

I am changing the GICI link to another NIU Board.

But when i give the command ISFUE ot kill the application connection i get the message: updating running.

So it is not possible for me to change tihs because of this message.
I blocked the existing NIU board but nothing changes.
It still gives me: "updating running"
Even after a few days of less traffic. (weekend)
I think it's locked because i get no messages from DNA to MD110. I change a subscriber in OWS but i can't see it on the telephone.

 

[doktor]

Hi CIF

You need to locate the program DIM and DIR.
Most important is DIM. If you send this command to the MD110: CNPIP:UNIT=DIM&DIR; you will see the LIM's where these programs are located.
Then restart DIM, in all LIM's listed (often in LIM=2&3).
This is done by: RFPUI:UNIT=DIM,LIM=;
Now, ISFUE should be possible. Otherwise restart DIR in all LIM's.
The reason for this misbehaviour, is the UPDFCN of the ICFUP;. If ICFUP channel for e.g. DNA absence registration or a voice mail service is set to UPDFCN=YES, you could have these problems regularly.
I try to set UPDFCN to NO, and manually do an updating, by setting it to YES, and then run the command: ICUPI;
Then problems with GICI seems to disappear.

///doktor

 

[CIF]

Thanx, The interface is reprogrammed.

But it is not working.

These are my parameters:



<ioddp;

I/O DEVICE DATA
NODE IODEV/SUBFS BPOS/EQU I/O-BUS TYPE/USAGE STATUS AUTH

LIMMEL - 012-0-52 - - IN SERVICE
LIMMEL GICI 012-0-52-4 - NETWORK/OUT IN SERVICE

END

<

<ioncp;

NETWORKING CONNECTION
NODE/IODEV LIM USER TYPE/CON IP PORT PROC

LIMMEL 12
GICI GICI-1 CLIENT 192.168.224.87 2656

END


<icfup;

INFORMATION COMPUTER COMMON FUNCTIONS DATA
UPDATING START TIME IS 02:30
MESSAGE WAITING FUNCTIONALITY IS ALL
INFORMATION COMPUTER EQUIPMENT DATA
IFCIND IODEV EQU RATE DFMT UPDFCN PARITY CCHECK
1 GICI 5 YES
FILLER=64 ICEXG=NONE USER=GICI-01

END

<

<isfup;

INTERCEPTION SERVICE GROUP DATA
IFCIND TEFMT TIFMT DTERM
1 2 2 01
END

 

[parnum]

I don't think it is working as under IONCP; 'PROC' you should have TCP as the protocol in use. Do you have any firewalls in place and have you opened port 2656 for TCP traffic?

best parnum

 

[doktor]

Very good input, parnum...
IF you get TCP under PROC we are closer to the success...

///doktor