Search results
- The flow for this messages is similar to the HTTP request/response transaction model. ... a user agent client (UAC) and a user agent server(UAS), and comprises all messages from the initial request to the final response.8 KB (1,261 words) - 08:43, 4 November 2013
- This is a SIGTRAN protocol and it was designed for remote processing of SS7 messages above MTP3 protocol, mostly ISUP and SCCP.8 KB (1,083 words) - 11:49, 27 October 2017
- * localaddress: Local address to set in sent messages3 KB (422 words) - 08:08, 23 November 2017
- ; Also, this parameter can be overridden in chan.dtmf messages by a 'methods' parameter13 KB (1,916 words) - 09:08, 4 November 2013
- Typically these messages are queued asynchronously and the module does not wait for them being dispa1 KB (173 words) - 10:23, 21 January 2013
- Normally these messages are queued asynchronously and the module does not wait for them being dispa825 B (122 words) - 16:10, 18 January 2013
- :::Auto append Answered, Ringing and Progress _signalling_ messages to Accept after successfull routing2 KB (314 words) - 13:18, 22 January 2013
- * Tell YATE that this script is interested in call.route messages * Wait for [[call.route]] messages to come in from YATE2 KB (400 words) - 10:10, 4 November 2013
- ; is specified in processed messages or the tone is not found for the specified18 KB (1,064 words) - 10:06, 4 November 2013
- === Unhandled messages ===2 KB (245 words) - 10:47, 21 January 2013
- This is used typically by RTP to send DTMF messages apparently from the channel the RTP stream belongs to.2 KB (248 words) - 08:26, 14 February 2014
- * [[Messages]] [[Category:SIP]] [[Category:Messages]]2 KB (274 words) - 09:02, 4 November 2013
- ; NOTE: If 0, no debug messages will be printed out from this group or lines belonging to it17 KB (2,660 words) - 08:04, 21 June 2018
- : It can be overridden in [[chan.rtp]] messages. * '''monitoring''': bool: Emit the messages required for SNMP monitoring6 KB (870 words) - 14:12, 10 January 2014
- t Timestamp debugging messages relative to program start e Timestamp debugging messages based on EPOCH (1-1-1970 GMT)12 KB (1,986 words) - 15:13, 31 October 2013
- ...g you can increase the number of '''-v''' in the command to see more error messages. t Timestamp debugging messages relative to program start4 KB (588 words) - 09:43, 8 December 2021
- t Timestamp debugging messages relative to program start e Timestamp debugging messages based on EPOCH (1-1-1970 GMT)5 KB (770 words) - 08:44, 7 August 2013
- Also, it can be overridden when sending DTMFs (chan.dtmf messages) by a '''methods''' parameter. Also, it can be overridden in chan.dtmf messages by a parameter with the same name.2 KB (298 words) - 09:11, 4 November 2013
- The problem to be solved was providing a way of dealing with flood messages, while not disturbing traffic for already established transactions. ...n: bool: Activate the drop mechanism for INVITE/REGISTER/SUBSCRIBE/OPTIONS messages when4 KB (598 words) - 15:43, 31 October 2013
- ...ser is subscribed to receive notification if another user is called or has messages. Internally Yate will handle the following messages:3 KB (456 words) - 09:16, 9 April 2015