Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Using the Voice of O365

To use The Voice of O365 several items | ‘things’ need to be organized. These items or actions are described below in general terms.

1.       Active Directory (DNS | Trust)

To continue to use the single ‘sign on' principle when Microsoft Office 365 in combination with The Voice of O365 is used a VPN connection to the Active Directory (Domain Controller) of the customer is needed (read Microsoft condition). With the help of this directory service data of the user including name, email address, phone numbers, etc. are mapped to the directory service of Skype for Business. Eliminating the need to sign-on twice. Note: It is not unthinkable that once the bi-directional forest trust running over the VPN is established a one-way trust is set up for user authentication only.

If an organization does not have an Active Directory it can, as additional cloud service, 'hire' one from The Voice of O365. A control panel provides the ability to add or delete users. To access the control panel follow this link.

2.       DNS-record adjustment

The Skype for Business client uses DNS records to connect to Skype for Business to: log-in and allow federation. To properly use the Voice of O365 service a number (5) DNS records changed | additions need to be made. Below an example, your domain is ‘contoso.com’. Change all 'contoso.com' values in your own domain name (both internal and external). Are the above adjustments made then follow this link to verify the changes.

Note: There is no traffic over the VPN connection other than AD authentication verification. The Firewall of the Voice of O365 has been set up so that all traffic outside of these servers will be blocked.

 3.       SIP domain Certificate

SoftApp adds, the for the customer, purchased SIP domain certificate to its Skype for Business platform (The Voice of O365). This certificate must be validated by the customer through an automated link that was sent by e-mail. Adding the certificate to the Voice of O365 domain also ensures a secure connection.

 4.       SIP trunk & telephone numbers

The Voice of O365 is SIP trunk (telecommunications provider) independent. The SIP trunk and corresponding telephone numbers in use by the customer will be need to be registered to the platform the Voice of O365. Hence calls will arrive on the platform of the Voice of O365 and will be accommodated by the platform the Voice of O365 - read handled by Skype for Business. For this to eventuate the customer (being the contractor) needs to contact their telecom provider and submit a request to this end. The above principle means that the customer does not leave the existing agreement with her telecom provider.
If the customer is using ISDN, then she must switch to a VoIP (SIP) connection. The customer has the option to make a request to her existing telecom provider or select a new telecom provider that could deliver e.g. a Microsoft certified SIP trunk.

5.       Voice Mail | Unified Messaging

To add Voice Mail functionality and Unified Messaging functionality to the Voice of O365, allowing the user to be informed in Outlook of made and missed calls, IM conversations and group discussions, it is a requirement to create a Unified Messaging dial plan in the Microsoft Office 365 administration portal of the customer.

6.       Skype for Business Online (Office 365)

To use all the features of The Voice of O365 the partner needs to turn off, for all users, Skype for Business Online in the Microsoft Office 365 administration portal of the customer.

  • No labels