Not sure if this is a bug or user error yet, too green on ARI. I’m working on making outbound calls via the REST API, and I’m seeing the following:
- Call is created by making a POST to /ari/channels
– Exact example:POST http://127.0.0.1:8088/ari/channels?app=hello-world&channelId=MOHCalling.789cd73a-9fd1-47c3-add7-711b6058260c&endpoint=PJSIP/1230&timeout=15
- PJSIP device rings
- Callee answers and hangs up
- No hangup event is registered, and the channel remains up
From the console logs:
[Feb 17 00:14:02] == WebSocket connection from '127.0.0.1:49554' closed
[Feb 17 00:14:04] Creating Stasis app 'hello-world'
[Feb 17 00:14:04] == WebSocket connection from '127.0.0.1:37202' for protocol '' accepted using version '13'
[Feb 17 00:14:07] -- Called 1230
[Feb 17 00:14:07] -- PJSIP/1230-00000002 is ringing
[Feb 17 00:14:10] -- PJSIP/1230-00000002 answered
[Answer call and hang up]
*CLI> Core show channels
Channel Location State Application(Data)
PJSIP/1230-00000002 s@user_context_1200:1 Up Stasis(hello-world)
1 active channel
0 active calls
0 calls processed
The last event I get over the websocket is "type": "StasisStart"
. No event when the callee hangs up. Since I’m still in the early phases of writing a client my app doesn’t really do much yet, I’ve tried 3 actions when the Stasis app starts:
- Nothing
- Answer
- Start MOH
All 3 behave the same. If I don’t put a timeout in my app to explicitly hangup the channel then the channel appears to stay open forever.
Is there something special I should know here I’m not seeing in the docs, or is this a bug? Asterisk 20.6.0.