Question for SBCSU - 4K Redundancy

[donb01]

Howdy,

Here is the pre-question:

Site A - HP4K V7 with 5 shelves, TDM Redundancy
Site B - Remote LTU w/APE, TDM Redundancy
Site C - Pure IP Remoote from Site B

Here are the Questions:

If the network fails at Site C and the phones go down (I assume TRS), does the system consider those phones in a DND state like in V5 if you unplugged a phone it was considered DND for forwarding purposes?

If the network fails at Site B, which has a few TDM phones for redundancy, but access to the gateway at Site B is cut off from Site C, does the same DND scenario apply?


What I am thinking (because my users don't use DND) is if I allow external CFW and I program a cell number in for the DND settings (if possible) that calls will go to that cellphone if Site C goes down??

I know there is another option for a standby gateway or something like that, but in this case it wouldn't matter if the standby gateway is at Site A, because each "Site B" has it's own outside trunking via PRI and the calls would have no way to route to Site A if the network is down. That would be a solution for a longer term outage, or PRI outage, in which case we would activate a Provider Disaster Plan (CLAR in the case of AT&T) and route all the calls temporarily from site B to Site A. I have never messed with the standby gateway stuff.

Thanks

 

[sbcsu]

Hi Don
I use the SDAT parameter STNOOOS and STNOAPE for that.
So if C goes down you can set their STNOOOS to go to any number internal or external (external if you put in the line access code)

If the network fails at B then I assume that the APESU will come into play at B, and if the APESU is updated regularly it will know where to send the calls as it too will have the STNOAPE parameters set.

End users wont know because if they dial the extension numbers it should dial the outside number (provided you have a carrier presence at B to take those incoming calls)

Nothing else needs to be set just the STNOOOS and STNOAPE numbers for ALL extensions including the ones at A because callers from B and possibly C will need to dial out as well.

Operator console parameters for OOS and APE are in the ACSU setup where you would normally put the night service extension as the OOS destination.

Version 7 of course could do more with virtualization but that depends on your hardware setup.

 

[sbcsu]

Hi
You could also put an OSB (HiPath 3K) at C for fallback registration of their IP Phones - something to consider anyway.
The OOS and APE numbers are covered in greater detail along with Alternate Routing on Error which I have not worked on myself but it seems to be as a fallback to OSB.
I include links below to V7 Documentation which may assist especially OpenScape 4000 V7 - Feature Usage Examples - Contents
To be honest there are so many options now with V7 it would be ideal to have a network planner for HiPath (Openscape 4000 V7) to look at setups prior to install.

These are all PDF documents and are relevant for Version 7
Troubleshooting AlFe
Installation, Configuration and Migration
Installation Guide
Portal Admin
AMO Descriptions
Hardware/Software
Feature Usage Examples
IP Solutions

 

[sbcsu]

Further just to clarify:

The STNOOOS number would normally be another extension or a mobile number for that user.
Whereas
The STNOAPE would be that extensions Direct Dial In number over the Carrier/PSTN network

 

[donb01]

Cool, thanks! I get where you're saying about doing things on the mothership too - although if I do it on the mothership doesn't just propegate out to the APEs during the 2 AM ritual dance?

The problem at C if the network goes down they won't be calling anyone from the IP phones. If their network stays up but their WAN goes down you would think they would still be able to call each other, but unfortunately the call has to be set up by the STMI and NCUI before it can hand off the call to DMC, so I don't think they are going to be dialing anyone except for cells. I will definitely set up the STNOOS/STNAPE for them though if they have a target number to give me. I built redundancy into the redundancy on this system, but unfortunately I have 3 sites that are islands with no hardware because I told them I could set up each site for $1200. Fortunately next year if we move our Medical Information System into the cloud we will be beefing up the WAN considerably, and adding redundant links to each site, so that will help.

 

[sbcsu]

Well it's always down to money with most customers at the end of the day.
You could setup the Openscape Business (OSB) at C and give the IP phones registration fallback to it.

Yes it does propagate out to the APE's but what I mean is that each extension whether it is at A,B or C should have its OOS and STNOAPE Numbers setup then that is saved at the mothership and sent out to the backup APE. Then in the event of a link failure and the APE is in use at least when the end users dial other extension numbers they will get through because the system will dial the OOSAPE numbers that you have programmed in.

Also in ZANDE ALLDATA you can (as you probably know) setup an APE message so as if the network connectivity is down (and the APE is in use) you can see it on the screen, by default it is Emergency Mode or something like that but I normally change it to IP LINK DOWN or something less frightening for the end users.