I call event server by AlarmCommandToken interface.
First I call management server for a token by a administrator user.
And then I call event server with the token.
But the event server returned “Invalided token”.The token did not expire.
I could receive alarms by milestone client.
How could i get support from milestone company if i can not fix this issue?
Thank u very much for your answer.
You might be using the wrong interface..
See VideoOS.Platform.Proxy.AlarmClient.IAlarmClient Interface Reference
There is a difference on the interface for c-code and e-code servers.
On the support question..
I believe you belong to an organization that is a Milestone partner and as such can create Support cases with Milestone Technical Support. You should be able to get help from users of this forum on development issues but you have an alternative route there.
@Bo Ellegård Andersen (Milestone Systems)
Thank u.
The interface work well in my private server.
But in the server of customer it does not work well.
The interface is web service interface than a SDK interface.
Please help me.
There are two versions of the Alarm Command web service: AlarmCommand and AlarmCommandToken. The former is for use with Windows/AD users on C-code, while the latter is for use with E-code and basic users on C-code.
In order to use the AlarmCommandToken interface you need to get hold of a token and keep it valid. See the documentation on the Server SOAP Protocol for further information about how to do this.
The AlarmCommand and AlarmCommandToken web services are hosted by the Event Server and will thus be exposed on the machine and port used by this. On a default installation on the local machine you can access the WSDL on these addresses:
See also the Alarm List sample
@Bo Ellegård Andersen (Milestone Systems)
I use AlarmCommandToken interface.
It work well when I call the interface of my milestone event server.
But i said “Invalided token” when i call the interface of company’s milestone event server.
With that information from you I would guess your server is not the same XProtect product as your company’s (or you use a basic authentication user in one place and a Windows users in the other place).
Perhaps you can run the Alarm List sample in both environments while you trace the network communication with Wireshark or similar and then do a comparison.