Perimeta configuration and management in the MetaView GUI


You can use the Perimeta Operator role in MetaView Web to configure your Perimeta using MetaView's intuitive GUI. Now you don't have to use the Command Line Interface whenever you need to configure your Perimeta. 


The Perimeta Operator user role sits alongside existing Perimeta provisioning user roles. MetaView Web can display up to 300 adjacencies, 30 service interfaces and 30 media addresses for every Perimeta in your network. It provides GUI access to the Message Manipulation Framework (MMF) and LUA, and also provides a 3rd party API that you can use for provisioning on your Perimeta.

The MetaView GUI is responsive, providing instant response to your actions. If MetaView and Perimeta are busy processing information in the background and can't give you an instant response, MetaView gives you clear feedback so that you know the interface has not hung and will respond in a reasonable time. Using MetaView to configure your Perimeta does not affect your Perimeta's mainline performance or capacity.



Who might need to use MetaView to configure Perimeta? You could break down your users into these three groups.

  • Provisioners are trained specifically for provisioning PBXs and peering agreements and activating these new services.
  • Operators are trained to do frequent, repetitive tasks, similar to "Provisioners". However, they are able to activate service in more complex deployments (e.g. GR deployments and those requiring new local IPs or VLANs). They also have more access than Provisioners to tweak and fix existing configuration.
  • Administrators are required to fully configure Perimeta and have access to all configuration options.

From Perimeta V3.9 onwards, MetaView Web presents three sets of user roles to meet these use cases.

The existing Perimeta Provisioning user role

  • Exposes the minimum configuration required for activating new service on Perimeta
  • Configuration exposed in a search-based GUI
  • Includes access to configuration on Perimeta, CFS and EAS as well as flow-through provisioning across Perimeta and CFS

The new Perimeta Operator user role

  • Configuration exposed in a tree-based GUI
  • Exposes commonly-used Perimeta configuration relevant to a lower-level admin or advanced provisioning engineer
    • Add new local IP addresses and VLANs (i.e. service interfaces)
    • Add accounts, configure some account limits (call setup, message rate and registrations) and associate accounts with adjacencies
    • Add interop profiles, configure some interop profile settings and associate interop profiles with adjacencies
    • Add/modify all adjacencies, including;
      • Configure some CAC limits (call setup, message rate and registrations) on an adjacency
      • Configure some call media policy configuration (media bypass policy, media descriptions, SDP repeats and enabling transcoding) on an adjacency
      • Add the remote address range of an adjacency to the trusted sources
      • Set up simple routing by specifying a core adjacency to route to on an adjacency
    • Add/modify routing rules based on destination domain-based and destination trunk group ID
  • Geographic Redundancy of Perimeta is supported

The new Perimeta Expert Management user role

  • Will expose all Perimeta configuration as an alternative to the CLI
  • Configuration exposed in a tree-based GUI

MetaView Server must support managing up to 33 Perimeta systems and up to 75 simultaneous users. Each instance can support up to 300 adjacencies, 30 service interfaces and 30 media addresses when using MetaView Web.