Skip to content
CLIRoutes

Integration · PBX & softswitch

Issabel setup for CLIRoutes

Issabel is a community fork of Elastix built on Asterisk with a FreePBX-derived interface. Most installs still use chan_sip trunks, configured as a block of peer details. This guide covers Issabel 4 and 5.

Tested on
Issabel 4 / 5 · Asterisk 13–16
Channel driver
chan_sip
Auth
IP or registration string
Signalling
sip.example-carrier.net:5060 UDP
Codecs
ulaw, alaw, g729

Before you start

  • Issabel admin access.
  • NAT settings in PBX → Settings → Asterisk SIP Settings with your external IP and local networks.
  • Your public IP on the CLIRoutes endpoint, or SIP credentials.

Placeholders in angle brackets, such as <ACCOUNT_ID>, come from your portal. The host shown is a placeholder; use the one listed under Portal → Network.

Set up Issabel

  1. 01

    Add a SIP trunk

    Go to PBX → PBX Configuration → Trunks → Add SIP Trunk. Set Outbound CallerID to an authorised number and Maximum Channels to your endpoint channel limit.

  2. 02

    Enter peer details

    Under Outgoing Settings, set the trunk name to cliroutes and paste the peer details. Remove the credential lines for IP authentication.

    PEER Details
    host=sip.example-carrier.net
type=peer
username=<ACCOUNT_ID>
secret=<SIP_PASSWORD>
fromuser=<ACCOUNT_ID>
fromdomain=sip.example-carrier.net
insecure=port,invite
disallow=all
allow=ulaw&alaw&g729
dtmfmode=rfc2833
qualify=yes
nat=force_rport,comedia
sendrpid=pai
context=from-trunk
  3. 03

    Add the registration string (credentials only)

    Paste the registration string so Issabel registers to us and can receive DID calls.

    Register String
    <ACCOUNT_ID>:<SIP_PASSWORD>@sip.example-carrier.net/<ACCOUNT_ID>
  4. 04

    Create the outbound route

    In Outbound Routes, add patterns 00|X. and +|X., select the cliroutes trunk and save. Click Apply Config at the top of the page.

  5. 05

    Open the firewall and test

    In Security → Firewall, allow SIP and RTP from the CLIRoutes ranges listed in the portal. Then check PBX → Tools → Asterisk CLI with sip show peer cliroutes and place a test call.

Issabel-specific notes

  • Fail2ban on Issabel can ban our signalling IPs after repeated 401 challenges during setup; whitelist the range before testing.
  • Issabel 5 can use PJSIP. If you switch, follow the Asterisk PJSIP guide for object names and keep the same outbound route.
  • Set CID Options to *Force Trunk CID* when all calls should present one authorised number.

Troubleshooting

SymptomLikely causeFix
403 ForbiddenSource IP not allow-listed, wrong credentials, or caller ID not authorisedCheck Portal → Endpoints and Caller IDs
484 Address IncompleteNumber sent in national format or with a leftover prefixSend country code + number, no + or 00
One-way or no audioNAT not handled or RTP blockedSet external address, open the RTP range

Last verified by the CLIRoutes routing team. Menus can change between releases; if a field has moved, tell us.

FAQ

Issabel questions

Can’t find what you need? Our routing team answers within the hour, around the clock.

Is Issabel still maintained?

Issabel is community maintained. It works well with CLIRoutes, but for new deployments consider FreePBX 17 or plain Asterisk on a supported OS.

Can I use the Issabel call center module with CLIRoutes?

Yes. The call center module dials through outbound routes, so it uses the same trunk and caller ID settings.

Why does the peer show UNREACHABLE?

Usually the firewall or Fail2ban is blocking our OPTIONS replies. Whitelist our ranges and run `sip reload`.

Which context should inbound calls use?

Use `from-trunk` (or `from-pstn`), then create inbound routes for each DID.

Ready to connect Issabel?

Open an account to get your endpoint, credentials and authorised caller IDs.

Open account