AIR originate not placing call into dialplan as expected

Asterisk Asterisk APIs
1

I am trying to originate a channel to a user (call extension 410), and send the channel directly into a conference bridge (dialplan) using the ARI with the following parameters:

            endpoint: PJSIP/410/sip:410@172.31.253.20;port=5060
             context: ext-meetme
           extension: 2663
            priority: 1
               label: ADMIN
             timeout: 10
           channelId: Conf_Bridge_0_Channel_0
            callerId: "My Conf" <Test>

So I send the following string to the /channels URI:

endpoint=PJSIP/410/sip:410@172.31.253.20;port%3D5060&context=ext-meetme&extension=2663&priority=1&label=ADMIN&callerId=%22My%20Conf%22%20%3CTest%3E&timeout=10&channelId=Conf_Bridge_0_Channel_0

The command succeeds, but the call doesn’t appear in the dialplan as expected. The websocket response below suggests the call is not going into the dialplan at the context/extension/priority/label I specified in the URI parameters. Why not?

{
    "application": "asteriskcontroller",
    "asterisk_id": "54:b2:03:10:1f:3a",
    "channel": {
        "accountcode": "",
        "caller": {
            "name": "Test Phone",
            "number": "410"
        },
        "connected": {
            "name": "",
            "number": ""
        },
        "creationtime": "2025-05-02T09:55:33.864-0400",
        "dialplan": {
            "app_data": "",
            "app_name": "",
            "context": "from-internal",
            "exten": "s",
            "priority": 1
        },
        "id": Conf_Bridge_0_Channel_0",
        "language": "en",
        "name": "PJSIP/410-00000086",
        "protocol_id": "",
        "state": "Down"
    },
    "timestamp": "2025-05-02T09:55:33.864-0400",
    "type": "ChannelCreated"
}
2

The call will only go to the dialplan upon answer. Was it answered? The output you’ve provided is of a channel in down state.

3

Ok - I assumed the first websocket response indicated a problem, but as I followed the chain of websocket responses I see it is working.