Thanks for confirming that!  Presumably your rerouting calling search space
on the RDP uses a route pattern that points to a RL containing the Standard
Local Route Group, which would explain it routing via the local gateway.



On Thu, Apr 12, 2012 at 7:25 PM, Jason Murray <murr...@usa.com> wrote:

>
> Phew at least I'm not the only one :)  I am still working in the lab so I
> tried unchecking the Mobile Phone checkbox and it still forwards out as
> calling the remote destination.  I just find it strange as well on how it
> even knows to send that called number to the HQ gateway.  I can't seem to
> find a route pattern or anything that tells it to do that.
>
>
>
>  ----- Original Message -----
>
> From: Kevin Spicer
>
> Sent: 04/12/12 01:09 PM
>
> To: Jason Murray
>
> Subject: Re: [OSL | CCIE_Voice] AAR and RDP
>
>  Hi Jason,
>
> I've also observed the same behaviour.  The only thing I've found in
> documentation relating to this is the following from the 8.5 features and
> services guide...
> *"Automatic Alternate Routing ** *
>
> *Prior to the implementation of this interaction, if a desk phone was
> configured for Automatic Alternate Routing (AAR) and the desk phone was
> configured with a mobile phone as a remote destination, the AAR feature did
> not get triggered for calls to the remote destination if the
> out-of-bandwidth condition applied. *
> **
>
> *Cisco Unified Mobility now supports Automatic Alternate Routing (AAR) as
> follows: *
> **
>
> *•If a rejection occurs due to lack of bandwidth for the location-based
> service, the rejection triggers AAR for any device that is configured for
> AAR. *
> **
>
> *•If a rejection occurs based on Resource Reservation Protocol (RSVP),
> however, AAR does not get triggered for calls to remote destinations.*"
>
>
>
> This leads me to believe that we cannot expect this to work in 7.0.
> Reading this now I just noticed it says 'with a mobile phone as a remote
> destination'- so I wonder if unchecking the mobile phone checkbox would
> make it work, can anyone confirm?
>
>
>
>  On Thu, Apr 12, 2012 at 5:49 PM, Jason Murray <murr...@usa.com> wrote:
>
>> Ok so I have a weird one for you.  I'm in lab 7 vol 2 testing aar from HQ 
>> phone
>> 2 to BR2 Phone 2.  I bring down the bandwidth to 23.  AAR works great to
>> 3001, and cue 3600.  When I call 3002 it sits there for a moment and then
>> just fails.  I look at the HQ gw and its sending number +447976852817.
>> I finally figure out through playing around with it that its the remote
>> destination number for BR2 Phone 2.  If I change the RD like 2815 or
>> something the HQ gw shows that number.  So I end up disassociating the
>> remote destinations from line 3002 and AAR works great but of course that
>> breaks mobile connect.  So when i put that association back it breaks aar
>> to 3002 again.
>>
>> So has anybody seen something crazy like this.  Not sure where to even
>> start working on this because I though AAR would use the External Number
>> Mask of the phone not send it to a remote destination number.  THoughts?
>>
>>
>> Thanks
>>  Jason
>> _______________________________________________
>> For more information regarding industry leading CCIE Lab training, please
>> visit www.ipexpert.com
>>
>> Are you a CCNP or CCIE and looking for a job? Check out
>> www.PlatinumPlacement.com
>
>
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit 
www.ipexpert.com

Are you a CCNP or CCIE and looking for a job? Check out 
www.PlatinumPlacement.com

Reply via email to