Idle-busy problem on CAS extension

[cuneyt2020]

Hi
The system is BC10 CN144

We use tlu76/3 CAS ext.s between IVR system and MD110... And yesterday i realized that some ports didn't retrieve any calls for week... (Approximately 20 ports)And checked the status of these ports by susip command and saw that
traafic state is idle and line state is busy...
I restarted the board no solution, i restarted ELP7 again and no solution..
67160 is working properly bu the other ones are not (One of them is also seemed "reserved")
[tt]
<SUSIP:dir=67184&67179&67174&67160&67153;;
STATUS INFORMATION AT 10:17:39 17AUG05
DIR TYPE TRAFFIC STATE/PTR LINE STATE/PTR DIV STATE ADD INFO
67184 CAS IDLE #027C RESERVED #03E4
67179 CAS IDLE #0263 BUSY #03CB
67174 CAS IDLE #0268 BUSY #03D0
67160 CAS SPEECH #0276 BUSY #03DE
67153 CAS IDLE #027D BUSY #03E5
END

<SUSIP:dir=67184&67179&67174&67160&67153;;
STATUS INFORMATION AT 10:17:52 17AUG05
DIR TYPE TRAFFIC STATE/PTR LINE STATE/PTR DIV STATE ADD INFO
67184 CAS IDLE #027C RESERVED #03E4
67179 CAS IDLE #0263 BUSY #03CB
67174 CAS IDLE #0268 BUSY #03D0
67160 CAS SPEECH #0276 BUSY #03DE
67153 CAS IDLE #027D BUSY #03E5
END

<SUSIP:dir=67184&67179&67174&67160&67153;;
STATUS INFORMATION AT 10:18:02 17AUG05
DIR TYPE TRAFFIC STATE/PTR LINE STATE/PTR DIV STATE ADD INFO
67184 CAS IDLE #027C RESERVED #03E4
67179 CAS IDLE #0263 BUSY #03CB
67174 CAS IDLE #0268 BUSY #03D0
67160 CAS SPEECH #0276 BUSY #03DE
67153 CAS IDLE #027D BUSY #03E5
END

<SUSIP:dir=67184&67179&67174&67160&67153;;
STATUS INFORMATION AT 10:18:31 17AUG05
DIR TYPE TRAFFIC STATE/PTR LINE STATE/PTR DIV STATE ADD INFO
67184 CAS IDLE #027C RESERVED #03E4
67179 CAS IDLE #0263 BUSY #03CB
67174 CAS IDLE #0268 BUSY #03D0
67160 CAS SPEECH #0276 BUSY #03DE
67153 CAS IDLE #027D BUSY #03E5
END

<SUSIP:dir=67184&67179&67174&67160&67153;;
STATUS INFORMATION AT 10:22:02 17AUG05
DIR TYPE TRAFFIC STATE/PTR LINE STATE/PTR DIV STATE ADD INFO
67184 CAS IDLE #027C RESERVED #03E4
67179 CAS IDLE #0263 BUSY #03CB
67174 CAS IDLE #0268 BUSY #03D0
67160 CAS IDLE #0276 FREE #03DE
67153 CAS IDLE #027D BUSY #03E5
END

<SUSIP:dir=67184&67179&67174&67160&67153;;
STATUS INFORMATION AT 10:23:46 17AUG05
DIR TYPE TRAFFIC STATE/PTR LINE STATE/PTR DIV STATE ADD INFO
67184 CAS IDLE #027C RESERVED #03E4
67179 CAS IDLE #0263 BUSY #03CB
67174 CAS IDLE #0268 BUSY #03D0
67160 CAS IDLE #0276 FREE #03DE
67153 CAS IDLE #027D BUSY #03E5


[/tt]

My first question is , what is the reason for this? is it because of MD's fault or IVR sytems fault? (Seemed like BC12 slp60 problem??)

Second question is how can i reset these ports, without restarting IVR servers?

Rgrds

 

[cnhui]

have you tried to restart the program unit ELP7 and TL37 ?

bye

 

[rfpui]

RFPUI:UNIT=TLP60,LIM=...;

----------------------------------
If anything can go wrong, it will.
(Murphy's Law)

 

[rfpui]

sorry
RFPUI:UNIT=SLP60,LIM=...;

----------------------------------
If anything can go wrong, it will.
(Murphy's Law)

 

[whosrdaddy]

rfpui,

restart slp60 for CAS extensions? I don't think so...

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

 

[IPuser]

If restarting ELP7 didn't do it then restarting DER (or DERS1) just might - BUT will also cut off ALL busy extensions in the LIM.
If neither of those works then try ending and reassigning the affected CAS Extensions (EXTEE/EXTEI), although probably won't let you because they're busy.

Doing all this with the line to the IVR disconnected might give a better chance of success.

 

[cuneyt2020]

I thought about DER but as you said, it affects not only the cas extensions,also the agents who are talking at that time. It's effect area is grater than IVR restart
But actually still do not know what the reason for it.?
AS all of you remember there was a problem on SLP60 or TLP 60 idle busy port problem in BC12 and it was fixed on lter service packs

 

[IPuser]

The BUSY / IDLE appearance just indicates that the Line Block (ELP7) and the Distribution Block (DER) have got out of step. Although it normally shouldn't, there a 1,001 ways that could have happened.
In the case of ISDN Trunks it's even worse, because there you've got 3 Blocks that can get out of step - DTR, TL60 & SL60.
Diagnosong it is a rather different job than clearing it. If it's not happenening too frequently and you can live with clearing it occasionally, just make sure you're Service Packs are up to date. Otherwise you might need some pretty advanced diagnostics .