I have a customer where they have a remote site that needs SRST feature. During normal operation, all the site phones will registered with the CUCM 7.x over WAN. However, when the WAN is down, the customer wants the remote site to utilize the local PSTN.
Q1) However, the problem is that the remote site is sharing the same DN range as the primary site. The remote site range is not in a contiguous block range so can't be seperated out on the PSTN E1 trunks. So with the setup of primary PSTN trunk at HQ and secondary backup PSTN trunk at remote site, even during WAN outages, all PSTN calls will still be routed in via the HQ from the PSTN carrier, and because the WAN link is down, the remote site phones will never be able to get the calls.
Is there any way to overcome this?
Q2) For outbound calls at remote site, can all the remote site phones "remember / memorise the DN" such that during SRST, they can all dial out via its local PSTN E1 trunk?
Any ideas would be greatly appreciated.
NB:- I have attached a drawing of the network diagram.
You can setup the branch phones with Call Forward Unregistered Numbers (CFUR) matching the branch site secondary DID range. The CFUR destinations can be set under CUCM DN configuration. Don't forget to set proper CSS there.
When WAN link is down the phones will not be seen by CUCM as registered and it will redirect calls to the CFUR numbers.
Translate DNIS on incoming calls to the branch PSTN to match phones DNs.
When branch phones in SRST mode dial out, they will use your secondary PSTN connection. You could restrict Calling Number presentation on such calls to avoid confusion for PSTN users.
Please rate helpful posts
Пожалуйста оценивайте полезные сообщения
Let me see if I have understand you correctly too.
On all the branch phones sitting at the remote site SRST Gateway, each phone will have 2 sets of extensions:-
i) 1xxx (original PSTN range at HQ)
ii) 2xxx (new range for branch office)
Point 1) Then at all the 1xxx branch phones, i setup a Call Forward Unregistered Numbers and point them to the relevant 2xxx on each phone. This will take care of all the inbound calls for 1xxx range during WAN failure for branch phones when the PSTN call comes in via HQ.
One Q though, when you said CFUR, do i need to put Call Forward No Coverage as well?
2nd Q, where would i do the "Translate DNIS on incoming calls to the branch PSTN to match Phone DN?? Since the 1xxx range that the remote site phone has is NOT a contiguous block, i can't easily setup a translation to translate them. Also, when you mean to match phone DN, you mean to match it to 1xxx or 2xxx?
Point 2) As for the outbound calls, Caller ID would be blocked and they would go out via the remote SRST Gateways's own PSTN trunk with the DID range of 2xxx.
Oh i see!!! So you are saying the PSTN range for branch site is 201-201-2XXX. And inside the CFUR fields are asking the centralized HQ Voice Gateway to route the call back out to PSTN (201-201-2XXX), the branch SRST VG would get the call, then somehow translate 201-201-2XXX back to 1XXX.
And i would have to block "Outbound Caller ID" on the remote site since 1XXX doesn't belong to the remote site.
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.