Section 3: Deploy Other Server Roles - Mediation server install

By -
Section 3: Deploy Other Server Roles

Mediation server Install

Let’s install the Mediation server now on MGOCSMED01


Click on Deploy Other Servers



In here click on Deploy Mediation Server.

Step 1: Install Files For Mediation Server.



In step 1 click on Install.




Accept the license agreement and click OK. Select location for install files and click OK.

Step 2: Activate Mediation Server



Click Run beside step 2.


Click Next on splash screen. Use RTCComponentService for service account and click Next. Review settings and click Next.



These warnings OK as we have not enabled logging: Review Log and click Finish.






STEP 3: Manual configuration of mediation server

We now need to configure the settings for the mediation server.
On the R2 console software (Admin tools):



Now at the forest level >> Right Click >> Properties >> Voice Properties
In Location Profiles we ADD


Now we name our location and give it a description:

Now we need to ADD Normalisation rules.
For our first example we simply tell the system that 4 digit extensions should be passed with no changes and are internal to our environment: (this is dependent on your own configuration)


Our second example simply passes the correctly dialled number for national calls to the PBX with no changes:
(Well… technically we had to remove the 0 from the passed number then add it to the regular expression for it to work, we do this as we require a 0 to be dialled for an external number call)


MORE RULES TO FOLLOW
Next we go to phone usage and ADD a usage:

Now we need to add a phone policy, give it a name and description, click OK. Then add policy in next tab and hit Configure to add our new phone usage policy.
Simply configure and add the usage policy we created earlier:


Now under global policy we can select a policy to use as default or set per user. Our example uses a default policy. 
Next we click on Routes Tab and ADD:


Now this we will fill in the details for our route to the PBX (We use MX-ONE with latest SP so it is SIP enabled)

Next we configure the mediation server settings.
Right click on mediation server and go to properties:



Select the IP address on mediation server to be used for listening (OCS side) and communications (PBX side) also choose Default Location Profile and click on Next Hop tab. Here select our Pool name in next hop and under PSTN gateway enter the IP address of IPPBX or Gateway. Under Certificate tab select the certificate for mediation server and OK this.



In the QoE tab select our pool and click OK.



Step 4: Configure Certificate

Click Run next to step 4.


On splash screen click Next, Choose Create a new Certificate and click Next. Choose Send Immediately and click Next.

Select the Mediation Server name and click Mark as Exportable and click Next. Fill in Details Next. Subject Name is FQDN of Mediation server and SAN can be empty unless a second domain in play. Click Next.

Fill in regional settings and click Next. Confirm CA and click Next. Click Assign certificate immediately and click Next.

Review settings and click Next. Click Finish when complete.




Comments

Post a Comment

Popular posts from this blog

Teams Device Health Monitoring and Reporting

By -
Image
 Microsoft have snuck in a nice new feature into the Teams Admin Center (TAC). We now see a new Notifications and Alerts  menu tree and below this Rules. When we go in here, we find only a single Default  Device State Rule with no option to create any new rules (yet at least...) When we edit this rule, we can see that we now have an option to monitor specific devices (think meeting room devices, collaboration bars etc.. here) Under Device users  we click on +ADD  then enter the name of the account, or accounts if you are monitoring multiple devices, associated with the device, such as the resource account. Then under Actions  we can choose either Channel alert  - to have a nice alert sent to our Teams Channel   OR Webhook  to use webhooks for alerting. Finally ensure to select Active  then Save. Once set up this will take maybe 15 mins to replicate and set up. Then once a device has gone offline, the alert will be sent "Immediately", however it seems to take between 5-10 mins
Read more

Unassigned Numbers in Microsoft Teams using Audiocodes SBC

By -
Image
Unlike Skype for Business, Microsoft Teams does not natively support the handling of Unassigned numbers in the system. So if someone leaves your organisation and you remove the number from them and someone tries to call it, the call will drop. Technically, Teams will return a "404 Not Found" back to the SBC and back on to the telco. What we can do here is to then assign the 404 error to a Route, change the Destination Number (to a call queue or to your main Reception number for example) and route it back to Teams. To do this there are a few simple steps: Step 1 – Create an Alternative Reasons Set Step 2 – Configure existing Teams IP Group to use the SBC Alternative Routing Reason Set Step 3 - Create new IPG Step 4 – Create a new route in IP-to-IP Routing Step 5 - Manipulate Numbers Step 6 – Test  Step 1 – Create an Alternative Reasons Set The first thing we need to do is create an " Alternative Routing Set ", we find this under Setup >> Signaling & Media &
Read more

Skype for Business Edge Server replication troubleshooter

By -
Image
Many times in Skype for Business/Lync the main issue I come across is the deployment is that the edge server(s) fails to replicate. We see this when we run the command in Skype for Business Management Shell : Get-CsManagementStoreReplicationStatus and we see that the edge servers have False and no LastStatusReport or ProductVersion is shown as below. There are a number of things which can cause this and I am going to list them here. Try them in order here as this will contain the most common to the least common issues I found. Ø   Routing Ø   Firewall rules Ø   DNS suffix Ø   DNS (Local and LAN) Ø   Registry entries for SCHANNEL Ø   Certificates A check we can use to see if the replication is working can be done by trying to connect to the following URL from the Front End Server whish hosts the CMS: https://edgeinternalfqdn.domain.ie:4443/Replicationwebservice You should get the following screen: Without this response there is an issue,
Read more