[cisco-voip] DID Best Practice

[Anthony Holloway]

This is just my opinion, but the best way is the way that makes sense for
your environment, and is easy to manage or troubleshoot.  The num-exp
command on a voice gateway is an option, and so would voice translation
rules.  I don't see how setting up Route Points in CUCM would be a good
choice, though, I have come in behind another Cisco Partner, and saw that
they did this.  It was basically, one 10 digit DN on an RP for every DID,
and it just CFA to another 4 digit DN on a Phone.  That was their method of
converting from 10 digits to 4 digits.  Is that easy to manage?  Does it
scale well?  Is that a good use of your finite CUCM resources?  To me, I
would say no, but at the end of the day, it does work, and users are only
slightly annoyed that all of their calls say "Forwarded for...".

Personally, I like to keep all of my digit manipulations in the CUCM dial
plan when possible.  Usually with the use of either translation or
transformation patterns.

Alternatively, and this might get controversial, but you should look into
+E.164 ("plus e one sixty four") number formats, as it makes your life a
lot easier to grow into your numbering plan and make very specific
decisions about your routing/manipulations.  PSTN SIP Trunking providers
(aka ITSPs) are sending you, and allow you to send them, in this format.
Do know when to use it though.  When all you have is a hammer, everything
looks like a nail.

--- Excerpt ---

*Endpoint Addressing*

*Each endpoint registered with the enterprise call control must have a
unique numeric address. Endpoint addresses in*
*Cisco Unified CM are equivalent to the directory numbers provisioned on
the lines of the endpoints. Use fully qualified*
*PSTN numbers (E.164 numbers) with a leading “+” as endpoint addresses.
This format is typically referred to as +E.164*
*format. The benefits of using +E.164 endpoint addresses include:*

   -
*Wide use in voice networks *
   -
*No need to develop and maintain an enterprise numbering scheme *
   -
*Easy creation of correct caller ID presentation for all on-cluster and
   off-cluster call flows *
   -
*Easy implementation of directory lookups *
   - *Simplified alternate routing to the PSTN in cases of WAN failure or
   bandwidth constraints *

Source: Cisco Preferred Architecture for Midmarket Collaboration 11.x
Design Overview
<http://www.cisco.com/c/dam/en/us/td/docs/solutions/PA/midmarket/11x/mmclb11x.pdf>

Find more design guidance here: Design Zone for Collaboration
<http://www.cisco.com/c/en/us/solutions/enterprise/design-zone-collaboration/index.html>

On Thu, Jan 14, 2016 at 7:19 AM, David Zhars <dzhars at gmail.com> wrote:

> What is the best way to route DIDs?  I see some setup on 2801s with
>
> num-exp DID# INTERNAL_EXT#
>
> They always seem to work, but someone told me the preferred way is through
> CM, apparently setting up a route point.
>
> Thoughts?
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160114/23acc2bd/attachment.html>