Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

IP Office Management API

Status
Not open for further replies.

derfloh

Technical User
Mar 18, 2010
5,614
DE
Hey guys,

I try to access IP Office through the Management REST API introduced in R10.1.

First of all I just want to pull some data.

To connect I use Posershell with the Cmdlet "Invoke-RestMethod". Following the docs I first call the authentication URI, collect the session cookie and then call an URL to get the IPO users.

This works well four or five times. Every following call of the script is answered with the following error message:

Code:
461:SessionTimeout192.168.111.92

Has anyone an idea what's going wrong?

A nice use case would be to get the IPO users and adjust the SIP contact and SIP name values since this is nod filled during mass import of users.

I appreciate any help ;-)

Need some help with IP Office?
 
I only played with it quickly.

Is that a problem though? I don't program much against APIs, but for what I know about REST stuff is that it's not the end of the world if it times out or fails.
Maybe IPO expects a new login/cookie per query and you just happened to ride it for a few more queries than you should have?
Maybe it's got a self preservation mechanism in there to choke you to a slow amount so you can't possibly crash the system.

I know on G450 gateways that too many SNMP queries can kill it. So, your fancy NMS polling it to death every minute isn't just monitoring its health, it's having an active role in making it less healthy :)

I'd maybe post that on the DevConnect forums to see if it's normal behaviour. In any case, if you're coding against it, I think it's a fair assumption that your code would manage error handling and re-establish the session for any given transaction if required.
 
Hmmm... perhaps the cookie is saved within a Powershell variable and kept... habe to check that.

I tried to close the session after running the script but that didn’t help.

DevConnect forums? I didn’t know about that. I only knew the Avaya support forum. Someone asked the same question there but never got any answer.

Need some help with IP Office?
 
I am a little further. It seems that the authentication URI can be called only five times before you run into the timeout. Probably the session remain open and more than five parallel sessions are not allowed.

I called the auth URI only once now and triggered the following calls (i.e. to get the users out of the IPO) multiple times. It worked fine calling the data about 10 timees.

I have to adjust my script to handle that.

Need some help with IP Office?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top