What ISDN switchtype are you using? After quite a lot of experimenting we ended up running NI2 protocol to our Nortel PBXs (61C & 81C). One limitation is that the Nortel sees NI2 as a PSTN protocol and will not allow inbound calls to tandem through and go out another PRI. I solved this by moving all the PSTN PRIs to the Call Manager. We have been running this setup troublefree for over a year.
We originally were set for D100 but continued to receive an invalid information element. Another reply stated that in D100 mode the gateway needs to be MGCP.
Then we tried DID/NI2 and ran into the same problem you mentioned. The PBX was unable to transfer DID's to an outbound trunk.
Currently we are set for 5E. The PBX was switching DID's to outbound trunks on an individual number basis. But when we used the wild card masks on the PBX to forward a range of DID's out the outbound trunk it does not work for calls coming in from the telco. But calls originating within the PBX route out to the Cisco gateway fine.
Another symptom that has appeared is that I now have a severe delay in my ring back indication.
I just helped someone doing this w/TACs help and Nortels help and heres what we needed to do.
We had to use DMS100 switchtype to Cisco gateway since as other gentleman stated 61c can't do NI2 to NI2. The nortel folks involved in job I was on said that the 61c could do user-side for DMS100 switch type and needed to see a DMS100 interface identifier of 0.
There isn't a way to set the DMS100 interface identifier in IOS that I could find and TAC also said it wasn't possible. But if the gateway is a MGCP gateway then in Call manager MGCP gateway config you can configure the port with DMS100, configure the interface identifier, and set it to emulate network. This works.
The problem we had was for SRST fallback, we can't use PRI to 61c because of the IOS issue not able to set the DMS100 interface identifer to 0. The 61c needs to see this in the SETUP message.
If anyone knows a way in IOS to get the interfacee identifer of 0 in ISDN SETUP messages w/DMS100 switchtype that would be great.
Thanks for the reply. My latest configuration is using 5E switch type. This works when we map a single DID to be switched from the PSTN to the Cisco gateway. But when we use the wild card to match a range of DID's to be switched to the Cisco gateway it stops working.
I really needed to provide SRST but may have to switch to MGCP.
My callmanager with a 3640 is currently running in conjunction with our Opt 61c here in the office. I have the PRI set up as d100 on the Nortel side and DMS100 on the Cisco side. I have had to add one command to make everything line up correctly. try the following and see if it works for you.
add this to your d-channel interface (eg. serial 1/0:23)
If you let me know I will try and print up the configurations for both devices for you to look at.
OK .. This is what I currently have setup between my 61c and my 3640 MGCP gateway. I am not very knowledgeable on the 61c side of the house, I leave that up to the others in my group.
This should also work on the Option11, as they are both the same thing. Just a different size
I hope this helps.
Adam's config is the only one I've seen work consistently. What works consistently for M1s, and has been implemented numerous times with success, is the following:
On the IOS gateway:
isdn switch-type primary-dms100
controller T1 1/0
clock source line primary
pri-group timeslots 1-24
isdn switch-type primary-dms100
isdn incoming-voice voice
!If on earlier version of IOS (12.1.x) also use
!isdn tei-negotiation first-call
Nortel Meridian Option X
1) Meridian 81c using NI2 Network side will only process the last 4-5 digits of any number, so tandeming to the PSTN is not possible (in fact, if the last 4-5 digits of the number sent out match a PBX phone extension that phone will ring).
2) Set Meridian PRI to S100 Network side if software allows. Successful integrations seem to be running version 22 or later on the Meridian.
3) Must set "S100" on the trunk group (RDB) and on the D-channel config. They can then set the PBX for network side.
4) Set VoIP Gateway for DMS100 User side. Caller name should work with IOS 12.2(5)+
5) Make sure PBX tech downloads MSDL channel if D channel does not come up. IMPORTANT!
6) PBX tech will also have to make sure correct parameters are set to pass calls from his PRI to CallManager to PRI on PSTN (NCOS, TGAR, others)
IOS info above can be replicated in CCM for MGCP gateways.
I'm not a Nortel M1 jockey, but good config information from the M1 that I've recorded is:
PARM RS422 DTE
RLS ID **
On a trunk (ds0)
NCOS 2 <<< Depends on permissions in switch
RTMB 79 1
TGAR 1 <<< Routing code. Could be different.
CLS CTD DTN and so on
On the trunk route:
NCRD NO <<<< set to yes on good config
DSEL 3VCE <<< also works as VOD
SRCH RRB <<< Can be set to LIN (linear hunt)
DCNO 0 *
and so on ......