System

From Sky Networks Wiki
Revision as of 11:22, 7 December 2013 by Admin (talk | contribs) (SIP Proxy)
Jump to navigation Jump to search

SYSTEM


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

SIP Proxy

This table defines the SIP proxies that will handle the calls. The proxies serve as the public face of the SKY DANCE system.


Figure41.png


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.
Figure42.png


Figure 42. SIP Proxy Edition.


Proxy Edit Screen.png


Figure 42a. SIP Proxy Edit Screen.


  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.

SIP Route Server

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


Figure38.png


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 – 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.


Figure39.png


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.


Figure40.png


Figure 40. SIP B2BUA.