Voice Quality issues on ISDN trunks
When working on voice quality issues on ISDN trunks, there's not much we can do remotely; but, there are things we can do which will save you time.
First of all, find out which are the ds1 boards associated. Then while on SAT, do a
list measurements ds1 log
DS-1 LINK PERFORMANCE MEASUREMENTS DETAILED LOG REPORT
Counted Since: 6:00 pm WED MAY 6, 2009
Date Time ES BES SES UAS/FS CSS LOFC
05/20 16:10 0 0 0 0 0 0
05/20 15:55 0 0 0 0 0 0
05/20 15:40 0 0 0 0 0 0
05/20 15:25 0 0 0 0 0 0
05/20 15:10 0 0 0 0 0 0
05/20 14:55 0 0 0 0 0 0
05/20 14:40 0 0 0 0 0 0
05/20 14:25 0 0 0 0 0 0
05/20 14:10 0 0 0 0 0 0
05/20 13:55 0 0 0 0 0 0
05/20 13:40 0 0 0 0 0 0
We need to see the first 3 columns showing 0's. Otherwise, it would indicate sync (clock) related issues and that would be a different story we don't want to step into.
Knowing which firmware the ds1 boards are running is important because if it's too far behind, it may have something to do with the issue in question.
The easiest thing to do here is to send out a tech on site, and ask to take a "BERT" bit error tester with him. It's a device which he can use to tap into the channels and literally listen to the conversation and determine where the static, noise is coming from. The second thing to do would be to have a "Trk-id" button placed on the affected station so in case issue appears, the user can press the button and he/she will see TAC/member information on the phone's display. With that info available, we can trace back and find out where that call came from.
Any comments are more than welcome
First of all, find out which are the ds1 boards associated. Then while on SAT, do a
list measurements ds1 log
DS-1 LINK PERFORMANCE MEASUREMENTS DETAILED LOG REPORT
Counted Since: 6:00 pm WED MAY 6, 2009
Date Time ES BES SES UAS/FS CSS LOFC
05/20 16:10 0 0 0 0 0 0
05/20 15:55 0 0 0 0 0 0
05/20 15:40 0 0 0 0 0 0
05/20 15:25 0 0 0 0 0 0
05/20 15:10 0 0 0 0 0 0
05/20 14:55 0 0 0 0 0 0
05/20 14:40 0 0 0 0 0 0
05/20 14:25 0 0 0 0 0 0
05/20 14:10 0 0 0 0 0 0
05/20 13:55 0 0 0 0 0 0
05/20 13:40 0 0 0 0 0 0
We need to see the first 3 columns showing 0's. Otherwise, it would indicate sync (clock) related issues and that would be a different story we don't want to step into.
Knowing which firmware the ds1 boards are running is important because if it's too far behind, it may have something to do with the issue in question.
The easiest thing to do here is to send out a tech on site, and ask to take a "BERT" bit error tester with him. It's a device which he can use to tap into the channels and literally listen to the conversation and determine where the static, noise is coming from. The second thing to do would be to have a "Trk-id" button placed on the affected station so in case issue appears, the user can press the button and he/she will see TAC/member information on the phone's display. With that info available, we can trace back and find out where that call came from.
Any comments are more than welcome
Comments
Post a Comment