Hi,
Has anyone gotten the Nailed-up connection for remote agents working for SIP Server where the agent initiates the call?
As per usual the Genesys manual is very terse about how to do it. Get call to route point, give short treatment and route the call to the special DN gcti::park.
How does the SIP Server know that the call is for a particular agent?
I am talking about the call that the agent makes to initiate the nailed-up connection.
SIP Server allows remote agents via a persistant connection. The connection is established between SIP Server and the agent’s phone (usually TDM) and is parked on Stream manager via a special DN gcti::park. When a customer call is distributed to that agent, SIP Server removes the persistant call from gcti::park and “bridges” it to the customer call. When the call is finished the agent does not physically release the call, SIP Server moves the agent leg back to gcti::park, ready for the next customer call.
SIP Server allows 2 types of nailed up connection.
If there is no persistant leg setup when the first call is distributed to the agent, it makes a call to the agent’s DN (actually the contact in the annex tab) and uses that leg as the persistant leg.
Otherwise the agent can initiate a call to SIP Server which is the persistant leg.
The second scenario is the one that the manual is very vague on how to setup. Has anyone gotten this to work and how?
Thanks for the Reply, but we are able to register our Mobile as agent but after that call didn’t landed on the agent.
We seen the status in Cc Pulse and it’s showing as Waiting for Next call.
We have referred the deployment guide of SIP but still getting this problem.
Can you please help me and if you want i can upload the logs