SAL Gateway upgrade questions 1

[bfordz]

We're running Avaya Aura CM 5.2 with a SALG of 1.x

So, we need to upgrade to stay compliant and "in touch" with Avaya maintenance / support.

To install an external server / SAL Gateway setup:
What type of server / equipment is required?
What OS is required to run the SAL Gateway?
What are the steps / procedures required to setup, install and get a SAL Gateway up and running?

Our vendor wants what seems to be an astronomical $$ amount to do this for us.
My boss doesn't want to pay the extra money because we own outdated / older equipment (we released maintenance in 2/16)
We need the SAL but I'm not sure it's something I can do myself.

Any input / suggestions would be appreciated.

 

[wpetilli]

I've also logging into the cdom of the remote branch and generated a test alarm. I see it in the log on the SALGW, but I haven't received the email.

 

[bfordz]

I'm assuming this is good news!
I just noticed my SALGW UI is ver: 2.5.3.0.7; can I assume that is automatically updated the SALGW to 2.5 and also applied the SP3 patch?

So, now all I have to do is finish the setups; add my "Managed Elements" etc.?

I do have a question about the smtp setup; no matter what I try I can't seem to get it to work.
I've tried using my Microsoft Office 365 email credentials and it wouldn't work.
I tried using my personal gmail account info and that's not working.

I have hardware firewalls in place but I monitored that for anything getting blocked and my firewall is passing the traffic.

Does anyone have any suggestions on getting this to work properly?

 

[bfordz]

To answer the problem of emails not working;
I found (on the web) Smtp2go. It's free and an easy setup.

It's what's working for me on two of my small servers I need notifications on.

Sorry,
I thought I had updated this earlier.

 

[bfordz]

I have one last question on finalizing my upgrade, same question wpetilli had.

"Do I need to make any changes in any of my CM/SP/GW's for this new SAL?"

If there aren't any changes to be made, could someone explain how the System now knows my SALGW is no longer on board (VSALGW)?

I had VSALGW ver.1.x.x. on our System Platform CM 5.2.1, now it's on a VMware server running on CentOS.

I just want to make sure I haven't missed anything.

 

[bfordz]

Is there a way I can send a "test" alarm from my System Platform / CM to my SALGW to make sure all is setup properly and the two are in communication with each other?

 

[wpetilli]

https://www.youtube.com/watch?v=sLV2DNDxv9I

 

[kyle555]

testinads in CM's CLI should do it.

Or, add a port-network or a media gateway that isn't really there. A PN should send a major and a gateway a minor alarm.

 

[bfordz]

Thank you to wpetilli and kyle555 for the quick response.

I viewed the video and I ran the commands as it explained but I'm not seeing anything in my logs.
Unless; the video is for cm6.x and I'm running cm5.2, would the log file be in a different folder?

logger -p local2.err "This is a test alarm from cdom"
I didn't get any errors from cli.


OK; I ran testinads and i got this response from the cli;

Reply from CummunicaMgr: Test message was sent to INADS, and the reply is CALL_A_OK.
That message was in the logs.

Thanks again gentlemen for your responses and help.