helix-admin/helix-engage-server
1
0
Fork 0
mirror of https://dev.azure.com/globalhealthx/EMR/_git/helix-engage-server synced 2026-05-18 20:08:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: remove hardcoded Inbound_918041763265 campaign fallback
Some checks failed
ci/woodpecker/push/woodpecker Pipeline failed
Details

Browse Source 
The default campaign name was hardcoded to 'Inbound_918041763265'.
After the Ozonetel campaigns were renamed (Inbound_918041763265 →
Global, Inbound_918041763400 → Ramaiah), agent login/dial would
break because the old name doesn't exist on Ozonetel anymore.

Campaign name now comes exclusively from the Agent entity's
campaignName field (per-agent) or the OZONETEL_CAMPAIGN_NAME env
var (per-workspace). No hardcoded fallback.
This commit is contained in:
saridsa2
2026-04-16 17:33:35 +05:30
parent 2666a10f48
commit 2d8308bed8
1 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
src/auth/agent-config.service.ts
View File

@@ -29,7 +29,11 @@ export class AgentConfigService {
return this.telephony.getConfig().sip.wsPort || '444'; return this.telephony.getConfig().sip.wsPort || '444';
} }
private get defaultCampaignName(): string { private get defaultCampaignName(): string {
return this.telephony.getConfig().ozonetel.campaignName || 'Inbound_918041763265'; // No hardcoded fallback — each Agent entity's own campaignName
// field is the source of truth. Env var is the per-workspace
// default; if neither is set, the Ozonetel login will use
// whatever the agent's entity specifies.
return this.telephony.getConfig().ozonetel.campaignName || '';
} }
async getByMemberId(memberId: string): Promise<AgentConfig | null> { async getByMemberId(memberId: string): Promise<AgentConfig | null> {