Because of the Multiple SIP Addresses feature, a total of 20 IP Address objects can be created. The IP Address object can configure an IP Address to be either a Services IP address or a Media IP address. However, one of the 20 IP addresses must be used during the bootup process and is assigned to the CTRL interface. This IP address must be in a trusted network since OAMP functionality is streamed over this IP. Once this IP address is assigned, that leaves 19 more IP addresses. Also, Up to a maximum of four IP Addresses configured for Media (RTP) can be created. The ratio of IP addresses configured for Media and IP addresses configured for Services is determined by the number of IP addresses configured as a Media IP address. Once the Media IP addresses have been created, the remaining IP Addresses can be configured for IP Services. The breakup of IP addresses is a combination of the following:
One Primary bootup IP address. This address is used for OAMP functionality. However, this address can also be used to service the SIP stack if required. This IP address is typically configured on a Private trusted network.* After the bootup IP address is created, there is then a pool of 19 IP addresses that can be allocated as either a Media IP address or a Service IP address. Of the 19 IP addresses left, a maximum of 4 IP addresses can be allocated for Media Services. It is at this point left up to the user to configure the combination of Media/Service IP addresses required. Below are a few examples describing the number of Service/Media IP Address that can be configured.
Example 1
Media IP Addresses configured. | Bootup IP address - can be used for SIP Signaling. | IP address max = 20 (20 - bootup IP address - Media IP addresses configured) |
4 Media IP addresses (2) Media 0's (2) Media 1's | 1 bootup IP address | (20 - 1 - 4 = 15) In this scenario, up to 15 IP addresses can be configured as a Service IP address. |
Example 2
Media IP Addresses created. | Bootup IP address - can be used for SIP Signaling. | IP address max = 20 (20 - bootup IP address - Media IP addresses configured) |
2 Media IP addresses (1) Media 0 (1) Media 1 | 1 bootup IP address | (20 - 1 - 2 = 17) In this scenario, up to 17 IP addresses can be configured as a Service IP address. |
Example 3
Media IP Addresses created. | Bootup IP address - can be used for SIP Signaling. | IP address max = 20 (20 - bootup IP address - Media IP addresses configured) |
3 Media IP addresses (2) Media 0 (1) Media 1 | 1 bootup IP address | (20 - 1 - 3 = 17) In this scenario, up to 16 IP addresses can be configured as a Service IP address. |
Up to four media objects can be created. Each media object configures an IP address for streaming RTP. The media objects are labeled Media 0 and Media 1. When configuring the media objects, up to two Media 0 and two Media 1 objects can be created. Which Logical Interface the Media objects are configured under doesn't matter. A user can configure two Media 0 objects under one the Logical Interface such as the CTRL interface or split the Media 0 objects so they are configured under separate Logical Interface objects (Data A/Data B/CTRL). This is true for Media 1 as well. The media objects are distinguishable through the IP addresses configured.
Network Diagram
The diagram below displays one scenario on how the Multiple SIP Address functionality operates. In the diagram there are two segregated SIP networks.
The first SIP Network scenario displays how SIP Network A is using the Control Port to pass the SIP signaling to the remote gateway. Meanwhile, the RTP data from Packet Facility A is being passed through interface Data A. One note on this scenario is the SIP signaling and RTP data are on different Subnets. Since the SIP Signaling and RTP data are communicating through different interfaces, they cannot be configured on the same subnet. The SIP signaling however, is controlling Packet Facility A even though they are on a separate subnet.
The second SIP Network scenario displays a second SIP Network labeled SIP Network B. In this scenario, the SIP Signaling is being passed through interface Data B and the RTP data on Packet Facility B is being passed through the Data B interface as well. In this scenario, both the SIP signaling and the RTP data are configured on the same subnet. Since they are both using interface Data A, they can both be configured on the same subnet.
The screenshots below display the settings that need to get configured in the various Web GUI objects to obtain the scenarios displayed above.
Scenario 1: SIP Network A
Configure an IP Address and default gateway for the interface Data A. This interface will be configured as a Media 0 interface and will be used for stream RTP data.
Configure an IP Address and default gateway for the interface Control 0. This interface will be configured as a Services interface and will be used for streaming RTP data.
Configure SIP Signaling object and select Multiple IP in the Operations field. Under the SIP Signaling object create the SIP IP Address object. The IP address selected will be used as one of the IP addresses that communicates with the SIP stack.
Configure a Packet Facility object. In the Packet Facility object enter a name to describe the Packet Facility being created. Select Media 0 in the Media Endpoint field since the Packet Facility will communicate through Data A.
Select the Network Address from the drop down menu. This will be the address that was given to the Data A interface since the Packet Facility being created will be passed through interface Data A.
Click in the Number Of Channels field and enter how many IP Channels/Ports will be configured in this Packet Facility (Group of IP Channels/Ports). Channels should be entered in multiples of 32.
Configure the Routing Configuration object the object, the object and then the object. Off the IP Network Element object, the Node Association object can be created. Within the Node Association object, select the node being configured.
Select the Packet Facility from drop down menu.
Select the SIP IP Address which is one of the IP addresses given to the SIP stack. The IP Address selected in the Service IP Address field will control the IP Facility selected in the Media Packet Facility field.
The Multi IP feature is now configured to have SIP Signaling IP Address 10.129.29.101 be communicating through the Control Port. This IP address communicates with the SIP stack and controls the RTP stream which is made up of a group of IP Channels labeled a Packet Facility. This Packet Facility communicates with the remote gateway through the Data A interface using IP address 10.129.39.100. At this point up to 18 more SIP signaling IP addresses can be configured to control the Media Stream. Scenario 2 can now be configured.
Backwards Compatibility
The SIP stack will have the capability of servicing the Primary bootup IPaddress as well any of the IP addresses that are configured as a Service through the IP Address object. For backwards compatibility reasons, the IMG 2020 can also be configured so that a Single IP address services the SIP stack. The Single IP address functionality was kept for the following reasons:
Any older existing configurations can still be utilized.
The SIP Virtual IP Address feature is not supported on a SIP stack that is configured for multiple IP's. If the SIP Virtual IP functionality is being employed, the Single SIP IP functionality must be utilized.
Additional Information
The Primary Interface is first configured during the bootup process and can be selected as a Service IP on the Control interface.
Up to two Media interfaces can be configured under the IP Network object. They are Media 0 and Media 1 and communicate through interfaces Data A and Data B respectively.
SIP Virtual IP addresses cannot be configured when the Multiple IP address functionality is enabled.
The SIP Proxy is also a SIP endpoint. The SIP Proxy needs to be defined as an external gateway.