Setting up a Bria SIP account with a SMS Conecta number
Short answer: Getting a SIP account running in Bria means adding a new SIP account under the app's account settings, then entering your SMS Conecta username, password and the domain sip.smsconecta.com. Keep G.711 on and pick either UDP/TCP 5060 or TLS 5061. After it registers, your real number is ready to ring and dial from inside Bria.
Bria, made by CounterPath (now folded into Alianza), is a business-grade softphone for desktop and mobile. Its vendor states paid plans can hold several VoIP service accounts at once, which comes in handy if you run more than one SMS Conecta number.
What you need first
- An active SMS Conecta number plus its SIP username and password.
- Bria installed on your desktop or mobile device (review the vendor's system requirements first).
- A Bria plan permitting you to add your own SIP service account.
Bria account settings
| Setting | Value |
|---|---|
| SIP server / domain / registrar | sip.smsconecta.com |
| Username / auth ID | <SIP_USERNAME> (from the number's page in the dashboard) |
| Password | <SIP_PASSWORD> (from the same page) |
| Transport and port | UDP or TCP 5060, TLS 5061 |
| Codecs | G.711 µ-law (PCMU) and A-law (PCMA) |
| Authentication | SIP digest, per-number username + password |
| DTMF | RFC 2833 (RTP events) or SIP INFO |
| Outbound proxy | Leave empty |
Step-by-step: adding the SIP account
- Sign in to Bria and navigate to its account settings.
- Select the option to add a new SIP account.
- Give the account a recognizable name, then enter <SIP_USERNAME> as the user ID and <SIP_PASSWORD> as the password.
- Enter sip.smsconecta.com as the domain, leaving the outbound proxy field empty.
- Repeat <SIP_USERNAME> in the authorization name field if the app shows one.
- Select your transport (UDP, TCP or TLS) within the account's advanced or topology options.
- Save and turn the account on, then confirm its status reads available or registered.
- Check the codec list to make sure G.711 µ-law and G.711 A-law are both enabled.
When Bria makes sense
Bria targets people handling many calls daily who want a polished interface, contact integration and consistent behavior across desktop and mobile. Being sold as a paid product by its vendor, it tends to draw professionals more than casual users.
The vendor lists certain providers as integration partners, and Bria's setup list may surface those. SMS Conecta isn't among them, so the generic SIP account route covered in the steps above is the one to use; nothing extra is needed.
For only occasional calls, the browser web dialer or a free softphone will likely cover you. Bria justifies its cost once you're shuttling between a desk and a phone all day and want matching account setups on both. Test inbound and outbound calls separately on each device after setup, since office firewall rules can differ from a home network.
Receiving calls
Once Bria registers, calls to your SMS Conecta number show up with answer and decline buttons plus the caller's number. On mobile, allow notifications so incoming calls can still reach you while the app sits in the background. Registering the same credentials elsewhere at the same time can divert inbound calls somewhere else.
Outbound caller ID
Bria pulls the caller ID from whichever account you select for a given call, so it's that account's SMS Conecta number that shows. With several numbers added, choose the account before you dial. Enter destinations with their country code for consistent results.
Troubleshooting Bria
- 401 Unauthorized or 403 Forbidden: the user ID, authorization name or password is incorrect. Re-copy them from the dashboard.
- One-way audio: enable STUN or ICE under the account's network options, or switch to TCP transport to get past NAT.
- No audio once the call connects: likely a codec mismatch; move PCMU and PCMA to the top and switch off the rest while testing.
- DTMF goes unrecognized: set the DTMF method to RFC 2833, or SIP INFO where the other end needs it.
Using Bria with more than one number
Teams often assign each person their own SMS Conecta number and Bria seat, or run separate numbers per country from one person's Bria. Either way, one Bria account maps to one number's credentials. Name each account clearly, say by country and purpose, so it's obvious which caller ID applies when you dial.
For inbound calls, every enabled account can ring simultaneously. Switch off accounts you don't need on a given device so calls land where expected.
Frequently asked questions
Will Bria work with any SIP provider?
Bria is built on standard SIP, and SMS Conecta numbers register the same as any SIP account would. Just confirm your Bria plan permits adding your own service account.
Is SMS Conecta partnered with Bria?
No. There's no partnership between SMS Conecta and Bria's vendor; the app simply connects via standard SIP credentials.
How many SMS Conecta numbers fit in Bria?
Each number occupies its own SIP account. The vendor states paid plans support multiple service accounts, so check your plan's limit.
Why does Bria mark my account as disabled?
The account may have been switched off in settings, or it's failing to register. Turn it on and double-check the credentials.
Is the paid version of Bria required?
Whether you can add your own SIP service accounts depends on the plan; check the vendor's current plan details before purchasing.
Related pages
- all SIP integrations
- SIP dialer overview
- MicroSIP setup
- 3CX integration
- SIP troubleshooting
- caller ID explained
- second number for business
- pricing
- Configuring an Asterisk PJSIP trunk: registering a SMS Conecta number
- Setting up a FreePBX SIP trunk: connecting a SMS Conecta number over PJSIP
Sources
- Alianza/CounterPath: Bria Solo (as of September 2026)