B-ACD not working

[andres.pasten]

Hi,

I´ve a config of B-ACD that is not working on a Cisco 1861. But the same cnfig works fine on others Cisco 1861. Here it is:

application
  service autoatt app-b-acd-aa-2.1.2.2.tcl
  paramspace english index 1
  param menu-timeout 6
  param second-greeting-time 10
  paramspace english language en
  param max-time-vm-retry 0
  param max-time-call-retry 60
  param voice-mail 99
  param aa-pilot 330030
  param max-extension-length 4
  param number-of-hunt-grps 2
  paramspace english location flash:
  param dial-by-extension-option 1
  param handoff-string autoatt
  param welcome-prompt _bacd_welcome.au
  param call-retry-timer 5
  paramspace english prefix en
  param service-name queue
  !
  service queue app-b-acd-2.1.2.2.tcl
  param queue-len 1
  param aa-hunt3 5572
  param number-of-hunt-grps 2
  param queue-manager-debugs 1
  param aa-hunt2 5570

dial-peer voice 1 pots
service autoatt
incoming called-number .*
port 0/1/0
!
dial-peer voice 2 pots
service autoatt
incoming called-number .*
port 0/1/1

The situation is this:

1.- The call arrives from the PSTN through the FXO 0/1/0 or 0/1/1

2.- Then dial-peer 1 and 2 triggers the service autoatt

But now the service is not triggered, Ive tried with debug voice application media service, and nothing appears...

The FXO are working fine for outgoing calls, using a debug vpm signal I can see the call arriving to the FXO.

Any idea?

TIA

Andres Pasten

Adexus S.A.

[Clifford McGlamry]

I wouldn't configure the FXO ports that way.

Put the pilot for the AA on a dial peer like this:

dial-peer voice 2501 voip
service aa
destination-pattern 1005
session target ipv4:10.1.10.10
incoming called-number 1005
dtmf-relay h245-alphanumeric
codec g711ulaw
no vad

If you need to get the FXO ports to the dial peer, use a PLAR to point it to the dial peer.

[andres.pasten]

Hi Clifford,

and that IP 10.1.10.10, is the IP address of the gateway running the B-ACD?

so the dial-peer is targeting the same gateway?

Please let me know.

[Clifford McGlamry]

It's the IP address of the loopback adapter on the BACD router.

[paolo bevilacqua · Accepted solution]

Actually the pots DP with port configuration is right in principle. It triggers the service directly on the pots DP.

That is a good thing since it avoids the VoIP loopaback, slightly improving response time and voice quality.

Then it has to seen why it doesn't work, it can be an issue with clid that sometime takes precedence. It can be worked out, however.

[andres.pasten]

Hi,

Finally the config was fine, we tested it on another Cisco 1861 and it worked fine. We replace the gateway and the issue was solved. Now I´m waiting for that 1861 to check what is wrong with it.

Thanks anyone for the support!!