It didn't work for me then I have changed the Topology and used E1s as we had E1s as well and it worked for me.
What is the format of your AA welcome prompt as per my knowledge It only supports u-Law while in SIP case we were having A-Law and E1s are on u-law. As per my knowledge Cisco AA tcl doesn't support transcoding therefore if we use transcoders in order to convert A-law to u-law it won't work.
If you are able to hear the welcome prompt as well as able to enter the digits then I believe this would be configuration issue.
Did you configure the voip dial-peer towards CCM to forward the call to operator or desired extension.
It works now. I've tried several days for this issue, but finally I found all the setting is okay except the test method. I always use my ip communicator to do the test, and I don't know why, it just can get the complete destination digit to send. I just use a phone and dial PSTN to the AA, it works. My goodness! Thanks for your help.
I am using SIP trunk to SP (Verizon). I think maybe the issue for ip communicator is because I connect to the GW through VPN. My dial-peer is to the SIP SRST GW,and both sip and h323 are workable.
My topology is
Verizon SIP PSTN -- SIP trunk -- CUBE(SRST SIP VG) -- SIP Trunk -- CUCM
My scenario is: When CUCM is unreachable, ip phones register to SRST SIP GW, and when outside people dial the pilot number, AA will answer and ask to enter ext. number or 0 to opetator.