Solved Clone DID configuration when using Geo-Redondancy

[Khadija Imad]

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 DIDs for the same route. Even if it is possible to export and import .. this makes too many risks of misconfiguration.

We asked something allow us to clone configuration DID from another one under inbound rules as shown here on my screnshot.

Thanks.

 

[YiannisH_3CX]

Hi @Khadija Imad

Please post this at the Ideas section of the forum so it can be upvoted by other users and evaluated by our management team. Thank you.