Chirpstack-gateway-bride with rabbitmq failure

ChirpStack Gateway Bridge
1

Hello,

This is my setup with RAK7371 WisGate Developer Base connected with USB to a RaspberryPi4B

chirpstack-gateway-bridge

cat docker-compose.yml

version: '3.6'
networks:
  loranet:
    external: true
services:
  chirpstack-gateway-bridge:
    image: chirpstack/chirpstack-gateway-bridge:3.14.0
    container_name: gatewaybridge
    hostname: gatewaybridge
    restart: always
    logging:
      options:
        max-size: "10m"
        max-file: "3"
    ports:
      - "1700:1700/udp"
    volumes:
      - ./chirpstack-gateway-bridge.toml:/etc/chirpstack-gateway-bridge/chirpstack-gateway-bridge.toml
    networks:
      loranet:

udp-packet-forwarder

cat docker-compose.yml

version: '3.6'
networks:
  loranet:
    external: true
services:
  udp-packet-forwarder:
    image: rakwireless/udp-packet-forwarder:v1.1.3
    container_name: udpforwarder
    hostname: udpforwarder
    restart: always
    logging:
      options:
        max-size: "10m"
        max-file: "3"
    privileged: true
    volumes:
      - ./global_conf.json:/app/global_conf.json:ro
    environment:
      MODEL: "RAK7371"
      MODULE: "RAK5146"
      CONCENTRATOR: "SX1303"
      HAS_GPS: "0"
      INTERFACE: "USB"
      GATEWAY_EUI: "26E804FFFE7093C0"
      SERVER_HOST: "gatewaybridge.loranet"
      SERVER_PORT: "1700"
      RADIO_DEV: "/dev/ttyACM0"
      GATEWAY_EUI_NIC: "usb0"
      BAND: "us_902_928"
    networks:
      loranet:

RabbitMQ mqtt plugin is enabled, where I see the connection established from chirpstack-gateway-bridge container. A queue is created mqtt-subscription-66C0A7FC63D30000qos0 which confirms successful creation of all the containers and the connection between chirpstack-gateway-bridge and rabbitmq is working.

But when I send data from lora devices I do not see any data received by chirpstack-gateway-bridge or rabbitmq.

Is there any documentation to how to setup wis developer gateway with chirpstack-gateway-bridge and store data to RabbitMQ?

2

Binding amp.topic with this routing key gateway.*.*.* helped fix the issue.

{"gatewayID":"ZsCn/GPTAAA=","state":"ONLINE"}