Avaya IP Office Server Edition - Part IV
JW: I’m JW with Digitcom.
EM: I’m EM with Digitcom.
JW: And today, we’re going to be talking to you about Avaya IP Office Release 9.1 Server Edition Resiliency. I’m going to spend the first minute and a half just describing an architectural drawing of what Server Edition is and how it functions, and then I’m going to pass it over to EM, going to hand the marker over to him and he’s going to explain Server Edition from a technical, architectural point of view, how the systems can fail to one another. I’m also presuming that the viewer has knowledge of Preferred Edition, and to some extent or to a great extent, IP Office in general. This is going to be a fairly technical discussion. So if you don’t have that level of knowledge, then take a step back, watch some of our other videos on what is IP Office and Preferred Edition, et cetera, and then come back and watch this one.
So, let me draw a quick diagram, as I said. So, let’s just say we have an Avaya IP Office 500V2 cabinet. We have that at Site 1. And then we have another 500V2 cabinet at Site 2. What we’re going to introduce now is this Server Edition, and this falls all under Release 9.1. So, what we have here is, this cabinet is connected to here, this cabinet is connected to here, effectively we should be drawing that to the cloud, and then up to here because it’s maybe going through the cloud. This could technically be at the same location, but we’re getting into semantics.
So, the purpose of the IP Office from a Server Edition point of view, is we’ve taken the brain essentially out of the V2 cabinet, so on the Preferred Edition the brain is sitting inside there, and we’ve offloaded that and the programming, provisioning, management, licensing, applications are now all residing on a single box. So effectively, these two, or three, or four, or five… and we can keep going up to 32 sites, and now all sharing the information that’s contained in that one Server Edition cabinet. I’m going to pass the marker over to you, EM, so you can continue this discussion and explain the resiliency and how it works from a V2 cabinet or an IP Office perspective.
EM: Alright. So, assuming that this is Server Edition Normal versus Server Edition Select — JW, you are right. There are 32 sites that we can join to. So, essentially, the same capacities as we would have with a small community network. But the big difference would be the Server Edition itself. Inside the Server Edition, which can live physically or in a virtual machine, we have a number of different components that matter. One of them is the one-X Server or one-X Portal. One of them is Contact Recorder. One of them is the IP Office itself, and I’ll go into more detail on that. And then the most importantly is the voicemail system.
So, all these guys live inside this virtual realm including the IP Office.
JW: So, can this all sit on one box, technically? All virtualized?
EM: Yes, absolutely.
JW: So, they’re separate images? You can’t have one image with all this inside it?
EM: It is one image with all this inside it. Each of these is a silo inside one big installation. And so, whether it’s virtual on some VMWare Stack somewhere, VMWare ESXI 5.something or other and up, or whether it’s on a physical box like one of the Avaya supply Dell boxes, either way this sits as one image, and all of these components run within it. And so, what makes it interesting, I think, is that when you first look at resiliency, each of these cabinets talks to the Server Edition as you said earlier on. And so, they share the component, the voicemail component. They share the one-X Server and so forth — And even Contact Recorder. But in order to make this effectively redundant, we can take this entire back image and put in a secondary Server Edition, known as the Server Edition Secondary, and bring this into the equation.
And once the secondary server gets added, each of the IP Offices end up having a link to it as well as the Server Edition. And so, what’s going on is, whenever we leave a voicemail on the main Server Edition, it’s being replicated. So this line here that goes in between the two of them is probably the most important line, and this line here ends up doing a couple of things. One of them is a heartbeat, so it’s able to tell if the other one’s up there or not. The second one is, it’s doing SMTP, and then lastly it’s doing voice. So that technically if a phone was registered to the secondary Server Edition, it can speak to the first Server Edition. If we have trunks on the second Server Edition and on the first Server Edition, we can ARS such that the IP Office Cabinet V2 right here goes to grab lines, if none are available here, it grabs them out of here.
JW: Let’s take a step back for a second. Let’s say you don’t have this second box, you only have one box. This link is lost. What happens and what does this phone system look like?
EM: Looks the same as he always did. So unfortunately, he doesn’t have any voicemail because he’s separated from the main Server Edition. So this is assuming, again, no secondary Server Edition, right?
JW: Okay. So, you’ve taken that out. Now, what happens? So, that also presumes you have lines coming into here. So if you have lines coming into here and it loses its connectivity to its Server Edition, this site here can still take inbound calls?
EM: It sure is self-sustaining. It just doesn’t have voicemails.
JW: Make outbound calls, but it doesn’t have voicemail.
EM: That’s right.
JW: So it loses the voicemail, but it still has its dial plan, but it doesn’t have an auto attendant so it would failover towards reception for example.
EM: That’s right.
JW: If we introduce this box, I know you just erased these lines, but if we go ahead and redraw them… So it lost this link, what happens here now? This box here will now start talking to that cabinet?
EM: Exactly. Amazingly so.
JW: So it keeps all the extensions?
EM: Because this guy is running specifically out of the group here, because this guy is running his own IP Office and he’s running his own voicemail system which is redundant to the first voicemail system, it can take messages for you, it can provide the correct greeting, et cetera, even though it doesn’t have the connection to the first Server Edition.
JW: Got it.
EM: Once that connection restores, these two have been passing messages anyway, so as soon as this guy is able to talk to the original Server Edition, all of those messages are already in the mailbox waiting for him.
EM: Capacity of a normal Server Edition? 2,500 extensions across 32 locations. The maximum on that box itself, if you were to blast all the phones against it and forget the 500’s for example, would be 2,000.
JW: 2,000 to one cabinet?
EM: 2,000 to one cabinet.
JW: But 25 in the whole thing?
EM: That’s right.
JW: Got it, okay.
EM: So you could have 2,000 on this cabinet, 500 on this cabinet, and no V2’s at all, as long as you were willing to give up the gateways and the local location. Remember, these gateways serve as a majorly important function, and that is the telco. So, as they get cut off from the equation, we still have lines in the case that you’ve got a 500V2.
JW: Okay. And if you have SIP trunks? The SIP trunks can fail.
EM: Same thing. See, SIP trunks still, again, come to the IP Office 500V2. If we didn’t have V2 here–
JW: Let’s say you have your SIP trunks, they come into here but then you’ve lost your connectivity here, can the SIP trunks fail? Well, I guess they will. They’ll come into the Server Edition still so you’ll still have your dial tone? Keeping in mind, this cabinet’s now failed.
EM: Well, SIP trunks, that would be up to you and your telco, right? If it was Digitcom, for sure, we would just fail your SIP trunks at this site to your SIP trunks on the Server Edition, and voicemail would get it, and the site would sort of be out of commission. Now, the phones on this site, supposing that the phones are IP phones, what one would likely do is, all these phones would start talking to the Server Edition. These SIP lines, because they lost registration to the 500V2 cabinet, would again be sending through calls to the Server Edition. So, you wouldn’t miss a beat because all the SIP lines are coming in here now.
JW: Got it.
EM: Alright, good.
JW: So, we’re going to do another video on Select Edition?
EM: Yes, sounds great.
JW: Alright. So, if you click the link at the end of this video, we’ll take you over to our Select Edition redundancy and we’ll continue this conversation over there. I’m JW.
EM: I’m EM.
JW: And we’re both with Digitcom.
EM: Thank you.