Skip to main content
June 16, 2026 · By Piyush Sahoo · Updated November 3, 2026 A call leg is one connection between a voice platform and one party, such as a phone, SIP device, or carrier. A two-person call usually has two legs, called the A-leg and B-leg, joined by a bridge. Each leg has its own identifier, events, record, and charge, so you can control it separately. This guide takes the idea from the SIP layer up to the bill. It counts the legs in common flows, shows where webhooks (callbacks) fire, and lists the Indian rules that depend on how you join legs.
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. Two diagrams compared. A SIP proxy forwards requests between two phones, which share one dialog and one Call-ID. A back-to-back user agent ends one dialog and starts another, which creates an A-leg and a B-leg with separate Call-IDs and audio that can pass through the platform. Two diagrams compared. A SIP proxy forwards requests between two phones, which share one dialog and one Call-ID. A back-to-back user agent ends one dialog and starts another, which creates an A-leg and a B-leg with separate Call-IDs and audio that can pass through the platform.

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. Six flows compared. An IVR or voicemail has one leg. Forwarding to an agent has two. Ringing three phones has one A-leg and three attempted B-legs, with one winner. Agent-first click to call has two, with the agent as the A-leg. A four-person conference has four legs into a room. An AI agent on a stream has one leg plus a WebSocket that is not a leg. Six flows compared. An IVR or voicemail has one leg. Forwarding to an agent has two. Ringing three phones has one A-leg and three attempted B-legs, with one winner. Agent-first click to call has two, with the agent as the A-leg. A four-person conference has four legs into a room. An AI agent on a stream has one leg plus a WebSocket that is not a leg. Three of these flows behave in ways worth noting:
  • Simultaneous ring creates legs that lose. Vobiz bridges the first answer and cancels the rest. Those report LOSE_RACE with code 9000, 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 any streaming_cost separately.

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, and codec, 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. Timeline of a transferred call. The A-leg rings for 7 seconds and is answered for 219 seconds, billed as 4 pulses. The B-leg starts near the end, rings for 21 seconds, and is answered for 38 seconds, billed as 1 pulse. Webhooks fire at answer, at transfer, at B-leg answer and connect, and at hangup. Timeline of a transferred call. The A-leg rings for 7 seconds and is answered for 219 seconds, billed as 4 pulses. The B-leg starts near the end, rings for 21 seconds, and is answered for 38 seconds, billed as 1 pulse. Webhooks fire at answer, at transfer, at B-leg answer and connect, and at hangup. 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 billsec and cost at zero.
Don’t assume another system works this way. Firebrick’s documentation, for example, attaches the CDR to the outbound leg and describes moving it when a call is diverted. Ask each provider how it meters legs. For Vobiz rates, see the pricing page.

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. Decision map. To redirect the first party, transfer with legs set to aleg and an aleg_url. To redirect the other party, use bleg and a bleg_url. To move both, use both URLs. To connect someone new, return a Dial from the transfer URL. To reach only one side, use legs on Play or Speak, or leg on DTMF, all defaulting to aleg. To match legs afterwards, use bridge_uuid on the CDR detail. Decision map. To redirect the first party, transfer with legs set to aleg and an aleg_url. To redirect the other party, use bleg and a bleg_url. To move both, use both URLs. To connect someone new, return a Dial from the transfer URL. To reach only one side, use legs on Play or Speak, or leg on DTMF, all defaulting to aleg. To match legs afterwards, use bridge_uuid on the CDR detail. When a multi-leg flow misbehaves, the symptom usually points at one leg:

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. Four India checks. Two domestic legs stay in India and pass the Vobiz anchoring rule. A domestic leg bridged to an international leg fails with Violates Media Anchoring, code 2070. Public network legs in two cities joined over your own network match DoT's toll bypass pattern for OSPs. An application-placed leg to a subscriber is an A2P call once the rule is in force, which requires declaring use and caller ID ranges. Four India checks. Two domestic legs stay in India and pass the Vobiz anchoring rule. A domestic leg bridged to an international leg fails with Violates Media Anchoring, code 2070. Public network legs in two cities joined over your own network match DoT's toll bypass pattern for OSPs. An application-placed leg to a subscriber is an A2P call once the rule is in force, which requires declaring use and caller ID ranges.

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.
The declaration and the charge start 60 days after Gazette publication. TRAI issued the text on 18 September 2026, so they can’t start before mid-November 2026. We could not confirm the publication date itself, so check whether they apply when you launch. On Vobiz, you set the number shown on a B-leg with 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. Its callbackUrl follows the B-leg live, and action gets the final DialStatus.
  • Limit each phase. timeout covers unanswered ringing, and timeLimit covers the connected bridge.
  • Listen for keys per leg. digitsMatch watches the A-leg and digitsMatchBLeg watches the B-leg.
  • Redirect. The Transfer API takes legs with aleg_url and bleg_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_type to stereo to 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 cost and total_cost for each leg. Webhooks carry durations rather than charges.
To step through a real sequence, use the Dial transfer visualizer. Live calls and transfers are billed and reach real people, so run them with your own Auth ID and Auth Token, and confirm the numbers first.

Frequently asked questions

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.
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.
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.
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.
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.
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

Sources

Standards Indian regulators and legal updates Vendor documentation, all read on November 3, 2026

Build on Vobiz

Provision a number and place your first programmable, multi-leg call.