Hunt Group Service Observe

[entertrain]

The hunt group is set for service observe. The COR is a valid service observe COR. The hunt group has one group extension. A fast busy is received when attempting to service observe the hunt group extension. Nobody else is service observing the group extension. I'm figuring the problem is with the group extension COR, however no idea how to check or change the group extension COR. Any suggestions? (G3si)

 

[mikeydidit]

You can change the hunt groups COR on the first page of the hunt group form. I would think that you would need to use the service observe feature for the members as the hunt group number is bascially just a route to number (no hardware assigned) directing calls to the members.

"Wise men speak because they have something to say; Fools because they have to say something."
(Plato)

 

[entertrain]

First, thanks for your response. All of the members have the correct COR for the service observe. The hunt group itself also has the correct COR. It sure seems odd. I may try changing the COR to an even less restrictive COR and see what happens, even though the COR it has allows for the service observe. Thanks again.

 

[mikeydidit]

Does the set that you are trying to use with the service observe have console permissions. I would try that too.

"Wise men speak because they have something to say; Fools because they have to say something."
(Plato)

 

[donbott]

How about the incoming trunk COR?

DonBott
Chairman
Omnipitence, Ltd.

 

[avayafreakje]

i dont think you can observe the huntgroup.

 

[4merAvaya]

You can Service Observe Stations, Agent IDs, or VDNs, but not the Skills of Hunt Groups.

Kevin

 

[entertrain]

Thanks to everyone for your input. Don, the incoing trunk COR is okay for the service observe. AVAYAfreakje, that's sort of what I thought maybe, but then why does the hunt group station form have an option for selecting service observe? I cannot find anything about that in AVAYA's documentation, but maybe I don't have the latest version. Kevin, what about the group extension defined within the hunt group? Can't I service observe the group extension, and if not why does AVAYA include the option for service observe on the hunt group form? Thanks again for everyone's input. I may need to change my programming to make this hunt group a VDN instead of a hunt group, and maybe never will determione why AVAYA has the service observe option on the hunt group form itself.

 

[Definity]

I might have missed it but I have never seen a service observe option on the hunt group form. entertain, can you confirm where on the hunt group form do you get a service observe selection field?? I only see "service level" on page-2 which starts with service.
I second 4merAvaya, you can't SO a hunt group extension.

 

[simreal]

4merAvaya is correct, You cannot SO hunt groups. My sugguestion would be to SO the VDN that is routing the calls to the skills.

We setup a DID number that points to a VDN. That VDn refrences a vector that prompts the caller for a security code and the if the code is entered correctly it routes the call to the feature access code for SO and then the extension of the VDn that those calls are routed thru. On the initial VDN that the DID points to you wanna set observe on agent answer to "y" and on the vdn that the calls route thru set it to "n" That makes it so you wait until the next call comes in instead of sitting there hearing a specific agent do nothing until they get a call.