Limitations

Top  Previous  Next
Trading and C&C > Turret Proxy To Open communication (TPO) > DDI Sharing > DDI Lines Sharing > Usage > Telephony functions > PBX dependent features > Video Call > References

Information provided in standard video call limitations are also applicable to DDI calls.

 

•Due to remote party Key Frame refresh delay, user who joins an existing video call may firstly receive black video until remote party sends the next key frame.

 

•Neither TPO cluster with Hot backup nor TPO fail over mechanism preserve video streams in case of failure.

oOngoing video may freeze in case of TPO failure

oUser is capable to hide frozen video as easily as hiding normal video

 

•Depending on configuration, pressing an empty DDI slot in order to initiate a manually allocated DDI call may reserve a video call.

 

•When user presses exclusive button to turn call strictly exclusive:

oother users can not join the call

oother users stop receiving remote party video

ouser who handles the exclusive call continues to receive remote party video

oif video out stream was sent by another user, video stop to be sent to the remote party.

oif video out stream was sent by the user who handles the exclusive call, video continues to be sent to the remote party.

 

•When user presses exclusive button to turn call in exclusive conference, current video state is preserved.

 

•PBX access point doesn't support video calls.

 

•DDI slot with MRD permanent or Static IP attribute doesn't support video calls.

 

•Initiating a conference disable video capabilities on the slot.

 

•On one DDI call/slot, only one DDI line user can send his video to remote party at a time. There is no way for the remote party to see two DDI line user videos on the same call. First DDI line user who sends his video takes ownership of the outbound video channel, afterward, other users have to way for the video channel to be freed before starting to send their video.

 

•When  user is configured with Default video state incoming DDI calls and/or Default video state outgoing DDI calls in send_only, he may be unable to activate video reception even if remote party is sending his video:


 

For instance, consider a "send / receive" video call is established on a DDI slot.

 

Both User A and Remote party send and receive each other video

Join1

 

User B as Default video state outgoing DDI calls set to send_only.

 

When he joins the DDI slot he doesn't send his video because of User A and he doesn't receive remote party video as per configuration.

 

From that point user B hasn't capability to start receiving remote party video.

Join1

 

•When video has been stopped because another user has activated strict Exclusive mode, user is unable to activate video reception even if Exclusivity mode has been released and if remote party is sending his video. The only way to activate video after that is to leave DDI slot and rejoin it.

 

•When user presses to Hold button:

oif other traders are connected on the slot, call with user who has pressed on Hold button is terminated ;

oif no other traders are connected on the slot, remote party passes in inactive video state ;

 

•When user resumes call, call stays in audio only. Video is inactive.

 

•When user B joins DDI slot and user A was on hold on this DDI slot, call with user A is terminated and call with user B is established in audio only.

 

•A user has no video if :

ohe has video disabled ;

ohis video codec doesn't match with video codec of infrastructure ;

oturret is T2 XMA based


 

Scenario 1 :

 

For instance, consider User A has no video and Remote party has video enabled.

 

User A is called by Remote party and answers call or User A calls Remote party and Remote party accepts call. Call is established between User A and Remote party.

 

Call is audio only in both way because of User A who has no video.

videoCallAudio01

 

User B has video enabled and he has configured Default video state outgoing DDI calls in inactive.

 

When he joins the DDI slot, call stays audio only in both way for User A and Remote party, but it is a video call inactive for User B.

 

From that point Remote party hasn't capability to start sending or receiving video until User B has pressed to send his video.

videoCallAudio02

 

 

Scenario 2 :

 

For instance, consider User A has video enabled, he has configured Default video state outgoing DDI calls in send_receive and a "send / receive" video call is established on a DDI slot.

 

Both User A and Remote party send and receive each other video.

videoCallAudio03

 

User B has no video.

 

When he joins the DDI slot, call stays video for User A and Remote party and call is audio for User B (he hasn't capability to start sending or receiving video).

videoCallAudio04

 

When User A leaves the slot, call is video inactive for Remote party and call stays audio for User B (he hasn't capability to start sending or receiving video).

 

If Remote party presses to activate his video (he sends it), he will send it but User B won't receive it because his call is audio only.

videoCallAudio05