Call.ringing
From Yate Documentation
(Difference between revisions)
(Created page with "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.ringing''' message ...") |
|||
| Line 15: | Line 15: | ||
'''formats''' | '''formats''' | ||
:::a comma-separated list of supported formats (codecs) advertised by the remote end of the RTP channel. | :::a comma-separated list of supported formats (codecs) advertised by the remote end of the RTP channel. | ||
| + | |||
| + | |||
| + | '''See also''' | ||
| + | |||
| + | * [[call.route]] | ||
Latest revision as of 13:42, 21 January 2013
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.ringing message seems to be emitted by a channel-creating module (such as h323chan and ysipchan).
The message seems to have been designed for asynchronous processing (broadcast).
[edit] Message parameters
rtp_forward
- yes or no -- currently, the code sets this to yes unconditionally
rtp_addr
- the remote IP address of the RTP channel.
rtp_port
- the remote port of the RTP channel
formats
- a comma-separated list of supported formats (codecs) advertised by the remote end of the RTP channel.
See also
