I only run 550's and 650's.
I really don't think speculating about ways for end users to "work
around" the problem is very constructive. As Tony and I have both said
this is a major flaw that should be fixed and I have a feeling it's
going to take a while due to having to wait for FreeSWITCH upstream to
fix it, and the fact that sipX generally stays at least a point version
behind on FreeSWITCH doesn't help things.
The more of these major bugs I find, the more my end users are going to
start wondering why I switched them over from the old system.
These are the major/critical issues I've run into over the last month:
http://track.sipfoundry.org/browse/XX-8438
http://track.sipfoundry.org/browse/XX-8646 - My coworker is almost
finished with this fix
http://track.sipfoundry.org/browse/XX-8652
On 07/18/2010 10:31 AM, Jim Canfield wrote:
On Sat, Jul 17, 2010 at 7:09 AM, Michael Scheidell
<[email protected] <mailto:[email protected]>> wrote:
I suppose we could just train everyone to push that extra 'more'
button and hit blind transfer.
In fact, an attended transfer to AA or VM doesn't make all that
much sense anyway.
For your Polycom 320/335's you can make blind transfer the default
behaver. Not that that offers much of a solution, just thought I would
throw that out for those users who do have them.
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________
sipx-users mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
