Yealink Forums
T58A - Video calls with Teams - Printable Version

+- Yealink Forums (http://forum.yealink.com/forum)
+-- Forum: IP Phone Series (/forumdisplay.php?fid=4)
+--- Forum: T5X Series (/forumdisplay.php?fid=58)
+--- Thread: T58A - Video calls with Teams (/showthread.php?tid=43599)

Pages: 1 2

RE: T58A - Video calls with Teams - itpino - 04-15-2020 08:57 AM

Hello, is it possible to downgrade from the Teams firmware?
The manual says that if I have a permanent license, it not allowed to downgrade. But the phone come with a Open SIP firmware and upgraded to Teams and order a permanent license over Yealink Portal.

After flashing on Teams Firmware, I found out over the forum, the video call doesn't work Angry
So I downgraded from the Teams firmware back to the Open SIP firmware and now it hangs on the Yealink Logo with black background.
Beacause I will returned it back.

RE: T58A - Video calls with Teams - complex1 - 04-15-2020 09:18 AM

(04-15-2020 08:57 AM)itpino Wrote:  Hello, is it possible to downgrade from the Teams firmware?
The manual says that if I have a permanent license, it not allowed to downgrade. But the phone come with a Open SIP firmware and upgraded to Teams and order a permanent license over Yealink Portal.

After flashing on Teams Firmware, I found out over the forum, the video call doesn't work Angry
So I downgraded from the Teams firmware back to the Open SIP firmware and now it hangs on the Yealink Logo with black background.
Beacause I will returned it back.

Hi,

I think the best you can do is open a support ticket @ Yealink and ask if they can help.
https://ticket.yealink.com/

RE: T58A - Video calls with Teams - NezarH - 04-20-2020 09:35 PM

Hello ,

I have purchased new SIP-T58A and CAM50 two days back , installed the firmware for SfB . at first I were so excited specially that it work very well , clear sound … BUT Wait , NO VIDEO ! only audio call !

reading the comments made me frustrated! I haven't done my home work correctly ! I thought because it video phone and support sfb and teams then video call out of the question !.

is a any solution or suggestions !?

have anyone tried sfb apk!

RE: T58A - Video calls with Teams - DaveZmeyrCo - 04-23-2020 05:18 PM

I don't believe there's any immediate plans to support video on these phones (I have two of them so I've gone down this journey). I met with Yealink here in the states and to some degree they're limited to what Microsoft allows and certifies. There is a Teams Video phone from Yealink, the VP59. I've been using this with 4 of my fellow users for about 3 months (Yealink got us some pre-release Teams units). They work pretty good though the interface still needs some work (they just released an update about a month ago that has drastically improved it).

RE: T58A - Video calls with Teams - Evil.2000 - 02-12-2021 04:48 PM

Hello folks,

I ordered the T58A to do video calls in MS Teams, stepped into the trap also and finally got to this thread to read that the phone doesn't support video calls.

Because of a mistake, I accidentally installed the T58 SIP firmware, which shows that the camera is working (as CyB0rg correctly stated in post #2).
But reflashing the correct T58A-Teams firmware failed. The phone was stuck after booting at the bright "Yeahlink" logo. So I logged in via the Web-UI and pulled the syslog for finding the boot error. Finally I got past the boot logo issue by reflashing the T58 SIP firmware, resetting to factory defaults and clearing the internal sd-card and reflashing the T58A-Teams firmware again.

Then I noticed that the camera is not working, so I pulled the syslogs again and digged into it.

While booting it seems that the camera got recognized:
Code:
<133>Dec 18 00:00:21 kern[0.0]: KMSG<5+notice> [    3.292732] init: (Parsing /system/etc/init/cameraserver.rc took 0.00s.)
<134>Dec 18 00:00:21 kern[0.0]: KMSG<6+info  > [   10.817399] uvcvideo: Found UVC 1.00 device 292A-IPC-OV2710 (0c45:6366)
<134>Dec 18 00:00:21 kern[0.0]: KMSG<6+info  > [   10.829104] uvcvideo: Unable to create debugfs 1-3 directory.
<133>Dec 18 00:00:21 kern[0.0]: KMSG<5+notice> [   19.239606] init: Starting service 'cameraserver'...
...
<134>Dec 18 00:00:21 GUI [1009:1154]: ANDR<6+info  > 549   549 I cameraserver: ServiceManager: 0xb6290380
<134>Dec 18 00:00:21 GUI [1009:1154]: ANDR<6+info  > 549   549 D CameraHal: camera_get_number_of_cameras(842): Open /dev/video0 success!
<134>Dec 18 00:00:21 GUI [1009:1154]: ANDR<6+info  > 549   549 D CameraHal: camera_get_number_of_cameras(842): Open /dev/video1 success!
<131>Dec 18 00:00:21 GUI [1009:1154]: ANDR<3+error > 549   549 E CameraHal: camera_get_number_of_cameras(976): mCamDriverPreviewFmt = 0, no support fmt
<134>Dec 18 00:00:21 GUI [1009:1154]: ANDR<6+info  > 549   549 I CameraService: Loaded "RK29_ICS_CameraHal_Module" camera module
<134>Dec 18 00:00:21 GUI [1009:1154]: ANDR<6+info  > 549   549 D CameraHal: camera_get_camera_info(1444): camera_get_camera_info(1444): camera_0 facing(0), orientation(0)
<134>Dec 18 00:00:21 GUI [1009:1154]: ANDR<6+info  > 549   549 I CameraService: init camera 0 state 1
<134>Dec 18 00:00:21 GUI [1009:1154]: ANDR<6+info  > 549   549 I ServiceManager: Waiting for service media.camera.proxy...
...
<134>Feb 10 20:38:11  GUI [1009:1154]: ANDR<6+info  > 2898  2898 I CameraManagerGlobal: Connecting to camera service
<134>Feb 10 20:38:11  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: camera_get_camera_info(1444): camera_get_camera_info(1444): camera_0 facing(0), orientation(0)
<134>Feb 10 20:38:11  GUI [1009:1154]: ANDR<6+info  > 1209  1209 V CameraService: getLegacyParametersLazy: for cameraId: 0
<134>Feb 10 20:38:11  GUI [1009:1154]: ANDR<6+info  > 1209  1209 I CameraService: CameraService::connect call (PID -1 "cameraserver", camera ID 0) for HAL version default and Camera API version 1
<134>Feb 10 20:38:11  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: camera_get_camera_info(1444): camera_get_camera_info(1444): camera_0 facing(0), orientation(0)
<134>Feb 10 20:38:11  GUI [1009:1154]: ANDR<6+info  > 1209  1209 V CameraService: startCameraOps: Start camera ops, package name = cameraserver, client UID = 1047
<134>Feb 10 20:38:11  GUI [1009:1154]: ANDR<6+info  > 1209  1209 V CameraService: updateStatus: Status has changed for camera ID 0 from 0x1 to 0xfffffffe
...
<134>Feb 10 20:38:16  GUI [1009:1154]: ANDR<6+info  > 1209  1209 I CameraFlashlight: Opening camera 0
<134>Feb 10 20:38:16  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: camera_get_camera_info(1444): camera_get_camera_info(1444): camera_0 facing(0), orientation(0)
<134>Feb 10 20:38:16  GUI [1009:1154]: ANDR<6+info  > 1209  1209 I CameraHal: camera_device_open(567): camera_device open
<134>Feb 10 20:38:16  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: CameraHal(124): it is a uvc camera!
<134>Feb 10 20:38:16  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: Calling process is: /system/bin/cameraserver
<134>Feb 10 20:38:16  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: Calling process is: /system/bin/cameraserver
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: cameraCreate(375): Camera driver: uvcvideo  Card Name:292A-IPC-OV2710  Driver version: 3.10.0  CameraHal version: 1.80.1
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: cameraCreate(382): mCamDriverSupportFmt: fmt = 1448695129(YUV 4:2:2 (YUYV)),index = 0
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: cameraCreate(382): mCamDriverSupportFmt: fmt = 1196444237(MJPEG),index = 1
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: cameraCreate(420): cameraCreate(420): mCamDriverPreviewFmt(MJPG) is cameraHal and camera driver is also supported!!
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: cameraCreate(422): mCamDriverPreviewFmt  = 1196444237
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: cameraCreate(428): cameraCreate(428): Current driver is uvcvideo, v4l2 memory is V4L2_MEMORY_MMAP
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: initDefaultParameters(565): mIsCtsTest:0 Support video sizes:(null)
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: initDefaultParameters(611): Support video stabilization: false
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: cameraConfig(744): cameraConfig(744): Set framerate(30 fps) success
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: cameraConfig(787): cameraConfig(787): Set white balance(auto) success
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: cameraConfig(864): cameraConfig(864): Set anti-banding Disabled
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: cameraConfig(945): cameraConfig(945): Set exposure 0    0
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  1209 D CameraHal: isNeedToRestartPreview(146): video width (640x480)
<134>Feb 10 20:38:17  GUI [1009:1154]: ANDR<6+info  > 1209  3073 D CameraHal: isNeedToRestartPreview(146): video width (640x480)

But when a call needs to be established, it prints:
Code:
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: ProcessId: 3674, Thread: main, Calling: call policies for : callId : 103 :
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isAudioCallAllowed : true,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isGroupCallAllowed() : true,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isVideoCallAllowed() : false,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isPstnCallAllowed() : false,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isJoinMeetingAllowed() : true,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isEvEnabled() : false,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isSafeTransferEnabled() : true,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: shouldShowCallingOption() : true,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isCallForwardingSettingsEnabled() : false,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isCallParkPolicyEnabled() : true,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isIntentionalWhiteboardAllowed() : true,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isInvisionWhiteboardAllowed() : true,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isDialInAllowed() : false,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isCallMeBackAllowed() : false,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isMeetingRecordingEnabled() : false,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isAutoAnswerSettingEnabled() : false,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isFileShareEnabled() : true,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isPhotoShareEnabled() : false,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isVideoShareEnabled() : true,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isScreenShareEnabled() : false,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isAnyShareEnabled() : false,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isCallTransferEnabled() : true,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isAnimationEnabled() : true,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isAllowDialOutConferencingEnabledInMeeting() : false
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 D CallPolicy: isPPTShareConsumptionEnabled() : false,
<134>Feb 10 14:06:03  GUI [1009:1154]: ANDR<6+info  > 3674  3674 I Calling: InCallFragment: ProcessId: 3674, Thread: main, Setting allow video to false in setupViews

CallPolicy: isVideoCallAllowed() : false lets me suppose, that there is a policy which forbids enabling the video calling.
The PID 3674 is the teams client:
Code:
<134>Feb 10 20:58:33  GUI [1009:1154]: ANDR<6+info  > 2055  3159 I am_proc_start: [0,3674,10021,com.microsoft.skype.teams.ipphone,activity,com.microsoft.skype.team​s.ipphone/com.microsoft.skype.teams.Launcher]
<134>Feb 10 20:58:33  GUI [1009:1154]: ANDR<6+info  > 2055  3159 I ActivityManager: Start proc 3674:com.microsoft.skype.teams.ipphone/u0a21 for activity com.microsoft.skype.teams.ipphone/com.microsoft.skype.teams.Launcher
...
<134>Feb 10 20:58:33  GUI [1009:1154]: ANDR<6+info  > 2055  2067 I am_proc_bound: [0,3674,com.microsoft.skype.teams.ipphone]
...
<134>Feb 10 20:58:33  GUI [1009:1154]: ANDR<6+info  > 2055  2067 D ActivityManager: setProcessGroup teams app, pid=3674

I searched through the Teams admin center for a call policy which may forbid video calling, but did not find anything.
So I suppose that either Microsoft is suppressing video calling due to less performance or there is a config which prevents the Teams app from enabling video.

Maybe someone can try to get the video working on the Teams-edition of the phone, regardless of the bad performance.
I will return my T58A and buy a working phone from another vendor.

P.S.: The Cam50 seems to be just a Sonix Technology SN0001 which is used by Dell in the Inspiron notebooks as well.

A small update:
The camera is working on T58A with SIP firmware, but not with the teams client. It seems that Microsoft or a config setting on the phone is preventing the Teams client from enabling video.

RE: T58A - Video calls with Teams - Proxytec - 06-30-2021 01:08 AM

same here. Bought the T58A and the Cam and was suprised that this is not working. Why they sell a IP-Phone with a camera slot when this is not working?

I was happy to be able to switch back and forth between SIP and MS Teams in order to use both. And so far it is working. But Teams do not work with the cam.