Call failure, please help, asap 2

[cmp241]

when making a call, the call fails and never connect. Below is the printout from Sysmonitor. You can see the call begin, but then it goes down hill from there. I am assuming this line, "11mS PRN: Line 5: Manual: Line Loopback Up" is part of the problem, I never saw Line Loopback Up before, what is it and how do I get rid of it. Also, another line, " 12mS PRN: LINE 5 IS DOWN", how can I verify that it's up or changing this setting. Any other comments or suggestions will be greatly aprreciated.

Thanks in advance.



1mS PRN: Monitor Started IP=192.168.42.10 IP 406 DS 3.1(56) PBX01
1mS PRN: LAW=A PRI=1, BRI=4, ALOG=0, ADSL=0 VCOMP=4, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=5 VMAIL=0(VER=0 TYP=1) CALLS=0(TOT=0)
11mS PRN: Line 5: Manual: Line Loopback Up
11mS ISDNL1Evt: v=5 peb=5,PHDI
11mS ISDNL3Evt: v=5 p1=5,p2=1001,p3=4,p4=127,s1=
12mS PRN: LINE 5 IS DOWN
12mS ISDNL3Evt: v=5 p1=5,p2=1001,p3=5,p4=0,s1=
17mS ISDNL2Tx: v=5 peb=5
0000 00 01 7f ...
17mS ISDNL1Tx: v=5 peb=5
0000 00 01 7f ...
28mS ISDNL1Evt: v=5 peb=5,F2 F1
29mS ISDNL1Evt: v=5 peb=5,F1 F2
29mS PRN: Clock 5: excursion 1
327mS RES: Wed 17/1/2007 14:12:16 FreeMem=48734156(12) CMMsg=2 (2) Buff=100 615 497 528 5 Links=10103 Elements=0
1018mS ISDNL2Tx: v=5 peb=5
0000 00 01 7f ...
1018mS ISDNL1Tx: v=5 peb=5
0000 00 01 7f ...
2018mS ISDNL2Tx: v=5 peb=5
0000 00 01 7f ...
2018mS ISDNL1Tx: v=5 peb=5
0000 00 01 7f ...
3001mS PRN: +++ START OF ALARM LOG DUMP +++
3001mS PRN: ALARM: 29/08/2006 11:43:15 IP 406 DS 3.1(56) <TLB Data Error> CRIT RAISED addr=00000000 d=16 pc=ff61f7ec 0021e574 ff5040dc ff403434 ff68d778 ff68d89c
3001mS PRN: ALARM: 29/08/2006 11:46:50 IP 406 DS 3.1(56) <TLB Data Error> CRIT RAISED addr=00000000 d=1 pc=ff61f7ec 00000000 00000000 00000000 00000000 00000000
3001mS PRN: ALARM: 29/08/2006 14:47:02 IP 406 DS 3.1(56) <TLB Data Error> CRIT RAISED addr=00000000 d=1 pc=ff61f7ec 00000000 00000000 00000000 00000000 00000000
3002mS PRN: ALARM: 29/08/2006 14:47:56 IP 406 DS 3.1(56) <TLB Data Error> CRIT RAISED addr=00000000 d=1 pc=ff61f7ec 00000000 00000000 00000000 00000000 00000000
3002mS PRN: +++ END OF ALARM LOG DUMP +++
3018mS ISDNL2Tx: v=5 peb=5
0000 00 01 7f ...
3018mS ISDNL1Tx: v=5 peb=5
0000 00 01 7f ...
3928mS ISDNL1Rx: v=5 peb=5
0000 02 01 01 03 ....
3929mS ISDNL2Rx: v=5 peb=5
0000 02 01 01 03 ....
4018mS ISDNL3Evt: v=5 p1=5,p2=1001,p3=5,p4=0,s1=
10011mS PRN: Line 5: Manual: Line Loopback Active
13909mS ISDNL1Rx: v=5 peb=5
0000 02 01 01 03 ....
13909mS ISDNL2Rx: v=5 peb=5
0000 02 01 01 03 ....
20011mS PRN: Line 5: Manual: Line Loopback Active
23890mS ISDNL1Rx: v=5 peb=5
0000 02 01 01 03 ....
23890mS ISDNL2Rx: v=5 peb=5
0000 02 01 01 03 ....
30011mS PRN: Line 5: Manual: Line Loopback Active
33871mS ISDNL1Rx: v=5 peb=5
0000 02 01 01 03 ....
33871mS ISDNL2Rx: v=5 peb=5
0000 02 01 01 03 ....
40011mS PRN: Line 5: Manual: Line Loopback Active
43853mS ISDNL1Rx: v=5 peb=5
0000 02 01 01 03 ....
43853mS ISDNL2Rx: v=5 peb=5
0000 02 01 01 03 ....
50011mS PRN: Line 5: Manual: Line Loopback Active
53834mS ISDNL1Rx: v=5 peb=5
0000 02 01 01 03 ....

 

[jml2665]

go into the monitor program, inder T1 tab, turn off loopback,

 

[jml2665]

oops, sorry forgot, in monitor it's under Trace Options then T1 tab

 

[hannibalik]

We had this problem and it was down to the wrong conversion of the lines. British Telecom had to come out and do the job again - we had to wait 5 working days. I hope that's not your issue.

 

[cmp241]

Thanks alot jml2665, the problem is fixed. Hannibalik, fortunately for us we didn't encounter your problem.

 

[hannibalik]

That's great news - good luck.

 

[jml2665]

real curious who did that to your system and why.

anyone with the monitor program who can access the IPOffice either locally or remote could do it

 

[kwing112000]

If the CSU is enabled the provider can do it as well i think.