Thanks for your help! I managed to get it working by splitting the dial-peers up... so that the number translation still occurs inbound, but before the call is then sent to the BACD script via another dial-peer. Worked off an example in the following document: http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/bacd/configuration/guide/40bacd.html#wpmkr1066903 The config used seems a little strange for voip dialpeer 100 (as both an outgoing and incoming dialpeer), but it works!! <CME router config> ! dial-peer voice 100 pots description Inbound PSTN to AA-Pilot service aa incoming called-number 85311124000 port 0/3/0:15 ! dial-peer voice 4000 voip description Inbound VoIP from GK translation-profile incoming aa_pilot <translates incoming called number "4000" to the full e164 aa-pilot number> voice-class codec 1 session protocol sipv2 incoming called-number . dtmf-relay rtp-nte digit-drop h245-alphanumeric no vad ! dial-peer voice 100 voip description VoIP Dialpeer to AA-Pilot service aa destination-pattern 85311124000 session target ipv4:142.11.66.254 <loopback interface on CME router> incoming called-number 85311124000 dtmf-relay h245-alphanumeric codec g711ulaw no vad !
cheers Mike ________________________________ From: Vik Malhi [mailto:[EMAIL PROTECTED] Sent: Wed 6/02/2008 4:19 a.m. To: 'ovais Iqbal'; Mike Prestidge Cc: ccie_voice@onlinestudylist.com Subject: RE: [OSL | CCIE_Voice] VoIP call into CME BACD script?? Mike- I think you are almost there except for the digit manipulation. I believe that the your translation is causing you problems since handoff to the TCL script occurs BEFORE the translation on the inbound VOIP dial-peer. Try the translation on the outbound dial-peer and change the "incoming called-number" to the full 10 digits. If you have further problems please post your config. Vik Malhi CCIE Voice Instructor / Developer - IPexpert, Inc. CCIE Voice #13890 CCSI #31584 URL: http://www.IPexpert.com <http://www.ipexpert.com/> Toll Free: +1.866.225.8064 International: +1.810.326.1444 ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ovais Iqbal Sent: Tuesday, February 05, 2008 6:37 AM To: Mike Prestidge Cc: ccie_voice@onlinestudylist.com Subject: Re: [OSL | CCIE_Voice] VoIP call into CME BACD script?? Ok, in your 2nd voip dial-peer do not put the destination-pattern and service aa command both in it, create one dial-peer with destination-pattern command pointing it to your loopback interface and then create an other voip dial-peer with incoming called number xxxxxxxxxxx command and there use the service aa command with no destination-pattern in it. This should work, but also make sure that the codec has to be G711ulaw and DTMF h245-alpha Thanks Ovais. On 2/5/08, Mike Prestidge <[EMAIL PROTECTED]> wrote: I currently have the CME BACD script up and running with the aa-pilot configured using the full e.164 number (85311124000). When placing calls into the script via the PSTN the calls work fine. What I am now trying to do is setup VoIP calls into the BACD script by dialing the on-net extension (4000) and translating it to the full aa_pilot. I have the following setup: - an inbound VoIP dialpeer to match the extension (4000) with a translation profile applied to translate the called number to the full aa-pilot number. - another voip dial-peer to match the aa-pilot number as the destination-pattern. This dial-peer has a session target pointing to a loopback interface on the CME router and has the BACD script ("service aa") also configured. Have tried a number of variations to the dial-peers but still haven't been successful in getting it to work. Is it possible to place VoIP calls into the CME BACD script and if so does anyone have an example configuration? thanks Mike This communication, including any attachments, is confidential. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002. -- Ovais Iqbal 416-294-7869
