" /> Routing Issue - Genesys CTI User Forum

Author Topic: Routing Issue  (Read 3057 times)

Offline livinginnj

  • Newbie
  • *
  • Posts: 26
  • Karma: 1
Routing Issue
« on: September 28, 2016, 11:01:26 PM »
Advertisement
Hi i am facing the below issue, Strategy is not executing in the RP 1260955. It is present in Avaya Switch.Any thoughts what is the root cause?

received from 65531(tserv_a)xxenp001:3000(fd=) message EventError
(Invalid origination or destination address)
AttributeErrorMessage 'Invalid origination or destination address'
AttributeReferenceID 23958993
AttributeThisDN '1260955'
AttributeConnID 0079028b99a62661
AttributeCallID 11013
AttributeErrorCode 600
AttributeTimeinSecs 1475101094 (15:18:14)
AttributeTimeinuSecs 650136
AttributeCustomerID 'Resources'
AttributeEventSequenceNumber 0000000002fa5b60

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Routing Issue
« Reply #1 on: September 29, 2016, 02:17:36 AM »
Show the TRoute request and full log

Enviado de meu E6633 usando Tapatalk


Offline livinginnj

  • Newbie
  • *
  • Posts: 26
  • Karma: 1
Re: Routing Issue
« Reply #2 on: September 29, 2016, 02:28:18 AM »
2016-09-28T15:18:14.648  Trace  xxenp001 tserv_a  GCTI-00-04541  RequestRouteCall received from [15] (00000002 urs_a 10.193.x.1:39886)
message RequestRouteCall
AttributeThisDN '1260955'
AttributeConnID 0079028b99a62661
AttributeOtherDN ''
AttributeExtensions [44] 00 02 00 00..
'CUSTOMER_ID' 'Resources'
'SWITCH' 'RB8800'
AttributeRouteType 1 (RouteTypeDefault)
AttributeReason [14] 00 01 01 00..
'RTR' 365
AttributeReferenceID 23958993
2016-09-28T15:18:14.648  Interaction  xxenp001 tserv_a  GCTI-00-04543  Interaction message "RequestRouteCall" received from 15 ("urs_a")
TDN:1260955
IID:0079028B99A62661
ODN:
OPER:36

@15:18:14.6489 [gctmi] Distributing request RequestRouteCall
@15:18:14.6489 [asai] Party [0079028b99a62661:1260955,s809,tRP,rDST,lINT] (reqRouteCall)
TP_AsaiData
FACILITY  CRV:9ca0
Facility: INVOKE
InvokeId: 2
Operation: RouteSelect
CalledNum: (unknown),''
@15:18:14.6490 [>>] 08 00 00 16 08 02 9C A0 62 96 1C 0E 91 A1 0B 02 01 02 02 01 B7 40 03 70 01 80
@15:18:14.6500 [<<] 08 00 00 17 08 02 1C A0 5A 96 1C 0F 91 A1 0C 02 01 02 02 01 B9 40 04 08 02 81 9C
TP_AsaiData
RELEASE_COMPLETE  CRV:1ca0
Facility: INVOKE
InvokeId: 2
Operation: RouteEnd
Cause: C_INVLDNUM
@15:18:14.6501 [asai] (processOperRouteEnd)
@15:18:14.6501 [gctmi] TMsg [EventError()] distributing to model
@15:18:14.6501 [gctmi] Party [0079028b99a62661:1260955,s809,tRP,rDST,lINT] processError
@15:18:14.6501 [gctmi] request RequestRouteCall ctiRefId 40096 removed from reqMgr
@15:18:14.6501 [0] 8.1.001.55 send_to_client: message EventError
(Invalid origination or destination address)
AttributeEventSequenceNumber 0000000002fa5b60
AttributeCustomerID 'Resources'
AttributeTimeinuSecs 650136
AttributeTimeinSecs 1475101094 (15:18:14)
AttributeErrorCode 600
AttributeCallID 11013
AttributeConnID 0079028b99a62661
AttributeThisDN '1260955'
AttributeReferenceID 23958993
2016-09-28T15:18:14.650  Interaction  xxenp001 tserv_a  GCTI-00-04545  Interaction message "EventError" sent to 15 ("urs_a")
IID:0079028B99A62661
TDN:1260955
OPER:52

2016-09-28T15:18:14.650  Trace  xxenp001 tserv_a  GCTI-00-04542  EventError sent to [15] (00000002 urs_a 10.193.x.1:39886)

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Routing Issue
« Reply #3 on: September 29, 2016, 07:07:13 AM »
From my point of view, the OtherDN parameter is missing, respectively has empty value, which means you wanted to route to "null" destination and the PBX declined it. Check your strategy.

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Routing Issue
« Reply #4 on: September 29, 2016, 01:20:14 PM »
Agree with Kubig

Enviado de meu E6633 usando Tapatalk


Offline livinginnj

  • Newbie
  • *
  • Posts: 26
  • Karma: 1
Re: Routing Issue
« Reply #5 on: September 29, 2016, 08:41:56 PM »
We use the same strategy for other Transfer Numbers  it all works. Only for one number it is not working so

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Routing Issue
« Reply #6 on: September 29, 2016, 09:04:39 PM »
So...check your strategy or configuration

Enviado de meu E6633 usando Tapatalk


Offline Tambo

  • Sr. Member
  • ****
  • Posts: 456
  • Karma: 5
Re: Routing Issue
« Reply #7 on: September 30, 2016, 10:24:29 AM »
delete RP and re-create from working one maybe ?!?

Offline Kubig

  • Hero Member
  • *****
  • Posts: 2755
  • Karma: 44
Re: Routing Issue
« Reply #8 on: September 30, 2016, 10:26:44 AM »
[quote]delete RP and re-create from working one maybe ?!?[/quote] Why?? ???

Offline Tambo

  • Sr. Member
  • ****
  • Posts: 456
  • Karma: 5
Re: Routing Issue
« Reply #9 on: September 30, 2016, 10:51:03 AM »
can be corrupt during creation, had it before with route points

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Routing Issue
« Reply #10 on: September 30, 2016, 12:05:33 PM »
RP corrupt? Hummmm could be not monitored and then you force the register again but not corrupt... It is just a DB object which is sent to TServer to ask for a Monitor request to the PBX :S

Enviado de meu E6633 usando Tapatalk


Offline Tambo

  • Sr. Member
  • ****
  • Posts: 456
  • Karma: 5
Re: Routing Issue
« Reply #11 on: September 30, 2016, 12:44:31 PM »
seriously it didn't show as being registered in logs, honestly  ;D

Offline n3vek7

  • Full Member
  • ***
  • Posts: 137
  • Karma: 3
    • ITKB
Re: Routing Issue
« Reply #12 on: September 30, 2016, 02:18:57 PM »
Corrupt, isn't it a generic answer when you don't know what was the problem and you just restarted a service?  ;D
Agree with cavagnaro/Kubig, RP is probably not monitored by TServer and it just doesn't exist. Make sure it is registered.