Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Before reading this article, we recommended reviewing our SIP Signaling IP address page.

Introduction

VoIP Innovations supports the ability to change the IP addresses on which you can send (and receive) traffic. Typically, this feature is used if you need to send from the same source IP address over different VI termination rate decks. For example, you have one IP address and want to send traffic to both our T38 rate deck for faxing, and our Standard/LCR routes from the same IP.

If you have the same IP address in two or more Endpoint Groups, those groups will have a drop down under the 'VI Server' section with corresponding VoIP Innovations' IP addresses giving you a choice on where you send your traffic.
To set up the option to use two different rate decks (and matching outbound routes) from the same IP address, begin by adding the IP address to two different Endpoint Groups. For an example we will use "Test 1" and "Test 2" for the Endpoint Groups and "Standard" and "T38" for the example rate decks.

Next, ensure that "Test 1" is set to use the "LCR" (labeled 'Standard' in the drop down) rate deck and the VI Server drop down is set for Primary.
Similarly, set the "FYI Second" group for the "T38" rate deck and the VI Server drop down as the Secondary option.
Having your endpoint groups configured in this manner, you will want to send fax traffic to 64.136.174.65 or one of the subsequent IPs under the Conversational (Advanced Server) category. Similarly, you will send voice traffic to 64.136.174.30 (or one of the other IPs under Conversational category.

It is important to remember that these changes will also affect inbound calls to DIDs on the respective groups. For example, if you choose Secondary and have any DIDs assigned to that group, inbound calls will primarily originate from 64.136.173.65. You will need to ensure you are configured to allow inbound SIP traffic from that IP address (andothers) in your system.
 
The VI Server Info column on the Endpoint Group Management page will specify the VI server for that endpoint group.

Creating an Advanced Server Configuration

If you do not have the same IP address in multiple Endpoint Groups, the option to choose between Primary and Secondary servers will not exist.
If you have the same IP address in two separate Endpoint Groups…



Open each endpoint group and change rate decks:




Use this drop-down menu to change between VI server IP addresses:




You can hover the information bubble for a summary of IPs based on the category you selected.

It is also important to note how our system views calls from an IP address in multiple groups as it relates to Endpoint Group ID numbers. You need not concern yourself with this information if you only have two groups with the same IP address and each are configured to use different VI Server IPs. However, if you have three or more groups with the same IP address and have one group set for Standard, one set for Custom, and one set for T.38 you need to understand how routing will occur. If you have a scenario such as this, we will route from the lowest number Endpoint Group ID for the groups having matching configurations. The below screenshots give a visual representation to bring clarity to this situation.
In the above screenshot we see three unique Endpoint Group IDs which are 23440, 23441, and 23442. Each group also has a friendly name which is used only for identifying the group by a name. In this example assume that each group contains only one IP
address, is the same for all three groups, and is 173.194.121.38. Notice that both group 23440 and group 23442 have the VI Server configured to use the same IP addresses but are set for different rate decks. Group 23441 is set to use the T.38 rate deck and group 23442 is set to use the Custom rate deck. Since our system looks for the lowest group ID number to route the call and the lowest group number in this scenario is 23440, our server will view any calls sent FROM 173.194.121.38 TO 64.136.174.30
(or any subsequent IPs) as coming from group 23440 and therefore route the call over our Standard rate deck.

  • No labels