You have the right concept here, you can route the call to desired destination based on called number which is what "destination-pattern" does for you. One thing you need to consider is also the incoming dial-peer (which in your example is dial peer 201 as it has incoming called-number .) so for faxing to work properly you should apply fax settings (fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco) to this dial-peer as well unless you have it defined globally.
Yes, this means that routing is based only on 2 digits, which does not sound right (never seen 2 digits received from telco). Since the other dial-peer uses 4 digits you should change the dial-peer 201 to "destination-pattern ...."
To find out for sure perform debug on the gateway to see what telco send you, if this is a PRI circuit use "debug isdn q931", if SIP "debug ccsip messages", if POTS "debug voice ccapi inout".
Please provide the debugs, as I have never seen telco sending you only 2 digits, plus your other dial-peer matches on 4. Unless these arrive on different trunks it would be impossible to receive different digit lengths.
dial-peer voice 302 voip destination-pattern 99 session protocol sipv2 session target ipv4:FAXSERVERIP:5062 dtmf-relay rtp-nte codec g711ulaw fax protocol t38 ls-redundancy 0 hs-redundancy 0 fallback cisco no va
After changing the destination pattern two digit( destination-pattern 99)
Any number which starts from '99XXXXXX' disconnects after 6 seconds , and the called party cannot hear anything , Meaning the the outgoing call matches the dial-peer voice 302 voip and routing the call to the faxserver ( this works also a pbx ) and fax server sends again to vg or cucm
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...