NEC IPK II and Cisco CME -- Incoming Caller ID Issues

Unanswered Question
Nov 19th, 2009

I'm hoping that one of the more knowledgable gurus here will have encountered the same or similar issue and can provide some insight on how to resolve a Caller ID issue I'm having between a SIP integration I have between my NEC IPK II system and my Cisco CME/CUE implementation on a 2821 IS Router.


Here's the situation... during the initial call invites, the Cisco system is sending the following invite:


/* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:10.0pt; font-family:"Calibri","sans-serif";}

Cisco to NEC

From:    "In-Patient 1"<sip:[email protected]>

To:          <sip:[email protected]>


The call goes through and the caller ID is correct. Unfortunately, the reverse is not true as the NEC system shows:

NEC to Cisco

From:    "233"<sip:[email protected]>

To:          <sip:[email protected]>


The issue here is that the NEC system is inappropriately sending the Display Name field as the extension and the URI field is the primary 10-digit number for the business. The result is that the Cisco side shows the extension and the main number but no caller ID name, and worse, attempting to redial calls the main number instead of the extension.


Now if someone has worked with this integration and knows the proper solution, I'm all ears, but my investigation so far has revealed that it's a problem on the NEC side that can't be resolved, so my question is... is there a way that I can teach the Cisco system to interpret the caller ID as always being the Display Name for both values? If I can at least make it so the extension can be redialed, I would be content until I get away from the NEC system completely.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
muranskycotech Wed, 11/25/2009 - 03:37

Bump... in hopes that I can get lucky that someone has experienced this type of issue.

Actions

This Discussion