Sure, but where is it written or set by the project one can no longer do an
attended transfer to a media based service? It's not, so the anology should
be thrown out. There, I just did it.

Besides the fact there are at least two workarounds for getting a DID number
to the conferencing system also does not apply, because there are ways to
make that work and seem transparent, AND_BOTH_USE_CASES_WORK.

Since what Jost OPENED a JIRA on and discovered was unknown and thought to
have worked all along, I see not reason to expect everyone to know that.
Josh is setting the expectations here, and we'll follow the JIRA with keen
interest, because it's a BOOGER of an issue and was unknown. How does one
set an expectation for an unkwown issue that was thought to have worked...
uh, stammer...

On Sun, Jul 18, 2010 at 4:11 PM, Todd Hodgen <[email protected]> wrote:

>  Analogy Tony.  A simple Analogy.
>
>
>
> *From:* Tony Graziano [mailto:[email protected]]
> *Sent:* Sunday, July 18, 2010 12:56 PM
> *To:* Todd Hodgen
> *Cc:* Josh Patten; [email protected]
>
> *Subject:* Re: [sipx-users] Help with Patton gateway
>
>
>
> I disagree. Doing an attended transfer to AA worked in 3.10.3, there is
> nothing in the notes that this is no longer supported going forward. The
> project also needs to set these expectations. It was never stated it was no
> longer supported. So in this case, setting an expectation would still result
> in disappointment.
>
>
>
> There is a workaround for a DID to a conference bridge. Two actually. So I
> don't see how that is relevant to the issue Todd has opened.
>
> On Sun, Jul 18, 2010 at 2:50 PM, Todd Hodgen <[email protected]> wrote:
>
> Set expectations.   You can’t do a supervised transfer to Auto Attendant or
> Voicemail in the system today.  It’s true, it’s accurate, it’s an
> expectation you need to set for the end users.  You can dance around this
> all you want, but it doesn’t change the fact that it isn’t supported.   Yes,
> it should be there, and there is a very limited use case for it.  Bottom
> line, it’s not there.
>
>
>
> Last I saw there is no way to set a DID to a conference bridge.  It should
> be there.  However, we set the expectation that it’s not there, or there is
> a workaround for it.
>
>
>
> Find one phone system that has everything, has no bugs, and has every
> feature that people desire.  It doesn’t exist.  They need to do a blind
> transfer.  That is why account managers, sales engineers and customer
> service representatives have to set the correct expectations with the end
> users.
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Josh Patten
> *Sent:* Sunday, July 18, 2010 10:27 AM
> *To:* [email protected]
>
>
> *Subject:* Re: [sipx-users] Help with Patton gateway
>
>
>
> 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]>
> 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/
>
>
>
>
> --
> ======================
> Tony Graziano, Manager
> Telephone: 434.984.8430
> sip: [email protected]
> Fax: 434.984.8431
>
> Email: [email protected]
>
> LAN/Telephony/Security and Control Systems Helpdesk:
> Telephone: 434.984.8426
> sip: [email protected]
> Fax: 434.984.8427
>
> Helpdesk Contract Customers:
> http://www.myitdepartment.net/gethelp/
>
> Why do mathematicians always confuse Halloween and Christmas?
> Because 31 Oct = 25 Dec.
>



-- 
======================
Tony Graziano, Manager
Telephone: 434.984.8430
sip: [email protected]
Fax: 434.984.8431

Email: [email protected]

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
sip: [email protected]
Fax: 434.984.8427

Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/

Why do mathematicians always confuse Halloween and Christmas?
Because 31 Oct = 25 Dec.
_______________________________________________
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/

Reply via email to