如何根据内部目录号查找Cisco Call Manager对应的外部号码？

Hey Daniel, let’s break down how to pull the correct external masks directly from Cisco Call Manager (CUCM) without relying on that error-prone spreadsheet. Here are practical, actionable methods tied to the route plan reports and translation rules you’re already working with:

Since you’re already looking at route plan reports, this is the most straightforward approach:

• Navigate to Call Routing > Route Plan Report in the CUCM Admin interface.
• Use the filter options to narrow down results: you can set Pattern Usage to "External Mask" or search for the specific number range you’re creating DNs for.
• Locate the External Mask column in the report results—this value is the system’s currently active mask for that route pattern, and you can copy it directly into the External Mask field when creating new DNs.
• Pro tip: If the report is too lengthy, use the Export button in the top-right corner to save results as a CSV. This makes it easy to filter and search for specific number segments.

External masks are often tied to translation rules that adjust calling party IDs. Here’s how to map them:

1. Find the translation rule linked to your target route pattern:
   • Go to Call Routing > Route/Hunt > Route Pattern, open the relevant pattern, and check the Calling Party Transformation Mask field or the associated Translation Pattern.
2. Parse the rule to get the mask:
   • For example, if the transformation mask is 91XXXXXXXXXX, your external mask will typically follow this format (adjust for your dial plan—you might drop a prefix like 9 if it’s just an access code).
3. Verify with Dialed Number Analyzer (DNA):
   • Use CUCM’s Dialed Number Analyzer to simulate a call. The transformed calling party ID shown in the results is exactly what you should use for the External Mask.

If you’re creating dozens or hundreds of DNs, manual lookup is inefficient. Use CUCM’s AXL API to pull external masks programmatically:

• Example simplified SOAP request (adjust API version to match your CUCM deployment):

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/11.5">
   <soapenv:Header/>
   <soapenv:Body>
      <ns:listRoutePattern>
         <searchCriteria>
            <pattern>8XXX</pattern>
         </searchCriteria>
         <returnedTags>
            <externalMask/>
         </returnedTags>
      </ns:listRoutePattern>
   </soapenv:Body>
</soapenv:Envelope>

• This request returns all external masks for route patterns matching 8XXX—you can parse the response and batch-populate your new DNs with the correct values.

Quick note: Always test with a dummy DN first in a non-production environment. Make a test call to confirm the calling party ID displays as expected before rolling out to live DNs.

内容的提问来源于stack exchange，提问作者Daniel