I want to apply an extensionupdate function based on the site of the target agent.
as this is known at the selection block within IRD, I cannot apply it afterwards because the routing is done. I need it to attach to the Extension Attributes so calls to a specific site have this update.
I don’t think I can apply it before the selection block because the target (agent/site) is not yet known.
Was wondering and hoping there is a function or method to do this.
What exactly are you trying to achieve? You can’t adjust extension data within a targeting block as far as I know, but there’s probably another way to do whatever it is you’re doing.
we want to route calls to specific External Route Points within a site.
in SiteA, we want inbound calls to use ERPs 60000-60030 and outbound calls to use ERPs 60030-60035. to achieve this we need to add ExtensionUpdate[‘epn’,‘Inbound’] into inbound strategy and ExtensionUpdate[‘epn’,‘Outbound’] to outbound strategy. Each ERP has a TServer section, epn option with value either ‘Inbound’ or ‘Outbound’.
this is not applicable to others sites so cannot just add this as a function block before the routing selection block.
You could use SelectDN + SuspendForDN + TRoute (the selection block does that on the background). So you would apply the ExtensionUpdate before the TRoute
I’m not clear why ERP’s would be used for Outbound calls. As far as I’m aware they are only required for ISCC routing (eg. between sites), outbound calls would simply be routed via the switch right?
I’m still not clear on the end goal, eg. why do you need to do this?
Perhaps give us some more detail about the environment too, eg. what switch are you using (Avaya, Alcatel, SIP Server etc)
As hsujdik mentioned, you could manually expand the target block and perform the individual functions manually. Not ideal for future maintenance though.
Why not to apply extensions from inside Target Selection block (after target/agent already known but before routing request is done)?
There are bunch of ways to do it (custom routing, etc.).
Yep custom routing (in the first tab in the target selection block) is what you want
It gives you the selected target as input variables and you provide it with the modified (or the same) target as output variables - and you can do whatever else you like in between
this seems like the best option.
where is custom routing configured? within the selection block, the custom routing field is blank presuming because it has non created. had a look within urs deployment and articles but nothing stands out on how it is done.
You better to look in Genesys docs.
Basically custom routing is subroutine that you can plug in into target selection object.
You create this subroutine (following plug in rules and putting inside all logic that you need) and put reference on it into target selection object.
