Hi,
Please bear with me on details - I'm trying to get to the point and sort this issue out as fast as I can. <smile>
Today we have had a few reports of users getting dropped calls when calling local(within area code)cell phones and hanging calls for 800 numbers and Int'l calls.
The dropped calls may be a cell phone signal range issue - I am not too concerned.
The hanging calls go out the T1 on the phone and the line never rings and the call apparently connects to the other caller but we cannot hear them.
The t! on our LED's for the phone remain on the display and we have waited for 5-10 minutes getting no results.
Then, we call back to the "same" number - it rings and connects and the call is ok now.
Last time I called AT&T Business/Customer support - our LD/Int'l carrier and had them run a test on our line, the have reset the circuit on the weekend and perhaps fixed the issue.
The AT&T "automated" phone call that calls me back on the status of the issue comes back always stating the line was tested and no problems found.
But, they have performed one intrusive test - they bring down the T1 and I am still unsure whether the test worked or not. And have had no resolution to any glitches we've had here.
I checked the logs and see nothing under Maint Logs - All. Just a DBMS check that comes back w/ 0 errors.
But, when I looked in the Logs-All Maint/Software form:
(These two types litter the logs)
#######################
Log Type: Software
Log Number: 2085
Severity: Warning
Date: 2008/Oct/13
Time: 14:28:36
Source: Call Control - Software
Description: trkhdlr_ logged invalid msg in releasing PLID 2 1 2 24 Peripheral State: 000, Data: 2C 0
Module: Call Control - Software
File Name and Line Number: log_outputs_util_en.c;2089
Log Type: Software
Log Number: 2081
Severity: Warning
Date: 2008/Oct/13
Time: 14:28:31
Source: Call Control - Software
Description: DAM audit recovered trk swid 67 at cab = 2 shelf = 1 slot = 2 circ = 24 in transient state 5 for too long owned by process hex 00 application 0
Module: Call Control - Software
File Name and Line Number: log_outputs_util_en.c;2089
######################
Anyone have any ideas or hints to what I should do next?
Thaks for any input!
-SP
Please bear with me on details - I'm trying to get to the point and sort this issue out as fast as I can. <smile>
Today we have had a few reports of users getting dropped calls when calling local(within area code)cell phones and hanging calls for 800 numbers and Int'l calls.
The dropped calls may be a cell phone signal range issue - I am not too concerned.
The hanging calls go out the T1 on the phone and the line never rings and the call apparently connects to the other caller but we cannot hear them.
The t! on our LED's for the phone remain on the display and we have waited for 5-10 minutes getting no results.
Then, we call back to the "same" number - it rings and connects and the call is ok now.
Last time I called AT&T Business/Customer support - our LD/Int'l carrier and had them run a test on our line, the have reset the circuit on the weekend and perhaps fixed the issue.
The AT&T "automated" phone call that calls me back on the status of the issue comes back always stating the line was tested and no problems found.
But, they have performed one intrusive test - they bring down the T1 and I am still unsure whether the test worked or not. And have had no resolution to any glitches we've had here.
I checked the logs and see nothing under Maint Logs - All. Just a DBMS check that comes back w/ 0 errors.
But, when I looked in the Logs-All Maint/Software form:
(These two types litter the logs)
#######################
Log Type: Software
Log Number: 2085
Severity: Warning
Date: 2008/Oct/13
Time: 14:28:36
Source: Call Control - Software
Description: trkhdlr_ logged invalid msg in releasing PLID 2 1 2 24 Peripheral State: 000, Data: 2C 0
Module: Call Control - Software
File Name and Line Number: log_outputs_util_en.c;2089
Log Type: Software
Log Number: 2081
Severity: Warning
Date: 2008/Oct/13
Time: 14:28:31
Source: Call Control - Software
Description: DAM audit recovered trk swid 67 at cab = 2 shelf = 1 slot = 2 circ = 24 in transient state 5 for too long owned by process hex 00 application 0
Module: Call Control - Software
File Name and Line Number: log_outputs_util_en.c;2089
######################
Anyone have any ideas or hints to what I should do next?
Thaks for any input!
-SP