Showing results for 
Search instead for 
Did you mean: 

CME B-ACD Nightservice and Huntgroups


need some help to configure nightservice vs. aa and huntgroups

we have a callmanager express.

Today its configured as follow:

Incoming calls from PSTN are translated to an huntpilot, which is configured with a AA Script.

Look here:

Incoming rule for called numbers from PSTN:

voice translation-rule 2

rule 1 /12340/ /94/

Calls someone from PSTN to 12340 the call is translated to called number 94. Then the scripts work and the caller hears an annoncement, after this

the lines in the huntgroup are called sequential.

The application config:


service aa flash:app-b-acd-aa-

  param number-of-hunt-grps 1

  paramspace english index 1

  param handoff-string aa

  paramspace english language en

  param max-time-vm-retry 5

  param aa-pilot 94

  paramspace english location flash:

  param second-greeting-time 120

  param call-retry-timer 10

  param max-time-call-retry 600

  param service-name queue


service queue flash:app-b-acd-

  param queue-len 10

  param aa-hunt1 95

  param aa-name aa

  param queue-manager-debugs 1

  param number-of-hunt-grps 2



and the huntgroup:

ephone-hunt 1 sequential

pilot 95

list 50, 77

timeout 10, 10

display-logout  logged out from Huntgroup

This works fine.

Now there should be a nightservice. The callers to 12340 should be redirectly immediatly to

an announcement and then the call should be end.

So I configured a nightservice:


night-service day Sun 08:00 07:59

night-service day Mon 17:00 07:59

night-service day Tue 17:00 07:59

night-service day Wed 17:00 07:59

night-service day Thu 17:00 07:59

night-service day Fri 17:00 07:59

night-service day Sat 08:00 07:59

I created a virtual DN:

ephone-dn  55  dual-line

number 90 secondary 49490 no-reg both

description TimeBasedRoutingNumber

call-forward all 94

call-forward night-service 99

night-service bell


Calls goes normal if night service is not active and to DN 99 if night service is active.

Then I changed the translation rule for incoming called number from PSTN pointed to the  new DN:

voice translation-rule 2

rule 1 /12340/ /90/

The results:

If night-service active, the call goes right to the extension 99.

If not, the call doesnt route as before, I got an fast busy.

If I do call-forward all 95 at ephone- dn 55 so the call will right go trough the hunt group if night service is not active, but the caller doesnt get the announcement.

Somebody can help?

Hall of Fame Master

For sure results, you can use my B-ACD modifications that support business hours and holiday schedule. Contact info in in my profile.


Hey Support Albakom,

Just came across this thread.

Not sure if you resolved it but if you havent or anyone who will like to do B-ACD with Night Service and a Dummy DN

Please find below

Continue using what you have done pointing the translation rule to 90

Create 2 dial-peers for this purpose and remove service from your main inbound dial-peer

dial-peer voice 23 voip

service app-b-acd-aa

incoming called-number 94

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

dial-peer voice 24 voip

destination-pattern 94

session target ipv4:

dtmf-relay h245-alphanumeric

codec g711ulaw

no vad

Please rate the post

Shibly Ibrahim

Please rate the post Shibly Ibrahim
Content for Community-Ad