[Freeswitch-users] Current timestamp variable in dialplan?

[Antony Stone]

On Friday 04 November 2022 at 19:13:27, Brian West wrote:

> Antony,
> 
> Maybe you can come to our next office hours?

Er, what?  Where are you?

> On Fri, Nov 4, 2022 at 1:05 PM Antony Stone wrote:
> > On Friday 04 November 2022 at 18:25:21, Brian West wrote:
> >
> > > I'd not recommend doing that, because every time you do a get var, you
> > > cause a pool allocation and doing this in a loop will make your session
> > > pool swell at the rate of whatever you're calling get_var on.  Doing
> > > anything at all inline with the dialplan is not the right approach. 
> > > your logic and info should be all external, keying off events either
> > > on ESL or custom modules you wrote.
> > 
> > Hm, this sounds like an interesting and important conceptual aspect of
> > the way FreeSwitch works which I suspect I haven't fully "got".
> > 
> > Can you point me at the documentation which explains this, for people who
> > are more used to procedural programming, and show how we should be
> > thinking about FreeSwitch dialplans instead?
> > 
> > I'm certainly keen on using FreeSwitch in as efficient a manner as
> > possible :)


Antony.

-- 
"Black holes are where God divided by zero."

 - Steven Wright

                                                   Please reply to the list;
                                                         please *don't* CC me.