[Freeswitch-users] Forked dialing withdifferentchannelvarsset...

UV uv at talknet.com.au
Fri Jun 6 07:49:00 PDT 2008 

Thanks Brian,

That answers my question (not complaint) perfectly.

For our internal documentation purposes, I assume, therefore, this format:
{foo=bar}sofia/blah1/blah,{foo=baz}sofia/blah2/blah
Is equivalent to that:
{foo=bar}sofia/blah1/blah,sofia/blah2/blah

And this format:
[foo=bar]sofia/blah1/blah,sofia/blah2/blah
Means blah1 channel will have foo=bar where blah2 channel won't have the foo
variable at all.

-----Original Message-----
From: freeswitch-users-bounces at lists.freeswitch.org
[mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of Brian
West
Sent: Friday, June 06, 2008 11:16 PM
To: freeswitch-users at lists.freeswitch.org
Subject: Re: [Freeswitch-users] Forked dialing
withdifferentchannelvarsset...

Yes the square braces and curly braces mean two different things.

For example if you do:

{foo=bar}sofia/blah1/blah,sofia/blah2/blah

foo=bar will be set on both blah1 and blah2 channels.

In this example:

[foo=bar]sofia/blah1/blah,[foo=baz]sofia/blah2/blah

In this example foo will have different values for each leg depending  
on which one is bridged to in the end.

If sofia/blah1 answers foo will be bar.. if sofia/blah2 answers foo  
will be baz

/b



On Jun 6, 2008, at 3:08 AM, Michael Collins wrote:

> I think the square brackets and the curly brackets mean two different
> things on the API originate command.  When bkw or anthm responds (wink
> wink) I'll update the bridge and/or originate wiki entries.
>
> -MC
>
>> -----Original Message-----
>> From: freeswitch-users-bounces at lists.freeswitch.org
> [mailto:freeswitch-
>> users-bounces at lists.freeswitch.org] On Behalf Of UV
>> Sent: Friday, June 06, 2008 12:20 AM
>> To: freeswitch-users at lists.freeswitch.org
>> Subject: Re: [Freeswitch-users] Forked dialing
>> withdifferentchannelvarsset...
>>
>> It is quite confusing...
>>
>> I would think the syntax would utilize the curly brackets and not the
>> square
>> brackets:
>>
>> <action application="bridge"
>> data="{effecitive_caller_id_number=1234}sofia/blah/blah,
>> {effective_caller_id_number=55555}sofia/blah/blah"/>
>>
>> This is how we use it on the API ORIGINATE commands as described in
>> http://wiki.freeswitch.org/wiki/Freeswitch_IVR_Originate
>>
>> but it is described also with the square brackets on
>> http://wiki.freeswitch.org/wiki/Misc._Dialplan_Tools_bridgecall
>>
>> Are both applicable?
>>
>> -----Original Message-----
>> From: freeswitch-users-bounces at lists.freeswitch.org
>> [mailto:freeswitch-users-bounces at lists.freeswitch.org] On Behalf Of
>> Michael
>> Collins
>> Sent: Friday, June 06, 2008 4:34 PM
>> To: freeswitch-users at lists.freeswitch.org
>> Subject: Re: [Freeswitch-users] Forked dialing with
>> differentchannelvarsset...
>>
>> Brian,
>>
>> Is this syntax going to be tagged for 1.0.1?  I ask because the
>> documentation guys are trying to get a handle on the deltas between
>> 1.0.0 and 1.0.1.
>>
>> Thanks!
>>
>>> -----Original Message-----
>>> From: freeswitch-users-bounces at lists.freeswitch.org
>> [mailto:freeswitch-
>>> users-bounces at lists.freeswitch.org] On Behalf Of Brian West
>>> Sent: Thursday, June 05, 2008 10:24 PM
>>> To: freeswitch-users at lists.freeswitch.org
>>> Subject: Re: [Freeswitch-users] Forked dialing with different
>>> channelvarsset...
>>>
>>> Try this.. i'm kinda shocked you didn't see us talking about this
> over
>>> and over in the pasty 24 hours.  You'll need to make sure you're on
>>> the latest code for this:
>>>
>>> <action application="bridge"
>>> data="[effecitive_caller_id_number=1234]sofia/blah/blah,
>>> [effective_caller_id_number=55555]sofia/blah/blah"/>
>>>
>>> /b
>>>
>>>
>>>
>>>> On Jun 5, 2008, at 10:53 PM, Rupa Schomaker (lists) wrote:
>>>
>>>> I have a seemingly simple problem that I can't figure out how to
>>>> implement.
>>>>
>>>> Simplified Problem:
>>>>
>>>> I'd like to have my cell phone and my deskphone ring at the same
>> time.
>>>> This seems simple, but there is a small caveat.  I need to have a
>>>> channel variable set differently for my cellphone.
>>>>
>>>> Specifically: voicepulse requires you to have the caller id number
>> and
>>>> caller id name set to the number in order to pass it on to the
>>>> PSTN.  I
>>>> want to see the callerid name on my deskphone however.
>>>>
>>>> ===
>>>>
>>>> Ok, normally, I'd just do a:
>>>>
>>>> <action application="bridge"
>>>> data="sofia/internal/101%$${domain},sofia/gateway/voicepulse/$$
>>>> {cellnumber}"/>
>>>>
>>>> but then my cell phone shows Unknown or Blocked when receiving the
>>>> call.
>>>>
>>>> If prior to that I do:
>>>>
>>>> <action application="set"
>>>> data="effective_caller_id_name=${caller_id_number}"/>
>>>>
>>>> Then I get the correct callerid on my cell, but only the callerid
>>>> number
>>>> on my deskphone.
>>>>
>>>> I asked on #freeswitch and had some hints, but they either went
> over
>>>> my
>>>> head or I didn't communicate my problem right.
>>>>
>>>> Using multiple extension entries with continue="yes" doesn't seem
> to
>>>> execute them in parallel (so the deskphone and the cell don't ring
>> at
>>>> the same time).
>>>>
>>>> The "obvious" answer is how I implemented this in asterisk -- and
>>>> maybe
>>>> that is my problem, thinking in terms of asterisk.
>>>>
>>>> The bridge equivalent would be the dial() app.  This allows me to
>> dial
>>>> back into the dialplan if I use the "local" channel.  This gives a
>>>> level
>>>> of indirection that would then let me modify the channelvars as
>>>> necessary.
>>>>
>>>> The only way I can see to "call" back into the dialplan is to use
>> the
>>>> transfer application.  But that can't do multiple extensions in
>>>> parallel
>>>> so doesn't solve my problem.
>>>>
>>>> What am I missing?
>>>>
>>>> -Rupa
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>> _______________________________________________
>> 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
>>
>>
>> _______________________________________________
>> 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
>
> _______________________________________________
> 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


_______________________________________________
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

More information about the FreeSWITCH-users mailing list