SIP in Yate
From Yate Documentation
(Difference between revisions)
(→SIP with NAT in Yate) |
(→Listeners set in Yate) |
||
| (87 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | The implementation of SIP it is done using a VoIP SIP driver based on [[YASS]] library. | |
| − | + | Yate can be used as a: | |
| + | * [[Yate as SIP server|SIP Server]] - by default Yate can be used as a SIP Server that will listen to all interfaces. You just have to configure users and routing rules in specific configuration files. | ||
| + | * [[Yate as a Conference Server|SIP conference Server]] | ||
| + | * [[SIP_Client|SIP Client]]. | ||
| + | * [[SIP Router]] | ||
| + | * [[SIP Session Border Controller]] | ||
| + | * [[SIP Registration Server]] | ||
| − | + | The main configuration file is [[SIP_Configuration_File|ysipchan.conf]]. | |
| + | |||
| + | The main functions in this file are: | ||
| + | * defining a '''[[Listeners in Yate|listener]]''' (a specific section in configuration file) which specify the interface so Yate will listen to, that can be on UDP, TCP or TLS. | ||
| + | * enable/disable '''methods''' section - will allow to enable/disable [[SIP Methods]]. | ||
| + | * define [[SIP_Flood_Protection|flood protection mechanisms]]. | ||
| + | * enable [[SIP Security in Yate|security]] - allows you to use of SRTP packets for voice. | ||
| + | * supports [[RTP_Forwarding|RTP forward]]. | ||
| + | * encapsulate SIP in ISUP signalling using SIP-T protocol. The protocol SIP-I is not supported by Yate. | ||
| + | |||
| + | === Yate Server as a SIP - B2BUA === | ||
| + | |||
| + | [[File:yate_b2bua_call_scenario.png]] | ||
| + | |||
| + | Yate is a back-to-back user agent (B2BUA). This is a logical entity that receives calls on SIP and sends them through other protocols as configured. In the figure it is IAX, but it can be H.323, Jingle, SIP. | ||
| + | |||
| + | Yate is not a Proxy Server, he does much more than that: | ||
| + | * maintains a complete state for the calls | ||
| + | * handles automatic call disconnection or call transfer | ||
| + | * conceals the caller identity | ||
| + | * generate requests of their own and also final responses | ||
| + | * can provide NAT traversal solution | ||
| + | * can interwork with different networks | ||
| + | * can overwrite and modify the SIP headers like Contact, Via, Route. | ||
| + | |||
| + | Yate implements SIP protocol that runs over User Datagram Protocol (UDP) and Transmission Control Protocol (TCP), but not over Stream Control Transmission Protocol (SCTP). | ||
| + | |||
| + | Yate can act as a SIP Server as you can see in the image below and also you can configure Yate to be a [[SIP Client]]. | ||
[[File:sip_flow_messages.png]] | [[File:sip_flow_messages.png]] | ||
| Line 12: | Line 45: | ||
A transaction occurs between a user agent client (UAC) and a user agent server(UAS), and comprises all messages from the initial request to the final response. | A transaction occurs between a user agent client (UAC) and a user agent server(UAS), and comprises all messages from the initial request to the final response. | ||
| − | The first line tells us that this is INVITE | + | The first line tells us that this is INVITE request which is used to establish a session. |
The responses can be provisional, starting with 1 followed by two digits (for example, "180 Ringing") or final starting with 2 followed by two digits (for example, "200 Ok"). | The responses can be provisional, starting with 1 followed by two digits (for example, "180 Ringing") or final starting with 2 followed by two digits (for example, "200 Ok"). | ||
| − | The scope of a transaction is defined by the stack of the Via headers of the SIP | + | The scope of a transaction is defined by the stack of the Via headers of the SIP request. |
| − | After 100 Trying | + | After 100 Trying response is sent, if no request arrives to Caller then Yate will send a copy of the first INVITE, this is called retransmission and the flow of the messages will continue. |
| + | A dialog is established, such as INVITE to an request a 2xx response - the action was successfully received, understood, and accepted. | ||
| − | + | As you can see in the image, the RTP can pass directly from caller to the callee once the transaction is established, or the RTP can go through Yate and Yate will send the SDP to the callee. | |
| − | + | ===How to configure SIP in Yate === | |
| − | + | This are the configuration files for SIP: | |
| − | * | + | * '''ysipchan.conf''' the main file for configuring SIP methods |
| + | * '''sipfeatures.conf''' configures some SIP features | ||
| + | * '''sip_cnam_lnp.conf''' controls how CNAM and LNP queries are performed | ||
| − | + | For configuring users, gateways no matter the protocol used, other files are used as '''regfile.conf''' or '''regexroute.conf'''. | |
| − | + | Using the default configuration from '''ysipchan.conf''' file, Yate will behave as a SIP server, that will listen on all interfaces or you can configure your own listeners. In Yate you can build UDP, TCP, TLS listeners. | |
| − | + | More infomations about [[SIP Routing in Yate]]. | |
| − | + | ==== SIP with NAT in Yate ==== | |
| − | + | Historically there have been problems with SIP when passing through NAT. This is not a SIP problem, but a RTP problem. SIP announces the RTP address and port, but if the client is behind NAT, it announces the client's RTP port, which can be different from the port the NAT allocates externally. The solution is to use a [[SIP SBC|SIP Session Border Controller]]. | |
| − | + | In '''[general]''' section from file ysipchan.conf the ''nat'' setting will try to replace nonroutable IP addresses of the RTP media stream with the address the SIP signalling was received from. This significantly improves chances that clients behind a dumb NAT get normal voice. You should also have parameter ''ignorevia'' enabled. | |
| − | + | When Yate is behind a NAT and registers in [[Accfile|accfile.conf]] to a Sip gateway you can set following parameters: | |
| − | === | + | * localaddress: Local address to set in sent messages |
| + | :- Set it to 'yes' to detect NAT and re-register with public IP when NAT is detected | ||
| + | :- Set it to 'no' or ipaddress (e.g. 1.2.3.4 or 1.2.3.4:5060) to disable NAT detection | ||
| + | * keepalive: Optional interval for NAT keep alive. | ||
| + | <!-- | ||
| + | ==== ISUP signalling with SIP-T ==== | ||
| − | + | In Yate, [http://en.wikipedia.org/wiki/ISDN_User_Part ISUP] signalling is encapsulated in SIP using [http://en.wikipedia.org/wiki/Session_Initiation_Protocol#SIP-ISUP_interworking SIP-T protocol]. | |
| − | + | The other way of encapsulating ISUP in SIP would be SIP-I, but it is not supported in Yate. | |
| − | |||
In section '''[sip-t]''' enable parameter ''isup'' that will build outgoing or decode incoming application/isup bodies.<br> | In section '''[sip-t]''' enable parameter ''isup'' that will build outgoing or decode incoming application/isup bodies.<br> | ||
| − | If enabled an incoming application/isup body will be decoded and added to the engine message issued by the receiving channel.<br> | + | If enabled, an incoming application/isup body will be decoded and added to the engine message issued by the receiving channel.<br> |
If the channel needs to add more then one body to an outgoing message, a multipart/mixed body will be attached to the message. | If the channel needs to add more then one body to an outgoing message, a multipart/mixed body will be attached to the message. | ||
| + | --> | ||
| − | === DTMF methods === | + | ==== DTMF methods ==== |
| − | In section '''[general]''' parameter ''dtmfmethods'' configures the allowed methods and the order they are tried: | + | In section '''[general]''' parameter ''dtmfmethods'' configures the allowed methods for sending or receiving DTMFs and the order they are tried: |
| − | * rfc2833 Send DTMFs as RFC2833 RTP signals. This method will be used if media is started and remote party advertised telephone event support in SDP. | + | * rfc2833 - Send DTMFs as RFC2833 RTP signals. This method will be used if media is started and remote party advertised telephone event support in SDP. |
| − | * info Send DTMFs using SIP INFO method. | + | * info - Send DTMFs using SIP INFO method. |
| − | * inband Send DTMFs in audio stream. This method will succeed if media is started, the tone generator module is loaded and there is a translator from PCM (yate 'slin' format) to current rtp format | + | * inband - Send DTMFs in audio stream. This method will succeed if media is started, the tone generator module is loaded and there is a translator from PCM (yate 'slin' format) to current rtp format |
| − | More information about | + | More information about [[SIP_Send_DTMFs|how to send DTMFs]]. |
| − | === Codecs supported in Yate === | + | ==== Codecs supported in Yate ==== |
The '''[codecs]''' section allows to individually enable or disable the codecs. | The '''[codecs]''' section allows to individually enable or disable the codecs. | ||
| Line 82: | Line 123: | ||
* amr_octet - Octet aligned AMR RTP payload default (if not in SDP) | * amr_octet - Octet aligned AMR RTP payload default (if not in SDP) | ||
| − | === Listeners set in Yate === | + | ==== Listeners set in Yate ==== |
| + | |||
| + | Configured listeners tell Yate on which network interfaces to listen. | ||
| + | |||
| + | They are set in section called [listener name] or in [general] section in ysipchan.conf. | ||
| + | |||
| + | Yate can bind TCP, UDP and TLS [[Listeners in Yate|listeners]]. | ||
| − | |||
| + | '''See also:''' | ||
| + | * [http://en.wikipedia.org/wiki/Session_Initiation_Protocol SIP Protocol]. | ||
| + | * [[SIP Configuration File]] | ||
| + | * [[SIP Features Module]] | ||
| + | * [[Telephony]] | ||
| − | + | [[Category:SIP]] [[Category:Codecs]] [[Category:DTMF]] [[Category:B2BUA]] | |
Latest revision as of 10:43, 4 November 2013
The implementation of SIP it is done using a VoIP SIP driver based on YASS library.
Yate can be used as a:
- SIP Server - by default Yate can be used as a SIP Server that will listen to all interfaces. You just have to configure users and routing rules in specific configuration files.
- SIP conference Server
- SIP Client.
- SIP Router
- SIP Session Border Controller
- SIP Registration Server
The main configuration file is ysipchan.conf.
The main functions in this file are:
- defining a listener (a specific section in configuration file) which specify the interface so Yate will listen to, that can be on UDP, TCP or TLS.
- enable/disable methods section - will allow to enable/disable SIP Methods.
- define flood protection mechanisms.
- enable security - allows you to use of SRTP packets for voice.
- supports RTP forward.
- encapsulate SIP in ISUP signalling using SIP-T protocol. The protocol SIP-I is not supported by Yate.
Contents |
[edit] Yate Server as a SIP - B2BUA
Yate is a back-to-back user agent (B2BUA). This is a logical entity that receives calls on SIP and sends them through other protocols as configured. In the figure it is IAX, but it can be H.323, Jingle, SIP.
Yate is not a Proxy Server, he does much more than that:
- maintains a complete state for the calls
- handles automatic call disconnection or call transfer
- conceals the caller identity
- generate requests of their own and also final responses
- can provide NAT traversal solution
- can interwork with different networks
- can overwrite and modify the SIP headers like Contact, Via, Route.
Yate implements SIP protocol that runs over User Datagram Protocol (UDP) and Transmission Control Protocol (TCP), but not over Stream Control Transmission Protocol (SCTP).
Yate can act as a SIP Server as you can see in the image below and also you can configure Yate to be a SIP Client.
The flow for this messages is similar to the HTTP request/response transaction model.
A transaction occurs between a user agent client (UAC) and a user agent server(UAS), and comprises all messages from the initial request to the final response.
The first line tells us that this is INVITE request which is used to establish a session.
The responses can be provisional, starting with 1 followed by two digits (for example, "180 Ringing") or final starting with 2 followed by two digits (for example, "200 Ok").
The scope of a transaction is defined by the stack of the Via headers of the SIP request.
After 100 Trying response is sent, if no request arrives to Caller then Yate will send a copy of the first INVITE, this is called retransmission and the flow of the messages will continue. A dialog is established, such as INVITE to an request a 2xx response - the action was successfully received, understood, and accepted.
As you can see in the image, the RTP can pass directly from caller to the callee once the transaction is established, or the RTP can go through Yate and Yate will send the SDP to the callee.
[edit] How to configure SIP in Yate
This are the configuration files for SIP:
- ysipchan.conf the main file for configuring SIP methods
- sipfeatures.conf configures some SIP features
- sip_cnam_lnp.conf controls how CNAM and LNP queries are performed
For configuring users, gateways no matter the protocol used, other files are used as regfile.conf or regexroute.conf.
Using the default configuration from ysipchan.conf file, Yate will behave as a SIP server, that will listen on all interfaces or you can configure your own listeners. In Yate you can build UDP, TCP, TLS listeners.
More infomations about SIP Routing in Yate.
[edit] SIP with NAT in Yate
Historically there have been problems with SIP when passing through NAT. This is not a SIP problem, but a RTP problem. SIP announces the RTP address and port, but if the client is behind NAT, it announces the client's RTP port, which can be different from the port the NAT allocates externally. The solution is to use a SIP Session Border Controller.
In [general] section from file ysipchan.conf the nat setting will try to replace nonroutable IP addresses of the RTP media stream with the address the SIP signalling was received from. This significantly improves chances that clients behind a dumb NAT get normal voice. You should also have parameter ignorevia enabled.
When Yate is behind a NAT and registers in accfile.conf to a Sip gateway you can set following parameters:
- localaddress: Local address to set in sent messages
- - Set it to 'yes' to detect NAT and re-register with public IP when NAT is detected
- - Set it to 'no' or ipaddress (e.g. 1.2.3.4 or 1.2.3.4:5060) to disable NAT detection
- keepalive: Optional interval for NAT keep alive.
[edit] DTMF methods
In section [general] parameter dtmfmethods configures the allowed methods for sending or receiving DTMFs and the order they are tried:
- rfc2833 - Send DTMFs as RFC2833 RTP signals. This method will be used if media is started and remote party advertised telephone event support in SDP.
- info - Send DTMFs using SIP INFO method.
- inband - Send DTMFs in audio stream. This method will succeed if media is started, the tone generator module is loaded and there is a translator from PCM (yate 'slin' format) to current rtp format
More information about how to send DTMFs.
[edit] Codecs supported in Yate
The [codecs] section allows to individually enable or disable the codecs. This is a list of supported codecs:
- default - Enable all unlisted codecs by default if a transcoder exists
- mulaw - Companded-only G711 mu-law (PCMU/8000)
- alaw - Companded-only G711 a-law (PCMU/8000)
- gsm: - European GSM 06.10 (GSM/8000)
- lpc10 - Linear Prediction Codec (LPC/8000)
- ilbc - Internet Low Bandwidth Codec (iLBC/8000)
- amr - Adaptive Multi-Rate 3GPP (AMR/8000)
- slin - Signed Linear 16-bit uncompressed (L16/8000)
- g723 - ITU G.723 all variations (G723/8000)
- g726 - ITU G.726 32-bit (G726-32/8000)
- g728 - ITU G.728 all variations (G728/8000)
- g729 - ITU G.729 all variations (G729/8000)
- g729_annexb - G.729 Annex B (VAD) support default (if not in SDP)
- amr_octet - Octet aligned AMR RTP payload default (if not in SDP)
[edit] Listeners set in Yate
Configured listeners tell Yate on which network interfaces to listen.
They are set in section called [listener name] or in [general] section in ysipchan.conf.
Yate can bind TCP, UDP and TLS listeners.
See also:
