Problem with Dialog 4224

[Njoro82]

Hi Team,

I got a 3-LIM system, with group-switch of course, and 3 operator consoles(8001-3),when an external call is received on OP 8001,and it be transferred to an internal user, and for any reason the internal user returns the call to the operator, the console hungs. I usually do an RFEXI to release it from the system. This happens with only one console; (8001). I have tried to move it to different LIMS, and different board positions, but it keeps happening. Has anyone experienced this, and what could be the solution?

 

[himdp]

You do RFEXI on a 3 LIM system because one OPI hangs !!! That is madness.
What version are you running?
Any lost signals (HIMDP) associated with the event?

 

[matab]

hi
i think you dont need rfexi for this problem
if you think need restart first block equ
bleqi:equ=x.x.x.x;
if not resolve
rfboi:bpos=x.x.x;

when op hang
1-blfdp;
2-himdp;
3-opcgp;
4-cnbip:bpos=x.x.x.; for firmware of your op console

pg4ever

 

[himdp]

Most likely a software problem as the hardware position has been changed with no effect. Agreed that the firmware should be at the latest version but so should the system software be at the latest SP level.

To check for a software problem, clear the history log (HIREI then make a call using the test case which causes the OPI to hang. Now print the history log and see if any lost signals are produced (HIMDP

 

[Satellite1900]

madness

\Satellite1900

 

[kxts500]

replace op console with another if work properly and that op console not work oop console is fault
if not resolve with replace port or config is fault
madness!

 

[himdp]

Hi Guys,
I don't know why the "madness" thing has caught on, maybe I have started a meme .

I have seen this so many times. Someone works out that RFEXI will clear most problems so they use it routinely use it for minor issues. Guess what hot shot, it fixes problems because it restarts the whole fricking exchange.
This kind of maintenance strategy gets the exchange a bad name with users because they keep getting cut off in the middle of a call for no apparent reason.

The bottom line is that the exchange gets an undeserved bad reputation and the guy that is causing the problems gets away with his reputation untarnished; in fact some customers think the guy is a hero because he solves the problem - Go figure.
This is a case where the adage "a little knowledge is a dangerous thing" is entirely appropriate.