[Freeswitch-users] Dial multiple users for "conference" call

[Michael Nielsen]

However, my country_code variable is available before the loopback:

2016-01-13 14:08:43.143791 [INFO] mod_dptools.c:1692 country_code +44

On Wed, Jan 13, 2016 at 1:57 PM, Michael Nielsen <mic.niel84 at gmail.com>
wrote:

> I can tell from the cli that the country_code variable is empty:
>
> Dialplan: loopback/293234-b Action set(dialed_number=${country_code}
>  293234) INLINE
>
> EXECUTE loopback/293234-b set(dialed_number= 293234)
>
>
> So my subscriber variables doesn't get used when using mod_conference...
>
> On Wed, Jan 13, 2016 at 1:54 PM, Michael Nielsen <mic.niel84 at gmail.com>
> wrote:
>
>> Hi Bote,
>>
>> Thank you so much for all your detailed info. That helped a lot and
>> solved almost everything.
>>
>> Final question... When I use the <action
>> application="conference_set_auto_outcall" data="loopback/293234"/>, doesn't
>> loopback means that it's try and dial 293234 from a matching dial plan
>> already existing within my FreeSWITCH?
>>
>> The case is, that I've got a dial plan recognising expression="^(\d{3,20})$"
>> etc.
>> And if a number doesn't contain a valid country code I'll append it
>> automatically according to the subscriber who initiate the calls.
>> So my subscriber for example has a variable set country_code = +44. When
>> I dial something it appends +44 if there is no country code.
>>
>> This works if I call something else than my conference dial plan, but
>> when calling the conference dial plan and using loopback it doesn't work.
>>
>> Does it make sense and can you help?
>>
>> On Tue, Jan 12, 2016 at 6:44 PM, Bote Man <bote_radio at botecomm.com>
>> wrote:
>>
>>> Michael, I make extensive use of the FreeSWITCH outbound conference
>>> calling feature. I recently figured that I got the results that you (and I)
>>> desire with these 2 lines in the dialplan of the extension that initiates
>>> the outbound conference call:
>>>
>>>
>>>
>>> <action application="set"
>>> data="conference_auto_outcall_caller_id_name=${caller_id_name}"/>
>>>
>>> <action application="set"
>>> data="conference_auto_outcall_caller_id_number=${caller_id_number}"/>
>>>
>>>
>>>
>>> It’s not clear to me which of the many, many, many Caller*ID variables
>>> are the best to use overall, but these are the ones that send the
>>> originating extension number and name as FreeSWITCH knows them to the
>>> dialed conferees. I find that effective_caller_id_number is not always
>>> effective J
>>>
>>>
>>>
>>> Of course, you can set caller_id_* to effective_* or any other
>>> assignments as needed; experimentation yields a lot of knowledge here. Use
>>> the “log” application liberally in your conference dialplan extension to
>>> display as many variables as you need to determine which holds the desired
>>> values, that’s how I did it. A lot of them are empty, some are default,
>>> nothing is set in stone so change and set them the way you see fit.
>>>
>>>
>>>
>>>
>>>
>>> Also, in answer to your previous query about the conferees still ringing
>>> after the originator hangs up, add the “endconf” flag to your conference
>>> kick-off string:
>>>
>>>
>>>
>>> <action application="conference" data="myconf at default
>>> ++flags{endconf|moderator|nomoh}"/>
>>>
>>>
>>>
>>> myconf – the “name” of the conference as FreeSWITCH knows it, can be
>>> pretty much anything readable, numbers, letters, literal value, variable
>>> replacement, etc.
>>>
>>>
>>>
>>> default – the conference profile to use as configured in
>>> autoload_configs/conference.conf.xml
>>>
>>>
>>>
>>> moderator flag – pulls in a different set of controls as specified in
>>> the config file mentioned above.
>>>
>>>
>>>
>>> Hope this helps.
>>>
>>>
>>>
>>> Bote
>>>
>>>
>>>
>>>
>>>
>>> *From:* Michael Nielsen
>>> *Sent:* Tuesday, 12 January, 2016 04:27
>>> *Subject:* Re: [Freeswitch-users] Dial multiple users for "conference"
>>> call
>>>
>>>
>>>
>>> Hi Larry,
>>>
>>>
>>>
>>> As you can see from my example, I am trying to set that exact variable:
>>>
>>> <action application="set"
>>> data="conference_auto_outcall_caller_id_number=${effective_caller_id_number}"/>
>>>
>>> But I want to set it from the effective_caller_id_number, so I can get
>>> the caller ID from the person who initiated the conference call.
>>>
>>>
>>>
>>> On Mon, Jan 11, 2016 at 7:50 PM, Larry Morley <lmorley at neny.cslimits.net>
>>> wrote:
>>>
>>> Michael,
>>>
>>> Go back and have another look at the "mad boss" example. The variable
>>> you likely want to set in this instance is
>>> "conference_auto_outcall_caller_id_number".
>>>
>>> Basically, what Mike J was telling you is that not all variables are
>>> salient; are set by FreeSwitch; have any meaning whatsoever; in the context
>>> of certain parts of a given FreeSwitch configuration.
>>>
>>> From the "mad boss" example:
>>>
>>> <!--These params effect the outcalls made once you join-->
>>>
>>>         <action application="set"
>>> data="conference_auto_outcall_caller_id_name=Mad Boss"/>
>>>
>>>         <action application="set"
>>> data="conference_auto_outcall_caller_id_number=0911"/>
>>>
>>> Hope that helps,
>>> Larry
>>>
>>> On Jan 11, 2016 9:02 AM, "Michael Nielsen" <mic.niel84 at gmail.com> wrote:
>>>
>>> https://freeswitch.org/confluence/display/FREESWITCH/Channel+Variables
>>>
>>>
>>>
>>> On Mon, Jan 11, 2016 at 3:00 PM, Michael Nielsen <mic.niel84 at gmail.com>
>>> wrote:
>>>
>>> In other dial plans I'm able to use ${effective_caller_id_number} from
>>> my directory.
>>>
>>> That means, if my subscriber 1001 are calling I can use 1001 as caller
>>> ID, so my called parties know who it is.
>>>
>>>
>>>
>>> On Mon, Jan 11, 2016 at 2:58 PM, Michael Jerris <mike at jerris.com> wrote:
>>>
>>>
>>>
>>> On Monday, January 11, 2016, Michael Nielsen <mic.niel84 at gmail.com>
>>> wrote:
>>>
>>> Seems as if it has nothing to do with multiple parties speaking
>>> together, just simultaneously calling them.
>>>
>>>
>>>
>>> Back to mod_conferece and the madboss example. It seems to work, but not
>>> getting the variable from the caller:
>>>
>>>
>>>
>>> 1) If I call some numbers, and hang up before the 60 seconds timeout -
>>> the numbers keeps ringing for 60 seconds, even though I as initiator have
>>> hung up.
>>>
>>> 2) <action application="set"
>>> data="conference_auto_outcall_caller_id_number=${effective_caller_id_number}"/>
>>> doesn't seems to be acknowledge, it shows Unknown number.
>>>
>>>
>>>
>>> What do you think effective_caller_id_number is here?  this is not a
>>> variable that is automatically set
>>>
>>>
>>>
>>> _________________________________________________________________________
>>> Professional FreeSWITCH Consulting Services:
>>> consulting at freeswitch.org
>>> http://www.freeswitchsolutions.com
>>>
>>> Official FreeSWITCH Sites
>>> http://www.freeswitch.org
>>> http://confluence.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/20160113/eabdf4dd/attachment-0001.html