Carrier and SIP Trunk Issues

Fix calls that do not reach the agent or do not go out: trunk connection and routing, number format, caller ID and carrier rules.

Showing instructions for Xebit VoiceCloud.Showing instructions for Xebit VoiceKit, on your own infrastructure. Switch with the selector at the top. Updated 22 October 2026.

Xebit does not sell or provide phone numbers. Your numbers live on your own SIP trunk with your own carrier, and Xebit connects to that carrier or your SBC over standard SIP. So when calls do not arrive, do not go out, or show the wrong caller ID, the fix is usually in your trunk, your routing or your carrier's rules. This page walks through what to check on each side.

How calls flow

  • Inbound: a caller dials a number on your trunk. Your carrier or SBC sends the call to Xebit, and Xebit routes it to the agent you assigned.
  • Outbound: the agent places a call through Xebit, which sends it out over your trunk. Your carrier connects it and presents your caller ID.

See Audio Bridge for the protocols Xebit speaks.

First checks

  • Sign in to the Xebit VoiceCloud dashboard at voice.xebit.ai and check the trunk connection and the numbers routed to each agent.
  • Sign in to the Xebit VoiceKit admin console on your own host and check the trunk connection and the numbers routed to each agent.
  • Open the calls list and look at the dispositions of affected calls. A call that never appears at all did not reach Xebit.

Inbound calls not reaching the agent

  • Is the trunk connected? Check the trunk is registered or connected to Xebit and not showing errors.
  • Does your carrier route the number to Xebit? The inbound route for the number on your carrier or SBC must point at Xebit. If calls never show up in the calls list, this is the most likely cause.
  • Is the number routed to the right agent? Check which agent the number is assigned to in Xebit.
  • Is the agent live and within its hours? See Agent Not Responding.
  • Does a test call work? If the agent answers a test call but not real calls, the problem is routing.

Outbound calls not going out

  • Is the trunk up? If your carrier rejects the call, it shows as failed to connect.
  • Is the destination allowed? Some trunks are restricted to certain countries or number types. Ask your carrier.
  • Is the trunk at its channel limit? Your carrier caps how many calls the trunk carries at once. Campaign pacing above that limit will fail.
  • Are the contact numbers valid? See the number format section below.

Wrong caller ID on outbound calls

Caller ID is set on your trunk and by your carrier, not in Xebit.

  • Check the number you want to present belongs to your trunk.
  • Ask your carrier whether they override or reject caller IDs that are not on the account.
  • Check any regional registration rules your carrier applies to business caller IDs.

Contact numbers showing as invalid

Numbers must be in E.164 format: a plus sign, the country code and the number, with no spaces, dashes or brackets. For example, +919876543210.

  1. Fix the numbers in your source list.
  2. Re-import the list into the campaign. See Import Contacts.

Network and firewall

Your SBC or carrier must be able to exchange signalling and media with Xebit VoiceCloud. If calls connect but there is no audio, check firewall rules for media traffic. Contact us for the addresses to allow.

On Xebit VoiceKit, your SBC and the Xebit VoiceKit hosts are both on your network. Check firewall rules allow SIP signalling and RTP media between them, and that the hosts handling calls are reachable from the SBC.

Buying numbers, countries and number types

Getting a new number, a number in another country or a different number type is done with your carrier. Once the number is on your trunk, route it to an agent in Xebit.

Still need help?

Email hello@xebit.ai or use the contact page, with the number, the time of a failed call and your carrier's name. For anything on the carrier's side, contact your carrier.

Support is included in your Xebit VoiceKit licence.

Next steps