Uses the 'on-hold' endpoint status type when describing in a conference-info document CallPeer-s which have a REMOTELY_ON_HOLD status.

1 files changed, 11 insertions, 0 deletions

diff --git a/src/net/java/sip/communicator/service/protocol/media/AbstractOperationSetTelephonyConferencing.java b/src/net/java/sip/communicator/service/protocol/media/AbstractOperationSetTelephonyConferencing.java
index 00a9d10..85a0288 100644
--- a/src/net/java/sip/communicator/service/protocol/media/AbstractOperationSetTelephonyConferencing.java
+++ b/src/net/java/sip/communicator/service/protocol/media/AbstractOperationSetTelephonyConferencing.java
@@ -1170,6 +1170,17 @@ public abstract class AbstractOperationSetTelephonyConferencing<
             return ConferenceInfoDocument.EndpointStatusType.dialing_out;
 
         /*
+         * RFC4575 does not list an appropriate endpoint status for
+         * "remotely on hold", e.g. the endpoint is not "hearing" the conference
+         * mix, but it's media stream *is* being mixed into the conference.
+         *
+         * We use the on-hold status anyway, because it's the one that makes
+         * the most sense.
+         */
+        if (CallPeerState.ON_HOLD_REMOTELY.equals(callPeerState))
+            return ConferenceInfoDocument.EndpointStatusType.on_hold;
+
+        /*
          * he/she is neither "hearing" the conference mix nor is his/her
          * media being mixed in the conference
          */