Release notes

When importing various files to 5gVision, it is now possible to drop them right to the menu item, with no need to open the corresponding screen first. This may be convenient in some cases if you chose a file in another app and started dragging it, but 5gVision did not have the screen you need open. You may drop the following files to 5gVision screens/menu items:

• .pcap file with SIP or H.323 logs to analyze them in Signaling collector.
• Vendor rates to import them to the Rate management system.
• Customer rates, code decks, or change decks.
• Your partners' CDR files to do CDR comparisons.

A new report type was added under the tab Report2: The main differences with the old Report are:

• Hours, days or weeks are in columns, while parameters are in rows. This data representation may be more convenient for some users, especially if stats are requested for only 1-4 parameters.
• It is easier to choose among several most frequently used parameters via a dedicated parameter strip.
• It is possible to sort the report by object and, for instance, see all traffic from each Customer grouped by Areas they send.

There are two options to cut off objects with very small traffic that you may not be interested to see:

• By sorting the report by one of the parameters chosen in the Sort by: dropbox. This parameter will also be highlighted in light red in the results.
• By filtering the report by one of the parameters chosen in the Filter by: dropbox. This parameter will also be highlighted in cyan in the results.

Sorting and filtering stats is currently possible by the aggregation columns only (Total, Average, Min, or Max for the interval).

Once you get a report from a DB for several parameters and both IN/OUT stats, you may easily remove some parameters or switch to only IN or only OUT stats by unselecting them in these two strips: One extra option is to switch to showing full numbers with no abbreviations like 10K or 25M via a new 1k 1000 1,000 strip. This works for the traditional Table and Report modules as well.

Two new statistical parameters were added:

• Number of hung calls per hour
• ACD of hung calls per hour

A call is considered hung if its duration is over a certain threshold. The default is 3 hours, but it can be changed on request.

Several improvements were made on alert notifications:

1. You may now not only group Alerts into different emails, but also group and sort them within the same email, using the following alert attributes: For instance, the first Notification grouping line will result in separate emails sent per each Custom intervals name: Grouping attributes are now added to the email subject (only for you own alerts, but not for tickets to external partners).

The second config line will send all alerts in the same email, sorting them ascending by the tag, interval, and then your comment. Names of grouping attributes are added to combination names: Notification grouping is set in Contacts or Config-Tickets per each external partner:

2. Various errors and warnings are written to the Alert log. For instance:

• Email / Push / SMS could not be sent due to server issues (server down, etc.).
• Email / Push / SMS limits per hour, day, month are reached per a contact or contact group.
• Sending Email / Push / SMS is disabled by contact group Schedules.
• Ticket emails are suppressed for this alert for a configured period.

3. Emails to which alerts and tickets were sent, as well as notification templates used for the emails are now written to the Alert log as well.

4. Your NOC may now add status and comments to every alert in the log, as well as send follow-up emails to the same contacts that received this alert initially.

1. Table filtering now allows to send regular expressions to a DB via prefixing your filters with ~ or !~ (not matching). For instance, you may choose certain number ranges by filtering number fields in CDRs like this: ~^1416[0-5][7-9]

2. If you prefix your column filter with PERM:, the filter will still be active even if you remove this column. For instance, you may filter out only Customers/Vendors with the c filter: And then hide the ID column and still see only Customer/Vendor objects in the table. Permanent filters are not cleared with the Remove all filters button, however, a Ctrl-click will clear them as well.

A new concept of parameter targets was introduced. You may now set performance targets or benchmarks for the following parameters: ACD, ASR, ABR, NER, Codes 487 %, PDD.

You may do this right in the Table or Report modules by adding the target columns and double-clicking their cells to edit: Targets are individual per each object combination and will show you if each parameter is performing well by coloring its cell.

Targets change color of both EMA (per-window of calls) and per-hour parameters.

You can also edit targets and their colors in Config: System -> Param. targets table: Target colors are made different from the default red-yellow-green highlight colors that are global for the whole system (and can be edited in Config: System -> Color levels). If a target is set, but the color is not, the corresponding parameter cell will remain white, and not colored by the default highlight.

If you add a target cell to a chart, you will see a thick flat line. You may adjust line thickness via right- or shift-clicking a target cell. Param. targets table is linked to Table and Report modules via cross-links in the right-click menu. You may, for instance, add a target right in the Table cell, and then edit its color by opening a floating Param. targets table:

Several major improvements were made to working with media in a Call flow.

1. With the full media collection enabled, some media is very long and takes a lot of time to extract. In most cases, people dont need to listen to full 2 hours of a call, but just for the first 1-2 minutes. For this reason, a concept of Media ranges was introduced. You may select the exact time range you want to listen to in a browser, download as a file, get media statistics for, or export to .pcap. 2. A new button to refresh the Call flow was added. If may be useful when you see incomplete packets or need to check if media for this call exists. See the above picture.

3. If you work with a long call and need to listen to different ranges, you may easily get back to previously rendered files: 4. Ranges also work for media statistics. Calculating it for 1-2 hours may take a couple of minutes. Instead, you may choose to only calculate it for a shorter range, like 10 minutes, to get a quick feeling if anything is wrong, and then recalculate for a longer range, or for a specific part of a call, for instance, from 50th to 70th minute.

The range for which stats were calculated is shown in the stats table head. The range is green if it covers full media duration, and red otherwise. Depending on your traffic, stats may not be calculated by default to speed up media processing by the logger, in this case you will see "no stats" in this cell, and will need to manually calculate the stats for the range you need. 5. In Media calls table, and when you export .pcap, you will get a window to select the range for any call with duration over 5 minutes:

It is possible to determine which tables are accessible to non-Admin users starting from this version. A new config table Role rules was added. After you are done editing this table, please press the Force all non-Admin users to refresh their web pages button if your changes are critical and you want to update access rights of all logged-in users with non-Admin roles.

You may now Double-click any IP address in the signaling log table, or click it in the Call flow and get a chart of Invites/Setups from/to this IP.

The last 10 custom intervals chosen in the Calendar for each table are now saved and are available after you reload the page.

User password management was improved:

1. A new global parameter Password pattern was added to "Config: System -> System config". All new passwords will be checked against this pattern.

For instance, 6/1/2/3/0 will mean:

• 6 - minimum password length,
• 1 - number of lowercase letters in a password,
• 2 - number of uppercase letters in a password,
• 3 - number of digits in a password,
• 0 - number of special characters ( ! @ # $ % ^, etc.) in a password.

2. When adding new users or changing passwords for existing users, you may now generate passwords automatically according to the above pattern. 3. You may force a user to change his/her password at the first login: or at any next login: A user will have the following login window in this case: You may also make a password visible with the "eye" icon.

An extensive memory optimization was performed to allow 5gVision to work on certain iPhone and iPad devices that impose very strict memory limits to web sites (as low as 25 Mbytes).

One of the outcomes of this is that all object names from statistics are not loaded any more to mobile devices, rather, only names of the objects that had any stats in the last 2 hours are loaded. This allows to cut memory usage 2-3 times in most cases, but may result in some of the names not shown in Reports if they are done over a long period of time.

It became possible to view Vendor->Customer statistics in Charts and Tables in the recent versions, so there are 3 modes we may suggest to our customers now:

1. Show Vendor->Customer stats. We believe this is the best option giving you the most flexibility, so this will be the default behavior, unless you request to switch to 2 other modes below.

Imagine that you have a Customer and a Vendor sending the same area to each other, for simplicity. Then this mode will show you full set of stats: The partner on the 3rd level shows both IN and OUT stats. The arrows demonstrate that once we get to the 3rd level, stats criss-cross, for instance, out of 150 attempts Carrier 1 got as a Vendor (stats are in the OUT column, so it is a Vendor), 50 were sent by Carrier 2 as a Customer (in the IN column).

2. Clone OUT stats into IN columns. Traditionally, a lot of our customers got used to a different way to view stats: the OUT stats on the 3rd level were cloned to the IN columns. This way, only Vendor stats could exist on the 3rd level, and if a partner on the 3rd level had any IN stats - they would be overwritten: This mode is easier to work with, and shows all stats in combinations like Customer->Area->Vendor in just one column (the IN column). You may also hide the OUT columns altogether, and still be able to view Vendor stats on the 3rd level.

3. Hide IN stats. To make it even less confusing, the IN stats may be simply hidden on the 3rd level, thus, you can see only Vendor stats there, and only in the OUT columns: Please let us know if you want to change to the modes 2 or 3.

An object type letter p used for "Poller internal statistics" (p001 - Server CPU load) was changed to i (for Internal), the new objects will look like i001. Letter p will be used in currently developed statistics per Products / Rate plans / Partitions. For instance: Premium, Standard, CLI, etc.

This change may only affect you if you are watching Internal statistical parameters, or have alerts configured on them. Most of the web configs should be updated accordingly, however, we would kindly ask you to double check them.

A Task scheduler is introduced with this version to allow users to run various tasks automatically. The first task added is a request to test routes via a Dialer. The Scheduler table is in the Config: System screen. You may specify the options each task will run with. For the Dialer, the options are quite the same as with the manual request, except that there is no need to manually generate the numbers from CDRs, it will be done with each task run, so different numbers will be tested each time. Any numbers left if the "Numbers:" textbox will be tested over and over (not recommended).

Each scheduled run of a Dialer will create a record in the Dialer "Request" table, and a record in a "Scheduler log" table on the Config: System logs screen. Please check this log for any errors.

When sharing CDRs with your partners over public links, you may now automatically include only Customer- or Vendor-related columns out of all the columns visible in the table you share. Generic columns like Duration, Disconnect code, etc. are included in any case.

1. Each media waveform in a table cell or in a Call flow will have a Right-click menu, allowing to open each audio file in a separate player. You may also simply Right-click any cell without a waveform yet loaded, and go to a player right away. 2. Export to .pcap with media is supported now for both (or only one) of the streams of each chosen leg. Shared links will contrain media statistics, if media is shown at the moment of creating a link. You may also choose to upload audio files to a link sharing server to let your partners listen to media streams while working with your links. Media in links will always contain both streams.

1. The Call flow will now let you play media of each leg, as well as view the media stats. Full media collection should be enabled for your switch in this case. Please contact support to investigate if your traffic will allow to support full collection. 2. The Route testing dialer CDRs will now have 2 columns to play media:

• Audio recorded by 5g media logger will play the audio collected by the logger installed at a dialer. This media will always have early media included, regardless of the media settings in the request. You may play or download media in one of the 3 formats - wav, mp3, mp3-mono, regardless of the format chosen in the request. Alt-clicking the waveform will split it into the up and down streams.
• Audio recorded by Freeswitch will play the audio that the Freeswitch, used as a dialer, records itself. This media may have early media missing due to restrictions of the Freeswitch, and will not have up and down streams separated in left and right channels. This column is hidden by default and is left for compatibility and for rare cases when 5g own media is not available.

There is also new media stats added to the Dialer CDRs per each media stream: packets, losses, MOS, R-factor, Jitter.

The Route testing dialer was upgraded with a possibility to initiate route tests right from the Table, Report, or Alert modules. The Area and Vendor will be filled automatically into the test form, as well as the Vendor technical prefix (needs to be configured in the "Config: System -> Carriers" table), and the codes, beloning to the Area. The codes will be used to retrieve test numbers from CDRs.

You may now assign an arbitrary tag to any customer or vendor in your system. This tag will be added to the configured object names via a separator, and will be visible in Tables, Reports, CDRs, etc. One of possible uses might be to associate each customer or vendor with an account manager. This way you will be able to quickly filter out only the objects, belonging to certain managers. We would recommend to use separators ending in @ or # to make sure your filters are more precise. To configure tags for each carrier, please go to "Config: System -> Carriers" table. You, or any other users that need to see your changes in carrier names, will need to refresh the browser page to pick us the new settings.

You may now assign a sound that a browser will play once new alerts of certain types arrive. Sounds may have priorities, if several sounds correspond to arrived alerts, only one sound with the highest priority will play. It is also possible to:

• force the browser title to blink, this will be visible in the browser tab and in the operating system taskbar (if the 5gVision tab is active and app icons have text names),
• force the newly arrived rows in the alert log to blink.

Sounds and other notifications will trigger only when the Alerts table is auto-refreshed, manual refreshes result in no notifications. The alert table should be on screen for auto-refresh, and, thus, notifications to work. Sounds are assigned to alerts in the Alerts ABS and Alerts DIFF config tables.

It became possible to get a diff of two signaling packets, comparing them side by side. Please press the Diff button in a Call flow or choose this option from a right-click menu in a log table.

When adding a new user, you would now be able to choose which screens to show to this user after you press the Save button. You may add, for example, only the very basic monitoring screens and no configs, or all screens for all products.

Parameters like height, width, column layout can now be saved for Floating blocks. Once you change any of these settings, all further floating blocks/tables in all screens will have them by default. You may now configure floating blocks to be as big or small as you like, and contain your set of columns.

An Auto-refresh strip was added to the Table and Alerts modules. You may now decide how often these tables will auto-refresh. By default, Alerts refresh every 5 minutes, and Tables dont auto-refresh.

Charts auto-refresh as before: every minute if this results in at least a two-pixel move of a chart. Otherwise, an auto-refresh period is adjusted so that a chart moves by 2+ pixels after a refresh.

A Highlight of table rows is now saved to a DB for all tables (previously it was saved for only small config tables, excluding large tables like CDR, Alerts, Rates, etc.). Thus, your highlight will survive a page refresh.

It is possible now to add a Total / aggregates row to any table, allowing you to conveniently analyze data that is loaded to the web interface (but not all the data in the DB for this table). Apart from common aggregates like Total, Count, or Average, you may see, for instance, All unique values in a table with counts, Date ranges for date columns in CDRs or Rate management, Minimum-maximum value ranges, etc.

Settings for a loop detection mechanism were updated with an option of duration tolerance.

If duration of a connected call suspected to be in a loop differ more than plus or minus the tolerance from other calls in a loop - this call is not counted as part of this loop.

The new cross links are added to the CDR and Signaling logs tables: View in Media by SRC IP and View in Media by DST IP. If you have the Media collector installed and your media is written randomly, you will be able to open all recorded calls for the same interval as you have in the CDRs or Signaling logs, filtered by the SRC or DST signaling IP. This way you may quickly check the quality by listening to suggested calls in any codec right in the web interface. Please note that by default the media is recorded randomly (about 1-5% of all media), so you may not listen to the very same call you viewed in CDRs or Signaling logs, but you may easily find similar calls to the same destination by filtering by the DST number.

Full media can be recorded on request provided the proper hardware is used.

You can now export any web table into an Excel file, preserving most of the formatting (or without formatting if you wish). The Export option is present for every table in the drop-down menu. There is a new button in the export dialog: Download Excel file. This is how a Report would look like after the export:

A possibility to send alert notification emails in HTML format was added. You may now create various email templates using an HTML editor. Here is one of the default templates: And this is how your notifications may look like with another default template: The easiest way to create a new tempate would be to clone an existing one, change the colors and layout of the new one, and assign it to chosen emails in the Contacts tab.

Ctrl-dragging the block resize handle will now resize the height of all blocks in a given row and the width of all blocks on screen for screens with multiple blocks.

The Alerting module (see Alerts) was enhanced with the following functionality:

• Accumulative alerts were added for the VoIP switch objects and SCR/DST numbers. Only the per-hour parameters can be accumulated. You may choose to start accumulating data from any day of week or day of month. For instance, you may set an alert if the minutes to a certain Vendor for a certain destination reach 300k from the beginning of the month or from Monday of each week. You may also set more granular accumulation periods like one day or 3 hours.
  
  Accumulative alerts are part of the Custom intervals module.

• You may now set the change direction in the Differential alerts as both (a parameter goes either UP or DOWN over the threshold percentage).
• The Alert log table was added right to the alert configuration table to make it easier to configure and check alerts in one place.
• The Object groups, Alerts ABS, and Alerts DIFF tables now have the Status column to enable/disabled the records in a more convenient way (rather than doing it by setting the Schedule=DISABLED).

1. The screen add/edit window was changed to make it easier to find and add various screens. Screens are now arranged by the products, and you may also add all screens of a particular product at once (for instance, if you choose the Rate management folder - the very folder and all the Rate management screens will be added. Please see more in Add/edit menu.

2. The column selection window was redesigned to make it easier to find and then add/remove/re-arrange table columns. This is especially convenient for tables with a lot of columns, like Chart, Report, or CDR.

Admin users may now create Global presets to share their column layout with other users. Please see more in Column selection.

1. The manual was significantly revised and split by products:

• Monitoring and Alerting.
• Traffic collector.
• Route testing dialer.
• CDR comparison.
• Rate management.

The Rate management manual is not fully complete, though.

You will now see separate screens for each manual in the menu tree on the left. The former User manual screen was changed into a folder.

2. The messaging system was added, allowing us to share company and product news with you.

Please have a look at the new messages once they arrive by clicking the Messages link on top of your web page (if the block on this screen is maximized, please return to normal mode to see the links on top).

3. You can now share screens in addition to cloning them. If the screen is shared as view-only, only the owner of the screen (the one who shared it) will be able to save changes. All other users will be looking at a copy of the owner's screen.

If the screen is shared as editable, all users will be able to modify it. However, changes by other users are not synchronized with your shared screen automatically, you need to refresh the screen to upload them.

1. The comparison tool in charts (the = button) can now be set to any number of days.

2. New parameters for number and % of calls using LRN were added (in case there is LRN info in the switch CDRs).

For MVTS II switches DST areas are now determined in 5gVision in case an area is empty in CDRs (a call got rejected before the area was matched in a switch, for instance, for disconnect codes like DB-201 Full authentication failed).

Areas matched by 5gVision will be seen in stats, but will only be seen in CDRs if CDR replication is active.

A dot symbol in filters was revised. Since dot is often used in object IDs (set 2 areas are a2., etc.) and names (IP addresses, etc.), it seems more logical to treat the dot as is, not as a regular expression symbol for "any character". Previously, to make a dot a dot it was necessary to escape it: \.

An exception to this are 2 combinations frequently used in regular expressions: .* and .+, here the dot is still treated as "any character".

A new parameter was added Duration Per Attempt, minutes. Names in the columns are DPA and Per-hour DPA.

This parameter is, effectively, ACD * ABR and is showing how many minutes (which is how much money) your network is making from every call attempted by a customer.

If needed, you may now add the 3rd set of DST areas in additing to the 2 set existed before. For instance, the first set will be from your switch, the second will have only full countries, and the third one will consist of several specific destinations where you need extra granularity on the code level.

IDs of areas of the third set will be prefixed with a3..

Report column sorting was enhanced with the mode to get back to the original DB sorting by object groups (with red lines). After you sorted by any column (and ruined the red lines), you may simply click on the initially sorted column (the one with a vague red sort icon) and restore the original sort.

1. It is possible now to define what to show in table cells for null or 0 statistical values and whether to highlight them. This is configured in "Config: System -> Color levels", see Color levels.

2. A Right-click browser menu can be called via pressing Shift + Right-click.

The following new parameters were added: % of attempts and connected calls disconnected by Source, Destination, Switch.

It is possible now to push alert notifications to the 5gVision own Android client (iPhone client will be added later).

Please get the application here

Please contact support to get the PINs needed to register the application at the 5gVision push server.

There is a new column in the Contacts table in alerts: Mobile client PIN. Once the PIN is filled and pushes are enabled at the Global table, you will start getting notifications of configured alerts to your mobile phone.

Push notifications have a lot of advantages over SMS:

• You dont have to pay for each message.
• Messages are not limited to 160 characters and are thus much more detailed.
• It is much easier to manage alerts in the 5gVision application.
• Our own aplication will allow us to add more features in future, like attached charts of alerts, links to stats for the alerted objects, etc.

Generation of Shared links was added for Table, Report and CDR modules.

Please press the Share button in these modules (as well as Chart or Log collector modules) to get an easy-to-open link to the data you see on screen that you may share with your partners. Only the very data you share is uploaded to the Sharing server as a text file, your partners wont be able to see anything else.

1. A Shared links log was added to Config-System->Shared links. It also became possible to remove links that were sent to partners in error.

2. The User Access Rules module was upgraded to support editing restrictions for tables and Options menus. It is possible to block adding, editing or deleting records in certain tables for certain users, as well as block any Action buttons (the buttons in the second row of the menu on top of each table).

Likewise, you may restrict users from editing of any individual options in each Options menu, and even set default values for the options.

These features come handy if you want to limit choices for non-advanced users in order to minimize a possibility of mistakes. For instance, when importing vendor rate sheets, or generating and emailing customer rate amendments.

1. Log of user authentications was added to Config: Users -> Auth log.

2. On the chart canvas, it is possible now to open a "table" menu via right-click. When a blue zoom box is dragged over a chart, and View in CDRs is chosen from the menu, the interval in CDRs will match the zoom box interval.

If the zoom interval exceeds 12 hours, it is limited to 12 hours in CDRs. The end of the time interval in CDRs will match the end of the zoom box interval.

The chart object auto-filtered in CDRs will generally be the last object that was added to the canvas by clicking on a Legend table cell. If you dont get the object you need filtered, please just remove its chart and add it again.

3. Object combinations cav (Customer->Area->Vendor) and cv (Customer->Vendor) will show both IN and OUT stats in Charts, Tables, and Reports. In essence, since both Customer and Vendor are present in these combinations, IN and OUT stats will be absolutely same for all parameters. However, viewing them in both IN and OUT columns is convenient in some cases.

1. It is possible now to set up per-minute intervals in the Custom alert intervals module. Per-hour intervals will be applied to per-hour stats (bars on charts), as before, and per-minute ones will be applied to Active call and EMA stats (lines on charts).

Users of Custom alert intervals module will now be able to set up alerts like these:

• compare this minute active calls with a previous minute, catching very sharp call drops or raises, or
• compare average active calls over the last 7 minutes with average calls over 18 minutes 31 minutes ago.

The data available for such comparisons is limited to the last 50 minutes to avoid excessive load to the system. If you need to compare parameters over longer periods, please use per-hour parameters with per-hour custom intervals of up to 2 weeks.

2. A possibility to set UP/DOWN threshold as an absolute value was added to DIFF alerts. You may set both the % change and the value change, alerts will be raised on either of them, with % change having the priority, i.e. if both conditions are met, the alert will be raised on % change.

Object ID regexp filters are added to an "Object groups" table in alerts. Please add the "ID include mask" and "ID exclude mask" colums as needed.

You may now, for instance, filter out only the main DST areas with a "a2\." exclude regexp, or only the DST set 2 areas with a "a2\." include regexp.

SRC/DST number stats can now be viewed per range of numbers, like 123456XXX, cutting off the last N digits that you may set in the Group strip of the table menu. Alerts by ranges are also possible, please add Group numbers column to the Object groups table.

This major new release introduces Custom styles - an existing new way to change 5gVision interface to whatever pleases your eyes.

You may try changing the style of this page right away:



This is just a quick demo, the new style will be lost after you refresh.

There are several "production" ways to apply, modify, and save the styles:

A. Simple and straightforward ones:

• If you click the Interface link on the very top of your page, next to the screen name, you will see a Style menu. There are several pre-defined Saved styles loaded in the system (and more to come), and you may try them out by simply choosing them in the drop-down box. Styles are not saved until you press the OK button below, if you refresh your browser page - you will get back to the previous style.
• Next, you might want to change the color of some of your block types clicking on color bars in the palette below. Most of the time you see statistics blocks of column 1 in the interface, the first choice. You may always return to default colors of the current style you use by clicking the Revert to default block colors button.
• If you are still not happy with the pre-set colors, you may choose a custom color, or applly additional intensity filters in options like Color intensity, block headers.

B. Advanced. This part is for users understanding basic principles and semantics of CSS (Cascading Style Sheets). 5gVision interface configs mostly consist of plain CSS declarations, except when we need to change a logo, an icon, or color intensity based on another color, in which case we use proprietory attributes that are processed in a special way and not addeded to CSS sheets.

• If you want to change different other elements of the interface, not just the backgrounds, you may click the Change style of interface elements and choose the very element you need with the help of the red outline appearing around elements with custom styles assigned.
• Once you start creating your own style, the system will suggest you to load any of the default Saved styles as a base for your changes. Please do. You may also add a new screen Config: Styles to conveniently get back to style configuration whenever needed.
• You may share any style you create via exporting it as a text file, and sending to other users that may import it via a button in Config: Styles table.
• System admins can also create and save global styles that will be available to all users in the company in addition to the default Saved styles.

A new Media collector module was developed to capture and play back media in any codec. The capturing will work in 2 modes:

A. You may set up IPs and number masks for which the media will be recorded randomly. Small customers/vendors/areas will have the preset minimum number of recorded calls per hour, lets say 10, objects with large traffic might have 100-500 calls recorded, depending on how many objects you are recording for.

B. You may force the system to record the next 5/10/20 calls in a row for specific IPs/numbers, for instance, if you are making a call and want to be sure it will be recorded.

Since media is recorded randomly and only for a short initial interval (we recommend 60-120 seconds) - it wont create too much of an additional load to the system, even if you want to monitor quality for all your customers and vendors.

Usually, 10-20 calls per hour is enough to understand what is going on with a specific vendor->area combination, there is no need to record absolutely every call.

The Media collector module comes at an additional price and requires the Signaling Log collector module installed, see Log collector.

There were 3 new statistical parameters added: DC1, DC2, DC3 for the % of chosen disconnect codes. The codes to include in each parameter are configured in Disconnect codes, you may have several codes included per parameter, if needed.

1. A new cross-link View in CDR, all legs was added to a context menu. The link will open a CDR table with all legs of a call filtered out, including all hunt attempts. This feature only works for the switches that have a field like "Conference ID" to tie different legs of one call together.

2. Likewise, there is a new cross-link View in Call flow, all legs that will open packets flow for all legs in a chosen call. Up to 20 legs can be shown on the same Call flow.

3. A Call flow window in a Log collector module can now be resized. Double click on the resize icon will revert the window to the default height and width.

4. The Packet viewing window was revised to allow seeing only the selected packet(s), the full leg(s) belonging to the selected packet(s), or all legs in a table (up to 1000 packets in total).

5. It is possible now to expand or collapse a packet body in a packet viewer window by clicking on its header (INVITE, etc.).

1. If there are 2 or more charts active in a Legend table, moving a mouse over a cell in the Legend table will highlight a chart on the canvas below.

2. When CDRs are exported to a file, a window with export options will pop up, allowing to choose a separator, whether to preserve dates and long numbers in Excel or not, a file name format, and other options.

3. It is possible now to filter SRC/DST IPs in signaling and media logs using whole networks, like this: =10.20.30.55/24. Network filtering works only with = or != signs.

1. New Report logic.

The old Reports only allowed to see combinations like ca, cac, cc. The new report mechanism allows any combinations existing in the system, adding cr, ar, car (where r is the disc. code or reason), and in case SRC areas are collected, bc, ba, bac (where b is the SRC area).

In addition:

• It is possible to open the 3rd level in Reports now, much like in Tables.
• In the old Reports, it was only possible to filter by ID in the first column, in the new Reports, each Object name column has a corresponding object ID column on top.
• Any object types can now be in any column, and you may also combine object types, for instance, you may set in the 3 top ID columns the values ID1: c, ID2: a, ID3: c||r this way you will get a report on 2 combinations: cac and car at the same time.
• If no IDs are chosen in the top filter rows, the default values of ID1: c, ID2: a, ID3: c will be added automatically.
• You may also add the separate ID columns for Objects 2 and 3 via the Column selection, if needed.
• When requesting the next level in Reports by pressing the plus sign, the objects that will be fetched are determined by the upper ID column. For instance, if you have a report on Customers only, and want to open the next level for Object 2, having its ID filter set to a||r, you will get combinations ca and cr on the 2nd level.

See Reports in the manual for more info.

2. New ways to manage DST and SRC areas.

• For customers with the switches that dont have areas and codes in the CDRs, and areas are to be loaded from files, it is now possible to edit and add the areas manually via a new Config: Objects -> DST 1 codes table.
• Additionally, any customer may load the second independent set of areas to the Config: Objects -> DST 2 codes table. For example, you may wish to collect total stats by whole countries in addition to your standard areas. Or, on the contrary, collect more granular areas for some destinations.
• In the same fashion, one may now edit and add the SRC areas to the SRC 1 codes table to get SRC area stats (requires the Traffic analysis module).

3. Traffic logs: collection of H323 with Call flows was added. Log tables have new columns with SRC and DST numbers extracted from the packets.

4. SRC/DST numbers stats can now be used in alerts, plus additional tables were added to monitor attempts and connects per the length of number in each area.

5. A new parameter % of attempts for disconnect codes was added.

6. Horizontal scroll in tables is now working in case you use the normal mouse scroll wheel (that normally scrolls vertically) in the following cases:

• If a table is short and has no vertical scroll bar at all.
• If your mouse is positioned over the table header or horizontal scroll bar while scrolling by wheel.
• If Shift is pressed while scrolling.

7. CDRs for Route testing dialer have a new column Play file, allowing playing recorded media, viewing the waveform, and jumping directly to any place in the audio file.

8. A loop detection mechanism was added with a parameter "% of loops" and indication in CDRs which calls were part of a loop. This feature is available for an additional fee.

9. An API was developed to get 5gVision charts from any external application by sending a URL with proper parameters to a 5gVision server. Please contact support if you need more info. This feature is available for an additional fee.