NEC IPK II and Cisco CME -- Incoming Caller ID Issues
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:
Cisco to NEC
From: "In-Patient 1"<sip:email@example.com>
The call goes through and the caller ID is correct. Unfortunately, the reverse is not true as the NEC system shows:
NEC to Cisco
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.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...