Can AST_SORCERY be used to hide dialplan implementation details?


This is the very first I’m giving a look at Sorcery.

  1. Can/should AST_SORCERY be used to protect dialplan implementation from details such as using either ASTDB, ODBC or memory (ie non-persistent) to store somthing?

  2. How can you bind ASTDB’s Foo/Bar family/key to some custom element in sorcery.conf ?

Best regards

  1. It’s not really made for that.
  2. You can’t.

Thanks for replying.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.