AI Voice Agents are live on our Tier 2 rails at $0.10 per minute. See the product
Support

Help center

Start with the topic you are stuck on. Everything below points at the documentation, a product page, or a person who can read a packet capture.

The five questions we answer most

If one of these is your problem, you can probably finish without opening a ticket.

  • Calls rejected with a 403. Check the source IP against the trunk allowlist and the From header against a DID on your account. Both are in SIP authentication.
  • DTMF not captured by an IVR. Send RFC 2833 and let us handle the conversion. See DTMF and media.
  • Messages accepted but not delivered. Read the delivery receipt, then check campaign registration. See delivery receipts.
  • A port stalled. Almost always a Customer Service Record that does not match the LOA. See the porting process.
  • An invoice line you cannot place. Every leg carries its own applied rate. See reading a CDR.
An engineer on a headset at a support desk

FAQs

Frequently asked questions

How do I get credentials?

Credentials are issued during onboarding, not from a self-serve signup form. Once your account is opened you get a trunk hostname, either a SIP username and password or an IP allowlist entry, and an API bearer token scoped to your account. Ask for a sandbox token at the same time if you want to build against the API before your first live call.

How long does a port take?

A clean simple port of a local number is typically seven to ten business days from a valid LOA, and a toll-free port is usually faster. Complex ports, partial ports, and accounts with a mismatched Customer Service Record take longer, which is why we read the CSR before submitting rather than after a rejection. Port state is visible over the API so your own dashboard can show it.

Why is my outbound call getting a fast busy or a 403?

The usual causes are an IP that is not on the trunk allowlist, a From header that does not match a DID on your account, a destination outside your allowed prefix set, or a spend cap or velocity limit that has been hit. Send us the SIP Call-ID and the timestamp and we will tell you which one it was.

My SMS is sending but not arriving. What do I check first?

Check the delivery receipt rather than the send response: a 202 on send only means we accepted the message. Then check whether the campaign is registered and active for the use case you are actually sending, whether the destination carrier has throughput limits below your send rate, and whether the recipient is in a STOP state on that number. Unregistered or mismatched traffic gets filtered quietly, not rejected loudly.

Can I get a SIP trace for a specific call?

Yes. Signaling and media captures are available on request for any call ID. Email contact@solvedtele.com with the call ID, a timestamp, and the destination, and you get the capture rather than a summary of it.

How do I raise my messaging throughput or channel count?

Channel counts on a SIP trunk are raised by request and take effect without a rebuild. Messaging throughput is a function of your 10DLC brand and campaign vetting score, so raising it means resubmitting vetting rather than changing a setting on our side. We prepare and submit the packet with you.

Where do I see what I have been charged?

Every leg carries the route, the carrier, the duration, and the rate that applied, so an invoice line reconciles against CDRs rather than against a monthly total. Pull CDRs over the API or have them exported to S3, Google Cloud Storage, or an endpoint you name, hourly or daily.

What counts as an emergency?

Anything blocking production traffic: calls failing on a route, registration dropping, messaging stopped, or the API returning errors across the board. Call +1 (866) 415-6192 for those. Configuration questions, quotes, and porting scheduling go to contact@solvedtele.com and are worked on the normal queue.

Something else? Contact us

Did not find it?

Send the call ID and the timestamp. We would rather read your trace than guess.