What type of redundancy options do Broadvox SIP Trunks support?
• Two gateways in two separate cities to signal to/receive traffic from • Ability to load balance traffic to multiple IP addresses on customer end • Ability to provide a primary/secondary configuration for the customer end The customer must provide a public, static IP address to signal to. Broadvox Version N SIP Trunks provide: • One virtual IP address that resides on a single cluster in the Dallas location to signal to/receive traffic from • Ability to load balance traffic to multiple IP addresses on customer end Concurrent call sessions (per trunk) must be split between IP addresses • Ability to provide a primary/secondary configuration for the customer end • Ability to perform fallback call forwarding to a PSTN number in the event the customer trunk is not reachable Fallback forwarding can be performed on a per-trunk basis Fallback forwarding can also be performed on a per-DID basis Per-DID forwarding is first precedence Per-trunk forwarding is second precedence Per-DID and per-trun
