Is direct routing all or nothing?

[biglebowski]

We are currently rolling out the Workplace client via a remote worker SBC but the business also wants to add telephony to the MS Teams client.

Avaya Teams calling is rubbish so we are going to explore direct routing but need to understand if we can use both solutions?

We have around 2500 DDIs that are used by contact centres and normal users, can we continue to push some DDIs to the Elite agent CC and others to MS Teams via direct routing?

Is there a way we can fall back to the Workplace client for DDI if Teams goes down?

Biglebowskis Razor - with all things being equal if you still can't find the answer have a shave and go down the pub.

 

[kyle555]

Well, you're paying for phone system to be allowed to add direct routing for those users.

Let's say it's SIP Trunk-->SBC-->SM-->CM-->SM-->SBC-->Teams. You can peel out however many DIDs you want to go straight to Teams.

I was playing with some configs and made my Teams extension an EC500 number off my CM station. Direct Routing sends the call to the SBC and then to CM and then it matches to my station - like if i was calling thru the PBX on my cell phone. That makes call processing pass through a CM station. If you route inward calls that way, then yeah, then direct routing is only ringing because of EC500 so if Teams is down, Workplace won't be. You'd still probably need to have no coverage path to let Teams be the users voicemail, which you would lose if Teams is down, and it's a configuration not for the faint of heart, and Teams only goes down once in a blue moon, and you'd be paying for licenses on both.

So yes, there is a way. It isn't very practical though.

 

[AvayaRed]

You can keep the call center DIDs on the Aura side and route the normal workers DIDS to the Teams with a connected certified SBC. ASBCE 8.1.x is certified for Teams but there are some vendors like Ribbon, AudioCodes and Oracle that have some more Teams integration with the SBC that has support for things like local survivability (Survivable Branch Appliance) in the event of a network outage. You would not be failing back over to the CM and Workplace in that example, you would be failing over to the SBC and calls would be inside of Teams still.

One thing that I wish Avaya G450s and S8300Es could do is act as the SBC and the gateway similar to AudioCodes and Ribbon so you do not need another VM just for the SBC and it would just be embedded in the S8300 sitting in the gateway.

 

[G van Hamburg]

I think the new S8300 will be able to have a SBCE deployed.

Freelance Certified Avaya Aura Engineer

 

[AvayaRed]

Any word on a GA, I heard the S8300F got pushed back? If they do, that would be good for server consolidation. I wonder if it would be on one 8300 blade or would require two in a gateway since the ASBCE take up alot of resources compared to other SBCs.

 

[G van Hamburg]

I will let you know when I find out, ok?

Freelance Certified Avaya Aura Engineer

 

[biglebowski]

Thanks, the licencing is not an issue as the business is moving from E3 to E5 for everyone for the exchange online security so it makes sense to start using direct routing instead of or as well as the Workplace client.

Have to say I'm really disappointed with Avaya over the whole Teams Calling and customer service mode in Workplace, they have been absolutely rubbish when it comes to passing on info or instructions so far.

Biglebowskis Razor - with all things being equal if you still can't find the answer have a shave and go down the pub.