cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

[Intermittent issue] - Zoom server sends composite content even though BFCP enabled for SIP meeting

RoomAppUser
Newcomer
Newcomer

‎2023-07-11 01:08 AM - edited ‎2023-07-11 02:34 AM

I observe an intermittent issue in a conference where zoom server sends composite content(content and video are merged as one stream) even though Room system application negotiated BFCP and bfcp hello being responded by server.

Setup - 
1. Room System app
2. Zoom Desktop client

Scenario - Zoom desktop client joins the conference as a first participant and started sharing content in meeting. Now Room App joins the conference as a second participant.

NOTE - Composite content issue can be observed at any time - during hijacks, Zoom joined existing conference and started sharing.  

Issue - Sometime Zoom server sends composite content even though BFCP hello messages sent by Room App being acknowledged.  

INVITE from Room System App at time 12:26:42.544 - 

INVITE sip:*********** SIP/2.0
Via: SIP/2.0/TLS x.x.x.x:46094;rport;branch=z9hG4bKPjdf1ea7b5-776b-4356-9f07-a6e890c8a722;alias
Max-Forwards: 70
From: "RoomAPP" <sip:***********>;tag=1ee40a7a-460c-4be7-8324-c72fff4083f8
To: sip:***********
Contact: "RoomAPP" <sip:RoomAPP@x.x.x.x:46094;transport=TLS;ob>
Call-ID: f292268d-bd8d-4681-a296-76a90b48f6ab
CSeq: 31537 INVITE
Route: <sip:zoomcrc.com:5061;transport=tls;lr>
Content-Type: application/sdp

v=0
o=- 3898047402 3898047402 IN IP4 x.x.x.x
s=pjmedia
b=AS:3981
t=0 0
a=X-nat:0
m=audio 5000 RTP/SAVP 8 0 9 120
/* Audio SDP */
m=video 5002 RTP/SAVP 97
c=IN IP4 x.x.x.x
b=TIAS:1856000
a=rtcp:5003 IN IP4 x.x.x.x
a=sendrecv
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=42e01f; packetization-mode=1;max-mbps=108000;max-fs=3600;max-fps=3000
a=content:main
a=label:11
a=framerate:30.0
a=ssrc:1669027275 cname:11e6c62907144b2a
a=crypto:1 AES_256_CM_HMAC_SHA1_80 inline:RNR1qKl9b3aXaj3XtBtV46wgDiMgNyRPknSzI44Sl9w3Fsxj1M6x2+KdMvkmKQ==
a=crypto:2 AES_256_CM_HMAC_SHA1_32 inline:nOCIT27b6HwXDeeMsRtJvgg3oWTJpItvs/XmL0hvd1Fv9YnmyxiAIaGnYqULyg==
a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:ZNZU8Vu2J7yq/yEwvod6go6RH3K9kr7PLBWxtSZm
a=crypto:4 AES_CM_128_HMAC_SHA1_32 inline:5LVaU2ednEne4NpKE7kojxiLpOPsT5MfFgIunI6Q
a=rtcp-fb:* nack pli
m=video 5004 RTP/SAVP 97
c=IN IP4 x.x.x.x
b=TIAS:1856000
a=rtcp:5005 IN IP4 x.x.x.x
a=sendrecv
a=rtpmap:97 H264/90000
a=fmtp:97 profile-level-id=428028; packetization-mode=1;max-mbps=245760;max-fs=8192;max-fps=3000
a=content:slides
a=label:12
a=framerate:30.0
a=ssrc:1783907843 cname:11e6c62907144b2a
a=crypto:1 AES_256_CM_HMAC_SHA1_80 inline:m/AxRL1iOoDc9Vo/FjC/WjLqu+5JnY+BfKJXJQHiBZCpvzJFEgx44x3nNOvu0w==
a=crypto:2 AES_256_CM_HMAC_SHA1_32 inline:bj7VnUzDeB2PrrAldAdrpEhCvwvFSstXzNHNet4SNYJVjYzal9ZnVnBrfJqA/w==
a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:Qa++NTzH/U5auK8Mfk3Hr2E7+ENhnugsZBMOzkHq
a=crypto:4 AES_CM_128_HMAC_SHA1_32 inline:pZTrM7ChJjCp1wL9sf8fFedwF5xC5351dTl7B+Qv
a=rtcp-fb:* nack pli
m=application 5006 UDP/BFCP *
c=IN IP4 x.x.x.x
a=floorctrl:c-only
a=floorid:6 mstrm:12
a=connection:new
a=setup:active


200 OK received from Zoom server at time 12:26:43.519 - 

 

SIP/2.0 200 OK 

Via: SIP/2.0/TLS 10.5.6.63:46094;rport=13592;branch=z9hG4bKPjdf1ea7b5-776b-4356-9f07-a6e890c8a722;received=162.255.37.96;alias
Contact: <sip:xyz.abc@162.255.37.178:5061;transport=tls>;isfocus
To: <sip:***********>;tag=b7c80c05
From: "RoomAPP"<sip:***********>;tag=1ee40a7a-460c-4be7-8324-c72fff4083f8
Call-ID: f292268d-bd8d-4681-a296-76a90b48f6ab
CSeq: 31537 INVITE
Min-SE: 90
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, UPDATE, INFO, REFER, NOTIFY, OPTIONS, MESSAGE, UPDATE
Content-Type: application/sdp
Server: Room Connector Controller,Version: 2.7.100,BuildTime: 2023/05/26 07:40:03
Content-Length: 1824

v=0
o=ZoomRC 101816 101816 IN IP4 4.35.64.191
s=ZoomRC
c=IN IP4 4.35.64.191
b=AS:1920
t=0 0
m=audio 3576 RTP/SAVP 114 9 0 8 101
/* Audio SDP */
m=video 3578 RTP/SAVP 109 110 111
b=TIAS:1920000
a=rtpmap:109 H264/90000
a=fmtp:109 profile-level-id=42801f;packetization-mode=0;max-mbps=270000;max-smbps=270000;max-fps=3000
a=rtpmap:110 H264/90000
a=fmtp:110 profile-level-id=42801f;packetization-mode=1;max-mbps=270000;max-smbps=270000;max-fps=3000
a=rtpmap:111 H264/90000
a=fmtp:111 profile-level-id=64801f;packetization-mode=1;max-mbps=270000;max-smbps=270000;max-fps=3000
a=sendrecv
a=rtcp-fb:* nack pli
a=rtcp-fb:* ccm fir
a=rtcp-fb:* ccm tmmbr
a=crypto:1 AES_256_CM_HMAC_SHA1_80 inline:Onlb6Fh1TK9m9wE2hMdl2PokurMwWgpZyNLdw9enlb7ZvkTEinPcZNhcS8oO6A==|2^48
a=content:main
a=label:1
a=answer:full
m=video 3580 RTP/SAVP 109 110
b=TIAS:960000
a=rtpmap:109 H264/90000
a=fmtp:109 profile-level-id=428028;packetization-mode=0;max-mbps=216000;max-smbps=216000;max-fs=8192;max-fps=3000
a=rtpmap:110 H264/90000
a=fmtp:110 profile-level-id=648028;packetization-mode=1;max-mbps=216000;max-smbps=216000;max-fs=8192;max-fps=3000
a=sendrecv
a=rtcp-fb:* nack pli
a=rtcp-fb:* ccm fir
a=rtcp-fb:* ccm tmmbr
a=crypto:1 AES_256_CM_HMAC_SHA1_80 inline:OSKM3bVVnqbdFIiPSiLnVgNnrvPJJJIYFpfliIF3vU4tQMJY7qFi9fCu10AZiQ==|2^48
a=content:slides
a=label:2
a=answer:full
m=application 3584 UDP/BFCP *
a=floorctrl:s-only
a=confid:1
a=floorid:6 mstrm:2
a=userid:2
a=setup:passive
a=connection:new


Then ACK is sent by RoomApp at 12:26:43.610
ACK sip:xyz.abc@162.255.37.178:5061;transport=tls SIP/2.0

BFCP Hello from RoomsApp at 12:26:43.728 (not responded by server) - 
BFCP SendBFCPMessage: Primitive: eHello CommonHdr { version: 1 length: 0 confId: 1 transId: 61 userId: 2 }

Again BFCP Hello from RoomsApp at an interval of 100 ms at 12:26:43.830
BFCP SendBFCPMessage: Primitive: eHello CommonHdr { version: 1 length: 0 confId: 1 transId: 62 userId: 2 }

Again BFCP Hello from RoomsApp at an interval of 100 ms at 12:26:43.932
BFCP SendBFCPMessage: Primitive: eHello CommonHdr { version: 1 length: 0 confId: 1 transId: 63 userId: 2 }

 

Again BFCP Hello from RoomsApp at an interval of 100 ms  (not responded in 100 ms) at 12:26:43.830
BFCP SendBFCPMessage: Primitive: eHello CommonHdr { version: 1 length: 0 confId: 1 transId: 62 userId: 2 }

Received Fast update over SIP INFO at 12:26:44.013- 
INFO sip:BJNSIP@10.5.6.63:46094;transport=TLS;ob SIP/2.0

/* Omitting other headers */

Content-Type: application/media_control+xml
Server: Room Connector Controller,Version: 2.7.100,BuildTime: 2023/05/26 07:40:03
Content-Length: 220

<?xml version="1.0" encoding="utf-8" ?>
<media_control>
<vc_primitive>
<to_encoder>
<picture_fast_update>
<media_stream>
11</media_stream>
</picture_fast_update>
</to_encoder>
</vc_primitive>
</media_control>

SIP/2.0 200 OK from RoomApp at 12:26:44.015

 

Again BFCP Hello from RoomApp at an interval of 100 ms at12:26:44.034
BFCP SendBFCPMessage: Primitive: eHello CommonHdr { version: 1 length: 0 confId: 1 transId: 64 userId: 2 }


Server responded to BFCP hello messages at (12:26:44.049, 12:26:44.150, 12:26:44.253)

BFCP OnReceiveData: Primitive: eHelloAck CommonHdr { version: 1 length: 10 confId: 1 transId: 62 userId: 2 }
BFCP OnReceiveData: Primitive: eHelloAck CommonHdr { version: 1 length: 10 confId: 1 transId: 63 userId: 2 }
BFCP OnReceiveData: Primitive: eHelloAck CommonHdr { version: 1 length: 10 confId: 1 transId: 64 userId: 2 }

 

0 Likes
0 REPLIES 0