Try adding {d} before the param. I don’t actually know if this works for Composer/ORS, but if you need to specify a type of data on IRD, you prefix it with the data type such as {d}, {s}…
not sure what you mean here - in the URS function block i just have the option of specifying as string or int for the params
i’ve logged a ticket to hopefully resolve.
this function call from ORS / URS is tricky with the params. I had another one i did where IRD would accept true, but Composer i have to set it as 1 as that’s all it’ll accept.
Basically error 0006 Operation impossible means in this case that URS simple cannot sent trequest at all.
One of things to check: 04a602c64e1e8c68 is virtual call (not coming to URS from tserver but created by request from ORS) and in such case such call isn’t “related” with any tserver so URS simply doesn’t know to which tserver to send request.
if so try to add in event spec extra parameter tserver with name of tserver or switch with name of switch.
Also use number as event identification (58 instead of EventDiverted) in all cases when strategy or its fragment that URS happen to execute is not compiled first (in URS web method func it doesn’t)
that’s true terry, this is a chat interaction i did try 58 enum instead of eventdiverted but still had issues. when you say put the switch name are you alluding to the vq@switch for thisdn attribute?
Yes, like that, just keyword name “tserver” (or switch) to be lowercase, like
|tserver:TServerAlcatel.
In other words - proovide name of tserver that URS will use for sending the event.
alright gonna try it and let you all know using the tserver name.
Genesys is swaying me to use the session:fetch tlib request type instead which i’ve done and can get working.
I asked him that i wanted to go the URS function route as it’s much more intuitive and easier for the next developer to understand than a custom SCXML block. I’lll keep you guys posted in case anyone is interested.
just some context to what i’m doing - just manually trying to manipulating and peg multiple VQs for reporting purposes that the customer is requesting for.
