|
|
Joined: Jan 2008
Posts: 11
Member
|
Member
Joined: Jan 2008
Posts: 11 |
I have a customer running a MICS w/6.1 Software. There are two DTI PRI cards installed. One PRI is a local T1 and the other is a Long Distance T1. The T1s use routing to determine which calls go out on each t1.
The problem is that the system is randomly dropping calls that appear to be longer than 20-Minutes in duration. It may drop the call after 22-minutes or after 31-minutes. It does not drop every call just about 1 out of 10.
The Local PRI T1 (Telepacific) is set as the Primary Clock Source with NI Protocol while the Long Distance T1 (Qwest) is set as Secondary with DMS100 Protocol.
What could cause this? It doesn't appear to be a Carrier Problem and I don't think both DTI cards are goofy.
|
|
|
Nortel Phone System Service in Canada
Do you need a Nortel Phone System technician or specific Nortel parts?
Atcom to the rescue! Our telephone techs have qualified experience servicing and troubleshooting Nortel CICS, MICS, & BCM telephone systems.
Service in Canada from sea to sea.
|
|
|
Joined: Apr 2001
Posts: 1,390
Member
|
Member
Joined: Apr 2001
Posts: 1,390 |
You have 2 different carriers?
And this problems is occurring on both spans?
How long in service before this started happening?
|
|
|
|
Joined: Oct 2002
Posts: 279
Member
|
Member
Joined: Oct 2002
Posts: 279 |
Is your 6.1 software the Maintenance Release (MR) version? And do you have a T1 or PRI, there were issues with pre 6.1 MR software and PRI's.
|
|
|
|
Joined: Feb 2007
Posts: 2,473
Member
|
Member
Joined: Feb 2007
Posts: 2,473 |
Why don't you set up both T1s as NI2? Besides,you might have a problems with COMBO module loosing sinchronization.
|
|
|
|
Joined: Jan 2008
Posts: 11
Member
|
Member
Joined: Jan 2008
Posts: 11 |
The MICS Version Level is "SP: 30CQE06 NAT".
It appears customer has received recent "Alarm: 44-0". The carrier has recently changed over circuits and I think that is when the dropped call problem started.
I am going to switch the Primary Clock Source to the LD T1 to see if it is a clocking issue.
|
|
|
|
Joined: May 2004
Posts: 335
Member
|
Member
Joined: May 2004
Posts: 335 |
I have yet to experience a T-1 issue that has turned out to be the MICS system, once it was up and running. Every complaint about dropped calls, can't call out, etc has turned out to be Telco so far.....knock on wood!
Punch down all your damn pairs!..........(please).
|
|
|
|
Joined: Jan 2008
Posts: 11
Member
|
Member
Joined: Jan 2008
Posts: 11 |
It appears after talking to both the Local PRI carrier and the Long Distance carrier that when mixing two or more T-1s it is best to make the Long Distance carrier the Primary Clock source because the local carrier usually has to sync with the LEC (if different) and can cause frame slippage problems which I think my customer was getting.
Since making the Long Distance carrier the Primary Clock source (local is secondary) the customer has not dropped any more calls. Also the MICS was pretty good about reporting an alarm (e.g., Alarm: 44-0) when the T-1 experienced a dropped call.
Another thing I have to remember is when changing T1 settings on the MICS it is best to reboot the MICS after all changes have been made. After I made T1 settings changes the PBX was acting very strange until we finally rebooted system and then everything was working great.
|
|
|
|
Joined: Jun 2006
Posts: 8,735 Likes: 12
Moderator-Nortel, Computers, General
|
Moderator-Nortel, Computers, General
Joined: Jun 2006
Posts: 8,735 Likes: 12 |
Scientists say that the universe is made up of Protons, Neutron & Electrons. They forgot "Morons". Dave. (CTUB) Canadian Techs Use Bix!
|
|
|
Forums84
Topics94,494
Posts639,868
Members49,836
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
117
guests, and
54
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|