Nupoint SX-2000 PRI to Cisco --> No Caller ID 1

[Morgan22]

Hi,

I have an SX-2000 with PRI-PSTN with Nupoint Auto-Attendant.

We recently linked the Mitel to a Cisco IP PBX using another PRI (not QSIG).

Mitel to Cisco phone calls do have internal CallerID (name and number). PSTN calls to Mitel phones through Nupoint do display callerID.
However PSTN calls through Nupoint and then forwarded to the Cisco PBX do not show callerID but instead display something like "VoiceMail". PRI D-Channel traces confirm that "VoiceMail" is passed to the Cisco pbx instead of the external caller's name and phone number.

My local contacts are saying "that's the way it works"...

Any help appreciated,

Thanks,

Eric

 

[TheMitelGuy]

Sounds like T1 is grabbing the values before the NP hangs up. I would agree with your Mitel dealer ("that's how she works"), but I have to think about a way around this...

 

[TheMitelGuy]

Try something...

Try sending the call to an extension, and then doing a RNA/Call Forward NA to the T1 to the Cisco. That might fix it.

 

[TheMitelGuy]

Your problem is coming from, the T1 is sending the CallerID of the "owner" of that particular call. It's true it is NuPoint (VoiceMail) for a period of less then one second, however the ownership should change to the CallerID once NP hangs up (i.e. the PBX does not have a owner to that call). You need to find a way to caputre the CallerID after NP hangsup >> hence my suggestion to reroute it to an extension and then on from there.

 

[piguligu]

Please tell me how can you do PRI D-Channel trace on Sx-2000 . From maintenance or from serial port on PRI card ?

 

[Morgan22]

Thanks MitelGuy,
I will check the D-channel trace just in case the proper CallerID is sent after the initial q.931 setup message.
I will also try your suggestion of rerouting the call.
Thanks for your help!!

P.S. To piguligu: I got the PRI traces from the Cisco gateway, not the SX.

 

[piguligu]

Thank You Morgan22.

 

[TheMitelGuy]

Basically you need to delay the T1 conenction for a few mili-seconds for the switch to present the proper (desired) CallerID.

If it doesn't work, let me know and I will go back to the drawing board.

 

[Morgan22]

Hi there MitelGuy,

Your suggestion of going first to a Mitel phone and then Forward NA to a Cisco phone works great! I also tried the permanent forward but it did not work. Only the busy/no_answer works and we get external Caller_ID on the Cisco IP phones instead of that "Voice Mail" tag.

Although this test works, I can't see how I can use this as a solution. The NA delay is too long to be practical. Also we would need to dedicate a Mitel phone for every Cisco phone out there (around 50).

I feel you are right about a timing issue. Let me know if you have other ideas I could try.

Thanks,

 

[TheMitelGuy]

Let me think about this. I will get back in short order. I've got a lot testing going on with new products right now, but will keep this on my mind while I work.

Make sure you rank this post!

 

[Morgan22]

BTW, solution was found a while back. The option in the Mitel required to forward Caller ID is called "DISPLAY HELD CALL ID ON TRANSFER".

Nice to know!