Mitel integrated to NEC PBX

[Frontline]

This is a new install. Site will be gradually moving their users from existing NEC system to the Mitel.

They have a Virtual MiCollab, a Virtual MCD, a physical MXe III as a PSTN gateway.
There are (2) PRI´s in the MXe for inbound/outbound calls and (2) PRI´s used to tie to the NEC PBX.

The issue we are having is when an external caller calls in to the NuPoint AA and tries to dial an extension on the NEC PBX. The call will ring the NEC phone one time, then the call drops. If I change the transfer type in the NuPoint from blind to supervised, the call will continue to ring the NEC handset until answered, but drops as soon as the NEC user picks up the handset.

All other scenarios seem to work ok. A direct DID call through the MXe to an NEC user rings through correctly and can be answered. An internal Mitel user can dial the NuPoint pilot number, dial the extension of an NEC user and the call will ring through and can be answered. Issue only happens with external callers to an NEC user

Not sure if this is an issue with the NuPoint trying to transfer an external call to NEC or if there is a configuration issue with the PRI´s and tie trunks to the NEC. All are set to use NI2


Any thoughts or information would be appreciated

[ZuluAlpha]

As a bridge while the problem is diagnosed could you have the NuPoint transfer the call externally to the DID? Depending on volume that might not be the cleanest solution but it might be something interesting to check.

[Frontline]

Thats a good thought for the short term

I'll give it a shot when I'm on site and update if it works, but still would like to find another solution

Thanks!

[lundah]

Any reason you're using NI2 on the link and not QSIG?

[Frontline]

Yes, unfortunately we are being told by the NEC vendor that the system does not support Qsig.

[v2win]

Could this possibly be a COR or interconnect restriction problem?

[Frontline]

Sorry for the late follow up on this one. It turned out to simply be an issue with the COS of the NuPoint ports. Public trunk to public trunk connect was not enabled. I swear we looked at that 3 different times, but you know how it is sometimes when you've been beating your head against something...you miss the little stuff

Thanks all for the replies