" /> Stand-alone Do Not Call management app - Genesys CTI User Forum

Author Topic: Stand-alone Do Not Call management app  (Read 2616 times)

Offline blacklord

  • Newbie
  • *
  • Posts: 30
  • Karma: 0
Stand-alone Do Not Call management app
« on: October 05, 2010, 12:44:01 AM »
Advertisement
Hi all,

Hoping someone may assist here. We're building a stand alone app that can populate and manage the Do Not call List but are running into some issues.

I'm sending the following request to OCS via COMDN but getting an error response. OCS clearly requires a record reference, but this is not documented in the API and we will never have a valid record in the context of what we're trying to build.


Following extract from the OCS log (with number blanked out and server names blanked out)...

received from 65200(TS_xxxxxx)xxx.xxx.xxx:3010(fd=10) message EventUserEvent
        AttributeReferenceID    1
        AttributeCustomerID    'Resources'
        AttributeThisDN 'COMDN'
        AttributeAddressInfoType        8 (AddressInfoAddressType)
        AttributeAddressInfoStatus      99
        AttributeUserData      [166] 00 04 01 00..
                'GSW_CM_MessageType'    32
                'GSW_CM_AttrTargetAppID'        0
                'GSW_CM_AttrOriginAppID'        236
                'GSW_CM_AttrProperties'(list) 'do_not_call'(list) 'GSW_PHONE'  'xxxxxxxxxx'
        AttributeExtensions    [17] 00 01 01 00..
                'status'        -1
        AttributeTimeinSecs    1286176384 (18:13:04)
        AttributeTimeinuSecs    663
        AttributeAddressType    99(Other)
        AttributeEventSequenceNumber    000000000000ecb2
        AttributeUserEvent      EventUserEvent
18:13:04.008 Trc 50002 TEvent: EventUserEvent
18:13:04.009 OCSEvent[2]::EventUserEvent
        TServer[107`TS_xxxxxx]
        DN[181`COMDN]CommunicationDN
{
Thirdparty, processing GSW_CM_ReqDoNotCall ...
Attribute <GSW_RECORD_HANDLE> not found
Attribute <GSW_CHAIN_ATTR> not found
18:13:04.009 Trc 50071 Send UserEvent
request to 65200(TS_ctidev01) message RequestDistributeUserEvent
        AttributeUserData      [140] 00 05 01 00..
                'GSW_CM_MessageType'    27
                'GSW_CM_AttrError'      4
                'GSW_SWITCH_DBID'      101
                'GSW_CM_AttrOriginAppID'        0
                'GSW_CM_AttrTargetAppID'        236
        AttributeCommunicationDN        'COMDN'
..sent to xxx.xxx.xxx:3010(fd=10)
}

And this is the event structure from the Outbound Contact 7.6 Reference Manual...

UserEvent Structure

The following depicts the event structure for T-Server to convey a DNC
request (CM_ReqDoNotCall) from a third-party application:

UserEvent
I
UserData
I
"GSW_CM_MessageType" 32
["GSW_CM_AttrError" 0]
"GSW_CM_AttrOriginAppID" <value=sender’s ID>
"GSW_CM_AttrTargetAppID" <value=receiver’s ID>
"GSW_CM_AttrProperties"
I
"do_not_call"
I
"GSW_PHONE" <value>
["GSW_CUSTOMER_ID" <value>]
["GSW_CHAIN_ATTR" <value>]

In this example, under UserData, the value of GSW_CM_MessageType is 32 for the
request CM_ReqDoNotCall. The value would be 33 for the response/notification
CM_EvDoNotCallProcessed or 27 for the error message CM_EvError, and
“do_not_call” under GSW_CM_AttrProperties would be replaced accordingly by
the proper message types.

cheers,

Lance

Offline René

  • Administrator
  • Hero Member
  • *****
  • Posts: 1832
  • Karma: 62
Re: Stand-alone Do Not Call management app
« Reply #1 on: October 05, 2010, 09:15:16 AM »
Hi Lance,

Based on OCS reply (error message) the request fails because requested campaign is not loaded.

[quote]request to 65200(TS_ctidev01) message RequestDistributeUserEvent
        AttributeUserData      [140] 00 05 01 00..
                'GSW_CM_MessageType'    27
                [color=red][b]'GSW_CM_AttrError'      4[/b][/color]
                'GSW_SWITCH_DBID'      101
                'GSW_CM_AttrOriginAppID'        0
                'GSW_CM_AttrTargetAppID'        236
        AttributeCommunicationDN        'COMDN'
..sent to xxx.xxx.xxx:3010(fd=10)

[b]GSW_CM_AttrError = 4 - CM_ERROR_CAMPAIGN_NOT_LOADED / Requested campaign not loaded.[/b][/quote]

Is there any active = loaded campaign at the moment your app sends the request? If there is no one then the request will fail as OCS stores copy of DNC table in its memory only when a campaign is loaded.

R.

Offline blacklord

  • Newbie
  • *
  • Posts: 30
  • Karma: 0
Re: Stand-alone Do Not Call management app
« Reply #2 on: October 05, 2010, 10:27:03 PM »
That did it! Thanks!