Teams Direct Routing with ASBCE 8.1.3 and IPO11.1 FP 2

[daken]

Has anyone got this FULLY working?

Working from the

http://ipofficekb.avaya.com/businesspartner/ipoffice/mergedProjects/teams/direct_routing/index.htm

The document appears to be incomplete.

Only have config for 3 Microsoft serve, what happens if the Microsoft request comes in from one of their other numerus Microsoft servers.
Twinning to the teams client stops all other calls, desk phone, avaya soft phone, mobile twinning.
If the Microsoft client hangs up the BYE message gets server error response.
Simple dial plan on teams appears incorrect.
Have unknown number translations in the sigma script.

Struggling now with the teams client transferring calls.

 

[jamie77]

Not fully tested, but you are correct about the multiple MS servers. I stopped messing with situations as I had so many call failures.

Avaya are aware and working on improvements. I have a very highly escalated ticket on just this at the moment. I'm hearing this improvement will be in R10.1 ASBCE.

The issue is with the ASBCE. If you want to get it working, use an Audio Codes Mediant, seems to work like a charm with that.

Annoying that this feature is released, but has very basic issues and simply doens't work properly.

I'm hoping they will get this sorted as I can see lots of customers wanting it.

As a workaround, add the MS IP Addresses you;ve seen as ASBCE SIP Servers of thier own. This 'solves' the issue.

Oh, and make sure your interworking has SIPS disbaled. The KB guides don't tell you to turn this off, but other guides do. The ASBCE will totally ignore SIP OPTIONS inbound with it turned on. MS don't want it any way.

Hope this help.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer