geo-redundancy

  1. Solved Clone DID configuration when using Geo-Redondancy

    The problem is when usign SIP Trunk Register, no matter how the option call source identification is configured, to have Geo-redondancy works, we must configure DIDs on the both SIP Trunks. It is very annoyuing and confusion for clients who have 20+ DIDs to have to deal with configuration of 2...
  2. Need an option to select any SIP Trunk to route inbound call when using Redundancy

    Since the Geo-redundancy requires the following configurations : 1- The addition of DID in each SIP Trunk, which is not convenient when you have many DID because there is no mass DID import/export feature. 2- The configuration of the inbound rules in double for each DID which can cause some...