Jabber Guest screen sharing not working on iPads

[mattio]

I've been working with the Jabber Guest SDK to add support for screen sharing recently. It works well on iPhones, but it seems to be failing on iPads. Of the two I have for testing, one is an older model iPad Mini 2 and one is a relatively new iPad. Both are running iOS 12.

When screen sharing starts on the iPad, the CJGuestCallRemotePresoVideoActiveNotification notification is received, but the CJGuestCallRemotePresoVideoStartedNotification is not. It's the same exact code when run on an iPhone -- no branching or device detection at all -- and both notifications are called as expected.

After some testing, I decided to download the Jabber Guest app from the Apple App Store. The same issue exists. Screen sharing works fine on an iPhone but doesn't on an iPad. On the iPad, the loading view appears, but the shared screen never appears.

Is this a known issue? If it is, will it be fixed in a release soon? Are there any work-arounds? 

Thanks,

Mattio

[Ratheesh Kumar]

Hi there

Are you using the same SIP profile for iPhones and iPads

Please check this

Don't See Screen Share in Production Deployment
Problem Callers don't see the screen share.
Possible Cause User Datagram Protocol (UDP)/Binary Floor Control Protocol (BFCP) settings have changed and the BFCP session may not be negotiated.
Solution On the Cisco Expressway-C, make sure that SIP UDP/BFCP filter mode is set to Off. On Cisco Unified Communications Manager, for endpoints that support BFCP and SIP trunk to Cisco Expressway-C, make sure that the SIP Profile is set to Allow Presentation Sharing using BFCP. For more information, see Check BFCP Settings for Screen Sharing.
Check BFCP Settings for Screen Sharing
Related Tasks
Check BFCP Settings for Screen Sharing
Check BFCP Settings for Screen Sharing
By default, Cisco Expressway-C passes the User Datagram Protocol (UDP)/Binary Floor Control Protocol (BFCP) setting untouched to and from Cisco Unified Communications Manager. That is, the SIP UDP BFCP filter mode setting, which determines whether INVITE requests sent to this zone filter out UDP/BFCP is set to Off. If the setting is set to On, UDP/BFCP settings are modified and the BFCP session may not be negotiated.

Procedure
Step 1 On the Cisco Expressway-C setting, do one of the following:
>From the administrator command-line interface, enter the following command:
xConfiguration Zones Zone Neighbor SIP UDP BFCP Filter Mode:
Make sure that SIP UDP/BFCP filter mode is set to Off.
Off means that INVITE requests are not modified; On means that any media line referring to the UDP/BFCP protocol is replaced with TCP/BFCP and disabled.
>From the administrator web page, "Configuration Zones Edit Zones Advanced," set the profile to Custom and make sure that SIP UDP/BFCP filter mode is set to Off.
Step 2 On Cisco Unified Communications Manager, for endpoints that support BFCP and SIP trunk to Cisco Expressway-C, make sure that the SIP Profile is set to Allow Presentation Sharing using BFCP.
Don't See Screen Share in Lab Deployment
Problem In a lab deployment in which Cisco Jabber Guest is pointed directly to Cisco Unified Communications Manager, without configuring Expressway, callers see a black screen instead of the screen share.
Possible Cause The media stream is blocked by a firewall.
Solution Enable a client-side firewall rule to allow the incoming screen share.

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/Guest/11_0/icg/jabc_b_installation-and-configuration-guide-for/jabc_b_installation-and-configuration-guide-for_chapter_0110.html

Hope this helps
Cheers
Rath!

***Please rate helpful posts***

[mattio]

I'll forward this to the system admins for review, but nothing in that document suggests there are different configurations by device -- that there's one setting for iPhones and another for iPads. For the same code, and even in the Jabber Guess iOS app itself, screen share works on an iPhone but fails on an iPad.

[mattio]

After a lot of trial and error, this seems to be related to self view.

Originally I called startSelfView on CJGuestCall within viewWillAppear. That would allow the user to see themselves before starting a call. What I found was that I needed to call [[CJGuestCall sharedInstance] stopSelfView] when the user starts a call, then call startSelfView again after the call is connected, then screen sharing works fine and the notifications are all called as expected.

I hope this helps someone else!