How To's
From Yate Documentation
(Difference between revisions)
(→Call detail records) |
|||
| Line 1: | Line 1: | ||
Yate has multiple routing modules and signalling modules. Here you can find some how to's for configuring Yate using different modules. | Yate has multiple routing modules and signalling modules. Here you can find some how to's for configuring Yate using different modules. | ||
| − | |||
| − | |||
The most popular scenarios for routing: | The most popular scenarios for routing: | ||
{|class="yate-table" | {|class="yate-table" | ||
| − | |class="yate-header-right"| | + | |class="yate-header-right"|==Routing== |
|- | |- | ||
|class="yate-content-right"| | |class="yate-content-right"| | ||
Revision as of 12:55, 11 September 2013
Yate has multiple routing modules and signalling modules. Here you can find some how to's for configuring Yate using different modules.
The most popular scenarios for routing:
| ==Routing== |
|
Example of register users in Regfile module.
Example of redirecting calls to another user.
Examples of how to route calls from javascript module.
Example of how to register users from a database.
Round robin routing examples.
Examples on how to convert SIP headers into SIP parameters.
Example on how to use copyparams from routing in CDR.
Setting up an IVR.
Useful information from various users about routing.
|
Contents |
Yate configuration as Server and / or Client
Various configuration for Yate to act as a Server and as a Client using different protocols.
| How To's |
|
Yate can be used as IAX Server and YateClient as IAX Client.
Yate used as a H323 Gatekeeper and YateClient as a H323 Client.
Configuring Yate as a SIP server.
Yate provides a protection mechanism against several types of SIP flood attacks.
Configuring Yate Server to use Jingle and YateClient to use a Jabber client.
Configuring Yate Server to be a H323 to SIP Signalling Proxy
Use Yate server to handle all your Google Voice calls.
Yate can be used with various service providers.
How to set up Yate as a PBX depending on the features you need.
|
Call detail records
Below are the modules and some tips you can use when writing call logs. You use this modules to obtain billing information.
| How To's |
|
How to write call logs to a database
Some things to take into account when wanting to bill from a database
How to write call logs to a file
Example of how to add custom parameters in CDR
For basic setups configure yate to write single cdr entry per call, instead of entry for each call leg.
|
Monitoring and debugging Yate
Some examples on how to monitor and enable debugging in Yate and the modules involved in this actions.
| How To's |
|
Overview on how to monitor yate using SNMP and rmanager.
Yate provides Debugging info on console.
Debug an external module in Telnet.
Yate offers the msgsniff module to allow the investigation of messages at runtime.
Yate can be monitored using Munin.
|
Miscellaneous
| How To's |
|
Tips on what you should pay attention to when running Yate in VMWare.
This example allows chat and short files transfer between Twinkle clients using SIP MESSAGE Request Method.
Notes on various protocols when you wish to handle many simultaneous calls.
How to modify call release cause codes.
|
VoIP to PSTN gateway
| How To's |
|
Example on how to use Yate as VoIP-PSTN gateway.
Guide to install Sangoma cards under Linux.
Guide to install Sangoma cards under Windows.
Guide to use Yate with BRI Stuff.
|
Troubleshooting
| Issue |
|
What to do if you suspect Yate is not connected to the database.
How to solve 'Headers already sent' warning for YateAdmin
You can use tcmpdump to follow VoIP traffic.
Various issues: STUN, kdoc, YateClient on Ubuntu 11.10
|
See also
