We need to keep the H323 GW in place as they act as a demarcation point for our Voice Cloud
All calls to/from the remote site will be configured to use the H323 GW even though they can "route" to each other directly- business reasons
Site 1 to have a SRST router and a H323 GW
When the network is working the inbound calls are sent to the H323 which has a VOIP Dial-Peer to the CCM cluster however when the connection is lost to the CCM cluster I want the calls to be sent to the SRST router as an alternative as the phones at Site 1 will being now registered to the SRST router
What is the best way to manage this- I think I need two dial-peers 1 x to go to CCM and the other to kick in when loss of connectivity to CCM and use this to point the calls directly to the SRST router almost as like MGCP with failover to H323. Can I configure the GW as MGCP from CCM to GW and use H323 Dial-Peer from the GW to the Voice Cloud and then have additional H323 as the alternative application for inbound calls pointing to the SRST router again as in SRST mode
or can I do the above but all in H323 dial-peers? I presume I could use preferences on the dial-peers for preference 1 to CCM, Preference 2 to SRST for inbound calls but this may involve automatically routing calls to the SRST routing maybe in some circumstances???
Re: Question on GW in SRST mode- H323 and MGCP dial-peers
Further to the answer, can I have a GW registered to CCM via MGCP and have H323 dial-peers as well? Can I configure it for CCM to send calls to the GW via MGCP and then for the GW to "extend" them via H323 dial-peers? The GW will be registered to CCM but also point to a GK using H323 - thanks
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...