We are using Trixbox integrated with Microsoft OCS2007 R2. We have a problem in such that when a users is Muted from within OCS it puts the person connected through trixbox on Hold. After 30 seconds the call gets dropped.
I have been doing some research as to what OCS does when it mutes users.
This is what I got when posting to a Microsoft forum
http://social.microsoft.com/Forums/en-US/communicationsservertele...
The problem has to do with your OCS PBX integration. My guess is that you are doing a direct SIP connection to an "unsupported" IP-PBX. The reason i suspect this is the following:
1) when a user is muted in OCS, the SDP info changes from "send/receive" (the normal state to talk and listen) to "receive only" (your endpoint can no longer "send" voice packets"). This is how OCS mutes people.
2) your PBX is using an older (yet valid/widespread) interpretation of "receive only"... your PBX interprets "receive only" as "put on hold".
Any OCS-supported IP-PBX is required to interpret "receive only" as "mute". It's part of the Direct SIP interop spec that MS publishes.
Unless you can reconfigure your PBX to this level of detail, you are probably out of luck doing direct SIP to OCS. You'll need to use a supported voice gateway otherwise.
I couldnt see how to make this change to the current version of Trixbox we are using, so I thought I would through it out there for a possible addtion to a later version of the software.
Member Since:
2009-11-16