Sign in Get started

Setting up a FusionPBX gateway: adding a SMS Conecta number

Updated 2026-09-30 · By the SMS Conecta team (SMSConecta Inc.)

Short answer: A SIP trunk goes by the name gateway in FusionPBX. Open Accounts > Gateways, click Add, and enter your SMS Conecta SIP username and password, sip.smsconecta.com as the proxy, Register set to true, and the external profile. Save, start the gateway, then add an inbound route for your number plus an outbound route using that gateway.

FusionPBX serves as a web interface over FreeSWITCH, so gateways, routes and codecs all live inside the GUI. The setup below relies on registration using SMS Conecta's per-number credentials.

What you need first

  • A SMS Conecta number along with the SIP username and password from its dashboard page.
  • FusionPBX admin or superadmin access, plus the domain you want this number ringing into.
  • Firewall rules permitting SIP to sip.smsconecta.com on 5060 (or 5061 for TLS) and FreeSWITCH's RTP range.

Settings to enter

SettingValue
SIP server / registrar / domainsip.smsconecta.com
Transport and portUDP or TCP 5060; TLS 5061
Username<SIP_USERNAME> (from the number's page in the dashboard)
Password<SIP_PASSWORD> (from the same page)
AuthenticationDigest (username + password), registration based
CodecsG.711 µ-law (PCMU) and G.711 A-law (PCMA)
DTMFRFC 2833 (RTP events) or SIP INFO
Inbound DID<YOUR_NUMBER> in E.164 format

Step-by-step: adding the gateway

Field names here follow FusionPBX's own documentation for Gateways as of September 2026.

  1. Sign in to FusionPBX, open the Accounts menu, and select Gateways.
  2. Click Add.
  3. Gateway: give it a name like smsconecta. Username: <SIP_USERNAME>. Password: <SIP_PASSWORD>.
  4. From User: <SIP_USERNAME>. From Domain and Proxy: sip.smsconecta.com. Realm can either stay blank or get set to the same host.
  5. Register: true. Expire Seconds: leave at its default unless support says otherwise.
  6. Context: public. Profile: external. Enabled: true.
  7. Under advanced options, set Register Transport to udp (or tls, with the proxy on port 5061), and Codec Preferences to PCMU,PCMA if that field is shown.
  8. Save, then click Start on the gateway list and confirm it shows as registered (REGED).

Inbound route: routing your DID to a destination

Go to Dialplan > Inbound Routes (Destinations on newer builds) and add a route whose destination number matches your SMS Conecta number. Point it toward an extension, ring group, IVR or call center queue within the right domain.

Since the gateway uses the public context, the route needs to match the number exactly as it arrives. Check the FreeSWITCH log or a test call's CDR entry for the format, whether or not it carries the plus sign.

Outbound route and caller ID

Open Dialplan > Outbound Routes, select the smsconecta gateway, and either pick or write a dial pattern, international numbers dialed with a leading plus, for example.

Set the outbound caller ID number, whether on your extensions or the route, to your SMS Conecta number, matching it to whichever number the gateway registers with. Outgoing calls draw against the number's 1,000 included minutes monthly.

Multiple numbers or multiple tenants

Every SMS Conecta number carries its own SIP username and password, so each number becomes its own gateway. Name them clearly, smsconecta-us-sales and smsconecta-gb-support for example, keeping outbound routes and logs easy to read.

In a multi-tenant FusionPBX, build the gateway inside the domain that will use it, or set it up as a global gateway if several domains need to dial out through it. Inbound routes always tie to one domain, so a single DID rings inside exactly one tenant.

Testing the gateway

  1. In Status > SIP Status (or via the fs_cli command sofia status gateway smsconecta), confirm the gateway state reads REGED.
  2. Call your SMS Conecta number from a different phone and confirm the inbound destination rings with two-way audio.
  3. Press digits in an IVR to verify DTMF, then place an outbound call and check what caller ID the other side sees.

Troubleshooting

  • Gateway shows FAIL_WAIT or keeps retrying: usually 401/403 from incorrect credentials. Re-copy them from the dashboard and restart the gateway.
  • Registered, yet inbound calls go nowhere: either the inbound route number doesn't match the arriving DID, or it was built in a different domain.
  • One-way audio: set the external RTP and SIP IP variables to your public address, forward the RTP range, and disable SIP ALG on the router.
  • Calls rejected for codec reasons: confirm PCMU and PCMA are allowed on both the external profile and the gateway.
  • IVR digits go unrecognized: use RFC 2833 DTMF, FreeSWITCH's default, with SIP INFO as the fallback.

Frequently asked questions

Is a FusionPBX gateway just a SIP trunk by another name?

Yes. FusionPBX refers to the connection with a SIP provider as a gateway; it performs the same role as a trunk would in other PBX systems.

Should Register be set to true or false?

True. SMS Conecta authenticates every number by username and password, which depends on registration.

Which SIP profile is the right one for the gateway?

The external profile, which is what FusionPBX designed for provider connections.

Can one SMS Conecta number be shared across several FusionPBX domains?

A number only has one set of credentials, so register it once and route it to a single domain; use separate numbers for separate tenants.

Is there a monthly cap on minutes?

Each number comes with 1,000 outgoing minutes and 500 outgoing SMS a month, plus unlimited incoming calls and SMS.

Related pages

Get a number in these countries

Sources