" /> C_PERM_DENIED in Avaya - Genesys CTI User Forum

Author Topic: C_PERM_DENIED in Avaya  (Read 5915 times)

Offline victor

  • Administrator
  • Hero Member
  • *****
  • Posts: 1419
  • Karma: 18
C_PERM_DENIED in Avaya
« on: December 13, 2006, 11:31:17 AM »
Advertisement
Hi, all,

I am having problem with Avaya routing here.
We are using URS to route the calls, and from time to time we get C_PERM_DENIED after URS issues a RequestRouteCall.
Interesting thing is that we do not get C_PERM_DENIED everytime a RouteRequest is issued on that RP nor does it depend on destination DN.

What is worse, Genesys received a C_PERM_DENIED and actually interprets it as a successful Route reply, thus URS has no clue that the call actually did not go anywhere and is still stuck on VDN.

Here is a sample of the log:

@13:05:33.8872 [0] Received from 18 (19a0 URS): message RequestRouteCall
        AttributeReferenceID    4538686
        AttributeRouteType      RouteTypeUnknown
        AttributeExtensions    [70] 00 03 00 00..
                'DEFAULT#'      '2200'
                'CUSTOMER_ID'  'Resources'
                'SWITCH'        'Switch_G3r'
        AttributeLocation      'Switch_G3r'
        AttributeOtherDN        '2710'
        AttributeConnID 0092016609fc6272
        AttributeThisDN '2721'
ts->route[CRV=4 <=> CRV=161]->link[1]
** ts6.5.308.01[-1] ** 13:05:33.8876
=== parsed message ===
prot_discr = 8
CRV = 8161
MsgType = 98 (FACILITY)
[color=green][removed MAPD messages were here][/color]
=== parsed message ===
prot_discr = 8
CRV = 115
MsgType = 90 (RELEASE COMPLETE)

Facility:  serv_discr = 17(q932_suppl)  fac_ie = component_tag = A1(INVOKE)
invoke_id tag: 02, value = 212
operation tag: 02, value = 185(RouteEnd)
params = q931_tag = 40
list =
[color=red]Cause:  code_std_loc = 97(ASAI_PubNetLocUsr)  cause = 43(C_PERM_DENIED)[/color]

link[1]->routeCRV[0x0115 <=> 0x0007]->ts
@13:05:22.6367 [0] 6.5.308.01 distribute_response: message EventRouteUsed
        AttributeTimeinuSecs    636737
        AttributeTimeinSecs    1165982722 (13:05:22)
        AttributeReferenceID    4538563
        AttributeCallState      3
        AttributeOtherQueue    '2430'
        AttributeThisQueue      '2430'
        AttributeThirdPartyDNRole      2
        AttributeThirdPartyDN  '2785'
        AttributeOtherDNRole    1
        AttributeOtherDN        '1305'
        AttributeThisDNRole    2
        AttributeThisDN '2430'
        AttributeExtensions    [18] 00 01 01 00..
                'G3Cause'      617
        AttributeCustomerID    'Resources'
        AttributeANI    '1305'
        AttributeDNIS  '2430'
        AttributeUserData      [426] 00 10 00 00..
                'RTargetRuleSelected'  ''
                'RTargetTypeSelected'  '100'
                'RTargetObjectSelected' ''
                'RTargetAgentSelected'  ''
                'RTargetPlaceSelected'  ''
                'RTenant'      'Resources'
                'RStrategyName' 'routing_strategy'
                'RTargetUsed'(list) 'TargetType'        '100'
                                    'TargetName'        ''
ion'    ''      'RRequestedSkills'(list)                'RRequestedSkillCombina
                'CustomerSegment'      'default'
                'ServiceType'  'defaul '
                'ServiceObjective'      ''
        AttributeConnID 0092016609fc626b
        AttributeCallID 2830
        AttributeCallType      2

I know that setting disable-digits-collection to 'true' usually fixes this problem, but I do not understand why it only affects some of VDNs and only some of the calls on those VDNs. Also, what is disable-digits-collection='false' do? Does it mean if I set it to false, I would no longer be able to get caller-entered-digits using CED[] function? ???

Best regards,
Vic

Offline Fra

  • Hero Member
  • *****
  • Posts: 856
  • Karma: -3
Re: C_PERM_DENIED in Avaya
« Reply #1 on: December 13, 2006, 11:40:36 AM »
Victor,

check the COR of the affected VDNs on Avaya.

Disable-digits-collection option enables the collection of digits *after* receiving RequestRouteCall with no impact on any digits
collected previously.

Jason

  • Guest
Re: C_PERM_DENIED in Avaya
« Reply #2 on: July 22, 2008, 08:39:14 PM »
This posting has info on the G3Cause codes you're experiencing. The 617 is a permission issue or feature setting for a station.

Jason

  • Guest
Re: C_PERM_DENIED in Avaya
« Reply #3 on: July 22, 2008, 08:40:19 PM »
Oh yeah, here's the location of the posting....
radiway . com ->Forums -> Genesys -> Framework -> TServer For Avaya G3Cause Codes

Valentine

  • Guest
LXItgXAtyzl
« Reply #4 on: April 08, 2009, 03:56:18 PM »
Extraordinarity: ,