Command for ITYPE cero extension

[DonPollo]

Hello guys!

Our platform is an integrated PBX/ACD MD110 with Genesys CTI. For achieved routing interaction, we´ve configured in the PBX a ITYPE zero extension (digital extension without a phisical teleset connected) where the CTI get the control of the interactions.

Over the ITYPE zero (0), we´ve configured an divert over an ACD group(for backup proposal)when CTI was down.

Sometime, the ITYPE zero is bloked and we need to know which is the command to realese this extension.

(Now, we´d done this action connected a teleset to the extension ITYPE)

 

[jazaya]

Hi:
Not sure if this is exactly what you are looking for but hope it helps:
BLDBE:bpos=limNo-MagNo-boardposition;
The command removes manual blocking of all individuals on a device board or clear all fault markings for the individual to zero.


THe following is an example:
Equipment position is LIM 2, magazine 3, board position 32;

Bldbe:Bpos = 2-3-32;
And of course BLEQE:equ=limNo-MagNo-boardposition-IndiviualNo;

Removes manual blocking of device individual or clears all fault markings for the individual to zero.
I think BLDBE is what you are looking for;
Regards




Experience it, there is no substitute.
RemoveThisJazayeri@kiasagroup.com

 

[DonPollo]

Thanks for your answer...but I think that I didn´t explain fine.

We have integrated a PBC/ACD MD110 with Genesys CTI. For routing interaction by the CTI, we need the following configuration in MD110:

A GS (Hunting Group) associated with an extension itype 0.
,CTI monitores both elements as a Routing Point so I could download a strategy for routing proposal.

Over the Hunting Group and the itype cero there are configured a divert for backup proposal, I mean, when the CTI was down the PBX take the control of the interaction and divert these to an ACD Group.

The extension itype cero is an special digital extension without a teleset connected, but with the call tone.

The problem is that something is wrong, and the CTI is down, the call arrives to the itype cero, after the 4 tone the call is divert to the ACD Group. Well, I put the CTI up, but the the call arrives to the itype cero everything is working as the CTI was down, I mean, in the 4 tone the call is divert...The problem is the itype is out of the Huning Group...this is the rason for the call wait until the 4 tone...so the only way to put into the Hunting Group again this extension is connected a phisical teleset to this extension and to an operation (i.e. hangup the teleset). When the itype is again into the HG everything work properly.

My question is: Is it possible put this extension (itype) again into the Hunting Group sending any commmand? (It is not operable connected a phisical extension or teleset in this extension for putting again the itype into the group).

Thanks!

 

[whosrdaddy]

DonPollo,

I see what's your point, in BC11 you have ASPAC 178 to retain the member in the group hunting. if you don't have BC11 you must find another way (in any way don't divert extensions that are in GH's)

http://www.damovo.com

 

[lalrl]

Which Softwarerelease do you have? If you have BC10 or higher, than program a real CTI-Group.

And: I think gh-grp can not be monitored. In your case only the extension is monitored. If I´m right, so I ask me, why you have a gh-grp? If CTI would be able to monitor a gh-grp, you would not need an extension. Then you would program a gh-grp without extensions with cdini to real ACD-grp. If monitoring stops, cdini would work. If monitoring starts, cdini would be passive. But this does not work, because in your Software (I assume BC9 or lower) gh-grp can not be monitored.

In your case I would test do delete the gh-grp and the extension and to reinstall the extension with the number of the old gh-grp.

Good Luck

 

[DonPollo]

Well, the PBX/ACD is a MD110 BC10; so I suppose that the command ASPAC 178 won´t work because it is for BC11.

And the other hand, our configuration should be in the way that I explained before, for recommendation of the CTI vendor (I mean, we follow the instruction that Genesys gives us). We tried different configuration and the only way that we achieved to receive the events in the CTI was: HG with a itype cero associated.

Only, we need to put this itype cero into the HG sending any kind of command when over the GH and the itype there is a divert configured. Now, we did it connecting a phisical extension to the itype line and it isn´t very usseful.

When we don´t have divert, we don´t have problem.

 

[lalrl]

you do not need aspac 178, if you use CTI-Group.

And just today I have read a manual from genesys about link to MD110. They offer both (indeed gh-grp with itype0-extension and CTI-group). In my opinion using gh-grp is oldfashioned. I remember to BC7 and BC8, where no CTI-group could be programmed in MD.

And you can sending cdini-commands also for a CTI-Group to activate backup.

And if the extension is out of the group (for any reasons), you would never have to wait 4tones before diversion. If extension is out of group, diversion from the group would work - but directly and not delayed. And: Normally diversion after time will not work to an ACD-Group - or you have special patches.

Other question to you: Is it necessary, that your agents will be present (#73*auth*pin#)in order to beeing involved in the routing scenario of genesys? Or is it enough, that agents are logging in via Softphone?