In Network routing truncates digits needed for call back to correctly routed company location

[ekaminsky]

When users call within their company to their co-worker at a different company location, they dial the 2 digit prefix for that location (10, 20, 30, etc.) followed by the 3 digit extension. However if they want to call an extension within their location they dial the 3 digit extension only. Within the location, this works fine for generating a returnable call back number (the 3 digit ext.). But when they call another location 10xxx, the caller id is only showing the 3 digit extension not the 5 digit to call the number back. The CUCM is only showing up as a 3 digit instead of the 5 needed for inter-site calls within their org.

What is the easiest way to setup calls to show the 5 digit caller id string (2 digit prefix + 3 digit extension)?

(In location will only be using the 3 digit)

[Chris Deren]

Sounds like you have partitioned dial plan where each location has DNs in local partition. Never a good design, and for the life of me I don't understand why people ever deployed this method.  

The best solution is to convert your DNs to be in common partition and be defined as 5 digits 10XXX, etc. and have site specific CSSes that allow 3 vs. 5 digit dialing via translations that prefix digits instead of stripping.  

If this is not what you want your only option is to route all calls between locations and use calling party transformations to adjust the CLID.