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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

CDP or UDP on a VOIP Network

Status
Not open for further replies.

BizFoneGuy

Technical User
Aug 14, 2005
123
CA
I'm networking several BCM's together and want to know which dialing plan CDP/UDP is better to implement and why? I have played around and managed to get the switches calling each other 3000 and 4000 extension numbers. Where I'm having problems it trying to allow for access to the PRI's at each end. I can access the analog lines using routing at each end, however it seems to be intermittent as you have to use 89# to get dialtone right way and then it works, but then last number redial doesn't. Dialing 89 seems to be intermittent based on whether you pause before dialing the rest of the number? I know the key is in routing but think it shouldn't be too complicated. I saw something suggesting that if the other end was 3000 DNs that you could simplify by having 3 and then 9 to access their trunks. So, CDP? UDP? any ideas or suggestions? Also will MCDN give you end to end source Caller ID with just BCM's in the network?
 
CDP is your best bet. UDP is usually reserved for integrating with Meridian's in a UDP/LOC dialing plan environment.

Do your IP trunks have access to the PRI via the remote access packages?
 
Currently I was just testing between 2 BCMs and a Nortel 4 port ip gateway using analog lines here in the shop. I can access the lines over the IP trunks but the routing mustn't be clean as dialing doesn't seem consistent and last number redial gives problems? Would like to see suggestion for routing for one end showing access to trunks in alternate switch, dn lenths, private/public etc. The IP trunks have access to the lines on the far end and it does work, but not stable/consistent. Can a CDP evolve into a UDP if it is later expanded or would it be a tear down?
 
If your Business Communications Manager is part of a private network, you have a choice of dialing plans. However, all Business Communications Managers on a network must use the same type of dialing plan and have the same Private DN lengths to ensure proper call direction. Plan out these settings before you start programming for the network.

• UDP plans use a routing code and a location code plus the set DN (i.e. 6-403-XXXX) to determine where a call gets routed. You specify a Private DN length to allow all required digits to be dialed. Each node on the network has a unique location code.

• CDP plans use a unique steering code that gets dialed as part of the set DN (i.e. 2XXXX for one node, 3XXXX for another node, and so on) to determine where the call
gets routed. Since each node on the network has a unique code, no other routing is required.

• The Meridian system administrator generates the Private Network IDs. These IDs are unique to each node on a network. Both UDP and CDP must include this code in programming.
 
Are you sending the "9" along with the remaining digits for PSTN calls? Probably will need to define your public DN lengths (prefix 9) for the proper number of digits. For 7 digit dialing over those trunks, set previx 9 for 8 digits. For full LD dialing, set prefix 91 for 12 digits.

CDP can evolve into UDP, but you'll most likely be rebuilding your dialing plan. Unly time I used UDP was when networking a BCM into an ESN dialing plan on a Meridian network
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top