From the debug, it looks like you are stripping the 9 (pre-dot, I assume, based on your comment of 9.123) at the CallManager before it hits the VG. But the VG is expecting that 9 to be there to match dial-peer 32. I can see that the called number on the trace your provided is 123, not 9123.
I would recommend not stripping the 9 at the CallManager and making sure that digit-strip is enabled on that POTS dial-peer. (It's on by default) BTW, that 9.T looks alot like would you would use in the CCM route pattern to remove the 9 pre-dot, but it means something else in the dial-peer. That '.' in the dial-peer is a wildcard and is not neccessary. The T is going to wait for the timeout anyway.
Personally, I avoid the T option like the plague. If you live in a country with a predictable length numbering plan (like NANP), I would recommend putting in fixed length dial-peers. Only use the T option for international calls.
Nevermind... Looks like you are using an E1, so I'm guessing it's not the NANP.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...