Skip to main content

Inputs we need from the customer

To integrate your telephony with Ocular's voice agents we need the information on this page. Fill it in and send it to your Ocular Customer Success contact. With everything received, configuration and the joint test take a few days; each missing item usually costs an extra test cycle with your carrier.

Do not send credentials by email or chat. If an option requires credentials (for example, registering Ocular as an extension of your PBX), Customer Success will point you to the secure channel.

1. General information​

ItemExample / formatRequired
Company and project in OcularProject name as shown in the platformYes
Technical contact on your sideName, email, phone, time zoneYes
Technical contact at your carrier or telephony providerName, email, ticket portalYes
Environment to integrateTest / production (or both, with dates)Yes
Countries of the numbersChile, United States, …Yes

2. How you will deliver calls to us​

Choose one option (see SIP URI forwarding into Ocular for the comparison):

  • A. SIP URI forwarding with TLS from your carrier to the SIP URI Ocular will provide (recommended).
  • B. Unencrypted SIP trunk to Ocular's IP.
  • C. Forwarding of your number to a number provided by Ocular.
  • D. Ocular as an extension of your PBX.

For A, B and D we also need the technical sheet in section 4.

3. Numbers​

For each number an Ocular agent will serve:

ItemFormat
Number (DID)E.164: +56 2 xxxx xxxx, +1 xxx xxx xxxx
UseInbound (the end customer calls), outbound (Ocular calls), both
Ocular agent that serves itAgent name in the platform
Service hoursDays and hours, with time zone (example: Monday to Friday 09:00 to 18:00 America/New_York)
Outside service hoursMessage to play and action: courtesy hang-up, forward to a number, voicemail
No agent available (overflow)Wait with music up to N seconds, courtesy hang-up, forward to a number
Identity to present on outbound callsNumber the end customer must see; it must be authorized at your carrier

4. Carrier technical sheet (options A, B and D)​

Ask your carrier or your telephony team for these. They are what delays an integration most when missing.

ItemWhat we needWhy
SIP signaling IP addressesComplete list, per site and per environment, including backupsWe only accept calls from declared sources; an undeclared source is dropped silently
Media (RTP) IP ranges and portsComplete rangesAudio travels on different paths than signaling
Transport and portTLS 5061 (recommended), UDP or TCP 5060Defines the profile we prepare
Does it accept a domain name (FQDN) as destination?Yes / noAllows infrastructure changes without touching your configuration
TLS requirementsVersion, cipher suites your equipment offers, whether it sends SNI, whether it requires a public-CA certificateAvoids encrypted-negotiation failures
SRTP (encrypted audio)Mandatory, optional, unsupported; profileAudio compatibility
CodecsG.711 µ-law (PCMU), G.711 a-law (PCMA), othersQuality and compatibility
Dialed-number formatE.164 with +, 10 or 11 digits, nationalWe normalize on entry, but we must know what arrives
Caller identityWhich SIP header carries the caller's numberIt is what the agent receives as the contact number
DTMFRFC 2833/4733 or otherTones during the call
KeepalivesOPTIONS every N seconds or another mechanismMonitoring
Backup destination (failover)Whether you will configure one and where it pointsAn empty backup turns errors into silence
Evidence available per callCall-ID, SIP code, resolved destinationDiagnosis during tests

5. Transfers to people or other numbers​

If the agent must hand calls to an advisor, a branch or another number (see SIP REFER away from Ocular):

ItemFormat
Destination listPer destination: identifier, display name, E.164 number, type (advisor, branch, help desk), hours when transfer is allowed
ModeConsult (the agent consults and returns to the customer) or handoff (the customer stays with the destination)
What to do if the destination does not answerReturn to the agent, voicemail, courtesy hang-up
Identity to present to the destinationThe end customer's number, your company's or Ocular's
Maximum customer wait timeSeconds
Does your carrier support SIP transfer (REFER) initiated from the receiving side of the call?Yes / no / unknown (we will confirm with your carrier)
ItemDetail
AI agent disclosureText the agent must say at the start, if your country or policy requires it
RecordingWhether calls are recorded, and the notice or consent required
Do-not-call listHow you will deliver and update the numbers that must not be called
Time windows for outbound callsIf you have restrictions stricter than the law
Numbers authorized for testingList of numbers (your team's) we may call during rollout, in writing

7. Joint testing​

ItemDetail
Available windowsDates and times with your team and your carrier online
Numbers you will test fromE.164
Test scriptWhat the person will say, what the agent is expected to do, which transfers to test
Acceptance criteriaWhat must be met to consider the integration complete

8. Integration with your systems (optional)​

ItemDetail
WebhooksURL where Ocular will send call events; must be HTTPS with a valid certificate
Ocular's egress IP addressesIf your firewall requires them, Customer Success will provide them
Per-contact data the agent must knowFields and an example (no real data); we apply minimization: only what is needed

How to send it​

Send this information to your Ocular Customer Success contact. Mark anything you do not know as "pending" and we will proceed with the rest. Customer Success will return, through the secure channel, the destination SIP URI, the Ocular addresses you must authorize at your carrier and the proposed date for the joint test.