Author Topic: Salesforce connector via MiCC and Nu-Point call events  (Read 1213 times)

Offline mjkadel

  • New Member
  • *
  • Posts: 4
  • Country: us
  • Karma: +0/-0
    • View Profile
Salesforce connector via MiCC and Nu-Point call events
« on: July 20, 2020, 01:52:39 PM »
Hi all,

We're still trying to roll out our new Mitel phone system with the help of a contractor. We have a MiCC server which acts as the Salesforce connector. The ACD users log into the CTI Softphone on their Salesforce homepage. Theoretically when somebody calls our ACD queue it should open a Salesforce case and fill in the account and contact fields automatically. When calls come in they first land in Nu-Point so the caller can navigate a call flow before ending up in the ACD queue.

There are always multiple call events in the .js logs in Salesforce. When the first call event contains the caller's phone number the integration works great. When the first call event contains the Nu-Point extension the integration does not work. If we aim the call directly at the queue, bypassing Nu-Point, the integration always works.

Does anyone know of a way to filter out the Nu-Point call events from being passed on to Salesforce through MiCC?

Thanks,

Michael


Offline johnp

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 2202
  • Country: us
  • Karma: +66/-0
    • View Profile
Re: Salesforce connector via MiCC and Nu-Point call events
« Reply #1 on: July 21, 2020, 06:11:01 PM »
You will likely need a delay for the dnis to become valid and reliable

Offline warlockcode

  • New Member
  • *
  • Posts: 3
  • Country: au
  • Karma: +0/-0
    • View Profile
Re: Salesforce connector via MiCC and Nu-Point call events
« Reply #2 on: July 22, 2020, 09:13:46 PM »
Try modifying the COS of the NuPoint ports to display the external number rather than the NuPoint extension.


 

Sitemap 1 2 3 4 5 6 7 8 9 10