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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem with T1 circuit

Status
Not open for further replies.

Redson101

Technical User
May 3, 2009
7
US
Working with an IP Office 500 at 4.2.14, and having a problem with a straight T1. Verified with the carrier the circuit is an E & M Tie, D4, AMI, wink wink. Yeah that old. Any time an outbound call off the circuit is made the circuit completes the call and stays up for 1-15 secs then crashes the circuit, in which both sides see the circuit in red alarm. To add more confusion, if an inbound call is made and sustained we can make all the outbound calls we want. As soon as we disconnect the inbound call, all outbound calls are dropped and the circuit crashes again. ANY IDEAS?
 
Have you taken a look at the T1 health in SSA (System Status Application)? Are you getting errors? I'll bet you are.

Kyle Holladay
ACA-I, ACA Call Center, ACS-I, ACS-M, TIA-CTP, MCP/MCTS Exchange 2007
ACE Implement: IP Office

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
 
What is the line signalling? CPE or the CO? You might to try to change that. Just a thought.
 
Don't think that will work;

Line Signaling: Default = CPE
This field affects T1 channels set to Loop-Start or Ground-Start. The field can be set to either CPE (Customer Premises Equipment) or CO (Central Office). This field should normally be left at its default of CPE. The setting CO is normally only used in lab back-to-back testing

Pressing the HELP button in the Manager won't hurt you..:p

Avaya_Red.gif

___________________________________________
It works! Now if only I could remember what I did...
___________________________________________
 
Neither do I but thought it couldn't hurt. Sounds like the systems don't see eachother in terms of signalling. Are you going through a CSU or direct to the IPO system?
 
I don't know about anyone else but I always have terrible issues wiht AMI/D4 and IP Office.

Kyle Holladay
ACA-I, ACA Call Center, ACS-I, ACS-M, TIA-CTP, MCP/MCTS Exchange 2007
ACE Implement: IP Office

"Thinking is the hardest work there is, which is the probable reason why so few engage in it." - Henry Ford
 
I've had D4/AMI links from IPO to other PBXs running for years with no trouble - so I don't think there is anything inherently wrong with IPO in this regard. It's very unusual that the pipe would go into red alarm...
Mike
 
That's why I was asking if the circuit was going into a CSU. The Network/DTE settings can (may) then be changed. I always question what the provider is set to though. I assume that he tried all the default settings (ESF/B8Zs)before anything else.
 
The signaling is CPE, and their old Executone was using old kentrox CSUs, however we are just going straight into the IPO from the circuit. Also we first tried to get the circuit up on ESF and the the circuit did not even come up.
 
The circuit does have to be D4 or else the IPO does not even recognize it, we have contacted the carrier and they tested the circuit hard and comes clean. Correctly me if I'm wrong, but if I am able to complete the call and receive inbound, doesn't sound like a framing or signaling issue!?!
 
Sounds like a protocol mismatch.

kholladay advised you to post information for the SSA application. Goto Alarms>Trunks>Line>24 hour performance

You will be able to see the t1 errors. Do you have any and what are they?

Also tell me if you are able to receive caller ID from your T-1 Tie. I believe you should not.
 
The provider says the protocol is set to Super Frame in which everything we are finding and what the provider says that D4 and Super Frame are the same. An option were are pursuing is placing a CSU between the IPO and the network that will allow us to manipulate the signaling, set the network side to D4 and the local side to Extended Super Frame.

Under SSA we are getting missed frames piling up when an outbound call is made.

No were not receiving caller ID.
 
You would not get caller ID on a T1 only on a PRI or is that Magix? I have not set up a T1 ever on a IPO so I won't be much help in programming but you said that if you have an incoming call it holds the outgoing connections without problem, that suggests that somehow the outgoing calls on it's own do not handle the d-channel information well and need incoming connections to keep the T1 alive.
Or maybe I am just babbling and need retraining after the weekend.

Joe W.

FHandw., ACS

If you can't be good, be good at it!
 
If you have framing errors then the circuit is afuk. May try to simply remove the cable to the PRI card, count to ten then plug back in.

 
FYI - I've looked up an AT&T T1 that we swung from Executone IDS to IPO some 18 months ago. Configured close to yours. We DO have an external CSU that we left in the mix. IPO config is as follows:
Channel Allocation 24 -> 1
Clock Quality: Network
CRC Checking = enabled
Haul Length: 0-115'
Channel Unit: Foreign Exchange
Line SubType: T1
Framing: D4
Zero Supression: AMI ZCS
Line Signalling: CPE
Incoming Routing Digits: 4
Channels - all are Bothway, bearer any, E&M Tie, Wink Start for both incoming and outgoing.

Hasn't skipped a beat...
Mike
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top