I'm aware that pots dial-peers strip the qualified digits from a destination pattern. For example, a pots dial-peer with 'destination-pattern 9T' would strip the leading 9 automatically. Therefore, if I were to call 912345, the result call would be to 12345.
So far so good.
I recently need to match only a particular dial-peer for a given caller so I implemented a translation profile on the ephone-dn for the call that translated the called number from 12345 to CC12345. Note that 'CC' are defined as valid dtmf digits; DTMF being from 0-9,*,#, A-D, Flash. I then created an outbound pots dial-peer with destination-pattern CCT so as to match this call. The dial-peer matched just fine, the only problem was that the 'CC' was not stripped! I had to apply another translation profile on this outbound pots dial-peer so as to strip 'CC'.
My question therefore is why do pots dial-peers strip normal numbers '0-9' but not 'A-D'?
P.S. I'm aware that the above can be accomplished in other ways such as cor-list. My question is soley in relation to digit stripping on pots dial-peers.