Digital Extension BLOKED

[Astonces]

Hi,

I have a problem with a Digital Extension in BC12 SP5.

How can I make this extension FREE and IDLE?

In this MD110, I cannot cut traffic to other extensions

<SUSIPIR=1220;
STATUS INFORMATION AT 12:53:40 10JUN05
DIR TYPE TRAFFIC STATE/PTR LINE STATE/PTR DIV STATE ADD INFO
1220 DTS IDLE #0258 BUSY #0390
ODN1:CONNECT
ODN2:IDLE
ODN3:IDLE


Thanks!!!

 

[rene2716]

Have you tried to do an RFBOI on the board ? or if this doesnt help remove the board and put it back.Try SFCEI and see if it becomes free, If this doesnt help you can try to restart programunit DER, but this interrupts traffic

grtz
rené

 

[NIUX]

Hi,

Print the below command (where xx is the blocked extension's LIM no):

SACOP:LIM=xx,UNIT=DER,DSOFF=9,FILNO=2,POINT=390;

BR///

 

[Runis]

Hi!!

I have the same problem as Astonces in BC12/SP5, hope you can help me too.

<SACOP:LIM=2,UNIT=DER,DSOFF=9,FILNO=2,POINT=390;
MEMORY CONTENT ON INDIVIDUAL POSITION
EXE A
FILE NUMBER RELOAD FILE START DS FILE START
2 0001F4C6
POINT RELOFF DSOFF ADDRESS DATA ISO
0390 0009 0002F1BF 60 `
END

Thanks,

 

[NIUX]

Hi Runis,

POINT is indicating the faulty extension's pointer for the given print-out of (Astonces).

You have to print:
SUSIPIR=XXX; for your extension.

BR///

 

[patcher]

Well... the easiest fix is to RFPUI KLP1T or KLP1O where the extension is located rather than waiting for an answer in this forum. You just need to talk to your customer when is the best time. This is because all DTS will be disconnected when you restart it. The other way is to SACOP and SACOS but may take a day or 2 or more if we will use the forum.

 

[alchohaz]

Is the information used for these pointers and what they do hidden away in ALEX?

I have the SACOS for the phone lock up pointers in BC9, but just curious as to where this located in the documentation.



[red]Striker : My orders came through. My squadron ships out tomorrow, we're bombing the storage depots at Daiquiri at 18:00 hours. We're coming in from the North, below their radar.[/red]
[blue]Elaine : When will you be back?[/blue]
[red]Striker : I can't tell you that? It's classified.[/red]

 

[whosrdaddy]

patcher,
we are seeing this type of error more and more since SP5 (even in SP7).
only correct fix for now is restart KLP1T (for releasing CONNECT) and DER (for resetting line pointer).

niux, that sacop is only for the line pointer (BUSY) but will not solve the CONNECT state.

alchohaz, this info is not found in ALEX and is only available for E/// guys and a few high level service partners. doing SACOS on a live system is not recommended because an error is quickly made and repairing corruptions made by SACOS are sometimes impossible.

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!

 

[alchohaz]

whosrdaddy, yep completely understand that as a an ex E/// engineer. Just thought i would try to get a bit more from the documentation if it was there.. But if it's not, no bother should be able to get elswhere it if i need it.

My past experiences have shown that these do clear themselves after a day or so, but of course it's often an MD, VP or equivalent whose phones goes in the middle of the day when the using KLP1T and DER is just not feasible.

Thanks anyway
Al



[red]Striker : My orders came through. My squadron ships out tomorrow, we're bombing the storage depots at Daiquiri at 18:00 hours. We're coming in from the North, below their radar.[/red]
[blue]Elaine : When will you be back?[/blue]
[red]Striker : I can't tell you that? It's classified.[/red]