" /> VHT + SIP + GVP - Genesys CTI User Forum

Author Topic: VHT + SIP + GVP  (Read 4486 times)

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

Bob-II

  • Guest
VHT + SIP + GVP
« on: May 27, 2008, 08:00:58 AM »
Advertisement
Hello all.
Can anyone explain me why VH_OFFER always set to "N" in VHT substrategy.
Turn On Threshold set to 00:00:00.

MainReport show next information:
|CallId|00000262683357626052008152142171|2008-05-26 15:21:42.171
|State|New Call|2008-05-26 15:21:42.171
|RefId|31245452626833576|2008-05-26 15:21:42.171
|EWT NoRounding|0|2008-05-26 15:21:42.171
|OpMode|VIRTUALQ|2008-05-26 15:21:42.171
|QueueId|VHT_VQ|2008-05-26 15:21:42.171
|Genesys VRP Device|SIP_Server:VHT_CBQ1_VRP|2008-05-26 15:21:42.171
|New Call|New Call|2008-05-26 15:21:42.171
|Callback Queue Transfer Device|VHT_CBQ1_VRP|2008-05-26 15:21:42.171
|Monitored Call|2008-05-26 15:21:42.171|2008-05-26 15:21:42.171
|Internal QueueId|0|2008-05-26 15:21:42.171
|Callback Offered Days|12345679|2008-05-26 15:21:42.171
|UnderThreshold Queue Transfer Device|50000|2008-05-26 15:21:42.171
|State|Incoming Call|2008-05-26 15:21:42.171
|Holding Queue Transfer Device|50000|2008-05-26 15:21:42.171
|Latest Callback Launch Time|2008-05-26 15:24:42.171|2008-05-26 15:21:42.171
|Earliest Callback Launch Time|2008-05-26 15:21:42.171|2008-05-26 15:21:42.171
|EWT|0|2008-05-26 15:21:42.171
|Upper EWT|0|2008-05-26 15:21:42.171
|Projected Agent Answer Time|2008-05-26 15:21:42.171|2008-05-26 15:21:42.171
|Upper Projected Agent Answer Time|2008-05-26 15:21:42.171|2008-05-26 15:21:42.171
|Lower Projected Agent Answer Time|2008-05-26 15:21:42.171|2008-05-26 15:21:42.171
|Internal EWT|0|2008-05-26 15:21:42.171
|External EWT|0|2008-05-26 15:21:42.171
|ASRLanguage||2008-05-26 15:21:42.171
|Route To Hold Queue|All Trunks Busy|2008-05-26 15:21:42.171
|State|Routing to Hold Queue|2008-05-26 15:21:42.171
|AgentsStaffed|1|2008-05-26 15:21:42.171

Thanks, Boris

Andy Bender

  • Guest
Re: VHT + SIP + GVP
« Reply #1 on: May 27, 2008, 08:07:39 PM »
Hi Boris,

Included in your "MainReport show next information"
is....
Route To Hold Queue|All Trunks Busy|

This is saing that all of the VH inbound trunks are busy, thus there was no trunk to offer VH treatment with, and therefore VH_OFFER was set to "N".

Andy

Bob-II

  • Guest
Re: VHT + SIP + GVP
« Reply #2 on: May 29, 2008, 10:19:01 AM »
Hello Andy.
Thank you for answer.
Can you show me the way for find misconfiguration on VHT or on GVP?
I have GVP installed on same server as VHT. This reserved only for VHT and have 1 ready port that configured on EyeQ. Line status show this port on "wait" status.
Thank you.
Boris.

Andy Bender

  • Guest
Re: VHT + SIP + GVP
« Reply #3 on: May 29, 2008, 01:11:06 PM »
Boris,

If you have only one port to take inbound calls and it is busy processing a call when a second call comes in then there is no available trunk to handle that second call until the first one finishes and frees up the trunk.  Thus, the “All Trunks Busy” situation.  The same thing will happen if you have 12, 24, or N number of inbound ports and  N+1 call arrives.  Just like when all you agents are busy and one more call arrives... the the Switch/ACD will put the call on hold until an agent becomes available.  VH is basically doing the same… if VH does not have a trunk to process the call with it, it will route the call to the hold queue and bypass the VH call treatment.  If it only happens on occasion, it’s probably OK. (the customer will "not" be offered the option for a call back and will be put on hold, to wait in line, just like VH wasn't there)  But if it’s frequent (very likely with only 1 inbound trunk configurated) then you simply need to configure [b]more [/b] inbound trunks.                                                   

If you get "All trunks Busy" on the first and only call then there may be a configutration issue.  However, you should expect "All trunks Busy" on the second call to a "one trunk" system.  Just as you would expect to go to hold it the "one and only" agent was already busy when a second call arrives.

Andy

Marked as best answer by on Today at 09:52:46 AM

Robert

  • Guest
Re: VHT + SIP + GVP
« Reply #4 on: October 30, 2009, 02:53:59 PM »
  • Undo Best Answer
  • It can happened that the VHT software doesn't recognize the GVP ports.