Recognizer STOP
The STOP method, sent from the client to the server, tells the recognizer resource to halt an active recognition. If a RECOGNIZE request was in progress and STOP terminated it, the response includes an Active-Request-Id-List header field naming the request-id of the terminated RECOGNIZE—and no RECOGNITION-COMPLETE event is sent for it. If no recognition was active, the response omits that header. Either way, the response carries a status of 200 (Success).
MRCPv1 example
A RECOGNIZE request is in progress when the client issues STOP; the response confirms the terminated request through the Active-Request-Id-List header:
| C->S: RECOGNIZE 543258 MRCP/1.0 Content-Type:text/uri-list Content-Length:... session:request1@form-level.store S->C: MRCP/1.0 543258 200 IN-PROGRESS C->S: STOP 543259 MRCP/1.0 S->C: MRCP/1.0 543259 200 COMPLETE Active-Request-Id-List:543258 |
MRCPv2 example
The same exchange in MRCPv2, with the Channel-Identifier header on every message:
| C->S: MRCP/2.0 ... RECOGNIZE 543258 Channel-Identifier:32AECB23433801@speechrecog Content-Type:text/uri-list Content-Length:... session:request1@form-level.store S->C: MRCP/2.0 ... 543258 200 IN-PROGRESS Channel-Identifier:32AECB23433801@speechrecog C->S: MRCP/2.0 ... STOP 543259 Channel-Identifier:32AECB23433801@speechrecog S->C: MRCP/2.0 ... 543259 200 COMPLETE Channel-Identifier:32AECB23433801@speechrecog Active-Request-Id-List:543258 |