Call.drop
From Yate Documentation
(Difference between revisions)
| Line 6: | Line 6: | ||
The message seems to have been designed for synchronous processing. | The message seems to have been designed for synchronous processing. | ||
| − | queues | + | ===queues=== |
The first call in a queue is dropped by sending the queue_name as id. If you want to drop a specific call send queue_name/$id - for example "myqueue/sip/1". | The first call in a queue is dropped by sending the queue_name as id. If you want to drop a specific call send queue_name/$id - for example "myqueue/sip/1". | ||
| − | cdrbuild | + | ===cdrbuild=== |
A call can be dropped by the cdrbuilder without actually dropping the call, by prepending cdrbuild/ - for example "cdrbuild/sip/1" | A call can be dropped by the cdrbuilder without actually dropping the call, by prepending cdrbuild/ - for example "cdrbuild/sip/1" | ||
Revision as of 15:46, 8 October 2012
This documentation has been extracted from the source of Yate-0.9-CVS and as such it might not be accurate -- technically or semantically.
The call.drop message seems to be emitted by a controlling module (such as rmanager) towards a channel-providing module.
The message seems to have been designed for synchronous processing.
Contents |
queues
The first call in a queue is dropped by sending the queue_name as id. If you want to drop a specific call send queue_name/$id - for example "myqueue/sip/1".
cdrbuild
A call can be dropped by the cdrbuilder without actually dropping the call, by prepending cdrbuild/ - for example "cdrbuild/sip/1"
Message parameters
id
- module-specific id of call to drop - for example "sip/123"
It can also be empty to drop all live channels.
Optional parameters
reason
- reason for dropping the call
