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
| Item | Example / format | Required |
|---|---|---|
| Company and project in Ocular | Project name as shown in the platform | Yes |
| Technical contact on your side | Name, email, phone, time zone | Yes |
| Technical contact at your carrier or telephony provider | Name, email, ticket portal | Yes |
| Environment to integrate | Test / production (or both, with dates) | Yes |
| Countries of the numbers | Chile, 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:
| Item | Format |
|---|---|
| Number (DID) | E.164: +56 2 xxxx xxxx, +1 xxx xxx xxxx |
| Use | Inbound (the end customer calls), outbound (Ocular calls), both |
| Ocular agent that serves it | Agent name in the platform |
| Service hours | Days and hours, with time zone (example: Monday to Friday 09:00 to 18:00 America/New_York) |
| Outside service hours | Message 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 calls | Number 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.
| Item | What we need | Why |
|---|---|---|
| SIP signaling IP addresses | Complete list, per site and per environment, including backups | We only accept calls from declared sources; an undeclared source is dropped silently |
| Media (RTP) IP ranges and ports | Complete ranges | Audio travels on different paths than signaling |
| Transport and port | TLS 5061 (recommended), UDP or TCP 5060 | Defines the profile we prepare |
| Does it accept a domain name (FQDN) as destination? | Yes / no | Allows infrastructure changes without touching your configuration |
| TLS requirements | Version, cipher suites your equipment offers, whether it sends SNI, whether it requires a public-CA certificate | Avoids encrypted-negotiation failures |
| SRTP (encrypted audio) | Mandatory, optional, unsupported; profile | Audio compatibility |
| Codecs | G.711 µ-law (PCMU), G.711 a-law (PCMA), others | Quality and compatibility |
| Dialed-number format | E.164 with +, 10 or 11 digits, national | We normalize on entry, but we must know what arrives |
| Caller identity | Which SIP header carries the caller's number | It is what the agent receives as the contact number |
| DTMF | RFC 2833/4733 or other | Tones during the call |
| Keepalives | OPTIONS every N seconds or another mechanism | Monitoring |
| Backup destination (failover) | Whether you will configure one and where it points | An empty backup turns errors into silence |
| Evidence available per call | Call-ID, SIP code, resolved destination | Diagnosis 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):
| Item | Format |
|---|---|
| Destination list | Per destination: identifier, display name, E.164 number, type (advisor, branch, help desk), hours when transfer is allowed |
| Mode | Consult (the agent consults and returns to the customer) or handoff (the customer stays with the destination) |
| What to do if the destination does not answer | Return to the agent, voicemail, courtesy hang-up |
| Identity to present to the destination | The end customer's number, your company's or Ocular's |
| Maximum customer wait time | Seconds |
| Does your carrier support SIP transfer (REFER) initiated from the receiving side of the call? | Yes / no / unknown (we will confirm with your carrier) |
6. Legal and compliance
| Item | Detail |
|---|---|
| AI agent disclosure | Text the agent must say at the start, if your country or policy requires it |
| Recording | Whether calls are recorded, and the notice or consent required |
| Do-not-call list | How you will deliver and update the numbers that must not be called |
| Time windows for outbound calls | If you have restrictions stricter than the law |
| Numbers authorized for testing | List of numbers (your team's) we may call during rollout, in writing |
7. Joint testing
| Item | Detail |
|---|---|
| Available windows | Dates and times with your team and your carrier online |
| Numbers you will test from | E.164 |
| Test script | What the person will say, what the agent is expected to do, which transfers to test |
| Acceptance criteria | What must be met to consider the integration complete |
8. Integration with your systems (optional)
| Item | Detail |
|---|---|
| Webhooks | URL where Ocular will send call events; must be HTTPS with a valid certificate |
| Ocular's egress IP addresses | If your firewall requires them, Customer Success will provide them |
| Per-contact data the agent must know | Fields 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.