03-05-2010 10:48 AM - edited 03-15-2019 09:39 PM
I am attempting to configure Basic ACD to service all incoming calls that are not matched against a registered ephone-dn or other lower preference dial peers. I have gotten the dial peer and application configured; however, I cannot figure out how to make it work with a wild card incoming called-number value. It appears that an explicit value is required on both the application param and incoming called-number command.
Has anyone done this before? If so, what am I missing? The following configuration works if the user dials exactly 5550100; however, any other number does not match for obvious reasons. If I change the incoming called-number command to include a wildcard on dial-peer 2, the application fails and gives a reorder tone.
application
service app-b-acd1 flash:bacd/app-b-acd-2.1.2.3.tcl
param number-of-hunt-grps 1
param queue-manager-debugs 0
param queue-len 15
param aa-hunt1 16085550100
!
service app-b-acd-aa1 flash:bacd/app-b-acd-aa-2.1.2.3.tcl
paramspace english index 0
param max-time-vm-retry 0
param max-time-call-retry 600
param voice-mail 0
param aa-pilot 16085550100
param number-of-hunt-grps 1
paramspace english language en
param handoff-string app-b-acd-aa1
param call-retry-timer 15
paramspace english location flash:bacd/
param service-name app-b-acd1
param drop-through-option 1
param drop-through-prompt _bacd_welcome.au
param second-greeting-time 45
!
03-05-2010 11:51 AM
To do that, send all calls for such wildcard, with a translation-profile changing called number to "aa-pilot".
Session target, some local interface.
On the same DP, configure incoming-called number with said pilot number.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide