ARI-Proxy (docker image) and RabbitMQ

[ramrui]

Hello,

I'm trying to send commands from RabbitMQ client (and also from RabbitMQ UI) without success.

Using ari.request exchange, and Routing key with ari.command.<app_name> or ari.command.<app_name>.<asterisk_id>.

I tried various JSONs like:

{
"type": "ChannelHangupRequest",
"channel": "<channel_id>",
"cause": 16
}

or

{
"method": "DELETE",
"path": "/channels/<channel_id>",
"params": {}
}

or

{
"resource": "channels",
"operation": "hangup",
"args": {
"channelId": "<channel_id>",
"cause": 16
}
}

without success.

I assume the message is arriving via AR Proxy, since if the JSON is malformed I get an error in Docker:

t=2026-02-25T17:28:48+0000 lvl=eror msg="Error unmarshall data" topics="[ari.get ari.get.app_bot_nos_rt ari.get.app_bot_nos_rt.00:50:56:96:e5:b9 ari.data ari.data.app_bot_nos_rt ari.data.app_bot_nos_rt.00:50:56:96:e5:b9 ari.command ari.command.app_bot_nos_rt ari.command.app_bot_nos_rt.00:50:56:96:e5:b9]" error="invalid character 's' looking for beginning of object key string"

I dont know if it is possible to increase ari-proxy logs.

Thanks for the help.

[Ulexus]

Unmarshalling errors are notoriously difficult to debug. It is usually easiest to log the data just before the unmarshalling attempt, you that you can see what it look like. Since it is complaining about the first character being 's', it is clearly not JSON. Most likely, it is some other error message that is being received instead of the JSON payload. If you read that message, it will likely give you the key insight you need.

[ramrui]

Thanks for your quick answer...
My problem is not the "unmarshall" error...

I used the example only to show that the published message reaches the ARI Proxy.

After correcting the JSON error, the ARI Proxy stopped giving errors.

But I can't see the message reaching Asterisk.

I'm trying to send a command to disconnect the call.

I don't know if I'm creating the JSON with the correct syntax, or if I'm missing something.

[Ulexus]

Are you supplying an ari.Client, or are you letting it provide its own?
You can increase the logging by supplying your own log15-compatible logger, to the Server.

ari-proxy/server/server.go

Lines 44 to 45 in 38a40c1

	// Log is the log15.Logger for the service. You may replace or call SetHandler() on this at any time to change the logging of the service.
	Log log15.Logger

By default, it discards all log messages.

[Ulexus]

Both ari.Client and ari-proxy.Server provide these logging hookups.

[ramrui]

I'm using ari-proxy on docker Proxy Server, running like this:

docker run
-e ARI_APPLICATION="my_test_app"
-e ARI_USERNAME="demo-user"
-e ARI_PASSWORD="supersecret"
-e ARI_HTTP_URL="http://<asterisk_server>:8088/ari"
-e ARI_WEBSOCKET_URL="ws://<asterisk_server>:8088/ari/events"
-e MESSAGEBUS_URL="amqp://<rabbitmq_server>:5672"
cycoresystems/ari-proxy:latest

To check the logs I'm using "docker logs -f ari-proxy"

I have a client connected to rabbitmq.

At this moment I'm publish the message using the UI of RabbitMQ.

[Ulexus]

Try running with VERBOSE=1

ari-proxy/cmd.go

Line 37 in 38a40c1

if viper.GetBool("verbose") {

[ramrui]

I'm just using the proxy server ari-proxy, docker image, not using the source code.

My question is about publish commands from RabbitMQ, for example to realese a call.

If I'm using the correct Exchange, routing key, and JSON content.

[Ulexus]

Yes, I understand. Run it with the additional environment variable VERBOSE=1. I was just giving you the code reference for context.

[ramrui]

Ok, great... sorry my misunderstood
With VERBOSE=1 I can see the requests arriving to ARI Proxy from RabbitMQ:

t=2026-02-26T01:53:13+0000 lvl=info msg="verbose logging enabled"
t=2026-02-26T01:53:13+0000 lvl=info msg="starting ari-proxy server" version=5.3.1
t=2026-02-26T01:53:13+0000 lvl=dbug msg="starting listener"
t=2026-02-26T01:53:13+0000 lvl=dbug msg="listening for events" application=app_bot_nos_rt
t=2026-02-26T01:58:38+0000 lvl=dbug msg="event received" kind=StasisStart
t=2026-02-26T01:58:38+0000 lvl=dbug msg="listening for events" application=app_bot_nos_rt
t=2026-02-26T01:58:43+0000 lvl=dbug msg="received request" kind= <---- REQUESTS
t=2026-02-26T02:00:01+0000 lvl=dbug msg="received request" kind=
t=2026-02-26T02:00:31+0000 lvl=dbug msg="received request" kind=
t=2026-02-26T02:00:48+0000 lvl=dbug msg="received request" kind=

But only with this information...

[Ulexus]

I've never used RabbitMQ, but with NATS, you can run it in debug mode, which will show the messages sent over the wire. Can you do something similar with RabbitMQ? Otherwise, my next step would be to add debugging to the ari-proxy server code, as indicated above.

[ramrui]

According to file ari-proxy/server/server.go, on line 340 I have a switch to "select" the kind...

	s.Log.Debug("received request", "kind", req.Kind)
	switch req.Kind {
	case "ApplicationData":
		f = s.applicationData

I believe to realease the call kind should be ChannelHangup.
On the log I should see something like:

t=2026-02-26T02:00:48+0000 lvl=dbug msg="received request" kind=ChannelHangup

My doubt is the JSON format of the request that I need to sent from RabbitMQ to ARI

[ramrui]

Using this payload:

{
"kind": "ChannelHangup",
"channel": "1772034025.107"
}

I've got on the logs:

t=2026-02-26T23:17:58+0000 lvl=dbug msg="received request" kind=
t=2026-02-26T23:21:30+0000 lvl=dbug msg="received request" kind=ChannelHangup
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x873147]

goroutine 38 [running]:
github.com/CyCoreSystems/ari-proxy/v5/server.(*Server).channelHangup(0xc00015aa00, {0x10?, 0x4?}, {0x0, 0x0}, 0xc0002a1200)
/home/runner/work/ari-proxy/ari-proxy/server/channel.go:95 +0x47
github.com/CyCoreSystems/ari-proxy/v5/server.(*Server).dispatchRequest(0xc00015aa00, {0xb7e430, 0xc000100820}, {0x0, 0x0}, 0xc0002a1200)
/home/runner/work/ari-proxy/ari-proxy/server/server.go:570 +0x2904
created by github.com/CyCoreSystems/ari-proxy/v5/server.(*Server).listen.(*Server).newRequestHandler.func2 in goroutine 50
/home/runner/work/ari-proxy/ari-proxy/server/server.go:331 +0xf5

[Ulexus]

That's definitely not a valid payload. You need to add the actual ChannelHangup field. The crash is because when it parsed the request, the ChannelHangup field was empty, hence the nil, hence the crash.

You would need to, at a minimum, have:

{
  "kind": "ChannelHangup",
  "channel": "1772034025.107",
  "channel_hangup": {
    "reason": "some reason"
  }
}