Exam 350-801 topic 1 question 173 discussion

The answer is C -Ip Phone - For the inbound call flow, globalization is done at ingress in the sip trunk/ gateway and localization at egress in the phone level with a calling party transformation. https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab11/collab11/dialplan.html#16685

I would say the answer is "Gateway". Here is my reasoning: - Localization can be configured on Gateway and/or Device pool and/or phone level. - However, In SRND 12, Under (Phone calling party number Localization) , the below statement shows that Cisco recommends placing the configuration in device pool and not on the phone: "The Calling Party Transformation Pattern is placed in a partition included in the destination phone's Calling Party Transformation Pattern CSS, configured at the device-pool level." And because we do not have "device pool" as an available answer, i would go with "Gateway" because you can't just go to each and every single phone to apply config

The question seems to point at a single end user (not end users). Wouldn't this be enough to consider "IP Phone" the correct answer?

In the inboud configuration of the Gateway

D .gateway

I would say the answer is "Gateway". Here is my reasoning: - Localization can be configured on Gateway and/or Device pool and/or phone level. - However, In SRND 12, Under (Phone calling party number Localization) , the below statement shows that Cisco recommends placing the configuration in device pool and not on the phone: "The Calling Party Transformation Pattern is placed in a partition included in the destination phone's Calling Party Transformation Pattern CSS, configured at the device-pool level." And because we do not have "device pool" as an available answer, i would go with "Gateway" because you can't just go to each and every single phone to apply config

The answer is C, because the calling party transformation CSS can only be applied to an IP phone or a device pool. Device pool is not a given answer, so, the answer is IP Phone. The associated transformation pattern, however, can be applied directly on the device pool or the gateway. The question is asking where the configuration can be applied. The final configuration (CSS) "Configuration" can only be applied to the Device Pool or an IP Phone. Not the gateway. -

Answer is C - Komy, explained it, with SRND12 I searched and found a similar answer in SRND route pattern is wrong, directs from CUCM away service parameters, is possible -> service parameters to globalize calling party numbers on all devices clusterwide IP phone, is possible with calling party transformation CSS gateway, is possible by varios manipulations via CLI i stick with Answer C, because gateway is ealiest ingrees in this callflow: ITSP > Gateway > Callmanager > Phone SRND: Thus, the guiding principle is: Accept localized forms upon call ingress, and globalize them; route the call based on the globalized form; and localize the call to comply to the form required by the destination. https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab12/collab12/dialplan.html?bookSearch=true#48778

Answer is D. https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab11/collab11/dialplan.html#16685 The globalization of the calling party number should be implemented by using the Incoming Calling Party Settings configured either on the gateway directly or in the device pool controlling the gateway.

The question asks where a configuration is done. The configuration in question is a calling number: wouldn't that be simply a DN on an IP Phone? Is this explanation too simple?

Correct is C, localization of egress call make on ip phone, in the calling-party transformation patter that applicable to phone. Cisco`s digital learning and CLCRO cource says that

Answer: C Pre-transformation calling party numbers should be globalized and routable before modifying at phone: globalize on ingress (at gateway), localize on egress (at phone)

C. You cannot modify the called-party number during call egress (gateway), when a call is delivered to a phone by CUCM. Calling Party XFORM (\+1.!, Pre-Dot) is applied to phone Device pool via CSS and maintains full E.164 in missed/received call directory.

sorry forgot link: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/10_0_1/ccmfeat/CUCM_BK_F3AC1C0F_00_cucm-features-services-guide-100/CUCM_BK_F3AC1C0F_00_cucm-features-services-guide-100_chapter_01010.html

Check out this link, am I reading at step 12 that maybe both gateway and phone configuration is where you set the call routing transformation pattern? Would that mean both C and D could be correct? My gut tells me gateway, but... just a thought.

Core routing in the globalized dial plan approach is based on routing +E.164 patterns so that the native dialing habit for this dial plan approach is global +E.164 dialing. Unified CM's translation patterns are used to convert localized user input as dialed from phones, to the global +E.164 form used to route the calls within the Unified Communications system.

Not sure how can someone normalize numbers in IP phone. Gateway should be the correct answer