So by multiple calls are you talking call waiting? its already enabled, if i call the extension directly call waiting is functioning, or are you saying that i need to configure the same extension multiple times on the same device (Ext 1/2 on Cisco, or line 1/2 on aastra) .
_________________________________________________________________________On Mon, Jul 28, 2014 at 12:09 PM, Michael Jerris <mike@jerris.com> wrote:
First, you need to have the phone configured to allow multiple calls, then you would use the "simo" attribute on the agents to have mod_fifo deliver multiple calls at the same time.On Jul 27, 2014, at 2:17 AM, Chris Tunbridge <blasterjr@gmail.com> wrote:_________________________________________________________________________X-Lite Soft Client.Jitsi SoftClientPolycom SoundPoint IP 550Cisco SPA525G2I have a script that creates fifo's on the fly, and at one point i had it worked with call waiting, but i don't remember what i did at that time, nor what changed (months and months ago) however, i cannot seem to get Calls in FIFO to trigger call waiting on the phones that are set as Members of that FIFO Queue.Basically if i have 2 calls come in, and i answer one, i want the 2nd call to ring through to my phone (as well as others) even though i am already on a call, Call Waiting currently works if i dial directly to the device (say extension to extension calling) or even by routing a call straight to an extension, then trying a second call to that extension.
I have tested this with the same results on the following
Aastra 6757i (Firmware 2.6.2019 and 3.3.something)
The behavior is the same regardless of the endpoint, i even tried creating loopbacks in order to trick the system, but from what i can tell, the server isn't even attempting to call the phone that's currently busy.
The problem is that we have clients who get off one call, and have to wait 30+ seconds (fifo_member_timeout) before they can answer the next call, I've tried adjusting lag and it seems to have no impact.
I'm working on getting a wireshark of this behavior, but i just wanted to reach out and see if the current behavior is in fact the correct one, and if not, or if there's a solution what i can do about it.
Have i overlooked something ridiculously small?Please let me know if you need anymore information.
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
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
_________________________________________________________________________
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
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
Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server
http://www.cudatel.com
Official FreeSWITCH Sites
http://www.freeswitch.org
http://wiki.freeswitch.org
http://www.cluecon.com
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