Skip to main content

TAS — Telephony Application Server

The TAS (Telephony Application Server) is the IMS application server that delivers the subscriber's telephony experience. It handles call control and supplementary services (call forwarding, barring, waiting, hold and the rest), runs conferences, takes and plays back voicemail, records CDRs for every call, resolves routing and number translation, and talks to the OCS over Diameter so that calls are charged in real time. Where the CSCF decides how a call is signalled, the TAS decides what the service does. OmniWeb surfaces its live calls, subscriber registrations, gateways, Diameter peers and configuration on one element page; call‑volume and trend charts live on the Grafana dashboards reached from the same page.

← Operations Guide

The TAS is a per‑instance element page reached from the sidebar when one runs in the site's inventory. All traffic goes through the OmniWeb backend proxy to the TAS's API, so it stays behind the single authenticated gateway. The documentation link in the page header (the in‑context help button) opens this page. It is organised into tabs.

Overview​

The TAS overview dashboard — active calls, registered subscribers, conference and voicemail counts, Diameter and gateway health, licence status and recent activity

The landing tab is a single‑screen health read for the application server: the number of active calls, registered subscribers, running conferences and stored voicemail records, the health of the Diameter peers and SIP gateways, and the licence status. It is the fastest way to confirm the TAS is up and carrying traffic.

Active Calls​

The Active Calls tab listing calls currently in progress with the parties, direction, state and duration

Every call currently in progress, each row showing the calling and called parties, the direction, the call state and its duration. Selecting a call opens its detail so you can see how a specific call is legged and where it sits in the dialplan — the first place to look when a subscriber reports a call in trouble right now.

CDR​

The CDR tab listing completed call detail records with parties, start time, duration and disposition

The call detail records the TAS has written — one row per completed call, with the parties, start time, duration and disposition. Open any record for its full detail. CDRs are the accounting and after‑the‑fact troubleshooting trail: use them to confirm a call happened, how long it ran and how it ended.

Subscribers​

The Subscribers tab listing subscriber registrations known to the TAS with identity, state and contact

The subscriber registrations the TAS knows about, each with the subscriber identity, registration state and current contact. Open a subscriber for the full registration detail. This is where you confirm a subscriber is registered to the application server before chasing why a service is not working for them.

Diameter​

The Diameter tab showing the TAS's Diameter peers and their connection state

The Diameter peers the TAS connects to — including the path to the OCS for charging and the HSS for user data — with each peer's hostname and connection state. Open a peer for its detail. When charging or subscriber lookups fail, this tab is where you confirm the underlying Diameter paths are up.

Gateways​

The Gateways tab listing SIP gateways and their registration/connection status

The SIP gateways the TAS uses to reach other networks and trunks, each showing its name and current status. Open a gateway for its detail. Use this tab to confirm the interconnect gateways are registered and available before diagnosing failed off‑net calls.

Conferences​

The Conferences tab listing active conferences and their participants

The active conferences and their participants. Open a conference to see who is in it, and act on it in place — lock or unlock the bridge, kick a participant, turn video on or off, or destroy the conference entirely. This is the operator's live control over a running bridge.

Voicemail​

The Voicemail tab listing stored voicemail records per subscriber

The stored voicemail records, per subscriber. Each record can be deleted individually — for example to clear a message left in error or to free a full mailbox.

OCS Test​

The OCS Test tab listing active online‑charging sessions with the option to terminate one

The active OCS (Online Charging System) sessions the TAS is holding, so you can see which calls are drawing against a real‑time balance. An individual charging session can be terminated from here — useful for clearing a session that has stuck open after its call has gone.

Routing​

The Routing tab listing the dialplan templates the TAS routes calls against

The dialplan templates the TAS routes calls against. The list shows each template; open one to read its content. This is the reference for how numbers are matched and where calls are sent — read it alongside the Number Translation tool to confirm a given number routes as intended.

Configuration​

The Configuration tab listing the application configuration the TAS is running

The application configuration the TAS is running, grouped by application. Open an entry to read its settings. This is the read reference for confirming the server is configured as expected without leaving OmniWeb.

Prompts​

The Prompts tab listing the TTS prompt recordings and their status

The text‑to‑speech prompt recordings the TAS plays to callers — the announcements and menu prompts — with the status of each. Use this tab to confirm the expected prompts are present and rendered.

Tools​

Alongside the tabs above, the TAS page carries a set of on‑demand tools for validating routing and subscriber data. Each takes a small form, runs the request against the application server through the OmniWeb proxy, and shows the result in place.

Call Simulator​

The Call Simulator tab — a form for source and destination numbers with the routing result and dialplan variables shown below, and a separate echo‑test call action

Places a test call through the TAS to validate routing and media. Enter a destination (and optionally a source number, source IP and a forced disposition), and the simulator walks the call through the dialplan without ringing anyone — it returns the resolved call type (MT, MO or emergency), the on‑/off‑net decision, every dialplan variable it set, and a step‑by‑step list of processing notes, so you can see exactly how a number would be handled before a real call is placed. The OCS authorisation and HLR lookup can each be skipped to isolate a stage. A separate echo‑test call action rings a destination and loops the party's own audio back, which confirms the live voice path to a handset.

Sh Query​

The Sh Query tab — a form for a public identity and data reference, with the returned Sh user data shown below

Queries the HSS over the Sh interface for a subscriber's user data. Enter the subscriber's public identity and choose the data reference to fetch — from the full repository data to a specific element such as the IMS user state, the serving S‑CSCF name, the initial filter criteria, the MSISDN or the IMSI — and the tool returns the transparent and repository service data the HSS holds. Use it to confirm what the application server sees for a subscriber when a service is not behaving as expected.

HLR Lookup​

The HLR Lookup tab — a form for an MSISDN with the HLR response and resulting dialplan variables shown below

Performs an HLR lookup over SS7 MAP (a Send Routing Information request) to resolve a subscriber's routing and roaming state. Enter the MSISDN in international format and the tool returns the HLR response together with the dialplan variables the result would set on a call. This is how you confirm a number's current network location before diagnosing why calls to it route the way they do.

Number Translation​

The Number Translation tab — a form for country code, phone number and disposition, with the translated number shown below

Tests how a dialled number is normalised and translated by the TAS routing rules. Enter a country code, the phone number and an optional disposition, and the tool returns the translated number the dialplan would use — read it alongside the Routing tab to confirm a given number is matched and rewritten as intended.

ESL​

The ESL tab — a console showing a FreeSWITCH prompt with a command entry field and example commands

An interactive console for issuing FreeSWITCH‑style commands to the TAS engine for diagnostics. Type a command and press Enter — the output is printed back in the console, and Arrow Up/Down recalls previous commands. Example commands such as status, sofia status, show channels and show registrations are offered as one‑click chips. It is the lowest‑level view of the running engine, for confirming live channels, gateway state and registrations directly.

Logs​

The Logs tab tails the TAS's live log output for troubleshooting a single application server without leaving OmniWeb.

Monitoring dashboards​

Call volumes, per‑service counters and other time‑series for the TAS are presented as Grafana dashboards, reached from the element page — OmniWeb does not duplicate those charts natively.

  • The CSCF signals the calls the TAS applies services to — the two together deliver IMS voice.
  • The HSS holds the subscriber and Sh user data the TAS resolves against.
  • The OCS rates and charges the TAS's calls in real time over Diameter.
  • The DRA relays the TAS's Diameter signalling (Sh, Gy) to those peers.
Last updated on