RickMc0025
IS-IT--Management
How Do I set up CDP for an extension that exsist at one location and I need it to be available at two other locations.
Thanks
Thanks
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
CDP Coordinate Dialing Plan
- Thread starter RickMc0025
- Start date
- Status
You will have to assign a steering code that is similar and convert with dmi tables. JP is right abt not duplicating same to different locations. We use LOC codes followed by ext dn so that same dn can exist in each switch but be reached by dialing loc x then station dn. You can also make cdp code a unique 1-2 digit number for each site, then dial whatever to other end. May upset some but only way to maintain a networked system and not have dialing conflicts.
- Thread starter
- #4
zog99
Technical User
- Feb 26, 2005
- 105
here are my notes on CDP.. they may help
A Co-ordinated Dialling Plan (CDP) identifies a string of digits (steering code), up to seven in length, and routes calls according to the rules programmed against this feature.
The Overlays used to set up a CDP are 86 and 87.
86 sets up the route selection and any digit manipulation required.
87 sets up the actual steering code and points to a specific route selection data block.
Take for example a situation where, a business has 2 Meridians with a network link connecting them, the route number on both switches is 100, extensions on Meridian A wish to call extensions on Meridian B,
Meridian A has extensions 2000 - 2999 and Meridian B also has extensions 2000 - 2999.
A CDP can be set up on both Meridians and extension users would be required to dial this followed be the extension number on the distant Meridian.
In this case extensions users would be instructed to dial 7 to connect to the extensions on the network.
Firstly a Digit Manipulation Table would be required as set out below:-
LD 86
REQ NEW
CUST xx
FEAT DGT (Digit manipulation data block)
DMI xxx (Digit Manipulation table index number, check other DGT table numbers and choose a unique one)
DEL 1 (in this case delete the first digit 7, the option can be anything between 0 and 15)
INST 0 (in this case no digits require inserting as the extension number is all that is required but up to 20 . digits can be inserted)
Once the DGT is created then a Route List Block (RLB) can be set up, this is the data block necessary to control which route the calls are carried over and any time of day barring or digit manipulation can be applied here.
Again in LD 86
REQ NEW
CUST xx
FEAT RLB (Route list block)
RLI xx (Route list index number, check all present tables and choose a unique number)
ENTR xx (Routing option, start with first choice 0 and graduate up to a possible 63)
ROUT xx (enter the route number of the link in this case 100)
TOD xx (time of day barring on the chosen route can be applied here, please refer to the manual if this is required)
DMI xx (Digit manipulation table number, in this case use the one allocated to the DGT table above)
After carriage returning through several prompts you will be presented with ENTR again, at this point it is possible to programme a 2nd choice route for the calls, if this is not required just carriage return through to the REQ prompt.
It is now possible to create the CDP
LD 87
REQ NEW
CUST xx
FEAT CDP (Co-ordinated dialling plan)
TYPE DSC (Distant steering code)
DSP DN (this is the display option to the destination set, DN is the preferred option but there are other options see manual for other choices)
RLI xx (enter the RLI created above)
FLEN xx (expected dialled digits, in this case 5, as the call does not need to start routing until all the digits are dialled)
carriage return through to the REQ prompt, now extension users can dial the other Meridians extensions just by prefixing the extension number with 7.
A Co-ordinated Dialling Plan (CDP) identifies a string of digits (steering code), up to seven in length, and routes calls according to the rules programmed against this feature.
The Overlays used to set up a CDP are 86 and 87.
86 sets up the route selection and any digit manipulation required.
87 sets up the actual steering code and points to a specific route selection data block.
Take for example a situation where, a business has 2 Meridians with a network link connecting them, the route number on both switches is 100, extensions on Meridian A wish to call extensions on Meridian B,
Meridian A has extensions 2000 - 2999 and Meridian B also has extensions 2000 - 2999.
A CDP can be set up on both Meridians and extension users would be required to dial this followed be the extension number on the distant Meridian.
In this case extensions users would be instructed to dial 7 to connect to the extensions on the network.
Firstly a Digit Manipulation Table would be required as set out below:-
LD 86
REQ NEW
CUST xx
FEAT DGT (Digit manipulation data block)
DMI xxx (Digit Manipulation table index number, check other DGT table numbers and choose a unique one)
DEL 1 (in this case delete the first digit 7, the option can be anything between 0 and 15)
INST 0 (in this case no digits require inserting as the extension number is all that is required but up to 20 . digits can be inserted)
Once the DGT is created then a Route List Block (RLB) can be set up, this is the data block necessary to control which route the calls are carried over and any time of day barring or digit manipulation can be applied here.
Again in LD 86
REQ NEW
CUST xx
FEAT RLB (Route list block)
RLI xx (Route list index number, check all present tables and choose a unique number)
ENTR xx (Routing option, start with first choice 0 and graduate up to a possible 63)
ROUT xx (enter the route number of the link in this case 100)
TOD xx (time of day barring on the chosen route can be applied here, please refer to the manual if this is required)
DMI xx (Digit manipulation table number, in this case use the one allocated to the DGT table above)
After carriage returning through several prompts you will be presented with ENTR again, at this point it is possible to programme a 2nd choice route for the calls, if this is not required just carriage return through to the REQ prompt.
It is now possible to create the CDP
LD 87
REQ NEW
CUST xx
FEAT CDP (Co-ordinated dialling plan)
TYPE DSC (Distant steering code)
DSP DN (this is the display option to the destination set, DN is the preferred option but there are other options see manual for other choices)
RLI xx (enter the RLI created above)
FLEN xx (expected dialled digits, in this case 5, as the call does not need to start routing until all the digits are dialled)
carriage return through to the REQ prompt, now extension users can dial the other Meridians extensions just by prefixing the extension number with 7.
You said Be available at two locations, do you mean dialable from two locations? If so that is possible baring the proper routing is in place. Example is for 2xxx working at site a
Build phone in site a for ext.
log into site b and look for tie programing between site a and b
create cdp in site b with ext # that points to site a
Now log into site c and look for routing to site b
create cdp in site c to point to site b
All of this will allow dialing between all 3 sites, but phone in one location.
Build phone in site a for ext.
log into site b and look for tie programing between site a and b
create cdp in site b with ext # that points to site a
Now log into site c and look for routing to site b
create cdp in site c to point to site b
All of this will allow dialing between all 3 sites, but phone in one location.
- Status
Similar threads
- Locked
- Question
- Locked
- Question