Topology

Conventional setup

The following is an illustration/approximation of your existing telephony setup. As you can see the ‘phone’ makes a call which is handled by the phone system pushed through a firewall/router and then onto the SIP trunk.






 

Voicesafe installation

The proposed installation requires an additional step to the above. Note the addition of the Voicesafe between the phone system and the firewall/router.



 

Requirements

To achieve a successful Voicesafe installation the following steps have to occur.


  • An additional trunk configured within the  phone connected to the Voicesafe.
  • Existing trunk configured on the Voicesafe to connect to the SIP trunk
  • Firewall/Router configured to forward inbound/outbound SIP traffic to and from the Voicesafe

 

 

Additional Trunk Phone System

Follows is an example of the additional trunk as configured with a FreePBX Phone system. Hosts/usernames/passwords will be provide upon request.


FreePBX Example


Trunk

Note the username and secrets are for illustration purposes a Voicesafe in a live environment would have individual username and secrets again these will be available upon request.



 


 































Outbound routes

Below is the outbound route which utilises the trunk above, note that an ‘Optional Destination on Congestion’ has been stated of ‘SIP Provider’. It is highly recommended that if available this functionality is configured. This will maintain the sites ability to make outbound calls if the Voicesafe fails or is unavailable.



 

 

 

 

Inbound routes

The default inbound routes should remain untouched within the example below all calls are configured with extension number 102 as the destination.



Existing SIP trunk configured on the Voicesafe

The Voicesafe will now need to be configure with the existing SIP trunk settings to allow connection to your current SIP provider, if further assistance is required then the Voicesafe installation team will be in contact. If you have additional documentation that you feel would be of assistance to the team please don’t hesitate to forward this to support@voicesafe.co.uk or give the team a call on 08453730591 to discuss.

 

 

Firewall/Router configured to forward inbound/outbound SIP traffic

Below is an example of the additional inbound and outbound services as configured with a Netgear FVS336GV2. IP address and bandwidth profiles will be individual for each Voicesafe installation and will need to conform to existing network architecture and security policies.


Netgear FVS336GV2

Below is the recommended settings to have in place within your firewall. Note if a failure occurs within the Voicesafe the inbound connections will need to be reconfigured to point directly to the phone system and the Voicesafe support team should be contacted. Please note, these are recommended settings, if they are not in line with security policies please adjust accordingly and inform the Voicesafe installation team of any concerns.

Bandwidth profile

 

 

 

Outbound Service

In the below only LAN users/IPs of 192.168.1.250 and 192.168.1.251 are able to use the outbound SIP:UDP service. In this example the Voicesafe is utilising 192.168.1.250 while the phone system is using 192.168.1.251. In the event of a failure of the Voicesafe this would still allow the phone system to make outbound calls, but prevents other LAN users/IPs from accessing the Service.

 

 

 

Inbound Service

The inbound service is defined as being directed to the Voicesafe 192.168.1.250. In the event of a Voicesafe failure this would need to be changed to the Phone system, in this example that would be 192.168.1.251.

 

 

 

Additional Services

In addition to the SIP services the Voicesafe also requires full outbound access to allow for updating and patching.



 

 

Note


Supported codecs

The following codecs are supported

· G729 (please state)

· G726

· G723

· G722

· Alaw

· Ulaw

· Gsm

· Slin



Failover if unavailable

It is highly recommended to state an option destination of your SIP trunk if the Voicesafe trunk reports congestion. This will maintains the ability to complete outbound calls if the Voicesafe fails or is unavailable.


Extension labelling

To assist in identifying of outbound extension it is recommended that the CallerID of extension is stated.