intermittent 'Call Barred' error message on phone screen

[fissure]

Hi there,

we have a site who reports occasionally getting a message on their Mitel 5224 phone screen of: Call Barred
when making outbound calls. They say they can attempt the call a few times in a row, get this error, then it goes through ok.

This is a Mitel 3300 CX, running 7.0.21.7 with call control relink: 37.0.9.14_SP1, no system relink has been applied.

The system is showing no alarms.
The system is using 4 x ISDN2e lines from British Telecom, all 8 channels are in the trunk group.

COS looks to be ok (and I would't expect a COS issue to cause this intermittent fault)

It is very unlikely all 8 trunks were in use at the time, and if they were, we'd have expected a different error anyway.

We've not come across this error, has anyone else seen it, or got any ideas?

Does it sounds like a Mitel issue or a line issue?

Thanks for your time, Neil.

 

[Lundah]

Sounds like the Telco is rejecting an call on an ISDN channel. Double check your config on the ISDN trunks, then call the telco.

 

[MitelInMyBlood]

I've seen this occur frequently on a tandem route where the distant machine disallows trunk-to-trunk calls, i.e., incoming tandem calls being interconnect-restricted from the distant machines telco trunks.

You can call an extension on the distant machine OK but if your distant party happens to have his PBX phone forwarded off-net the trunk interconnect restriction disallows the call. The upstream machine sees "Call Barred" when ordinarily they would be able to call the person, were it not for the fact that his phone is forwarded externally.

 

[T8keiteasy]

I've found this article on MOL :

Technical Bulletin
# 05-6298-00002

Article Title
How to prevent BRI call rejection problems after upgrading to 6.0.5.7 in EMEA region

Is this a new site or upgraded ?

Now, it's about French users too !!!

 

[fissure]

Thanks for everyone's feedback.

Using individual trunk select, we have dialled out with each trunk in turn, and encountered the issue on the last 2, of the 8 ISDN lines.

We have raised a fault with the telco and await their response.

If this turns out not to be the resolution, we'll post an update.