turn/stun服务器

[Daghe]

使用推荐的coturn服务器部署在公网

/etc/turnserver.conf配置如下

listen-port = 3478 listen
-ip =公网ip    
external-ip =  公网ip 
relay-device = eth0
listen-device = eth0
relay-ip =  公网ip 
min-port = 49152＃“连接使用最小端口”
max-端口= 65535＃“连接使用最大端口”

lt-cred-mech
user = ling：0xccba8f3a6a025a38eb4a0e795fc92705
userdb = / etc / turnuserdb.conf
realm = demo
stale-nonce
cert = / etc / turn_server_cert.pem pkey
= / etc / turn_server_pkey.pem
use-auth-secret
no-loopback-peers
no-multicast-peers
移动性
no-cli

使用电信4G能够显示混合流画面，移动与联通4克无法显示，是穿透服务器的问题，日志如下

2940394: session 008000000000001435: usage: realm=<demo>, username=<>, rp=2, rb=48, sp=2, sb=156
2940394: session 008000000000001435: closed (2nd stage), user <> realm <demo> origin <>, local 223.112.90.172:3478, remote 117.136.46.217:53953, reason: allocation watchdog determined stale session state
2940395: session 001000000000001534: usage: realm=<demo>, username=<>, rp=2, rb=48, sp=2, sb=156
2940395: session 001000000000001534: closed (2nd stage), user <> realm <demo> origin <>, local 223.112.90.172:3478, remote 117.136.46.217:53954, reason: allocation watchdog determined stale session state
2940395: session 003000000000001259: usage: realm=<demo>, username=<>, rp=0, rb=0, sp=0, sb=0
2940395: session 003000000000001259: closed (2nd stage), user <> realm <demo> origin <>, local 223.112.90.172:3478, remote 117.136.46.217:40559, reason: allocation watchdog determined stale session state
2940403: session 008000000000001436: usage: realm=<demo>, username=<>, rp=2, rb=48, sp=2, sb=156
2940403: session 008000000000001436: closed (2nd stage), user <> realm <demo> origin <>, local 223.112.90.172:3478, remote 117.136.46.217:53956, reason: allocation watchdog determined stale session state
2940403: session 000000000000001747: usage: realm=<demo>, username=<>, rp=2, rb=48, sp=2, sb=156
2940403: session 000000000000001747: closed (2nd stage), user <> realm <demo> origin <>, local 223.112.90.172:3478, remote 117.136.46.217:53957, reason: allocation watchdog determined stale session state
2940412: session 000000000000001750: usage: realm=<demo>, username=<>, rp=1, rb=20, sp=1, sb=72
2940412: session 000000000000001750: closed (2nd stage), user <> realm <demo> origin <>, local 223.112.90.172:3478, remote 58.210.137.42:56187, reason: allocation watchdog determined stale session state
2940634: session 001000000000001533: peer 10.5.231.17 deleted
2940634: session 000000000000001746: peer 10.5.231.17 deleted
2940635: session 004000000000001122: peer 10.5.231.17 deleted
2940635: session 002000000000001152: peer 10.5.231.17 deleted
2940643: session 005000000000001106: peer 10.5.231.17 deleted
2940643: session 006000000000001570: peer 10.5.231.17 deleted
2940643: session 001000000000001535: peer 10.5.231.17 deleted
2940643: session 008000000000001437: peer 10.5.231.17 deleted
2940652: session 003000000000001260: peer 10.5.231.17 deleted
2940934: session 001000000000001533: usage: realm=<demo>, username=<ling>, rp=56, rb=7300, sp=4, sb=316
2940934: session 001000000000001533: closed (2nd stage), user <ling> realm <demo> origin <>, local 223.112.90.172:3478, remote 117.136.46.217:53952, reason: allocation timeout
2940934: session 001000000000001533: delete: realm=<demo>, username=<ling>
2940934: session 000000000000001746: usage: realm=<demo>, username=<ling>, rp=54, rb=7144, sp=3, sb=244
2940934: session 000000000000001746: closed (2nd stage), user <ling> realm <demo> origin <>, local 223.112.90.172:3478, remote 117.136.46.217:40558, reason: allocation timeout
2940934: session 000000000000001746: delete: realm=<demo>, username=<ling>
2940935: session 004000000000001122: usage: realm=<demo>, username=<ling>, rp=49, rb=6348, sp=4, sb=316
2940935: session 004000000000001122: closed (2nd stage), user <ling> realm <demo> origin <>, local 223.112.90.172:3478, remote 117.136.46.217:53955, reason: allocation timeout
2940935: session 004000000000001122: delete: realm=<demo>, username=<ling>
2940935: session 002000000000001152: usage: realm=<demo>, username=<ling>, rp=48, rb=6328, sp=3, sb=244
2940935: session 002000000000001152: closed (2nd stage), user <ling> realm <demo> origin <>, local 223.112.90.172:3478, remote 117.136.46.217:40560, reason: allocation timeout
2940935: session 002000000000001152: delete: realm=<demo>, username=<ling>
2940943: session 005000000000001106: usage: realm=<demo>, username=<ling>, rp=5, rb=364, sp=4, sb=316
2940943: session 005000000000001106: closed (2nd stage), user <ling> realm <demo> origin <>, local 223.112.90.172:3478, remote 117.136.46.217:53958, reason: allocation timeout
2940943: session 005000000000001106: delete: realm=<demo>, username=<ling>
2940943: session 006000000000001570: usage: realm=<demo>, username=<ling>, rp=5, rb=364, sp=4, sb=316
2940943: session 006000000000001570: closed (2nd stage), user <ling> realm <demo> origin <>, local 223.112.90.172:3478, remote 117.136.46.217:53959, reason: allocation timeout
2940943: session 006000000000001570: delete: realm=<demo>, username=<ling>
2940943: session 001000000000001535: usage: realm=<demo>, username=<ling>, rp=4, rb=344, sp=3, sb=244

[dandy__kiven]

hello,Daghe:

I use Android P2P for intercom, LAN is ok, but I can't post my own video using data traffic, this should be a problem with the turn server. I have a problem that I don't configure the turn server. The most important thing is that I know where to configure my turn server, I hope to get help.

Thank you very much for your patience. If the details are not clear, the ntel team hopes to get friendly help.

You can contact my email and exchange: 1213126651@qq.com. I will reply as soon as possible. Thanks to the Intel team, I hope to get friendly help.

我使用安卓P2P进行对讲，局域网是没问题的，但是使用数据流量就不能发布自己视频，这应该是turn服务器的问题。我存在不会配置turn服务器的问题，最重要的是我知道在哪里配置指向我的turn服务器，希望得到帮助

可以联系我的邮箱并交流：1213126651@qq.com。我会第一时间做出回复。感谢 I