GuardguyMO
Technical User
I have a mixed system with a Nortel 81c (4-digit numbers and all the DID's) and a Cisco Call Manager (5-digit numbers and no DID's).
I have an existing 500 block of DID's that belongs to the Nortel. I am in the process of converting all 800 (a mix of DID's and extensions) of my existing phones over to the Cisco. I plan on this taking several months to accomplish. I have already converted a few offices that only have extensions with no problems.
As I convert an office to the new phones that has a DID, I am making a translation in the PBX for that DID to be converted to a 5-digit number that gets pushed to the Cisco gateway. (Currently all numbers that begin with a 3 are sent to the Cisco Gateway.)
To make this less painful on the users I am simply adding a 3 to their existing 4-digit extension to make it a Cisco 5-digit number.
(DID 9xxx is now 39xxx, EXT 7xxx is now 37xxx)
The problem happened when I converted a couple of the DID numbers (I have only done two so far). I am doing this by outting the phone 9xxx in the PBX and then making a new DSC of the same 9xxx number. I also made a DMI to drop the first digit and insert 39 so as to convert the 4-digit number in the PBX to a 5-digit number that now starts with 3 to send it to the Cisco and can be programmed as a key on a Cisco phone. This DMI is only for the DID 9xxx numbers.
One thing that may need to be considered is that until everyone gets the new phones, people will continue to call the 9xxx number and the 39xxx number when trying to make station to station calls for anyone that had a DID. It won't be an issue when someone try's to dial extensions such as 7xxx as this number will no longer exist in the PBX.
All numbers that go to the Cisco point to Route 21. I also created RLI 33 to use the new DMI.
Here is an example on the PBX:
ERR5132 0 21 21 33 39652
This is what ERR5132 means:
ERR5132 data
For a tandem CDP DSC call, the incoming route and outgoing route belong to the same Route List Index (RLI). To avoid potential looping problems, the CDP DSC database may need to be modified.
The output data is: customer number, incoming route, outgoing route, outgoing route list index, outpulsed digits.
Is this something to be concerned with? I have made several test calls and we only get the ERR code occasionally. We have not yet narrowed down what seems to trigger it. The error code mentions the CDP DSC database may need to be modified. What modifications would that be?
On a final note I am not very well versed in BARS and NARS programming.
I have an existing 500 block of DID's that belongs to the Nortel. I am in the process of converting all 800 (a mix of DID's and extensions) of my existing phones over to the Cisco. I plan on this taking several months to accomplish. I have already converted a few offices that only have extensions with no problems.
As I convert an office to the new phones that has a DID, I am making a translation in the PBX for that DID to be converted to a 5-digit number that gets pushed to the Cisco gateway. (Currently all numbers that begin with a 3 are sent to the Cisco Gateway.)
To make this less painful on the users I am simply adding a 3 to their existing 4-digit extension to make it a Cisco 5-digit number.
(DID 9xxx is now 39xxx, EXT 7xxx is now 37xxx)
The problem happened when I converted a couple of the DID numbers (I have only done two so far). I am doing this by outting the phone 9xxx in the PBX and then making a new DSC of the same 9xxx number. I also made a DMI to drop the first digit and insert 39 so as to convert the 4-digit number in the PBX to a 5-digit number that now starts with 3 to send it to the Cisco and can be programmed as a key on a Cisco phone. This DMI is only for the DID 9xxx numbers.
One thing that may need to be considered is that until everyone gets the new phones, people will continue to call the 9xxx number and the 39xxx number when trying to make station to station calls for anyone that had a DID. It won't be an issue when someone try's to dial extensions such as 7xxx as this number will no longer exist in the PBX.
All numbers that go to the Cisco point to Route 21. I also created RLI 33 to use the new DMI.
Here is an example on the PBX:
ERR5132 0 21 21 33 39652
This is what ERR5132 means:
ERR5132 data
For a tandem CDP DSC call, the incoming route and outgoing route belong to the same Route List Index (RLI). To avoid potential looping problems, the CDP DSC database may need to be modified.
The output data is: customer number, incoming route, outgoing route, outgoing route list index, outpulsed digits.
Is this something to be concerned with? I have made several test calls and we only get the ERR code occasionally. We have not yet narrowed down what seems to trigger it. The error code mentions the CDP DSC database may need to be modified. What modifications would that be?
On a final note I am not very well versed in BARS and NARS programming.