The call setup is OK, so your Call Manager to gateway and PRI is good, as well as to the phone.
It appears your phone is unable to send packets to the MGCP router. Try an extended ping from the gateway router to your phone sourcing packets from FastEthernet0/0.108. If this fails, confirm that your phone has the correct default gateway. If it does try a traceroute from the router on your phone's subnet to the gateway router.
Do you have any security filtering that may be blocking packets?
I do have some access-lists, just those listed as mustdo's in Internetworking docs. Applied them towards the multilink interface though. Strange thing is that it seems access-lists were created on a core switch that don't seem to be applied. I configured this switch via a Cisco automated program.
Can any of the attached configs add up to blocked packets. Strange thing is that I can ping all over the darn place! to and from from all the pertainite interfaces and ofcourse from the CCM.
Let me know if their is any other items needed for complete view of problem. Thanks
Is SBB_AR_FM1 a different GW from the previous post where you provided MGCP.txt?
I ask because the config now has this:
mgcp bind control source-interface FastEthernet0/0
mgcp bind media source-interface FastEthernet0/0
FA0/0 does not have an IP Address assigned.
In your other conversation you noted that inbound calls work but outbound calls have one way audio. Is this still the case?
Try and inbound test call then an outbound test call. After the inbound call web into the IP Address of the phone, for example http://. On the left side click on the "Stream 1" link. Note the remote address and port. Do the same after the outbound call. What is different between the two (the port will be different just want to see what it is)?
The local and remote addresses stayed the same in both senarios, however the remote tcp/udp ports changed. I have tried this multiple times and seems to change arbitrarily. Did that provide any more insight?
The audio path is directly between the IP phone and the gateway. The control path is between the Call Manager and the endpoints, so be sure that you can ping between the gateway router and the phone. It may be that the phone can communicate with the Call Manager, but only one way to the gateway.
I would suggest removing security access lists until you get the calls working.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.