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:
- Login Media Server via URL https://<server IP>:8443/emlogin/
- Verify Media Server has license via Web Server. Login in the SMGR or standalone WebLM.
- Install license via WebLM Server. Go to home > Licensing > General settings
- Once you have added and saved the WebLM Server info, go to monitoring and verify license has been acquired.
- Install license via WebLM Server. Go to home > Licensing > General settings
- 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
- In the networking setting > general setting you have the option to change settings if you have done this during the deployment
- Add the media server node name in CM
- 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.
- 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
- Add Media Server x then display for verification
- 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.
- You can run measurement on the Media Server as well
- Check element status via Media Server GUI. Make sure operational state = unlocked, Element Status = Normal, and Alarm description = No alarms
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.