When the router is in fallback mode, there is no MGCP backhaul to the CM, so the dial peer hands control back to the default session application, which is H323 mode of operation, Therefore, whatever is configured as a destination pattern will take over. Since you have a destination pattern of 9T, the router has no idea of how many digits will come after the 9 access code, so it applies a default interdigit timeout of 10 seconds after the last digit is entered (in case you dial more digits). If no more digits come in after the interdigit timeout , the call is placed.
When the D channel is being backhauled to the call managerwith MGCP , all call routing is done using the configured route patterns on the CM itself, so if the CM decides there are no more digits to come (for example using the 9.@ route pattern) so it places the call immediately after the last digit is dialed as it knows there are no more to come.
Will it be different in SRST mode or not? I remember in H323 there is no delay when not in SRST mode. But if H323 use the dial pattern from the router,I think, even not in SRST mode, there still is delay.true or wrong?
Even if the router is a H323 gateway for a CM, the call from the CM still contains all the digits in the H225 setup mesasge. This is called enbloc signalling. The gateway knows there are no more digits to come so it places the call immediately. When the router is in SRST mode, the digits come from the IP handsets that are now homed directly to the router, so there is no Call manager to analyse the digits and make a decision about the length of the dialplans. Unless you want to configure multiple dial peers with the local number plan, you will have to use the 9 as an access code and an interdigit timeout.
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.