After think and think and think, about called numbers, E.164 format with the + prefix is used for external destinations. Therefore, called-number normalization is the result of globalization.
Now, Internal DNs are used for internal destinations. Normalization is achieved by stripping or translating the called number to internally used DNs.
■ External to internal:
■ Calling-party number: E.164
■ Called-party number: Directory number
■ External to external (if applicable):
■ Calling-party number: E.164
■ Called-party number: E.164
■ Internal to internal:
■ Calling-party number: Directory number
■ Called-party number: Directory number
■ Internal to external:
■ Calling-party number: E.164
■ Called-party number: E.164
While both A and C are correct, however the question is asking "how is it being normalize"
a good example will be assuming on cucm line/extensions you are using a 11 digit E164 format with +1 but the PSTN for incoming digit they are forwading you 10 digit, you will have to normalize the number by perfoming translation rules
voice translation-rule 1
rule 1 /[0-9].........$/ /+1\0/
So A is the most correct answer.
Answer is A - like devadarshan91730 mentioned
Normalized called-party numbers: E.164 format with the +prefix is used for external destination. Therefore, called-number normalization is the result of globalization. Internal directory numbers are used for internal destinations. Normalization is achieved by stripping or translating the called numbers to internally used directory numbers.
The answer A says "stripping or translating the called numbers to internally used directory numbers" is closer to Localization than Globalization, so I would not be so sure that is the correct answer. Furthermore, prefixing of the number with "+" is called the globalized format of an E.164 number and is defined in the Internet Engineering Task Force RFC 2806. The best practice, the incoming call must be globalized, next routed and finally Localized. Now, E.164 must be normalized to +E.164 on a globalized environment, for example, from a ISDN BRI, you do no need to prefix 011 for international call, just you can dial the E.164 format without access codes, and setting the TON to International but it is not globalization, so D can not be correct neither. If it were up to me, I would rather to choose C instead A.
Well, I think I am changing my mind. Another think I would like to comment that E.164 number, in order to ITU-T E.164, is a external called-party number (without "+").
If it is a External incoming call (from GW), calling- and called-party numbers are usually provided in localized E.164 format. If Called-party number is internal, A. could be the best answer. If Called-party number is external (offnet to offnet call), C. could be the best answer.
If it is a Internal Outgoing Call (from internal IP phone DN) to external Called-Party number change the called number to +E.164 format if any other format was used (according to local dial rules, enterprise access codes, etc.) and this case, the best answer could be C.
In order of all of above, the closest answer would be A because it has a more specific scenario (PSTN Gateway to Internal DN). And C. is more general. So finally I prefer A.
Normalized called-party numbers: E.164 format with the +prefix is used for external destination. Therefore, called-number normalization is the result of globalization. Internal directory numbers are used for internal destinations. Normalization is achieved by stripping or translating the called numbers to internally used directory numbers. So answer A
Answer should be (A),
How can we say (D: no normalization is required) ?. IP phones within an organization will have DN configured to reach internal users. If we do not normalize the called number, should we expect to configure all phones with a Global number instead of a normal DN ?
Because the question is not specifying if the called party number is external or internal, how we can be sure (speculation) that the called number is a 4 digit DN, even it could has implementations where DN's are in E.164 format. The question just says there is a E.164 called-party number, no anymore
about if we should expect DN's in global format, there are destination
DN whit aliases as enterprise alternate number or +E.164 alternate number using Global Dial
Plan Replication (GDPR) and Inter-cluster Lookup Service (ILS).
The question is no so easy enough.
I think the answer here is D, WE are asked about Called party numbers, so A is invalid as we would only strip or translate to internal if the call was inbound,
Actually, the answer could be A, if the question is referring to incoming call routing and the normalization of +e164 called party numbers to local DNs as per this document states
https://community.cisco.com/t5/collaboration-voice-and-video/basics-of-globalized-call-routing/ta-p/3121674. As usual, it all depends on what Cisco are looking for in this very vaguely phrased question
The think is that the question does not specify if the called-party number is external or internal. Furthermore, it could have deployments where DN's are in E.164 format and then it would be necessary to do normalization if the localized format is not equal to the E.164 format. So, I am not so sure about answer A, there is no mention in the question if the called number is just an internal 4 digits number, or external, or even the called DN is in E.164 format.
Now, returning at the first, of there is a called-party number, whether it be internal or external (no specified by the question), in E.164 format, it might not be necessary to normalize.
In the exam I could choose the answer D in order of my interpretation, it could be wrong or it could be right. If someone come up with another interpretation, It will be appreciated and I am looking forward to know more interpretations.
I think the answer is D, because called numbers are already in 164, as stated in question. And what I find in internet.
Number normalization
This term refers to the process of changing numbers to a well-defined, standardized (normalized) format. In this case, all external phone numbers are changed to +E.164 format (that is, the E.164 format with the plus [+] prefix).
Normalized called-party numbers: E.164 format with the +prefix is used for external destination. Therefore, called-number normalization is the result of globalization. Internal directory numbers are used for internal destinations. Normalization is achieved by stripping or translating the called numbers to internally used directory numbers.
Answer is A
If it is a globalized envirement, all number should be in E.164 format so no normalization is required.
upvoted 4 times
...
This section is not available anymore. Please use the main Exam Page.350-801 Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
G0y0
2 months agoiExpo_91
7 months, 1 week agoDaKenjee
11 months, 3 weeks agoG0y0
1 year, 5 months agoG0y0
1 year, 5 months agobasscov
2 years, 2 months agoKomy
2 years, 4 months agoG0y0
1 year, 5 months agoG0y0
1 year, 5 months agodevadarshan91730
2 years, 4 months agosomedudebob
2 years, 6 months agoCiscoCUCMKing
2 years, 9 months agoCiscoCUCMKing
2 years, 9 months agoG0y0
1 year, 5 months agovirtu
2 years, 9 months agoMo_G
2 years, 10 months agoBotikus
2 years, 10 months ago