Key takeaways
- A call is what people experience. A leg is what a platform controls, meters, and records.
- “A” means first, not caller. On a call your app places, the A-leg is the person you dialed.
- Count legs by flow. An IVR needs one, a forward needs two, and a conference needs one per member.
- On Vobiz, each answered leg is charged separately, so a bridged minute counts on both legs.
- In India, the join matters. Vobiz requires both legs of a domestic call to stay in India, and TRAI’s new A2P rules will cover API-placed calls.
What is a call leg?
A leg is one side of a call as seen by one system in its path. The word is relative, and that explains most of the confusion around it. Cisco’s gateway guide says inbound and outbound call legs are defined from the device’s point of view. So the outbound leg from your platform can be an inbound leg for the next carrier. PortaOne’s billing docs show how this adds up: a call crossing two gateways, from PSTN to internet and back to PSTN, produces four accounting records, which a shared ID ties together. When you build on a voice API, you only count the legs on your own platform. That platform stands between the parties and treats each side as its own connection.Where the term comes from
“Call leg” began as a SIP term. RFC 2543 used it, and RFC 3261 replaced it with “dialog” in 2002, noting that the old name was no longer used in that specification. It also calls a “call” an informal term. The old wording still shows in RFC 3261’s message grammar, which comments status 481 as “Call Leg/Transaction Does Not Exist”. SIP still sends that response when a request names a dialog that no longer exists. The industry kept the word and widened it. Today, “leg” usually means the whole connection and everything attached to it, including its events, record, and cost.A-leg vs B-leg: what is the difference?
The A-leg exists first. The platform creates the B-leg from it to reach someone else. RFC 3261 doesn’t define either label, so these are industry conventions rather than a standard.
The second row is the easy one to get wrong. Vobiz’s Transfer API glosses
aleg as the caller and bleg as the callee, which fits inbound calls. On an API-placed call, the A-leg is the party who received your call, because it’s the original call.
The same words differ between platforms
Check the labels whenever you read another system’s docs or logs. Which party counts as Leg A can change with the flow, and the fields that link legs vary too. This table translates the terms, as each source documented them on November 3, 2026:How many legs does a call have?
The flow sets the count, not the number of people talking. A caller listening to a menu is one leg. Two people talking through a platform are two.- Simultaneous ring creates legs that lose. Vobiz bridges the first answer and cancels the rest. Those report
LOSE_RACEwith code9000, which is a normal outcome, so don’t alert on it. - A conference has no A-to-B bridge. Each member’s leg joins a shared room, and you can control members one at a time.
- A stream isn’t a leg.
<Stream>forks audio to a WebSocket without using<Dial>, so it creates no B-leg. A CDR reports anystreaming_costseparately.
Choosing a flow by its legs
If you’re designing a flow, decide what each leg must do for you.
Capacity planning starts here too. Vobiz’s concurrency guide suggests one channel per agent or per simultaneous outbound leg, plus headroom for peaks.
What does a leg look like in SIP?
On the SIP side, each leg of a two-party call through a back-to-back user agent (B2BUA) is normally its own dialog. RFC 3261 identifies a dialog by three values: a Call-ID, a local tag, and a remote tag. Vobiz’s hangup cause reference describes the SIP and B2BUA layer beneath its call logs. This position is what makes a leg programmable, because the platform takes part in each dialog separately. It can end one dialog and start another. Not every B2BUA touches the audio. RFC 7092 sorts them by how much of the call they handle:
Three debugging habits follow from this:
- Don’t join legs on the SIP Call-ID. RFC 7092 says a signalling-only B2BUA doesn’t guarantee that any header carries over between sides. RFC 7989 exists partly because border devices deliberately change call identifiers. Use your platform’s IDs instead.
- Look at each leg’s quality separately. A relay terminates media on both sides, so one bad path may affect only one leg. Vobiz CDRs report
mos,jitter,packet_loss, andcodec, which you can compare across the two records. - Expect several early dialogs when a call forks. RFC 3261 lets provisional responses from different destinations create separate early dialogs. Only those that answer can continue, which mirrors the winner and losers in a simultaneous ring.
Where does a leg’s time and money go?
Each leg runs its own clock. Vobiz’s transferred-call guide gives a worked example with two legs, which we’ve plotted below.
That’s five pulses across two legs, on a call that lasted under four minutes end to end. Three rules explain the total:
- The bridge counts twice. The A-leg is billed for its whole life, including the bridged period, and the B-leg for its own.
- Rounding works per leg. A 38-second leg is billed as a full pulse, even though it only spans the final part of the call.
- Ringing is free. Billable time starts at answer, and an unanswered leg gets a record with
billsecandcostat zero.
Which leg should you target?
Start from what should change, then choose the control. Vobiz applies a default when a request doesn’t name a leg, so name the leg every time.Why do call legs matter in India?
Indian rules often turn on where each leg runs and what starts it. So leg design is a compliance question as well as an engineering one. These notes summarise the linked documents as of November 3, 2026, and they’re not legal advice.Keep both legs inside India
Vobiz’s India calling regulations page requires both legs of a domestic call to stay within India, and conference participants too. Bridging a domestic leg to an international leg fails with the Violates Media Anchoring hangup cause. That shapes your design in three ways:- Agents. Seat anyone who takes a domestic leg in India.
- Application servers. The hangup cause reference says your server must be in India for India calls, under code
2070. - Conferences. The same reference warns against mixing PSTN and WebRTC members.
Watch for toll bypass in private-network joins
DoT’s 2021 OSP guidelines define toll bypass as illegally carrying voice between the public network in India and a foreign country, or between public networks in two Indian cities, through your own network. Put in leg terms, that’s two public network legs joined across a private link. If your organisation meets the OSP definition, review any such design. The guidelines date from June 2021. Khaitan & Co reports that DoT notified new principal service authorisation rules on 24 June 2026. We could not confirm whether those rules change the OSP position.Treat API-placed legs as A2P
TRAI’s September 2026 Third Amendment defines an A2P call as a voice call “initiated by an application, software system, or automated platform without direct human dialling and delivered to an individual telecom subscriber”. TRAI’s press release summarises the change. Three points matter for leg design:- A live agent may not take you outside it. Stakeholders asked TRAI to exclude API-bridged calls with a human on the line, citing ride-hailing and agent diallers. TRAI kept the definition, saying providers can’t reliably tell the difference. An agent-first flow may therefore count, so raise it with your provider.
- Undeclared calls count as spam. Senders must declare A2P use and caller ID ranges to the originating provider, and undeclared calls count as unsolicited commercial communication. TRAI’s memorandum notes that SIP and PRI connections made up 15,736 of 20,591 disconnections in April 2026.
- The number series on the customer-facing leg matters. The text lets terminating operators charge originating operators up to ₹0.05 per minute on A2P calls, with an exemption for 140xx, 1600xx, and 1601xx series numbers.
callerId on <Dial>. Calling regulations cover which series fits each call type, and 140 and 160 series acquisition covers commercial numbers.
How does Vobiz expose call legs?
Vobiz lets you address legs directly through its Call API and VobizXML. Different identifiers appear at different points in a call:
You act on legs through these controls:
- Create and bridge.
<Dial>creates one or more B-legs and bridges the first success to the A-leg. ItscallbackUrlfollows the B-leg live, andactiongets the finalDialStatus. - Limit each phase.
timeoutcovers unanswered ringing, andtimeLimitcovers the connected bridge. - Listen for keys per leg.
digitsMatchwatches the A-leg anddigitsMatchBLegwatches the B-leg. - Redirect. The Transfer API takes
legswithaleg_urlandbleg_url. To connect another person, return a<Dial>from that URL. - Record across legs. A session recording started at answer continues through a transfer. The Record Calls API sets
record_channel_typetostereoto split caller and callee into separate channels. - Detect machines. Machine detection is set on a Make Call request, so it applies to that outbound first leg, not to a B-leg from
<Dial>. - Reconcile. The CDR API returns
costandtotal_costfor each leg. Webhooks carry durations rather than charges.
Frequently asked questions
What is a call leg in simple terms?
What is a call leg in simple terms?
A call leg is one connection between a voice platform and one party. The platform sits in the middle, so a normal two-person call runs as two connections joined together. Each one can ring, answer, fail, and end by itself.
How do the A-leg and B-leg differ?
How do the A-leg and B-leg differ?
The A-leg exists first, and the platform creates the B-leg from it to reach another party. On an inbound call, the A-leg is the caller. On a call your app places, the A-leg is the person you dialed first.
Is a call leg the same as a SIP dialog?
Is a call leg the same as a SIP dialog?
Nearly. RFC 2543 used the term call leg, and RFC 3261 replaced it with dialog. Platforms now use leg more loosely, for the whole connection and its records. A platform leg usually maps to one dialog on its SIP side.
How many legs does a conference call have?
How many legs does a conference call have?
A conference has one leg per participant, so a five-person conference has five legs. Each leg connects to a shared room instead of being bridged to one other party. That lets you mute or remove one member without touching the rest.
Are both legs of a forwarded call billed?
Are both legs of a forwarded call billed?
On Vobiz, yes, when both are answered. Each leg is charged separately on its own billable time, rounded up to its pulse, so the bridged period counts on both. An unanswered leg still gets a record, at zero cost. Other providers can differ.
Why would you transfer only one leg?
Why would you transfer only one leg?
You transfer one leg to change one party’s next step and leave the other on its current flow. On Vobiz, set legs to aleg or bleg and supply that leg’s URL. Use both only when each side needs new instructions.
Further reading on Vobiz
- Transferred calls end to end · Dial status reporting · Hangup causes
- What is SIP? · What is a voice API? · Context-aware call transfers
Sources
Standards- IETF, RFC 3261: SIP: Session Initiation Protocol, June 2002.
- IETF, RFC 7092: A Taxonomy of Session Initiation Protocol (SIP) Back-to-Back User Agents, December 2013.
- IETF, RFC 7989: End-to-End Session Identification in IP-Based Multimedia Communication Systems, October 2016.
- DoT, Revised Guidelines for Other Service Providers, 23 June 2021.
- TRAI, Press release 119/2026 on the Third Amendment, 18 September 2026.
- TRAI, Third Amendment Regulations, 2026, 18 September 2026.
- Khaitan & Co, Update on the principal telecommunication services authorisation rules, June 2026.
- Cisco, Understanding inbound and outbound dial peers on Cisco IOS platforms.
- PortaOne, xDR calculation.
- Firebrick, Call Data Records.
Build on Vobiz
Provision a number and place your first programmable, multi-leg call.