I got an issue and I am sure is cause I have been at this all day and I have missed something.
I am working in a 3845 running 12.4(10) setting up SRST. Behind this RTR I have 2 small call centers that I just want to fall back and hunt a group of phones for while in SRST. I looked around and found an idea here and set it up.
max-conferences 20 gain -6
ip source-address 172.26.1.127 port 2000
max-dn 600 dual-line
alias 1 21810 to 21522 cfw 21200 timeout 12 huntstop
alias 2 21810 to 21531 cfw 21200 timeout 12 huntstop
alias 3 21810 to 21340 cfw 21200 timeout 12 huntstop
alias 4 21810 to 21349 cfw 21200 timeout 12 huntstop
alias 5 21810 to 21313 cfw 21200 timeout 12 huntstop
alias 6 21810 to 21338 cfw 21200 timeout 12 huntstop
In a way this works. The calls come in and go to one of the alias numbers. But only one. It picks a random alias each time. The phone rings for about 12 sec then stops. The caller hears about 3 more rings and they reorder tone.
Call to the second call center (on the same router) bounce between 2 phones continually until the caller hangs up, but will not move to another one of the phones. The next call will pick 2 phones also randomly. Here is the config.
alias 7 21000 to 21244 cfw 21000 timeout 12 huntstop
alias 8 21000 to 21250 cfw 21000 timeout 12 huntstop
alias 9 21000 to 21260 cfw 21000 timeout 12 huntstop
alias 10 21000 to 21273 cfw 21000 timeout 12 huntstop
alias 11 21000 to 21253 cfw 21000 timeout 12 huntstop
alias 12 21000 to 21270 cfw 21000 timeout 12 huntstop
Anyone have any thoughts on where my screw up is and why it is acting differently for each number?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...