FAQ

How do I configure an IXICA SIP trunk and multiple DIDs in Yeastar?

IXICA · YEASTAR VOICE SETUP FAQ

How do I configure an IXICA SIP trunk and multiple DIDs in Yeastar?

Connect your IXICA SIP trunk to Yeastar, add your telephone numbers, and route each number to the right user or team.

Applies to: Yeastar P-Series Cloud Edition, using a registration-based IXICA trunk. Yeastar’s IXICA listing identifies this edition and links to the P-Series registration-trunk guide. Other P-Series editions and S-Series may have different menus or settings; do not treat these instructions as an S-Series procedure. This guide covers voice calling only.

Before you begin

  • Sign in to the Yeastar PBX web portal with permission to manage trunks and call routes.
  • Have your IXICA SIP username, password, authentication name, assigned DIDs and any account-specific connection instructions ready.
  • Use 11-digit IXICA voice numbers: country code 1 plus the ten-digit number, with no leading “+”, spaces, brackets or hyphens. Example: 14165551212. All example numbers in this guide are illustrative, not account values.
  • Identify or create the intended destination extensions, IVRs, ring groups and queues before assigning incoming calls.
  • For an existing live installation, record the current settings and plan changes with your administrator.

Sources: Yeastar’s IXICA provider listing and P-Series registration-trunk guide. The 11-digit IXICA format is supplied for this FAQ by IXICA.

Step 1 — Add a trunk and select the IXICA template

  1. Go to Extension and Trunk → Trunk.
  2. Click Add.
  3. Enter a descriptive name, such as IXICA – Main Office (example name).
  4. Under Select ITSP Template, select Canada.
  5. Look for and select IXICA in the ITSP list.
  6. Make sure Trunk Status is set to Enabled.

If IXICA is missing from your list, check template availability for your PBX edition and firmware with your administrator or IXICA. Do not substitute another provider’s template. Yeastar documents a General configuration option, but manual configuration requires the correct IXICA connection values.

Step 2 — Enter the SIP registration details

Review the template’s connection settings, then enter your own IXICA account values.

Yeastar field What to enter or check
Trunk Type Register Trunk for the registration-based service covered here.
Username Your IXICA SIP registration username.
Password The password for that SIP account.
Authentication Name The authentication name supplied by IXICA. If IXICA confirms that it is the same as Username, enter the same value.
Hostname/IP, Port, Domain and Transport Retain the IXICA template values unless your provisioning instructions require different values. Complete any account-specific or unfilled fields using IXICA’s instructions.
Enable Outbound Proxy Enable and configure only if IXICA instructs you to use an outbound proxy; use the supplied address and port.
  1. Check that all credentials were copied without unwanted spaces.
  2. Click Save, then Apply.
  3. Check the trunk’s Status and confirm that it registers successfully.
Keep SIP credentials distinct from telephone numbers. Do not replace Username or Authentication Name with a DID unless IXICA specifically supplied that DID as the credential. The 11-digit rule applies to your voice numbers, not to arbitrary account usernames. Server addresses, passwords and ports are not provided in this FAQ.

Reference for Steps 1–2: Yeastar registration-trunk setup.

Step 3 — Add all DIDs to the trunk

A DID is a direct telephone number. If IXICA delivers several DIDs through one trunk, add the numbers to that trunk rather than creating a duplicate trunk for every number.

  1. Return to Extension and Trunk → Trunk and edit the IXICA trunk.
  2. Open DIDs/DDIs and click Add.
  3. For an individual number, choose Create Method → Single DID.
  4. In DID/DDI, enter your assigned number in 11-digit format, for example 14165551212, without a leading “+” or punctuation.
  5. Optionally enter a DID/DDI Name, such as Sales or Support, to help identify the number on incoming calls.
  6. Click Confirm and repeat for each additional DID.
  7. For a consecutive block that is entirely assigned to your service, you may instead select DID Range and enter the first and last numbers in 11-digit format. Do not use a range that includes numbers you do not own.
  8. Click Save and Apply.
Important for registration trunks: Yeastar states that DIDs differing from the SIP authentication name must be added to the trunk, or incoming calls through that trunk can fail. Adding a DID in Yeastar does not order or activate that number with IXICA; it must already be assigned and delivered to your service.

Reference: Configure DID Numbers on a Trunk.

Step 4 — Create an inbound route for each destination

  1. Go to Call Control → Inbound Route and click Add.
  2. Enter a descriptive route name, such as IXICA – Main Number (example name).
  3. Under Trunk, select the IXICA trunk.
  4. In the DID Pattern section, set DID Matching Mode to DID Pattern.
  5. Click Add under the DID patterns and enter the exact 11-digit DID for this route, for example 14165551212.
  6. Leave Caller ID Pattern blank unless you intentionally want to restrict which callers can use the route. This field matches the calling number; it is not where you enter the DID being called.
  7. Choose the desired Default Destination, such as an extension, IVR, ring group or queue.
  8. If required, configure Time Condition and the relevant destinations for business hours and after hours.
  9. Click Save and Apply.
  10. Repeat for DIDs that need different destinations. Several exact DID patterns can share one route when they should reach the same destination.

Example routing plan — replace the placeholders

DID placeholder Example route name Example destination
[MAIN DID] IXICA – Main Main IVR
[SALES DID] IXICA – Sales Sales queue
[SUPPORT DID] IXICA – Support Support ring group
[DIRECT USER DID] IXICA – Direct User Individual extension

Replace each placeholder with a real DID assigned by IXICA, in 11-digit format. The destination names above are examples, not required names.

Optional: direct mappings for many extensions

Yeastar also documents DID Number to Specific Extension for individual one-to-one mappings and Match DID Range to Extension Range for consecutive number blocks. For range mapping, the DID range and extension range must contain the same number of entries. Use these modes only when they fit your numbering plan; separate exact-DID routes are easier to review for a small mixed set of users and teams.

Reference: Route Inbound Calls based on DID Numbers.

Step 5 — Configure the outbound route

  1. Go to Call Control → Outbound Route and click Add.
  2. Name the route and configure the Dial Patterns for the numbers users are allowed to call.
  3. Select the IXICA trunk for the route.
  4. Select the extensions or extension groups allowed to use the route, and configure role or time restrictions where applicable.
  5. Set digit stripping and prefix addition as needed so standard Canadian/US destination numbers are sent in 11-digit format, without a leading “+”. Do not apply the ordinary-number format indiscriminately to international or special-number calls; have your administrator handle those separately.
  6. Click Save and Apply.
  7. Review the outbound-route order: Yeastar checks higher-positioned matching routes first.
No mandatory access digit: Yeastar’s general guide demonstrates an outbound access prefix of 8 with one digit stripped. That is an example, not an IXICA requirement. Use the dialling plan chosen for your organisation.

Reference: Yeastar outbound-route instructions.

Step 6 — Review outbound caller ID

  1. Edit the IXICA trunk and review its Outbound Caller ID settings.
  2. Use only caller ID numbers authorised for your IXICA service, in the required 11-digit voice format.
  3. If users need different outbound numbers, review Yeastar’s per-extension caller ID options with your administrator rather than assuming that inbound DID routing assigns the outbound identity.
  4. Save and apply any changes, then check the displayed number on a real outbound call.

Outbound caller ID requires support from the trunk provider. Incorrect caller ID settings can prevent calls from completing. Do not change advanced SIP-header parameters without a specific IXICA instruction or analysis by your administrator.

Reference: Yeastar SIP Trunk Settings — Outbound Caller ID and SIP Headers.

Step 7 — Test the trunk and every number

  • Registration: Confirm that the IXICA registration trunk is connected.
  • Inbound calls: Call every DID from an external telephone and confirm its intended destination.
  • Hours: Test business-hours and after-hours destinations if configured.
  • Outbound calls: Test from every relevant extension or group and verify the number shown on the receiving telephone.
  • Audio and handling: Confirm two-way audio, hold, transfer and IVR digit recognition where used.
  • Record results: Note any failed test’s time and timezone, direction, calling number, called number and error message.

This is a recommended acceptance checklist, not confirmation that a live IXICA/Yeastar installation has been tested.

Common questions and troubleshooting

Do I need a separate trunk for every DID?

No, not when IXICA delivers those DIDs on the same trunk. Add them under DIDs/DDIs, then create the inbound routes. Follow IXICA’s service design if separate trunks or accounts were provisioned.

Why does the trunk register, but incoming calls fail?

Check that the called DID is listed on the trunk, especially when it differs from the authentication name. Check that an inbound route selects the IXICA trunk, matches the exact 11-digit called number and points to a valid destination. Review any Caller ID Pattern restrictions.

Why do several DIDs reach the wrong destination?

Compare each route’s DID patterns, selected trunk, destination and time condition. Check for overlapping patterns or broad routes that may be capturing calls. Use exact-number routes while troubleshooting.

What if the DID still does not match?

Ask your administrator to inspect the called number in the incoming SIP request and compare it with the saved DID. Yeastar’s Get DID From setting determines which SIP header supplies the DID. Do not guess a header or change it at random; retain the template value unless packet analysis or IXICA’s instructions show a change is needed.

What if outgoing calls fail?

Check the route’s dial patterns, allowed extensions, selected trunk, route order, number transformation and authorised caller ID. Confirm that the trunk is registered. If the problem persists, send IXICA support the failed call details and relevant error, without exposing SIP passwords or other private credentials.

Troubleshooting references: trunk DID requirements, DID routing and SIP trunk settings.

Final checklist

  • Correct edition confirmed; IXICA template selected and trunk enabled.
  • SIP credentials entered and registration successful.
  • All assigned DIDs added in 11-digit format without a leading “+”.
  • Inbound routes and any time conditions saved and applied.
  • Outbound route permissions, dialling format and caller IDs reviewed.
  • Every DID, outbound calling, two-way audio and normal call handling tested.

Prepared 18 November 2026 from the official Yeastar documentation linked above. This guide uses P-Series Cloud Edition as its documented baseline. Connection values must come from IXICA’s provisioning instructions. Interface labels and available features can vary with edition and firmware. All bracketed DID fields must be replaced with the customer’s assigned numbers; no account credentials are embedded.

Share

Back to all FAQ answers