Signaling Service
# Introduction
To communicate with another peer you simply need to exchange contact information and the rest will be done by WebRTC. The process of connecting to the other peers is also known as signaling.
Peers with different signaling address can not connect to each other.
# Deploy by Yourself
Deploy your own Signaling Service (Recommended)
- cbsignal (Golang)
cbsignal disables zlib compression by default. You can turn on compression in config.yaml .
# Use free Signaling Service
- 'wss://signal.cdnbye.com' (HongKong,default)
- 'wss://opensignal.cdnbye.com' (America)
- 'wss://signalcloud.cdnbye.com' (Germany)
- wss://signal.p2pengine.net:8089 (Russia)
# Change Signaling Address
# Via Console (Recommended)
- Log on Console
- Click on the Signal Management button in the P2P Setting
- Input your signaling address and conform
# Via SDK Config
# Web SDK
p2pConfig: {
wsSignalerAddr: 'ws://your.signalservice.com',
// Other p2pConfig options provided by cdnbye
}
// Pass p2pConfig to your P2PEngine ...
# Android SDK
P2pConfig config = new P2pConfig.Builder()
.wsSignalerAddr("ws://your.signalservice.com")
.build();
P2pEngine.initEngine(ctx, YOUR_TOKEN, config);
# iOS SDK
CBP2pConfig *config = [CBP2pConfig defaultConfiguration];
config.wsSignalerAddr = @"ws://your.signalservice.com";
self.engine = [[CBP2pEngine alloc] initWithToken:YOUR_TOKEN andP2pConfig:config];
# Flutter SDK
Cdnbye.init(
YOUR_TOKEN,
config: P2pConfig(
wsSignalerAddr: 'ws://your.signalservice.com',
)
);