False Busy Trunks on TL 11

[Gallian]

Hi,
I have a TLU75 route with the PTT and there are 16 trunks on this route. The trunks get false busy that is when the call has been ended the trunk status still remains IDLE BUSY. The temporary solution to this is to restart the TLP11 PU, which offcourse disconnects all the other real calls as well.
It is a 1 LIM BC 10 system. Can someone please guide why this happens and what is the permanent remedy for this problem.
BR
ecptfa

 

[longstone]

I think this problem occurs due to trunk-to-trunk connection. don't connect your analog trunks to another analog trunks that is yours.tl11 do not have b-answer

 

[patcher]

There is no way to trunk to trunk. If no clear disconnect, you had to set your SIG right. The only person who can transfer t-t is the operator but with supervision. Check your parameters and also try to reproduce the fault or verify how can you reproduce it, this way you can tell which parameter is wrong.//patcher

 

[Gallian]

Hi,
The Parameters are as follows
ROU SEL TRM SERV NODG DIST DISL TRAF
1 011000000000001 3 2100000000 0 30 128 00151515
SIG BCAP
200010000000 001100
The fault usually occurs at peak hours and in normal hours the trunks are usually IDLE FREE.

 

[patcher]

What is the CNI level of the system? So when you SUSIP the route, the result of Traffic State is IDLE and LineState is BUSY. This means program unit DTR is not updated properly after the call. Most probably upgrading it up to the last CNI will fix your problem; ask your Tech Support in your place...//patcher

 

[Gallian]

CNI Level is 140/R2A. Whats the latest CNI level in BC 10 do u know if there is a patch in any Higher CNI level for this Problem.
ecptfa

 

[patcher]

BC10 is now up to CNI142. Not sure if your fault is corrected in this level. //patcher

 

[patcher]

Its up to CNI143 but no related correction. Probably your fault is only customer related case. I am sure its timing problem between PTT and MD. This fault happen specially if you have less line more traffic. I am suspecting 2 fault here but not sure which one is happening. 1st: PTT's time before free marking is faster than the MD or MD's time is faster than the PTT. This case both seizure may create fault or mismatch status in DTR. Can you CNPIP your TLP11. //patcher

 

[rakirong]

post your route data so we can see(RODAP),the programming might be wrong.

 

[Gallian]

HI,
The route data is as follows.
ROU TYPE VARC VARI VARO FILTER
1 TL11 H'00000022 H'00000008 H'00000005 NO

The CNPIP for TLP 11 is
CNPIP:UNIT=TLP11;

PROGRAM UNIT INFORMATION
PU-NAME PU-NO PRODUCT NUMBER REV PATCH
TLP11 H'391 3/CAA 111 8758/011 R3A YES
TYPE
B'0000 0000 0000 0000 0001 0011 1000 0000
TYPEEXT
B'0000 0000 0000 0000 1110 0000 0100 1011
LOADED IN LIM
1
Waiting for ur response.
ecptfa

 

[Bartjo]

Same problem!!

We do have exactly the same prblem with the MD110
Same sofwtare level. Even if we pull the card the system tells us that there is a call (after putting back the card of course).
So there is an bug in the software, KPN can't find the problem. most of the time we see the trunks connected to eachother (no trunk to truk traffic)

 

[patcher]

Connected to each other? Can you try if you can ECF the extension to PTT and call that extension from PTT, see if this traffic case work. If yes, CTDEI the TL lines see if the call disconnect when you hang up the call. //patcher

 

[rakirong]

Does this problem happen on incoming or outgoing calls only? Or it is happening in both cases?

 

[rakirong]

Do you have a voice mail system in your pabx?Where is the destination of your incoming calls?& lastly is DISA feature activated in your system?

 

[rakirong]

iS THIS THE TYPE OF FAULTS YOU ARE GETTING WHEN YOU DO ALLOP AFTER THE CALLS?


RDATE RTIME
21JAN03 11:33:37
260 FAULT ON LINE TO INTERWORKING PABX OR PUBLIC EXCHANGE
DATE TIME ALP NOIF UNIT EQU BRDID INF1 INF2
21JAN03 11:33:37 12 28 TLP11 002-2-10-02 76 72 1
RDATE RTIME
21JAN03 11:33:38
260 FAULT ON LINE TO INTERWORKING PABX OR PUBLIC EXCHANGE
DATE TIME ALP NOIF UNIT EQU BRDID INF1 INF2
21JAN03 11:33:44 25 12 TLP11 002-0-50-07 76 90 1
RDATE RTIME
21JAN03 11:33:45
260 FAULT ON LINE TO INTERWORKING PABX OR PUBLIC EXCHANGE
DATE TIME ALP NOIF UNIT EQU BRDID INF1 INF2
21JAN03 11:33:46 5 38 TLP11 004-0-62-03 76 94 1
RDATE RTIME
21JAN03 11:33:46
260 FAULT ON LINE TO INTERWORKING PABX OR PUBLIC EXCHANGE
DATE TIME ALP NOIF UNIT EQU BRDID INF1 INF2
21JAN03 11:33:53 2 69 TLP11 002-0-50-05 76 88 1
RDATE RTIME
21JAN03 11:33:54

 

[Gallian]

Ok,
We do have a voice mail system and the Incoming calls are routed to the auto attendant,thats DIAVOX everything is then handled and routed by the voice mail system.The DISA has not been initiated. The Problem occurs only with outgoing calls.
The alarm 260 is present in the ALLOP when this problem occurs.It is resetted offcourse.

 

[Bartjo]

The answers on our site:
Those lines are normaly only used in case there is a problem. Users know how to select the destination code (not for long, we will block that).
It's always outgoing traffic.
CTDEI? next time we'll try
Voicemail? Yes, Onebox but not through the analog lines
DISA? We used it before, still active but no one uses it
Errors same answer as Gallian, reset... they look the same why?

 

[patcher]

Gallian, Can you try this. NOTE!!! The SACOP/SACOS below is only for BC10 TLP11 Rev R3A.

>SACOP:LIM=1,UNIT=TLP11,SECTOR=PROG,ADDR=79E1;
data under 79e1 should be 0A.

>SACOS:LIM=1,UNIT=TLP11,SECTOR=PROG,ADDR=79E1,DATA=02;
>YES;

After this make a test calls. Check if the changes we've made affect the trunks. If something is wrong you can easily change it back to 0A by changing the DATA=0A.

If no affect then ALREI and recheck you EQU if hanging still occur in the system.

//patcher

 

[Rou5]

hi ! Gallian.
I am used parameters.
ROUTE DATA
ROU TYPE VARC VARI VARO FILTER
12 TL11 H'00000001 H'00000188 H'00000015 NO

PTS sends "Dial tone" (varo 00000015).
good day..

 

[patcher]

I have no response on this one, what happened??? //patcher