Plantronics + Polycom. Now together as Poly Logo

VVX1500 Video errors

SOLVED
davem2626
Valued Contributor

VVX1500 Video errors

Hi there

 

Having a bit of an issue with video between 2 x VVX1500's....

 

Noticed the following in the logs - any ideas on what they mean?:

 

1210103325|cap  |4|00|[SoVidVideoCaptureManagerC::soYuvCapProcessEncodeMsg][ERROR] Display to preview/PIP window failed! failureCt=3, pipChannelOk=F, pipResizerOk=F, displayOk=F, pipChanState=Idle, camFrameAddr=0x452d6000, pipFrameBuf=0x0.

1210103325|cap  |4|00|[SoVidDefaultCameraC::configureDevice][ERROR] Invalid encoder codec type () for camera.

000016.398|so   |4|00|SoVideoIFrameRequesterC::instanceDestroy - unexpected state, instance was not initialized

1210103325|cap  |4|00|[SoVidDefaultCameraC::open] Device successfully opened! ('drvCameraInit' succeed!)

 

 

 

Many thanks

 

Dave

Message 1 of 4
1 ACCEPTED SOLUTION

Accepted Solutions
davem2626
Valued Contributor

Re: VVX1500 Video errors

Ok I found out what my issue was!!....

 

We are using VVX's on a Broadsoft platform - when added the DTAF's didnt tick the video enabled box!

 

I could call video call a phone within the same subnet as it wasn't going through the AS however a phone in a different subnet means the AS will strip the video SDP off if that box is not ticked....

 

Also if your on Broadsoft just quickly check the AS will allow video calling:

 

AS_CLI/Interface/SIP> get

 

networkSupportVideo = true

 

 

Cheers

 

Dave

View solution in original post

Message 4 of 4
3 REPLIES 3
davem2626
Valued Contributor

Re: VVX1500 Video errors

and also the following:

 

1210121820|cap  |3|00|[SoVidVideoCaptureManagerC::soYuvCapProcessEncodeMsg] No buffer to send to DSP. count=1025
1210121901|cap  |3|00|[SoVidVideoCaptureManagerC::soYuvCapProcessEncodeMsg] No buffer to send to DSP. count=2049
1210122022|cap  |3|00|[SoVidVideoCaptureManagerC::soYuvCapProcessEncodeMsg] No buffer to send to DSP. count=4097
1210122306|cap  |3|00|[SoVidVideoCaptureManagerC::soYuvCapProcessEncodeMsg] No buffer to send to DSP. count=8193

 

Message 2 of 4
davem2626
Valued Contributor

Re: VVX1500 Video errors

and also:

 

000033.201|cap  |4|00|[SoVidDefaultCameraC::open] Device successfully opened! ('drvCameraInit' succeed!)
000033.205|cap  |4|00|[SoVidDefaultCameraC::configureDevice][ERROR] Invalid encoder codec type () for camera.
000033.470|cap  |4|00|[SspsVideoYuvCameraChanC::procMsgSoSspsYuvChanConfig] Camera device created, configured and is READY!!
000033.472|cap  |4|00|[SoVidVideoCaptureManagerC::soYuvCapProcessEncodeMsg][ERROR] No active camera found! noActiveCameraChanCt=1
000033.474|cap  |4|00|[SoVidVideoCaptureManagerC::soYuvCapProcessEncodeMsg][ERROR] Display to preview/PIP window failed! failureCt=1, pipChannelOk=F, pipResizerOk=F, displayOk=F, pipChanState=Open, camFrameAddr=0x43ef7000, pipFrameBuf=0x0.
000033.485|cap  |4|00|[SoVidVideoCaptureManagerC::soYuvCapProcessEncodeMsg][ERROR] Display to preview/PIP window failed! failureCt=3, pipChannelOk=F, pipResizerOk=F, displayOk=F, pipChanState=Idle, camFrameAddr=0x440cd000, pipFrameBuf=0x0.

 

I can make a vid call from 1 VVX1500 to a VVX500 and thats fine - on setting logging to level 1 for video and making a test call again the following is seen:

 

1210125507|cap  |3|00|[SoVidVideoCaptureManagerC::soYuvCapProcessEncodeMsg] No buffer to send to DSP. count=16385

 

 

 

UC Software Version 5.0.0.6874 BootROM Software Version 5.2.0.3747

Message 3 of 4
davem2626
Valued Contributor

Re: VVX1500 Video errors

Ok I found out what my issue was!!....

 

We are using VVX's on a Broadsoft platform - when added the DTAF's didnt tick the video enabled box!

 

I could call video call a phone within the same subnet as it wasn't going through the AS however a phone in a different subnet means the AS will strip the video SDP off if that box is not ticked....

 

Also if your on Broadsoft just quickly check the AS will allow video calling:

 

AS_CLI/Interface/SIP> get

 

networkSupportVideo = true

 

 

Cheers

 

Dave

View solution in original post

Message 4 of 4