I'm afraid you're right. There was an auto wrap-up in OpenACD back in v1 that is set per client, but this didn't make it into OpenACD v2 and is therefore not configurable in sipx. I think it makes sense to have an auto wrap-up feature, and I'll check if it's simple enough to port to OpenACD v2. Feel free to follow this issue (http://track.sipfoundry.org/browse/XX-10351).
Jan Vincent Liwanag [email protected] On Wednesday, August 1, 2012 at 10:30 PM, Jan Fricke wrote: > > Mea culpa… > > > There was a typo in the commands behind the star codes. But there is > something else that I did not expect. > > > I have created a queue with one agent. When he receives a call and finishes > it he is in the wrap-up state. To make him receive another call I need to: > Logoff, Login, Go Available. Simply going available to end wrap-up does not > work. Is this desired? Is it possible to configure auto-wrap time from > sipxconfig? > > > > > > Sincerely > > > Jan > > > > > > > > > Von: Kumaran [mailto:[email protected]] > Gesendet: Mittwoch, 1. August 2012 12:19 > An: Jan Fricke > Cc: sipXecs developer discussions > Betreff: Re: AW: [sipx-dev] OpenACD > > > > > > > > Then fix should in the build...I don't know the what causing the > issue...Definitely help need from JV or Cristi... > > Regards, > Kumaran T > > On 8/1/2012 3:35 PM, Jan Fricke wrote: > > > Yes it is… > > > > > > Von: Kumaran [mailto:[email protected]] > Gesendet: Mittwoch, 1. August 2012 11:58 > An: sipXecs developer discussions > Cc: Jan Fricke > Betreff: Re: [sipx-dev] OpenACD > > > > > > > > Is sipxconfig latest(sipxconfig-4.6.0-261.gbbdad.x86_64)? > > Regards, > Kumaran T > > On 8/1/2012 3:25 PM, Jan Fricke wrote: > > > In my installation the default star codes were *87 and *90. I tried both > before I used the web portal. Made an yum update 5 minutes ago. > > > Sipxopenacd release 51.g717ed > > > Openacd 0.9.5 release 1327.g2d43 > > > > > > The update did not solve the issue. Also tried to disable the portal on 5050 > and 5051. What should I see in the full.log of openacd when using the star > codes? > > > > > > Sincerely > > > > > > Jan > > > > > > Von: [email protected] > (mailto:[email protected]) > [mailto:[email protected]] Im Auftrag von Jan Vincent > Liwanag > Gesendet: Mittwoch, 1. August 2012 11:32 > An: sipXecs developer discussions > Betreff: Re: [sipx-dev] OpenACD > > > > > > This is expected behavior as far as openacd is concerned. An agent can only > be logged in via the agent web portal or through release codes, but not both > at the same time. > > > > > > > > If the agent logs in via the web portal, the agent can change release/idle > states using the buttons on said portal. Release/star codes won't work. > > > > > > > > For the release codes to work, the agent must be logged off the web portal > first. Then log in through the release codes ( *88 by default ) then go > available ( *86 ). > > > > > > > > Jan Vincent Liwanag > > > > [email protected] (mailto:[email protected]) > > > > > On Wednesday, August 1, 2012 at 5:12 PM, Kumaran wrote: > > > > Hi Jan, > > Did you checking in latest 4.6 build? Because for star codes not working > > in older builds in which issue raised and closed...In the latest build it > > should work fine.. > > > > Regards, > > Kumaran T > > > > On 8/1/2012 2:38 PM, Jan Fricke wrote: > > > > > > I’m trying OpenACD in our 4.6 testsystem. Port 5050 is not reachable from > > outside. From localhost (using links bash browser J) it works fine. > > > > > > I think there is something I have do configure in the Firewall. But I did > > not find something like Contact Center or ACD (except the old deprecated > > ACD system). > > > > > > > > > > > > Another thing is that going available etc. works using the portal on 5050. > > But the star codes like *87 does not have any effect. Its openacd is > > hanging up instantly which is normal I think. The logs on debug show > > something like this when using one of the star codes: > > > > > > > > > > > > 10:33:02.197763 [DEBUG] <0.317.0>@freeswitch_media_manager:798 recieved > > event '"81d5d01a-dbb3-11e1-a040-e766a4e6efc4"' from c node. > > > > > > > > > > > > But the state in the agent web-interface does not change and calls in the > > queue don’t become routed to the agent. > > > > > > > > > > > > Any ideas? > > > > > > > > > > > > _____________________________ > > Jan Fricke (B.Sc.) > > > > IANT - > > APPLIED NGN-TECHNOLOGIES > > > > Turn-Key VoIP/UC Solutions and More... > > > > > > Fon: +49 (5331) 6794 0 > > Fax: +49 (5331) 6794 499 > > Mail: [email protected] (mailto:[email protected]) > > Web: www.iant.de (http://www.iant.de/en/startseite) > > > > > > IANT is eZuce (http://www.ezuce.com/) Elite Partner for EMEA > > > > IANT is Member of GROUPLINK (http://www.grouplink.de/) > > > > > > > > > > > > > > Von: [email protected] > > (mailto:[email protected]) > > [mailto:[email protected]] Im Auftrag von Todd Hodgen > > Gesendet: Mittwoch, 1. August 2012 07:56 > > An: 'sipXecs developer discussions' > > Betreff: Re: [sipx-dev] OpenACD > > > > > > > > > > > > > > > > Thanks Jan. > > > > > > > > > > > > From: [email protected] > > (mailto:[email protected]) > > [mailto:[email protected]] > > (mailto:[mailto:[email protected]]) On Behalf Of Jan > > Vincent Liwanag > > Sent: Tuesday, July 31, 2012 10:52 PM > > To: sipXecs developer discussions > > Subject: Re: [sipx-dev] OpenACD > > > > > > > > > > > > Hi Todd, > > > > > > > > > > > > > > > > Indeed the information on the wiki is not up to date. Feel free to ask your > > questions here as needed. > > > > > > > > > > > > > > > > All of the configuration needed is done through sipx now. Thus the > > administration pages on port 9999 is no longer needed (and will be turned > > off by default). > > > > > > > > > > > > > > > > The agent portal running on port 5050 is still used. Agents configured in > > sipx can be logged in through this portal. The new agent portal now only > > need the username and password (no additional voip endpoints to configure). > > > > > > > > > > > > > > > > As per recipes, the best resource for now would be this > > (https://github.com/OpenACD/OpenACD/wiki/How-routing-works). > > > > > > > > > > > > > > > > I'll also review the wiki pages myself, and update as necessary. > > > > > > > > > > > > > > > > Jan Vincent Liwanag > > > > > > > > [email protected] (mailto:[email protected]) > > > > > > > > > > On Wednesday, August 1, 2012 at 5:06 AM, Todd Hodgen wrote: > > > > > > I’m working on setting up OpenACD for the first time. In reading the > > > wiki, there is a lot of old information that needs to be updated. I’m > > > happy to do that as I go through my own configuration of OpenACD for > > > testing. > > > > > > > > > > > > > > > > > > Is there a primary resource for bouncing content off of, or just post > > > questions in the Dev list? > > > > > > > > > > > > > > > > > > For example – I am sure this is no longer a requirement, and will remove > > > it unless someone tells me otherwise - this is specifically under wiki > > > 4.6 instructions. And yes, I know the devs are busy writing code and > > > the wiki is not their priority – I’m hoping assist as best I can on this. > > > > > > > > > yum install sipxopenacd > > > > > > > > > service mongod start > > > > > > > > > service sipxecs restart > > > > > > > > > > > > > > > > > > > > > > > > > > > Additionally – logging into ports 5050 and 9999 seem to no longer be > > > required, is that correct? If not, where are the agent and supervisor > > > pages located? > > > > > > > > > > > > > > > > > > Are there any sample recipes that are fully supported that can be > > > imported and documented in the wiki? Any other documents in possession > > > that can be used to document the wiki pages? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > sipx-dev mailing list > > > > > > > > [email protected] (mailto:[email protected]) > > > > > > > > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > > > > > > > > > > > > > > > > > > _______________________________________________ > sipx-dev mailing list > [email protected] (mailto:[email protected]) > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > > > > > > > > > _______________________________________________ > sipx-dev mailing list > [email protected] (mailto:[email protected]) > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ > >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
