Summary

  • RFC 3624 turned MGCP's one-endpoint-at-a-time audit into a bulk report that could be continued when a reply reached the datagram-size limit.
  • 200 OK did not mean the requested range was complete: BA/NE identified where to resume, while BA/EL told the Call Agent which endpoints a compact count or state vector described.

In 2003, the recovery problem was practical: a Call Agent that failed over might need to reconstruct its view of a gateway containing hundreds or thousands of endpoints. Base MGCP's audit commands inspected one endpoint at a time. RFC 3624 added a Bulk Audit package so the agent could ask about a group, discover endpoint names, and obtain selected state or connection information. The RFC was Informational, and its IESG note explicitly distinguished MGCP from the standards-based Megaco alternative in RFC 3015. The package should be read as a historical recovery interface, not as evidence of any named carrier's deployment. (RFC 3624; earlier MGCP in RFC 2705; later MGCP 1.0 in RFC 3435.)

The package separated questions that a broad wildcard could make look alike. BA/Z asked for the configured naming pattern. BA/X asked which non-persistent virtual endpoints were instantiated now. A naming convention such as conference/* could therefore exist even when only a scattered subset of those endpoints had been created. Treating the pattern as an inventory would turn a rule for possible names into a claim about present state.

For existing endpoints, BA/C returned connection counts in order. A hexadecimal digit encoded zero through fifteen connections; Z meant more than fifteen, not an exact figure. BA/M represented connection modes. BA/S tested requested endpoint conditions and returned T, F, or O for out of service. It was a compact logical-OR test across the requested conditions—not a description of every connection. The RFC expressly says the endpoint-state indicator says nothing about connection state. None of these values answered whether a call completed, media flowed, an application worked, or a customer could reach a service.

Then came the datagram ceiling. A gateway could return fewer endpoints than requested if the full report would exceed the maximum datagram size. In that case it had to include BA/NE, the next local endpoint name. The Call Agent could place that name in a subsequent BA/SE request and continue. A success code acknowledged this transaction's response; the continuation field disclosed that the larger audit remained unfinished. (RFC 3624, §§2.1.1.1, 2.1.1.7)

Counts and state required a second kind of boundary: correspondence. BA/EL had to precede a BA/C or BA/S list and identify the endpoints represented by its positions. This mattered especially for virtual endpoints whose instantiated ranges could be disjoint. A vector without the endpoint map might be perfectly parseable and still be operationally misassigned. When counts and state were requested together, they had to cover the same endpoints. (RFC 3624, §§2.1.1.8, 2.1.2)

RFC 3624 defines a way to resume a large audit; it does not define an atomic snapshot across requests. The pages could describe observations gathered at different moments, and the specification gives no snapshot epoch that would make them one frozen view. In failover, that omission matters: the agent may recover a useful control-plane picture without having proved that it is complete, simultaneous, or equivalent to service. The distinction echoes a broader operational principle in Running-Code Primacy: abstractions must remain answerable to what the running system actually does. That essay is a disclosed analytical lens here, not evidence about MGCP implementation.

The report's grammar was modest—and that modesty was useful. It told the Call Agent what the gateway returned, which names those values belonged to, and where the next request should start. It did not turn a recovery query into an end-to-end service test. A control view is evidence about control state. The operator still needs separate evidence for connections, media, applications and customer outcomes.