MICS 6.1 / 2PRI dropping incoming calls

[leardininwc]

This is an MICS w6.1, 2xDTI in slots3,4 and 6P Combo in slot2. The system seems to work fine untill the comercial hits the air and they get a high volume of calls. There also 4 M0x16 station modules on the system. I have a DID configured to Ring Only about 38 M7208 sets with 4 Icm keys each. The 2 PRI circuits are with Tele Pacific and they tell me that my switch does not respond to a release request. Can anybody help please? I also see a lot of 312, 313, 367, and 904 events.

Thank you,
Michael Leardini

 

[lugerlover]

first thought is the dtmf recievers "lacking of" try adding add a 2nd combo


Event code: 312
Reset:
No

Description:
The clock server received an unexpected event or invalid FUMP message received by the clock.

Action:
Record information from the event and network logs then contact your local support group. No further action required.


--------------------------------------------------------------------------------
Event code: 313
Reset:
No

Description:
The clock server did not receive the clock alarm from the N15 after a time-out period.

Action:
Record information from the event and network logs then contact your local support group. No further action required

Event code: 367
Reset:
No

Description:
A reset has occurred in the BRI or DTI card. The first parameter indicates the card index, and the second parameter weather it is a BRI or DTI card.
The event occurs only if there are BRI or DTI cards present in the sysetm.

Action:
Obtain the BRI/DTI traceback for the card that reset.

Event code: 904
Reset:
No

Description:
ISDN Loop Driver received unexpected input.

Action:
If the event persists, contact your local support group.

 

[PERRYPJ]

ISDN DOESN'T USE DTMF FOR INCOMING CALLS, D-CHANNEL DOES ALL THE SIGNALLING

OLD ROLMEN WORKING ON NORTELS

 

[lugerlover]

oops sorry..usually must call a pri but really just T1

 

[DMilden]

We also had a similar problem awhile back with a PRI and T1. Site was interconnected with other sites but the dropped calls was only happening at this 1 site. After weeks of extensive testing with nortel it ended up being the software which at the time was 6.1 (7.0 wasnt out at this time). Nortel patched us a newer 6.1 version sent it to us and we havent had the problem since.

I would suggest upgrading to 7.0 before anything but Im unsure if this problem was patched in 7.0 or not.

 

[lugerlover]

yes there was a 6.1 MR

 

[leardininwc]

Thanks,
6.1 MR will be. I'll let you know if that will fix it.

Michael Leardini

 

[leardininwc]

Today for the first time it worked perfect without changing the software. What I noticed this morning was that all the incoming calls were coming on Line 31 instead of Line 1. All the outgoing call were going out from Line 53. I reversed the PRI lines so all incoming would come on Line 1 and that stopped all the problems, no more events. Could this have been the cause??

 

[lugerlover]

Nop ethink its a software issue where channel go mbusy and u grab it"cant dial out....mr fixed.as did 7.0.

 

[bwtc]

leardininwc,

Can you please post your system version, so we can know if you're on the proper MR ?

You can find it by going into programming -> Maintenance -> System version

Thanks