利用coturn部署stun/turn服务器时遇到问题

我利用coturn在3478端口部署了STUN/TURN服务器，并在安全组设置了入方向和出方向的端口对全部流量进行全部开放，并且关闭了防火墙的限制，但是我的TURN服务器依然不可用（可以发送ICE请求，但是功能不可用）。有没有大佬能够解决？谢了

启动TURN服务的命令

/usr/local/turnserver/bin/turnserver -v -r 47.94.53.126 -a -o -c /usr/local/turnserver/share/examples/turnserver/etc/turnserver.conf

具体配置

listening-port=3478
listening-ip=172.18.61.183
tls-listening-port=5349 # TLS 加密端口
cert=/ssl/cert.pem
pkey=/ssl/cert.key
external-ip=47.94.53.126
user=user:654321
realm=47.94.53.126

lt-cred-mech
relay-ip=0.0.0.0

min-port=49152
max-port=65535


verbose
log-file=/var/log/turnserver.log

部分日志

696: session 001000000000000010: realm <47.94.53.126> user <user>: incoming packet BINDING processed, success
696: session 001000000000000011: realm <47.94.53.126> user <user>: incoming packet BINDING processed, success
706: session 001000000000000010: realm <47.94.53.126> user <user>: incoming packet BINDING processed, success
706: session 001000000000000011: realm <47.94.53.126> user <user>: incoming packet BINDING processed, success
716: session 001000000000000010: realm <47.94.53.126> user <user>: incoming packet BINDING processed, success
716: session 001000000000000011: realm <47.94.53.126> user <user>: incoming packet BINDING processed, success
726: session 001000000000000010: realm <47.94.53.126> user <user>: incoming packet BINDING processed, success
726: session 001000000000000011: realm <47.94.53.126> user <user>: incoming packet BINDING processed, success
736: session 001000000000000010: realm <47.94.53.126> user <user>: incoming packet BINDING processed, success
736: session 001000000000000011: realm <47.94.53.126> user <user>: incoming packet BINDING processed, success
743: session 001000000000000010: refreshed, realm=<47.94.53.126>, username=<user>, lifetime=0
743: session 001000000000000010: realm <47.94.53.126> user <user>: incoming packet REFRESH processed, success
743: session 001000000000000011: refreshed, realm=<47.94.53.126>, username=<user>, lifetime=0
743: session 001000000000000011: realm <47.94.53.126> user <user>: incoming packet REFRESH processed, success
744: session 001000000000000010: usage: realm=<47.94.53.126>, username=<user>, rp=22, rb=1160, sp=22, sb=1888
744: session 001000000000000010: closed (2nd stage), user <user> realm <47.94.53.126> origin <>, local 172.18.61.183:3478, remote 36.112.200.70:30675, reason: allocation timeout
744: session 001000000000000010: delete: realm=<47.94.53.126>, username=<user>
744: session 001000000000000010: peer 172.17.0.1 deleted
744: session 001000000000000010: peer 36.112.200.70 deleted
744: session 001000000000000010: peer 10.24.68.63 deleted
744: session 001000000000000010: peer 47.94.53.126 deleted
744: session 001000000000000011: usage: realm=<47.94.53.126>, username=<user>, rp=22, rb=1160, sp=22, sb=1888
744: session 001000000000000011: closed (2nd stage), user <user> realm <47.94.53.126> origin <>, local 172.18.61.183:3478, remote 36.112.200.70:30676, reason: allocation timeout
744: session 001000000000000011: delete: realm=<47.94.53.126>, username=<user>
744: session 001000000000000011: peer 172.17.0.1 deleted
744: session 001000000000000011: peer 36.112.200.70 deleted
744: session 001000000000000011: peer 10.24.68.63 deleted
744: session 001000000000000011: peer 47.94.53.126 deleted