thank you for your effort , i wish to do a series videos about installation avaya aura solution with its applications from a to z as a course and many thanks
Hello Dear thank you for your time and your great explanation i trying to add a session manger to my system manger but i miss the step at MIN 7:04 after searching i found the i should add it as Session manger Adding but i miss under standing the meaning of Management ip for the session manager !!!
Hello. Session Manager has 2 ip interfaces. The management and the SM100. The SM100 is the Security Module that all of the sip traffic and Http/https for PPM is used to send and receive for the endpoints. It also has an IP address for management. This is what is used to SSH to SM and also what SMGR communicates with SM on. The sip entity you add for SM is the SM100 ip or FQDN and when you add SM into SMGR in the inventory you add the management ip or FQDN. I hope that clears things up. Make sure you subscribe to my channel if you haven’t already 👍🏼
Thank you for the great explanation. I had an issue with SM patch. Having installed 8.1.0.0.810007 SM and then applied patch 8.1.3.2.813207 and Security Module didn't came up at all. There's a error in replication. Tried a fresh install and 8.1.3.1.813113 patch, same result. Then I didn't install patch and stayed in base SM version 8.1.0.0.810007 and it got registered to SMGR immediately. Seems like SMGR and SM version issue.
Hello, I have found that from experience and this is usually to do with trust management between SMGR and SM that it is always best to make sure SMGR is at the latest patch level and it usually cures the problem. I have also found that having a static entry in the host file for the nanagement fqdn of sm in smgr helps even if DNS is being used and is correct. Stay tuned for more videos. I will be doing more in depth videos of AADS with Active Directory integration and automatic user synchronisation with SMGR.
Great explanation in your videos
Great work 🙏🙏
Looks like there is a section missing just before 7:10
Great Video
thank you for your effort , i wish to do a series videos about installation avaya aura solution with its applications from a to z as a course and many thanks
Hello Dear
thank you for your time and your great explanation
i trying to add a session manger to my system manger but i miss the step at MIN 7:04
after searching i found the i should add it as Session manger Adding but i miss under standing the meaning of Management ip for the session manager !!!
Hello. Session Manager has 2 ip interfaces. The management and the SM100. The SM100 is the Security Module that all of the sip traffic and Http/https for PPM is used to send and receive for the endpoints. It also has an IP address for management. This is what is used to SSH to SM and also what SMGR communicates with SM on. The sip entity you add for SM is the SM100 ip or FQDN and when you add SM into SMGR in the inventory you add the management ip or FQDN. I hope that clears things up. Make sure you subscribe to my channel if you haven’t already 👍🏼
Hello, good afternoon, do you have any ideas for this message? 500 asm identity unresolved, on my end point I just see acquiring service...
Thank you for the great explanation. I had an issue with SM patch. Having installed 8.1.0.0.810007 SM and then applied patch 8.1.3.2.813207 and Security Module didn't came up at all. There's a error in replication. Tried a fresh install and 8.1.3.1.813113 patch, same result. Then I didn't install patch and stayed in base SM version 8.1.0.0.810007 and it got registered to SMGR immediately. Seems like SMGR and SM version issue.
Hello,
I have found that from experience and this is usually to do with trust management between SMGR and SM that it is always best to make sure SMGR is at the latest patch level and it usually cures the problem. I have also found that having a static entry in the host file for the nanagement fqdn of sm in smgr helps even if DNS is being used and is correct.
Stay tuned for more videos. I will be doing more in depth videos of AADS with Active Directory integration and automatic user synchronisation with SMGR.