Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No sound in voice call #2854

Open
wangjincheng123-ai opened this issue Nov 14, 2024 · 4 comments
Open

No sound in voice call #2854

wangjincheng123-ai opened this issue Nov 14, 2024 · 4 comments

Comments

@wangjincheng123-ai
Copy link

OpenIM Server Version

3.8.0

Operating System and CPU Architecture

Linux (AMD)

Deployment Method

Source Code Deployment

Issue Description and Steps to Reproduce

公司有两个网段A和B,im所有的服务(报错livekit)部署在B网络下的一台服务器C上,然后域名和B网络的公网ip进行绑定,app使用域名后(连接wifi:无论A网络还是B网络),可正常发送消息, 语音通话在连接B网络(服务器所在网络时),可正常通话, 连接A网络,能拨通语音通话,对方也能接到,但是没有声音传输. B网络公网ip的7880,7881,7882, 50000-60000端口已和B网络下的C服务器上的端口,进行了映射
livekit的启动命令为:
Docker运行-d
-p 7880:7880
p 7881:7881
-p 7882:7882/udp \

  • v $ PWD / livekit / livekit.yaml: / livekit。yaml
    livekit / livekit-server
    ——配置/ livekit。yaml
    ——bind 0.0.0.0
    ——节点ip = B网络公网ip
    chat-rpc-chat.ymal文件的livekit配置如下:
    liveKit:
    url: "ws://B网络公网ip:7880"
    请问语音通话没有声音是怎么回事?

Screenshots Link

No response

@OpenIM-Robot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


OpenIM Server Version

3.8.0

Operating System and CPU Architecture

Linux(AMD)

Deployment Method

Source Code Deployment

Issue Description and Steps to Reproduce

The company has two network segments A and B. All im services (error reporting livekit) are deployed on a server C under the B network, and then the domain name is bound to the public IP of the B network. After the app uses the domain name (connect to wifi : Regardless of network A or B), messages can be sent normally. Voice calls can be made normally when connected to network B (when the server is located). Voice calls can be made when connected to network A, and the other party can also receive it, but there is no sound. transmission. Ports 7880, 7881, 7882, and 50000-60000 of the B network’s public IP address have been mapped to the ports on the C server under the B network.
The startup command of livekit is:
Docker run -d
-p 7880:7880
p 7881:7881
-p 7882:7882/udp \

  • v $PWD/livekit/livekit.yaml:/livekit. yaml
    livekit/livekit-server
    --config/livekit. yaml
    ——bind 0.0.0.0
    ——Node ip = B network public network ip
    The livekit configuration of the chat-rpc-chat.ymal file is as follows:
    liveKit:
    url: "ws://B network public network ip:7880"
    Why is there no sound in voice calls?

Screenshots Link

No response

@OpenIM-Robot OpenIM-Robot changed the title 语音通话没有声音 No sound in voice call Nov 14, 2024
@OpenIM-Robot
Copy link

Hello! Thank you for filing an issue.

If this is a bug report, please include relevant logs to help us debug the problem.

Join slack 🤖 to connect and communicate with our developers.

@wangjincheng123-ai
Copy link
Author

2024-11-14T01:50:27.403Z ERROR livekit service/signal.go:188 could not handle new participant {"room": "8bd4c22e-b664-4b9f-b9f9-babf7a71b8ce", "participant": "4266501388", "connID": "CO_tVHeamG7brg2", "error": "could not restart participant", "errorVerbose": "could not restart participant\ngithub.com/livekit/livekit-server/pkg/service.(*RoomManager).StartSession\n\t/workspace/pkg/service/roommanager.go:368\ngithub.com/livekit/livekit-server/pkg/service.(*defaultSessionHandler).HandleSession\n\t/workspace/pkg/service/signal.go:118\ngithub.com/livekit/livekit-server/pkg/service.(*signalService).RelaySignal\n\t/workspace/pkg/service/signal.go:185\ngithub.com/livekit/psrpc/pkg/server.(*streamHandler[...]).handleOpenRequest\n\t/go/pkg/mod/github.com/livekit/[email protected]/pkg/server/stream.go:202\ngithub.com/livekit/psrpc/pkg/server.(*streamHandler[...]).handleRequest.func1\n\t/go/pkg/mod/github.com/livekit/[email protected]/pkg/server/stream.go:141\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1695"}
github.com/livekit/livekit-server/pkg/service.(*signalService).RelaySignal
/workspace/pkg/service/signal.go:188
github.com/livekit/psrpc/pkg/server.(*streamHandler[...]).handleOpenRequest
/go/pkg/mod/github.com/livekit/[email protected]/pkg/server/stream.go:202
github.com/livekit/psrpc/pkg/server.(*streamHandler[...]).handleRequest.func1
/go/pkg/mod/github.com/livekit/[email protected]/pkg/server/stream.go:141

@OpenIM-Robot
Copy link

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿


2024-11-14T01:50:27.403Z ERROR livekit service/signal.go:188 could not handle new participant {"room": "8bd4c22e-b664-4b9f-b9f9-babf7a71b8ce", "participant": "4266501388", "connID": "CO_tVHeamG7brg2", "error": "could not restart participant", "errorVerbose": "could not restart participant\ngithub.com/livekit/livekit-server/pkg/service.(*RoomManager).StartSession\n\t/workspace/pkg/service/roommanager.go:368\ngithub.com/livekit/livekit-server/pkg/service.(*defaultSessionHandler).HandleSession\n\t/workspace/pkg/service/signal.go:118\ngithub.com/livekit/livekit-server/pkg/service.(*signalService).RelaySignal\n\t/workspace/pkg/service/signal.go:185\ngithub.com/livekit/psrpc/pkg/server.(*streamHandler[...]).handleOpenRequest\n\t/go/pkg/mod/github.com/livekit/[email protected]/pkg/server/stream.go:202\ngithub.com/livekit/psrpc/pkg/server.(*streamHandler[...]).handleRequest.func1\n\t/go/pkg/mod/github.com/livekit/[email protected]/pkg/server/stream.go:141\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1695"}
github.com/livekit/livekit-server/pkg/service.(*signalService).RelaySignal
/workspace/pkg/service/signal.go:188
github.com/livekit/psrpc/pkg/server.(*streamHandler[...]).handleOpenRequest
/go/pkg/mod/github.com/livekit/[email protected]/pkg/server/stream.go:202
github.com/livekit/psrpc/pkg/server.(*streamHandler[...]).handleRequest.func1
/go/pkg/mod/github.com/livekit/[email protected]/pkg/server/stream.go:141

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants