" /> DNIS between two sites - Genesys CTI User Forum

Author Topic: DNIS between two sites  (Read 4929 times)

This topic contains a post which is marked as Best Answer. Press here if you would like to see it.

Vic

  • Guest
DNIS between two sites
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Hi,

another question I was hoping someone can help me with is:

howcome AttributeANI is passed along from site A to site B byt AttributeDNIS is not? Is there a way to force Genesys to use AttributeDNIS received form remote TServer as opposed to using the local one?

Mikael Jansson

  • Guest
DNIS between two sites
« Reply #1 on: January 01, 1970, 12:00:00 AM »
Hi !
We have a Meridian Network, and there it's not possible to get AttributeDNIS from switch within the private network. (according to our switch vendor).
Regards Mikael

Vic

  • Guest
DNIS between two sites
« Reply #2 on: January 01, 1970, 12:00:00 AM »
I know!!! this is why I thought if we have TServer on Site A and TServer on Site B, there is a way to have Genesys to transfer DNIS along with everything else when you send the call from A to B.

I mean, it does not make much sense to have Genesys on site B to retrieve DNIS from site B if it knows that call came from Site A and has DNIS already attached to it.

Any ideas? Right now, I am forced to use attachdata to get the thing across, but it is making everything sooo ugly!

Mikael Jansson

  • Guest
DNIS between two sites
« Reply #3 on: January 01, 1970, 12:00:00 AM »
Hi Again !
Sorry if I offended you in some way ;)

But since value in AttributeDNIS is "owned" by the switch i think it's hard to force Genesys to use a different value from the one passed on by the switch.

Hopefully someone else has a solution for you. Because I also would like this feature.

Cherers
Mikael

Marked as best answer by on May 07, 2025, 01:51:44 AM

Dave

  • Guest
DNIS between two sites
« Reply #4 on: January 01, 1970, 12:00:00 AM »
  • Undo Best Answer
  • You could always have the routing strategy at Site A copy the value from AttributeDNIS and put it into UserData, then use that UserData in the strategy at Site B if you're re outing the call once it gets there...

    Kerrick

    • Guest
    DNIS between two sites
    « Reply #5 on: January 01, 1970, 12:00:00 AM »
    It has been said, but the answer is to attach the DNIS to the TKVList while the call is at site one.

    I have heard you can update the DNIS property in a routing strategy, but not sure of how it is done. It was one of the network carrier folks that was telling they use router to change the DNIS for small business customers.

    Good luck.