Versions Compared

Old Version 3

changes.mady.by.user Rijnhard Hessel

Saved on

compared with

New Version 4

changes.mady.by.user Rijnhard Hessel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Info

These settings will need to be configured by

...

T|Forge, however understanding them is crucial to getting the most out of your integration, for your particular use case.

The settings here are only a subset of those available, as these are the only relevant ones to Integrators.

Warning

Pay attention to redis_port, redis_db and http_port, as these will be assigned to you and could change, they will be the same for all clients of your integration and should be set at a global level in your application and should be relatively easy to change.

setting

values

default

description

outbound_scope

  • private - only for calls generated by Integrator

  • spy - for calls generated by any integrator

  • global - for all outbound calls

private

determines when a CDR should be sent on an outbound call.

inbound_scope

  • Off - no inbound cdr's

  • global - receive CDR's for all inbound calls

Off

determines when a CDR should be sent on an inbound call.

Note

This is unaffected by inbound queue setup and does not determine inbound call connection notifications.
(Which are determined by queue setup)


redis_port

any valid port number

6379

this will be assigned to an integrator globally (across all Teleforge clients), it should be globally configurable in your application

redis_db

0-16

0

this will be assigned to an integrator globally (across all Teleforge clients), it should be globally configurable in your application

http_port

any valid port number over 8300

8300

this will be assigned to an integrator globally (across all Teleforge clients), it should be globally configurable in your application

http_enabled

On/Off

On

Will the Integrator be using the REST API? Even if using WebRTC, disabling this will prevent recording access.

webrtc_enabled

On/Off

Off

Will the Integrator be using the WebRTC integration route? (this requires additional setup)

random_cli

On/Off

Off

Warning

Deprecated - replaced byverified_cli

IF the client has the random CLID feature then it can be enabled or disabled at an integrator level (send "random" as the outbound_id when making a call)

verified_cli

On/Off

Off

IF the client has purchased a Verified Call product then it can be enabled or disabled at an integrator level (send the campaign name as the outbound_id when making a call)

default_ring

any valid integer (in seconds)

35

the default amount of time to ring the callee before hanging up.

international_calls

On/Off

Off

Are international calls allowed for the Integrator? For security reasons, this is Off by default

country_code

any valid country code

27

The "home" country to assume 0 prefixed numbers belong to

external_agents

On/Off

Off

non-extension to non-extension calls, usually this is if agents are roaming and the PBX is used as a middleman between their cellphone and the client.