Skynet Documentation

From Sky Networks Wiki
Revision as of 17:53, 2 May 2013 by Admin (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search


Table of Contents


Table of Figures4

Table of Tables7

Introduction8

Minimum Requirements9

Get Started10

The Main Menu Bar11

HOME11

TRANSLATIONS11

RESOURCE GROUPS28

GATEWAY LIST31

ROUTES34

SYSTEM38

ADMINISTRATION41Table of Figures


Figure 1. Login Window.10

Figure 2. The Main Menu Bar.11

Figure 3. Routing Process.13

Figure 4. Partition Table.16

Figure 5. Partition Addition.17

Figure 6. Partition Addition –cont.17

Figure 7. Partition Addition Confirmation Window.17

Figure 8. Partition Addition –Existing Partition Alert.17

Figure 9. Partition Deletion Confirmation Window.18

Figure 10. Calling Pre Translation Window.19

Figure 11. Calling Pre Translation - Dialed Number and Translated Number Search Aid.20

Figure 12. Calling Pre Translation Addition Window - 1.20

Figure 13. Calling Pre Translation Addition Window - 2.21

Figure 14. Called Pre Translation Window.22

Figure 15. Called Translation Window.23

Figure 16. Called Translation Edition.24

Figure 17. Routes Edition.25

Figure 18. Called Post Translation Window.25

Figure 19. Called Post Translation Table Addition.26

Figure 20. Called Post Translation Addition.26

Figure 21. Called Post Translation Edition.27

Figure 22. Calling Post Translation Window.27

Figure 23. Resource Groups Window.28

Figure 24. Resource Groups Detailed Window.28

Figure 25. Resource Group Addition Window.30

Figure 26. Gateway List Window.31

Figure 27. Gateway List Addition Window.32

Figure 28. Gateway List Edition Window.33

Figure 29. Routes Window.34

Figure 30. Route Creation Window.35

Figure 31. Route Configuration Window -1.35

Figure 32. Route Configuration Window - 2.36

Figure 33. Route Configuration Window - 3.36

Figure 34. Route Configuration Window - 4.36

Figure 35. Route Edition - 1.37

Figure 36. Route Edition - 2.37

Figure 37. Resource Group Replacement.38

Figure 38. SIP Route Server.38

Figure 39. SIP Route Server Cluster.39

Figure 40. SIP B2BUA.39

Figure 41. SIP Proxy.40

Figure 42. SIP Proxy Edition.40

Figure 43. User Administration Window.41

Figure 44. Group Creation Window.42

Figure 45. Group Edition Example.43

Figure 46. User Creation Window.43

Figure 47. User Edition Window.44Table of Tables


Table 1. Definitions.11

Table 2. Characters * and ? in the Translation Records.15Introduction


Minimum Requirements


ROUTING runs on a customized Linux server. The hardware configuration has been designed to fit your specific needs.


Being a web application, ROUTING runs on all the major browsers:

Firefox

Google Chrome

Internet Explorer

Safari


The communication channel between your switch and the LAN where the web module will be running has to be IP.


Get Started


To begin a session in ROUTING type the URL that is assigned to your network in the address bar of your browser.


Your screen will display the Login page (Figure 1). Type your Username and Password to initiate the Routing module.


[[Image:]]


Figure 1. Login Window.


The login screen is part of a "single sign on" server. With one User ID and password you will be able to access other modules if any. Select the check box if you want to be warned before logging into other sites.


Once your username and password have been authenticated, you will be directed to the Home webpage. You will see the Main Menu Bar and on the top right corner, you will see your username and the current date.


Your administrator will define your profile based on a role and permission security.


The Main Menu Bar


In this bar (Figure 2) you will find the resources you need to understand and manage the traffic routing and retrieve data related to the switch configuration.


[[Image:]]


Figure 2. The Main Menu Bar.


Following is a detailed description of the web module.

HOME


This tab displays an interactive Network Topology Diagram that will show status information of the elements that make part of your routing network. Under Construction.

TRANSLATIONS


Translations perform two important tasks: Adjust the numbering, and perform call routing.


Before explaining in detail the process of routing, table 1 summarizes the most relevant definitions to understand the process.


Table 1. Definitions.


Term Definition
ANI Calling party’s phone number.
Device Driver SIP Signaling IP Addresses defined in the Proxy Servers.
DNI Called party’s phone number.
Fast Busy It is a partition where no provider is assigned and the call is not connected.
Gateway List List of IP addresses associated with the suppliers.
Partition A partition groups the common routing policies for one or more carriers. The purpose of a partition is to deliver the quality service to a group of customers with needs identified with the routing policies defined for that partition.
RG Resource Group. The RG defines the status, direction, translations and other technical parameters needed to identify a carrier in the network. The RG defines routing and numbering processing for a customer.
RG In Client’s RG.
RG Out Provider’s RG.
Route A route is a list of RG Out that defines a path to a destination.

In terms of numbering, the Client’s ANI and DNI are adapted to your technical requirements through the Calling Pre Translation and Called Pre Translation processes. Once they reach your network resources and a provider is selected, the ANI and DNI are adapted to the provider’s technical requirements through the Calling Post Translation and Called Post Translation processes.


In terms of routing, it’s in the translation process where a route is selected so the call reaches its destination.


[[Image:]]
Figure 3. Routing Process.


An explanation of the routing process is explained a follows:


  • Client Validation

Once a call reaches your network, the first step is to verify that the client’s IP address and the originating port match the IP and port configured in the Resource Group for that client – RG In. It is also verified that the client sends the call to the Proxy’s IP address - Device Driver - configured in the RG In.


  • RG In Assignation

Once the client has been validated, a RG In is assigned. In the RG In the Calling Pre Translation (not mandatory), Called Pre Translation (not mandatory) and Called Translation (mandatory) tables that the client associated with this RG In must follow, are defined.


  • Calling Pre translation

In the Calling Pre Translation process the ANI is modified, if needed, to meet your network requirements. It is also here where the call might be forwarded to a specific partition depending on the ANI, if required.


One example of the different operations performed in Calling Pre Translation is when the prefix 011 is deleted from the original ANI.


Another example is when you have extensions in different branches of your company, connected to your network. For routing purposes, such extensions are seen as customers, therefore it is required that the extension number where the call was generated is changed into a specific phone number.


In other cases the ANI is used to prevent fraud. You can block a number or a series of numbers in the partition, by forwarding the call to the Fast Busy partition.


There may be cases where the ANI is analyzed but no change is made in the numbering. Here, depending on the ANI received in the partition, you could forward the call to another partition, for example, to assure premium quality routes.


It may be the case that no ANI format adjustment or partition forwarding is required. Therefore the Calling Pre Translation table query is not necessary; it depends on the client’s configuration in the RG In.


  • Called Pre Translation

In this step the DNI format is adjusted, if needed, to match your internal format. An example is when the prefix 011 or +1 is removed from the dialed number.


You can block calls to a certain number or series of numbers by forwarding the call to a Fast Busy partition. Or you can forward the call to a Fast Busy partition when the call does not include a distinctive prefix agreed with your customer in the DNI.


You also use a Called Pre Translation record to forward the call to a given partition, for example, to assure premium quality routes.


It may be the case that no DNI format adjustment or partition forwarding is required. Therefore the Called Pre Translation table query is not necessary; it depends on the client’s configuration in the RG In.


  • Called Translation

In the Called Translation process a call can pass for various partitions until it reaches its destination, which can be a route with a list of RG Out or a call blocking.


If a route is assigned in the process of Called Translation, the least–cost order, the percentage, or a mix of both is applied, resulting in the selection of a single RG Out for the specific call.


In the RG Out the tables Called Post Translation and "Calling Post Translation" are defined.


  • Calling Post Translation

In Calling Post Translation the ANI is modified to adjust it to the provider’s requirements. An example is when your client does not send the ANI but your provider requires one. In that case the system creates an ANI, according to the configuration in the Calling Post Translation table.


Another example is when your provider requires that you remove or add the + sign to the ANI or change the complete number. Also, when one of the extensions in your network is making a call, the provider might need to receive a phone number, not an extension number.


It may be the case that no ANI format adjustment is required. Therefore the Calling Post Translation table query is not necessary; it depends on the client’s configuration in the RG Out.


  • Called Post translation

In Called Post Translation the DNI is adjusted to fulfill the provider’s requirements. An example is when your provider requires that the DNI is preceded of a certain code for validation purposes.


In the Post Translation process the GW list is assigned to the RG Out and with it, the outgoing IP address and port.


The following table is applicable when creating a record in the translation tables:


Table 2. Characters * and ? in the Translation Records.


Character Action
* The numbers represented by the star character are not altered in the translation. The numbers or symbols (+) preceding the star character are subject to the translation. They can be replaced, complemented or deleted. A single * in this field means that the translation is applied to every ANI in that particular partition. A number followed by an * denotes that the adjustment is performed to the digits before the *.
? The digits of a number that are represented by a question mark represent not only the digits from 0 to 9 but also any character, like the + or #. For example, the number 70?? includes the numbers 7000 through 7099 and the translation is applied to the whole series. It applies also to number that include characters, like 700#.

Partitions

This table refers to the Called Translation partitions. The list of partitions created in the switch is shown in the table of figure 4.


[[Image:]]


Figure 4. Partition Table.


The fields in this table are:


  • Partition

This is the number assigned to the partition.


  • Description

This is a brief description of the partition.


To add a new partition:


  1. Click “Add” to create a new partition. A new row will appear (Figure 5) and the cursor will be located in a new cell under the header “Partition”.

Note: The partition number and dialed number combination is unique, this means that there are no two partitions with the same dialed number.


[[Image:]]


Figure 5. Partition Addition.


  1. Enter the partition number you want to create and click outside the cell to exit. The cell will display a red flag in the upper left corner to denote the addition or change (Figure 6). If you enter a partition that does not exist, the system will display the alert ‘“Partition: x” already exist’.
[[Image:]]


Figure 6. Partition Addition –cont.


  1. Double click on the field under “Description” to activate the cell. Enter a description of the new partition.
  2. Click “Save” to confirm the partition addition or “Cancel” to discard it. The following window will appear:
[[Image:]]


Figure 7. Partition Addition Confirmation Window.


Note: The cell will display a visual alert if the partition number already exists (Figure 8).


[[Image:]]


Figure 8. Partition Addition –Existing Partition Alert.


To delete an existing partition:


  1. Select the check box or check boxes next to the partition you want to delete.
  2. Click “Delete”. The following window will appear:
[[Image:]]


Figure 9. Partition Deletion Confirmation Window.


  1. Click “Yes” to confirm the deletion or “No” to discard it.

Note: You can select all the partitions by clicking “Select all” and then delete the whole group.


To edit an existing partition:


  1. Double click on the description and edit the field. Click outside the cell. The cell will display a red flag in the upper left corner to denote the change.
  2. Click “Save” to confirm the partition edition or “Cancel” to discard it. The window of figure 9 will appear.
  3. Click “Yes” to confirm the edition or “No” to discard it.

If you have a large amount of partitions, you can make use of the buttons [[Image:]] to move across the partition list.


Use the button [[Image:]] to refresh the web page. You can decide to display 50, 100, 500, or all the partitions using the drop-down list next to “Rows”.


Calling Pre Translation

Calling Pre Translation refers to the ANI formatting process to adjust the numbering to your network requirements.


Figure 10 shows the table that comprises the Calling Pre Translation records that run in your switch.



Figure 10. Calling Pre Translation Window.


The fields in the table are:


  • Dialed Number

This field refers to the ANI from where the call is being generated.


  • Translated Number

There are two possible values here: the formatted ANI, which fulfills the numbering requirements of your network or a blank cell that denotes no change in the ANI.


  • Description

Type here a brief explanation of the record or specific annotation about it.


  • Fw. Partition

There are two possible cases here: the number of a partition in the Called Translation table where the call is forwarded, or a blank cell that denotes no change in the partition.


  • Modified by

The system automatically fills this field with the user’s login name who performed the addition (or modification).


  • Modified

The system automatically fills this field with the date of the change.


To perform a custom search, use any combination of the search fields. The fields Dialed Number and Translated Number are supplemented by a window that helps refine the search. Make use of the options <, >, =, <=, > =, Begins with, and Containing, to perform a search of a specific number or a range of numbers.


[[Image:]]


Figure 11. Calling Pre Translation - Dialed Number and Translated Number Search Aid.


To create a Calling Pre Translation record:


  1. Click “Add” to create a new Calling Pre Translation. The following window will appear:
[[Image:]]


Figure 12. Calling Pre Translation Addition Window - 1.


  1. Enter the partition number. If the partition you entered is not created in the switch, you will see a text box saying “ANI Pre Translation ‘x’ already exist”.
  1. Enter a description of the record if required.
  1. Click “Add” to create a new record in the translation.
  1. Enter the Dialed Number subject to translation. The cell will display a red flag in the upper left corner to denote the addition or change (Figure 13).
[[Image:]]


Figure 13. Calling Pre Translation Addition Window - 2.


  1. Enter the ANI new format under Translated Number (if required).
  1. Double click on the field under Description and enter a brief explanation of the translation if required.
  1. Double click on Fw. Partition and enter the partition in the Called Translation if you are going to redirect the translated number to another partition.
  1. The system will fill the fields Modified by and Modified with the user login name and date of the addition.
  1. Add more registers to the Calling Pre Translation if needed and repeat the actions.
  1. Click “Save” to confirm the new Calling Pre Translation record or “Cancel” to discard it. In both cases a confirmation window will appear.

Note: If you do not enter data on a cell that should be filled, the system will display a visual alert on the cell and a text box saying, “This field is required”.


To delete registers in a Calling Pre Translation record:


  1. If you want to delete a line in the Calling Pre Translation record, select the check box of the Translation you want to edit.
  1. Click on x to delete specific registers of the Calling Pre Translation record.
  1. Click “Save” to confirm the changes or “Cancel” to discard them.

To edit an existing translation:


  1. Select the check box of the Translation you want to edit.
  2. Double click on the fields you want to edit. The fields that can be edited are: Translated Number, Description, and Fw. Partition.

Called Pre Translation

Called Pre Translation refers to the DNI handling process to adjust the numbering format to your network requirements.


Figure 14 shows the table that comprises the Called Pre Translation records that run in your switch.


[[Image:]]


Figure 14. Called Pre Translation Window.


This table has the same structure as the Calling Pre Translation table and the same definitions apply here except for “Dialed Number” that refers here to the DNI that is going to be formatted.


The creation, deletion and edition of Called Pre Translation records follow the same steps explained in Calling Pre Translation.


Called Translation

In the Called Translation process the call’s ANI and DNI are already formatted and a route is associated depending on the destination.


[[Image:]]


Figure 15. Called Translation Window.


Figure 15 shows an example of the Called Translation table. What follows is a description of this table.


  • Partition

This is the partition where the RG is appointed if it has not been modified in Called Pre Translation and Calling Pre Translations.


  • Dialed Number

This is the called party or range of dialed numbers.


  • Translated Number

Although the DNI is formatted in Called Pre Translation, it is also possible to do it in Called Translation. In that case this field is used to specify the adjustment in the DNI.


  • Description

This field tells you the purpose of the Called Translation. For example, blocking of fraudulent calls, translation for testing purposes, or routing of specific numbering range.


  • Route or Fw. Partition

The Route or Forward Partition fields contain the route of the call or numbering range. The Fw. Partition is part of the Called Translation Table.


  • Max. Duration

This parameter is used to control the length (in seconds) of calls. In this field you can program the disconnection of calls suspiciously long.


  • Modified

The system automatically fills this field with the current date of creation or modification of the translation.


The addition and deletion of Called Translation records follow the same steps explained in Calling Pre Translation.


Make use of the “Multiple Edition” functionality to edit Called Translation records. Figure 16 shows an example of multiple edition where the series of numbers that begin with 5025311 will have a new route assigned to them, in this example route 99.


[[Image:]]


Figure 16. Called Translation Edition.


To edit the routes assigned to an existing Called Translation:


  1. Select the check box next to the translation(s) you want to edit the route.
  1. Click on “Edit Routes”. The system will display the window for route edition (Figure 17). This window is explained in detail in the menu option for “Routes”.


Figure 17. Routes Edition.


  1. Make the changes in the routes and click on “Save” to confirm them or “Cancel” to discard them. In both cases a confirmation window will appear.

Called Post Translation

Called Post Translation refers to the DNI handling process to adjust the numbering format to your provider’s requirements. It is here where the RG is linked to a group of outgoing IP.


Figure 18 shows the table that comprises the Called Post Translation records that run in your switch.


[[Image:]]


Figure 18. Called Post Translation Window.


The field “Gateway” refers to the list of IP addresses defined in the menu option “Gateway List”. These are the provider’s IP addresses.


To create a Called Post Translation table:


  1. Click “Add” to create a new Translation table. The following window will appear:
[[Image:]]


Figure 19. Called Post Translation Table Addition.


  1. Type the Post Translation Partition or use the arrows to scroll up and down. If the partition already exists you will see a text box saying, “Post Translation ‘xxxx’ already exist”.
  1. Type a brief description of the post translation table if required.
  1. Click “Add” to create a translation record in the table (Figure 20) and fill in the fields Dialed Number (DNI) and Gateway. Fill in the fields Translated Number, Translated NOA, and Description if required. The field Gateway Description is filled automatically by the system.
  1. Click “Add” again to create more translation records.
  1. Click “Save” to confirm the addition or “Cancel” to discard them.
[[Image:]]


Figure 20. Called Post Translation Addition.


To edit an existing Post Translation Table:


  1. Select the check box next to the translation and click on “Edit”. The following window with editable fields will open:
[[Image:]]


Figure 21. Called Post Translation Edition.


  1. Edit data and/or add/delete translation records to the table.
  1. Click “Save” to confirm the changes or “Cancel” to discard them.

Calling Post Translation

Calling Post Translation refers to the ANI handling process to adjust the numbering format to the provider’s requirements


Figure 22 shows the table that comprises the Calling Post Translation records that run in your switch.



Figure 22. Calling Post Translation Window.


In some cases your provider may request that the field NOA (Nature of Address) is adjusted reflecting the nature of the ANI. The field “Translated NOA” refers to the adjustment required by your provider to clarify whether it is an international, or national number.


The creation, deletion and edition of Calling Post Translation records follow the same steps previously explained.

RESOURCE GROUPS


The Resource Group defines the status, direction, translations and other technical parameters needed to identify a carrier in the network. A carrier can have one or more incoming, outgoing, or in/out RGs.



Figure 23. Resource Groups Window.


Figure 24 displays the details of a specific RG.



Figure 24. Resource Groups Detailed Window.


Following is a description of this window:


  • General
    • Id: This is the number that identifies the carrier’s RG.
    • Description: This field describes the Resource Group. It can tell, for example, the carrier that is associated with the RG, the purpose of the RG and the circuit direction.
    • Admin Status: This field tells if the RG is active or not.
    • CIR Direction: This field tells the circuit direction, IN, OUT, IN + OUT.
    • Device Driver: This is your SIP Signaling IP Address. The field has a drop - down list with all the interfaces that you could use to pass SIP Signaling.
  • IP
    • IP Address, Netmask, Port. In a RG In this is the client’s IP address, netmask, and port. A “0” in the Port means that you process calls from any port. In a RG Out this is the Proxy’s IP address.
  • Partitions
    • Partition: This field defines the Called Translation partition.
    • Pre Translation: This field defines the Called Pre Translation table if required.
    • ANI Pre Translation: This field defines the Calling Pre Translation table if required.
    • Post Translation: This field defines the Called Post Translation table if required.
    • ANI Post Translation: This field defines the Calling Post Translation table if required.

The fields Pre Translation and ANI Pre Translation are used when the RG is used as RG In (client). The fields Post Translation and ANI Post Translation are used when the RG is used as RG Out (provider).


  • Calls
    • Call Count: Number of simultaneous calls allowed for this RG. A “0” call count means unlimited amount of simultaneous calls.
    • Flag Pound: Select one of three options, LEAVE_POUND (the DNI is not modified), ADD_POUND and REM_POUND (remove pound).
    • Other modifiers.

To add a new Resource Group:


  1. Click “Add” to create a new Resource Group. The following window will appear:
[[Image:]]


Figure 25. Resource Group Addition Window.


  1. Select an available ID. The available IDs will appear as you type one.
  1. Type the description of the Resource Group if required.
  1. Select the Administration Status, Circuit Direction and Device Driver.
  1. Depending on the RG type (client or provider), enter the Calling Pre Translation and Called Pre Translation, Calling Post Translation table numbers if required.
  1. Enter the Called Translation table number.
  1. Enter the Called Post Translation number for RG Out.
  1. Configure the IP address depending on the type of RG.
  1. Define the Call Count, the Flag Pound, and the other modifiers.
  1. Click “Save” to confirm the addition or “Cancel” to discard them.

To delete an existing Resource Group select the check box and click “Delete”. A confirmation window will appear. Click “Yes” to confirm the deletion or “No” to cancel it.


To edit an existing Resource Group select the check box next to the Resource Group you want to edit. The Resource Group window will open for that carrier. Edit and save the changes.

GATEWAY LIST


This is the list of IP addresses associated with the suppliers. The Gateway List is assigned in the Called Post Translation process.



Figure 26. Gateway List Window.


Figure 26 shows the Gateway List window. Following is an explanation of each field in the table:


  • Position

This is the position of the IP address in the Gateway List.


  • IP Address and Port

This is the carrier’s IP address and Port


  • Percentage

If the Percentage scheme is used this field represents the percentage of calls each IP address handle in the Gateway List. Least Cost means that the first option will be the IP Address in position 1. If for any reason it does not connect, the system will try the IP Address in position 2 and so forth


  • Prefix

This field defines the prefix to be included for all the DNIs for that specific IP address.


  • Modified By

The system fills this field with the username of the person who performed the modification.


  • Modified

The system fills this field automatically with the date of the last modification of the Gateway List.


To create a Gateway List:


  1. Click “Add” to create a new Gateway List. The following window will appear:
[[Image:]]


Figure 27. Gateway List Addition Window.


  1. Enter the Gateway List Id. If you enter an existing Id, the system will display a visual alert and a text box saying “Gateway List ‘x’ already exist”.
  1. Type a brief description of the Gateway List if needed.
  1. Select the Search Type. You can chose here between Least Cost or Percentage schemes.
  1. Click “Add” to create a new row in the Gateway List and fill in the technical parameters: Position, IP Address, Port, Prefix, and Percentage. As you fill the fields, a red flag in the upper right corner will appear to denote an addition pending for recording.
  1. Add more lines if needed or click “Save” to confirm the addition of the new Gateway List, or “Cancel” to discard it. Use the x to delete lines in the Gateway List if needed.

To delete an existing Gateway List select the check box next to the list and click “Delete”.


To edit an existing Gateway List select the check box next to the list and click “Edit”. The system will display the Gateway List window with editable fields as shown in the following figure:



Figure 28. Gateway List Edition Window.

ROUTES


In this tab you can configure and manage the routes to all the destinations you offer.



Figure 29. Routes Window.


Figure 29 shows the Routes Window. Following is an explanation of each field of the table:


  • Position

This field denotes the order in the RG Out to be followed when a provider does not connect a call. The call is re-routed to the next RG Out of the list. This field applies when the Least Cost Routing scheme is used.


  • Resource Group

These are the Resource Group IDs that compose the route.


  • Resource Group Description

This field contains the name of the carrier and other details of the Resource Group.


  • Percentage

If the route works under the percentage scheme, this field denotes the percentage of traffic managed per Resource Group.


  • Modified

The system fills this field automatically with the date of the last modification of the route.


To create a route:


  1. Click “Add”. The following window will appear:
[[Image:]]


Figure 30. Route Creation Window.


  1. Enter the Route ID or select it from a drop - down list, and enter the Route Description.
  1. Select the Search Type and the Reroute value from a drop –down list. Reroute means the disconnection cause code to be used to reroute within the same route.
  1. Click “Save” to confirm the changes or close the window to discard them.
  1. When you click “Save”, you will be redirected to the following window:


Figure 31. Route Configuration Window -1.


  1. Drag the Resource Groups that will compose your route from the list on the left and drop them under the route you are configuring. Figure 32 shows an example where the automatic routing module is routing part of the traffic, according to the percentage it is given.


Figure 32. Route Configuration Window - 2.


  1. You can re-order the Resource Groups by dragging them and dropping them in another position. This is useful to determine the position of the RG Out when working under Least Cost Route scheme.
  1. If working under the percentage scheme, you can edit the percentage of calls the Resource Groups are going to manage (see Figure 33).


Figure 33. Route Configuration Window - 3.


You can track the percentage distribution in the cell under Percentage (Figure 34).



Figure 34. Route Configuration Window - 4.


  1. Click “Save” to confirm the changes.
  1. To go back to the Routes list, click on Route in the Main Menu bar.

To delete an existing route select the check box next to the route and click “Delete”. A confirmation window will appear.


To edit an existing route:


  1. Click “Edit”. The following window will appear:


Figure 35. Route Edition - 1.


  1. You can add new Resource Groups or remove the existing ones by dragging them and dropping them back on the list to the left.
  1. You can edit the Search Type and percentage of each Resource Group. You can also change the order of the Resource Groups.
  1. Click on [[Image:]] to display the list of Partitions, RG and clients affected by the edition (Figure 36).
[[Image:]]


Figure 36. Route Edition - 2.


  1. Click “Save” to confirm the changes.
  1. Go back to the Routes List.

To replace a Resource Group in the routes it takes part:


  1. Click on “Replace RG”. The following window will appear:
[[Image:]]


Figure 37. Resource Group Replacement.


  1. Enter the Resource Group Description you want to replace and the new description.
  1. Click “Apply” and confirm the changes by clicking “Save”.

SYSTEM


In this chapter, technical details of the network topology described in chapter 1 are managed.

SIP Route Server

In this option the routing servers – Ariadna, are defined. These servers are responsible for managing the static and automatic routing.



Figure 38. SIP Route Server.


You can add and delete routing servers of the list by using the corresponding buttons.


SIP Route Server Cluster

In the process, the Back to Back User Agent – Minos- queries the routing servers and in return, the routing servers will deliver the list of qualified suppliers to terminate the call. In this table the pair of routing servers that the B2BUA query, are defined.



Figure 39. SIP Route Server Cluster.


The percentage of calls a B2BUA will consult to a routing server or the other is defined in the SIP Route Server Cluster. For example, in row 1 of figure 39 the User Agent queries the routing server Madrid and Miami in the same percentage of calls.


You can add and delete SIP Routing Server Clusters of the list by using the corresponding buttons.


SIP B2BUA

This table defines the list of B2BUA associated with the SIP Route Server Clusters.



Figure 40. SIP B2BUA.

SIP Proxy

This table defines the list of B2BUAs associated with the Proxy –Talos- and the percentage of calls per User Agent.



Figure 41. SIP Proxy.


To edit a Route Server:


  1. Select the check box of the Proxy list you want to edit and click “Edit”. The following window will appear.
[[Image:]]


Figure 42. SIP Proxy Edition.


  1. Drag and drop B2BUA from the list of available UA to the left and configure your list to the right.
  1. Assign the load of each UA.
  1. Click “Save” to confirm the changes or “Cancel” to discard them.

ADMINISTRATION


Users

This tab includes the creation and deletion of users, and the modification of user profiles.


Figure 43 shows an example of the Administration window.


[[Image:]]


Figure 43. User Administration Window.


What follows is a description of the fields of the window:


  • Group

A Group includes a number of roles that define functions and access to certain features of the platform.


  • Users

This part of the table lists the users and usernames currently active in the platform.


To create a new Group:


  1. Click on New Group. The following window will appear.
[[Image:]]


Figure 44. Group Creation Window.


  1. Enter a new Group Name and the Group Description.
  1. Define the functionality of the group by dragging roles from the list to the left and dropping them on the right side.
  1. Click “Save” to confirm the creation or “Cancel” to discard it.

To edit a group:


  1. Click on the button [[Image:]] of the group you want to edit. The following window will appear:
[[Image:]]


Figure 45. Group Edition Example.


  1. Edit the list of roles for that group.
  1. Click “Save” to confirm the edition or “Cancel” to discard it.

To create a new user:


  1. Click on New User. The following window will appear:
[[Image:]]


Figure 46. User Creation Window.


  1. Enter the Username.
  1. Define the roles and restrictions by dragging Groups from the list to the left and dropping them on the right side.
  1. Click “Save” to confirm the edition or “Cancel” to discard it.

To delete a user, click on the x and confirm deletion of the row.


To edit a user:


  1. Click on [[Image:]] to expand the user groups of roles (Figure 47).
[[Image:]]


Figure 47. User Edition Window.


  1. Drag groups from the list of groups and drop them under the user to add functionalities, or drag them from the user’s profile and drop them on the list of groups to disable them.
  1. Click on “Save” to confirm the changes.

Make use of the Search window to locate a user in the list.

Retrieved from "https://sky-networks.com/mediawiki/index.php?title=Skynet_Documentation&oldid=7"