SIP SBC
From Yate Documentation
(Difference between revisions)
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | Yate can be used as a SIP session border controller providing security for the internal network of the carrier. It provides also NAT traversal support. | + | Yate can be used as a [http://en.wikipedia.org/wiki/Session_border_controller SIP session border controller] providing security for the internal network of the carrier. It provides also NAT traversal support. |
To enable this feature you have to add in ysipchan.conf: | To enable this feature you have to add in ysipchan.conf: | ||
| Line 14: | Line 14: | ||
'''See also''' | '''See also''' | ||
| − | *[http://en.wikipedia.org/wiki/Session_border_controller SIP Session border controller] | + | * [http://en.wikipedia.org/wiki/Session_border_controller SIP Session border controller] |
| + | * [[SIP Configuration File]] | ||
| + | * [[Regular_expressions|regexroute.conf]] | ||
| + | * [[Telephony]] | ||
| + | |||
| + | [[Category:SIP]] [[Category:Server]] [[Category:SBC]] | ||
Latest revision as of 11:01, 4 November 2013
Yate can be used as a SIP session border controller providing security for the internal network of the carrier. It provides also NAT traversal support.
To enable this feature you have to add in ysipchan.conf:
[general] ignorevia=yes
If you want to use RTP forward between the 2 endpoints you can setup in regexroute.conf something like:
${rtp_forward}possible=;rtp_forward=yes
See also
