Connect. Communicate. Collaborate. Securely.

Home » Kerio User Forums » Kerio Operator » Operator 2.5.0 pretty slow AMI Interface
  •  
link611

Messages: 84
Karma: 0
Send a private message to this user
Hi there,

we use an AMI Interface for a TAPI driver connected to a phonemanagement system.

since Operator 2.5.0 the AMI Interface is pretty slow to serve the call informations to the TAPI driver. (about 7-10 seconds)

with Operator 2.4.8 was everything just fine. (about 1-2 seconds)


Maybe some fix for this issue?
  •  
Filip Jenicek (Kerio)

Messages: 1094
Karma: 80
Send a private message to this user
Hi,

we don't experience any slowness or a similar issue with AMI.

Operator 2.4.x was based on the old 1.8 asterisk version. Operator 2.5.x uses the new Asterisk 13. Therefore it is possible that the AMI events look a bit different.

Filip
  •  
link611

Messages: 84
Karma: 0
Send a private message to this user
So, same problem with Operator 2.5.2 and 2.5.2 p1

I was contacting the developer of the TAPI Interface for Asterisk, he thinks, that operator is sending now way more informations to analyse for the TAPI Interface, that's why it is so slow.


Maybe you can test it?


http:// www.phonesuite.de/de/produkte/ast_tsp/phonesuite_tapi_for_as terisk.htm

[Updated on: Fri, 13 January 2017 09:54]

  •  
Filip Jenicek (Kerio)

Messages: 1094
Karma: 80
Send a private message to this user
Yes, the AMI messages have probably changed a bit. Does the TAPI interface support Asterisk 13?
  •  
link611

Messages: 84
Karma: 0
Send a private message to this user
i asked the developer:

it supports asterisk 13.
  •  
Filip Jenicek (Kerio)

Messages: 1094
Karma: 80
Send a private message to this user
What type of AMI account in Operator do you use? Is it a user's username + ami password or a system account created on the integrations page?
  •  
link611

Messages: 84
Karma: 0
Send a private message to this user
A system Account in The Integration page
  •  
Filip Jenicek (Kerio)

Messages: 1094
Karma: 80
Send a private message to this user
Well, the AMI interface of Asterisk in Operator 2.5 is extended by several custom Kerio events. The events are mostly related to active calls and call history. Operator uses these events to display the current state on the Active Calls screen, etc.

I would expect the TAPI driver to just ignore them, I don't know why the messages slow it down, although I admit there is a bunch of them when making a call.

If you used a user's AMI account, then you'd receive events just for that particular user. I don't know if that is sufficient for the driver, though. The system account relays all AMI messages, inc. the custom Kerio ones.

  •  
link611

Messages: 84
Karma: 0
Send a private message to this user
The tapi Driver ignores those Events, but i think ist takes a while Till The right informations are send to The Driver because of The many other informations.
  •  
areichmann

Messages: 17
Karma: 4
Send a private message to this user
Same problem here, AMI Interface from Kerio 2.5> is unusable for TAPI integration because slow response times.

So we can not update our customers to Operator > 2.4
  •  
bsc-computer

Messages: 44
Karma: 4
Send a private message to this user
we, too ...

with three different customers we have had same problems

- Update to 2.5.x > pretty slow AMI response
- downgrade to 2.4.x > normal speed

we use http://phonesuite.de/ or similar application
At the moment we can't update customers


>>Well, the AMI interface of Asterisk in Operator 2.5 is extended by several custom Kerio event

That seems to be the real reason.

[Updated on: Thu, 19 January 2017 11:39]

  •  
Filip Jenicek (Kerio)

Messages: 1094
Karma: 80
Send a private message to this user
Understood. The same question for both of you, do you use the system account? Have you tried the user's account? The user's account should be filtered and should not have all events.

I'll file a new ticket to filter the extra events in the next version.
  •  
bsc-computer

Messages: 44
Karma: 4
Send a private message to this user
Filip Jenicek (Kerio) wrote on Thu, 19 January 2017 12:03
Have you tried the user's account? The user's account should be filtered and should not have all events.

you mean "Password for dialer (AMI)" at user settings.
No, we haven't tried this.
We have different situation.
- with a serverside TAPI Service we only can use one AMI account.
- with a lot of user/extentions it's a pretty lot of work.

Filip Jenicek (Kerio) wrote on Thu, 19 January 2017 12:03

I'll file a new ticket to filter the extra events in the next version.


The solution could be an additional checkbox to the system AMI accounts,
to filter those events

[Updated on: Thu, 19 January 2017 12:28]

  •  
Filip Jenicek (Kerio)

Messages: 1094
Karma: 80
Send a private message to this user
Well the events are for designed to be used by Operator's processes. They should be internal only and should not be sent out. The fact that they got out is a mistake, which we'll fix.
areichmann

Messages: 17
Karma: 4
Send a private message to this user
serverside TAPI with one AMI Account
Previous Topic: Grandstream 2160
Next Topic: ADAT Config
Goto Forum:
  


Disclaimer:
Kerio discussion forums are intended for open communication between forum members and may contain information and material posted by members which may be useful in learning about Kerio products. The discussion forums are not intended to provide technical support for any specific product. Any information implied or expressed in the discussion forums is that of the posting member. Kerio is in no way responsible for the information posted in the forums, or its accuracy. Kerio employees may participate in the discussions, but their postings do not represent an offical position of the company on any issues raised or discussed. Kerio reserves the right to monitor and maintain the forums to promote free and accurate exchange of information.

Current Time: Thu Mar 23 01:19:50 CET 2017

Total time taken to generate the page: 0.01239 seconds
.:: Contact :: Home ::.
Powered by: FUDforum 3.0.4.