I have this problem, a 500 telephone type was functioning correctly until last friday, what happen to the phone is that I can´t hear the dial tone, I hear my own voice.
I can dial any other extension and rings in the other side, but I can´t hear the otherside, the telephone works perfectly in other place.
I usually save all the sesions if I make a mistake to know what I did and when, as I´m a newbie into meridian.. here is the mistake that appeared and what I think caused the problem to the telephone.... I work with a Meridian 1 Option 11.
This is the strange part of the file that I suppose could be the error and solution, what happened the day before the telephone was reported damaged. I don´t know if this is or not the cause.
REQ: prt
TYPE: tnb
TN 27 1
DATE
PAGE
DES
.
.
.
.
DATE 7 AUG 2002
NACT
TIM000 17:52 31/7/2003 CPU 0
AUD021 0019B60A 00000100 00000001 00000450 00000000 00000000 00000006 00000450
AUD028 0019B60A 00000100 00000001 00000000 00000000 00000000 00000006 00000450
AUD004 0019B60A 00000000 00000000 00000000 00000000 00000000 0000000C 00003180
AUD017 00000004 0000FFDE 0000FFFE
AUD019 00008114 00001150 00004050
AUD017 00000031 00007FCA 00007FFA
AUD019 00008C50 00001F50 00004180
AUD019 00008C54 00000450 00000181
AUD017 0000003F 0000FFDE 0000FFFE
****
OVL000
>
TFS501 4 1 0
TFS501 49 2 0
TFS501 63 1 0
This error "TFS501" mention something about found time slot x on a loop incorrectly identified as busy. The time slots have been idled. Since these time slots were not used by the system, they represented higher blocking probability.
I have tried move the actual TN to another, but it didn´t work . I tried the telephone in other place and it works perfectly.
What can I do..?
I can dial any other extension and rings in the other side, but I can´t hear the otherside, the telephone works perfectly in other place.
I usually save all the sesions if I make a mistake to know what I did and when, as I´m a newbie into meridian.. here is the mistake that appeared and what I think caused the problem to the telephone.... I work with a Meridian 1 Option 11.
This is the strange part of the file that I suppose could be the error and solution, what happened the day before the telephone was reported damaged. I don´t know if this is or not the cause.
REQ: prt
TYPE: tnb
TN 27 1
DATE
PAGE
DES
.
.
.
.
DATE 7 AUG 2002
NACT
TIM000 17:52 31/7/2003 CPU 0
AUD021 0019B60A 00000100 00000001 00000450 00000000 00000000 00000006 00000450
AUD028 0019B60A 00000100 00000001 00000000 00000000 00000000 00000006 00000450
AUD004 0019B60A 00000000 00000000 00000000 00000000 00000000 0000000C 00003180
AUD017 00000004 0000FFDE 0000FFFE
AUD019 00008114 00001150 00004050
AUD017 00000031 00007FCA 00007FFA
AUD019 00008C50 00001F50 00004180
AUD019 00008C54 00000450 00000181
AUD017 0000003F 0000FFDE 0000FFFE
****
OVL000
>
TFS501 4 1 0
TFS501 49 2 0
TFS501 63 1 0
This error "TFS501" mention something about found time slot x on a loop incorrectly identified as busy. The time slots have been idled. Since these time slots were not used by the system, they represented higher blocking probability.
I have tried move the actual TN to another, but it didn´t work . I tried the telephone in other place and it works perfectly.
What can I do..?