Dear Mr.Fouraki,
Thank you very much ! I don't think I have the luxury to verify the command to see if that will solve my problem as it is just not available on my router's IOS.
By the way, I have another problem here. I think they should be related. I have 8 sites (VoIP) sites connected via a WAN to my CCM. As you know that on CCM, you need to configure route pattern and gateway (I am using H323). Initially, all the H323 gateway IP address on CCM are pointing to the remote end site router serial interface (primary link). However, if the primary link is down, even when the ISDN back-up is kicked up, the H323 gateway is down as the primary serial interface is still down. Hence, ideally, I should have all the H323 gateway IP address on CCM to be pointing to the remote end site loopback interface. So, I did this. Then, when come to specifying the route pattern, I use the loopback0 interface IP address as the new H323 gateway IP address (as configured on CCM).
The problem after doing the above configuration change, I found that all the remote end site cannot make outgoing call but can receive incoming call for both type of on-net and off-net VoIP calls. In addition to that, the remote end user can also make VoIP calls to phones connected to the FXS POTs on the same router.
Then, I found the work-around. When I created an extra (dummy) H323 gateway entry that points to the old serial interface, but the route pattern's H323 gateway is still pointing to the remote end router's looopback0, this problem is gone. All the VoIP can make outgoing and incoming calls for both type of on-net and off-net calls.
Why is this happening ? Is it because the H323 gateway IP address used by the remote end router is different from the one used by CCM. Please help ?
