I am presuming that 10.10.100.3 is the loopback?
Regardless
Run a debug voice application all and paste the output... let's see if
we ever hit the application...
Also, this is going to sound insane... but if you make any changes to
the application you need to reboot the router.... or restart the
application...
Jonathan
On Tue, Dec 15, 2009 at 11:58 AM, Girard, Jeffrey COL MIL USA
<jeffrey.gir...@us.army.mil> wrote:
> Classification: UNCLASSIFIED
> Caveats: NONE
>
> This is what I sent to the list late last night
>
> DP 222 config
>
> dial-peer voice 222 voip
> service aa
> destination-pattern 3500
> session target ipv4:10.10.100.3
> incoming called-number 3500
> dtmf-relay h245-alphanumeric
> codec g711ulaw
> no vad
> !
>
> Debug voice dialpeer. Call is coming in from PSTN to 3500
>
> Oct 11 13:37:12.837: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
> Calling Number=911, Called Number=3500, Voice-Interface=0x49DCA2B4,
> Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
> Peer Info Type=DIALPEER_INFO_SPEECH
> Oct 11 13:37:12.837: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
> Result=Success(0) after DP_MATCH_INCOMING_DNIS; Incoming Dial-peer=1
> Oct 11 13:37:12.837: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
> Calling Number=911, Called Number=3500, Voice-Interface=0x0,
> Timeout=TRUE, Peer Encap Type=ENCAP_VOICE, Peer Search Type=PEER_TYPE_VOICE,
> Peer Info Type=DIALPEER_INFO_FAX
> Oct 11 13:37:12.837: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
> Result=NO_MATCH(-1) After All Match Rules Attempt
> Oct 11 13:37:12.837: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
> Calling Number=, Called Number=3500, Peer Info Type=DIALPEER_INFO_SPEECH
> Oct 11 13:37:12.837: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
> Match Rule=DP_MATCH_DEST; Called Number=3500
> Oct 11 13:37:12.837: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
> Result=Success(0) after DP_MATCH_DEST
> Oct 11 13:37:12.837: //-1/xxxxxxxxxxxx/DPM/dpMatchPeers:
> Result=SUCCESS(0)
> List of Matched Outgoing Dial-peer(s):
> 1: Dial-peer Tag=222
> Oct 11 13:37:12.857: //-1/0440C96E800C/DPM/dpMatchPeersCore:
> Calling Number=, Called Number=3500, Peer Info Type=DIALPEER_INFO_SPEECH
> Oct 11 13:37:12.857: //-1/0440C96E800C/DPM/dpMatchPeersCore:
> Match Rule=DP_MATCH_DEST; Called Number=3500
> Oct 11 13:37:12.857: //-1/0440C96E800C/DPM/dpMatchPeersCore:
> Result=Success(0) after DP_MATCH_DEST
> Oct 11 13:37:12.857: //-1/0440C96E800C/DPM/dpMatchPeersMoreArg:
> Result=SUCCESS(0)
> List of Matched Outgoing Dial-peer(s):
> 1: Dial-peer Tag=222
> Oct 11 13:37:12.857: //-1/0440C96E800C/DPM/dpMatchPeersCore:
> Calling Number=, Called Number=3500, Peer Info Type=DIALPEER_INFO_SPEECH
> Oct 11 13:37:12.857: //-1/0440C96E800C/DPM/dpMatchPeersCore:
> Match Rule=DP_MATCH_DEST; Called Number=3500
> Oct 11 13:37:12.857: //-1/0440C96E800C/DPM/dpMatchPeersCore:
> Result=Success(0) after DP_MATCH_DEST
> Oct 11 13:37:12.857: //-1/0440C96E800C/DPM/dpMatchPeersMoreArg:
> Result=SUCCESS(0)
> List of Matched Outgoing Dial-peer(s):
> 1: Dial-peer Tag=222
> Oct 11 13:37:12.857: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
> Calling Number=3500, Called Number=3500, Peer Info Type=DIALPEER_INFO_SPEECH
> Oct 11 13:37:12.857: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
> Match Rule=DP_MATCH_DEST; Called Number=3500
> Oct 11 13:37:12.857: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
> Result=Success(0) after DP_MATCH_DEST
> Oct 11 13:37:12.857: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
> Result=SUCCESS(0)
> List of Matched Outgoing Dial-peer(s):
> 1: Dial-peer Tag=222
>
>
> I interpret the above that 3500 matched on DP 222 as was expected. The below
> is what I interpret as the Inbound DP matching activity as the call returns
> from the loopback
>
>
> Oct 11 13:37:12.857: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
> Calling Number=3500, Called Number=, Voice-Interface=0x0,
> Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
> Peer Info Type=DIALPEER_INFO_SPEECH
> Oct 11 13:37:12.857: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
> Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=222
>
> I interpret the above as the call matched as an inbound DP to DP222
>
> Oct 11 13:37:12.857: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
> Calling Number=3500, Called Number=, Voice-Interface=0x0,
> Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
> Peer Info Type=DIALPEER_INFO_SPEECH
> Oct 11 13:37:12.857: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
> Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=222
> Oct 11 13:37:12.861: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
> Calling Number=, Called Number=3500, Peer Info Type=DIALPEER_INFO_SPEECH
> Oct 11 13:37:12.861: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
> Match Rule=DP_MATCH_DEST; Called Number=3500
> Oct 11 13:37:12.861: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersCore:
> Result=Success(0) after DP_MATCH_DEST
> Oct 11 13:37:12.861: //-1/xxxxxxxxxxxx/DPM/dpMatchPeersMoreArg:
> Result=SUCCESS(0)
> List of Matched Outgoing Dial-peer(s):
> 1: Dial-peer Tag=222
> Oct 11 13:37:12.861: //-1/0440C96E800C/DPM/dpMatchPeersCore:
> Calling Number=, Called Number=3500, Peer Info Type=DIALPEER_INFO_SPEECH
> Oct 11 13:37:12.861: //-1/0440C96E800C/DPM/dpMatchPeersCore:
> Match Rule=DP_MATCH_DEST; Called Number=3500
> Oct 11 13:37:12.861: //-1/0440C96E800C/DPM/dpMatchPeersCore:
> Result=Success(0) after DP_MATCH_DEST
> Oct 11 13:37:12.861: //-1/0440C96E800C/DPM/dpMatchPeersMoreArg:
> Result=SUCCESS(0)
> List of Matched Outgoing Dial-peer(s):
> 1: Dial-peer Tag=222
> Oct 11 13:37:22.897: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
> Calling Number=3500, Called Number=, Voice-Interface=0x0,
> Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
> Peer Info Type=DIALPEER_INFO_SPEECH
> Oct 11 13:37:22.897: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
> Result=Success(0) after DP_MATCH_ORIGINATE; Incoming Dial-peer=222
> Oct 11 13:37:22.905: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
> Calling Number=, Called Number=, Voice-Interface=0x0,
> Timeout=TRUE, Peer Encap Type=ENCAP_VOIP, Peer Search Type=PEER_TYPE_VOICE,
> Peer Info Type=DIALPEER_INFO_SPEECH
> Oct 11 13:37:22.905: //-1/xxxxxxxxxxxx/DPM/dpAssociateIncomingPeerCore:
> Result=NO_MATCH(-1) After All Match Rules Attempt
>
>
> Im certainly no expert (though Im trying ;), but it appears to me that at
> time hack 13:37:12.857 my call matched DP 222 as an inbound. The remainder
> of the debug after that point I cant interpret - only to know that at the end
> it appears that I did not get a successful match.
>
> Below is the aa config
>
> application
> service aa flash:app-b-acd-aa-3.0.0.2.tcl
> paramspace english index 1
> param number-of-hunt-grps 2
> param handoff-string aa
> paramspace english language en
> param max-time-vm-retry 2
> param aa-pilot 3500
> paramspace english location flash:
> param second-greeting-time 60
> param welcome-prompt _bacd_welcome.au
> param call-retry-timer 15
> param voice-mail 53002
> param max-time-call-retry 90
> param service-name queue
>
>
> Jeff
>
> -----------------------------------------------------------
> Jeffrey T. Girard ("Jeff")
> COL, 53
> Future Forces Integration Directorate (FFID), Deputy - Networks
> office: (915)568-1240 DSN 978
> Mobile: (915)727-4222
> reply to: jeffrey.gir...@us.army.mil
>
>
> -----Original Message-----
> From: Jonathan Charles [mailto:jonv...@gmail.com]
> Sent: Tuesday, December 15, 2009 10:40 AM
> To: Girard, Jeffrey COL MIL USA
> Cc: ccie_voice@onlinestudylist.com
> Subject: Re: [OSL | CCIE_Voice] Embedded call-queue script ? (UNCLASSIFIED)
>
> do you have a specific incoming called-number on the dial peer?
>
>
> Jonathan
>
> On Tue, Dec 15, 2009 at 11:35 AM, Girard, Jeffrey COL MIL USA
> <jeffrey.gir...@us.army.mil> wrote:
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>> Jonathan -
>> Thanks for your replies.
>>
>> So, that is not my issue, as when I was configuring the queue and
>> scripts last night, I also received the same indications as you.
>>
>> So, Im still back to my original problem in that it does not appear
>> that the call is matching the inbound DP 222.
>>
>> Jeff
>>
>> -----------------------------------------------------------
>> Jeffrey T. Girard ("Jeff")
>> COL, 53
>> Future Forces Integration Directorate (FFID), Deputy - Networks
>> office: (915)568-1240 DSN 978
>> Mobile: (915)727-4222
>> reply to: jeffrey.gir...@us.army.mil
>>
>>
>> -----Original Message-----
>> From: Jonathan Charles [mailto:jonv...@gmail.com]
>> Sent: Tuesday, December 15, 2009 10:25 AM
>> To: Girard, Jeffrey COL MIL USA
>> Cc: ccie_voice@onlinestudylist.com
>> Subject: Re: [OSL | CCIE_Voice] Embedded call-queue script ? (UNCLASSIFIED)
>>
>> Oh, to prove it is reading it:
>>
>> R3(config-app)#service queue flash:/bacdprompts/app-b-acd-2.1.2.2.tcl
>> R3(config-app-param)#
>> Dec 15 17:22:32.071: //-1//HIFS:/hifs_ifs_cb: hifs ifs file read
>> succeeded. size=24985, url=flash:/bacdprompts/app-b-acd-2.1.2.2.tcl
>> Dec 15 17:22:32.075: //-1//HIFS:/hifs_free_idata: hifs_free_idata: 0x4A4B4B7C
>> Dec 15 17:22:32.075: //-1//HIFS:/hifs_hold_idata: hifs_hold_idata: 0x4A4B4B7C
>> R3(config-app-param)#^Z
>>
>>
>> This is running adventerprise 12.4(22)T2
>>
>>
>> Jonathan
>>
>>
>> On Tue, Dec 15, 2009 at 11:23 AM, Jonathan Charles <jonv...@gmail.com> wrote:
>>> application
>>> service queue flash:/bacdprompts/app-b-acd-2.1.2.2.tcl
>>> param queue-len 10
>>> param aa-hunt1 2001
>>> param number-of-hunt-grps 2
>>> param aa-hunt2 2002
>>> param queue-manager-debugs 1
>>>
>>> However, I do have the TCL script located in a subdirectory in flash...
>>>
>>> If you copy over the CCME full tarball from CCO you get that directory
>>> structure...
>>>
>>>
>>>
>>> Jonathan
>>>
>>>
>>>
>>>
>>> On Tue, Dec 15, 2009 at 11:04 AM, Girard, Jeffrey COL MIL USA
>>> <jeffrey.gir...@us.army.mil> wrote:
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>> I have a separate posting on this list asking for assistance on why my
>>>> B-ACD does not appear to be matching the DP using the Loopback approach.
>>>>
>>>> I printed out the "CUCME B-ACD and Tcl Call-Handling Applications" doc
>>>> from the CCO pages and was reading it cover to cover to see if I could
>>>> find anything in there.
>>>>
>>>> On page 34 of that document, it indicates that "In Cisco IOS Release
>>>> 12.4(15)T or later releases, to use the embedded call-queue script" On
>>>> page 35 it indicates the same for the AA script.
>>>>
>>>> The big difference is in the command to enter the service location
>>>>
>>>> It appears that prior to 12.4(15)T, the commands should be:
>>>>
>>>> Service aa flash:app-b-acd-aa-x.x.x.x.tcl
>>>> Service queue flash:app-b-acd-aa-x.x.x.x.tcl
>>>>
>>>> While for IOS versions 12.4(15)T and after, the commands should be:
>>>>
>>>> Service aa app-b-acd-aa-x.x.x.x.tcl
>>>> Service queue app-b-acd-aa-x.x.x.x.tcl
>>>>
>>>> Without designating the flash: location (as the scripts are embedded)
>>>>
>>>> So, can anyone confirm that my understanding is correct?
>>>>
>>>> If my understanding is correct, I am running 12.4(24)T1 at home, so I
>>>> may be using the wrong commands to call the service.
>>>>
>>>> Jeff
>>>>
>>>> -----------------------------------------------------------
>>>> Jeffrey T. Girard ("Jeff")
>>>> COL, 53
>>>> Future Forces Integration Directorate (FFID), Deputy - Networks
>>>> office: (915)568-1240 DSN 978
>>>> Mobile: (915)727-4222
>>>> reply to: jeffrey.gir...@us.army.mil
>>>>
>>>>
>>>> Classification: UNCLASSIFIED
>>>> Caveats: NONE
>>>>
>>>>
>>>> _______________________________________________
>>>> For more information regarding industry leading CCIE Lab training, please
>>>> visit www.ipexpert.com
>>>>
>>>
>> Classification: UNCLASSIFIED
>> Caveats: NONE
>>
>>
>>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
