Call.progress
From Yate Documentation
(Difference between revisions)
(Created page with " The '''call.progress''' message is emitted by a channel-creating module (such as h323chan and ysipchan). The message has been designed for asynchronous processing (broadcast...") |
|||
| (One intermediate revision by one user not shown) | |||
| Line 14: | Line 14: | ||
'''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.ringing]] | ||
| + | * [[Starting CDR Ring Timer on call.progress]] | ||
Latest revision as of 13:56, 18 October 2013
The call.progress message is emitted by a channel-creating module (such as h323chan and ysipchan).
The message has 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
