Unified Communications

Hello all -

I am hoping this group has some good input on a question that has been posed to us in telecom, and that question is this:

How do we go about putting SIP Trunking at remote locations that have less then 50 people in the building (Branch Office)? These locations are geographically diverse from our main campus, by hundreds of miles, so maintaining a local survivability is required in any design we build out. That means for us, we have to have a SIP Trunk provided at the location, and can't trunk it back to our Main Campus, in the event the WAN between sites goes down. The LSP/Branch Session Manager and SBC, should still be able to operate to provide inbound/outbound calling. Furthermore, all of these sites do not have a Virtual server infrastructure to build upon, so we are left with having to use physical device of some sort if we go SIP/SBC. Also to throw a wrinkle in this, one of the sites may also require Remote Worker functionality through the SBC (So we are looking for both Trunking and Remote Worker on the same SBC).

So MY real question for the group here is, how do you go about providing SIP trunking at your remote locations that may fit the description above? I have seen and read about some smaller SBCs (i.e. Oracle, Audio Codes, etc.), I have also seen where folks have stood up a server, and ran a small/local VM instance, and put Avaya SBCE on it, and I bet there are other out of the box ideas as well. What I really would like to know from the group is, what have others done here?  Was it affordable, what worked well, and what issues you all might have run into?

Hello all -

I am hoping this group has some good input on a question that has been posed to us in telecom, and that question is this:

How do we go about putting SIP Trunking at remote locations that have less then 50 people in the building (Branch Office)? These locations are geographically diverse from our main campus, by hundreds of miles, so maintaining a local survivability is required in any design we build out. That means for us, we have to have a SIP Trunk provided at the location, and can't trunk it back to our Main Campus, in the event the WAN between sites goes down. The LSP/Branch Session Manager and SBC, should still be able to operate to provide inbound/outbound calling. Furthermore, all of these sites do not have a Virtual server infrastructure to build upon, so we are left with having to use physical device of some sort if we go SIP/SBC. Also to throw a wrinkle in this, one of the sites may also require Remote Worker functionality through the SBC (So we are looking for both Trunking and Remote Worker on the same SBC).

So MY real question for the group here is, how do you go about providing SIP trunking at your remote locations that may fit the description above? I have seen and read about some smaller SBCs (i.e. Oracle, Audio Codes, etc.), I have also seen where folks have stood up a server, and ran a small/local VM instance, and put Avaya SBCE on it, and I bet there are other out of the box ideas as well. What I really would like to know from the group is, what have others done here?  Was it affordable, what worked well, and what issues you all might have run into?

Hello all -

I am hoping this group has some good input on a question that has been posed to us in telecom, and that question is this:

How do we go about putting SIP Trunking at remote locations that have less then 50 people in the building (Branch Office)? These locations are geographically diverse from our main campus, by hundreds of miles, so maintaining a local survivability is required in any design we build out. That means for us, we have to have a SIP Trunk provided at the location, and can't trunk it back to our Main Campus, in the event the WAN between sites goes down. The LSP/Branch Session Manager and SBC, should still be able to operate to provide inbound/outbound calling. Furthermore, all of these sites do not have a Virtual server infrastructure to build upon, so we are left with having to use physical device of some sort if we go SIP/SBC. Also to throw a wrinkle in this, one of the sites may also require Remote Worker functionality through the SBC (So we are looking for both Trunking and Remote Worker on the same SBC).

So MY real question for the group here is, how do you go about providing SIP trunking at your remote locations that may fit the description above? I have seen and read about some smaller SBCs (i.e. Oracle, Audio Codes, etc.), I have also seen where folks have stood up a server, and ran a small/local VM instance, and put Avaya SBCE on it, and I bet there are other out of the box ideas as well. What I really would like to know from the group is, what have others done here?  Was it affordable, what worked well, and what issues you all might have run into?

Thanks James R. -

Yeah I was wondering what devices some of the other folks I saw had talked about using a local system to host it... I will check these out and see where/how they might fit in our planning. Glad you shared that!

James

------------------------------
James Davis
Voice and Data Senior Engineer
University of Nebraska Medical Center
Omaha NE

Original Message:
Sent: 12-08-2020 04:50 PM
From: James Rawland
Subject: Physical SBCs for the Branch Office

Check out the Portwell CAD-0230 to see if it meets your needs.

-James

------------------------------
James Rawland
Telecom Engineer
PeaceHealth
Springfield OR

Original Message:
Sent: 12-08-2020 04:38 PM
From: Shaun Smith
Subject: Physical SBCs for the Branch Office

We are using routers with 4G LTE as our survivable links should the WAN circuit go down.  The amount of call traffic may be limited and should be load tested, but it has worked for our purposes for several years.  Good cellular service is also a requirement :-)

------------------------------
Shaun Smith
UTHealth
Houston

Original Message:
Sent: 12-08-2020 04:28 PM
From: James Davis
Subject: Physical SBCs for the Branch Office

Hello all -

I am hoping this group has some good input on a question that has been posed to us in telecom, and that question is this:

How do we go about putting SIP Trunking at remote locations that have less then 50 people in the building (Branch Office)? These locations are geographically diverse from our main campus, by hundreds of miles, so maintaining a local survivability is required in any design we build out. That means for us, we have to have a SIP Trunk provided at the location, and can't trunk it back to our Main Campus, in the event the WAN between sites goes down. The LSP/Branch Session Manager and SBC, should still be able to operate to provide inbound/outbound calling. Furthermore, all of these sites do not have a Virtual server infrastructure to build upon, so we are left with having to use physical device of some sort if we go SIP/SBC. Also to throw a wrinkle in this, one of the sites may also require Remote Worker functionality through the SBC (So we are looking for both Trunking and Remote Worker on the same SBC).

So MY real question for the group here is, how do you go about providing SIP trunking at your remote locations that may fit the description above? I have seen and read about some smaller SBCs (i.e. Oracle, Audio Codes, etc.), I have also seen where folks have stood up a server, and ran a small/local VM instance, and put Avaya SBCE on it, and I bet there are other out of the box ideas as well. What I really would like to know from the group is, what have others done here?  Was it affordable, what worked well, and what issues you all might have run into?

------------------------------
James Davis
Voice and Data Senior Engineer
University of Nebraska Medical Center
Omaha NE
------------------------------

Hello all -

I am hoping this group has some good input on a question that has been posed to us in telecom, and that question is this:

How do we go about putting SIP Trunking at remote locations that have less then 50 people in the building (Branch Office)? These locations are geographically diverse from our main campus, by hundreds of miles, so maintaining a local survivability is required in any design we build out. That means for us, we have to have a SIP Trunk provided at the location, and can't trunk it back to our Main Campus, in the event the WAN between sites goes down. The LSP/Branch Session Manager and SBC, should still be able to operate to provide inbound/outbound calling. Furthermore, all of these sites do not have a Virtual server infrastructure to build upon, so we are left with having to use physical device of some sort if we go SIP/SBC. Also to throw a wrinkle in this, one of the sites may also require Remote Worker functionality through the SBC (So we are looking for both Trunking and Remote Worker on the same SBC).

So MY real question for the group here is, how do you go about providing SIP trunking at your remote locations that may fit the description above? I have seen and read about some smaller SBCs (i.e. Oracle, Audio Codes, etc.), I have also seen where folks have stood up a server, and ran a small/local VM instance, and put Avaya SBCE on it, and I bet there are other out of the box ideas as well. What I really would like to know from the group is, what have others done here?  Was it affordable, what worked well, and what issues you all might have run into?