Make sure you're not routing the call through the translation rule, which changes the ANI. In such case the expected GW transfrom rule wouldn't match. In my case I had a translation rule, which expanded 3 digit ANI to full E.164 with + for internal calls.
regards On Tue, Jun 22, 2010 at 3:43 AM, Paul Dardinski <pa...@marshallcomm.com>wrote: > I am running into this as well. > > > > I am seeing the 4D going on the egress PSTN call even though I have > explicitly configured cng txform on the gw. I also get the correct ANI on > directly dialed (ie. 91617863XXXX), but on the AAR forced call (XXXX) I end > up with only the 4D in the cng and redir cng. > > > > Does AAR require it to be done on an explicit AAR only RP/RL ? > > > > Also, can someone clarify AAR CSS/group at the device level? Normally it is > required to enable AAR at the Line level for the E164 completion (using the > external phone# mask) , so is the device level AAR configuration for > separate call routing? > > > Thanks in advance, > > Paul (#16842 RS/Sec) > > > > * * > > > > *From:* ccie_voice-boun...@onlinestudylist.com [mailto: > ccie_voice-boun...@onlinestudylist.com] *On Behalf Of *kobel > *Sent:* Sunday, June 20, 2010 11:02 AM > *To:* ccie_voice@onlinestudylist.com > *Subject:* [OSL | CCIE_Voice] AAR and ANI formatting > > > > Hello, > > I'm playing with AAR and VM. When out of bandwidth condition occurs, AAR > correctly kicks in for different types of calls (between HQ and BR1, direct > calls to VM from BR1, for incoming PSTN calls to BR1 forwarded to voicemail > in HQ). It seems that the configuration is ok. > > But I've an issue with ANI format sent to PSTN when AAR is used. All > ANI/DNIS manipulation is done on BR1 gateway via Calling/Called Party > Transformation Rules. When I make a call from BR1 to VM in HQ via PSTN > (explicitly, using 9.12123945600), the ANI is formatted correctly > (6178631xxx/subscriber). But when I press the messages button in BR1, I can > see following output from "debug isdn q931" on BR1 router (outgoing SETUP): > > Calling Party Number i = 0x0081, '1002' > Plan:Unknown, Type:Unknown > Called Party Number i = 0xA0, '12123945600' > Plan:Unknown, Type:National > Redirecting Number i = 0x000081, '5600' > Plan:Unknown, Type:Unknown > > Surprisingly, in the CUC port monitor I can see completely different > information - please compare with attached screenshot. I needed to configure > alternative extension in CUC to correctly recognize the caller as CUC > subscriber. > > It seems that AAR can handle such call correctly, but it doesn't respect > the ANI transformation rules on the GW. Have you also observed this > behaviour? Is there any workaround? > > regards > kobel >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
