great question. short answer is it must be INVITE, not REFER as it stays in the media path.
Looking for a REFER based connection to agent would allow for some insane scalability as OpenACD really only consumes a fraction of the CPU to do it's job. OpenACD today uses the FS session to determine when agents are available based on open channels and such. Having said that, OpenACD has a general architecture for queueing anything like email and voicemail, so i suspect queuing based on REFER would require tracking/subscribing to the SIP messages to determine call state to replicate what FS session provides. but post to http://groups.google.com/group/openacd if you want a more in-depth response On Tue, Jan 25, 2011 at 9:32 AM, Tony Graziano <tgrazi...@myitdepartment.net> wrote: > as an incoming call center the call would go to the agent via an invite. > i am assuming it will bridge the call via its FS config, and there is no > transfer. > though i might be wrong and will wait to be corrected... > > On Tue, Jan 25, 2011 at 9:28 AM, Matt White <mwh...@thesummit-grp.com> > wrote: >> >> Sorry for being too lazy to test this for myself. I was just talking with >> someone and the question came up. >> >> Does the new openacd implementation use the same conference method to join >> the caller to the agent the current ACD uses or does it use a standard >> refer? >> >> -M >> >> _______________________________________________ >> sipx-users mailing list >> sipx-users@list.sipfoundry.org >> List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > > > > _______________________________________________ > sipx-users mailing list > sipx-users@list.sipfoundry.org > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users/
