Invalid campaign mode Error code: 11

[G3n35Y5]

We have integrated GVP with outbound. Upon starting the campaign we get "Invalid campaign mode Error code: 11". Following error can be observed in OCS logs:

04:12:24.241 CampaignGroup(181) (Campaign_A@Campaign_A): CampGrMsg: OCS version: 8.1.300.15;  WorkTime: 1;
GroupDBID: 1733; GroupName: Campaign_A;
CampaignDBID: 190; CampaignName: Campaign_A;
Queues: TrunkGroup: CC_TrunkGroup@SIP_Switch(TG);
VoIP ready
Status: Loaded Power GVP
Chains - Created: 1; Deleted: 0;    Records - Created: 1; Deleted: 0;
Group Configuration - Type: AgentGroup/Regular;
Dialers: Active: SIP_Server(951, type 1); PersonalClbk: SIP_Server(951, type 1)
Dialer switch:
04:12:24.954 OCMClient[OCManager]::message received
GSW_CM_MessageType              9 [GSW_CM_ReqStartDialing]
GSW_CM_AttrReferenceID          339
GSW_CM_AttrCampaignID          190
GSW_CM_AttrGroupID              1733
GSW_CM_AttrDialMode            11 [Power GVP]
GSW_CM_AttrOptimizeBy          1 [BusyFactor]
GSW_CM_AttrOptimizeGoal        80
Thirdparty, processing GSW_CM_ReqStartDialing ...
[b]SIPDialer[951]::WARNING: Unknown TrunkGroup (DBID=45765)
04:12:24.954 CampaignGroup(181) (Campaign_A@Campaign_A): ERROR: Required server for this dialing mode 'SIP_Server' in 'Resource not found' state[/b]
GSW_CM_MessageType              27 [GSW_CM_EvError]
GSW_CM_AttrReferenceID          339
GSW_CM_AttrCampaignID          190
GSW_CM_AttrGroupID              1733
GSW_CM_AttrOriginAppID          833
GSW_CM_AttrError                11 [GSW_CM_ERROR_INVALID_CAMPAIGN_MODE]
04:12:24.954 sent to  OCMClient[OCManager]

Upon analysing, we observed error: (DN is not configured in CME) in SIP Server logs.

09:51:34.770 Trc 04541 RequestRegisterAddress received from [24] (00000008 OCS 17.197.120.133:52507)
message RequestRegisterAddress
AttributeThisDN 'CC_TrunkGroup'
AttributeRegisterMode 0
AttributeControlMode 0
AttributeAddressType 1 (DN)
AttributeReferenceID 2147483647
09:51:34.770  -- created: CRequest@7f37a0146680 RequestRegisterAddress-OCS[24]/2147483647
09:51:34.770: $+TLIB:CTI:Unknown:0:0
09:51:34.770 +++ CIFace::Request +++
  -- new invoke
09:51:34.770 Std 36225 Client 8(OCS): registration requested for DN (CC_TrunkGroup) not in CME
  Parsed: RequestRegisterAddress
  From: OCS[24]/2147483647
  Numbers: -<CC_TrunkGroup> -<none>
  Status: parsed:1 queued:0 sent:0 acked:0 preevent:0 event:0 context:0 transferred:0
  -----
@09:51:34.7705 [0] 8.1.101.17 send_to_client: message EventError
(DN is not configured in CME)
AttributeEventSequenceNumber 0000000000000145
AttributeTimeinuSecs 770513
AttributeTimeinSecs 1405331494 (09:51:34)
AttributeErrorCode 59
[b]AttributeErrorMessage 'DN is not configured in CME'[/b]
AttributeReferenceID 2147483647
AttributeAddressType 1 (DN)
AttributeControlMode 0
AttributeRegisterMode 0
AttributeThisDN 'CC_TrunkGroup'
AttributeClientID 8
09:51:34.770 Int 04545 Interaction message "EventError" sent to 24 ("OCS")
09:51:34.770 Trc 04542 EventError sent to [24] (00000008 OCS 17.197.120.133:52507)
  -- processed internally
09:51:34.770 --- CIFace::Request ---
09:51:34.770  -- deleted: CRequest@7f37a0146680 RequestRegisterAddress-OCS[24]/2147483647
09:51:34.770: $-TLIB:CTI:Unknown:0:0

We have checked all configurations. What could be the reason for same?

[Kubig]

Did you configure a Trunk Group DN? Have your campaign gr connection to the SIP server?

[G3n35Y5]

Yes Kubig. Trunk group DN is already created and all options have been set. Campaign group also has a a connection to SIP server. We restarted SIP server many times but the concern does not get resolved even after that.

[Kubig]

Do you see free ports for GVP within SIP or RM logs? Could you post your TG DN configuration?

[locmnvivas]

I met this issue many time. mainly resolved by restart SIP Server. For the newest one, the reason is someone configure SIP Server in tab Connections of Campaign Group (only need connection to SIP at OCS application). Remove it and i was fine then.

[Kubig]

You are not right - your configuration is useful for pure VoIP Outbound solution, but in case when you have other campaign mode then VoIP, you have to set connection to the SIP on campaign object level. From my point of view, it is configuration mistake and not related as SIP server bug.

[locmnvivas]

Hi
You are correct. I have met this issue again last week. Checking the log of Outbound, it showed that MSML was not available.
So I guess this is the issue of Trunk Group registered with SIP Server. I waited for about 10 mins and restart the campaign, worked fine.

[abdel]

I had the same issue, but in my case all was working fine, suddenly when I restarted the compaign, I had encountred that error, I had to restart the Resource Manager.