[Freeswitch-users] mod_distributor configuration advice

[Victor Chukalovskiy]

I suppose you call distributor 3 or 5 times and use "|" when bridging e.g:

<action application="bridge" 
data="{ignore_early_media=true}freetdm/${distributor(outbound_rr)}/1/a/1$1*|**freetdm/${distributor(outbound_rr)}/1/a/1$1***|**freetdm/${distributor(outbound_rr)}/1/a/1$1**"/>

Note 1: keep in mind that distributor does not randomize, but simply 
moves a pointer one step each time it's called. So for the best results 
you need to have even sum of weights in the distributor list and call it 
odd number of times from the diaplan. Or to be more precise,  M and N 
should not have a common divisor other than 1 :) where M is a sum of 
weights in the list and N is the number of times you call 
distributor(list) it in the dial-plan.

*I think that mod_distributor is lacking "randomize" logic big time!* 
Keeping track of what is dividable by what is not trivial.

Note 2: I'm not sure if {ignore_early_media=true} should be repeated 
after "|". Suggest to test or check WiKi.

Note 3: fail_on_single_reject should be set before bridge to avoid 
failing over on "USER_BUSY", "UNALLOCATED_NUMBER" etc.

Cheers,
-VIctor



On 14-05-05 02:22 PM, bedgar at vseinc.com wrote:
>
> Update:
>
> So I figured out how to use this module to cycle through the channel 
> groups.
>
> Snippet from distributor.conf.xml:
>
>     <list name="outbound_rr" total-weight="4">
>
>       <node name="t1_1_1" weight="1"/>
>
>       <node name="t1_1_2" weight="1"/>
>
>       <node name="t1_1_3" weight="1"/>
>
>       <node name="t1_1_4" weight="1"/>
>
> Snippet from dialplan:
>
>      <action application="bridge" 
> data="{ignore_early_media=true}freetdm/${distributor(outbound_rr)}/1/a/1$1"/>
>
> Follow-up question:
>
> If the channel group is fully utilized when it is comes around in list 
> how can I get the outbound call to use the next group in the list.
>
> Example:
>
> Node name t1_1_2 is slated to be used in the list for the next 
> outbound call but there are no available channels in that group.  How 
> can I get it to try the subsequent group or groups in the list until 
> an available channel is realized?
>
> The third item from my posting is still an open question:
>
> 3.  If a group that is next to be used based on the weight ends up in 
> a down state, as an automatic remedy, how could that group be excluded?
>
> Thank you,
>
> Brian
>
> *From:* freeswitch-users-bounces at lists.freeswitch.org 
> [mailto:freeswitch-users-bounces at lists.freeswitch.org] *On Behalf Of 
> *Brian Edgar
> *Sent:* Friday, May 2, 2014 2:38 PM
> *To:* freeswitch-users at lists.freeswitch.org
> *Subject:* [Freeswitch-users] mod_distributor configuration advice
>
> Good Day FS Users,
>
> I am looking to utilize mod_distributor to round robin my outbound 
> through TDM.  I have multiple 4-port Sangoma cards.  Some spans are 
> dedicated to inbound trunks from my provider and some spans are 
> dedicated to outbound.
>
> 1. I wanted to group my spans and reference these groups in 
> mod_distributor.  Is this possible?
>
> 2. If so, what would be the syntax in distributor.conf.xml?
>
> 3. In addition, if a span or group that is next to be used based on 
> the weight ends up in a down state, how could that span or group be 
> excluded as an automatic remedy?
>
> Thank you,
>
> Brian
>
>
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
>
> 
> 
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20140505/6799109f/attachment-0001.html