Which two configuration changes can correct this issue?

Refer to the exhibit. IT shows an H.323 gateway configuration in a Cisco Unified Communications Manager environment. An inbound PSTN call to this H.323 gateway fails to connect to IP phone extension 2001. The PSTN user hears a reorder tone. Debug isdn q931 on the H.323 gateway shows the correct called-party number as 5015552001.

300-075-implementing-cisco-ip-telephony-and-video-part-2-ciptv2_img_084
Which two configuration changes can correct this issue? (Choose two.)
A. Add port 1/0:23 to dial-peer voice 123 pots.
B. Ensure that the Significant Digits for inbound calls on the H.323 gateway configuration is 4.
C. Add a voice translation profile to truncate the number from 10 digits to 4 digits. Apply the voice translation profile to the Voice-port. The configuration field “Significant Digits for inbound calls” is left at default (All).
D. Add the command h323-gateway voip id on interface vlan120.
E. Change the destination-pattern on the dial-peer voice 23000 VoIP to 501501? and change the Significant Digits for inbound calls to 4.

cisco-exams

4 thoughts on “Which two configuration changes can correct this issue?

  1. The destination pattern on voip dial-peer should be 5015552001 not 2… And Ensure that the Significant Digits for inbound calls on the H.323 gateway configuration is 4.

    Although answer B does not give a complete solution, it seems more assertive than C; Setting the significant digits to four on a PSTN gateway instructs CUCM to ignore all but the last four digits of the called party number for routing incoming gateway or trunk calls.

  2. I would rather say it answer is “C” and “E” because the question asks for two changes where each can correct the problem.
    Answer B alone would not correct the problem, because without the adaption of the destination pattern, as outline in answer E, the incoming number 5015552001 will not match the voip dial-peer.
    Supporting documentation for answer C
    https://www.cisco.com/c/en/us/support/docs/voice/call-routing-dial-plans/64020-number-voice-translation-profiles.html#con7

  3. Should be A. You need to specify the port under the dial-peer.
    And E. The destination pattern on voip dial-peer should be 5015552001 not 2…

    1. So, dial-peer 123 pots, it does NOT need a port designation. That would be because it is an incoming dial-peer. What you DO need is some significant digits to something like, incoming called-number ….
      Altogether, it would need to look something like

      dial-peer voice 123 pots
      incoming called-number ….
      direct-inward-dial

Leave a Reply

Your email address will not be published. Required fields are marked *


The reCAPTCHA verification period has expired. Please reload the page.