" /> EventPartyChanged updates AttributeOtherDN - Genesys CTI User Forum

Author Topic: EventPartyChanged updates AttributeOtherDN  (Read 2428 times)

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
EventPartyChanged updates AttributeOtherDN
« on: January 04, 2022, 11:53:28 AM »
Advertisement
Hello,

I am using genesys urs with ird strategy to collect the extension value of the advisor performing an instant transfer (using WDE 8.5).
when the transfer is started, this value is present in the EventQueued messsage under AttributeOtherDN - under route point.
but after EventQueued there is EventPartyChanged message where the AttributeOtherDN changes to the callers ANI.  in this same event the extension is now only under AttributeThirdPartyDN and also part of a value in AttributeNetworkDestDN (switch::extension).
In the next event (EventRouteRequest) when the strategy is played, the extension is now under AttributeNetworkDestDN only. so my problem is if i use the 'orig' function in ird it collects the caller ANI., not the extension. 

A workaround is to use Consult (two step) transfer method where the AttributeOtherDN still contains the extension value under EventRouteRequest so can be used in the strategy.

Is there anything that is possible here to collect the required attribute value (or extension)?
i looked into using the 'GetRawAttribute' function in ird but this needs the attribute id of AttributeNetworkDestDN which i cannot locate anywhere.

We are using WDE 8.5 / TServer for avaya cm 8.1 / URS 8.1.4.

thanks.

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: EventPartyChanged updates AttributeOtherDN
« Reply #1 on: January 04, 2022, 03:29:36 PM »
You get the Attributes that are currently on the URS when call was queued into the RP and strategy executed, not past events.
You need to adjust your strategy to what is happening on it, not the other way

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Re: EventPartyChanged updates AttributeOtherDN
« Reply #2 on: January 04, 2022, 04:27:46 PM »
all these events are on the same route point.
the problem i have is the attribute value i need changes before the strategy starts (on eventrouterequest).
based on this it looks like the AttributeNetworkDestDN is the only one i can use but cannot see any function in ird to use its value. is there any other known method to obtain it and use it?
as i mentioned i looked into the 'GetRawAttribute' function in ird but need the attribute id- which i cannot find anywhere.  there was an article that contains the IDs of attributes but not the one i want it for.

thanks.

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: EventPartyChanged updates AttributeOtherDN
« Reply #3 on: January 04, 2022, 07:50:06 PM »
You are answering yourself...as said, you can't capture data from events before strategy execution...

Offline hsujdik

  • Hero Member
  • *****
  • Posts: 541
  • Karma: 30
Re: EventPartyChanged updates AttributeOtherDN
« Reply #4 on: January 04, 2022, 09:57:28 PM »
How about changing the option "use-data-from" to "original"?

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 655
  • Karma: -7
Re: EventPartyChanged updates AttributeOtherDN
« Reply #5 on: January 04, 2022, 11:47:35 PM »
[quote author=hsujdik link=topic=12222.msg54611#msg54611 date=1641333448]
How about changing the option "use-data-from" to "original"?
[/quote]

thanks for this.
the setting 'use-data-from' has a value of current for all tservers (premise and site). i am sure we need this to remain as the current value for other call scenarios and was recommended by Genesys some time ago.

is there a way i can override the option either through the route point or strategy?
i noticed the option is under xtrouter section of the tserver options - does this mean i cannot use it in RP annex options for example?

Offline hsujdik

  • Hero Member
  • *****
  • Posts: 541
  • Karma: 30
Re: EventPartyChanged updates AttributeOtherDN
« Reply #6 on: January 05, 2022, 12:06:18 AM »
I don't think these options can be overriden at all. Maybe you can set the ISCC Parameters to propagate=udata then... check if it fits on what you expect on your environment before changing it