Search results

  1. edossantos

    Call By FileTxt To Extension

    That's not controlled from the CFD app. You can change it from the outbound rule, or from the SIP Trunk settings.
  2. edossantos

    Get transferred extension

    No, unfortunately you can't get that information from the CFD app.
  3. edossantos

    Determining Extension Status Do Not Disturb

    The value for DND is "Out of office".
  4. edossantos

    Call By FileTxt To Extension

    Maybe your SIP Trunk rejects the calls coming from the MakeCall caller ID. You might need to adjust your SIP Trunk settings to take the caller's number from a different place. Or adjust your outbound rule to set an outbound number there.
  5. edossantos

    Session.ani

    Like that you're adding the number before the JSON, that will break the JSON. You need to put it somewhere in the middle.
  6. edossantos

    Session.ani

    Use the Expression Editor to build an expression that concatenates static text with variables.
  7. edossantos

    Call By FileTxt To Extension

    You should keep your existing outbound rule for regular calls from your staff, and then add another rule for calls from CFD apps.
  8. edossantos

    CallFlow Outbound Dialer Not working after upgrade to Version 20.0 Update 0 (Build 1620 Beta)

    Those expressions are wrong. Use the Expression Editor to build the expression, use the logical functions EQUALS, NOT_EQUALS, etc.
  9. edossantos

    Call By FileTxt To Extension

    You need to leave extensions and groups empty in your outbound rule. You can use a prefix if you want.
  10. edossantos

    Call By FileTxt To Extension

    Looks like you're not getting any number from the text file. Calls are started by the MakeCall IVR, which will call the origin first, and then transfer the call to the destination.
  11. edossantos

    Call By FileTxt To Extension

    The C# code is probably checking the status of extensions that don't exist. You should adjust this to your system.
  12. edossantos

    CallFlow Outbound Dialer Not working after upgrade to Version 20.0 Update 0 (Build 1620 Beta)

    The Get Extension Status component also tells you the current profile in property CurrentProfileName. The possible values for this are: Available > "Available" Away > "Away" Do Not Disturb (DND) > "Out of office" Lunch > "Custom 1" Business Trip > "Custom 2"
  13. edossantos

    CallFlow Outbound Dialer Not working after upgrade to Version 20.0 Update 0 (Build 1620 Beta)

    You need to create a condition. In the branch where you want to make calls, you need to set the Condition property to the NOT(MyGetExtensionStatusComponent.IsInCall) expression.
  14. edossantos

    Can't select CFD app extension as a destination in Forwarding Rules

    This will be added in v20 Update 2 as far as I know.
  15. edossantos

    CFD - Match customer record and send email

    CONCATENATE(TranscribeAudio1.RecognizedText,"\n",Validate_ID.CustomerID)
  16. edossantos

    CallFlow Outbound Dialer Not working after upgrade to Version 20.0 Update 0 (Build 1620 Beta)

    You will need to add the logic to check if the agent is busy or not. You can use the Get Extension Status component to do that, which has the IsInCall property that tells you that.
  17. edossantos

    CallFlow Outbound Dialer Not working after upgrade to Version 20.0 Update 0 (Build 1620 Beta)

    If the call is going through a queue now, that's likely to cause issues. The hotfix comes to solve that. Meanwhile, a possible workaround is that you start the calls from each agent extension, and not from the queue.
  18. edossantos

    3CX Database

    3CX uses postgresql internally.
  19. edossantos

    Salesforce User License & Permissions

    No need to use an administrator. Just a user having access to read/create contacts, read leads, read accounts, read users, and create activities.
  20. edossantos

    CFD - Match customer record and send email

    Please check this article about how to send emails with the CFD: https://www.3cx.com/docs/cfd-emails-voice-app/ The subject or body can be expressions. Use the Expression Editor to build an expression for any of those fields (probably the body), concatenating static text with variables.