" /> Auto Agent Login In Avaya to Genesys SIP Trunking - Genesys CTI User Forum

Author Topic: Auto Agent Login In Avaya to Genesys SIP Trunking  (Read 9445 times)

Offline pspenning

  • Jr. Member
  • **
  • Posts: 99
  • Karma: 0
    • West Interactive
Auto Agent Login In Avaya to Genesys SIP Trunking
« on: May 14, 2007, 02:55:38 PM »
Advertisement
Good Day,
I am about as new to Genesys as one can get....  For Now...

However, I am running into a small issue during the installation of our platform.

We have been asked to provide a hunt group with "Auto Login" agents for our IVR piece.  We can do this with no problem when connecting our Agents to specific T-1 ports but, with Genesys, we are 100% SIP Trunk connectivity from our Avaya S8700 ESS to the GVP.  Has anyone done this before?  If so please help a poor newbie out...  :'(
Thank you in advance.

Perry

Peter J

  • Guest
Re: Auto Agent Login In Avaya to Genesys SIP Trunking
« Reply #1 on: May 15, 2007, 04:11:00 AM »
Are you trying to login your GVP in?

If you are using SES then all you need to do is provide username for every IPCS port which would match the extension you have provisioned in Avaya.

You also need to define ports then you need to do it via Resources->IVR, where you would define a DN and a Port.

I assume you have done that too.

The trick is Annex in IVR Port Annex - you have to create AutoLogin Section. In there, add these keys:

* AgentId
* Queue
* SetLoggedIn  (you want to set it to true)
* SetReady (Ditto)

Then, you will need to create a person, select default place that is that of a port and also assign agent id to that person equal to that of annex in IVR port.

Oh, last but not least, you can always create an app that would log your agents for you if you don't like AutoLogin section. 

Did it help you?





Offline pspenning

  • Jr. Member
  • **
  • Posts: 99
  • Karma: 0
    • West Interactive
Re: Auto Agent Login In Avaya to Genesys SIP Trunking
« Reply #2 on: May 15, 2007, 12:09:50 PM »
Fantastic!  I think....  Remember, I am a little new to this...
So what I understand you to say is that the auto login piece is actually done on the IVR side as apposed to the Agents in Avaya....  I thought that this would have to be done this way but I just wanted some validation.  I will try this and report back but it all sounds like what I am looking for.  I appreciate your help.

Perry

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1417
  • Karma: 18
Re: Auto Agent Login In Avaya to Genesys SIP Trunking
« Reply #3 on: May 16, 2007, 04:30:44 AM »
PSP (Playstation Portalble?)

adding to Annex will probably get you what you want. You still would probably want a tool though to control when they login and logout. :)

Offline pspenning

  • Jr. Member
  • **
  • Posts: 99
  • Karma: 0
    • West Interactive
Re: Auto Agent Login In Avaya to Genesys SIP Trunking
« Reply #4 on: May 16, 2007, 01:25:13 PM »
I wish....  (PSP - My Initials Perry S. Pennington)

Actually I was reviewing this post with our Consulting group who is installing our platform and after going to Genesys as well as testing, it has been determined that this is not possible in the way we were asked to do it.  Sooooo...  We just created a simple Hunt in Linier fashion with X-ported stations as the members.  Those X-ported stations are then mapped as OPS lines to the SIP trunks.  We can still get reporting on it but not from the Avaya side....  So far it seems to do everything that was requested...

Thanks for the help!
Perry

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1417
  • Karma: 18
Re: Auto Agent Login In Avaya to Genesys SIP Trunking
« Reply #5 on: May 16, 2007, 04:06:13 PM »
Perry,

why would Annex not work for you? What was the problem?
We are installing GVP on a client side right now, and I would like to be aware of any irregularities arising due to its use.

Vic

el.spiko

  • Guest
Re: Auto Agent Login In Avaya to Genesys SIP Trunking
« Reply #6 on: May 16, 2007, 04:44:45 PM »
Looks like the SIP trunking vs. SIP extensions is the issue.  You probably want to check back with your consulting group and see if they can provide you sip stations for the GVP vs. a SIP trunk. 

Offline pspenning

  • Jr. Member
  • **
  • Posts: 99
  • Karma: 0
    • West Interactive
Re: Auto Agent Login In Avaya to Genesys SIP Trunking
« Reply #7 on: May 16, 2007, 04:58:40 PM »
I wish I could answer these questions...  I am very very strong on the Avaya side but am just cutting my teeth on Genesys.  I will ask our consulting group about Annex and report back...  Sorry...

As for the SIP trunks vs SIP Stations, that sounds logical...  But we are still working with SIP trunking on the Avaya side which is where the hunt group / queue is.  How could that allow for an auto login type of agent?  Or would that still be done on the Genesys side?  (Do I even make sense???)  ???

el.spiko

  • Guest
Re: Auto Agent Login In Avaya to Genesys SIP Trunking
« Reply #8 on: May 16, 2007, 06:20:16 PM »
From the Genesys GVP reference manual.  IVR in front and Behind are logical concepts when dealing with SIP however it still matter on how you configure you application and how you setup your IP ports.  With a SIP trunk, you're using an IVR in front model with with SIP extensions you are logically behind the switch.  With a SIP trunk there are no agents or extensions.


[b]Ports[/b]

A port is defined as the capability to receive or send a discrete call. For example, a hardware platform supporting 23 simultaneous and discrete
conversations would require 23 ports.
The GVP architecture has universal ports, which deliver features such as
Automatic Speech Recognition (ASR), Text-to-Speech (TTS), and inbound
call processing.
GVP can simultaneously handle multiple calls for one or more voice
applications. In the IPCS/VCS, a set of physical ports is not dedicated to a particular voice application. A call received on any physical port can access
any configured voice application.
You can deploy the IPCS/VCS component of GVP in front of or behind the
switch. Each mode has Universal Port capability. Different approaches are
used in each configuration to identify the desired voice application.

[b]Behind-the-Switch Deployment[/b]
When the IPCS/VCS is deployed behind the switch, the enterprise switch is
configured with a unique Directory Number (DN) for each Digital Signal Zero
(DS0) from the enterprise switch that terminates on the IPCS/VCS. A DN is a
unique logical number associated with each port on the enterprise switch. The
Genesys Configuration Manager environment permits the association of an
IPCS/VCS port with a DN, with the help of an IVR Server application. Each
instance of IPCS/VCS must be registered manually as an IVR object under the
Resources > IVRs section, as described in Step 1 of “Configuring IVRs and
IVR Ports” on page 387. Each IPCS/VCS is configured with a corresponding
set of DNs.
Identifying the voice application in a behind-the-switch configuration also
requires the Genesys IVR Server. The IPCS/VCS registers itself with the
Genesys IVR Server at startup. Each IPCS/VCS universal port (IVR port) is
labeled with a unique IVR port number on each IPCS/VCS. The IVR Server
reads objects in Configuration Manager with the mapping of each IVR port to
its designated DN from the IVR.
When an incoming call arrives at the enterprise switch:
1. The call is presented to an available IVR port on the IPCS/VCS.
2. Simultaneously, the enterprise switch provides the IVR Server, through the
CTI Link, with the incoming call’s ANI and DNIS.
3. The IPCS/VCS contacts IVR Server and solicits caller information that is
associated with that unique IVR port number.
4. The IVR Server associates the number received from the IPCS/VCS with
an enterprise switch DN, and returns the associated information to the
IPCS/VCS.


[b]In-Front-of-the-Switch Deployment[/b]

When the IPCS/VCS is deployed in front of the switch, it receives the
incoming call’s ANI and DNIS directly from the Public Switched Telephone
Network (PSTN).

With an IVR-In-Front-of-the-Switch Configuration
Configuring DNs
1. Create a Switching Office object of the Virtual Switch for IVR-in-Front
type.
2. Create a Switch configuration object that represents your virtual switch,
and associate it with this Switching Office.
3. On the Switches tab of the virtual T-Server application, associate the
Switch with a virtual T-Server application that represents your IVR Server.
4. Under the Virtual Switch, configure DNs of the Voice Treatment Port
type. These DNs are “fake” DNs, because they are in a virtual switch, not a
real switch.
Configuring IVRs and IVR Ports
1. Create an IVR object of any type except Unknown:
a. The value of the IVR Name field is the IVR Client Name specified in the
IPCS/VCS configuration. Refer to the Genesys Voice Platform 7.5
Deployment Guide.
b. Specify a valid version of the IVR Server.
c. Use the Browse button to select the IVR Server application.
2. Under the IVR object, create IVR Port objects for all active IVR ports:
a. Use a two-digit format (such as 01) to specify a Port Number.
b. Browse for the Associated DN, which should be the Voice Treatment
Port DN you created in Step 4 of “Configuring DNs”.