Author Topic: error.com.telera.queue), message(Queue Error Event ) Any ideas?  (Read 8637 times)

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

Jay

  • Guest
Does any one have any idea on this error. I am trying to use Queue_call command to route point on the switch.


[2008/05/21 19:37:32.020] 1F60 VxmlUtil.cpp:3903 C=12:L=1:U=321:D=E_12_121 VXML Error: event(error.com.telera.queue), message(Queue Error Event ), element(QUEUE_CALL), current url (RAISE_EXCEPTION)
« Last Edit: May 23, 2008, 04:14:11 AM by victor »

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: error.com.telera.queue), message(Queue Error Event ) Any ideas?
« Reply #1 on: May 21, 2008, 09:57:32 PM »
Jay,

You haven't mentioned GPV deployment mode but in case of "behind" deployment I would suggest you to check IVR TServer log. You should find more information about the error GVP returns during queuing there.

In case of "in-front" deployment mode you should find more detail in PopGateway log. But I'm not 100 % sure about that...

R.

Jay

  • Guest
Re: error.com.telera.queue), message(Queue Error Event ) Any ideas?
« Reply #2 on: May 22, 2008, 09:01:50 AM »
Thanks Rene. If I am not mistaken I did not find any log info in Tserver but let me  double check the logs and get back to you. Big thank you for your suggestions.

Jay

  • Guest
On_hook no ri found for 'xxxxx'
« Reply #3 on: May 22, 2008, 03:15:34 PM »
Hi Rene or any one

I am trying to send the call using 

<QUEUE_CALL USR_PARAMS="GenesysRouteDN:myRoutePointonTheSwitch/>

It is waiting for some time and then it is throwing  error.com.telera.queue), message(Queue Error Event ), element(QUEUE_CALL), current url (RAISE_EXCEPTION) In the Pop gate way logs.


I see the following one in Tserver logs.


09:56:24.408 Int 04543 Interaction message "RequestReleaseCall" received from 372 ("I-Server_750")
(vld_req)+
@09:56:24.4080 [0] 7.5.006.75 send_to_client: message EventError
(Call in invalid state)
AttributeEventSequenceNumber 00000000000005e2
AttributeTimeinuSecs 408000
AttributeTimeinSecs 1211468184 (09:56:24)
AttributeErrorCode 496
AttributeThisDN '61702'
AttributeReferenceID 368
09:56:24.408 Int 04545 Interaction message "EventError" sent to 372 ("I-Server_750")
09:56:24.408 Trc 04542 EventError sent to [372] (00000002 I-Server_750 192.168.218.12:1064)

@09:56:25.5800 link [1]: (len 18) 'RL40PS5.0.J.F'
<< 1 00 10 03 00 00 02 0d 01 00 01 61 7a 20 19 0c 8e 74 3e
CIM: ON_HOOK
OAIMemberID:LineID;UG=1;DIRN=61702
CallID:CPCallID=0c8e743e

on_hook: no ri found for '61702'
@09:56:25.5800 [0] 7.5.006.75 distribute_event: message EventAbandoned

Appreciate your help. Thanks in advance.

Marked as best answer by on November 14, 2024, 09:51:15 PM

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Jay,

Could you post here logs of TServer and IVR TServer capturing an attempt to queue a call? Posted snippet says only the request to drop a call issued by I-Server can't be executed by TServer due invalid call state. Invalid state could mean e.g. call wasn't established yet or something else...

What switch do you have? Is GVP configured in "in-front" or "behind" mode?

R.

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: error.com.telera.queue), message(Queue Error Event ) Any ideas?
« Reply #5 on: May 23, 2008, 12:06:32 PM »
Jay,

Please register on this forum. It allows you sending me personal messages.

René

Offline ivr_genesys

  • Newbie
  • *
  • Posts: 19
  • Karma: 0
Re: error.com.telera.queue), message(Queue Error Event ) Any ideas?
« Reply #6 on: May 27, 2008, 08:47:17 PM »
I am registered. Please send/ping me when you are available.  I have Tserver log available. Thanks for your help.

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: error.com.telera.queue), message(Queue Error Event ) Any ideas?
« Reply #7 on: May 30, 2008, 08:57:32 AM »
Hi,

Sorry for late reply. I missed your post. Is your issue still present or it has been solved somehow? ;)

R.