Avaya PBX 的版本控制/配置管理?

发布于 2024-08-02 12:07:01 字数 279 浏览 7 评论 0原文

在 Acme Widgets,我们使用 Avaya 8xxx 系列 PBX。编码到 PBX 中的一些向量非常重要,因为如果以错误的方式更改它们,几乎所有电话领域的应用程序和功能都会变得混乱(IVR、CTI、CRM 和 ACD)。

最近有一些讨论,我们对过去如何编码某些向量存在分歧,而且越来越多的情况是多个不同的人正在对这些非常重要的组件进行更改。

我曾询问我的 PBX 管理员是否有相当于 PBX 矢量配置管理/版本控制工具的东西,但他不相信有。大家觉得怎么样?有人听说过这样的事情吗?

谢谢!

Here at Acme Widgets, we use an Avaya 8xxx series PBX. Some of the Vectors that are coded into the PBX are super important, in that if they're changed in the wrong way, pretty much all of our telephony arena applications and features go haywire (IVR, CTI, CRM, and ACD).

There have been some recent discussions where we've disagreed as to how certain vectors have been coded in the past, and there have also been increasing situations where multiple different folks are making changes to these highly important components.

I've asked my PBX administrator if there is something equivalent to a Configuration Management/Version Control tool for PBX Vectors, and he doesn't believe there are. What do y'all think? Has anyone ever heard of such a thing?

Thanks!

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

我们只是彼此的过ke 2024-08-09 12:07:01

我不知道有专门用于 PBX Vector 的 VCS。它实际上取决于此类对象的内部格式。

根据“配置 Avaya Definity PBX” :

矢量化使用概述每个站点覆盖路径的表格,而不是单独配置每个站点(搜索配置)。根据您的 Avaya Definity 软件版本,该表可以支持每个引导 13 到 32 条或更多路由。

这意味着:

  • 如果它是基于文本的,则任何 VCS 工具都可以存储向量的 2 个版本之间的增量,
  • 对于版本工具的选择,更重要的是如何完成更新:从单个位置或使用代理通过全国。在前一种情况下,集中式 VCS(Subversion、Perforce 等)就足够了,可以直接访问存储矢量定义的单个存储库。在后一种情况下,需要 DVCS(Mercurial、Git,...),以便每个代理能够使用完整的本地存储库,然后在它们之间进行同步。

I do not know of a VCS specialized in PBX Vector. It actually depends on the internal format of such an object.

According to "Configuring Avaya Definity PBX":

vectoring uses a table outlining the coverage path for each station, instead of each station being configured individually (hunt-to configuration). Depending upon your Avaya Definity software version, the table can support anywhere from 13 to 32 routes or more per vector.

That means:

  • if it is text-based, any VCS tool can store deltas between 2 versions of a vector
  • what will be more important as to the choice of a Version tool is how the update is done: from a single location, or with agent through the country. In the former case, a centralized VCS (Subversion, Perforce, ...) is enough, with a direct access to a single repository storing the vector deifnitions. In the latter case, a DVCS (Mercurial, Git, ...) is needed, in order for each agent to work with the full local repository, and then synchronize it between them.
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文