I`m looking into an issue with AAR with regards to the options when the WAN is down as oppose to it being busy when AAR will kick in
It was along the following lines
Extension 1111, partition "remotesite" is on a remote site SRST site with a full DID 1546785xxxx
is this correct
Create a translation pattern of 1XXX and assign a new partition "TP1XXX" to the TP. You then assign a CSS to extension 1111 which contains both "remoteste" and "TP1XXX" partitions but the "remotesite" is higher order- in the event that the remote extension is not available due to WAN being down , the call to 1111 will choose the TP1XXX partition as the first choice partition , "remotesite" is no longer available. The TP 1xxx will then translate the internal number 1111 to the full DID. Reading another design doc I understand this can work in 3.x but does it not in 4.x - will it work in 5.X bearing in mind the "not registered call forward setting"
many thanks
It was along the following lines
Extension 1111, partition "remotesite" is on a remote site SRST site with a full DID 1546785xxxx
is this correct
Create a translation pattern of 1XXX and assign a new partition "TP1XXX" to the TP. You then assign a CSS to extension 1111 which contains both "remoteste" and "TP1XXX" partitions but the "remotesite" is higher order- in the event that the remote extension is not available due to WAN being down , the call to 1111 will choose the TP1XXX partition as the first choice partition , "remotesite" is no longer available. The TP 1xxx will then translate the internal number 1111 to the full DID. Reading another design doc I understand this can work in 3.x but does it not in 4.x - will it work in 5.X bearing in mind the "not registered call forward setting"
many thanks
