Can anyone provide direction on integrating Call manager with a Nortel Meridian PBX such that name display works when making calls between handsets connected to each system?
Try the follow:
Your gateway must be configured as QSIG as wel as your Nortel PBX.
Then in CCM you have to activate IE Delivery in system parameters.
If you do debug isdn q931 in your gw you should see the names beeing delivered.
Actually, CallManager can't decode the Facility IE that QSIG uses to deliver name information. CallManager sends a Display IE with name information, and that is what it can decode as well.
Use SL100 or DMS100 on the Nortel. Configure the Cisco as DMS100. If using an IOS gateway, use 12.2(5a). Remember to check the "Display IE Delivery" checkbox on the gateway configuration in CallManager.
Dave, I'm doing this same thing but with a Lucent Definity G3. What signalling do you recommend for proper name display?
thanks for the info - we can't use DMS100 because the router and switch can only be configured as talking to a network i.e. as a user end. In order for this to work we would need the router to emulate a DMS100 network side.
Based on this info, has anyone, anyway succeeded in getting name display to work between a Cisco CCM phone and a Nortel Meridian handset (specifically!)
Please, you can explain to me since you made to visualize the name between Nortel PABX and CallManager.
I am making this configuacion but I do not have positive results.
You can use SL100 network-side on the PBX, which is basically the same thing. Then configure the router as dms100 user side, and on the D channel serial interface, configure isdn flip-chan-bit and it should work.
I am able to send Display IE , but only send. PBX (Nortel Meridian 1) ignore this message. I am using net5, I am not able to use DMS100 because both sides support only user side, not network side.
On debug, there is no IE names going from PBX. I dont know how to configure PBX to send IE in the same format. SE from KAPSCH told me that only Qsig is able to carry names over trunk. I tried Qsig but with the same results.
Is there anybody who have this config running, or it is really possible to send name massages over trunk between Cisco and Nortel PBX?
Any helps are appreciated
We do have the name display working. Dave's configuration postings are correct. There was an additional option to set on the PBX to get it to send the display name. Under the D channel setup there is an option for RCAP. That needs to be set to DN2
that's certainly good news. Can you let me know the exact model and s/w versions you are using for the routers, ccm's and PBX's - want to make sure we are comparing like for like.
You bet.. We have a vg200 running version 12.2(6a) using H.323.
CCM version 3.1.2c
The PBX is a Nortel Meridian Option 81c running generic 2611 release 2319 The trunk card is qpc720f.
Hope this helps
based on your help I am able to see "names" in call setup from both sides.
But call setup is not complete and is followed by
Cause i=0x81e4 - Invalid information element contents.
It looks like wrong signalling error between SL100 and DSM100. Please could you help me with detail config. On Cisco site I specified only ISDN switch type DMS100.
I am running on C2650 IOS 12.2(6a) and on PBX there is Meridian 1-Option11c,Release 23.47 Kapsch PH1.
One more note:
What does it mean command "isdn flip-chan-bit". I didnt find any reference or explenation. I am not able to type-in this command.
Here is the config on the serial interface.
no ip address
no logging event link-status
isdn switch-type primary-dms100
isdn incoming-voice voice
no cdp enable
Are the people that are successfully doing this using public or private ISDN on the Nortel. I have public only and was told I needed to upgrade to private in order to make this work.
Are you using public or private ISDN networking on your Nortel? I'm told that mine will not work because I only have public. Thanks!
we are also using a Lucent Definity PBX and primary-net5 signaling.Is there a possibility that we could pass the name display over the Lucent phones? We use a 3660 gw.
I haven't tried primary-net5 signaling with a Definity G3 PBX before to see if name display works or not. It definitely works using other types such as dms100 or ni. You might want to look at debug isdn q931 on the router for an inbound and outbound call, and look at the SETUP messages to see if you see something like "Display i = 'Yanna'"
I am trying to set up a WSX6608 E-1 with a Nortel Meridian. Has anyone got a working config for the Meridian as our British Telecom engineers have hit a brick wall. Layers 1 & 2 come up and the trace from the D channel just shows continuous restarts and status messages in the CCM log. CCM 3.1c on 7835, WSX6608 E1 in Catalyst 6500. Have not got the card details from the Meridian but think this a software config problem not hardware. CCM set to Euro ISDN, Network side but with clock coming from Meridian.
I don't know if this will help but I just got it working on our system with the same set up in North America. I had to use DMS-100 signalling on the D-channels with the Nortel PBX set to user side and the Call Manager as the network side. The trick was to reverse your clocks, set the clock to come from the Call Manager.
We have been working with Cisco account groups / engineering in the UK to design and gain IVT certification for an off the shelf module for an integration platform we have out in the field already called Abridge. The module is known as the Legacy PBX gateway. This is designed to provide feature rich supplementary services including Name Display, Network Ring again, Message Waiting and some operator services. It is a hardware / software solution which runs on a Windows 2000 server and connects to a 2MB E1 trunk for the PBX and presents as an H323 gateway on the Call Manager side. Email me for more information or if you would like to trial at mailto:email@example.com or check out www.checkmate.com/cisco. Dominic.
We had an MGCP gateway connected to a Nortel Option 81 PBX working well. I had to convert the gateway from MGCP to SIP and when I did calls coming into the gateway from the PBX were being rejected by my gateway with a cause of:
Cause i = 0x81E4 - Invalid information element contents
I added the "isdn flip-chan-flag" command to my serial interface (since replaced with the "isdn channel-id invert extended-bit " command) and it started working perfectly. Found that command in this post and thought I'd add my experience so hopefully it will help someone else in the future!