Num-exp vs translation profiles vs dial-peer

Question

Hi friends,
This topic has been discussed many times still I couldn't find any relevant answer for the same and even configuration sometimes give unseen results.
As far as I know, following techniques exist in router for digit manipulation;
1. Number expansion
Applied globally
2. Translation profile
Applied on dial peer or PoTS interface or Controller or VoIP globally
3. Various commands found under dial peer like forward, prefix, strip digits etc.
Having all information available, I understand it fair well about independent working of all of the above techniques. But when it comes to apply all of the above techniques together, then it becomes complex which techniques apply in what order and hence not very clear to configure. I found lot of discussions on this topic and also found that Cisco has lot of contradictory information about the same in it's documents.
Will appreciate if someone can let me know in exactly which order above techniques are checked in router for both inbound and outbound call?

Answer 1

Hi Chris,
Thanks for your time.
It's getting conflicted with what Cisco stuff says;
Following is the priority for inbound VoIP dial-peer as per Cisco stuff;
Priority 1: Global voice translation profile (applicable only for incoming call)
Priority 2: Number Expansion
Priority 3: Inbound Dial Peer Selection
Priority 4: Voice Translation Profile under Dial-Peer (I skipped CLID here purposefully)
Same is applicable for PoTS inbound call where stuff says that voice translation profile applied to PoTS interface has more priority than number expansion.
I'm comfortable with digit manipulation applied during outbound call but for incoming call, it's still not clear. What do you suggest for the above priorities? 
Tomorrow I'll also try to put my hands on doing some test configuration to actually check during inbound voip call, global translation profile has more priority or number expansion?
Thanks
Vivek