Call Type Prediction on T-server

[OXE_4400]

I need to distinguish incoming internal and external calls (both non CC).
Stat server assign incoming call to type internal only in case of incoming call from other agent (Main Mask CallInternalReceived).
Exist T-server option call-type-by-dn for Call Type Prediction.
I have created inbound-translator-0 option with value rule-internal, where rule-internal corresponds to another section with internal numbering rules inside. But I am not getting what I want.
How it works exactly?
I need to count all calls from ANI 99xx as internal.

[cavagnaro]

Maybe a filter can  be your friend PairExists("ANI","99*")

[OXE_4400]

Hmmm. Sometimes the best ideas are quite simple. Many thanks. I will check it.

[OXE_4400]

Not exactly PairExist.
Filter works in case of strict:
ANI="9951"
but doesn't work using * or ?.

According to stat server user guide:
You can use the ? and/or * wild-card characters in the designation of the option’s value. Stat Server matches ? in a wild-card string to any single character. Stat Server matches * to zero or more characters.

I have tried ANI="99*", also ANI="99??".
Does anybody knows how it works.?

[cavagnaro]

Hum...maybe those doesn't work with wildcards...
What you can try:
As soon as call enters RP re-attach the ANI as a new KVP (myANI) and then on the target object associate a VQ and then apply the filter to this VQ in the way of PairExists which does accept wildcards as "99*"
I think that will work

[OXE_4400]

These calls are not going through RP, its simple non-CC incoming internal or external calls. Calling user dials agent number and I need to count separately inc internal and external calls.
Exists some specific Extensions parameters attached to external incoming call but I can't be sure on these parameters. They are linked to ISDN numbering plan, number type.

[cavagnaro]

Thinking more:

There is a chance that you can load a strategy to an extension so when the extension rings you execute a strategy that will attach a KVP and then you might try to filter it on the event CallInbound with that KVP:

http://www.sggu.com/smf/index.php/topic,2426.msg9126.html#msg9126

The idea would be:
1. Change TServer or URS option "event_arrive" to "routerequest, ringing"
2. IRD doesn't support loading strategy on extension - it's necessary to "load" it manually using CME
    - create section "urs" in the annex-tab of the extension
    - create a new key "strategy" with value corresponding to the name of existing strategy

This strategy will only attach a KVP with the value you may need (CallTypeCustomer = "AsInternal")
So your filter would be:

PairExists("CallTypeCustomer","AsInternal")
or
PairExists("CallTypeCustomer","*")

I haven't tried it yet because I have no access to a Genesys environment for these days...vacations they say hehe

Hope this can help you

[cavagnaro]

Other option:

[option]
Stat Server now supports two wild-card characters (? and *) when applied to user-data values in filters. (This functionality does not apply to user-data keys in filters.) The ? wild-card character in a string can substitute for any single character; the * wild-card character in a string can substitute for zero or more characters. Wild-card support is disabled by default. To enable this feature, set the filters-allow-wildcards-in-values Stat Server configuration option to yes. (ER# 41555115)
[/option]

You may need to enable this option and restart SS to make it work

Cheers