Connection/IP based setups would send the IP address that the customer is coming from. Our system allows the connection as long as the customer is coming from the IP that the connection was built for.

Once logged into the Ipitomy, go under Providers > SIP Providers along the left hand menu:

then click on the Add Provider button. That'll bring up the following setup screen:

• Name: enter a name for this connection
• User Type: set to friend.
• DTMF Mode: set to rfc2833.
• RFC2833 Compensate: set to No.
• Host: set to the address of the server that the customer was assigned to. Usually the closest one for the best latency (lasas.vintalk.com or nysas.vintalk.com)

Everything else can be left on default or modified according to customer requirements. The top section alone should be all that's needed to connect to the server.

This would send the calls in the format of [DID]@IP, which is what our connection-based SIP trunks need.

For further reference, the external IP sent is found under PBX Setup > SIP:

Geo-Redundancy

One of the benefits of our new setup is redundancy. You can add the other server address (NY if you were setup in LA, and vice versa) and you'll be able to make calls through that as well, since the connection gets replicated to both servers. You will need to add a new SIP provider with a host of the other server address (LA = lasas.vintalk.com, NY  = nysas.vintalk.com).

Once that's complete, the call routes needed to be modified to accomodate the new SIP trunk.

In order to set this up, go under Call Routing > Outgoing in the left hand menu once logged into the Ipitomy:

Once on the routing page, we would need to update all of the routes to failover to the other server in case the first one is unreachable.

To start, click on the Action button (shown as a pencil):

On the route details, you would need to select the other trunk that was created in the Trunks section and add it to the list of active trunks.

Once both trunks are listed, click Save Changes at the bottom.

NOTE: The order of the trunks is important. The first one listed would be primary, second secondary and so on.

You would need to do this for every single route in order for it to be effective on all calls. Repeat in the same manner.