ConferenceCall and SingleStepConference endpoints

[avc859587618170]

Hey everyone! Has anyone used either the ConferenceCall or SingleStepConference endpoints? I'm in the process of trying to get this set up in my proof of concept application. For 10.2, the swagger page is showing the below as an example of the body for a SingleStepConference:

{
  "activeCall": {},
  "deviceToJoin": {
    "typeOfNumber": "string",
    "mediaClass": "string",
    "connectionRate": "string",
    "bitRate": "string",
    "delayTolerance": 0,
    "switchingSubDomainCCIEType": "string",
    "switchingSubDomainInformationElements": "string"
  },
  "participationType": 0,
  "accountCode": {},
  "authCode": "string",
  "correlatorData": {},
  "userData": {},
  "subjectOfCall": "string",
  "languagePreferences": "string"
}

This seems quite a bit different from what I was seeing in the 10.1 swagger page, which was this:

{
  "activeCall": {
    "callID": 0,
    "deviceID": "string"
  },
  "deviceToJoin": "string",
  "participationType": "string"
}

{
  "activeCall": {
    "deviceID": "5580:CM55::0",
    "callID": 462
  },
  "transferredTo": "5590:CM55:0.0.0.0:0"
}

Does anyone have an example of what the body should be for both the ConferenceCall and SingleStepConference? Thanks for any help!!

Have a good day,

Dave

[flynn1]

Starting condition;

• 50500 is in a call with 50501 (CallID 1249).

We want to Single-step 50502 into the call:

Sending WTI request to AES using: /api/fe/v1/SingleStepConferenceCall
{
        "deviceToJoin": "50502:CM181::0",
        "participationType": "active",
        "activeCall": {
                "callID": 1249,
                "deviceID": "50500:CM181::0"
        }
}
======== Incoming WTI Response =============

{"SingleStepConferenceCallResponse": {
        "globallyUniqueCallLinkageID": "00081012491730192407",
        "conferencedCall": {
                "callID": 1249,
                "deviceID": "50502:CM181::0"
        },
        "resultingConnections": {"connection": [
                {
                        "callID": 1249,
                        "deviceID": "50501:CM181::0"
                },
                {
                        "callID": 1249,
                        "deviceID": "50500:CM181::0"
                },
                {
                        "callID": 1249,
                        "deviceID": "50502:CM181::0"
                }
        ]}
}}​

participationType can also be "silent" if you do not want participants to see that they are in a conference. This is typically used for recorders.

[flynn1]

Starting conditions:

• 50500 in Call 1249 (Held) to 50501.
• 50500 in Call 1286 (Active, talking) to 50502

We want to conference the two calls together:

Sending WTI request to AES using: /api/fe/v1/ConferenceCall
{
        "activeCall": {
                "callID": 1286,
                "deviceID": "50500:CM181::0"
        },
        "heldCall": {
                "callID": 1249,
                "deviceID": "50500:CM181::0"
        }
}
======== Incoming WTI Response =============

{"ConferenceCallResponse": {
        "callLinkageData": {"globalCallData": {"globalCallLinkageID": {"globallyUniqueCallLinkageID": "00081012491730192407"}}},
        "conferenceCall": {
                "callID": 1286,
                "deviceID": "50500:CM181::0"
        },
        "connections": {"connectionListItem": [
                {
                        "endpoint": {"deviceID": "50500:CM181::0"},
                        "newConnection": {
                                "callID": 1286,
                                "deviceID": "50500:CM181::0"
                        }
                },
                {
                        "endpoint": {"deviceID": "50502:CM181::0"},
                        "newConnection": {
                                "callID": 1286,
                                "deviceID": "50502:CM181::0"
                        }
                },
                {
                        "endpoint": {"deviceID": "50501:CM181::0"},
                        "newConnection": {
                                "callID": 1286,
                                "deviceID": "50501:CM181::0"
                        }
                }
        ]}
}}​

[avc859587618170]

Awesome!!! Thank you! I can't wait to get this in my POC..

Have a great day and thanks again!

Dave

[avc859587618170]

Quick question.. will these conferences work for an outside number? Or do they only work for internal calls? I'm thinking Single Step won't work for an external number?

Thanks again!!

Dave

[flynn1]

You can conference an outside number into a call using the normal process: hold call, make new call, answer new call and conference the two calls (alternatively, conference before answer).

SSC can only be made to a local station. See the "Single Step Conference Call Service" section of the TSAPI Programmers Guide for full details.

Martin

[avc859587618170]

Thanks again Martin!

Dave

[avc859587618170]

So, I'm finally getting time to work on this.. but i think I'm doing it wrong. So, to make a conference call, I need to:

• Put current call on hold
• Dial new number
• Answer new call
• Conference in old call that's on hold

So, to dial a new number, I need to somehow use the 2nd call appearance? Does that sound right? And if so, how do I do that?

Thanks for any insight!

Dave

[flynn1]

As you are using Third-party features and not First-party, you can just use makeCall. It will use the next available call appearance.

[avc859587618170]

As you are using Third-party features and not First-party, you can just use makeCall. It will use the next available call appearance.

Cool! Thanks Martin!

Dave

[avc859587618170]

Ok, I can't seem to figure this out. So, trying to do a conference call using the "/fe/v1/ConferenceCall" endpoint. So, the below is the json body I'm sending:

{
    "activeCall": {
        "callID": 1034,
        "deviceID": "1234567890:rcd2cm2act81t:0.0.0.0:1"
    },
    "heldCall": {
        "callID": 1004,
        "deviceID": "0987654321:rcd2cm2act81t:0.0.0.0:1"
    }
}

The activeCall is the new call I made and that was answered that I now have active.
The heldCall is the first call I made, which I then put on hold.

I get a 400 BadRequest with the below as the error:

{
    "stateIncompatibility": "invalidConnectionIDForActiveCall"
}​

I do see an error in the dmcc-trace.log that says: "InvalidConnectionIDForActiveCallException: The Call ID in activeCall or heldCall has not be specified correctly: error code 23"

I only have 2 callid's right? One for the call I originally call and put on hold, and the other is for the second call I've made and I'm currently on the phone with. I don't get a different one in there somewhere do I?

Thanks for any insight!

Dave

[flynn1]

At first glance, I would say that the the DeviceID of both the active and held calls must be that of the conference controller - the device making the conference. I presume that the numbers you gave are faked but the fact that they are different makes me think that you are not using the same number for both.

[avc859587618170]

Ooohhh, that seems weird though.. but it worked!! I used the below payload:

{
    "activeCall": {
        "callID": 1046,
        "deviceID": "1234567890:rcd2cm2act81t:0.0.0.0:1"
    },
    "heldCall": {
        "callID": 1045,
        "deviceID": "1234567890:rcd2cm2act81t:0.0.0.0:1"
    }
}

where the deviceid is my avaya lab number I'm using to make all of the calls.

Thanks as always Martin!

Dave

[flynn1]

You should always consult the TSAPI Programmers Reference when you want to know what can and can't be used in requests. You can get a copy by following the instructions in https://support.avaya.com/forums/for...rking-with-wti

[avc859587618170]

You should always consult the TSAPI Programmers Reference when you want to know what can and can't be used in requests. You can get a copy by following the instructions in https://support.avaya.com/forums/for...rking-with-wti

Thanks Martin! I'll download that now.. it looks like a great resource!!

Dave