Quick links:
Product Overview
Installation
Settings and Administration
ADSL
SIP Support
Telephone ports
Network
Firewall
Wireless
VPN
Misc
Licenses
Troubleshooting
Differences
This shows you the differences between two versions of the page.
|
sip:trunk [2010/11/18 14:04] tibor |
sip:trunk [2010/11/18 14:13] (current) tibor |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== SIP Trunk ====== | ====== SIP Trunk ====== | ||
| The SIP Trunk module is designed to connect IP-PBX's and other SIP endpoints (phones) to Internet Telephony Service Providers by acting as a B2BUA (Back-To-Back User Agent) with one interface to the ITSP and the other to the IP-PBX and SIP phones. The ITSP interface is called SIP Trunk and the protocol used on both interfaces are SIP. The main function performed by this module is to provide a demarcation point where all communication on the SIP trunk behaves in a predictable way regardless of what equipment connects on the PBX interface. | The SIP Trunk module is designed to connect IP-PBX's and other SIP endpoints (phones) to Internet Telephony Service Providers by acting as a B2BUA (Back-To-Back User Agent) with one interface to the ITSP and the other to the IP-PBX and SIP phones. The ITSP interface is called SIP Trunk and the protocol used on both interfaces are SIP. The main function performed by this module is to provide a demarcation point where all communication on the SIP trunk behaves in a predictable way regardless of what equipment connects on the PBX interface. | ||
| + | |||
| + | ^ :!: You might need to purchase a [[:license]] to be able to use SIP Trunks in your unit. ^ | ||
| + | | Without SIP Trunk license the [[web GUI:SIP Trunk]] page is not functional. | | ||
| + | |||
| + | ===== Configuration ===== | ||
| + | SIP Trunks are configured on the [[web GUI:SIP Trunk]] page. | ||
| + | To make an outgoing call use the SIP Trunk module the [[web GUI:SIP Switch#Dial Plan]] on the [[web GUI:SIP Switch]] page is used. | ||
| ===== Interoperabilty ===== | ===== Interoperabilty ===== | ||
| Line 9: | Line 16: | ||
| ===== Routing calls ===== | ===== Routing calls ===== | ||
| - | To make an outgoing call use the SIP Trunk module the Dial Plan on the SIP Switch page is used. The call is routed to the SIP Trunk module if the "Forward to" field of the Dial Plan equals the string "SIPTRUNKx" where x is the SIP Trunk module number (1-9). | + | To make an outgoing call use the SIP Trunk module the Dial Plan on the [[web GUI:SIP Switch]] page is used. The call is routed to the SIP Trunk module if the "Forward to" field of the Dial Plan equals the string "SIPTRUNKx" where x is the SIP Trunk module number (1-9). |
| ===== Firewall/NAT traversal ===== | ===== Firewall/NAT traversal ===== | ||
| Line 15: | Line 22: | ||
| ===== Header manipulation and variable substitution ===== | ===== Header manipulation and variable substitution ===== | ||
| - | A generic SIP header manipulation tool for SIP requests passing through the box is available through configuration using the grammar for the header field component in a SIP URI using '?', '=', '%' and '&', as described in RFC 3261. In short, header fields for usage in SIP messages are put at the end of a SIP URI after a '?'. The header is written on the form header_name=header_value and additional headers are separated by a '&'. Any characters not allowed in this header component according to RFC 3261 must be escaped with %HEX construction where HEX is the 2-digit hexadecimal number representing the escaped character. Specific to Internet Gate is that the string "%%__remove%%" put as header_value means the header should be removed. Also the Internet Gate supports variable substitution in the form $(variable_name) so the "$(" sequence is treated specially. If a specified header field is already present in the SIP request it is replace, else the header field is added. Variables that can be used for variable substitution are: | + | A generic SIP header manipulation tool for SIP requests passing through the box is available through configuration using the grammar for the header field component in a SIP URI using '?', '=', '%' and '&', as described in [[http://www.ietf.org/rfc/rfc3261.txt|RFC 3261]]. |
| + | |||
| + | In short, header fields for usage in SIP messages are put at the end of a SIP URI after a '?'. The header is written on the form header_name=header_value and additional headers are separated by a '&'. Any characters not allowed in this header component according to RFC 3261 must be escaped with %HEX construction where HEX is the 2-digit hexadecimal number representing the escaped character. | ||
| + | |||
| + | Specific to Internet Gate is that the string "%%__remove%%" put as header_value means the header should be removed. Also the Internet Gate supports variable substitution in the form $(variable_name) so the "$(" sequence is treated specially. If a specified header field is already present in the SIP request it is replace, else the header field is added. | ||
| + | |||
| + | Variables that can be used for variable substitution are: | ||
| * ruri.user = user from Request-URI | * ruri.user = user from Request-URI | ||
