" /> MultiSite TServer Configuration - Genesys CTI User Forum

Author Topic: MultiSite TServer Configuration  (Read 6005 times)

john

  • Guest
MultiSite TServer Configuration
« on: January 01, 1970, 12:00:00 AM »
Advertisement
Can anbody help?
We want to transfer calls via the PSTN from one location to another, both sites have TServer. The call will come through an IVR then transfer out of the IVR to a DN with RLT configured. (this should not be a factor in the scenario)
Can the 2 TServers negotiate the message exchange necessary for a screen pop when the voice has been routed over the PSTN? The switches are not networked.
Any help is appreciated.
Thanks
John (CTIGUY)

Ray

  • Guest
MultiSite TServer Configuration
« Reply #1 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • It is possible if you have :
    1.A license for external routing
    2. The 2 Tservers on the same network
    3. Each Tserver must contain the other in it's CME connection tab.
    4. The access codes are defined in the switch config under resources in the CME
    5.You are using external route points in CME and your strategy.

    Victor

    • Guest
    MultiSite TServer Configuration
    « Reply #2 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • You will also need a Network Overflow Manager or IR to transfer the attach data between the TServers.

    Philou

    • Guest
    MultiSite TServer Configuration
    « Reply #3 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Hi,
    Can you explain what is it the Network Overflow Manager... I know IR in the GENESYS suite.
    It's a product in this suite ?
    Thanks.

    Jim

    • Guest
    MultiSite TServer Configuration/NOM
    « Reply #4 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • NOM allows attached data to be passed site to site in a multisite enviroment.
    We are using Avaya/Lucent switchs and external router does not work in our enviroment and we do not use IR. NOM was the solution to pass IVR attached data on interflowed calls.
    It's a bit of pain to set up but works fine.

    If you want more details let me know.

    Jim

    Victor

    • Guest
    MultiSite TServer Configuration
    « Reply #5 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Nom stands for Netowrk Overflow Manager. The whole point for it, is to allow for attach data to be passed from one TServer to another without all the fancy and pricey IR.

    The concept itself is very simple a call is transfered from one PBX to another PBX via an NACD, and NOM remembers the Network Call Id generated by the NACD, so when the call arrives at PBX #2, NOM tells TServer on that PBX to attach user data previously contained by TServer #1 for this call.

    Do I make any sense?
    Vic


    Philou

    • Guest
    MultiSite TServer Configuration/NOM
    « Reply #6 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Thank you for your assistance.

    Philou

    • Guest
    MultiSite TServer Configuration/NOM
    « Reply #7 on: January 01, 1970, 12:00:00 AM »
  • Best Answer
  • Thank you for your assistance