NEC NEAX2000 ivs2 integration with UC500 series

[ben-miall]

I ave come across a customer who has an ageing NEC NEAX2000ivs2 PABX for resident areas and a CISCO UC500 for the offie area.  They are able to make calls between the two systems so not intergartion issues int hat respect.

The problem they are having is that on the NEC system all phones are able to see the extension number of the caller, however the Cicso phones whilst being able to receive the call cannot see the extensiohn number of the caller coming from the NEC system they just get caller unknown.  The calls between the Cisco handsets display the calling extension number fine.

Has anyone else come across this same issue and what were the workarounds.

Any assistance would be greatly appreciated.

[tarcorac]

Hello,

unfortunately, we don't have any hands-on experience with the NEC 2000, as we don't have one in our lab.  I'm assuming you're using ab ISDN PRI trunk to connect the UC500 to the NEC PBX. If that's the case, the best way to troubleshoot this problem would be by first assessing whether or not the NEC is sending the calling party ID during an outbound call. From the UC500 CLI, enter command "debug isdn q931". Place a test call. Check to see whether the calling party number is being passed within the setup message. Since the NEC 2000 is configured almost the same way as the 2400, you may also want to use the app note found at: http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/pbx/interop/notes/614999nt.pdf

as a guideline for configuring the ISDN PRI trunk. Even though the note was written for ISDN PRI QSIG trunk applications, some/most of the configuration is also applicable for other PRI protocol variants.

Tony Arcoraci

Unified Communications Interoperability Group