The closest thing to an example that exists is the E.164 dial plan is documented in the UCM SRND Dial Plan chapter. There is also a session on this at Cisco Live if you are attending in person or virtually. It takes a lot of work to understand how all of the pieces interact as well as the impact to other UC applications. At an extremely high level:

• Incoming calls use the Incoming Called Party Transformation CSS (UCM 7.1+ only) of the inbound trunk to globalize the number. Prior to 7.1 you did not have a CSS option here which is difficult with SIP Trunks since they do not have the ISDN TON feature.
  
• (Optionally) this can be localized again on the user's phone using the Incoming Calling Party Transformation CSS on the device. I prefer not to do this if the customer is receptive to seeing ANI displayed globally.
  
• Outbound calls are globalized through translation patterns in the device-level CSS of the device. UCM performs all routing in global form only after it is translated.
• Outbound calls are localized using the Outbound Called and Calling Party Transformation CSSes on the trunk.

Be sure you know the difference between transformation (modify existing call) and translation (new call). They cannot be used interchangably.

The main hurdle is that Cisco never provides a finished product example. The SRND will give you isolated examples; however, they don't fit together into any working final design. I would strongly suggest working with a partner who has gone through this and actually understands all of the details involved. On your own it will take several attempts and at least 100 hours before you have this all figured out and understand all of the details [gotchas].