Cisco SRST Hunt-Groups and queueing

Hello all,

Apparently, we have been implementing Cisco SRST feature at one of our site using Call-Manager-Fallback mode. And below is our Alias configuration example:

alias 1 1800 to 1864 cfw 1827 timeout 16
alias 2 1800 to 1827 cfw 1811 timeout 16
alias 3 1800 to 1811 cfw 1897 timeout 16
alias 4 1800 to 1897 cfw 1800 timeout 16

What I was expecting to happen is if a call is received on 1800, it will FIRST be routed to 1864. If it's busy or not answered within 16 secs, it will be routed to 1827 and so on. But, what I have found is the SRST router routes the call based on the extension which was REGISTERED FIRST with the SRST router (or may be random??).
What I am trying to achieve here is, ext. 1897 should only be receiving calls if all other 3 extensions are busy or not answering.

Could you please advise me if this can be possible?

I don't think using "Preference" keyword on alias command would make difference because that can only be used if I have more than one dial-peer for the same destination-pattern (extension) which in this case I don't.

Also, I don't want to use "Call-forward busy" and "Call-forward noan" commands because that will forward calls from any registered extension, not only from the hunt-group.

Also, I was wondering if the SRST router has the ability to queue the calls? What happens to the next call if every extension in this hunt-group is busy on other call?

I am using Cisco 2851 router with 3.3 Ver of SRST.

Your help will be much appreciated!!!

Thanks,
Pratik.
widuserAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

lrmooreCommented:
What version of Call Manager are you using?
All call handling should be taken care of in the Call Manager application, not on the SRST gateway itself, especially if using mgcp fallback mode.
0
shameer2000611Commented:
just put the preference command like below and try


alias 1 1800 to 1864 preference 1 cfw 1827 timeout 16
0
widuserAuthor Commented:
Irmoore, I am using Call Manager 4 but this is irrelavent to this issue as SRST router won't be able to talk to the CCM in case of a WAN outage as the CCM resides on WAN. I am not using MGCP.

Shameer, I have tried using preference command but unfortunately, that doesn't work. The use of "preference" keyword here actully defines preference of x1864 dial-peer over any other x1864 dial-peer's that may have been created.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Voice Over IP

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.