The config below works like a charm. As far as I know it is the only config that works with Nortel Meridian 1s - the Meridians seem to be fairly picky about how they route different switch types. The main trick is to set the gateway up as switch type DMS 100, user side, and the Meridian 1 as switch type SL-100, network side.
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 VG200 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)
Here is some pertinent config info from a Meridian PBX that is
working with the above PRI
On the D-Channel:
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 <<< Per Customer should be UNR not CTD
I would like to know if you have come across these problems in a VG200 to Meridian T1 PRI link:
1. When the receptionist attached to the PBX transfers an external call to an IP phone linked via the T1 PRI link, the CLID that appears on the IP phone display is 'Attendant' instead of the original CLID.
2. The transfer is not clean. The receptionist has to press the 'release' key a couple of times before the call is transferred.
Not sure where in the PBX config this can be fixed...
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...