Hi all,
Part of an app I'm working on has a web UI for managing conferences on a
FreeSWITCH instance. One of the goals in this effort is to allow a
conference host to invite participants. We had initially used the 'api
conference dial/bgdial' commands, but unfortunately we ran into some
proble
On Mon, Oct 13, 2008 at 9:14 AM, Joe Attardi <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Part of an app I'm working on has a web UI for managing conferences on a
> FreeSWITCH instance. One of the goals in this effort is to allow a
> conference host to invite participants. We had initially used the 'ap
Woof!
On Mon, 13 Oct 2008 11:02:49 -0400, Kristian Kielhofner
<[EMAIL PROTECTED]> wrote:
> Instead of modifying the URI, why not attach your own header:
> X-conf-pin: 1234
> I haven't done it yet, but it might be as simple as:
> action application="conference" data="confname+${sip_X-conf-pin}
On Mon, Oct 13, 2008 at 1:40 PM, Andy Spitzer <[EMAIL PROTECTED]> wrote:
> Woof!
>
> On Mon, 13 Oct 2008 11:02:49 -0400, Kristian Kielhofner
> <[EMAIL PROTECTED]> wrote:
>
>> Instead of modifying the URI, why not attach your own header:
>> X-conf-pin: 1234
>> I haven't done it yet, but it might b
Hi Kristian,
Kristian Kielhofner wrote:
> I'm still pretty new at this (and I'm sure there are better ways to do
> it) but I *think* this should ask for ping 1234 unless you are coming
> from SIP host 192.168.0.5 (at least according to the $sip_from_host,
> presumably parsing the host portion of t
you don't have to use the pin in the conference
you can use a small script or some dialplan logic to ask for an arbitrary
pin then
comp it to the one from the header.
On Tue, Oct 14, 2008 at 4:11 PM, Joe Attardi <[EMAIL PROTECTED]> wrote:
> Hi Kristian,
>
> Kristian Kielhofner wrote:
> > I'm sti
