Have two problems with srst. When a remote site goes into srst mode, how can calls be redirected to their pstn number from ccm? Currently the call goes directly to their voice-mail.
The second problem is when the remote site is in srst mode and they place a outside call, the caller id on the other side displays the directory number and not the full number. What do I need to add to my call manager fallback that will solve this problem?
"We are using CCM 4.1(3)so will have to wait for the CF unregister feature."
No. Have you checked out the CCM SRND?. Your requirement can be met with a carefully thought out dial-plan. When CCM makes a call to 4242 for example the call will fail because the remote site is not accessible via IP. But CCM can be told to try another way such that the dialled digits are manipulated to match the E.164 which of course will be routed by the GW across PSTN.
The same applies in reverse. Say for instance a user dials the fully qualified number from HQ to an IP phone located at remote office. The dial structure or plan should ensure that if IP WAN is available - then it must be untilized in such a scenario. To do this obviously the full length number should be manipulated to 4digits and routed over IP WAN. I am using 4digits as an example but this would be your short form dialled number for inter-site dialling.
I have not looked into CF unregister feature but I would find it difficult to accept that Cisco would release a licence based feature (i.e. SRST) that did *NOT* have a solution to what I would describe as quite a fundamental requirement in 4.1(3)
I'm holding off on upgrading to 4.2 until I've tested upgrade procedure on spare box. I'll be sure to use the UR feature then. If I follow your translation rule correctly, what you are doing is accepting any digits(.*) and with the first 4 digits (....$\) you are replacing with the pattern 361572 (361572\1).
This sounds like it's going to be applied to the dialed number, when I need to be able to change the External Phone Number Mask like in CCM?
By the way, gate solution is working like a charm...thanks
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.