I do not believe I need to create a Trung group with GCTI::PARK which I believe is a function of Media server
and I have the option in WDE voice.login,dnless set to true that gives me the ability to add a new phone number in WDE upon login. but as soon as I try to log in the Place is put in a OOS and I am not able to log in and my nailed up connection never gets initialted. can you please help.
so I have an extension provisioned with the necessary options. and WDE is allowing me to put in a secondary number, but as soon as I try to log in an agent to that location. I get DN OOS and cannot log in that agent in WDE, so the nailed up connection never happens ie the call never reaches the agent and stays in queue for ever.
so gcti::park is a hidden functionality of SIP server ie available by default. The issue is that I as soon as we log into WDE the agent VOICE is put OOS. I did try putting in the gateway IP directly in the SIP contact it allowed me to log in but the outbound call is never initiated to get me nailed up
Dear All,
I need a help from you guys, We configured nailed up connection “SIP Server Establishes the Nailed-up Connection on Agent Login or Ready state” while login nailed up established on Agent Phone Number which is not wired line and in my country it is restrict that after 1 hour call should be disconnect automatically so that nailed up connection also disconnect and agent goes not ready as described in document attached below
"AttributeExtensions
The connect-nailedup-on-login key supports this feature. It overrides the connect-nailedup-on-login option setting but only for a current login session.
Specifies SIP Server actions when receiving a TAgentLogin request from a DN with the configured nailed-up connection, as follows:
When this key is set to a Routing Point number, SIP Server immediately establishes a nailed-up connection between an agent's endpoint and the specified Routing Point. After processing the TRouteCall request to the gcti:park device, SIP Server parks the agent on gcti::park, establishing the persistent SIP connection with the agent's endpoint.
When this key is set to gcti::park, SIP Server parks the agent on the gcti::park device directly, establishing the persistent SIP connection with the agent's endpoint.
When this key is set to an empty value, SIP Server disables this feature for a particular agent in a current login session.
I am still surprised why people still use Nailed-Up connection and no Follow-Me function (which is quite similiar but does not require permanent connection via PSTN). Is there any specific reason for using Nailed-up rather than Follow-me?
Well I have been testing and at least here what I found is that cellphone connectivity sucks, so, many calls get lost. With nailed at least the failure reduces.
This is obviously factors Genesys can’t handle.
We use the Follow-me/DNLess function (provided by WDE) accross many customers and never have encountered any issue linked to voice quality or connectivity at all. Also, as the call (to remote agent) is still 3pcc, it can be still recorded as usual by active recording systems.
Not only local customers using that. Also the worldwide customers having call centers accross regions and continents. Somewhere it’s better to use internet connection rather than PSTN. Of course it strongly depends on local provider’s network quality and at last but not least on used architecture and customer’s network infrastructure.
I am not against “nailed-up” agents at all, just want to add other possible way(s) how to achieve the same. The choice is still up to you …
