Skip to main content

Configuring Avaya Aura Media Server

Robert Johnston
Updated

 Written By:

  Michael Kellogg

Manufacturer:

  Avaya

Product:

  Media Server

Version:

  

Patch Information:

  

Ticket Number(s):

  

 

Description:

This article will show you how to do a base configuration on the Avaya Aura Media Server. The content provided here is for general guidance.

 

Assumption:  CM and ASM routing is in place and no DSP are available.  AMS VM has been deployed and configured with serverIP. 

Steps:

  1. Login Media Server via URL https://<server IP>:8443/emlogin/
  2. Verify Media Server has license via Web Server. Login in the SMGR or standalone WebLM.
    1. Install license via WebLM Server. Go to home > Licensing > General settings
      src_c37ccc1589654161807faa34786a7a5b.png
    2. Once you have added and saved the WebLM Server info, go to monitoring and verify license has been acquired.
      src_4e700ae79b624ebd8368fe131134bc67.png
  3. In CM validate how many VOIP channels are available.   This determines the total number of simultaneous AAMS channels that CM may establish across all Media Servers and corresponds to the number of AAMS channel licenses purchased
    src_14c7aeb09e1c4461969d939366009305.png
  4. In the networking setting > general setting you have the option to change settings if you have done this during the deployment

    src_0cb9bb0a946d44228f7d2eb9972c927a.pngsrc_0e2c8a7648194c1e88aa6f7eab0b4f42.png
  5. Add the media server node name in CMsrc_659476d71691413c82f612db14046d39.png
  6. Add the signaling group for Media server.  Media server connects directly to procr, TLS is the prefer protocol.  Note:  You will not need to establish trunk members for media server.src_c6ea93faf1a742f29a81e6bcb7a29609.png
  7. You are now ready to add remaining configuration via Media Server GUI.  If you decide to use TCP as the preferred protocol you will need to add the PROCR IP as a trusted node.  If using TLS this is not required
    src_ac8fa058e9664a828ac5a22b4e2444e0.png
  8. Add Media Server x then display for verificationsrc_79ec10f659c746a4bbbd9456dc4f5ee6.png
  9. Verify Media Server is in service.  You are now ready to process calls and use the resources VOIP calls and announcements.  Note:  If Media Server is in Pending in-service state this is either a network issue or configuration.
    src_c282bf9cf9d1465c8bb211c3566fcf84.pngsrc_2eb6103633fe483e830e6b0cad2a9156.png
  10. You can run measurement on the Media Server as wellsrc_0f3916758fd04d5592d81ea74e6b0731.png
  11. Check element status via Media Server GUI.  Make sure operational state = unlocked, Element Status = Normal, and Alarm description = No alarms src_e8af631e2cb84c3096d0537f74acd6f2.png

 

Disclaimer: intlx Solutions Knowledge Base

The information contained in this knowledge base ("Content") is provided for informational purposes only and is intended to be a general resource. intlx Solutions does not guarantee the accuracy, completeness, or timeliness of the Content.

Use at Your Own Risk: By accessing and using the Content, you agree that you do so at your own risk. intlx Solutions assumes no responsibility for any errors or omissions in the Content, nor for any damages or losses you may suffer arising out of or related to the use of the Content.

Current Customers: If you are a current intlx Solutions customer and have questions or require further clarification on any information presented here, please do not hesitate to contact our support team directly. They are available to assist you and ensure you have the most up-to-date information specific to your needs.

Not a Customer? If you are not currently an intlx Solutions customer but are interested in learning more about our solutions and how we can help your business, please click here. We look forward to the opportunity to discuss your needs and explore how a partnership with intlx Solutions can benefit you.

Thank you for your understanding.


 

Related articles