Check the Group Type on the first page of your hunt-group form. From your first post it sounds like you want it set to ead-mia (mia is "most idle agent").
You should be able to accomplish this by using an "if" node with a formula that checks the statistic you want. For example: SkillGroup.PG#.CUSTOMER_SERVICE.Avail>0 would check for more than 0 available agents in that particular skill group.
There may be a better way than using an "if" node...
It's really hard to say. I'd investigate the PIM logs as they should give you more detail as to why they aren't starting.
Are you using CMS on both of these PBXs?
In this case it should be the CMS servers trying to initialize the connect to the PGs. I'm assuming the RTA feed on the HA CMS is set up like the primary.
Was the CMS IP/hostname specified on the PGs during the initial setup? If you have a primary and HA configuration you need to leave that...
I'm assuming that you're using Audix. If so you could set the second extension to use the voicemailbox from the first extension. You can do this by adding an entry to the auto-attendant routing-table in Audix (ch auto route).
The "cov" should be if you want coverage on the digits that you are sending to (i.e.- if you're routing to the digits of an extension it will utilize the coverage path on that station). It's been a while since I've done much with vectoring, but that's the way I remember it.
If you have the right features enabled on your PBX you could use ead-loa which would base the decision off of the agent's occupancy. IIRC this is enabled with business advocate.
However, this does seem like a case of "Social engineering through technology.
Not sure what aspect of the configuration you are looking for, but a good starting place would be:
http://www.cisco.com/application/pdf/en/us/guest/products/ps1001/c1225/ccmigration_09186a008059a835.pdf
FYI-
After contacting Avaya they found that port 5022 was not defined in the sshd_config file. Once it was added in and the daemon was restarted it works just fine.
Did you verify that you have the correct switch number set on this subscriber in Audix? I know you mentioned that the old mailbox and this one are on the same switch, but this was the only other thing I could think of. Good luck!
That is correct, I'm trying to get ASA to connect to this media server using SSH on port 5022.
Unless I'm mistaken nothing should need to be in ip-services since I'm connecting directly to the virtual IP of the media servers. At least this is not necessary on any of our other S87xx machines...
Hi-
We have been switching over everything we can to SSH and SFTP lately. I have one CM 2.2.2 S8700 that refuses all connections to port 5022.
I can access these media servers by the standard SSH port (22) using putty and it will connect without an issue. However ASA forces you to connect on...
We recently installed a new duplicated PG that is connecting to an Avaya AES server. We were having trouble getting our PGs to talk with it, so we disabled PGB and turned off the CMS feature in order to troubleshoot just the AES link. We are receiving the following error:
Unable to...
Look in your feature access codes for "Group Control Restrict Deactivation".
Then from a phone with console permissions you should be able to dial that code followed by a 2, then the COR number.
i.e.: if your code was *34 and your cor was 12 it would be "*34 2 12".
CSI is just what I last heard that Avaya professional services was called. Who knows...could be something different now.
Glad that worked out for you, I've been dealing with TCS and IEX feeds a lot lately so it was fresh in my mind.
You also have to change the interval for which TCS is pulling the data. This can be changed by CSI or I believe you can just change the value in the tcs.conf file that should be located in the script install directory.
I've run into almost the exact same issue in the past, we were unable to reach certain areas in Italy from one of our centers. The only real difference is that this was an international call, and instead of setting up a VDN and Vector I just used TAC codes to reach that site.
As in your...
Not that it has much to do with the upgrade but I have run into a similar issue in the past. In our case, the ACD in question was connected to the CMS by a cross-over ethernet cable from the CLAN (the other ACDs were over the company ethernet). They used a cross-over connector and a piece of...
I ran the trace as you suggested. When I use the DID it works like so, I can see it being answered by an Audix station (4883) when using point4:
08:33:37 active trunk-group 13 member 182 cid 0x3254
08:33:37 dial 2065
08:33:37 ring station 2065 cid 0x3254
08:33:47 no answer...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.