Search results

Page title matches

• YIAX design
  3 KB (399 words) - 11:45, 4 November 2013
• Yate Design
  The purpose of Yate's design is to provide an extensible telephony engine. Holding the base code as simp [[Category:Programmers]] [[Category:Design]]
  2 KB (324 words) - 11:32, 13 November 2015

Page text matches

• What is Yate
  [[Category:Server]] [[Category:Client]] [[Category:Design]]
  3 KB (376 words) - 12:42, 4 November 2013
• Handling many simultaneous calls
  ...e largest number of simultaneous calls but unfortunately is plagued by bad design decisions and typical operating system handling of network sockets. We do not recommend IAX for handling large number of calls because of these design problems.
  4 KB (758 words) - 16:06, 31 October 2013
• Yate architecture
  * [[Yate Design]]
  811 B (119 words) - 13:48, 13 February 2013
• Yiax
  See [[YIAX design]] for implementation notes.
  232 B (38 words) - 14:38, 16 November 2012
• Yate and OpenSIPS
  ...nce services in a highly efficient way, thanks to its scalable and modular design.
  2 KB (343 words) - 15:13, 30 October 2012
• Messages
  * [[Yate Design]]
  8 KB (1,217 words) - 20:38, 10 March 2014
• Beginners in Yate
  It is written in C++, having in mind a modular [[Yate Design| design]], allowing the use of scripting languages like Perl, Python or PHP to crea
  5 KB (888 words) - 13:05, 10 March 2015
• Yate Design
  The purpose of Yate's design is to provide an extensible telephony engine. Holding the base code as simp [[Category:Programmers]] [[Category:Design]]
  2 KB (324 words) - 11:32, 13 November 2015
• Programmer's guide
  But all Yate API's are quite unified, so all Yate design pages, apply to all API's. Enjoy. == About Yate design and implementation ==
  4 KB (524 words) - 09:01, 10 March 2016
• Configure M2UA
  ...ocated in different networks types, PSTN and Internet. This gateway-client design does not allow a SS7 layer 3 present on the gateway side because the M2UA g ...t's own Point Code. For some reasons, let's say security issues or network design, we do not want to process the traffic received from Node 1 on Node 3 so th
  13 KB (2,284 words) - 11:12, 13 December 2017
• Configure Cisco SLT
  ...td/doc/product/access/sc/rel9/soln/voip20/impl/impdesn.htm|Voice Networks: Design Fundamentals]
  10 KB (1,328 words) - 09:09, 26 October 2017
• SIP query for CNAM and LNP
  For each of the queries an INVITE without media is sent to the designated server. From the SIP answer (which is supposed to be a 3xx Redirect) th
  5 KB (700 words) - 10:31, 4 November 2013
• Analog
  '''Note:''' In Yate's terminology, FXS/FXO designates the local (Yate) end of the line, not the remote one.
  17 KB (2,660 words) - 08:04, 21 June 2018
• More About VoIP
  ...ines were analogue, nowadays they are almost entirely digital. The PSTN is designed after a lot of standards. This applies to VoIP protocols as well.
  9 KB (1,569 words) - 13:20, 20 March 2013
• Call.cdr
  The message seems to have been designed for asynchronous processing (broadcast).
  2 KB (321 words) - 10:37, 21 January 2013
• Telephony
  This is a SIGTRAN protocol and it was designed for remote processing of SS7 messages above MTP3 protocol, mostly ISUP an M2PA is a peer to peer SS7 layer 2 protocol. It was designed to replace MTP2 protocol in the IP scenarios.
  8 KB (1,083 words) - 11:49, 27 October 2017
• Call.progress
  The message has been designed for asynchronous processing (broadcast).
  612 B (88 words) - 11:56, 18 October 2013
• Chan.rtp
  The message is designed for synchronous processing.
  3 KB (375 words) - 08:03, 8 June 2016
• Call.ringing
  The message seems to have been designed for asynchronous processing (broadcast).
  719 B (108 words) - 10:42, 21 January 2013
• Call.answered
  The message seems to have been designed for asynchronous processing (broadcast).
  960 B (147 words) - 10:35, 21 January 2013