Here it is in a nutshell (well a big nutshell anyway)
We have 2 Meridian phone systems within the same building (for redundancy purposes) an Option 81 and an Option 61
We recently changed PRI providers from one carrier to another and had to replace 10 PRI's (6 PRI's on the 81 and 4 PRI's on the 61)
By changing the carrier we also had to change the PRI configuration protocol from NI2 to DMS100...
I had our maintenance provider make the necessary changes to the programming on the Loops, DChannels, Protocols etc.
Ever since the carrier change when an inbound call comes across the PRI to the 81 and the call gets transferred to a user on the 61 the caller ID doesn't follow the call and only the route # comes on on the display screen.
Here is a printout of the DCH that the DID # comes in on...
ADAN DCH 33
CTYP MSDL
GRP 2
DNUM 5
PORT 1
DES
USR PRI
DCHL 75
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC D100
SIDE USR
CNEG 1
RLS ID 36
RCAP ND2
PRI INTERFACE ID
029 2
076 3
T200 3
T203 10
N200 3
N201 260
K 7
From what I've been told by our maintenance provider is that since our SW and release is no longer supported by AVAYA that there is nothing that they can do. They mentioned something about the NI2 protocol works...When a call comes from the CO to the Option 81 and gets transferred to the Option 61. The 81 acknowledges the original call and (if transferring the call to the 61) sends a request to the CO to keep sending the CLID. which is how it worked over the old carrier network when we were using NI2.
When we migrated to the new carriers netword we were advised that the protocol to use was DMS100 which is how we configured both PBX's to accommodate the 10 new PRI's.
As per the carrier they don't support NI2 protocol.
Is there any truth in this ?
What I don't understand is that DMS100 is a Nortel designed protocol and don't understand why it wouldn't work on a Nortel product.
Any help would be greatly appreciated.
We have 2 Meridian phone systems within the same building (for redundancy purposes) an Option 81 and an Option 61
We recently changed PRI providers from one carrier to another and had to replace 10 PRI's (6 PRI's on the 81 and 4 PRI's on the 61)
By changing the carrier we also had to change the PRI configuration protocol from NI2 to DMS100...
I had our maintenance provider make the necessary changes to the programming on the Loops, DChannels, Protocols etc.
Ever since the carrier change when an inbound call comes across the PRI to the 81 and the call gets transferred to a user on the 61 the caller ID doesn't follow the call and only the route # comes on on the display screen.
Here is a printout of the DCH that the DID # comes in on...
ADAN DCH 33
CTYP MSDL
GRP 2
DNUM 5
PORT 1
DES
USR PRI
DCHL 75
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC D100
SIDE USR
CNEG 1
RLS ID 36
RCAP ND2
PRI INTERFACE ID
029 2
076 3
T200 3
T203 10
N200 3
N201 260
K 7
From what I've been told by our maintenance provider is that since our SW and release is no longer supported by AVAYA that there is nothing that they can do. They mentioned something about the NI2 protocol works...When a call comes from the CO to the Option 81 and gets transferred to the Option 61. The 81 acknowledges the original call and (if transferring the call to the 61) sends a request to the CO to keep sending the CLID. which is how it worked over the old carrier network when we were using NI2.
When we migrated to the new carriers netword we were advised that the protocol to use was DMS100 which is how we configured both PBX's to accommodate the 10 new PRI's.
As per the carrier they don't support NI2 protocol.
Is there any truth in this ?
What I don't understand is that DMS100 is a Nortel designed protocol and don't understand why it wouldn't work on a Nortel product.
Any help would be greatly appreciated.