oozenoz

That's the problem, right there... the T1 is slipping, but (probably) not enough to cause the trunks to go out of service.

Do you have an external CSU on the circuit between the DS1 card and the smartjack? If you do, check what it is using for it's clock source (suggest NETWORK so it takes clocking from the telco transmit)

What is the clock source for the system? You should be using the T1 here as well.

__________________
- calvin

rhwimmers

Its an extended D-Marc (shouldnt be a problem) and then straight to the MM710AP card... I take it they have integrated CSUs?

PBXtech.info

 

rhwimmers

Its a MM710AP card in a G350...Controlled by an S8700..

martinyoung

Do a "status sync" and see what your clock source is, it should not be 1A. If it is, now do a "ch sync" and verify that you have a DS1 as sync source. If you only have one DS1 that will be your sync source. If there is not a DS1 listed as sync, enter one now. If there is one there you need to restart it as your timing source. Do a "disable sync" then a "enable sync". After that passes, do a "status sync" again. You are now clocking off the DS1 and all the problems should be gone.

If you were clocking off the T1 already you now need to find out if the slippage is at your end or with the vendor. Make a loop back jack and get ready to perform some service affecting tests. You make a loop back jack using a biscuit or a spare wall jack lying around. You tie pins 1&2 to 4&5, or to use color code blue pair to orange pair. Let us know if this will be necessary.

__________________
Marty
Retired Avaya DSIC tech

martinyoung

I didn't catch it earlier that you have a G350. Sync is not set from Communication Manager for them. You can status the sync from CM but you set the sync from the console port of the G350.

__________________
Marty
Retired Avaya DSIC tech

rhwimmers

Not exactly sure what you think I should try... But from the 8700 stat sync I get this.
Stratum Level: 4
Maintenance Name: UDS1-BD Physical Location: 01B16
Switching Capability: Enabled
Excessive Reference Switching: No
B16 IS a DS1 (their are probably about 8-10 DS1s)

If I telnet to the G350 box I can do a show sync timing and get this
MG23-G350-023(super)# show sync timing

SOURCE MM STATUS FAILURE
--------- ------------------- ----------------------- ---------------
Primary Not Configured
Secondary Not Configured
Local v0 Active None

Active Source: v0 Sync Source Switching: Enabled

Do the MM710APs have integrated CSUs? Is their any config for it?

PBXtech.info

 

martinyoung

Your response is that the DS1 board in the G350 is not responding to clocking.

Go back to the G350 command line and type this "set sync interface primary v2".

You will not be changing the sync source, that will still be 01B16, but now the DS1 module will show up. Run the tests again that you ran in the message just before this. Then run the two tests mentioned previously.

Any change?

__________________
Marty
Retired Avaya DSIC tech

rhwimmers

MG23-G350-023(super)# show sync tim

SOURCE MM STATUS FAILURE
--------- ------------------- ----------------------- ---------------
Primary v2 Locked Out None
Secondary Not Configured
Local v0 Active None

Active Source: v0 Sync Source Switching: Enabled

ran the set command switched the primary to "locked out"... What did you mean that the DS1 will now show up
" You will not be changing the sync source, that will still be 01B16, but now the DS1 module will show up"

martinyoung

What do you get now when you "test board 023v2"? Remember to cancel after test 146 and do this test twice.

What do you get when you run the DS1 summary?

If you are still slipping, go back to the G350 and type "set sync source primary". Then run the above two tests again.

As to your second question, do a "display sync". Does the card appear on the list?

__________________
Marty
Retired Avaya DSIC tech

rhwimmers

well when I do the test board 023v2 - it fills up the first screen, then you can hit next page to view all the other tests...are you saying to just cancel after the first screen shows up- then run it again? If so, this is the results from it:
Port Maintenance Name Alt. Name Test No. Result Error Code

023V2 MG-DS1 138 PASS
023V2 MG-DS1 139 PASS
023V2 MG-DS1 140 PASS
023V2 MG-DS1 141 PASS
023V2 MG-DS1 142 PASS
023V2 MG-DS1 143 PASS
023V2 MG-DS1 144 PASS
023V2 MG-DS1 145 PASS
023V2 MG-DS1 146 PASS
023V2 MG-DS1 1227 ABORT 1412
023V201 ISDN-TRK 0123/001 36 PASS
023V201 ISDN-TRK 0123/001 255 PASS
023V201 ISDN-TRK 0123/001 256 ABORT 1116
023V201 ISDN-TRK 0123/001 257 PASS
023V202 ISDN-TRK 0123/002 36 PASS
Port Maintenance Name Alt. Name Test No. Result Error Code

023V2 MG-DS1 138 PASS
023V2 MG-DS1 139 PASS
023V2 MG-DS1 140 PASS
023V2 MG-DS1 141 PASS
023V2 MG-DS1 142 PASS
023V2 MG-DS1 143 PASS
023V2 MG-DS1 144 PASS
023V2 MG-DS1 145 PASS
023V2 MG-DS1 146 PASS
023V2 MG-DS1 1227 ABORT 1412
023V201 ISDN-TRK 0123/001 36 PASS
023V201 ISDN-TRK 0123/001 255 PASS
023V201 ISDN-TRK 0123/001 256 ABORT 1116
023V201 ISDN-TRK 0123/001 257 PASS
023V202 ISDN-TRK 0123/002 36 PASS
Port Maintenance Name Alt. Name Test No. Result Error Code

023V2 MG-DS1 138 PASS
023V2 MG-DS1 139 PASS
023V2 MG-DS1 140 PASS
023V2 MG-DS1 141 PASS
023V2 MG-DS1 142 PASS
023V2 MG-DS1 143 PASS
023V2 MG-DS1 144 PASS
023V2 MG-DS1 145 PASS
023V2 MG-DS1 146 PASS
023V2 MG-DS1 1227 ABORT 1412
023V201 ISDN-TRK 0123/001 36 PASS
023V201 ISDN-TRK 0123/001 255 PASS
023V201 ISDN-TRK 0123/001 256 ABORT 1116
023V201 ISDN-TRK 0123/001 257 PASS
023V202 ISDN-TRK 0123/002 36 PASS
023V209 ISDN-TRK 0123/009 257 PASS
023V210 ISDN-TRK 0123/010 36 PASS
023V210 ISDN-TRK 0123/010 255 PASS
023V210 ISDN-TRK 0123/010 256 ABORT 1116
023V210 ISDN-TRK 0123/010 257 PASS
023V211 ISDN-TRK 0123/011 36 PASS
023V211 ISDN-TRK 0123/011 255 PASS
023V211 ISDN-TRK 0123/011 256 ABORT 1116
023V211 ISDN-TRK 0123/011 257 PASS
023V212 ISDN-TRK 0123/012 36 PASS
023V212 ISDN-TRK 0123/012 255 PASS
023V212 ISDN-TRK 0123/012 256 ABORT 1116
023V212 ISDN-TRK 0123/012 257 PASS
023V213 ISDN-TRK 0123/013 36 PASS
It goes on up to port 24 with the same pattern...
Doing the list meas.. I get the following -

DS-1 LINK PERFORMANCE MEASUREMENTS SUMMARY REPORT

Counted Since: 8:59 am WED JUL 12, 2006
Valid 15-Minute Intervals in Last 24 Hours: 57
Seconds Elapsed In Current Interval: 605 ESF Error Events: 2
Test: none Pattern: none Synchronized: N/A
Loopback/Span Test Bit-Error Count: 0 Test Duration: 00:00:00

Worst 15-Minute Interval 24-Hour Current
Category Date Time Count Count Interval Count

Errored Seconds 07/18 23:30 37 2001 24
Bursty Errored Seconds 07/18 23:30 0 0 0
Severely Errored Seconds 07/18 23:30 0 0 0
Unavailable/Failed Seconds 07/18 23:30 0 0 0
Controlled Slip Seconds 07/18 23:30 37 2001 24
Loss Of Frame Count 07/18 23:30 0 0 0

If do a stat sync it still just lists the 01b16 card - but disp sync on the 8700 is below - note it only has DS1s that are local in the si cabinets..

SYNCHRONIZATION SOURCE (circuit pack location)

Stratum: 4

Primary: 01B16 Secondary:

CIRCUIT PACKS AVAILABLE FOR SYNCHRONIZATION
Location Type Name Slip Location Type Name Slip
01A16 DS1 dcs+ to n1 #2 y
01A14 DS1 CISCO VG200 y
01B17 DS1 IDZD 334172 y
01B18 DS1 IDZD 334175 y
01B16 DS1 DCS+ to MO y
01A15 DS1 VG200 #2 n
01A04 DS1 Trunk Gr 8 y
01A17 DS1 Trunk Group 8 y

NOTE: DS1 and BRI TRUNK sources result in stratum 4, type II synchronization

The remainder of the pages are blank...

oozenoz

Your results are promising.... this is what you reported earlier:
controlled slip seconds during the worst interval in the past 24 hours: 37
controlled slip seconds in the past 24 hours: 1573
current interval: 21

controlled slip seconds during the worst interval in the past 24 hours: 37
controlled slip seconds in the past 24 hours: 2001
current interval: 24

looks like the total error count keeps incrementing.... if the slips are in fact gone (which the DS1 test indicates) the counter will start to decrease to 0 as the day moves forward. keep running the list measurements every hour and monitor that value....

__________________
- calvin

martinyoung

The reason for canceling the test after 146 is because the rest of the tests are for each of the 24 channels of that T1 and you are not interested in that. Tests 138 through 146 are for testing the entire span for red, yellow, blue alarms, slips, framing, translations, etc.

Notice that test 144 is passing which means you are not slipping any more. The amount of echo should also be reducing, if not entirely gone. As oozenoz points out, the DS1 summary is a historical record for the last 24 hours so if you are clean now the data will decrease.

Since you do have other T1s in your system, you can run these same tests on them for a comparison, especially the DS1 summary test. If you want to see the details, display the DS1 log rather than the summary. This will display the data in 15 minute increments for the last 24 hours.

__________________
Marty
Retired Avaya DSIC tech

rhwimmers

looks like I will wait a bit and see what happens... I was HOPING this would fix the fax issue - no such luck
On a fax machine that has a handset - I can call a "bad" number and I get the initial beep - then it switches to just garbled junk... If I call a "good" number I hear that beep then the regular analog noises...

Another interseting thing - if I dial a fax via 5 digit I get the same results as a "bad" fax - the garbled noise - but if I call that DID via 8 digits, (9,1234567) it is a "good" fax...SO not sure if that helps -
It appears that you CAN fax to regular fax machines (line hooked into fax machine) but for these people that are on a faxserver of some sort or if they have an analog card in their PC - its not going through...
Thanks so much for the quick help today - learned a lot in the process!

oozenoz

Then let's move forward.

We can assume the slip problem has been fixed but keep an eye on it anyway.

I take from the rest of the last post that you use 5-digit dialing internally between stations, 9 is your external route access code and you dial locally using 7 digit numbers. Is this correct?

I also take it that if you attempt to dial from station to station the faxes do not complete - have you actually tested this or just listening to the tones? Modem cards will begin training (negotiating the transmit/receive speed for the transmission) based on the chipset on the card. So you can call one fax machine and it may sound completely different from another - at first. Each transmission rate has it's own characteristic 'sound.' Eventually the receiving machine will try different speeds, stepping down to lower and lower speeds until the sending fax can reply back that it's ok with that speed. If they can't negotiate, the call will drop.

Try faxing to known working faxes, make sure they work, then try the PC's that werent' working before. If this continues, we can look into changing the compression algorithm on the sending fax (I've actually had to do this myself to get faxes to go through to older machines, it's not difficult... just a pain)

__________________
- calvin

rhwimmers

You are correct for our dial plan... I did not try to actually send a fax doing 5 digit. I DO know that anytime the user hears the fax beep and then the garbled stuff - the fax fails...anytime they fax- hear the beep, then the modem noises, the fax goes through.
I printed a activity report from the fax - if you just dial the numbers from a fax machine that the status is "ok" you hear all themodem noises...If you dial any of the ones that are "NG" you get that beep - then garbled noise... So its easy to replicate, fortunately, but it is strange that certain "faxes" dont like my pri!