Is there any way to set the origination_caller_id for a FIFO outbound call to an on-hook agent? I can't find anything in the wiki about a FIFO or member variable to set this. It seems to be set to 'Queue' by default, and appears to be hardcoded in the module source. It would be nice to be able to change per FIFO queue. That way agents that handle multiple companies can more easily see which queue is calling and answer accordingly. It is not a big deal, since it does automatically set the origination_caller_id_number to 'fifo+<fifo name>'. However, depending on the phone, the caller ID number is not always readily shown, and must be looked for. Thanks to anyone who has some insight on this, -Adam
if you add {origination_caller_id_name=foo,origination_caller_id_number=123} before the static entries for the on hook agent it will prevail over the default one. If you are using 1.0.4, this feature is only available in trunk or one of the 1.0.5 pre releases. On Mon, Nov 23, 2009 at 4:49 PM, Adam Ford <lists@redbonez.net> wrote:
Is there any way to set the origination_caller_id for a FIFO outbound call to an on-hook agent? I can’t find anything in the wiki about a FIFO or member variable to set this. It seems to be set to ‘Queue’ by default, and appears to be hardcoded in the module source. It would be nice to be able to change per FIFO queue. That way agents that handle multiple companies can more easily see which queue is calling and answer accordingly.
It is not a big deal, since it does automatically set the origination_caller_id_number to ‘fifo+<fifo name>’. However, depending on the phone, the caller ID number is not always readily shown, and must be looked for.
Thanks to anyone who has some insight on this,
-Adam
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:213-799-1400
I actually tried that, as a guess, based on the configuration output of fifo list. However I am running a tarball release of 1.0.4, which would explain why it did not work for me. I appreciate the feedback, and will make a note to implement this when I update my installation. Are the svn-trunk updates pretty solid? I have not attempted an update yet, as it is a production system. Thanks, -Adam From: freeswitch-users-bounces@lists.freeswitch.org [mailto:freeswitch-users-bounces@lists.freeswitch.org] On Behalf Of Anthony Minessale Sent: Monday, November 23, 2009 5:13 PM To: freeswitch-users@lists.freeswitch.org Subject: Re: [Freeswitch-users] FIFO Orgination_caller_id if you add {origination_caller_id_name=foo,origination_caller_id_number=123} before the static entries for the on hook agent it will prevail over the default one. If you are using 1.0.4, this feature is only available in trunk or one of the 1.0.5 pre releases. On Mon, Nov 23, 2009 at 4:49 PM, Adam Ford <lists@redbonez.net> wrote: Is there any way to set the origination_caller_id for a FIFO outbound call to an on-hook agent? I can't find anything in the wiki about a FIFO or member variable to set this. It seems to be set to 'Queue' by default, and appears to be hardcoded in the module source. It would be nice to be able to change per FIFO queue. That way agents that handle multiple companies can more easily see which queue is calling and answer accordingly. It is not a big deal, since it does automatically set the origination_caller_id_number to 'fifo+<fifo name>'. However, depending on the phone, the caller ID number is not always readily shown, and must be looked for. Thanks to anyone who has some insight on this, -Adam _______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org -- Anthony Minessale II FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire AIM: anthm MSN:anthony_minessale@hotmail.com <mailto:MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com <mailto:PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <mailto:sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org <mailto:googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:213-799-1400
On Mon, Nov 23, 2009 at 4:43 PM, Adam Ford <lists@redbonez.net> wrote:
I actually tried that, as a guess, based on the configuration output of fifo list. However I am running a tarball release of 1.0.4, which would explain why it did not work for me.
I appreciate the feedback, and will make a note to implement this when I update my installation. Are the svn-trunk updates pretty solid? I have not attempted an update yet, as it is a production system.
Trunk has been very solid with a few minor exceptions. Best bet is to back up everything and do the upgrade during down time. If you have a test system that you can use as a sandbox that would be even better... -MC
And because it's static string for on-hook members, it's hard to set dynamically. For now, I'm using a callback way - whenever the sip client answered the call, it fetch the real connected number from a http server. That's not ideal because not only it add the complexity but also the callee have no idea what the number is before answer. The problem for on-hook agent is that it call the agent first, and then get one customer from the fifo queue, so it is not possible to let the agent know the real caller-id before answer. Ideas? 2009/11/24 Anthony Minessale <anthony.minessale@gmail.com>
if you add {origination_caller_id_name=foo,origination_caller_id_number=123} before the static entries for the on hook agent it will prevail over the default one.
If you are using 1.0.4, this feature is only available in trunk or one of the 1.0.5 pre releases.
On Mon, Nov 23, 2009 at 4:49 PM, Adam Ford <lists@redbonez.net> wrote:
Is there any way to set the origination_caller_id for a FIFO outbound call to an on-hook agent? I can’t find anything in the wiki about a FIFO or member variable to set this. It seems to be set to ‘Queue’ by default, and appears to be hardcoded in the module source. It would be nice to be able to change per FIFO queue. That way agents that handle multiple companies can more easily see which queue is calling and answer accordingly.
It is not a big deal, since it does automatically set the origination_caller_id_number to ‘fifo+<fifo name>’. However, depending on the phone, the caller ID number is not always readily shown, and must be looked for.
Thanks to anyone who has some insight on this,
-Adam
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
-- Anthony Minessale II
FreeSWITCH http://www.freeswitch.org/ ClueCon http://www.cluecon.com/ Twitter: http://twitter.com/FreeSWITCH_wire
AIM: anthm MSN:anthony_minessale@hotmail.com <MSN%3Aanthony_minessale@hotmail.com> GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com<PAYPAL%3Aanthony.minessale@gmail.com> IRC: irc.freenode.net #freeswitch
FreeSWITCH Developer Conference sip:888@conference.freeswitch.org <sip%3A888@conference.freeswitch.org> iax:guest@conference.freeswitch.org/888 googletalk:conf+888@conference.freeswitch.org<googletalk%3Aconf%2B888@conference.freeswitch.org> pstn:213-799-1400
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
On Mon, Nov 23, 2009 at 4:58 PM, Seven Du <dujinfang@gmail.com> wrote:
And because it's static string for on-hook members, it's hard to set dynamically. For now, I'm using a callback way - whenever the sip client answered the call, it fetch the real connected number from a http server. That's not ideal because not only it add the complexity but also the callee have no idea what the number is before answer.
The problem for on-hook agent is that it call the agent first, and then get one customer from the fifo queue, so it is not possible to let the agent know the real caller-id before answer. Ideas?
Tony and Brian were discussing this today. They bring up a really good point: do you want to risk having calls remain on hold as they bounce around looking for an agent? This can happen if you pre-determine which caller goes to which agent and the agent doesn't answer. I do understand why this feature matters to many people - it's how old school ACD systems work. However, mod_fifo is more efficient. It's hard to justify decreasing call routing efficiency in order to display the caller's info to the on-hook agent prior to answering. -MC
You do realize that the whole concept is OLD skewl. You should be popping this info via external resources when the agent is bridged to the caller and the info is there before they are done saying "thanks for calling spacely sprockets, this is George how may I help you .... " /b On Nov 23, 2009, at 7:07 PM, Michael Collins wrote:
Tony and Brian were discussing this today. They bring up a really good point: do you want to risk having calls remain on hold as they bounce around looking for an agent? This can happen if you pre- determine which caller goes to which agent and the agent doesn't answer. I do understand why this feature matters to many people - it's how old school ACD systems work. However, mod_fifo is more efficient. It's hard to justify decreasing call routing efficiency in order to display the caller's info to the on-hook agent prior to answering.
-MC
On Mon, Nov 23, 2009 at 5:12 PM, Brian West <brian@freeswitch.org> wrote:
You do realize that the whole concept is OLD skewl. You should be popping this info via external resources when the agent is bridged to the caller and the info is there before they are done saying "thanks for calling spacely sprockets, this is George how may I help you .... "
/b
Agreed! Screen pop should be easy in the 21st Century. If it's not then you've got MUCH bigger problems than caller ID being delivered to your FIFO agents...
-MC
Yes, that's what we are doing. 2009/11/24 Brian West <brian@freeswitch.org>
You do realize that the whole concept is OLD skewl. You should be popping this info via external resources when the agent is bridged to the caller and the info is there before they are done saying "thanks for calling spacely sprockets, this is George how may I help you .... "
/b
On Nov 23, 2009, at 7:07 PM, Michael Collins wrote:
Tony and Brian were discussing this today. They bring up a really good point: do you want to risk having calls remain on hold as they bounce around looking for an agent? This can happen if you pre- determine which caller goes to which agent and the agent doesn't answer. I do understand why this feature matters to many people - it's how old school ACD systems work. However, mod_fifo is more efficient. It's hard to justify decreasing call routing efficiency in order to display the caller's info to the on-hook agent prior to answering.
-MC
_______________________________________________ FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
Its the proper way to do it. And do you know the second you're bridged... if you have a phone that isn't daft... snom or polycom... the display will update to the person your bridged to. /b On Nov 23, 2009, at 7:24 PM, Seven Du wrote:
Yes, that's what we are doing.
2009/11/24 Brian West <brian@freeswitch.org> You do realize that the whole concept is OLD skewl. You should be popping this info via external resources when the agent is bridged to the caller and the info is there before they are done saying "thanks for calling spacely sprockets, this is George how may I help you .... "
/b
participants (5)
-
Adam Ford
-
Anthony Minessale
-
Brian West
-
Michael Collins
-
Seven Du