-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Hi there - I work for a small company that has been exclusively using Mitel phone systems for about 20 years. We want to use the cloudlink API to build custom screen pop features into our internal application; point being, we are building this functionality ourselves, and it's not something that Mitel pro services can provide for us.
We've identified the fact that the cloudlink is the way we can get features like screen pop working. In fact, if we can get just one API call working, then it will be TRIVIAL for us to make that happen, because our dev team is VERY accustomed to using REST APIs.
The problem is that we've been unable to even successfully make the initial authentication call. The error message coming back ultimately says that the Client ID is invalid.
For THREE WEEKS we've been going round and round in circles with our "reseller" and, more recently, some sales engineering folks at Mitel. We've probably asked a hundred different times: what is our client ID? How do we get the client id? How is it generated?
Nobody seems to be able to answer that question for us. At one point, someone from the reseller suggested that we use our user name (i.e. email address) as the client id. You probably won't be shocked to hear that didn't work.
The reseller offered to sell us training (ostensibly specific to the API), and they've offered to refer us to Mitel Pro Services... which won't engage unless they have a statement of work, a signed bid, etc.
According to your own docs (esp. the sample code I've copied/pasted below), this client ID is issued by Mitel.
I'm so desperate that I'm filing this bug here in github - is there someone at mitel that cares enough to just point us in the right direction here? Because what we're getting from the "official" channels is not just useless, it's harmful because it is wasting massive amounts of our time.
appData: {
client_id: "CLIENT_ID" // provide valid unique clientId issued by Mitel
}