MakeCall endpoint

[avc859587618170]

Hey gang, I'm trying to use the "/fe/v1/MakeCall" endpoint to make a call from avaya one-x to my cell phone. I had been using the "/telephony/addresses/" endpoint, which I think is deprecated... and it had worked fine. I've tried using the below payload, both with the calling device as my station only, in this case the fake 123456789, and also as a device id, 123456789:rcd2cm2act81t:0.0.0.0:1.

{
  "callingDevice": "123456789",
  "calledDirectoryNumber": "1987654321",
  "callCharacteristics": {
    "priorityCall": "false"
  }
}

The station only gets the closest throwing the error:

{
    "stateIncompatibility": "invalidDeviceState"
}​

The AES logs don't give much more info that "invaliddevicestate".. I've event tried constructing the json like the xml is shown as in the XML Programmer Guide.. which would look like this:

{
  "callingDevice": "tel:+1123456789ext=123456789ext",
  "calledDirectoryNumber": "tel:+1987654321",
  "callCharacteristics": {
    "priorityCall": "false"
  }
}​

None of that worked. Does anyone have any ideas?

Thanks for any help!!

Dave

[avc859587618170]

Ok, this is bizarre to me, but hey, who am I?

So, looks like you need to include the switch info.. device Id stuff even though the called directory number is my cell phone. So, the below worked, I was able to call my cell... which by the way, is not my real number..

{
  "callingDevice": "3135551212:rcd2cm2act81t:0.0.0.0:1",
  "calledDirectoryNumber": "3138675309:rcd2cm2act81t:0.0.0.0:1",
  "callCharacteristics": {
    "priorityCall": false
  }
}

Have a good night!

Dave

[jtb1]

Thanks for posting the solution you found.

[flynn1]

For all device IDs, you must use the DMCC format. To get a device ID in the correct format, use /api/fe/v1/GetDeviceId or /api/fe/v1/GetThirdPartyDeviceId.

Martin

[avc859587618170]

Thanks Martin.. I thought the get device id was to verify the number was a real number in a cm.. Oops.. Thanks for the info!!