Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IPO and Teams 2

Status
Not open for further replies.

GOBrien-IWS

IS-IT--Management
Feb 5, 2021
11
US
Hey All,

Does anyone have any experience configuring IPO to work with any virtual SBC's to Teams direct routing? Feel free to share any positive or negative experiences.

I had this going back in the Skype for Business on prem days - time to move on.
 
I think it's supported on the ASBCE now, but always had a crap time with those.

Deployed plenty with Audiocodes connected up to an IPO, some physical, some virtual. All of them have been positive experiences. Their install/support engineers are very good and to be honest you can install them yourself after watching one be set up, I really like them. Good design and you can do some very cool stuff with them. It can double up on your IPO SIP licences though, depending on how you configure your inbound calls. You can spin the virtual one up for free to try it out, limited to 3 concurrent calls. That's what I did before we started buying them. Got it configured and connected to teams, our IPO and a couple of other PBXs we have running just by reading the docs and playing with it, it's a nice, logical, interface.

Also heard good stuff about Ribbon, but haven't ever touched one.

APSS/ACIS/ACSS-SME
not arrogant, just succinct.
 
Ours is running through an Avaya SBCE, but also done it with AudioCodes for us and customers.

The changes Avaya made in R11.1.2 help, as the Avaya sees your Teams calls as associated to your Avaya User. This really helps with caller ID which can be a pain in the arse.

I've changed the default Sigma Script for a couple of bits. I copy the PAI name and put it in the FROM field to teams. This gets group informaiton pushed up. Also, if a call is answered on your Avaya, the IPO send a cuase 31 disconnect message. Teams sees this as a missed call. I've changed it so instead of Cause 31, it sends answered by other. Daves the confusion of a missed call.

Still prefer using Workplace, but it does work well.

The guides are pretty good, but have some steps missing.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top