ISDN Overflow

[mszodiac]

Hi Everyone,

I've got this scenario:

2 Mitel MCD rel. 6.0 SP2.  Both are used as PSTN gateways.

1st MCD  has 6 T1s, programmed for incoming calls only.  2nd MCD also has 6 T1s but is programmed for outgoing calls only.  The problem is that outgoing calls are failing over to the 1st MCD randomly.  The traffic reports show there are plenty of idle channels on the 2nd MCD.  We've reshuffled the trunk members on the 2nd MCD, rebooted it, and at this point, we can't really find a pattern as to why it's happening.

Any other ideas on how to troubleshoot this? Thanks!

[ralph]

I suspect that you're getting a route failure signal from the carrier so then the Mitel will send it to the next route.
It's probably not a problem with the PBX but a problem with the carrier.
Is the 1st T1 group with the same carrier as the overflow group?

Ralph

[mszodiac]

I suspect that you're getting a route failure signal from the carrier so then the Mitel will send it to the next route.
It's probably not a problem with the PBX but a problem with the carrier.
Is the 1st T1 group with the same carrier as the overflow group?

Ralph

Yes! It is the same carrier for both groups.

[ralph]

I'm still thinking there may be a problem with the carrier that's sending a busy route message to the PBX.
The only thing I can think of is to run a CCS trace for a while and see if you can catch it.
It might not hurt to try and track what calls or overflowing via SMDR records and check to see if there is something in common such as area code.
If you can find some specific calls that are overflowing and you know your TG isn't busy then I think you could go to the carrier and have them do some traces.   They may have you set up on some "cheap" routes that are having their own congestion issues.

Ralph

[august]

Do you have an e2t card?  Maybe you are missing e2t?

In maintenance you can type: show status resource.

[mszodiac]

Do you have an e2t card?  Maybe you are missing e2t?

In maintenance you can type: show status resource.

Yes.  We have an E2T card.  Here's the status, although I really do not know how to translate it.  I've attached the snapshot of the output. 

[august]

I was looking for local e2t, but I don't see it.
 
You can try on the RTC shell the command: systemInfoTop

systemInfoTop: Starts a task that outputs the system resource information every 2.5 seconds.
The information is displayed using VT100 escape codes. For this information to be
displayed correctly, the terminal must be configured to be 132 columns wide and 48 rows
wide.The DSP, E2T and T38 information is updated once every other screen update to reduce the
load on the processor.

[mszodiac]

I was looking for local e2t, but I don't see it.

I wondered about the local E2T as well.  But we do have Echo Cancellation card with 128 channel.  I've attached our hardware modules config. 

[mszodiac]

@ ralph.  CCS trace was the first thing that came to mind.  But with an enterprise, it was almost impossible to see.  The screens on both gateways were just non stop.  There's also no pattern on SMDR.

[august]

You need the 128 echo canceller when you have the e2t card.  You can see the card in the Hardware Compute Card.

[mszodiac]

@august. Yes.  We do have 2 E2T cards. Does this equate to the 192 available under Remote E2T (show resource output)?