Merlin Network Closcksync issues 4

[jonnybb1]

I have two Merlin Magix (rel 1 Rev6) Networked together via a T1 PTP circuit. Each Magix has a T1 trunk and a T1 TIE card (all are 100 DS1 cards).
Problem, the Tie connection on the MASTER unit has scratching and clicking and dropped calls, not all the time but periodically/daily. The other Tie connection on the SLAVE Magix has no issues. Here is the layout:

MAster: T1 trunk setup as Slot5, Primary Loop / T1 TIE is setup as Slot 4 Secondary Local

Slave: T1 TIE is setup as Slot 3, Primary loop,/ T1 Trunk is setup as Secondary local.

Again the problem is occuring on the TIE line to the MASTER unit where I get 8404 errors every day, and scrathing and clicking, even call drops periodically/ daily.

Things I have tried:
1) I have swapped the clocksync config for the SLAVE unit from primary to sec and from loop to local on both cards in all combinations.
2) I have swapped the T1 TIE card (on the MASTER unit)and renumbered.
3) I have moved to new wire pairs from the smart jack.
4) Swapped PAradyne 3150 CSU for another at both ends.
5) And have pulled out my hair!
6) Had the Telco (SBC) out twice to move wire pairs and runs tests to no avail.
7)Pulled out my hair!

Does anyone have a solution?

Thanx a bunch!

John B
San Diego, CA

 

[SYQUEST]

What exactly did Pacific Bell repair do?

Did they monitor the ckt with test equipment like a T-Berd?

If so what were the results?

Which San Diego COs or are they served from the same CO?

What about the cords or wiring between the DS1 module and CSU and NIU?

You state the errors and noise are on the Master side of the Tie T1. What happens on the Slave side of the Tie T1?

Do the T1s ride fiber or copper to the CO?

What parameters is the Tie T1 set up for? AMI/B8ZS/SF-D4/ESF: what is the Legend setup for in the Tie slot?

....JIM....

 

[jonnybb1]

Here are the answers as best as I can:
Q:What exactly did Pacific Bell repair do?
A:They ran an obtrusive loop test remotely from PTP and said all was ok.

Qid they monitor the ckt with test equipment like a T-Berd?
A:I do not think so...?
Q:If so what were the results?
A:N/A

Q:Which San Diego COs or are they served from the same CO?
A: There are 2 locations one in San Diego (Clairemont Mesa) & one in Chula VIsta. There is Copper from Customer to Fiber Huts beyaond that I don't know.

Q:What about the cords or wiring between the DS1 module and CSU and NIU?
A:Yes I did change all the wires from the NIU->CSU->PBX

You state the errors and noise are on the Master side of the Tie T1. Q:What happens on the Slave side of the Tie T1?
A:When there is static on the MAster (in San Diego) calls that are transferred from the Slave (Chula Vista) over the TIE get dropped.

Qo the T1s ride fiber or copper to the CO?
A:Copper to the Fiber HUt, and SBC did change the wire pairs.

Q:What parameters is the Tie T1 set up for? AMI/B8ZS/SF-D4/ESF: what is the Legend setup for in the Tie slot?
A: B8ZS - B8ZS

I am sorry I don't have all the answers, but maybe this helps you help me I hope! Thanx for the reply!

John B
San Diego

....JIM....

 

[SYQUEST]

Just verifing some things. You mentioned the Line Code is B8ZS, but what is the framing format, SF-D4 or ESF?

Now PB's T1 parameters must match the Magix's T1 settings. In this case since it "works" so to speak the framing must be OK or it would not work at all, but a Line Code conflict could cause the problem if they set a parameter to AMI somewhere in the T1 route either at the fiber hut or the one of the COs.

I am thinking this is a Pacific Bell problem. You need to have them verify their T1 parameters for this circuit FIRST. From your description this is an intermittent problem, so I would open a trouble ticket with repair and request they do some monitoring of the circuit to sectionalize where the errors are coming from. -- When they tested previously did they see the same errors you saw? I would also request they test or monitor at the customer premise.

You mention on the Clairemont Mesa end (SNDGCA03) it comes from a fiber hut. Do you have any idea the approximate cable length from the hut to the customer? And can you tell me what kind of NIU is at the customer location? What I am trying to learn is the type of design path the T1 is: HDSL or repeatered T1. HDSL can have Doublers in the circuit that can cause wierd problems. Are the NIUs the same type for both T1 circuits? If they are HDSL, PB can dump the maintenance log from the HTU-R module and look at its history.

I use to work for a paging company. One of our locations was 5252 Balboa Ave. The cable plant for this location was a real mess!! We had about eight T1s there. All copper, no fiber, lots of fun!

 

[SYQUEST]

---I hit the wrong key on the keyboard---

Continuing, the building had a fire on the first floor, luckily the MPOE did not burn, but the construction people backhoed the cable in the parking lot during reconstruction and it was a real big mess!

Anyway, let me know if you have any progress...

....JIM....

 

[redphone]

What are the Paradyne CSU's clock set to? The Paradyne at the Master location should be set to the CPE and the Paradyne at the Slave location should be set to the Network.

Have you tried bybassing the CSU's?

Also, the T1 Trunk and the Slave location should be setup as Secondary loop. But that shouldn't cause the problem your having. It is just a back up in case the PtoP goes down.

 

[jonnybb1]

I will check the CSU settings tomorrow. The T1 trunk at the slave location IS set secondary loop. So everything is getting clocked off the T1 trunk on the Master location. I am almost positive it is a clocking issue, but it is intermittent which causes the problem of reproducing it for troubleshooting at the Telco. But as I understand the whole Legend/Magix networking thing, if settings were off at the PBX or perifieral equipment, then these symptoms (the snap, crackle, pop, and some call drops) would be consistently happening until the right setting was changed.

Because this is only happening on the TIE line at the MASTER location, I think it has to be somewhere between the CSU (Paradyne 3150) and the Telco, but getting them to admit it is the problem.

 

[jonnybb1]

BTW, can you remond me how to check the settings on the CSU to make sure it is set to CPE??

John B

 

[SYQUEST]

Are the 8404 errors the only ones you are getting?
Can you post a print of the Error Log?

I would be interested in seeing what channels are generating these codes or others.

I believe you can download a copy of the Paradyne manual from the Avaya website.

....JIM....

 

[isoparts]

Hello all. I am sort of a newbie at pbx programming and need some help. I currently have a merlin magix pbx in house up and running. I just had a point to point T1 installed between one of my warehouses and my headquarters. I added a 100D to my HQ Magix....I installed a new Magix with a 100DCD card in it at my warehouse. I was wondering if anyone had instructions or a whitepaper that would help me get these two magix programmed and networked together?

All inbound / outbound traffic would be through my existing HQ Magix.

Any help you can offer is greatly appreciated! Thank you.

 

[SYQUEST]

Yes, you can download all the manuals for the Legend and Magix from Avaya's website. You want the Features document and the Networking Document for sure...

The Networking document covers all aspects of connecting multiple systems together which sounds like what you are planning to do. Also reading and searching thru old posts on the forum can provide you with good info too...

Happy reading!

....JIM....

 

[isoparts]

Thanks Jim. I spent hours on Avaya's website looking for information before coming upon this thread. It is hard to find the information that you need there...but now that I know what documents I am looking for...that should help. Thanks so much! Mike.

 

[SYQUEST]

Mike, I believe the correct URL is "support.avaya.com" and you do have a lttle hunting once there, but all the versions are listed. Sometimes it is a good idea to look at older versions of manuals because some information was not carried over when manuals were revised.

Hope this helps!

....JIM....

 

[isoparts]

Thanks again Jim. I found the correct document. For those of you that need it...it is here:

http://support.avaya.com/edoc/docs/legend/leg61nr1.pdf

or document number 555-661-150, Network Reference.

Thanks, Mike

 

[jonnybb1]

Sorry for the delay I thought I already posted a follow-up to the original reply...

Here is what happened:
An Avaya tech (dispatched from the call center) put a T-Bird on the smart jack and helped me to attest that our equipment is working fine.

SBC did a "Level A" rebuild on the PTP. They say they replaced a bad Fiber repeater, Faulty Titan Card, NIU, and jumpers. They say again that it tested clean afterwards.

I will check the error logs again today and see the result, but I have a feeling that they won't do all this work unless there is an actual problem they are hunting down!

Thanx for all your support! This is why I love this website!

John B

 

[isoparts]

Hi All, sorry if this is the wrong place to post this question, but i cannot find a better place.

I have successfully networked my two Magix locations together...I can call extensions to each office from the other and have centralized VM working. The problem that I am having, is that I cannot place outbound calls from the slave location...it is intermittent. Out of about 15 tries, maybe 2 will go through (btw, my main location handles all traffic...there is no outside connectivity at the slave site).

I have been over the programming three times...and calling internal extensions works great...it is isolated to the local and LD calling...dial 9-1-xxx-xxx-xxxx amber light on the 100D card blinks once and then i get a fast busy.

Has anyone ever encountered this problem before?

Things I have researched:
- all channels full or bad channel on ptp t1...but wouldnt this cause problems with internal dialing as well?
- call restrictions...there are none set on either side.
- absorbed numbers...set to none.

I am lost...any help is greatly appreciated.

Thanks so much,

Mike

 

[ken1713]

Have you set ls disconnect at both switches? also check remote access and remove restrictions.

 

[isoparts]

ls disco is set on both slave and master switch. remote access is set to no restrictions.

 

[SYQUEST]

Hey Mike,

Can you post a printout of the ARS tables and trunk pool setup on the slave system? We need to see what you have set up for your config. This might be the area where the problem is.

Can you access a trunk in the pool directly and place a call that way?

....JIM....

 

[isoparts]

I ruled out hardware and Point to Point problems....brought the switch to my main location plugged it in directly via crossover. Swapped out cards with cards that I know work and still the same problem...intermittent calls outbound. Even looping through the channels on the PRI....channel 2 would work one time...but not the next...etc. I am thinking there is a problem with the master switch programming...but havent found any issues yet as all calls from the master site work fine. Here is the slave info:


SLAVE ARS

A AUTOMATIC ROUTE SELECTION


A ARS IS: ACTIVE ACCESS CODE: 9


A TABLE 25: Default Toll Output Table

A Pool Absorb Other Digits FRL Call type Start Pattern
A 1)899- 00 9------------------- 3 BOTH --:-- A
A 2)---- -- -------------------- - ----- --:-- A
A 3)---- -- -------------------- - ----- --:-- A
A 4)---- -- -------------------- - ----- --:-- A
A 5)---- -- -------------------- - ----- --:-- A
A 6)---- -- -------------------- - ----- --:-- A

A Pool Absorb Other Digits FRL Call type Start Pattern
A 1)899- 00 9------------------- 3 BOTH --:-- B
A 2)---- -- -------------------- - ----- --:-- B
A 3)---- -- -------------------- - ----- --:-- B
A 4)---- -- -------------------- - ----- --:-- B
A 5)---- -- -------------------- - ----- --:-- B
A 6)---- -- -------------------- - ----- --:-- B
A AUTOMATIC ROUTE SELECTION



A TABLE 26: Default Local Output Table

A Pool Absorb Other Digits FRL Call type Start Pattern
A 1)899- 00 9------------------- 3 BOTH --:-- A
A 2)---- -- -------------------- - ----- --:-- A
A 3)---- -- -------------------- - ----- --:-- A
A 4)---- -- -------------------- - ----- --:-- A
A 5)---- -- -------------------- - ----- --:-- A
A 6)---- -- -------------------- - ----- --:-- A

A Pool Absorb Other Digits FRL Call type Start Pattern
A 1)899- 00 9------------------- 3 BOTH --:-- B
A 2)---- -- -------------------- - ----- --:-- B
A 3)---- -- -------------------- - ----- --:-- B
A 4)---- -- -------------------- - ----- --:-- B
A 5)---- -- -------------------- - ----- --:-- B
A 6)---- -- -------------------- - ----- --:-- B
A AUTOMATIC ROUTE SELECTION



A TABLE 27: Dial 0 Output Table

A Pool Absorb Other Digits FRL Call type Start Pattern
A 1)899- 00 -------------------- 3 BOTH --:-- A
A AUTOMATIC ROUTE SELECTION



A TABLE 28: N11 Output Table
A 01)411 02)611 03)811

A Pool Absorb Other Digits FRL Call type Start Pattern
A 1)70-- 00 -------------------- 3 BOTH --:-- A
A AUTOMATIC ROUTE SELECTION


TRUNK POOLS:

A GENERAL TRUNK INFORMATION



A QCC QCC Extern
A Trk SS/PP RemAccess Pool TlPrfx HldDisc Principal Prty Oper Switch
A 801 1/ 1 No Remote 899 Yes Long 4 21
A 802 1/ 2 No Remote 899 Yes Long 4 21
A 803 1/ 3 No Remote 899 Yes Long 4 21
A 804 1/ 4 No Remote 899 Yes Long 4 21
A 805 1/ 5 No Remote 899 Yes Long 4 21
A 806 1/ 6 No Remote 899 Yes Long 4 21
A 807 1/ 7 No Remote 899 Yes Long 4 21
A 808 1/ 8 No Remote 899 Yes Long 4 21
A 809 1/ 9 No Remote 899 Yes Long 4 21
A 810 1/10 No Remote 899 Yes Long 4 21
A 811 1/11 No Remote 899 Yes Long 4 21
A 812 1/12 No Remote 899 Yes Long 4 21
A 813 1/13 No Remote 899 Yes Long 4 21
A 814 1/14 No Remote 899 Yes Long 4 21
A 815 1/15 No Remote 899 Yes Long 4 21
A 816 1/16 No Remote 899 Yes Long 4 21
A 817 1/17 No Remote 899 Yes Long 4 21
A 818 1/18 No Remote 899 Yes Long 4 21
A 819 1/19 No Remote 899 Yes Long 4 21
A 820 1/20 No Remote 899 Yes Long 4 21
A 821 1/21 No Remote 899 Yes Long 4 21
A 822 1/22 No Remote 899 Yes Long 4 21
A 823 1/23 No Remote 899 Yes Long 4 21
A 824 1/24 No Remote Yes Long 4
A 825 2/ 1 No Remote 70 Yes Long 4
A 826 2/ 2 No Remote Yes Long 4
A 827 2/ 3 No Remote Yes Long 4
A 828 2/ 4 No Remote Yes Long 4
A 829 0/ 0 No Remote Yes Long 4
A 830 0/ 0 No Remote Yes Long 4
A 831 0/ 0 No Remote Yes Long 4
A 832 0/ 0 No Remote Yes Long 4
A 833 0/ 0 No Remote Yes Long 4
A 834 0/ 0 No Remote Yes Long 4
A 835 0/ 0 No Remote Yes Long 4
A 836 0/ 0 No Remote Yes Long 4
A 837 0/ 0 No Remote Yes Long 4
A 838 0/ 0 No Remote Yes Long 4
A 839 0/ 0 No Remote Yes Long 4
A 840 0/ 0 No Remote Yes Long 4
A 841 0/ 0 No Remote Yes Long 4
A 842 0/ 0 No Remote Yes Long 4
A 843 0/ 0 No Remote Yes Long 4
A 844 0/ 0 No Remote Yes Long 4
A 845 0/ 0 No Remote Yes Long 4
A 846 0/ 0 No Remote Yes Long 4
A 847 0/ 0 No Remote Yes Long 4
A 848 0/ 0 No Remote Yes Long 4
A 849 0/ 0 No Remote Yes Long 4
A 850 0/ 0 No Remote Yes Long 4
A 851 0/ 0 No Remote Yes Long 4
A 852 0/ 0 No Remote Yes Long 4
A 853 0/ 0 No Remote Yes Long 4
A 854 0/ 0 No Remote Yes Long 4
A 855 0/ 0 No Remote Yes Long 4
A GENERAL TRUNK INFORMATION


A 856 0/ 0 No Remote Yes Long 4
A 857 0/ 0 No Remote Yes Long 4
A 858 0/ 0 No Remote Yes Long 4
A 859 0/ 0 No Remote Yes Long 4
A 860 0/ 0 No Remote Yes Long 4
A 861 0/ 0 No Remote Yes Long 4
A 862 0/ 0 No Remote Yes Long 4
A 863 0/ 0 No Remote Yes Long 4
A 864 0/ 0 No Remote Yes Long 4
A 865 0/ 0 No Remote Yes Long 4
A 866 0/ 0 No Remote Yes Long 4
A 867 0/ 0 No Remote Yes Long 4
A 868 0/ 0 No Remote Yes Long 4
A 869 0/ 0 No Remote Yes Long 4
A 870 0/ 0 No Remote Yes Long 4
A 871 0/ 0 No Remote Yes Long 4
A 872 0/ 0 No Remote Yes Long 4
A 873 0/ 0 No Remote Yes Long 4
A 874 0/ 0 No Remote Yes Long 4
A 875 0/ 0 No Remote Yes Long 4
A 876 0/ 0 No Remote Yes Long 4
A 877 0/ 0 No Remote Yes Long 4
A 878 0/ 0 No Remote Yes Long 4
A 879 0/ 0 No Remote Yes Long 4
A 880 0/ 0 No Remote Yes Long 4