Re: [asterisk-users] queue welcome message
Hello! just fyi. If anyone wants to use the same function - here is the solution I found: Before calling the queue() do a queue_member_count and if 1 do not call the queue. Works fine with dynamic members. if you use static members - I think there is no solution ;-) best regards Martin - Original Message - From: Martin Schrott - thinking:systems To: [EMAIL PROTECTED] ; Asterisk Users Mailing List - Non-Commercial Discussion Sent: Tuesday, July 01, 2008 6:18 AM Subject: Re: [asterisk-users] queue welcome message Hello Tarek, thank you for your idea. But this only would work for the first caller - when the moh starts. all other callers go directly into moh on the position where the first caller is in moh. So this does not work. :-( Anyone an other idea? thank you Martin - Original Message - From: Tariq .. To: Asterisk Users Mailing List - Non-Commercial Discussion Sent: Monday, June 30, 2008 5:13 PM Subject: Re: [asterisk-users] queue welcome message the only suggestion i would have for you is to use a SINGLE file for your MOH .. and you record the welcoming note in the begining of the file.. so whenever a caller comes in .. they will hear the MOH .. which has the welcoming note before the music starts... i know it's a stupid trick but it does the work for your needs... Salam Tarek Sawah -- From: [EMAIL PROTECTED] To: asterisk-users@lists.digium.com Date: Mon, 30 Jun 2008 09:19:27 +0200 Subject: [asterisk-users] queue welcome message Hi all! I would like to ask, how you realize the following in a call queue: When a caller gets into a queue how can I play a welcome Message to this caller first, before he starts hearing the music? We now use a playback before the caller gets into the queue. But when the queue is closed the caller heared already that somebody will pick up soon, but then gets into voicemail - because the queue has no members. So it would be great to let the queue welcome the caller at first and then start music. Is this possible? specifiing a queue-youarenext does only work when the caller is not the first in line. specifiing a periodic announce does play the message after the periodic-announce-frequency has been over. Is there also something else we can use? Thank you Martin Earn cashback on your purchases with Live Search - the search that pays you back! Learn More ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] queue welcome message
Hi all! I would like to ask, how you realize the following in a call queue: When a caller gets into a queue how can I play a welcome Message to this caller first, before he starts hearing the music? We now use a playback before the caller gets into the queue. But when the queue is closed the caller heared already that somebody will pick up soon, but then gets into voicemail - because the queue has no members. So it would be great to let the queue welcome the caller at first and then start music. Is this possible? specifiing a queue-youarenext does only work when the caller is not the first in line. specifiing a periodic announce does play the message after the periodic-announce-frequency has been over. Is there also something else we can use? Thank you Martin ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] queue welcome message
Hello Tarek, thank you for your idea. But this only would work for the first caller - when the moh starts. all other callers go directly into moh on the position where the first caller is in moh. So this does not work. :-( Anyone an other idea? thank you Martin - Original Message - From: Tariq .. To: Asterisk Users Mailing List - Non-Commercial Discussion Sent: Monday, June 30, 2008 5:13 PM Subject: Re: [asterisk-users] queue welcome message the only suggestion i would have for you is to use a SINGLE file for your MOH .. and you record the welcoming note in the begining of the file.. so whenever a caller comes in .. they will hear the MOH .. which has the welcoming note before the music starts... i know it's a stupid trick but it does the work for your needs... Salam Tarek Sawah From: [EMAIL PROTECTED] To: asterisk-users@lists.digium.com Date: Mon, 30 Jun 2008 09:19:27 +0200 Subject: [asterisk-users] queue welcome message Hi all! I would like to ask, how you realize the following in a call queue: When a caller gets into a queue how can I play a welcome Message to this caller first, before he starts hearing the music? We now use a playback before the caller gets into the queue. But when the queue is closed the caller heared already that somebody will pick up soon, but then gets into voicemail - because the queue has no members. So it would be great to let the queue welcome the caller at first and then start music. Is this possible? specifiing a queue-youarenext does only work when the caller is not the first in line. specifiing a periodic announce does play the message after the periodic-announce-frequency has been over. Is there also something else we can use? Thank you Martin -- Earn cashback on your purchases with Live Search - the search that pays you back! Learn More -- ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Queue with different music for each caller
Hello Thomas
you can use different music for each caller if you like.
in extensions.conf you can set the music class.
exten = s,n,Set(CHANNEL(musicclass)=yourmusicforthiscaller)
and if you like different music for each caller you can set a variable with
the musicname and then set the musicclass:
exten = s,n,Set(mymusicclass=${CALLERID(num)}musicclass)
exten = s,n,Set(CHANNEL(musicclass)=${mymusicclass})
so you set the music for each calling number
when the caller has the number 1234 the music will be 1234musicclass
when the caller has the cid 456 the music will be 456musicclass
you see, everything is possible.
hope to help,
Martin
- Original Message -
From: Thomas Winter [EMAIL PROTECTED]
To: asterisk-users@lists.digium.com
Sent: Tuesday, June 24, 2008 11:22 AM
Subject: [asterisk-users] Queue with different music for each caller
Hi,
is there an possibilty to have for each caller different music when queued.
I see there only the global musiconhold = default in queues.conf, what menas
same musci for all waiting callers.
Any other idea to realize this?
best regards
Thomas
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
___
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
AstriCon 2008 - September 22 - 25 Phoenix, Arizona
Register Now: http://www.astricon.net
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Queue with different music for each caller
Hello Thomas, no problem. In asterisk 1.6 use SetMusicOnHold(musiconholdname) then it will work in older Asterisk versions! br, Martin - Original Message - From: Thomas Winter [EMAIL PROTECTED] To: Asterisk Users Mailing List - Non-Commercial Discussion asterisk-users@lists.digium.com Sent: Tuesday, June 24, 2008 5:50 PM Subject: Re: [asterisk-users] Queue with different music for each caller On Tuesday 24 June 2008 15:22, Martin Schrott - thinking:systems wrote: Hello Thomas you can use different music for each caller if you like. in extensions.conf you can set the music class. exten = s,n,Set(CHANNEL(musicclass)=yourmusicforthiscaller) Hi Martin, thanks for your suggestion, I forgot to notice that Iam still using 1.2.X Jun 24 17:45:31 ERROR[17784]: pbx.c:1437 ast_func_write: Function CHANNEL not registered So, this didnt work for me. best regards Thomas ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] asterisk v1.6 monitor_exec
Hi all, can anybody tell me how I get asterisk calling an executable after a queue call? only setting MONITOR_EXEC and MONITOR_FILENAME does not work anymore! We use normal monitor to record _in and _out files. does work perfectly. But calling an exec does not do anything. We also tried setting MONITOR_OPTIONS=b Can anybody tell us, how we can get that running? We would like to call something like: /usr/bin/xyz -a -b -c Thank you very much, Martin ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2008 - September 22 - 25 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] asterisk v1.6 queue() continue after answered call
Hi list, we upgraded to v1.6 and have a problem understanding the queue() behaveour of the v1.6 in queues. we try to set the queue up to not hangup if an agent answeres the call but then hangs up again. we would then like the queue to go on in the dialplan. But the queue does not want to go on and hangs up. :-( we triyed to use the c flag and the timeoutrestart both did not work. How could we set up the queue to go on after a call? Hope anybody can help. thank you Martin ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] AgentCallBackLogin vs AddQueueMember
Hi Kevin, Hi list, you are right, acting now is not needed, when callbacklogin will be removed anywhere in future... But thinking how to realice alternatives can't be so wrong. Callbacklogin gives a very simple way to use more queues for one agent, which only has to logon to only one system. No need to make dbs or tables for saving, where the agent has to be logged in. No need to create your own login functions. No additional tables, which members are logged in. Just one entry in queues.conf and agents.conf This is simple. For sure, it would also be possible to use addqueuemembers functionality: -make own tables where you save, in which queues each member has to be logged in. -create a table, to see wich members exist and which are logged in. Do not forget the destination to call them. -create a login functionallity, to use your tables. -Then add the member to each queue by calling aqm once for each queue. (Our cpu will thank us) for using it so much. -do not think of logs. (there are patches helping you... and members-name, wich you can use... try how) It is as simple as callbacklogin ;-) Next difficulty is, using agent-groups... When we use aqm to call different groups, we only have to make groups in agents.conf and put them into the queues. That is it. But no problem, we also can create additional tables and script a little bit. We do not need to sleep at night. To summerice: using aqm we would have to make own tables of groups. Then we have to make tables of members, that are logged in. Then we have to read this tables, check who is logged in, then call aqm for each member that is logged in and put it into each queue, the third table has saved this member for... !!! Only to write it here is more work then using agent callbacklogin! scripting it would be crazy, when callbacklogin does it for us !!! So we can only hope, that there will be an alternative application, that works like callbacklogin. I am sure, a lot of cc designers will stop upgrading, if callbacklogin is removed and now new simmilar application is provided! Nobody can effort to do this additional work to change all dialplans. :-) Where is the problem keeping callbacklogin as additional feature in future versions. Nobody has to support or change it. Just keep it working. Or create a new application that does all the same, when you can't stand it. If you can tell me in thre lines how to use addqueuemember doing all things we need from callbacklogin app, then I will use it from today on. Othervise it is a reinventing of the wheel. Hope there will be a alternate application in newer versions of asterisk. Thanks Martin - Original Message - From: Kevin P. Fleming [EMAIL PROTECTED] To: Alan Ferrency [EMAIL PROTECTED] Cc: Asterisk Users Mailing List - Non-Commercial Discussion asterisk-users@lists.digium.com Sent: Wednesday, April 11, 2007 11:45 PM Subject: Re: [asterisk-users] AgentCallBackLogin vs AddQueueMember Alan Ferrency wrote: However, this is not what we need. This adds a phone channel to the queue, and does not track which person is using that phone. This means that all queue activity is associated with a SIP channel in the logs, which is not acceptable. Right. This is why we added the 'membername' argument to the AddQueueMember application, so that queue logs can reflect a logical name for the queue member, regardless of what channel/interface they logged in from. Using this map of people to phones, our dial plan would then need to ensure that: - a person cannot be logged into more than one phone - only one person at a time can be logged into a phone - queue activity logs are associated with a person, not a phone For points #1 and #2, you are correct that this logic will have to be built. Point #3 is already taken care of by the addition of the 'membername' as I commented on above. However, I personally see this as a huge benefit; I much prefer Asterisk to provide mechanisms for users to do things, but not the policy on how they are to be used. When chan_agent is in use, you don't get to decide what to do if a second user tries to log in from the same channel, that has been decided for you. If instead you write that logic in the dialplan (or start from an example you find in the docs, on the wiki, etc.) you can completely control how the system behaves. Can the AddQueueMember solution handle the equivalent of autologoff if a queue member fails to answer a queued call in time? Absolutely; the example in doc/queues-with-callback-members.txt shows how to do it. To me, saying We removed the AgentCallbackLogin() application because you can reimplement it completely in the dialplan therefore it isn't necessary is just like saying We removed the VoiceMail() application because you can reimplement it in the dialplan. If that was true, we would have already done it. In fact there is an effort under way to do exactly that, and for the reason I outlined above: today, if you want the voicemail
Re: [asterisk-users] AgentCallBackLogin vsAddQueueMember
sorry, was only for users list... Hi Kevin, Hi list, you are right, acting now is not needed, when callbacklogin will be removed anywhere in future... But thinking how to realice alternatives can't be so wrong. Callbacklogin gives a very simple way to use more queues for one agent, which only has to logon to only one system. No need to make dbs or tables for saving, where the agent has to be logged in. No need to create your own login functions. No additional tables, which members are logged in. Just one entry in queues.conf and agents.conf This is simple. For sure, it would also be possible to use addqueuemembers functionality: -make own tables where you save, in which queues each member has to be logged in. -create a table, to see wich members exist and which are logged in. Do not forget the destination to call them. -create a login functionallity, to use your tables. -Then add the member to each queue by calling aqm once for each queue. (Our cpu will thank us) for using it so much. -do not think of logs. (there are patches helping you... and members-name, wich you can use... try how) It is as simple as callbacklogin ;-) Next difficulty is, using agent-groups... When we use aqm to call different groups, we only have to make groups in agents.conf and put them into the queues. That is it. But no problem, we also can create additional tables and script a little bit. We do not need to sleep at night. To summerice: using aqm we would have to make own tables of groups. Then we have to make tables of members, that are logged in. Then we have to read this tables, check who is logged in, then call aqm for each member that is logged in and put it into each queue, the third table has saved this member for... !!! Only to write it here is more work then using agent callbacklogin! scripting it would be crazy, when callbacklogin does it for us !!! So we can only hope, that there will be an alternative application, that works like callbacklogin. I am sure, a lot of cc designers will stop upgrading, if callbacklogin is removed and now new simmilar application is provided! Nobody can effort to do this additional work to change all dialplans. :-) Where is the problem keeping callbacklogin as additional feature in future versions. Nobody has to support or change it. Just keep it working. Or create a new application that does all the same, when you can't stand it. If you can tell me in thre lines how to use addqueuemember doing all things we need from callbacklogin app, then I will use it from today on. Othervise it is a reinventing of the wheel. Hope there will be a alternate application in newer versions of asterisk. Thanks Martin - Original Message - From: Kevin P. Fleming [EMAIL PROTECTED] To: Alan Ferrency [EMAIL PROTECTED] Cc: Asterisk Users Mailing List - Non-Commercial Discussion asterisk-users@lists.digium.com Sent: Wednesday, April 11, 2007 11:45 PM Subject: Re: [asterisk-users] AgentCallBackLogin vs AddQueueMember Alan Ferrency wrote: However, this is not what we need. This adds a phone channel to the queue, and does not track which person is using that phone. This means that all queue activity is associated with a SIP channel in the logs, which is not acceptable. Right. This is why we added the 'membername' argument to the AddQueueMember application, so that queue logs can reflect a logical name for the queue member, regardless of what channel/interface they logged in from. Using this map of people to phones, our dial plan would then need to ensure that: - a person cannot be logged into more than one phone - only one person at a time can be logged into a phone - queue activity logs are associated with a person, not a phone For points #1 and #2, you are correct that this logic will have to be built. Point #3 is already taken care of by the addition of the 'membername' as I commented on above. However, I personally see this as a huge benefit; I much prefer Asterisk to provide mechanisms for users to do things, but not the policy on how they are to be used. When chan_agent is in use, you don't get to decide what to do if a second user tries to log in from the same channel, that has been decided for you. If instead you write that logic in the dialplan (or start from an example you find in the docs, on the wiki, etc.) you can completely control how the system behaves. Can the AddQueueMember solution handle the equivalent of autologoff if a queue member fails to answer a queued call in time? Absolutely; the example in doc/queues-with-callback-members.txt shows how to do it. To me, saying We removed the AgentCallbackLogin() application because you can reimplement it completely in the dialplan therefore it isn't necessary is just like saying We removed the VoiceMail() application because you can reimplement it in the dialplan. If that was true, we would have already done it. In fact there is an effort under way to do exactly that, and for the reason I outlined above:
[asterisk-users] exec after recording agents
Hi all, Hope somebody can help us. What we try to do: + record a incoming call with the recordagents option in agents.conf + after recording start a script to convert to mp3. The script is running perfect. We can also use that with normal monitoring and monitor_exec or with the monitor function in queues. but in agents.conf we cannot find a possibility to activate a script after the recording. Anyone a idea, how we could run our script after a agent recording? ? ? Thank you for your help! MArtin ___ --Bandwidth and Colocation provided by Easynews.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
