Can someone suugest how I might be able to trace call activity when calls are dropping. I was told by a telco that they had no netowrk problems and that the fault for calls being dropped must be in the Lucent switch. This seemed unlikely as we had 8 other services using the same 120 trunks and all the CSRS stations were spread across several different digital boards. The calls that were dropping were just for one VDN and the only CSRS affected were those to which calls were routed to from that VDN. I'd really liek to be able to discount switch error. Any info on how to monitor the switch would be appreciated.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Calls dropping 1
- Thread starter Scott99
- Start date
Guest_imported
New member
- Jan 1, 1970
- 0
display events, category denials, r9.5 or later SW version,
assuming ISDN trunks, or cdr reporting with disconnect information.
assuming ISDN trunks, or cdr reporting with disconnect information.
-
1
- #4
scottyjohn
Technical User
we had this problem and used the "list measurements ds-1 log xxxx" where xxxx is the board location of the DS-1 you are checking.
This displays the last 24 hours on the DS-1 you are looking at and armed with this data you can then go back to your telco and say "well actually, these circuits are showing errors of this type at this time".
It seems that our Telco's network monitoring system did not show our circuits as having any errors, despite us seeing call cut offs and serious error seconds at our end. We are getting them to look into the sensitivity of their alarm triggers but I dont think they will action! We'll just have to keep checking them at this end!
Hope this helps!
John
This displays the last 24 hours on the DS-1 you are looking at and armed with this data you can then go back to your telco and say "well actually, these circuits are showing errors of this type at this time".
It seems that our Telco's network monitoring system did not show our circuits as having any errors, despite us seeing call cut offs and serious error seconds at our end. We are getting them to look into the sensitivity of their alarm triggers but I dont think they will action! We'll just have to keep checking them at this end!
Hope this helps!
John
- Thread starter
- #5
scottyjohn
Technical User
Hi Scott,
The area of the log to look at is error seconds, bursty error seconds and severely errored seconds. I think these can relate to any fault which may occur, but in general we found that error seconds and bursty error seconds are not too much of a problem as the call will still hold, but severely errored seconds will drop the call completely. An engineer told us that bursty error seconds is possibly just a time sync slip between the trunk and its time source, but a severely errored second is when the trunk loses contact completely with its far end. We were showing errors all day and this was due to a faulty aggregate card at our telco. But to make it worse then there was a fiber break on the same ring which led to severely errored seconds and call cut offs.
Hope this helps. John
The area of the log to look at is error seconds, bursty error seconds and severely errored seconds. I think these can relate to any fault which may occur, but in general we found that error seconds and bursty error seconds are not too much of a problem as the call will still hold, but severely errored seconds will drop the call completely. An engineer told us that bursty error seconds is possibly just a time sync slip between the trunk and its time source, but a severely errored second is when the trunk loses contact completely with its far end. We were showing errors all day and this was due to a faulty aggregate card at our telco. But to make it worse then there was a fiber break on the same ring which led to severely errored seconds and call cut offs.
Hope this helps. John
- Thread starter
- #7
- Status
Similar threads