Forum Discussion
Analog devices, Cloud PBX and Cloud Connector requirement
We have tested and have a working AudioCodes Analog adapter on our Skype for Business system. We are planning on using them at over 120 offices. We are using an MP114 from AudioCodes.
Best of luck!
Mike Wheeler This is awesome! Would you mind sharing how you are using the MP114 to connect to your SFB deployment? We are also using this same device at over 62 of our locations and we are facing challenges with integrating it.
- rplsystemsMar 26, 2019Copper Contributor
How did you get your MP114 to connect to your SFB deployment?
- Carl_CarterMay 22, 2019Copper Contributor
rplsystems We use MP114's in our deployment currently but it's all On-Prem at the moment. You basically give it a static IP address, add your meditation server as a proxy on the MP114, assign a E164 formatted phone number to one of the endpoints, go into Topology builder and add it as a trunk, and finally create an analog device using Skype PowerShell.
So far the only way I see that you'll be able to add analog devices for cloud deployments is through Direct Routing. You'll need to add your SBC to your Cloud's tenant and then register your analog device to the SBC instead. Then you would send calls from the cloud down to your SBC which would then route it to your ATA.
Another option would be to maintain two SIP trunks, one for your cloud environment and one for your on-prem environment and just keep all your analog devices on-prem. In this situation you'll basically just be making a direct call from your cloud client to the on-prem device.
We're looking at setting up SBC's in Microsoft Azure in different regions to support our users. I'm curious to see if we can still setup the MP-114's to register with our Azure based SBC's and see if we can still route calls to and from them. The SBC would basically see the MP114 as a "remote" user so hopefully this will still work.