Inbound calls to CX flash sets once, clients get out of service tone

[RDECIT]

We have a CX with build 9.0.2.

It is linked to an ISDN 30 (8 channel active) The main number is a system speed call translated to a key appearance of 5000 on all sets. When we dial into the main line, the sets all flash once and the calling party gets the out of service tone.

All out bound calls are fine.

CSS Trace shows the following: (The main number is 352200 )

15:02:39 RI100 DPN 2B ISRM_I ;10;*3#*19*Z#*58*Ca*1*Z#*233*dIBc#*58*CI*W6a#
15:02:39 RI100 DPN 16 SSRM_C *50*7971954407#352200
15:02:39 RI100 DPN 17 CRM/CIM ;2;*166*1 2 3 4#*234*Y@#
15:02:51 RI100 DPN 2B ISRM_I ;10;*3#*19*Z#*58*Ca*1*Z#*233*`IBc#*58*CI*W6a#
15:02:51 RI100 DPN 10 SSRM_C *238*dXD#352233
15:02:51 RO100 DPN 2 CRM/CIM ;0;
15:02:51 RI100 DPN 17 CRM/CIM ;2;*166*1 2 3 4#*234*Y@#
15:02:52 RI100 DPN 2B ISRM_I ;10;*3#*19*Z#*58*Ca*1*Z#*233*dIBc#*58*CI*W6a#
15:02:53 RI100 DPN 16 SSRM_C *50*7971954407#352200
15:02:53 RI100 DPN 17 CRM/CIM ;2;*166*1 2 3 4#*234*Y@#

 

[kwbMitel]

How does the system respond if you dial 352200 from an internal set?

Success or failure will tell us if the issue is trunk related or routing related.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[kwbMitel]

New thought, check your alarms, is your E2T working?

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.

 

[Mitelpassion]

The CO is disconnecting the call, it's complaining about higher layer compatibility...

not sure what.
check outgoing call characteristics, higher layer compatibility under ISDN trunks. something there maybe misconfigured.

Looks like a services mismatch to me.
could also be a COS problem, check your COS, use a default one to test.

if you dial the speed dial internally do the phones ring as expected?
if you dial the key appearance number does this ring?
what is the key appearance programmed as?

looks like someone also tried dialling 352233 but this number didn't exist on your system so you disconnected the call first.

 

[RDECIT]

Thanks for all your suggestions, we have fixed this issue now. Originally there had been a mistake on the order. The CXi had been ordered with a BRI card, which was configured off site. When we got to site we found the client to have ISDN 30. We removed the BRI card and replaced with a PRI, but removed all BRI information AFTER the card swap. This looked like it had caused issues as we found a BRI reference (which we couldn't clear) to UNIT 1 which was now the PRI. In the end we cleared all Unit and Trunk information, installed the BRI in slot 1 and PRi in slot 2 and ran the config wizard. This resolved the issue.

 

[Mitelpassion]

wow how the hell did it even "accept" calls? (retorical Question

from experience removing cards and then deprogramming always causes issues.

E