On Wed, 2008-06-04 at 11:10 -0400, M. Ranganathan wrote: > On Wed, Jun 4, 2008 at 10:56 AM, Damian Krzeminski <[EMAIL PROTECTED]> wrote: > > M. Ranganathan (JIRA) wrote: > >> [ > >> http://track.sipfoundry.org/browse/XCF-2522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_29377 > >> ] > >> > >> M. Ranganathan commented on XCF-2522: > >> ------------------------------------- > >> > >> Is it necessary to support call transfer once the call has been > >> established? > >> > > > > Naive question warning. > > I thought that all sipXconfig would do is to initialize the call. Why > > would it restrict or change anything with regard to what you can do with > > that call? > > D. > > > The 3pcc controller is going to follow the recommendation of flow 4 > that is defined in http://tools.ietf.org/html/rfc3725
I completely agree with Woof on this. There are some times and places where a B2BUA is the only way to go - the ACD and sipXbridge connections are good examples. I don't think that click-to-dial is a good example. A phone that doesn't support REFER (or even REFER w/ Replaces) is not interesting and we shouldn't worry about them. Getting out of the signaling path is a core principle. -- Scott Lawrence tel:+1.781.229.0533;ext=162 or sip:[EMAIL PROTECTED] sipXecs project coordinator - SIPfoundry http://www.sipfoundry.org/sipXecs CTO, Voice Solutions - Bluesocket Inc. http://www.bluesocket.com/ http://www.pingtel.com/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
