Avaya API for automation

[avaya137xx]

Hi ,

we are using SMGR 8.1 and I would like to know what are the API I should use and also how to get credentials to use .
We wont be using the ASA to perform any task in AVAYA due to some policy in the org, instead we will be using element cut through in the SMGR to do the MACD tasks.
and any additional help would be great ..

 

[kyle555]

System Manager has an API document. Basically, an account that can login to the webpage can use the API with same permissions the account has.

Huge pain to build your own web app on top.

Why not just let people log in to System Manager? It has granular enough RBAC to let people change users and not break things.

 

[avaya137xx]

When we create a SMGR account for MACD team , they will have access to all commands in CM( from element cut through ) which we dont want to happen .
is there a way where we can limit the command access in SMGR also like in CM

 

[kyle555]

Absolutely. I just tried it. When you create a Security Role, you pick what goes inside. Cut through, reports, whatever.

Then under each major "thing" of stuff you can admin in CM - like endpoints, or trunks, or whatever, you pick what they can and can't do.

So, my profile had no cut through, and I could do everything to endpoints except delete. So when I look at endpoints, I can add, change, whatever in SMRG, but there's no way I could remove one.

 

[avaya137xx]

Sorry I am little confused , you dont have element cut through access but you can still do the end point addition , Modify , Delete ?

 

[avaya137xx]

please check the uploaded screenshot , I have option grayed out here under security role .
could you please if i am at wrong page

 

[kyle555]

I don't see a screenshot.

But you can manage CM through the Communication Manager Element Manager - click "Communication Manager" from the center list in SMGR

It's a web GUI to program CM. So, your role can include or exclude cut-through access and also define what commands they have access to.

 

[avaya137xx]

thank you so much , it worked .
But i would also want to know if you could hep me to get the API that can be used automate system health check and MACD work.

 

[kyle555]

https://www.devconnectprogram.com/s..._aura_system_manager/releases/8_1_2/index.gsp

You're going to pull your hair out.

If you want some automation for create/delete, you can build a LDAP sync.

https://support.avaya.com/css/P8/documents/101058519

What you can do is map AD groups to SMGR Roles for admins. So, you can have Buddy Tier 1 in the AVAYATIER1 group on AD, build a LDAP sync to create users mapping that AD group to that SMGR role you built with limited privilege, and then anyone on your helpdesk tier 1 can automagically log in.

You can also map groups to a UserProvisioningRule. So, the AD group AvayaNewYorkBasicAdminUsers can map to a provisioning rule named AvayaNewYorkBasicAdminUsers. That rule can map the LDAP "telephoneNumber" or ipPhone or whatever to extension/mailbox and the rest of the provisioning rule defines what SM they're on, what phone template to use, etc. You can also allow deletions on SMGR so that when a user is not part of that group anymore, their SMGR account is deleted. If you allow deletions on CM and AAM - it's that confusing box in the CM and AAM profile - the "delete on unassign or delete of user", then removing the user from the LDAP group would remove their SMGR profile, CM endpoint, and mailbox.

To adopt the API, you're going to have to consume all of the features of that API that you wish to implement. Unless you've got very special requirements, it's probably not worth your time. For a price, VOSS or Kurmi are middleware stacks that plug atop "any UC" and sell an interface tuned to what you want. They probably have easy servicenow integrations too and get you to extend the admin interface from being more than "program phones" and more like "help me manage my ops according to my processes

 

[avaya137xx]

Thank you so much sir, yes we have our AD group Mapped to our SMGR Roles , so everything is going to be done just same as you explained( as its still going on).
and VOSS we are using on the CISCO side already.
on the Avaya platform nothing yet so I was thinking to use my python skill to build web applications
many thanks for the replies .

 

[kyle555]

Just pay VOSS