According to https://code.google.com/p/webrtc/issues/detail?id=2768 ; The Chrome WebRTC engine reserves payload 98 and 99, IKR? So, to avoid taking a nasty spill down the stairs and subjecting ourselves to further school absences, we'll just start our payload space at 102 when making WebRTC calls.......
This commit is contained in:
parent
f9f36993e8
commit
8d2c6b354e
|
@ -6090,8 +6090,11 @@ SWITCH_DECLARE(void) switch_core_media_gen_local_sdp(switch_core_session_t *sess
|
||||||
if (!smh->payload_space) {
|
if (!smh->payload_space) {
|
||||||
int i;
|
int i;
|
||||||
|
|
||||||
|
if (switch_channel_test_flag(session->channel, CF_WEBRTC)) {
|
||||||
smh->payload_space = 98;
|
smh->payload_space = 102;
|
||||||
|
} else {
|
||||||
|
smh->payload_space = 98;
|
||||||
|
}
|
||||||
|
|
||||||
for (i = 0; i < smh->mparams->num_codecs; i++) {
|
for (i = 0; i < smh->mparams->num_codecs; i++) {
|
||||||
smh->ianacodes[i] = smh->codecs[i]->ianacode;
|
smh->ianacodes[i] = smh->codecs[i]->ianacode;
|
||||||
|
|
Loading…
Reference in New Issue