AFAIK AAR only works between phone endpoints inside the same cluster.<br>CCM needs a complete E.164 number to be able to reroute the call through the PSTN. This fully qualified phone number is built from the external number mask of the destination device and the dialed extension (the PSTN access digit is taken from the AAR Group configuration)
<br>If you want to reroute a call rejected by a GK, a PSTN GW in the same route group as the GK controlled trunk should do the trick, you have to do some digit manipulation on the route group though...<br><br>Patrick<br><br>
<div><span class="gmail_quote">On 11/17/06, <b class="gmail_sendername">Jonathan Charles</b> <<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Found this quote in the SRND for 4.1:<br><br>"<span>
Automated alternate routing (AAR) provides a mechanism to reroute calls
through the PSTN or other network by using an alternate number when
Cisco CallManager blocks a call due to insufficient location bandwidth."<br><br>My question is, what happens if a Gatekeeper rejects the call, does this count as 'insufficient location bandwidth' or does AAR only work if locations-based bandwidth is exceeded?
<br><br><br><br><br>Jonathan<br></span>
<br>_______________________________________________<br>cisco-voip mailing list<br><a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a onclick="return top.js.OpenExtLink(window,event,this)" href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">
https://puck.nether.net/mailman/listinfo/cisco-voip</a><br><br><br></blockquote></div><br>