Dataset · ur-IN · Telephony Speech
Buy a Urdu telephony speech dataset
Speech captured over a real telephony path — a genuine call through the network, not studio audio downsampled afterwards to imitate one. Available for Urdu as a licensed build against your specification, with audio, verbatim transcripts, speaker metadata and consent records.
- Language
- Urdu (Perso-Arabic (Nastaliq))
- Type
- Telephony Speech
- Per speaker
- 10–20 minutes of accepted audio per speaker
- Accepted yield
- 50–60% of recorded time is accepted
How Urdu telephony speech is recorded
Speech captured over a real telephony path — a genuine call through the network, not studio audio downsampled afterwards to imitate one.
Scenario-driven calls between a caller and an agent or IVR flow, each leg recorded separately, across a deliberate spread of handsets and network conditions.
50–60% of recorded time is accepted. Dropped calls, network artefacts beyond tolerance and unusable legs are discarded. Real network conditions are the point of the style and also its main cost.
What is in the package
- 16-bit PCM WAV audio, captured at 48 kHz / 24-bit and delivered at your target rate
- Verbatim Perso-Arabic (Nastaliq) transcripts with utterance-level timestamps
- Call metadata: duration, codec, handset class, carrier, packet-loss events
- Intent label per call and per turn
- DTMF and hold, transfer and barge-in events
- Agent and caller leg identifiers
- Per-speaker metadata: age band, gender, region, dialect, education band, device
- Consent records mapped to speaker IDs and retained for audit
- Speaker-disjoint train / dev / test splits
Specification
| Field | Standard value |
|---|---|
| Language | Urdu (ur-IN) |
| Speech type | Telephony Speech |
| Per speaker | 10–20 minutes of accepted audio per speaker |
| Sample rate | 8 kHz narrowband, matching what a deployed contact-centre model actually receives |
| Codec | G.711 and AMR-NB captured explicitly, with the codec recorded per call in the manifest |
| Legs | Caller and agent recorded on separate legs, never as a mixed call recording |
| Network conditions | Handset type, network carrier and packet-loss events logged per call |
| Dialects covered | Dakhini (Hyderabad), Lucknawi, Dehlvi, Bihari Urdu |
| Recording cities | Hyderabad, Lucknow, Delhi, Bhopal |
| Transcription | Native verbatim, second-pass reviewed |
Quality gates applied to telephony speech
The failure modes this style is prone to: studio audio downsampled to 8 khz and passed off as telephony, which has none of the codec or packet-loss characteristics that matter
- Codec and sample rate verified per file, rejecting any studio audio that has been downsampled to fake a telephony path
- Echo and double-talk checked on both legs
- DTMF events verified against the call log
- Level normalisation applied per leg, since handset output levels vary far more than studio microphones do
Pricing and volumes
| Volume | Indicative range | Delivery |
|---|---|---|
| 50 hours (pilot-scale) | ₹2,10,000 – ₹4,10,000 | 3-4 weeks |
| 250 hours | ₹9,97,500 – ₹19,47,500 | 5-8 weeks |
| 1,000 hours | ₹35,70,000 – ₹69,70,000 | 10-16 weeks |
Bands, not a price list. A signed specification converts them into one fixed figure, and staged delivery lets you start training before the full corpus lands.
Why generic Urdu corpora underperform
Indian Urdu specifically, and Dakhini in particular, are absent from public data dominated by Pakistani Urdu broadcast speech.
Spoken Urdu and spoken Hindi are largely mutually intelligible; the distinction is mainly lexical and orthographic. Decide up front whether transcription is in Nastaliq, Devanagari, or both.
- Right-to-left Nastaliq tooling errors and diacritic loss
- Merged phonemes transcribed by sound rather than by etymology, or vice versa, inconsistently
- Dakhini forms replaced with standard Urdu
Licensing and compliance
- Perpetual, transferable licence covering model training, derivative models and commercial deployment
- Written informed consent from every speaker, retained and auditable
- Compliant with India's DPDP Act 2023 handling requirements and mapped to GDPR obligations for EU buyers
- No scraped, resold or re-licensed third-party audio in any delivery
How buying works
- Send your specification or use the standard one above
- Receive a fixed scope, price and delivery schedule within one working day
- Optional paid pilot of 10-20 hours against the same spec
- Recruitment and recording begin on signature, with staged batches
- Acceptance testing per batch, then final delivery with the full manifest
Frequently asked
Can I buy an off-the-shelf Urdu telephony speech dataset today?
We build to specification rather than reselling a fixed corpus, because off-the-shelf Urdu audio almost never matches a real deployment's dialect mix and noise profile. A 50-hour build ships in three to four weeks.
What licence do we get?
A perpetual, transferable licence with full IP transfer on delivery. You can train, distribute and commercialise models built on the data without further payment.
Can we get a free sample?
Yes — a short sample reflecting the agreed specification is provided before the pilot is signed, so you can check transcript quality and audio characteristics.
Which Urdu dialects are included?
By default Dakhini (Hyderabad), Lucknawi, Dehlvi and others, with quotas set at recruitment. You can weight the mix to match where your product is deployed.
Related pages
Quote this Urdu dataset
Tell us the volume and dialect mix for Urdu telephony speech and you get a fixed price and delivery date.