Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Voice Hunt Group in SRST (call-manager-fallback)

I'm looking for assistance in getting my Voice Hunt Group pilot accessible from the PSTN when the router is in SRST mode (call-manager-fallback)

Under normal conditions, the hunt pilot of 9555 5000 is routed to CUCM which controls the hunting process.

In SRST mode, I wish for the same hunt  pilot/group to be active.

If I set the hunt pilot on the SRST router to the full number (9555 5000), this bypasses CUCM under normal conditions

If I set the hunt pilot on the SRST router to the extension (5000), 5000 is not recognised when external calls arrive in from the PSTN.

i.e. The hunt pilot does not create additional dialpeers using "dialplan-pattern 1 955550.. extension-length 4 extension-pattern 50.." command

I have tried creating additional dialpeer using "destination-pattern 95555000" with a preference 0 to CUCM, hoping the hunt pilot dialpeer would have lower preference, however the hunt pilot dialpeer created from the hunt pilot commands takes preference.

I have also tried "alias 1 95555000 to 5000" under call-manager-fallback. This does not seem to work either

When in SRST mode, the hunt pilot works either way when you call the corresponding number from an internal phone.

Am I missing come configuration?

Subset of the  SRST router configuration:

voice hunt-group 1 parallel

list 88401,88402,88403

timeout 60

pilot 5000

call-manager-fallback

secondary-dialtone 0

max-conferences 8 gain -6

transfer-system full-consult

limit-dn 7940 2

limit-dn 7942 2

timeouts interdigit 3

ip source-address 10.10.10.1 port 2000

max-ephones 30

max-dn 60

system message primary SRST mode: Network Down

dialplan-pattern 1 955550.. extension-length 4 extension-pattern 50..

voicemail 0296661000

translation-profile incoming toPSTN

translation-profile outgoing toPhone

call-forward busy 00296661000

call-forward noan 00296661000 timeout 15

time-zone 42

date-format dd-mm-yy

dial-peer voice 1 pots

description --Inbound POTS Dialpeer--

incoming called-number 955550..

direct-inward-dial

port 0/0/0

dial-peer voice 100 voip

description --Dialpeer to CUCM1--

preference 1

destination-pattern .T

modem passthrough nse codec g711alaw

session target ipv4:10.20.20.10

voice-class codec 1 

fax-relay ecm disable

fax rate disable

no vad

Any help would be much appreciated.

1 ACCEPTED SOLUTION

Accepted Solutions

Voice Hunt Group in SRST (call-manager-fallback)

The behaviour is as expected, because in SRST, by default,the dial-peer hunting

choices are - Longest match > explicit preference > least recent use.

Use "dial-peer hunt 2"

"dial-peer hunt 2" forces the dial-peer hunting choices to be - Explicit preference >

longest match in phone number > random selection.

Hence, since the dial-peers  have preference 0  respectively, the call

will hit them first.

Hope this helps!

Regards,

Karthik Sivaram

2 REPLIES

Voice Hunt Group in SRST (call-manager-fallback)

The behaviour is as expected, because in SRST, by default,the dial-peer hunting

choices are - Longest match > explicit preference > least recent use.

Use "dial-peer hunt 2"

"dial-peer hunt 2" forces the dial-peer hunting choices to be - Explicit preference >

longest match in phone number > random selection.

Hence, since the dial-peers  have preference 0  respectively, the call

will hit them first.

Hope this helps!

Regards,

Karthik Sivaram

New Member

Voice Hunt Group in SRST (call-manager-fallback)

Thanks Karthik, the "dial-peer hunt 2" command was helpful.

I also set "preference 2" under the voice hunt group.

This allowed the dial-peers for the Hunt Pilot to CUCM to take preference, and fall back to the SRST router in the event of WAN failure.

2497
Views
0
Helpful
2
Replies