Concepts & Examples ScreenOS Reference Guide

Volume 6: Voice-over-Internet Protocol

Release 6.2.0, Rev. 01

Juniper Networks, Inc.
1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408-745-2000

www.juniper.net
Part Number: 530-023768-01, Revision 01

Copyright Notice
Copyright © 2008 Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, JUNOS, NetScreen, ScreenOS, and Steel-Belted Radius are registered trademarks of Juniper Networks, Inc. in the United States and other countries. JUNOSe is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners. All specifications are subject to change without notice. Juniper Networks assumes no responsibility for any inaccuracies in this document or for any obligation to update information in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.

FCC Statement
The following information is for FCC compliance of Class A devices: This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. The equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case users will be required to correct the interference at their own expense. The following information is for FCC compliance of Class B devices: The equipment described in this manual generates and may radiate radio-frequency energy. If it is not installed in accordance with Juniper Networks’ installation instructions, it may cause interference with radio and television reception. This equipment has been tested and found to comply with the limits for a Class B digital device in accordance with the specifications in part 15 of the FCC rules. These specifications are designed to provide reasonable protection against such interference in a residential installation. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures: Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Consult the dealer or an experienced radio/TV technician for help. Connect the equipment to an outlet on a circuit different from that to which the receiver is connected. Caution: Changes or modifications to this product could void the user's warranty and authority to operate this device.

Disclaimer
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR JUNIPER NETWORKS REPRESENTATIVE FOR A COPY.

ii

Table of Contents
About This Volume vii Document Conventions................................................................................. viii Web User Interface Conventions ........................................................... viii Command Line Interface Conventions ................................................... viii Naming Conventions and Character Types .............................................. ix Illustration Conventions ............................................................................ x Requesting Technical Support .......................................................................... x Self-Help Online Tools and Resources....................................................... xi Opening a Case with JTAC ........................................................................ xi Document Feedback ....................................................................................... xi Chapter 1 H.323 Application Layer Gateway 1

Overview ......................................................................................................... 1 Alternate Gatekeeper ....................................................................................... 2 Examples ......................................................................................................... 2 Example: Gatekeeper in the Trust Zone ..................................................... 2 Example: Gatekeeper in the Untrust Zone ................................................. 4 Example: Outgoing Calls with NAT ............................................................ 5 Example: Incoming Calls with NAT............................................................ 8 Example: Gatekeeper in the Untrust Zone with NAT................................ 10 Chapter 2 Session Initiation Protocol Application Layer Gateway 15

Overview ....................................................................................................... 15 SIP Request Methods ............................................................................... 16 Classes of SIP Responses ......................................................................... 18 SIP Application Layer Gateway ................................................................ 19 Session Description Protocol Sessions ..................................................... 20 Pinhole Creation ...................................................................................... 21 Session Inactivity Timeout....................................................................... 22 SIP Attack Protection ............................................................................... 23 Example: SIP Protect Deny ............................................................... 23 Example: UDP Flooding Protection ................................................... 24 SIP with Network Address Translation ........................................................... 25 Outgoing Calls ......................................................................................... 26 Incoming Calls......................................................................................... 26 Forwarded Calls....................................................................................... 27 Call Termination ...................................................................................... 27 Call Re-INVITE Messages ......................................................................... 27 Call Session Timers.................................................................................. 27 Call Cancellation ...................................................................................... 27 Forking .................................................................................................... 28 SIP Messages ........................................................................................... 28 SIP Headers ............................................................................................. 28
Table of Contents

iii

..................................................................................................................... 82 About SCCP.................................................... 55 Bandwidth Management for VoIP Services .............................................................................. 30 Examples .................. 69 Call Agent ............................................................................................... 87 Example: Call Manager/TFTP Server in the Trust Zone......... 73 ISP-Hosted Service...................................................................................................................................... 33 Example: Incoming Call (Interface DIP)...................... 88 Example: Call Manager/TFTP Server in the Untrust Zone .................................. Call Manager/TFTP Server in the DMZ ................... 41 Example: Proxy in the Public Zone ....................................................................................... 83 Cluster ........................................................................................... 73 Media Gateway in Subscribers’ Homes—Call Agent at the ISP ......... 69 Call... 95 Example: Intrazone..................... 99 Example: Full-Mesh VPN for SCCP ....................................................................................................... 83 Call Manager .............. 92 Example: Intrazone.......................................................... 85 Media Setup .....Concepts & Examples ScreenOS Reference Guide SIP Body.............................. 39 Example: Proxy in the Private Zone ..........................................................................................................................................................................................83 SCCP Transactions......................................................................................................101 iv Table of Contents ................................................................................................................................................................................................................................. 69 Commands.. 67 MGCP Security ...... 64 Chapter 3 Media Gateway Control Protocol Application Layer Gateway 67 Overview .................... 87 Examples .................................................................................................... 86 SCCP Messages..................................................................................................... 84 Client Initialization ................................................................................................................ 68 About MGCP...................... Call Manager/TFTP Server in Untrust Zone ......................................................................................... Call Manager/TFTP Server in Trust Zone ............................................................ 32 Incoming SIP Call Support Using the SIP Registrar............................................................................. 83 SCCP Client ........... 34 Example: Incoming Call (DIP Pool).................................................. 44 Example: Untrust Intrazone ............ 72 Examples ............................................. 69 Connection ..........................................................37 Example: Incoming Call with MIP ..............................................................................................................................................................................................................................................70 Response Codes .......................................................................................................................................................................................................................................................................................... 68 Entities in MGCP........................................................................................................................... 68 Endpoint .......................... 49 Example: Trust Intrazone. 30 SIP NAT Scenario.................................................................... 76 Chapter 4 Skinny Client Control Protocol Application Layer Gateway 81 Overview ......................................................................................... 84 Client Registration.......................................................................................................................................... 53 Example: Full-Mesh VPN for SIP....................... 84 Call Setup...................... 81 SCCP Security ........................................... 85 SCCP Control Messages and RTP Flow...... 90 Example: Three-Zone.................. 83 SCCP Components........

........................120 Index.....................................IX-I Table of Contents v ................113 Scenario 2: Intrazone Call Within Private Network ............112 Configuration Examples .....117 Scenario 3: Users Across Different Networks ........................................................................................................................................................................Table of Contents Chapter 5 Apple iChat Application Layer Gateway 111 Overview ...............................................113 Scenario 1: Private–Public Network...............................................................111 Configuring the AppleiChat ALG ..............................................................................................................................

Concepts & Examples ScreenOS Reference Guide vi Table of Contents .

323 protocol and provides examples of typical scenarios.323 Application Layer Gateway. Examples of typical scenarios follow a summary of the MGCP architecture. Examples of typical scenarios follow a summary of the SIP architecture. Chapter 5. Chapter 3. “Apple iChat Application Layer Gateway. Chapter 2.” presents an overview of the Media Gateway Control Protocol (MGCP) ALG and lists the firewall security features of the implementation. “Skinny Client Control Protocol Application Layer Gateway. “Session Initiation Protocol Application Layer Gateway. “H.” describes the Session Initiation Protocol (SIP) and shows how the SIP ALG processes calls in route and Network Address Translation (NAT) modes. Chapter 4.” presents an overview of the AppleiChat ALG and lists the firewall security features of the implementation. “Media Gateway Control Protocol Application Layer Gateway.About This Volume Volume 6: Voice-over-Internet Protocol describes the supported VoIP Application Layer Gateways (ALGs) and contains the following chapters: Chapter 1.” describes the H. Examples of typical scenarios follow a summary of the SCCP architecture. vii . Examples of typical scenarios follow a summary of the AppleiChat architecture.” presents an overview of the Skinny Client Control Protocol (SCCP) ALG and lists the firewall security features of the implementation.

and follow the instructions on the page.Concepts & Examples ScreenOS Reference Guide Document Conventions This document uses the conventions described in the following sections: “Web User Interface Conventions” on page viii “Command Line Interface Conventions” on page viii “Naming Conventions and Character Types” on page ix “Illustration Conventions” on page x Web User Interface Conventions The Web user interface (WebUI) contains a navigational path and configuration settings. Select an option from the list. click the question mark (?) in the upper left of the screen.2. viii Document Conventions . begin by clicking a menu item in the navigation tree on the left side of the screen. The navigation tree also provides a Help > Config Guide configuration page to help you configure security policies and Internet Protocol Security (IPSec). then click OK: Address Name: addr_1 IP Address/Domain Name: IP/Netmask: (select). To enter configuration settings. Click the ? character in the upper left for Online Help on the Config Guide.2. with each page separated by angle brackets. 10. commands are in boldface type and variables are in italic type. Command Line Interface Conventions The following conventions are used to present the syntax of command line interface (CLI) commands in text and examples. The following example shows the WebUI path and parameters for defining an address: Policy > Policy Elements > Addresses > List > New: Enter the following. Anything inside square brackets [ ] is optional. As you proceed. In examples: Variables are in italic type.5/32 Zone: Untrust To open Online Help for configuration settings. In text. your navigation path appears at the top of the screen. Anything inside braces { } is required.

and Japanese. ScreenOS supports the following character types: Single-byte character sets (SBCS) and multiple-byte character sets (MBCS). for example. which have special significance as an indicator of the beginning or end of a name string that includes spaces. the following command means “set the management options for the ethernet1. For example.0/24 Any leading spaces or trailing text within a set of double quotes are trimmed. NOTE: A console connection only supports SBCS. each choice is separated by a pipe ( | ). VPN tunnels. Examples of SBCS are ASCII. Document Conventions ix .1. Examples of MBCS—also referred to as double-byte character sets (DBCS)—are Chinese. ASCII characters from 32 (0x20 in hexadecimals) to 255 (0xff). virtual systems. for example: set address trust “local LAN” 10. The WebUI supports both SBCS and MBCS. although many CLI keywords are case-insensitive. Name strings are case-sensitive. the entire string must be enclosed within double quotes. the ethernet2. Korean. For example. you only have to type enough letters to identify the word uniquely. However. Typing set adm u whee j12fmt54 will enter the command set admin user wheezer j12fmt54. “ local LAN ” becomes “local LAN”.1. auth servers. Naming Conventions and Character Types ScreenOS employs the following conventions regarding the names of objects—such as addresses. and zones—defined in ScreenOS configurations: If a name string includes one or more spaces. Multiple consecutive spaces are treated as a single space. European. all the commands documented in this guide are presented in their entirety.About This Volume If there is more than one choice. IKE gateways. and Hebrew. admin users. or the ethernet3 interface”: set interface { ethernet1 | ethernet2 | ethernet3 } manage NOTE: When entering a keyword. “local LAN” is different from “local lan”. depending on the character sets that your browser supports. except double quotes ( “ ).

juniper.pdf. Figure 1: Images in Illustrations Autonomous System or Virtual Routing Domain Local Area Network (LAN) with a Single Subnet or Security Zone Internet Dynamic IP (DIP) Pool Security Zone Interfaces: White = Protected Zone Interface (example = Trust Zone) Black = Outside Zone Interface (example = Untrust Zone) Policy Engine Generic Network Device Tunnel Interface Server VPN Tunnel Router Juniper Networks Security Devices Switch Hub Requesting Technical Support Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC). JTAC hours of operation—The JTAC centers have resources available 24 hours a day. 365 days a year. or are covered under warranty. 7 days a week.net/support/warranty/. and need postsales technical support. x Requesting Technical Support .Concepts & Examples ScreenOS Reference Guide Illustration Conventions Figure 1 shows the basic set of images used in illustrations throughout this volume.juniper. If you are a customer with an active J-Care or JNASC support contract. visit http://www.net/customers/support/downloads/710059. you can access our tools and resources online or open a case with JTAC. Product warranties—For product warranty information. JTAC policies—For a complete understanding of our JTAC procedures and policies. review the JTAC User Guide located at http://www.

net/customers/csc/software/ Search technical bulletins for relevant hardware and software notifications— http://www. Use the Case Manager tool in the CSC at http://www.juniper.juniper.net/alerts/ Join and participate in the Juniper Networks Community Forum— http://www.juniper.juniper.juniper.juniper.net/customers/support/requesting-support/. visit us at http://www.net/company/communities/ Open a case online in the CSC Case Manager— http://www. For international or direct-dial options in countries without toll-free numbers. use our Serial Number Entitlement (SNE) Tool— https://tools.About This Volume Self-Help Online Tools and Resources For quick and easy problem resolution.net/techpubs/ Find solutions and answer questions using our Knowledge Base— http://kb.net/customers/cm/ To verify service entitlement by product serial number.net/ Download the latest versions of software and review your release notes— http://www.juniper. and Mexico).net/customers/support/ Find product documentation—http://www.net/customers/cm/. Call 1-888-314-JTAC (1-888-314-5822—toll free in USA. Juniper Networks has designed an online self-service portal called the Customer Support Center (CSC) that provides you with the following features: Find CSC offerings—http://www. Canada.juniper.net/SerialNumberEntitlementSearch/ Opening a Case with JTAC You can open a case with JTAC on the Web or by telephone.juniper.juniper.net. Document Feedback If you find any errors or omissions in this document. contact Juniper Networks at techpubs-comments@juniper. Document Feedback xi .

Concepts & Examples ScreenOS Reference Guide xii Document Feedback .

admission. This chapter contains the following sections: “Overview” on page 1 “Alternate Gatekeeper” on page 2 Overview The H. although it is possible to make configurations for other hosts that use VoIP.323 Application Layer Gateway (ALG) on a Juniper Networks security device. In such a telephony system. Overview 1 . such as NetMeeting multimedia devices.323 Application Layer Gateway This chapter describes the H. Gatekeepers can reside in the two different zones or in the same zone. and call status for VoIP calls. gatekeeper devices manage call registration.323 Protocol Gatekeeper Gatekeeper Permit Trust Zone Permit Endpoint Endpoint Internet Untrust Zone NOTE: Illustrations in this chapter use IP phones for illustrative purposes.323 Application Layer Gateway (ALG) allows you secure voice over IP (VoIP) communication between terminal endpoints such as IP phones and multimedia devices.Chapter 1 H. Figure 2: H.323 protocol and provides examples for configuring the H.

Admission. the primary gatekeeper sends Gatekeeper Confirm (GCF) and Registration Confirm (RCF) messages to the endpoint.5) in the Untrust zone.323 ALG supports the gatekeeper and the alternate gatekeeper in the same zone. the security device can be in either transparent or route mode. If the primary gatekeeper fails. These messages contain the list of available alternate gatekeepers. The alternate gatekeeper provides high availability. and an IP phone host (2. you need to configure a security policy that allows the endpoint device to reach the alternate gatekeeper when the endpoint cannot reach the primary gatekeeper. you set up two policies that allow H. 2 Alternate Gatekeeper . You can configure the primary and alternate gatekeepers in the Trust. To use the alternate gatekeeper feature. NOTE: Currently. During the registration process.2. Both the Trust and Untrust security zones are in the trust-vr routing domain. the Juniper Networks H. or DMZ zones. Examples This section contains the following configuration scenarios: “Example: Gatekeeper in the Trust Zone” on page 2 “Example: Gatekeeper in the Untrust Zone” on page 4 “Example: Outgoing Calls with NAT” on page 5 “Example: Incoming Calls with NAT” on page 8 “Example: Gatekeeper in the Untrust Zone with NAT” on page 10 Example: Gatekeeper in the Trust Zone In the following example. and Status (RAS) protocol before they can attempt calls between them.323 ALG in ScreenOS supports the use of an alternate gatekeeper. IP-enabled phones and other multimedia devices registered with that gatekeeper are registered with the alternate gatekeeper. In this example. redundancy and scalability for the IP end points.323 traffic to pass between IP phone hosts and a gatekeeper in the Trust zone.Concepts & Examples ScreenOS Reference Guide Alternate Gatekeeper The H. Untrust.2. All the IP end points must register with a gatekeeper through the Registration.

5/32 Zone: Untrust 2. 2.323 Application Layer Gateway Figure 3: H. Policies Policies > (From: Trust.2. IP_Phone Service: H. Address set address untrust IP_Phone 2.5 Endpoint IP Phones WebUI 1. then click OK: Source Address: Address Book Entry: (select).Chapter 1: H.323 Action: Permit CLI 1. then click OK: Address Name: IP_Phone IP Address/Domain Name: IP/Netmask: (select). then click OK: Source Address: Address Book Entry: (select).2. Address Policy > Policy Elements > Addresses > List > New: Enter the following.323 Gatekeeper in the Trust Zone Trust Zone Gatekeeper Untrust Zone Internet Endpoint IP Phone 2. Any Service: H. IP_Phone Destination Address: Address Book Entry: (select).5/32 2.2. To: Trust) New: Enter the following.323 Action: Permit Policies > (From: Untrust.323 permit save Examples 3 .2. Policies set policy from trust to untrust any IP_Phone h.2.323 permit set policy from untrust to trust IP_Phone any h.2. Any Destination Address: Address Book Entry: (select). To: Untrust) New: Enter the following.

10/32 Zone: Untrust 2.2. you set up two policies to allow H. To: Trust) New: Enter the following. then click OK: Address Name: IP_Phone IP Address/Domain Name: IP/Netmask: (select). 2.Concepts & Examples ScreenOS Reference Guide Example: Gatekeeper in the Untrust Zone Because transparent and route modes do not require address mapping of any kind. IP_Phone Destination Address: Address Book Entry: (select). and the IP phone at IP address 2. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following. then click OK: Source Address: Address Book Entry: (select).2. Figure 4: H. Policies Policies > (From: Trust.5/32 WebUI 1.2. security device configuration for a gatekeeper in the Untrust zone is usually identical to the configuration for a gatekeeper in the Trust zone. To: Untrust) New: Enter the following.2. then click OK: Address Name: Gatekeeper IP Address/Domain Name: IP/Netmask: (select).2.323 Action: Permit Policies > (From: Untrust. then click OK: Source Address: Address Book Entry: (select). The device can be in transparent or route mode. Any Destination Address: Address Book Entry: (select). Any 4 Examples . IP_Phone Service: H.2.2.2. 2.5 (and the gatekeeper) in the Untrust zone.323 Gatekeeper in the Untrust Zone Trust Zone LAN Untrust Zone Internet IP_Phones IP_Phone 2. In the following example. Both the Trust and Untrust security zones are in the trust-vr routing domain.323 traffic to pass between IP phone hosts in the Trust zone.5/32 Zone: Untrust Policy > Policy Elements > Addresses > List > New: Enter the following.

25 MIP 1.323 permit IP_Phone any h.1. Addresses set address untrust IP_Phone 2.5 MIP 1.323 permit Example: Outgoing Calls with NAT When the security device uses NAT (Network Address Translation).5) is in the Untrust zone.2. IP_Phone2 (2.1.2.1.2.250 ethernet3 1.1. the devices in the Trust zone include the endpoint host (10.1.25).1.323 Application Layer Gateway Service: H. then click OK: Source Address: Address Book Entry: (select). Policies set policy from trust to untrust set policy from trust to untrust set policy from untrust to trust set policy from untrust to trust save any IP_Phone h. To: Untrust) New: Enter the following.1. Gatekeeper Service: H.5 Examples 5 .2.1. Both the Trust and Untrust security zones are in the trust-vr routing domain.323 Action: Permit CLI 1.10/32 2.25 -> 10.2.1. When you set a security device in NAT mode.1. and when it is in the Untrust zone it has a public address.2. You configure the security device to allow traffic between the endpoint host IP_Phone1 and the gatekeeper in the Trust zone and the endpoint host IP_Phone2 in the Untrust zone.1. you must map a public IP address to each device that needs to receive incoming traffic with a private address.1. Figure 5: Network Address Translation—Outgoing Calls ethernet1 10.323 Action: Permit Policies > (From: Trust.5 Gateway 1.2.5 -> 10.1.1.1. In this example.1.1.1.1/24 Trust Zone Gatekeeper 10. Any Destination Address: Address Book Entry: (select). a gatekeeper or endpoint device in the Trust zone has a private address.1.323 permit gatekeeper any h.1/24 Untrust Zone Internet IP_Phone2 2.Chapter 1: H.323 permit any gatekeeper h.5) and the gatekeeper device (10.5/32 set address untrust gatekeeper 2.1.1.2.1.25 IP_Phone1 10.

25/32 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following. then click OK: Address Name: IP_Phone2 IP Address/Domain Name: IP/Netmask: (select).1.1.1. then click OK: Zone Name: Untrust Static IP: (select this option when present) IP Address/Netmask: 1.1.1. 2.1.1.1.255.Concepts & Examples ScreenOS Reference Guide WebUI 1. 10. 10.1. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following.255 Host IP Address: 10. Mapped IP Addresses Network > Interfaces > Edit (for ethernet3) > MIP > New: Enter the following.5/32 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following.255. then click OK: Address Name: Gatekeeper IP Address/Domain Name: IP/Netmask: (select).5/32 Zone: Untrust 3.1/24 2. then click Apply: Zone Name: Trust Static IP: (select this option when present) IP Address/Netmask: 10.1.1.1/24 Select the following.5 Netmask: 255. then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet3): Enter the following. then click OK: Address Name: IP_Phone1 IP Address/Domain Name: IP/Netmask: (select).2. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.5 Host Virtual Router Name: trust-vr 6 Examples .1. then click OK: Mapped IP: 1.2.

1. MIP(1.1.25) Service: H.Chapter 1: H.250 5. IP_Phone2 Service: H. To: Untrust) New: Enter the following.1. then click OK: Source Address: Address Book Entry: (select). To: Untrust) New: Enter the following.323 Action: Permit Policies > (From: Untrust.5) Service: H.255. then click OK: Source Address: Address Book Entry: (select). then click OK: Mapped IP: 1. Route Network > Routing > Destination > trust-vr New: Enter the following.1. then click OK: Network Address/Netmask: 0. To: Trust) New: Enter the following.1.323 Action: Permit Policies > (From: Untrust.1.0. Gatekeeper Destination Address: Address Book Entry: (select).0.1.25 Netmask: 255.0/0 Gateway: (select) Interface: ethernet3 Gateway IP Address: 1. IP_Phone2 Service: H. then click OK: Source Address: Address Book Entry: (select).1.323 Action: Permit Policies > (From: Trust. IP_Phone2 Destination Address: Address Book Entry: (select). MIP(1.1.323 Application Layer Gateway Network > Interfaces > Edit (for ethernet3) > MIP > New: Enter the following.255 Host IP Address: 10.255.1. IP_Phone2 Destination Address: Address Book Entry: (select).323 Action: Permit Examples 7 . Policies Policies > (From: Trust. then click OK: Source Address: Address Book Entry: (select). To: Trust) New: Enter the following.25 Host Virtual Router Name: trust-vr 4. IP_Phone1 Destination Address: Address Book Entry: (select).

1.1/24 set interface ethernet3 zone untrust set interface ethernet3 ip 1.323 permit set policy from untrust to trust IP_Phone2 mip (1. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.2. where a DIP pool provides source addresses only.323 permit set policy from untrust to trust IP_Phone2 mip(1. or other VoIP (Voice-over-IP) protocols.1.5) h.1/24 Trust Zone ethernet3 1.1.1.1.5/32 set address trust gatekeeper 10.1.5 host 10.323 permit set policy from trust to untrust gatekeeper IP_Phone2 h.25 4.1.2.1. The following example uses DIP in an H.1.1.1.250 5.323 VoIP configuration.0/0 interface ethernet3 gateway 1. This differs from most configurations.1. Policies set policy from trust to untrust IP_Phone1 IP_Phone2 h.0.25/32 set address untrust IP_Phone2 2.1. Mapped IP Addresses set interface ethernet3 mip 1. Figure 6: Network Address Translation—Incoming Calls ethernet1 10.5 set interface ethernet3 mip 1.1/24 Untrust Zone Internet LAN DIP Pool ID 5 1.1. together with the services H. you configure the security device to accept incoming calls over a NAT boundary.1. or DIP(interface) when the DIP pool uses the same address as an interface IP address.1.1.1/24 2. Route set vrouter trust-vr route 0. SIP. Addresses set address trust IP_Phone1 10. to support incoming calls. The keyword “incoming” instructs the device to add the DIP and interface addresses to the global zone.1. 8 Examples .1.Concepts & Examples ScreenOS Reference Guide CLI 1.1.1.0. You can use such address entries as destination addresses in policies.1.5/32 3.12 ~ 1.1.1.1.1. you can create a DIP address pool for dynamically allocating destination addresses.150 The name of the DIP pool can be DIP(id_num) for a user-defined DIP.1.1. To do this.25) h.1.25 host 10.323 permit save Example: Incoming Calls with NAT In this example.323.1.

2. Any Service: H.323 Action: Permit Examples 9 .323 Application Layer Gateway WebUI 1.1/24 2.1.Chapter 1: H.2.1. then click OK: ID: 5 IP Address Range: (select). then click OK: Zone Name: Untrust Static IP: (select this option when present) IP Address/Netmask: 1.1.1. IP_Phones1 Destination Address: Address Book Entry: (select). then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet3): Enter the following.12 ~ 1. then click OK: Source Address: Address Book Entry: (select). Addresses Policy > Policy Elements > Addresses > List > New (for Trust): Enter the following.5/32 Zone: Untrust 4. then click OK: Address Name: IP_Phones1 IP Address/Domain Name: IP/Netmask: (select).1.1/24 Enter the following.1.1. To: Untrust) New: Enter the following.1. 10. DIP with Incoming NAT Network > Interface > Edit (for ethernet3) > DIP > New: Enter the following.1. Policies Policies > (From: Trust.5/24 Zone: Trust Policy > Policy Elements > Addresses > List > New (for Untrust): Enter the following. 1.1. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.150 Port Translation: (select) In the same subnet as the interface IP or its secondary IPs: (select) Incoming NAT: (select) 3. then click OK: Address Name: IP_Phone2 IP Address/Domain Name: IP/Netmask: (select).2. then click Apply: Zone Name: Trust Static IP: (select this option when present) IP Address/Netmask: 10.

1/24 Gateway 1.12 1.1.2.2.250 Gatekeeper 2. then click OK: Source Address: Address Book Entry: (select).25) and host IP_Phone2 (2.150 incoming 3.5) are in the Untrust zone and host IP_Phone1 (10.5/32 4.1.323 nat src dip 5 permit set policy from untrust to trust IP_Phone2 dip(5) h. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.1.1.1. DIP with Incoming NAT set interface ethernet3 dip 5 1. DIP(5) Service: H. the gatekeeper device (2.1.25 Untrust Zone Internet IP_Phone2 2.1. To: Trust) New: Enter the following. You configure the security device to allow traffic between host IP_Phone1 in the Trust zone and host IP_Phone2 (and the gatekeeper) in the Untrust zone.1.1.1.1. Policies set policy from trust to untrust IP_Phones1 any h.5/24 set address untrust IP_Phone2 2.5 -> 10.1.1/24 set interface ethernet3 zone untrust set interface ethernet3 ip 1.1.1.323 Action: Permit CLI 1. Figure 7: Gatekeeper in the Untrust Zone ethernet1 10. Both the Trust and Untrust security zones are in the trust-vr routing domain. Addresses set address trust IP_Phones1 10.2.1.1.1.5 MIP 1.2.2.1/24 NAT Mode Trust Zone LAN ethernet3 1.2. IP_Phone2 Destination Address: Address Book Entry: (select).1.1.323 permit save Example: Gatekeeper in the Untrust Zone with NAT In this example.2.5) is in the Trust zone.1.1.Concepts & Examples ScreenOS Reference Guide Policies > (From: Untrust.2.1.1.2.2.1/24 2.1.5 IP_Phone1 10.5 10 Examples .

255 Host IP Address: 10. then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet3): Enter the following. then click OK: Zone Name: Untrust Static IP: (select this option when present) IP Address/Netmask: 1.323 Application Layer Gateway WebUI 1.1. 2.255. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following. Mapped IP Address Network > Interfaces > Edit (for ethernet3) > MIP > New: Enter the following.2.1.1.2.255.2.1.1.25/32 Zone: Untrust Policy > Policy Elements > Addresses > List > New: Enter the following.5 Netmask: 255.2. then click Apply: Zone Name: Trust Static IP: (select this option when present) IP Address/Netmask: 10. then click OK: Address Name: IP_Phone2 IP Address/Domain Name: IP/Netmask: (select). then click OK: Address Name: Gatekeeper IP Address/Domain Name: IP/Netmask: (select).1.1. then click OK: Address Name: IP_Phone1 IP Address/Domain Name: IP/Netmask: (select).1. 2.5/32 Zone: Untrust 3.5 Examples 11 .Chapter 1: H.1.1/24 Enter the following.5/32 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following.1. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following. 10. then click OK: Mapped IP: 1.1/24 2.

MIP(1.1.250 5. IP_Phone1 Destination Address: Address Book Entry: (select). Policies Policies > (From: Trust.323 Action: Permit CLI 1. then click OK: Source Address: Address Book Entry: (select).1. Addresses set address trust IP_Phone1 10.323 Action: Permit Policies > (From: Untrust.0. To: Trust) New: Enter the following.5) Service: H. then click OK: Source Address: Address Book Entry: (select). Route Network > Routing > Destination > trust-vr New: Enter the following.323 Action: Permit Policies > (From: Untrust.Concepts & Examples ScreenOS Reference Guide 4. MIP(1.5/32 set address untrust gatekeeper 2. then click OK: Source Address: Address Book Entry: (select).5) Service: H.1/24 set interface ethernet3 zone untrust set interface ethernet3 ip 1.2.1.1.1/24 2. then click OK: Network Address/Netmask: 0. To: Trust) New: Enter the following.1.1.1. then click OK: Source Address: Address Book Entry: (select).2. IP_Phone2 Service: H.5/32 12 Examples .1.0.1.1. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10. Gatekeeper Service: H. IP_Phone1 Destination Address: Address Book Entry: (select).323 Action: Permit Policies > (From: Trust.1.25/32 set address untrust IP_Phone2 2. To: Untrust) New: Enter the following.2. Gatekeeper Destination Address: Address Book Entry: (select).1.0/0 Gateway: (select) Interface: ethernet3 Gateway IP Address: 1. To: Untrust) New: Enter the following.2. IP_Phone2 Destination Address: Address Book Entry: (select).

1.5) h.323 permit set policy from untrust to trust gatekeeper mip(1.5) h.5 4.1.323 permit set policy from trust to untrust IP_Phone1 gatekeeper h.5 host 10. Policies set policy from trust to untrust IP_Phone1 IP_Phone2 h.1.1.250 5.1. Route set vrouter trust-vr route 0.1.1. Mapped IP Addresses set interface ethernet3 mip 1.Chapter 1: H.1.0.323 permit save Examples 13 .323 Application Layer Gateway 3.1.323 permit set policy from untrust to trust IP_Phone2 mip(1.1.0/0 interface ethernet3 gateway 1.0.

Concepts & Examples ScreenOS Reference Guide 14 Examples .

SDP provides information that a system can use to join a multimedia session. times. modifying. or multimedia. port numbers. with features such as instant messaging and application-level mobility in network environments. voice or video. Juniper Networks security devices support SIP as a service and can screen SIP traffic. and terminating multimedia sessions over the Internet. during the session.Chapter 2 Session Initiation Protocol Application Layer Gateway This chapter describes the Session Initiation Protocol (SIP) Application Layer Gateway (ALG) and contains the following sections: “Overview” on page 15 “SIP with Network Address Translation” on page 25 “Examples” on page 32 Overview Session Initiation Protocol (SIP) is an Internet Engineering Task Force (IETF)-standard protocol for initiating. Overview 15 . Note that the IP address and port number in the SDP header (the “c=” and “m=” fields. SDP might include information such as IP addresses. for example. Session-description information is included in INVITE and ACK messages and indicates the multimedia type of the session. to negotiate and modify the parameters of the session. SIP’s primary function is to distribute session-description information and. allowing and denying it based on a policy that you configure. SIP is a predefined service in ScreenOS and uses port 5060 as the destination port. the Juniper Networks SIP ALG supports only Session Description Protocol (SDP). respectively) are the address and port where the client wants to receive the media streams and not the IP address and port number from which the SIP request originates (although they can be the same). and dates. telephony. SIP is also used to terminate a multimedia session. Although SIP can use different description protocols to describe the session. See “Session Description Protocol Sessions” on page 20 for more information. Such sessions might include conferencing.

Route. To. and a User Agent Server (UAS). session description protocols. the SIP ALG translates the From. which listens to the responses and notifies the user when they arrive. and Record-Route header fields are modified as shown in Table 2 on page 29. the IP addresses in the Via. BYE—A user sends a BYE request to abandon a session. and Record-Route header fields are modified as shown in Table 2 on page 29. A BYE request from either user automatically terminates the session. Call-ID. From. In NAT mode. To. To. CANCEL—A user can send a CANCEL request to cancel a pending INVITE request. Contact. ACK—The user from whom the INVITE originated sends an ACK request to confirm reception of the final response to the INVITE request. A User Agent (UA) is an application that runs at the endpoints of the call and consists of two parts: the User Agent Client (UAC). Examples of UAs are SIP proxy servers and phones. ScreenOS supports the following method types and response codes: INVITE—A user sends an INVITE request to invite another user to participate in a session. In NAT mode. when the OPTIONS request is sent from a UA outside NAT to a proxy inside NAT. which sends SIP requests on behalf of the user. and Call-ID fields as shown in Table 2 on page 29.Concepts & Examples ScreenOS Reference Guide SIP messages consist of requests from a client to a server and responses to the requests from a server to a client with the purpose of establishing a session (or a call). each of which contains a method field that denotes the purpose of the message. In NAT mode. A CANCEL request has no effect if the SIP server processing the INVITE had sent a final response for the INVITE before it received the CANCEL. When the UA is inside NAT and the proxy is outside NAT. To. the ACK request must include it. From. and message encoding it supports. If the original INVITE request did not contain the session description. the SIP ALG translates the address in the Request-URI and the IP address in the To: field to the appropriate IP address of the internal client. 16 Overview . the IP addresses in the Via. the IP addresses in the Via. Route. Contact. From. Route. and Record-Route header fields are modified as shown in Table 2 on page 29. the IP addresses in the Via. Call-ID. Contact. In NAT mode. From. SIP Request Methods The SIP transaction model includes a number of request and response messages. OPTIONS—Used by the User Agent (UA) to obtain information about the capabilities of the SIP proxy. A server responds with information about what methods. Call-ID. The body of an INVITE request may contain the description of the session. Via. and Record-Route header fields are modified as shown in Table 2 on page 29. Contact. In NAT mode. Route. Call-ID.

4xx. Route. In NAT mode. For example. the IP address in the Request-URI: header field is changed to a private IP address if the message is coming from the external network into the internal network. No translation is needed for the outgoing response. to user C. 1xx. Refer—Used to refer the recipient (identified by the Request-URI) to a third party by the contact information provided in the request. in the Request-URI. 6xx Response Codes—Used to indicate the status of a transaction. In NAT mode. however.. who is also in the private network. and Record-Route header fields are modified as shown in Table 2 on page 29. In NAT mode. 3xx. Route. REGISTER requests are handled as follows: REGISTER requests from an external client to an internal registrar—When the SIP ALG receives the incoming REGISTER request it translates the IP address. the IP addresses in the Via. Contact. Incoming REGISTER messages are allowed only to a MIP or VIP address. Call-ID. From. Call-ID. From. Contact. Header fields are modified as shown in Table 2 on page 29. Contact. To. To. From. and Contact header fields. and Record-Route header fields are modified as shown in Table 2 on page 29. If user C is registered with a registrar. A SIP registrar server records all the information it receives in REGISTER requests and makes this information available to any SIP server attempting to locate a user. and Record-Route header fields are modified as shown in Table 2 on page 29. and Record-Route header fields are modified as shown in Table 2 on page 29. In NAT mode. The IP addresses in the Via. Route. Call-ID. the IP address in the Request-URI is changed to a private IP address if the message is coming from the external network into the internal network. 202. the address in the Request-URI is changed to a private IP address if the messages is coming from the external network into the internal network. The IP address in the Via. To. To. Subscribe—Used to request current state and state updates from a remote node. and Record-Route header fields are modified as shown in the table in Table 2 on page 29. Overview 17 . Route. if any. Info—Used to communicate mid-session signaling information along the signaling path for the call. Update—Used to open pinhole for new or updated SDP information. Call-ID. Contact. 2xx. The Via. in a public network. Contact. A backward translation is performed for the incoming response. In NAT mode. The IP addresses in Via. From. 5xx.Chapter 2: Session Initiation Protocol Application Layer Gateway REGISTER—A user sends a REGISTER request to a SIP registrar server to inform it of the current location of the user. Call-ID. if user A in a private network refers user B. Call-ID. Notify—Sent to inform subscribers of changes in state to which the subscriber has a subscription. REGISTER requests from an internal client to an external registrar—When the SIP ALG receives the outgoing REGISTER request it translates the IP addresses in the To. To. From. From. Route. its port mapping is stored in the ALG NAT table and is reused to perform the translation. Via. the SIP ALG allocates a new IP address and port number for user C so that user C can be contacted by user B.

Success (200 to 299)—Action successfully received. Table 1 provides a complete list of current SIP responses. understood. and accepted. SIP responses are grouped into the following classes: Informational (100 to 199)—Request received. continuing to process the request. Server Error (500 to 599)—Server failed to fulfill an apparently valid request. Client Error (400 to 499)—Request contains bad syntax or cannot be fulfilled at this server. Redirection (300 to 399)—Further action required to complete the request. Global Failure (600 to 699)—Request cannot be fulfilled at any server. all of which are supported on Juniper Networks security devices. Table 1: Session Initiation Protocol Responses Class Informational Response Code-Reason Phrase 100 Trying 182 Queued Response Code-Reason Phrase 180 Ringing 183 Session progress 202 Accepted 301 Moved permanently 380 Alternative service 401 Unauthorized 404 Not found 407 Proxy authentication required 410 Gone 414 Request-URL too large 480 Temporarily not available 483 Too many hops 486 Busy here Response Code-Reason Phrase 181 Call is being forwarded Success Redirection 200 OK 300 Multiple choices 305 Use proxy 302 Moved temporarily Client Error 400 Bad request 403 Forbidden 406 Not acceptable 409 Conflict 413 Request entity too large 420 Bad extension 482 Loop detected 485 Ambiguous 488 Not acceptable here 402 Payment required 405 Method not allowed 408 Request time-out 411 Length required 415 Unsupported media type 481 Call leg/transaction does not exist 484 Address incomplete 487 Request canceled Server Error 500 Server internal error 502 Service unavailable 501 Not implemented 504 Gateway time-out 603 Decline 502 Bad gateway 505 SIP version not supported 604 Does not exist anywhere Global Failure 600 Busy everywhere 606 Not acceptable 18 Overview .Concepts & Examples ScreenOS Reference Guide Classes of SIP Responses SIP responses provide status information about SIP transactions and include a response code and a reason phrase.

which the SIP ALG records in a pinhole table. the SIP ALG permits it through the firewall but generates a log message informing the user that it cannot process the packet. You can simply create a policy that permits SIP service. The media stream carries the data (audio data. For SIP messages that do not contain SDP. If a security device receives a SIP message in which SDP is encrypted. This policy enables the security device to intercept SIP traffic and do one of the following actions: permit or deny the traffic or enable the SIP ALG to open pinholes to pass the media stream. The SIP ALG uses the IP addresses and port numbers recorded in the pinhole table to open pinholes and allow media streams to traverse the security device. and a parser extracts information such as IP addresses and port numbers. The SIP ALG needs to open pinholes only for the SIP requests and responses that contain media information (SDP). the security device invokes the SIP ALG. the signaling and the media stream. SIP signaling traffic consists of request and response messages between client and server and uses transport protocols such as User Datagram Protocol (UDP) or Transmission Control Protocol (TCP). The SIP ALG monitors SIP transactions and dynamically creates and manages pinholes based on the information it extracts from these transactions. however. The SIP ALG intercepts SIP messages that contain SDP and.Chapter 2: Session Initiation Protocol Application Layer Gateway SIP Application Layer Gateway There are two types of SIP traffic. The media stream. NOTE: Juniper Networks security devices do not support encrypted SDP. and the security device filters SIP signaling traffic like any other type of traffic. extracts the information it requires to create pinholes. The Juniper Networks SIP ALG supports all SIP methods and responses (see “SIP Request Methods” on page 16 and “Classes of SIP Responses” on page 18). permitting or denying it. The SIP ALG examines the SDP portion of the packet. Juniper Networks security devices support SIP signaling messages on port 5060. uses dynamically assigned port numbers that can change several times during the course of a call. The SIP ALG reads SIP messages and their SDP content and extracts the port-number information it needs to dynamically open pinholes and let the media stream traverse the security device. for example) and uses Application Layer protocols such as Real Time Protocol (RTP) over UDP. Overview 19 . The SIP ALG for IPv6 supports Netscreen Redundancy Protocol (NSRP). If SDP is encrypted. it is impossible to create a static policy to control media traffic. You can allow SIP transactions to traverse the Juniper Networks firewall by creating a static policy that permits SIP service. Without fixed ports. In this case. NOTE: We refer to a pinhole as the limited opening of a port to allow exclusive traffic. As a result. the security device simply lets them through. using a parser. the media content that SDP describes cannot traverse the security device. the SIP ALG cannot extract the information it needs from SDP to open pinholes.

Therefore. In this release of ScreenOS. It displays in this format: c=<network type><address type><connection address> Currently. the destination IP address can also be a multicast IP address. while the media-level information applies to a particular media stream. the port number for RTCP is one higher than the RTP port number. the media-level information begins with the m= field. but ScreenOS does not currently support multicast with SIP. The port number indicates the destination (not the origin) of the media stream. NOTE: Generally. If the destination IP address is a unicast IP address. and a unicast IP address or domain name as the destination (connection) IP address. It displays in this format: m=<media><port><transport><fmt list> Currently. the security device supports only “audio” as the media and “RTP” as the Application Layer transport protocol. 20 Overview . and might contain media-level information. two are particularly useful to the SIP ALG because they contain Transport Layer information. An SDP session description always contains session-level information. The two fields are the following: c= for connection information This field can appear at the session or media level. Of the many fields in the SDP description. which appears at the beginning of the description. Every RTP session has a corresponding Real Time Control Protocol (RTCP) session. the SIP ALG must reserve ports (create pinholes) for both RTP and RTCP traffic. The session-level information applies to the whole session. which comes after. It can contain session-level and media-level information.Concepts & Examples ScreenOS Reference Guide Session Description Protocol Sessions An SDP session description is text-based and consists of a set of lines. m= for media announcement This field appears at the media level and contains the description of the media. NOTE: In the SDP session description. the security device opens ports only for RTP and RTCP. whenever a media stream uses RTP. "IP4 and IP6" as address types. the SIP ALG creates pinholes using the IP address and port numbers specified in the media description field m=. By default. the security device supports "IN" (for Internet) as the network type. The format list (fmt list) provides information about the Application Layer protocol that the media uses.

Overview 21 . Figure 8 describes a call setup between two SIP clients and how the SIP ALG creates pinholes to allow RTP and RTCP traffic. The IP address comes from the c= field in the SDP session description. the destination IP address can also be a multicast IP address. thus opening port 5060 for SIP signaling messages. This information comes from the SDP session description and parameters on the security device: Protocol: UDP. the SIP ALG removes the pinhole. immediately afterwards the SIP ALG removes the pinhole for the direction from which the packet came. Destination port: The parser extracts the destination port number for RTP from the m= field in the media level and calculates the destination port number for RTCP using the following formula: RTP port number + one Lifetime: This value indicates the length of time (in seconds) during which a pinhole is open to allow a packet through. When the lifetime expires. and the SIP ALG uses it to create a pinhole for the media. the parser extracts that IP address. Pinhole Creation Both pinholes for the RTP and RTCP traffic share the same destination IP address. A packet must go through the pinhole before the lifetime expires. Source IP: Unknown. Destination IP: The parser extracts the destination IP address from the c= field in the media or session level. this indicates an error in the protocol stack. the parser determines the IP address based on the following rules (in accordance with SDP conventions): First. The illustration assumes that the security device has a policy that permits SIP. If there is one. Source port: Unknown. The following lists the information the SIP ALG needs to create a pinhole. the SIP ALG parser extracts the IP address from the c= field in the session level. Because the c= field can appear in either the session-level or media-level portion of the SDP session description. If there is no c= field in the media level. When a packet goes through the pinhole within the lifetime period. but ScreenOS does not currently support multicast with SIP.Chapter 2: Session Initiation Protocol Application Layer Gateway NOTE: Generally. and the security device drops the packet and logs the event. and the SIP ALG uses it to create a pinhole for the media. the SIP ALG parser verifies if there is a c= field containing an IP address in the media level. If the session description does not contain a c= field in either level.

0.2 1.2. When managing the sessions.1. If User B sends media anyway.0. Client B sends the media traffic (RTP/RTCP) to Client A through pinhole 1 12.2. Per SDP. which indicates that the session is on hold. consuming resources on the security device. Per SDP. Session Inactivity Timeout Typically a call ends when one of the clients sends a BYE or CANCEL request. Doing so indicates to User B not to send any media until further notice. In this case. for example.2: 3000) 10.1:2000) 2. SIP ALG creates a pinhole for 1.1.1.1 Trust Zone Security Device SIP Proxy Untrust Zone Client B 2. Client A sends the media traffic (RTP/RTCP) to Client B through pinhole 2 Pinhole 2 NOTE: The SIP ALG does not create pinholes for RTP and RTCP traffic when the destination IP address is 0. Settings such as the inactivity timeout apply to a group as opposed to each session.2: 3000 6.2.1: 2000 3. Client B replies to the SIP proxy with a Ringing response 5. The SIP proxy forwards a 200 OK response from Client B to Client A through the security device 9. The SIP ALG intercepts the BYE or CANCEL request and removes all media sessions for that call.Concepts & Examples ScreenOS Reference Guide Figure 8: SIP ALG Call Setup Client A 1.0.2. SIP ALG creates pinhole for 2. the call might go on indefinitely. a power failure. A call can have one or more voice channels. There could be reasons or problems preventing clients in a call from sending BYE or CANCEL requests.2.0. the security device considers the sessions in each voice channel as one group. for example.2.Client A sends an INVITE request destined for Client B to the SIP proxy through port 5060 on the security device (SDP 1.0. during a telephone communication. one for RTP and one for RTCP. the security device drops the packets. To put a session on hold. Client A sends an ACK response destined for Client B to the SIP proxy through port 5060 on the security device 7.1. 22 Overview . The SIP proxy forwards an INVITE request to Client B 4. Each voice channel has two sessions (or two media streams).1.0. The inactivity-timeout feature helps the security device to monitor the liveliness of the call and terminate it if there is no activity for a specific period of time.1. a user (User A) sends the other user (User B) a SIP message in which the destination IP address is 0. The SIP proxy forwards the ACK response to Client B Pinhole 1 11. Client B sends a 200 OK response to the SIP proxy in reply to the INVITE request (SDP: 2. The SIP proxy forwards the Ringing response from Client B to Client A through port 5060 on the security device 8.

If a reply contains a 3xx. Packets are dropped for a period of 5 seconds. you configure the security device to protect a single SIP proxy server (1.1. If either of these timeouts expires. you can use the sip protect deny command to configure the security device to monitor INVITE requests and proxy server replies to them.1.1. whether malicious or through client or server error.3/24) from repeat SIP requests to which it has already denied service. You can also configure the security device to monitor INVITE request to a specific proxy server by specifying the destination IP address.3/24 set alg sip protect deny timeout 5 save Overview 23 . for a configurable number of seconds (the default is 3). 4xx. the security device checks all INVITE requests against this table and.Chapter 2: Session Initiation Protocol Application Layer Gateway There are two types of inactivity timeouts that determine the lifetime of a group: Signaling-inactivity timeout: This parameter indicates the maximum length of time (in seconds) a call can remain active without any SIP-signaling traffic.1. after which the security device resumes forwarding INVITE requests from those sources. SIP attack protection is configured globally. the security device removes all sessions for this call from its table. thus terminating the call. Example: SIP Protect Deny In this example. discards any packets that match entries in the table. Each time an RTP or RTCP packet occurs within a call. or 5xx response code (see “Classes of SIP Responses” on page 18). this timeout resets. SIP Attack Protection The ability of the SIP proxy server to process calls can be affected by repeat SIP INVITE requests. Subsequently. The sip protect deny command supports both IPv4 and IPv6 addresses. this timeout resets. The default setting is 43200 seconds (12 hours). that it initially denied. To prevent the SIP proxy server from being overwhelmed by such requests. The default setting is 120 seconds. WebUI You must use the CLI to protect SIP proxy servers from being inundated by SIP messages. CLI set alg sip app-screen protect deny dst-ip 1. Each time a SIP-signaling message occurs within a call. Media-inactivity timeout: This parameter indicates the maximum length of time (in seconds) a call can remain active without any media (RTP or RTCP) traffic within a group. the ALG stores the source IP address of the request and the IP address of the proxy server in a table.

5 threshold 80000 save 24 Overview . CLI set alg sip signaling-inactivity-timeout 30000 set alg sip media-inactivity-timeout 90 save Example: UDP Flooding Protection You can protect the security device against UDP flooding by zone and destination address.000 seconds and the media-inactivity timeout to 90 seconds. WebUI NOTE: You must use the CLI to set SIP-signaling and media-inactivity timeouts. then click Apply: Zone: Untrust UDP Flood Protection (select) > Destination IP: Enter the following.1. then click the Back arrow in your browser to return to the Screen configuration page: Destination IP: 1. In this example. see “UDP Flood” on page 4-53. you set a threshold of 80. NOTE: This example uses a general ScreenOS command and is not necessarily SIP-specific. WebUI Security > Screening > Screen: Enter the following.000 per second for the number of UDP packets that can be received on IP address 1.1.5. For more information about UDP flood protection and how to determine effective settings.1. you configure the signaling-inactivity timeout to 30.Concepts & Examples ScreenOS Reference Guide Example: Signaling-Inactivity and Media-Inactivity Timeouts In this example.1. before the security device generates an alarm and drops subsequent packets for the remainder of that second.1.1.5 Threshold: 80000 Add: (select) CLI set zone untrust screen udp-flood dst-ip 1. in the Untrust zone.

If the security device detects more than 20 connection attempts from the same IP address. The security device translates SDP information for allocating resources to send and receive the media. then click OK: Source IP Based Session Limit: (select) Threshold: 20 Sessions CLI set zone untrust screen limit-session source-ip-based 20 save SIP with Network Address Translation The Network Address Translation (NAT) protocol enables multiple hosts in a private subnet to share a single public IP address to access the Internet. NAT replaces the private IP address of the host in the private subnet with the public IP address. For more information about source-based session limits and how to determine effective settings. For an outgoing message. WebUI Screening > Screen (Zone: Untrust): Enter the following. SIP with Network Address Translation 25 . see “Source-Based and Destination-Based Session Limits” on page 4-30. and the message is routed to the appropriate host in the private subnet. NOTE: This example uses a general ScreenOS command and is not necessarily SIP-specific. For an incoming message. the SIP ALG collects information from the message header into a call table. the public IP address is converted back into the private address. you prevent flood attacks on the SIP network from attackers in the Untrust zone by setting a maximum of 20 concurrent sessions from a single IP address. which it uses to forward subsequent messages to the correct end point. When a new message arrives. Using NAT with the SIP service is more complicated because SIP messages contain IP addresses in the SIP headers as well as in the SIP body. the ALG processes it as a REINVITE. For outgoing traffic. To.Chapter 2: Session Initiation Protocol Application Layer Gateway Example: SIP Connection Maximum In this example. which includes IP addresses and port numbers for transmission of the media. the private IP address and port number of the client are replaced with the public IP address and port number of the Juniper Networks firewall. the public address of the firewall is replaced with the private address of the client. The SIP headers contain information about the caller and the receiver. For incoming traffic. How IP addresses and port numbers in SIP messages are replaced depends on the direction of the message. If a new INVITE message arrives that matches the existing call. for example an ACK or 200 OK. The SIP body contains the Session Description Protocol (SDP) information. the ALG compares the From. When an INVITE message is sent out across the firewall. it begins dropping subsequent attempts until the number of sessions drops below the specified maximum. and the security device translates this information to hide it from the outside network. and Call-ID fields against the call table to identify the call context of the message.

Concepts & Examples ScreenOS Reference Guide

When a message containing SDP information arrives, the ALG allocates ports and creates a NAT mapping between them and the ports in the SDP. Because the SDP requires sequential ports for the Real Time Protocol (RTP) and Real Time Control Protocol (RTCP) channels, the ALG provides consecutive even-odd ports. If it is unable to find a pair of ports it discards the SIP message.

Outgoing Calls
When a SIP call is initiated with a SIP request message from the internal to the external network, NAT replaces the IP addresses and port numbers in the SDP and creates a binding to map the IP addresses and port numbers to the Juniper Networks firewall. Via, Contact, Route, and Record-Route SIP header fields, if present, are also bound to the firewall IP address. The ALG stores these mappings for use in retransmissions and for SIP response messages. The SIP ALG then opens pinholes in the firewall to allow media through the security device on the dynamically assigned ports negotiated based on information in the SDP and the Via, Contact, and Record-Route header fields. The pinholes also allow incoming packets to reach the Contact, Via, and Record-Route IP addresses and ports. When processing return traffic, the ALG inserts the original Contact, Via, Route, and Record-Route SIP fields back into the packets.

Incoming Calls
Incoming calls are initiated from the public network to public Mapped IP (MIP) addresses or to interface IP addresses on the security device. MIPs are statically configured IP addresses that point to internal hosts; interface IP addresses are dynamically recorded by the ALG as it monitors REGISTER messages sent by internal hosts to the SIP registrar. (For more information, see “Examples” on page 32.) When the security device receives an incoming SIP packet, it sets up a session and forwards the payload of the packet to the SIP ALG. The ALG examines the SIP request message (initially an INVITE) and, based on information in the SDP, opens gates for outgoing media. When a 200 OK response message arrives, the SIP ALG performs NAT on the IP addresses and ports and opens pinholes in the outbound direction. (The opened gates have a short time-to-live, and time out if a 200 OK response message is not received quickly.) When a 200 OK response arrives, the SIP proxy examines the SDP information and reads the IP addresses and port numbers for each media session. The SIP ALG on the security device performs NAT on the addresses and port numbers, opens pinholes for outbound traffic, and refreshes the timeout for gates in the inbound direction. When the ACK arrives for the 200 OK, it also passes through the SIP ALG. If the message contains SDP information, the SIP ALG ensures that the IP addresses and port numbers are not changed from the previous INVITE—if they are, the ALG deletes old pinholes and creates new pinholes to allow media to pass through. The ALG also monitors the Via, Contact, and Record-Route SIP fields and opens new pinholes if it determines that these fields have changed.

26

SIP with Network Address Translation

Chapter 2: Session Initiation Protocol Application Layer Gateway

Forwarded Calls
A forwarded call is when, for example, user A outside the network calls user B inside the network, and user B forwards the call to user C outside the network. The SIP ALG processes the INVITE from user A as a normal incoming call. But when the ALG examines the forwarded call from B to C outside the network and notices that B and C are reached using the same interface, it does not open pinholes in the firewall, because media will flow directly between user A and user C.

Call Termination
The BYE message is used to terminate a call. When the security device receives a BYE message, it translates the header fields just as it does for any other message, But because a BYE message must be acknowledged by the receiver with a 200 OK, the ALG delays call teardown for five seconds to allow time for transmission of the 200 OK.

Call Re-INVITE Messages
Re-INVITE messages are used to add new media sessions to a call, and to removing existing media sessions. When new media sessions are added to a call, new pinholes are opened in the firewall and new address bindings created. The process is identical to the original call setup. When one or more media sessions are removed from a call, pinholes are closed and bindings released just as with a BYE message.

Call Session Timers
The SIP ALG uses the Session-Expires value to time out a session if a Re-INVITE or UPDATE message is not received. The ALG gets the Session-Expires value, if present, from the 200 OK response to the INVITE and uses this value for signaling timeout. If the ALG receives another INVITE before the session times out, it resets all timeout values to this new INVITE or to default values, and the process is repeated. As a precautionary measure, the SIP ALG uses hard timeout values to set the maximum amount of time a call can exist. This ensures that the security device is protected in the event of the following: End systems crash during a call and a BYE message is not received. Malicious users never send a BYE in an attempt to attack a SIP ALG. Poor implementations of sip proxy fail to process Record-Route and never send a BYE message. Network failures prevent a BYE message from being received.

Call Cancellation
Either party can cancel a call by sending a CANCEL message. Upon receiving a CANCEL message, the SIP ALG closes pinholes through the firewall—if any have been opened—and releases address bindings. Before releasing the resources, the ALG delays the control channel age-out for approximately five seconds to allow time for the final 200 OK to pass through. The call is terminated when the five second timeout expires, regardless of whether a 487 or non-200 response arrives.
SIP with Network Address Translation

27

Concepts & Examples ScreenOS Reference Guide

Forking
Forking enables a SIP proxy to send a single INVITE message to multiple destinations simultaneously. When the multiple 200 OK response messages arrive for the single call, the SIP ALG parses but updates call information with the first 200 OK message it receives.

SIP Messages
The SIP message format consists of a SIP header section, and the SIP body. In request messages, the first line of the header section is the request line, which includes the method type, Request-URI, and protocol version. In response messages, the first line is the status line, which contains a status code. SIP headers contain IP addresses and port numbers used for signaling. The SIP body, separated from the header section by a blank line, is reserved for session description information, which is optional. Juniper Networks security devices currently support the Session Description Protocol (SDP) only. The SIP body contains IP addresses and port numbers used to transport the media. In NAT mode, the security device translates information in the SIP headers to hide the information from the outside network. NAT is performed on SIP body information to allocate resources, that is, port numbers where the media is to be received.

SIP Headers
In the following sample SIP request message, NAT replaces the IP addresses in the header fields—shown in bold font—to hide them from the outside network.
INVITE bob@10.150.20.5 SIP/2.0 Via: SIP/2.0/UDP 10.150.20.3:5434 From: alice@10.150.20.3 To: bob@10.150.20.5 Call-ID: a12abcde@10.150.20.3 Contact: alice@10.150.20.3:5434 Route: <sip:netscreen@10.150.20.3:5060> Record-Route: <sip:netscreen@10.150.20.3:5060>

28

SIP with Network Address Translation

It must also know what client initiated the call. and whether the message is a request or response. Note that for several of the header fields the ALG must know more than just whether the messages comes from inside or outside the network.Chapter 2: Session Initiation Protocol Application Layer Gateway How IP address translation is performed depends on the type and direction of the message. Table 2: Requesting Messages with NAT Message Type Inbound Request (from public to private) Fields To: From: Call-ID: Via: Request-URI: Contact: Record-Route: Route: Action Replace ALG address with local address None None None Replace ALG address with local address None None None Replace ALG address with local address None None None N/A Replace local address with ALG address Replace local address with ALG address None None Replace local address with ALG address Replace local address with ALG address Replace local address with ALG address None Replace local address with ALG address Replace local address with ALG address Replace ALG address with local address Outbound Response (from private to public) To: From: Call-ID: Via: Request-URI: Contact: Record-Route: Route: Outbound Request (from private to public) To: From: Call-ID: Via: Request-URI: Contact: Record-Route: Route: SIP with Network Address Translation 29 . which can be any of the following: Inbound request Outbound response Outbound request Inbound response Table 2 shows how NAT is performed in each of these cases.

150.33. Note that the Media Pinhole contains two port numbers.123. The following except from a sample SDP section shows the fields that are translated for resource allocation. Observe how.123. that is. the translations performed in the INVITE message are reversed.33. o=user 2344234 55234434 IN IP4 10. For more information.3 c=IN IP4 10. for RTCP and RTP. an INVITE message sent from a SIP client to a SIP server might have the following fields: c=IN IP4 10.4 m=audio 33447 RTP/AVP 0 c=IN IP4 10. see “Session Description Protocol Sessions” on page 20. being public. but gates are opened to allow the media stream access to the private network.3 m=audio 43249 RTP/AVP 0 SIP messages can contain more than one media stream. SIP NAT Scenario In Figure 9. The IP addresses in this message. are not translated. For example. 52002 and 52003. ph1 sends a SIP INVITE message to ph2.33.20.Concepts & Examples ScreenOS Reference Guide Message Type Outbound Response (from public to private) Fields To: From: Call-ID: Via: Request-URI: Contact: Record-Route: Route: Action None Replace ALG address with local address Replace ALG address with local address Replace ALG address with local address N/A None Replace ALG address with local address Replace ALG address with local address SIP Body The SDP information in the SIP body includes IP addresses the ALG uses to create channels for the media stream. port numbers to send and receive the media. 30 SIP with Network Address Translation . Translation of the SDP section also allocates resources. for a total of 12 channels per call. The SDP section of the INVITE message indicates where the caller is willing to receive media.123. The Via/Contact Pinhole provides port number 5060 for SIP signaling. The concept is similar to attaching multiple files to an email message.4 m=audio 33449 RTP/AVP 0 Juniper Networks security devices support up to 6 SDP channels negotiated for each direction.150. in the 200 OK response message.20. Note how the IP addresses in the header fields—shown in bold font—are translated by the security device.4 m=audio 33445 RTP/AVP 0 c=IN IP4 10.

0/UDP 5.6.6.1 1234 Any IP Any Port 6.6.6.0 Via: SIP/2.5.5.6.2 SIP ph2 INVITE Sip: ph2@ 6.1 Internal Network 5.6.6.1 m=audio 52002 RTP/AVP 0 6.6.5.6.1 o=IN IPv4 6.5.0/UDP 6.Chapter 2: Session Initiation Protocol Application Layer Gateway Figure 9: SIP NAT Scenario 1 Security Device SIP ph1 5.6.6 SIP/2.5.6.1 5060 6.6.1 From: ph1@6.1 External Network INVITE Sip: ph2@ 6.5.6.5.6.5.5.5.1 45002/45003 Via/Contact Pinhole 5.5.6.5.6.1:5060 Call-ID: a1234@6.6.6.5.1:5060 Call-ID: a1234@5.2 CSeq 1 INVITE Content-type: application/sdp Content-Length: 98 V=0 o=ph1 3123 1234 IP IP4 6.6.2 6.1 m=audio 62002 RTP/AVP 0 Media Pinhole 5.6.6.5.5.1 From: ph1@5.6.6.6.5.1 52002/52003 Any IP Any Port SIP with Network Address Translation 31 .5.2 CSeq 1 INVITE Content-type: application/sdp Content-Length: 98 V=0 o=ph1 3123 1234 IP IP4 5.0 Via: SIP/2.1 To: ph2@6.6.6 SIP/2.5.6.1 To: ph2@6.1 o=IN IPv4 5.

6.2 6.1 External Network SIP/2.6.2 c=IN IP4 6.6.1 From: ph1@6.6.6.2 CSeq 1 INVITE Content-type: application/sdp Content-Length: 98 Contact SIP: 6.6.2 SIP/2.6.6.6.6.0 200 OK Via: SIP/2.6.6.Concepts & Examples ScreenOS Reference Guide Figure 10: SIP NAT Scenario 2 Security Device SIP ph1 5.5..6.6.5.5.5.6.1 To: ph2@6.2 m=audio 62002 RTP/AVP 0 6.5.2 5060 ACK SIP:ph2@6.6:5060 V=0 o=ph2 5454 565642 IP IP4 6.5..6..5.2 c=IN IP4 6..6.6.6.1:1234 Call-ID: a1234@6.6.6.2 SIP ph2 Media Pinhole Any IP Any Port 6.6.5.1 From: ph1@5.6..0/UDP 5.6.2 m=audio 62002 RTP/AVP 0 5.0 .2 62002/62003 Via/Contact Pinhole Any IP Any Port 6.1 To: ph2@6.0/UDP 6.6.6. Proxy in the DMZ” on page 46 “Example: Untrust Intrazone” on page 49 “Example: Trust Intrazone” on page 53 “Example: Full-Mesh VPN for SIP” on page 55 32 Examples . Examples This section contains the following sample scenarios: “Incoming SIP Call Support Using the SIP Registrar” on page 33 “Example: Incoming Call with MIP” on page 39 “Example: Proxy in the Private Zone” on page 41 “Example: Proxy in the Public Zone” on page 44 “Example: Three-Zone.0 200 OK Via: SIP/2.6.6..5.0 . ACK SIP:ph2@6.2 SIP/2.6.1:5060 Call-ID: a1234@5.2 CSeq 1 INVITE Content-type: application/sdp Content-Length: 98 V=0 o=ph2 5454 565642 IP IP4 6.1 Internal Network SIP/2.6.5.6.6.

and stores the information in an Incoming DIP table. Then. Interface DIP is adequate for handling incoming calls in a small office. The security device monitors outgoing REGISTER messages.Chapter 2: Session Initiation Protocol Application Layer Gateway Incoming SIP Call Support Using the SIP Registrar SIP registration provides a discovery capability by which SIP proxies and location servers are able to identify the location or locations where users want to be contacted. Registration creates bindings in a location service that associates the address-of-record with the contact address or addresses. when an INVITE message is received from outside the network.323 services only. as shown in Figure 11. security devices currently support UDP and TCP only. URIs must contain IP addresses. You can take advantage of SIP proxy registration service to allow incoming calls by configuring Interface DIP or DIP pools on the egress interface of the security device. performs NAT on these addresses. while we recommend setting up DIP pools for larger networks or an enterprise environment. A user registers one or more contact locations by sending a REGISTER message to the registrar. NOTE: Incoming call support using Interface DIP or a DIP pool is supported for SIP and H. Domain name resolution is also currently not supported. Examples 33 . the security device uses the Incoming DIP table to identify which internal host to route the INVITE message to. For incoming calls. as shown in Figure 11. The To: and Contact: fields in the REGISTER message contain the address-of-record URI and one or more contact URIs. therefore.

5.0 From: ph1@6. For an explanation of how incoming DIP works with the SIP registration service.6.0 From: ph1@5.5. then create a policy permitting SIP traffic from the Untrust zone to the Trust zone and reference that DIP in the policy.6. You set Interface DIP on the ethernet3 interface to do NAT on incoming calls.5.1 To: ph1@5.6.6.5.1 To: ph1@6.2 Internal Network REGISTER sip: 6.1 5.1 CSeq 1 INVITE Contact <sip: 5.6.5.5.6.5. This enables phone1 in the Trust zone to register with the proxy in the Untrust zone.5.6.6.6.1 CSeq 1 INVITE Contact <sip: 6.6.5.1 : 1234 6.6.5.5.1:5555> Expires: 7200 200 OK From: ph1@5.6.1 CSeq 1 INVITE Contact <sip: 5.5.5.1:5555> Expires: 3600 Example: Incoming Call (Interface DIP) In this example.1 : 5555 3600 Security Device SIP ph1 5.2 SIP/2.Concepts & Examples ScreenOS Reference Guide Figure 11: Incoming SIP Incoming DIP Table 5.6.5.6.6.5.1 CSeq 1 INVITE Contact <sip: 6.5.6.6.5.1:1234> Expires: 3600 Update Timeout value 200 OK From: ph1@6.6.1:1234> Expires: 7200 6. You also create a policy that permits SIP traffic from the Trust to the Untrust zone using NAT Source.2 REGISTER sip:6. see “Examples” on page 32. 34 Examples .6.5.1 To: ph1@6.2 SIP/2.1 To: ph1@5.1 External Network Add entry to Incoming DIP table Registrar 6.6. and phone2 and the proxy server are on the ethernet3 interface in the Untrust zone.6. phone1 is on the ethernet1 interface in the Trust zone.6.

Addresses Policy > Policy Elements > Addresses > List > New: Enter the following.1.1. 1.3/24 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following.4 Proxy Server 1.4/24 Zone: Untrust Examples 35 .1.1. then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet3): Enter the following.1.Chapter 2: Session Initiation Protocol Application Layer Gateway Figure 12: Incoming Call with Interface DIP on ethernet3 Interface ethernet1 10.1/24 Untrust Internet Interface DIP on ethernet 3 phone1 10. then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select). then click Apply: Zone Name: Trust Static IP: (select this option when present) IP Address/Netmask: 10.1.1. then click OK: Zone Name: Untrust Static IP: (select this option when present) IP Address/Netmask: 1. then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select).3 WebUI 1.1.1.1.3 phone2 1.1. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.1.1.1/24 Enter the following.1. 10.1.1.1/24 Interface Mode: Route 2.1/24 Trust Security Device LAN ethernet3 1.1.1.

To: Untrust) New: Enter the following.1.Concepts & Examples ScreenOS Reference Guide Policy > Policy Elements > Addresses > List > New: Enter the following. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.4/24 set address untrust proxy 1. To: Trust) New: Enter the following.1. Any Destination Address Address Book Entry: (select). DIP(ethernet3) Service: SIP Action: Permit CLI 1.1/24 set interface ethernet3 route 2. phone1 Destination Address Address Book Entry: (select). Addresses set address trust phone1 10. Policies Policies > (From: Trust.1. then click OK: Source Address Address Book Entry: (select).1.1.1.3/24 set address untrust phone2 1. DIP with Incoming NAT Network > Interface > Edit (for ethernet3) > DIP > New: Select the Incoming NAT option.1.1.1.1. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): None (Use Egress Interface IP) Policies > (From: Untrust.3/24 3.1.1/24 set interface ethernet3 zone untrust set interface ethernet3 ip 1. then click OK. then click OK: Address Name: proxy IP Address/Domain Name: IP/Netmask: (select). DIP with Incoming NAT set interface ethernet3 dip interface-ip incoming set dip sticky 36 Examples . any Service: SIP Action: Permit > Advanced: Enter the following. then click OK: Source Address Address Book Entry: (select).1. 1.3/24 Zone: Untrust 3. 4.

1.1.3 WebUI 1.40 > phone2 1.1.1. Figure 13: Incoming Call with DIP Pool ethernet1 10. then click OK: Zone Name: Untrust Static IP: (select this option when present) IP Address/Netmask: 1. For an explanation of how DIP works with the SIP registration service.1.1/24 Enter the following.1. This enables phone1 in the Trust zone to register with the proxy in the Untrust zone.1. Policies set policy from trust to untrust phone1 any sip nat src permit set policy from untrust to trust any dip(ethernet3) sip permit save Example: Incoming Call (DIP Pool) This example.1/24 Untrust Internet phone1 10.4 Proxy Server 1.1.1.1.1. then click Apply: Zone Name: Trust Static IP: (select this option when present) IP Address/Netmask: 10. then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet3): Enter the following.Chapter 2: Session Initiation Protocol Application Layer Gateway 4. see “Examples” on page 32. and phone2 and the proxy server are in the Untrust zone.1.3 DIP Pool on ethernet3 1. You set a DIP pool on the ethernet3 interface to do NAT on incoming calls.1.1.1. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.1. You also create a policy that permits SIP traffic from the Trust to the Untrust zone using NAT Source. phone1 is in the Trust zone.1.1/24 Interface Mode: Route Examples 37 . then set a policy permitting SIP traffic from the Untrust zone to the Trust zone and reference that DIP pool in the policy.1.1/24 Trust Security Device LAN ethernet3 1.20 .1.

1.1.1.1. Policies Policies > (From: Trust.40 Port Translation: (select) In the same subnet as the interface IP or its secondary IPs: (select) Incoming NAT: (select) 4.3/24 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following.1. DIP Pool with Incoming NAT Network > Interface > Edit (for ethernet3) > DIP > New: Enter the following. then click OK: Address Name: proxy IP Address/Domain Name: IP/Netmask: (select).1.1.20 ~ 1. 1. 1.1.40)/port-xlate 38 Examples . 10.20-1.Concepts & Examples ScreenOS Reference Guide 2.3/24 Zone: Untrust 3. phone1 Destination Address Address Book Entry: (select).1. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): 5 (1. then click OK: ID: 5 IP Address Range: (select). Any Service: SIP Action: Permit > Advanced: Enter the following.1. 1.4/24 Zone: Untrust Policy > Policy Elements > Addresses > List > New: Enter the following. then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select). To: Untrust) New: Enter the following. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following.1.1. then click OK: Source Address Address Book Entry: (select).1. then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select).1.

To: Trust) New: Enter the following.1. DIP Pool with Incoming NAT set interface ethernet3 dip 5 1.1. and phone2 and the proxy server are on the ethernet3 interface in the Untrust zone. You also create a policy allowing phone1 to register with the proxy server in the Untrust zone.4/24 set address untrust proxy 1.Chapter 2: Session Initiation Protocol Application Layer Gateway Policies > (From: Untrust. This example is similar to the previous two examples (“Example: Incoming Call (Interface DIP)” on page 34 and “Example: Incoming Call (DIP Pool)” on page 37).1.3/24 set address untrust phone2 1. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.20 1.1. Examples 39 .1/24 set interface ethernet3 zone untrust set interface ethernet3 ip 1. Policies set policy from trust to untrust phone1 any sip nat src dip 5 permit set policy from untrust to trust any dip(5) sip permit save Example: Incoming Call with MIP In this example.1.1/24 set interface ethernet3 route 2.1.1. Addresses set address trust phone1 10. except that with a MIP you need one public address for each private address in the Trust zone. phone1 is on the ethernet1 interface in the Trust zone. while with Interface DIP or a DIP pool a single interface address can serve multiple private addresses.1.1.1.40 incoming set dip sticky 4. DIP(5) Service: SIP Action: Permit CLI 1.3/24 3.1. You put a MIP on the ethernet3 interface to phone1.1. then create a policy that allows SIP traffic from the Untrust zone to the Trust zone and reference that MIP in the policy.1. Any Destination Address Address Book Entry: (select). then click OK: Source Address Address Book Entry: (select).1.

1/24 ethernet3 1.1.1.1.1.1.4/24 Zone: Untrust 40 Examples .1. 1. then click Apply: Zone: Trust Static IP: (select this option when present) IP Address/Netmask: 10.3/24 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following.1. then click OK: Zone: Untrust IP Address/Netmask: 1.1.1. then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select).1.4 WebUI 1.1. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following.1/24 phone2 1. then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select). Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.1.1/24 Enter the following.1.Concepts & Examples ScreenOS Reference Guide Figure 14: Incoming Call with MIP ethernet1 10.1/24 Trust Security Device LAN Untrust Internet Proxy Server phone1 10. 10.1.1.3 Virtual Device MIP on ethernet3 1.1. then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet3): Enter the following.1.1/24 Interface Mode: Route 2.1.

Addresses set address trust phone1 10.1. then click OK: Address Name: proxy IP Address/Domain Name: IP/Netmask: (select). MIP(1. then click OK: Source Address: Address Book Entry: (select).1. phone1 and the SIP proxy server are on the ethernet1 interface in the Trust (private) zone. Examples 41 .1. MIP set interface ethernet3 mip 1.3) Service: SIP Action: Permit CLI 1.1.3/24 Zone: Untrust 3. MIP Network > Interfaces > Edit (for ethernet3) > MIP > New: Enter the following.255 Host IP Address: 10.1. To: Trust) New: Enter the following.3 4. any Destination Address: Address Book Entry: (select).1.1.1. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.3 Netmask: 255.1.1.1.255.3 host 10.1. You also create a policy from the Trust to the Untrust zone to allow phone1 to call out. and phone2 is on the ethernet3 interface in the Untrust zone. You put a MIP on the ethernet3 interface to the proxy server to allow phone2 to register with the proxy.1.1.Chapter 2: Session Initiation Protocol Application Layer Gateway Policy > Policy Elements > Addresses > List > New: Enter the following.3/24 3.3/24 set address untrust phone2 1.1.1.3 4.1. then click OK: Mapped IP: 1. 1.1/24 set interface ethernet3 route 2. Policy Policies > (From: Untrust. Policy set policy from untrust to trust any mip(1.1.4/24 set address untrust proxy 1.1.1.1.1.1/24 set interface ethernet3 zone untrust set interface ethernet3 ip 1.255.1. then create a policy allowing SIP traffic from the Untrust to the Trust zone and reference that MIP in the policy.3) sip permit save Example: Proxy in the Private Zone In this example.1.

4 phone1 10. then click OK: Address Name: proxy IP Address/Domain Name: IP/Netmask: (select).1.1. 10. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following.1.1.3/24 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following.1.3 Virtual Device MIP on ethernet3 1.1.1. then click OK: Zone: Trust Static IP: (select this option when present) IP Address/Netmask: 10. 1.1.2 -> 10.1/24 Trust Security Device LAN ethernet3 1.1.1.4 WebUI 1.1. then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select).1.1.1.4 phone2 1.Concepts & Examples ScreenOS Reference Guide Figure 15: Proxy in the Private Zone ethernet1 10.1/24 Enter the following. then click OK: Zone: Untrust IP Address/Netmask: 1.1.1.1.1/24 Interface Mode: Route 2.1.1.1. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following. then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet3): Enter the following. 10. then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select).1.4/24 Zone: Untrust Policy > Policy Elements > Addresses > List > New: Enter the following.1.1.1.1/24 Untrust Internet Proxy Server 10.4/24 Zone: Trust 42 Examples .

then click OK: Source Address: Address Book Entry: (select).1/24 set interface ethernet3 zone untrust set interface ethernet3 ip 1.255. MIP(1.1.4/24 set address trust proxy 10.1. To: Trust) New: Enter the following.1.4/24 3.1. To: Untrust) New: Enter the following.2 Netmask: 255.255 Host IP Address: 10. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): None (Use Egress Interface IP) Policies > (From: Untrust.4 4.1.1.1. Policies set policy from trust to untrust any phone2 sip nat src permit set policy from untrust to trust phone2 mip(1. then click OK: Mapped IP: 1. MIP set interface ethernet3 mip 1. Addresses set address trust phone1 10.1.Chapter 2: Session Initiation Protocol Application Layer Gateway 3.1.255.1.1.4 Host Virtual Router Name: trust-vr 4.3) > MIP > New: Enter the following.1. Policies Policies > (From: Trust.1. phone2 Destination Address: Address Book Entry: (select). MIP Network > Interfaces > Edit (for loopback. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.1/24 set interface ethernet3 route 2.2 host 10.1.1.1.1. then click OK: Source Address: Address Book Entry: (select) any Destination Address: Address Book Entry: (select) phone2 Service: SIP Action: Permit > Advanced: Enter the following.1.1.1.2) sip permit save Examples 43 .2) Service: SIP Action: Permit CLI 1.1.1.3/24 set address untrust phone2 1.

4 Proxy Server 1. This example is similar to the previous incoming call examples (see “Example: Incoming Call (DIP Pool)” on page 37 and “Example: Incoming Call with MIP” on page 39) and. phone1 is on the ethernet1 interface in the Trust zone.1/24 Enter the following.1.1. then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select).1.3/24 Zone: Trust 44 Examples . then click Apply: Zone: Trust Static IP: (select this option when present) IP Address/Netmask: 10. then click OK: Zone: Untrust IP Address/Netmask: 1. and the proxy server and phone2 are on the ethernet3 interface in the Untrust (public) zone. then create a policy permitting SIP traffic from the Untrust zone to the Trust zone and reference that DIP in the policy.1.1. Figure 16: Proxy in the Public Zone ethernet1 10.1. then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet3): Enter the following.1. 10.1/24 Security Device Trust LAN Untrust Internet phone1 10.1.1.1. You configure Interface DIP on the Untrust interface.1.1. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following.1/24 Interface Mode: Route 2.1.1.1/24 ethernet3 1. you can use DIP or MIP on the Untrust interface.Concepts & Examples ScreenOS Reference Guide Example: Proxy in the Public Zone In this example. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following. You also create a policy from Trust to Untrust to allow phone1 to register with the proxy server in the Untrust zone.1.3 Interface DIP on ethernet3 phone2 1. as with those examples.1.3 WebUI 1.

then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select).1.Chapter 2: Session Initiation Protocol Application Layer Gateway Policy > Policy Elements > Addresses > List > New: Enter the following. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): None (Use Egress Interface IP) Policies > (From: Untrust. then click OK: Source Address: Address Book Entry: (select) phone1 Destination Address: Address Book Entry: (select) Any Service: SIP Action: Permit > Advanced: Enter the following.1.1. Interface DIP Network > Interface > Edit (for ethernet3) > DIP: Select the Incoming NAT check box. To: Untrust) New: Enter the following.1.1.1.1.1.1.1.4/24 set address untrust proxy 1.3/24 Zone: Untrust 3.4/24 Zone: Untrust Policy > Policy Elements > Addresses > List > New: Enter the following.3/24 set address untrust phone2 1. 1.1/24 set interface ethernet3 zone untrust set interface ethernet3 ip 1.1/24 2.1. Any Destination Address: Address Book Entry: (select). Addresses set address trust phone1 10.1. 4. 1. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.1.3/24 45 Examples . then click OK: Address Name: proxy IP Address/Domain Name: IP/Netmask: (select).1. Policies Policies > (From: Trust. then click OK: Source Address: Address Book Entry: (select). DIP(ethernet3) Service: SIP Action: Permit CLI 1. To: Trust) New: Enter the following.

and create a policy from the DMZ to the Trust zone and reference that MIP in the policy. Figure 17: Proxy in the DMZ Untrust Internet phone2 1.1. phone1 is on the ethernet1 interface in the Trust zone.2.2.1.4 ethernet3 1.2. The arrows in Figure 17 show the flow of SIP signaling traffic when phone2 in the Untrust zone places a call to phone1 in the Trust zone.1.3-> 10.3 Trust Proxy Server 2. with three zones.2/24 DMZ Security Device ethernet1 10.1. Interface DIP set interface ethernet3 dip interface-ip incoming 4.4 46 Examples . you need to create bidirectional policies between each of the zones. Policies set policy from trust to untrust phone1 any sip nat src permit set policy from untrust to trust any dip(ethernet3) sip permit save Example: Three-Zone.1.1.2.Concepts & Examples ScreenOS Reference Guide 3.1. In fact.1. Proxy in the DMZ In this example.1/24 ethernet2 2. phone2 is on the ethernet3 interface in the Untrust zone.1. You put a MIP on the ethernet2 interface to phone1 in the Trust zone. the media flows directly between phone1 and phone2. and the proxy server is on the ethernet2 interface in the DMZ.2.1/24 Virtual Device MIP on ethernet2 2. After the session is initiated.3 LAN phone1 10.2.1.

2.1. 1.4/24 Zone: DMZ 3.1.3/24 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following.1.1.255 Host IP Address: 10.2.Chapter 2: Session Initiation Protocol Application Layer Gateway WebUI 1. MIP Network > Interfaces > Edit (for ethernet2) > MIP > New: Enter the following.3 Netmask: 255. Address Policy > Policy Elements > Addresses > List > New: Enter the following.1/24 2. then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select).1.2. then click OK: Mapped IP: 2.2.1. then click OK: Address Name: proxy IP Address/Domain Name: IP/Netmask: (select). 2.2.2/24 Network > Interfaces > Edit (for ethernet3): Enter the following.255.1.3 47 Examples .255.2. then click OK: Zone Name: Untrust Static IP: (select when this option is present) IP Address/Netmask: 1.4/24 Zone: Untrust Policy > Policy Elements > Addresses > List > New: Enter the following. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10. then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select). 10. then click OK: Zone Name: DMZ Static IP: (select when this option is present) IP Address/Netmask: 2.1.1/24 Enter the following.1.1. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following. then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet2): Enter the following.

MIP(2. then click OK: Source Address: Address Book Entry: (select). phone1 Service: SIP Action: Permit Policies > (From: Untrust. then click OK: Source Address: Address Book Entry: (select). Policies Policies > (From: Trust.Concepts & Examples ScreenOS Reference Guide 4. To: DMZ) New: Enter the following. then click OK: Source Address: Address Book Entry: (select).2. then click OK: Source Address: Address Book Entry: (select). proxy Service: SIP Action: Permit Policies > (From: DMZ. proxy Destination Address: Address Book Entry: (select). then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: Enable (DIP on): None (Use Egress Interface IP) Policies > (From: DMZ. then click OK: Source Address: Address Book Entry: (select).3) Service: SIP Action: Permit 48 Examples .2. To: Trust) New: Enter the following. To: DMZ) New: Enter the following. proxy Service: SIP Action: Permit > Advanced: Enter the following. phone2 Destination Address: Address Book Entry: (select). phone2 Service: SIP Action: Permit Policies > (From: Untrust. phone1 Destination Address: Address Book Entry: (select). phone2 Destination Address: Address Book Entry: (select). proxy Destination Address: Address Book Entry: (select). To: Trust) New: Enter the following. To: Untrust) New: Enter the following.

1.1/24 set interface ethernet3 zone untrust set interface ethernet3 ip 1. you create a loopback interface.3 host 10.1. Creating a loopback interface enables you to use a single MIP for the proxy server in the Trust zone. To allow intrazone SIP traffic between the two phones in the Untrust zone.2.1.1.3) sip permit set policy from trust to untrust phone1 phone2 sip nat src permit save Example: Untrust Intrazone In this example.2.1.1. To: Untrust) New: Enter the following. then put a MIP on the loopback interface to the IP address of the proxy server.4 3. then click OK: Source Address: Address Book Entry: (select). then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: Enable (DIP on): None (Use Egress Interface IP) CLI 1.2.3 4. For more information about using loopback interfaces. Examples 49 . phone1 Destination Address: Address Book Entry: (select). phone2 Service: SIP Action: Permit > Advanced: Enter the following.2.3/24 set address untrust phone2 1. and the proxy server is on the ethernet1 interface in the Trust zone.2. see “MIP and the Loopback Interface” on page 8-73. phone2 is in a subnet on the ethernet3 interface in the Untrust zone. Addresses set address trust phone1 10.1/24 set interface ethernet3 route set interface ethernet2 zone dmz set interface ethernet2 ip 2.Chapter 2: Session Initiation Protocol Application Layer Gateway Policies > (From: Trust. MIP set interface2 mip 2. Because blocking is on by default in the Untrust zone.2.2. phone1 is on the ethernet4 interface in the Untrust zone.2.4/24 set address dmz proxy 2.1. Policies set policy from trust to dmz phone1 proxy sip nat src permit set policy from dmz to untrust proxy phone2 sip permit set policy from untrust to trust phone2 phone1 sip permit set policy from untrust to dmz phone2 proxy sip permit set policy from dmz to trust proxy mip(2.1.1.2/24 set interface ethernet2 route 2. you must also turn off blocking to allow intrazone communication. add ethernet3 and ethernet4 to a loopback group. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.1.

1/24 Loopback 1 1.5 ethernet1 10.1.Concepts & Examples ScreenOS Reference Guide Figure 18: Untrust Intrazone Untrust phone1 1./24 ethernet3 1.1/24 Enter the following.4 phone2 1.1.1.5 Trust WebUI 1.4 Internet ethernet4 1.1/24 MIP on Loopback.1.4. then click OK: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 1.1.1.5-> 10.1.1.1/24 50 Examples .1.1.1/24 LAN proxy 10.1 1.1.1.2.1.1.1. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10. then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet4): Enter the following.1.1.1.4.1. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.

then click OK: Interface Name: loopback. then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select). then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select). 1.1. then click OK: As member of loopback group: (select) loopback.Chapter 2: Session Initiation Protocol Application Layer Gateway Network > Interfaces > Edit (for ethernet3): Enter the following.4/32 Zone: Untrust Policy > Policy Elements > Addresses > List > New: Enter the following.1 Zone: Untrust (trust-vr) IP Address/Netmask: 1. 10. then click OK: Address Name: proxy IP Address/Domain Name: IP/Netmask: (select).5/32 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following.1.4/32 Zone: Untrust 3.2.1 Zone Name: Untrust Examples 51 .1.2.4. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following.1. then click OK: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 1. 1.1 Zone Name: Untrust Network > Interfaces > Edit (for ethernet4): Enter the following.1.1.1.1/24 Network > Interfaces > New Loopback IF: Enter the following. then click OK: As member of loopback group: (select) loopback. Loopback Group Network > Interfaces > Edit (for ethernet3): Enter the following.1/24 2.

To: Untrust) New: Enter the following.255 Host IP Address: 10.Concepts & Examples ScreenOS Reference Guide 4.1.255.1. then click OK: Source Address: Address Book Entry: (select).1 route 52 Examples .1.1 ip 1.1. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: Enable (DIP on): None (Use Egress Interface IP) Policies > (From: Untrust. Blocking Network > Zones > Edit (for Untrust): Enter the following. then click OK: Mapped IP: 1. To: Trust) New: Enter the following. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10. then click OK: Source Address: Address Book Entry: (select).5 Netmask: 255.1. Any Destination Address: Address Book Entry: (select).1.4.1/24 set interface ethernet3 zone untrust set interface ethernet3 ip 1.1/24 set interface ethernet4 route set interface loopback.1) > MIP > New: Enter the following.255. Any Service: SIP Action: Permit > Advanced: Enter the following.5 Host Virtual Router Name: trust-vr 5.1 zone untrust set interface loopback.1.1. MIP Network > Interfaces > Edit (for loopback.1/24 set interface ethernet3 route set interface ethernet4 zone untrust set interface ethernet4 ip 1. MIP(1.5) Service: SIP Action: Permit CLI 1.1. proxy Destination Address: Address Book Entry: (select). then click OK: Block Intra-Zone Traffic: (clear) 6. Policies Policies > (From: Trust.1.4.1/24 set interface loopback.2.4.

2.1. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.5 5.Chapter 2: Session Initiation Protocol Application Layer Gateway 2.2.4 Trust Security Device Untrust Internet LAN phone2 10.1 mip 1.1/24 Interface DIP on ethernet3 WebUI 1.3. then click OK: Interface Mode: NAT Examples 53 .3/24 Proxy Server 3.4.1. then set policies to allow bidirectional SIP traffic between the Trust and the Untrust zones. Policies set policy from trust to untrust proxy any sip nat src permit set policy from untrust to trust any mip(1. and the proxy server is on the ethernet3 interface in the Untrust zone. phone1 is on the ethernet1 interface in the Trust zone.1.1. Figure 19: Trust Intrazone phone1 10.1 set interface ethernet4 loopback-group loopback.1. Blocking unset zone untrust block 6.4.1.1.3. MIP set interface loopback. phone 2 is on the ethernet2 interface in a subnet in the Trust zone. Loopback Group set interface ethernet3 loopback-group loopback. Addresses set address trust proxy 10.1.1.5/32 set address untrust phone1 1.1.5 host 10.1 4.2 ethernet2 10.3.1.1/24 ethernet3 3.1. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10.1.1. To allow both phones in the Trust zone to communicate with each other.1/24 Enter the following.1.4/32 3.3 ethernet1 10.1. you configure Interface DIP on the ethernet3 interface to allow them to contact the proxy server.4/32 set address untrust phone2 1.1.5) sip permit save Example: Trust Intrazone In this example.2. Blocking is off by default in the Trust zone (as it is in custom zones you define).3.

then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select). proxy Service: SIP Action: Permit 54 Examples . To: Untrust) New: Enter the following.3. 3.4/24 Zone: Untrust 3.2.3/24 2. 10. then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select).Concepts & Examples ScreenOS Reference Guide Network > Interfaces > Edit (for ethernet2): Enter the following. 10. then click OK: Source Address: Address Book Entry: (select).2.1. DIP with Incoming NAT Network > Interface > Edit (for ethernet3) > DIP > New: Enter the following.1/24 Enter the following.3.1.2/24 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following. then click OK: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 3.1.3.3.1. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following. then click OK: Incoming NAT: (select) 4. then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet3): Enter the following. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10.3/24 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following. Any Destination Address: Address Book Entry: (select). then click OK: Address Name: proxy IP Address/Domain Name: IP/Netmask: (select). Policies Policies > (From: Trust.

To: Trust) New: Enter the following. Interface DIP set interface ethernet3 dip interface-ip incoming 4.1.3.3/24 set interface ethernet3 route 2. Examples 55 . to create a fully meshed network.2.4/24 3. Each site has a single security device.1/24 set interface ethernet2 zone trust set interface ethernet2 ip 10.1.3.1.1. the central office and two branch offices are linked by a full-mesh VPN. you configure two tunnels.2. The proxy server is in the Trust zone at the Central Office.3/24 set address trust phone2 10. phone1 is in the Trust zone at Branch Office One. Policies set policy from trust to untrust any proxy sip nat src permit set policy from untrust to trust proxy dip(ethernet3) sip permit save Example: Full-Mesh VPN for SIP In this example. then click OK: Source Address Address Book Entry: (select) proxy Destination Address Address Book Entry: (select) Any Service: SIP Action: Permit > Advanced: Enter the following. one to each of the other devices.1.2/24 set address untrust proxy 3. Addresses set address trust phone1 10.3. and phone2 is in the Trust zone at Branch Office Two.1.3. All interfaces connecting the devices are in their respective Untrust zones.1/24 set interface ethernet2 nat set interface ethernet3 zone untrust set interface ethernet3 ip 3. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: Enable (DIP on): None (Use Egress Interface IP) Policies > (From: Untrust. On each device. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10. then click Return to set the advanced options: NAT: Source Translation: (select) (DIP on): None (Use Egress Interface IP) CLI 1.Chapter 2: Session Initiation Protocol Application Layer Gateway > Advanced: Enter the following.

5.1.3 interface unnumbered Gateway Router To branch-1: 4.1.2.2. VPN 1 VPN 2 Branch-1 VPN 3 Branch-2 tunnel.4 Untrust eth4-5.3.3 WebUI (for Central) 1.1 To branch: 3.4. then click Apply: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 1.4.4.1.5.1.3.1/24 Network > Interfaces > Edit (for ethernet2/2): Enter the following.7 Untrust eth2/2 1.4 To branch-2: 5.3.3 tunnel.1 Trust Zone Branch Office One phone1 10.1.1.2.1/24 56 Examples .3.1 Gateway Router To central: 1.3 tunnel.5 Trust Zone tunnel.Concepts & Examples ScreenOS Reference Guide NOTE: The security devices used in this example must have at least three independently configurable interfaces available.1.3 Note: The Untrust Zone for each device is not shown Central Office Trust Zone Trust eth2/8-10.6.2.3 interface unnumbered Branch Office Two phone2 10.1. Interfaces Network > Interfaces > Edit (for ethernet2/1): Enter the following.1 Gateway Router To central: 1.3 Untrust eth3 3.1.3.1.1.2.2.1 To branch: 2.5 Trust eth1 10.3. then click Apply: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 1.1 tunnel 1 6.1.1.7.5.2.2.2.1 Untrust eth4-4.1.6.6 Untrust eth2/1: 1.7. Figure 20: Full-Mesh VPN for SIP Proxy 10.5.1.1.1 interface unnumbered Central tunnel 2 7.2 Untrust eth3 2.4.2.2 interface unnumbered Trust eth1 10.1.

VPN VPNs > AutoKey Advanced > Gateway > New: Enter the following.1/24 Enter the following.1.3 Preshare Key: netscreen Outgoing Interface: ethernet2/1 VPNs > AutoKey IKE > New: Enter the following.3.3. then click Return to return to the basic Gateway configuration page: Bind to: (select) Tunnel Interface.6. then click OK: Address Name: Proxy IPv4/Netmask: 10. Address Policy > Policy Elements > Addresses > List > New: Enter the following.6.2.7/24 2.1 VPNs > AutoKey Advanced > Gateway > New: Enter the following. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10.3. then click Apply: Tunnel Interface Name: 2 Zone (VR): Untrust IP Address / Netmask: 7. then click OK: Interface mode: Route Network > Interfaces > New Tunnel IF: Enter the following. then click Apply: Tunnel Interface Name: 1 Zone (VR): Untrust IP Address / Netmask: 6.7.Chapter 2: Session Initiation Protocol Application Layer Gateway Network > Interfaces > Edit (for ethernet2/8): Enter the following. then click OK: Gateway Name: to-branch-2 Security Level: Standard IPvc4/v6 Address/Hostname: 2.3.7. tunnel.6/24 Network > Interfaces > New Tunnel IF: Enter the following.1. then click OK: Gateway Name: to-branch-1 Security Level: Standard IPvc4/v6 Address/Hostname: 3. then click OK: VPN Name: vpn-branch-1 Advanced: Enter the following advanced settings.2.2 Preshare Key: netscreen Outgoing Interface: ethernet2/2 Examples 57 .3/32 Zone: Trust 3.

To: Untrust) New Enter the following. then click OK: Source Address (select) Address Book Entry: Proxy Destination Address (select) Address Book Entry: Any-IPv4 Service: SIP Action: Permit Policies > (From: Untrust.2. To: Trust) > New: Enter the following. Routing Network > Routing > Destination > New: Enter the following.1.2.3 main outgoing-interface ethernet2/1 preshare netscreen sec-level standard set ike gateway to-branch-2 address 2. then click OK: VPN Name: vpn-branch-2 Advanced: Enter the following advanced settings. then click OK: Source Address (select) Address Book Entry: Any-IPv4 Destination Address (select) Address Book Entry: Proxy Service: SIP Action: Permit CLI (for Central) 1.1.1.1. VPN set ike gateway to-branch-1 address 3. then click OK: Network Address / Netmask: 10. Interfaces set set set set set set set set set set set 2.0/24 Interface (select): tunnel. tunnel.1/24 interface ethernet2/8 route interface tunnel.1/24 interface ethernet2/2 zone untrust interface ethernet2/2 ip 1.6/24 interface tunnel.1/24 interface ethernet2/8 zone trust interface ethernet2/8 ip 10.6.2 4. then click Return to return to the basic Gateway configuration page: Bind to: (select) Tunnel Interface.2 zone untrust interface tunnel.3.6.2 ip 7.3.3.0/24 Interface (select): tunnel.2 5.7.1 ip 6.2 main outgoing-interface ethernet2/2 preshare netscreen sec-level standard 58 Examples .1.1 zone untrust interface tunnel.1.Concepts & Examples ScreenOS Reference Guide VPNs > AutoKey IKE > New: Enter the following.1. interface ethernet2/1 zone untrust interface ethernet2/1 ip 1.7/24 Address set address trust proxy 10. Policies Policies > (From: Trust.7.1 Network > Routing > Destination > New: Enter the following.3/32 3.3. then click OK: Network Address / Netmask: 10.1.2.2.

then click Apply: Tunnel Interface Name: 3 Zone (VR): Untrust Unnumbered (select) Interface: ethernet4 Examples 59 .1.1.1.3/24 Network > Interfaces > Edit (for ethernet4): Enter the following.4.1/24 Interface mode: NAT Network > Interfaces > Edit (for ethernet3): Enter the following. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10.1 set vpn vpn-branch-2 gateway to-branch-2 no-reply tunnel idletime 0 sec-level standard set vpn vpn-branch-2 id 2 bind interface tunnel.2.1 5. then click Apply: Tunnel Interface Name: 2 Zone (VR): Untrust Unnumbered (select) Interface: ethernet3 Network > Interfaces > New Tunnel IF: Enter the following. then click Apply: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 3.0/24 interface tunnel. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.4.0/24 interface tunnel. Routing set route 10. Policies set policy from untrust to trust any proxy sip permit set policy from trust to untrust proxy any sip permit save WebUI (for Branch Office 1) 1.3.4/24 Network > Interfaces > New Tunnel IF: Enter the following.Chapter 2: Session Initiation Protocol Application Layer Gateway set vpn vpn_branch-1 gateway to-branch-1 no-reply tunnel idletime 0 sec-level standard set vpn vpn-branch-1 id 1 bind interface tunnel.1.2 4.3.1. then click Apply: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 4.2 set route 10.

1. then click OK: Address Name: phone1 IPv4/Netmask: 10. To: Untrust) > New: Enter the following.1 VPNs > AutoKey Advanced > Gateway > New: Enter the following.5.1 Preshare Key: netscreen Outgoing Interface: ethernet3 VPNs > AutoKey IKE > New: Enter the following. then click Return to return to the basic Gateway configuration page: Bind to (select): Tunnel Interface. tunnel. then click OK: VPN Name: vpn-ns50 Advanced: Enter the following advanced settings.2.3 4.0/24 Interface (select): tunnel. then click OK: Gateway Name: to-ns50 Security Level: Standard IPvc4/v6 Address/Hostname: 5.3 Network > Routing > Destination > New: Enter the following.2. then click OK: Network Address / Netmask: 10.3. Routing Network > Routing > Destination > New: Enter the following. Policies Policies > (From: Trust.Concepts & Examples ScreenOS Reference Guide 2.0/24 Interface (select): tunnel.3/32 Zone: V1-Trust 3.1. then click OK: 60 Examples .5 Preshare Key: netscreen Outgoing Interface: ethernet4 VPNs > AutoKey IKE > New: Enter the following.5.1.1. then click OK: Gateway Name: to-central Security Level: Standard IPvc4/v6 Address/Hostname: 1.1. Address Policy > Policy Elements > Addresses > List > New: Enter the following. then click OK: VPN Name: vpn-central Advanced: Enter the following advanced settings. tunnel. VPN VPNs > AutoKey Advanced > Gateway > New: Enter the following. then click Return to return to the basic Gateway configuration page: Bind to (select): Tunnel Interface.1 5. then click OK: Network Address / Netmask: 10.

3.1/24 set interface ethernet1 route set interface ethernet3 zone untrust set interface ethernet3 ip 3.Chapter 2: Session Initiation Protocol Application Layer Gateway Source Address (select) Address Book Entry: phone2 Destination Address (select) Address Book Entry: Any-IPv4 Service: SIP Action: Permit Policies > (From: Untrust.1. then click OK: Source Address (select) Address Book Entry: Any-IPv4 Destination Address (select) Address Book Entry: phone2 Service: SIP Action: Permit CLI (for Branch Office 1) 1.5 main outgoing-interface ethernet4 preshare netscreen sec-level standard set vpn vpncentral gateway to-central no-replay tunnel idletime 0 sec-level standard set vpn vpncentral bind interface tunnel. Policies set policy from trust to untrust phone1 any sip permit set policy from untrust to trust any phone1 sip permit save WebUI (for Branch Office 2) 1.1.3 4. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.1 5. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10. VPN set ike gateway to-central address 1.0/24 interface tunnel.3 zone untrust set interface tunnel.3. Address set address trust phone1 10.1 set vpn vpn-ns50 gateway to-ns50 no-replay tunnel idletime 0 sec-level standard set vpn vpn-ns50 bind interface tunnel. To: Trust) > New: Enter the following.2 ip unnumbered interface ethernet3 set interface tunnel.3 ip unnumbered interface ethernet4 2.2.1.1.1.1.4/24 set interface tunnel.1/24 Examples 61 .3. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.1.4.3 set route 10.3/24 set interface ethernet4 zone untrust set interface ethernet4 ip 4.5.5.1.0/24 interface tunnel.2 zone untrust set interface tunnel.1 main outgoing-interface ethernet3 preshare netscreen sec-level standard set ike gateway to-ns50 address 5.1.2.4.3/32 3. Routes set route 10.

VPN VPNs > AutoKey Advanced > Gateway > New: Enter the following. then click OK: Gateway Name: to-central Security Level: Standard IPvc4/v6 Address/Hostname: 1.2.3/32 Zone: Trust 3.2 VPNs > AutoKey Advanced > Gateway > New: Enter the following.Concepts & Examples ScreenOS Reference Guide Enter the following.2. then click OK: 62 Examples . then click Return to return to the basic Gateway configuration page: Bind to (select): Tunnel Interface. then click OK: Interface mode: NAT Network > Interfaces > Edit (for ethernet3): Enter the following.1 Preshare Key: netscreen Outgoing Interface: ethernet3 VPNs > AutoKey IKE > New: Enter the following. then click OK: Address Name: phone2 IPv4/Netmask: 10.2.4. then click Apply: Tunnel Interface Name: 2 Zone (VR): Untrust Unnumbered (select) Interface: ethernet3 Network > Interfaces > New Tunnel IF: Enter the following.1.2.1.2/24 Network > Interfaces > Edit (for ethernet4): Enter the following.4/24 Network > Interfaces > New Tunnel IF: Enter the following. then click Apply: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 2. Address Policy > Policy Elements > Addresses > List > New: Enter the following.4. then click OK: VPN Name: vpn-central Advanced: Enter the following advanced settings. then click Apply: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 4. then click Apply: Tunnel Interface Name: 3 Zone (VR): Untrust Unnumbered (select) Interface: ethernet4 2. tunnel.

then click OK: Source Address (select) Address Book Entry: phone2 Destination Address (select) Address Book Entry: Any-IPv4 Service: SIP Action: Permit Policies > (From: Untrust.4. To: Trust) > New: Enter the following. To: Untrust) New Enter the following. then click OK: Source Address (select) Address Book Entry: Any-IPv4 Destination Address (select) Address Book Entry: phone2 Service: SIP Action: Permit Examples 63 .4 Preshare Key: netscreen Outgoing Interface: ethernet4 VPNs > AutoKey IKE > New: Enter the following. then click OK: Network Address / Netmask: 10.3. then click OK: Network Address / Netmask: 10.0/24 Interface (select): tunnel.1. then click Return to return to the basic Gateway configuration page: Bind to (select): Tunnel Interface.4.3 5. Policies Policies > (From: Trust.1.3 4. Routing Network > Routing > Destination > New: Enter the following.2 Network > Routing > Destination > New: Enter the following.1. tunnel.Chapter 2: Session Initiation Protocol Application Layer Gateway Gateway Name: to-ns50 Security Level: Standard IPvc4/v6 Address/Hostname: 4. then click OK: VPN Name: vpn-ns50 Advanced: Enter the following advanced settings.0/24 Interface (select): tunnel.

0/24 interface tunnel. Routes set route 10.3 ip unnumbered interface ethernet4 2.2.4/24 set interface tunnel.2/24 set interface ethernet4 zone untrust set interface ethernet4 ip 4.Concepts & Examples ScreenOS Reference Guide CLI (for Branch Office 2) 1.1/24 set interface ethernet3 zone untrust set interface ethernet3 ip 2.1.2.3 5.2 set route 10. The advantage of this strategy is that VoIP traffic can use additional bandwidth when it is available.2.1 Main outgoing-interface ethernet3 preshare netscreen sec-level standard set ike gateway to-ns50 address 4.4.3 zone untrust set interface tunnel.4. using the standard ScreenOS traffic shaping mechanisms: Guarantee bandwidth for VoIP traffic—The most effective way to ensure quality VoIP service. is to create a policy guaranteeing the minimum bandwidth necessary for the amount of VoIP traffic you expect on the interface and set priority queuing to the highest level. Address set address trust phone2 10.4. VPN set ike gateway to-central address 1. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.4.3/32 3.1.1.2 set vpn vpn-ns50 gateway to-ns50 no-replay tunnel idletime 0 sec-level standard set vpn vpn-ns50 id 5 bind interface tunnel. The disadvantage of this method is that non-VoIP traffic cannot use additional bandwidth even when VoIP traffic is not using it. and other types of traffic can use bandwidth not guaranteed for VoIP when VoIP traffic is not using it.1.0/24 interface tunnel. 64 Examples . Policies set policy from trust to untrust phone2 any sip permit set policy from untrust to trust any phone2 sip permit save Bandwidth Management for VoIP Services We recommend the following ways to manage bandwidth for VoIP services. and still allow other types of traffic on the interface.2 ip unnumbered interface ethernet3 set interface tunnel. You would also set priority queuing to the highest level for VoIP traffic.1.2.3.4Main outgoing-interface ethernet4 preshare netscreen sec-level standard set vpn vpncentral gateway to-central no-replay tunnel idletime 0 sec-level standard set vpn vpncentral id 4 bind interface tunnel.2.1. Limit bandwidth for non-VoIP traffic—By setting a maximum bandwidth for non-VoIP traffic. you make the remaining bandwidth available to VoIP traffic.2 zone untrust set interface tunnel.3 4.

If VoIP traffic suddenly needs more bandwidth. The illustration assumes you have determined you need to support at least eight VoIP calls (8 x 64 Kbps bandwidth per call. the security device marks the outer header of the IP packet (if the policy is configured to do so). For more information about configuring bandwidth and priority levels. In VPN configurations. Figure 21 on page 65 shows how priority-level settings can affect guaranteed bandwidth (gbw) and maximum bandwidth (mbw) usage on an ethernet1 (2 Mbps) interface. can enforce Quality of Service (QoS) in its DiffServ domain. it cannot get it unless it has a higher priority than the office-traffic services. This creates a 512 Kbps overlap of maximum bandwidth for VoIP and office-traffic services. You have guaranteed the remaining bandwidth to general office traffic and have set maximum bandwidth for your office traffic to include bandwidth not guaranteed to VoIP. shown by the dashed lines. The left side of Figure 21 shows what bandwidth usage with these settings looks like with high office-traffic usage and low VoIP traffic usage on the interface.Chapter 2: Session Initiation Protocol Application Layer Gateway Use priority queuing and Differentiated Services Codepoint (DSCP) marking—Guaranteeing bandwidth for VoIP traffic and limiting bandwidth for non-VoIP traffic both govern throughput on the security device. typically the LAN or WAN edge router. for a total of 512 Kbps) and occasionally as many as 16 calls. see “Traffic Shaping” on page 176. The right side of Figure 21 shows what bandwidth usage looks like in the same circumstance when you give VoIP traffic a higher priority and set office traffic to a lower priority. see “Traffic Shaping” on page 195. or leaves the TOS byte as 0 so that the next-hop router can enforce the correct QoS on the encrypted traffic. Figure 21: Priority-Level Settings Guaranteed and maximum bandwidth settings Adding priority level settings VoIP gbw 512 Kbps VoIP Traffic VoIP 2 Mbps Total Bandwidth mbw 1536 Kbps mbw 1024 Kbps 2 Mbps Total Bandwidth Office Traffic Office Traffic gbw 1024 Kbps Office Traffic Examples 65 . DSCP marking enables you to preserve your priority-queuing settings downstream and to keep or change the received DSCP value set by the originating networking device upstream so that the next-hop router. For information about how DSCP works with priority levels in policies.

Concepts & Examples ScreenOS Reference Guide 66 Examples .

The corresponding VoIP-based state machines are invoked to process the parsed information. Overview 67 . while the media gateways carry out the instructions of the call agent. maintains call control intelligence. Any malformed-packet attack is blocked by the ALG. The payload of the incoming VoIP signaling packet is fully inspected based on related RFCs and proprietary standards. The MGCP ALG performs the following procedures: Conducts VoIP signaling payload inspection. via the call agent. The payload of the incoming MGCP signaling packet is fully inspected in accordance with RFC 3435. Examples of typical scenarios follow a summary of the MGCP architecture. Conducts MGCP signaling payload inspection. Any out-of-state or out-of-transaction packet is identified and properly handled. This chapter includes the following sections: “Overview” on page 67 “MGCP Security” on page 68 “About MGCP” on page 68 “Examples” on page 73 Overview The Media Gateway Control Protocol (MGCP) is supported on security devices in route. MGCP is a text-based Application Layer protocol used for call setup and control.Chapter 3 Media Gateway Control Protocol Application Layer Gateway This chapter presents an overview of the Media Gateway Control Protocol (MGCP) Application Layer Gateway (ALG) and lists the firewall security features of the implementation. Any malformed packet attack is blocked by the ALG. Provides stateful processing. transparent. and Network Address Translation (NAT) mode. MGCP is based on a master-slave call control architecture in which the media gateway controller.

About MGCP MGCP is a text-based. Manages pinholes for VoIP traffic. Firewall policy enforcement between gateways (media policy). Per-gateway MGCP message flooding control. if necessary. the transaction level. are processed. Seamless switchover/failover if calls. including calls in progress. Firewall policy enforcement between gateway and gateway controller (signaling policy). and call state. and any needed pinhole is dynamically created and closed during call setup. MGCP packets matching the RFC 3435 message format. damage is contained within the impacted gateway. application layer protocol that can be used for call setup and control. Entities in MGCP There are four basic entities in MGCP: “Endpoint” on page 69 “Connection” on page 69 “Call” on page 69 “Call Agent” on page 69 68 MGCP Security . All other messages are dropped. and at the call level. are switched to the standby firewall in case of system failure. The protocol is based on a master/slave call control architecture: the media gateway controller (call agent) maintains call control intelligence. and media gateways carry out the instructions from the call agent. the IP address and port information used for media or signaling is identified by the ALG. transaction state. To keep the VoIP network secure. Any embedded IP address and port information in the payload is properly translated based on the existing routing information and network topology. MGCP Security The MGCP ALG includes the following security features: Denial of Service (DoS) attack protection—the ALG performs stateful inspection at the UDP packet level. Any malfunctioning or hacked gateway will not disrupt the whole VoIP network. and is replaced with the translated IP address and port number. Combined with per-gateway flooding control.Concepts & Examples ScreenOS Reference Guide Performs Network Address Translation (NAT). Per-gateway MGCP connection flooding control.

mynetwork.com Several network addresses can be associated under one domain name in the Domain Name System (DNS). which is created by the MGC when establishing a new call. trunk. An endpoint is named as below: local-endpoint-name@domain-name The following are some valid endpoint IDs: group1/Trk8@mynetwork. The media gateway controller (MGC) can instruct media gateways to create. The following are two examples of call agent names: CallAgent@voipCA. delete and audit a connection.168. However. The notified entity for an endpoint is the call agent currently controlling that endpoint.net group2/Trk1/*@[192. Call ID is a hexadecimal string with a maximum length of 32 characters.mynetwork.net (all endpoints within the MG) Connection Connections are created on each endpoint by a MG during call setup. Call Agent One or more call agents (also called media gateway controllers) are supported in MGCP to enhance reliability in VoIP network. different call agents might send MGCP commands to this endpoint. A complex call. By keeping track of the time to live (TTL) of DNS query/response data and implementing retransmission using other alternative network addresses.com voipCA. switchover and failover is achieved in MGCP. modify. A typical VoIP call involves two connections. An endpoint should send any MGCP command to its notified entity. Call A call is identified by its call ID. About MGCP 69 .net (any endpoint within the MG) *@voiptel. for example a three-party call or conference call.10. An endpoint can be an analog line. Two or more connections can have the same call ID if they belong to the same call. The concept of notified entity is essential in MGCP. and its maximum length is 32 characters. A connection is identified by its connection ID which is created by the MG when it is requested to create a connection. Call ID is unique within the MGC. might require more connections.8] (wild-carding) $@voiptel. or any other access point. Connection ID is presented as a hexadecimal string.Chapter 3: Media Gateway Control Protocol Application Layer Gateway Endpoint A media gateway (MG) is a collection of endpoints.

Table 3 lists supported MGCP commands.Concepts & Examples ScreenOS Reference Guide The notified entity is set to a provisioned value upon startup.1 t=0 0 m=audio 3456 RTP/AVP 0 70 About MGCP .] Mode.][Pac kageList] CreateConnection (CallId.] [encapsulated EPCF]) CRCX CRCX 1205 aaln/1@gw-25. composed of a parameter name followed by a parameter value. Refer to RFC 2234 for a complete explanation of command syntax.net MGCP 1. CreateConnection—used by a call agent to instruct the gateway to create a connection with.1 s=c=IN IP4 128.96.] [LocalConnectionDescriptor. the gateway.] [LocalConnectionOption. the command syntax.com MGCP 1. with a description of each.25678 753849 IN IP4 128. Commands The MGCP protocol defines nine commands for controlling endpoints and connections. optionally followed by session description protocol (SDP) information. Table 3: MGCP Commands (page 1 of 3) Command Verb Description EPCF Command Syntax Examples EPCF 2012 wxx/T2@mynet. ReturnCode. [ConnectionId.] [encapsulated RQNT. If the notified entity for an endpoint is empty or has not been set explicitly. and examples.0 C: A3C47F21456789F0 L: p:10.41. Zero or more parameter lines.att. but could be changed by a call agent through the use of a Notified Entity parameter contained in a MGCP message.] [SpecificEndPointId.41.96. a:PCMU M: sendrecv X: 0123456789AD R: L/hd S: L/rg v=0 o=. EndpointId. A command header has the following elements: A command line: command verb + transaction ID + endpointId + MGCP version.0 B: e:mu EndpointConfiguration—used by ReturnCode a call agent to inform a gateway [PackageList] of coding characteristics (a-law EndpointConfiguration (EndpointId.] [SecondEndPointId. and endpoint inside.] [SecondConnectionId. [{RemoteConnectionDescriptor | SecondEndpoindId}. All commands are composed of a command header. its value defaults to the source address of the last successful non-audit MGCP command received for that endpoint. or mu-law) expected by the line [BearerInformation]) side of the endpoint. [NotifiedEntity.

DeleteConnection can also be EndpointId.63.net MGCP 1. [PackageList] Notify (EndpointID.] [encapsulated RQNT.0 N: ca-new@callagent-ca.D/2.att.D/8.] [encapsulated EPCF]) RQNT The NotificationRequest ReturnCode.net MGCP 1.] specific endpoint.D/9.net MGCP 1. ObservedEvents) NTFY About MGCP 71 .] RequestIdentifier. PL=10.D/[0-9#*T](D)))) D: (0T|00T|xx|91xxxxxxxxxx|9011x.] change the parameters for an [PackageList] existing connection.net MGCP 1.L/hu.D/6 ModifyConnection—used by a ReturnCode.att.] [QuarantineHandling. JI=27.4723891 7428910 IN IP4 128. PR=780. ReturnCode. EndpointId. [DigitMap.96.D/ 9.D/4.D/0.63.] [encapsulated EPCF]) Notify—used by a gateway to inform the call agent when requested event(s) or signal(s) occur. call agent to instruct a gateway to ConnectionParameters. delete an existing connection.0 N: ca@ca1. command is used by a call agent [PackageList] to instruct a MG to monitor for NotificationRequest[(EndpointId. ConnectionId.att. [encapsulated RQNT.] [DetectEvents.D/1.net MGCP 1.T) S: T: G/ft NTFY 2002 aaln/1@rgw-25.Hardware error P: PS=1245.D/2. [PackageList] DeleteConnection (CallId.] sustained.net:5678 X: 0123456789AC O: L/hd.] [RemoteConnectionDescriptor.25 s=c=IN IP4 128. certain event(s) or signal(s) for a [NotifiedEntity.] [SignalRequests.att.] RequestIdentifier. D/2. ModifyConnection (CallId. [NotifiedEntity.0 C: A3C47F21456789F0 I: FDE234C8 E: 900 .25 t=0 0 m=audio 3456 RTP/AVP 0 Example 1: MGC -> MG DLCX 9210 aaln/1@rgw-25.D/1.att.0 C: A3C47F21456789F0 I: FDE234C8 Example 2: MG -> MGC DLCX 9310 aaln/1@rgw-25.Chapter 3: Media Gateway Control Protocol Application Layer Gateway Table 3: MGCP Commands (page 2 of 3) Command Verb Description MDCX Command Syntax Examples MDCX 1210 aaln/1@rgw-25. call agent to instruct a gateway to [LocalConnectionDescriptor.] [LocalConnectionOption. LA=48 RQNT 1205 aaln/1@rgw-25. [RequestedEvents. OS=62345. connection that can no longer be [NotifiedEntity.0 C: A3C47F21456789F0 I: FDE234C8 M: recvonly X: 0123456789AE R: L/hu S: G/rt v=0 o=.D/6.R(L/oc.att. OR=45123.att.96.net X: 0123456789AA R: L/hd(A. used by a gateway to release a ConnectionId. [NotifiedEntity.] [Mode.] [encapsulated EPCF]) DLCX DeleteConnection—used by a ReturnCode. E(S(L/dl).

] [LocalConnectionOptions. RestartMethod.X.Concepts & Examples ScreenOS Reference Guide Table 3: MGCP Commands (page 3 of 3) Command Verb Description AUEP AuditEndpoint—used by a call agent to audit the status of the endpoint. followed by ID 1204.] [QuarantineHandling.T.] [RequestedIdentifier.] [LocalConnectionDescriptor.I.] [MaxMGCPDatagram.N.] [DetectEvents.0 F: A. and optionally is followed by session description information.] [Mode.P RSIP RestartInProgress—used by a gateway to notify a call agent that one or more endpoints are being taken out of service or placed back in service. transaction ID. requires a response code. EndPointIdList. The response header in the following response message shows the response code 200 (successful completion).] [ReasonCode.] [PackageList] AuditConnection (EndpointId. and the comment: OK: 72 About MGCP .] [BearerInformation. whether successful or not.att. each containing a parameter name letter followed by its value.] [PackageList] RestartInProgress (EndpointId.] [NotifiedEntity.] [SignalRequests.net MGCP 1.] [RestartDelay. Command Syntax ReturnCode.] [ObservedEvents.att.att. [RestartDelay.N.] [RemoteConnectionDescriptor. [CallId. The response code is in the header of the response message. The response header is composed of a 3-digit response code.O Example 2: AUEP 1200 *@rgw-25.] [ConnectionParameters.0 RM: graceful RD: 300 Response Codes Every command sent by the calling agent or gateway.net MGCP 1.] [ConnectionIdentifier. ConnectionId. The response header is composed of a response line. and optionally followed by commentary.] [DigitMap.S.] [EventStats.D.LC. R.M.] [ReasonCode]) Examples Example 1: AUEP 1201 aaln/1@rgw-25.] [NotifiedEntity. RSIP 5200 aaln/1@rg2-25. [NotifiedEntity.net MGCP 1.att.] [Capabilities]} [PackageList] AuditEndpoint (EndpointId. AUCX 3003 aaln/1@rgw-25.net MGCP 1.0 I: 32F345E2 F: C. RequestedInfo) ReturnCode. [RequestedInfo]) ReturnCode.L.0 AUCX AuditConnection—used by a call agent to collect the parameters applied to a connection. followed by zero or more parameter lines. | { [RequestedEvents.] [BearerMethod.

residential customers are in the res_cust zone. in this example both gateways are in the same subnet. and then policies. 400 – 499: indicate a transient error (final response).25678 753849 IN IP4 128.41. The security device and the call agent are on the cable service provider’s premises. 200 – 299: indicate a successful completion (final response). it sends all MGCP commands to its current notified entity.96. or set-top box.41. A response to a command is sent to the source address of the command. Examples This section includes the following configuration scenarios: “Media Gateway in Subscribers’ Homes—Call Agent at the ISP” on page 73 “ISP-Hosted Service” on page 76 Media Gateway in Subscribers’ Homes—Call Agent at the ISP In this example (see Figure 22) you configure a security device at a Cable Service Provider to support MGCP for their network of residential subscribers. Although gateways frequently reside in different zones. not to the current notified entity. After creating zones—untrust_subscriber for the customers and trust_ca for the service provider. therefore no policy is needed for media.96. 500 – 599: indicate a permanent error (final response).1 t=0 0 m=audio 3456 RTP/AVP 96 a=rtpmap:96 G726-32/8000 The ranges of response codes are defined as follows: 000 – 099: indicate a response acknowledgement. However. RTP traffic between the gateways never passes through the firewall. requiring policies for media traffic.1 s=c=IN IP4 128. and send back responses to corresponding network addresses.Chapter 3: Media Gateway Control Protocol Application Layer Gateway 200 1204 OK I: FDE234C8 v=0 o=. 100 – 199: indicate a provisional response. An integrated Access Device (IAD). you configure addresses. is in each subscriber’s home. A media gateway can receive MGCP commands from various network addresses simultaneously. Refer to RFC 3661 for detailed information about response codes. The call agent is in the trust_ca zone. Examples 73 . acting as a gateway—each IAD represents a separate residence.

2. 10.0/24 Cable Service Provider Network Ethernet 4 10.1.1.1.Concepts & Examples ScreenOS Reference Guide Figure 22: Media Gateway in Subscribers’ Home Untrust IAD IAD Security Device Ethernet 3 2.2 IAD IAD IP Phone IP Phone IP Phone Trust Call Agent IP Phone WebUI 1. 1 call agent IP Address/Domain Name: IP/Netmask: (select).0/24 Zone: untrust-subscriber Policy > Policy Elements > Addresses > List > New: Enter the following.2.1. then click OK: Zone Name: untrust_subscriber Network > Zones > New: Enter the following. 2. Zones Network > Zones > New: Enter the following.101/32 Zone: trust_ca 74 Examples .2. then click OK: Zone Name: trust_ca 2. then click OK: Address Name: call_agent1 Comment: Our No.2. then click OK: Address Name: SubscriberSubNet Comment: Our subscribers’ network IP Address/Domain Name: IP/Netmask: (select). Addresses Policy > Policy Elements > Addresses > List > New: Enter the following.

Chapter 3: Media Gateway Control Protocol Application Layer Gateway 3.255.1.1.0 “Our subscribers' network” set address trust_ca call_agent1 10.2.2.255.255 “Our No. Interfaces Network > Interfaces > Edit (for ethernet3): Enter the following. SubscriberSubNet Destination Address Address Book Entry: (select).255. call_agent1 Service: MGCP-CA Action: Permit CLI 1. call_agent1 Destination Address Address Book Entry: (select). then click Apply: Zone Name: untrust_subscriber Static IP: (select this option when present) IP Address/Netmask: 2.0/24 Enter the following. then click OK: Interface Mode: route 4.1. 1 call agent” Examples 75 .2. then click OK: Interface Mode: route Network > Interfaces > Edit (for ethernet4): Enter the following.0 255. To: trust-ca) New: Enter the following.2. then click OK: Name: Pol-Subscribers-To-CA Source Address Address Book Entry: (select).101/32 Enter the following. SubscriberSubNet Service: MGCP-UA Action: Permit Policies > (From: untrust_subscriber. then click OK: Name: Pol-CA-To-Subscribers Source Address Address Book Entry: (select).255.101 255. then click Apply: Zone Name: trust_ca Static IP: (select this option when present) IP Address/Netmask: 10.1. To: untrust_subscriber) New: Enter the following. Policies Policies > (From: trust-ca. Zones set zone name untrust_subscriber set zone name trust_ca 2. Addresses set address untrust_subscriber SubscriberSubNet 2.

2.1.0/24 set interface ethernet3 route set interface ethernet4 zone trust_ca “Our No. 1 call agent” set interface ethernet4 ip 10. and supported by the gateway: sf_gw (2. After setting addresses for the gateways and the call agent.3. in this case: 3.2. Asia customers are in the Untrust zone. To allow MGCP signaling between the call agent in the DMZ and the gateway in the Untrust zone.101) is in the DMZ.1.101.3. you create one policy for each direction.201). Interfaces set interface ethernet3 zone untrust_subscriber “Our subscribers’ network” set interface ethernet3 ip 2. and supported by the gateway: asia_gw (3.2.2.2/24 set interface ethernet4 route 4. To protect the IP address of the call agent in the DMZ from exposure.110). (see Figure 23) an ISP located on the American west coast provides MGCP service to customers in Asia and San Francisco. 76 Examples .1. in route mode to allow them to stream media directly after call setup. you configure the interfaces. putting ethernet4 and ethernet5. you map the IP address of the call agent (10.3.1. A single policy is sufficient to allow bidirectional communication between gateways in the Trust and Untrust zones.101) to an IP address from the pool of addresses on the ethernet6 interface. Finally.Concepts & Examples ScreenOS Reference Guide 3. San Francisco customers are in the Trust zone. you create policies. you place a MIP on ethernet6. referencing the MIP that protects the call agent. Policies set policy name Pol-CA-TO-Subscribers from trust_ca to untrust_subscriber call_agent1 SubscriberSubNet mgcp-ua permit set policy name Pol-Subscribers-To-CA from untrust_subscriber to trust_ca SubscriberSubNet call_agent1 mgcp-ca permit ISP-Hosted Service In this example. which are trusted. that is. You create another pair of policies to allow signaling between the call agent and the gateway in the Trust zone.1.3.1. The call agent: west_ca (10.

2 Security Device ISP Network Eth4 .10 IP Phone asia_gw 3.1.3. then click OK: Address Name: sf_gw Comment: gateway in asia IP Address/Domain Name: IP/Netmask: (select).201/32 zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following.10.101 Virtual Device MIP on Ethernet6 3.2. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following.3.2.1.201 IP Phone WebUI 1.2.3.2.3. then click OK: Address Name: asia_gw Comment: gateway in asia IP Address/Domain Name: IP/Netmask: (select).10 Eth6 .110/32 zone: Untrust Policy > Policy Elements > Addresses > List > New: Enter the following.3. then click OK: Address Name: west_ca Comment: ca in west coast IP Address/Domain Name: IP/Netmask: (select).1.2.1.3. 10.Chapter 3: Media Gateway Control Protocol Application Layer Gateway Figure 23: ISP-Hosted Service DMZ west_ca 10.101 Eth5 .101/32 zone: DMZ Examples 77 . 3.3.1.2.3.1.10.1.1.3.110 Untrust Zone Trust Zone sf_gw 2.2.101 . 2.

then click OK: Mapped IP: 3. asia_gw Service: MGCP-UA Action: Permit Policies > (From: Untrust To: DMZ) New: Enter the following. then click Apply: Zone Name: Untrust Static IP: (select this option when present) IP Address/Netmask: 3.Concepts & Examples ScreenOS Reference Guide 2.255 Host IP Address: 10. then click Apply: Zone Name: DMZ Static IP: (select this option when present) IP Address/Netmask: 10. Interfaces Network > Interfaces > Edit (for ethernet4): Enter the following. west_ca Service: MGCP-CA Action: Permit 78 Examples .3.3. then click OK: Interface Mode: NAT 3.255.1. then click OK: Interface Mode: route Network > Interfaces > Edit (for ethernet6): Enter the following. then click OK: Source Address Address Book Entry: (select). asia_gw Destination Address Address Book Entry: (select).1.10/24 Enter the following. west_ca Destination Address Address Book Entry: (select).3.101 Host Virtual Router Name: trust-vr 4.255.1. then click Apply: Zone Name: Trust Static IP: (select this option when present) IP Address/Netmask: 2.2.101 Netmask: 255. then click OK: Source Address Address Book Entry: (select).2.1.10/24 Enter the following. Policies Policies > (From: DMZ To: Untrust) New: Enter the following.3. MIP Network > Interfaces > Edit (for ethernet6) > MIP > New: Enter the following.2/24 Enter the following. then click OK: Interface Mode: route Network > Interfaces > Edit (for ethernet5): Enter the following.

110/32 “gateway in asia” set address dmz west_ca 10. west_ca Destination Address Address Book Entry: (select).1. Interfaces set interface ethernet4 ip 2.Chapter 3: Media Gateway Control Protocol Application Layer Gateway Policies > (From: Trust To: DMZ) New: Enter the following.101 netmask 255.3. west_ca Service: MGCP-CA Action: Permit Policies > (From: DMZ To: Trust) New: Enter the following. then click OK: Source Address Address Book Entry: (select).101 host 10. sf_gw Destination Address Address Book Entry: (select).2.3.1.1. then click OK: Source Address Address Book Entry: (select).2.1. Addresses set address trust sf_gw 2.201/32 “gateway in s.2.2/24 set interface ethernet5 route set interface ethernet5 zone dmz set interface ethernet6 ip 3.10/24 set interface ethernet6 zone untrust 3.2. sf_gw Service: MGCP-UA Action: Permit Policies > (From: Trust To: Untrust) New: Enter the following.f.1.101/32 “ca in west coast” 2.1. then click OK: Source Address Address Book Entry: (select).255 vrouter trust-vr Examples 79 .3.255.3. Mapped IP Address set interface ethernet6 mip 3. asia_gw Service: MGCP-UA Action: Permit > Advanced: Enter the following.255. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) DIP on: None (Use Egress Interface IP) CLI 1.10/24 set interface ethernet4 route set interface ethernet4 zone trust set interface ethernet5 ip 10. sf_gw Destination Address Address Book Entry: (select).” set address untrust asia_gw 3.3.3.

3.Concepts & Examples ScreenOS Reference Guide 4.3. Policies set policy from dmz to untrust west_ca asia_gw mgcp-ua permit set policy from untrust to dmz asia_gw mip(3.101) mgcp-ca permit set policy from trust to dmz sf_gw west_ca mgcp-ca permit set policy from dmz to trust west_ca sf_gw mgcp-ua permit set policy from trust to untrust sf_gw asia_gw mgcp-ua nat src permit 80 Examples .

SCCP signaling payload inspection—fully inspects the payload of incoming SCCP signaling packets in accordance with RFC 3435. a Cisco H. Any malformed-packet attack is blocked by the ALG. a secondary) Call Manager over TCP on port 2000 and register with the primary Call Manager. Seamless failover—switches over all calls in process to the standby firewall during failure of the primary. known as the Call Manager. and Network Address Translation (NAT) modes. This connection is then used to establish calls coming to or from the client. transparent. Overview 81 . if available. Any malformed packet attack is blocked by the ALG. Examples of typical scenarios follow a summary of the SCCP architecture. VoIP signaling payload inspection—fully inspects the payload of incoming VoIP signaling packets based on related RFCs and proprietary standards. run the Skinny client and connect to a primary (and. SCCP is a binary-based Application Layer protocol used for Voice-over-Internet Protocol (VoIP) call setup and control. also called End Stations. In the SCCP architecture. does most of the processing. through the Call Manager. The SCCP ALG supports the following: Call flow from a Skinny client. This chapter includes the following sections: “Overview” on page 81 “SCCP Security” on page 82 “Examples” on page 87 Overview Skinny Client Control Protocol (SCCP) is supported on security devices in route. to another Skinny client.Chapter 4 Skinny Client Control Protocol Application Layer Gateway This chapter presents an overview of the Skinny Client Control Protocol (SCCP) Application Layer Gateway (ALG) and lists the firewall security features of the implementation.323 proxy. IP phones.

the transaction level. Any out-of-state or out-of-transaction packet is identified and properly handled. and the call level.Concepts & Examples ScreenOS Reference Guide Stateful processing—invokes the corresponding VoIP-based state machines to process the parsed information. based on the existing routing information and network topology. Firewall policy enforcement between Call Managers (Inter-Cluster). Seamless switchover/failover if calls. All other messages are dropped. Firewall policy enforcement between Cisco IP phones and the Call Manager (Intra-Cluster). Packets matching the SCCP message format. transaction state. and call state are processed. are switched to the standby firewall in case of system failure. with the translated IP address and port number. SCCP Security The SCCP ALG includes the following security features: Denial of Service (DoS) attack protection—The ALG performs stateful inspection at the UDP packet level. Network Address Translation (NAT)—translates any embedded IP address and port information in the payload. if necessary. including calls in progress. 82 SCCP Security . Per-gateway SCCP connection flooding control. Pinhole creation and management for VoIP traffic—identifies IP address and port information used for media or signaling and dynamically opens (and closes) pinholes to securely stream the media. Call Manager flood control—Protects the Call Manager from being flooded with new calls either by an already compromised connected client or by a faulty device. Firewall policy enforcement between gateways (media policy).

323 server with overall control of all devices and communication in the SCCP VoIP network. monitoring and controlling SCCP groups.323 for call setup.Chapter 4: Skinny Client Control Protocol Application Layer Gateway About SCCP The following sections give a brief overview of SCCP and how it works: “SCCP Components” on page 83 “SCCP Transactions” on page 84 “SCCP Messages” on page 87 SCCP Components The principle components of the SCCP VoIP architecture include the following: SCCP Client Call Manager Cluster SCCP Client The SCCP client runs on an IP phone. regions of numbers. Inter-Cluster calls using the gatekeeper for admission control and address resolution. also called an End Station. The Call Manager in the cluster knows about all SCCP clients in the cluster. which uses SCCP for signaling and for making calls. in which the Call Manager knows about each SCCP client. About SCCP 83 . Transmission of media is over RTP. Call Manager behavior varies in each of the following cluster scenarios: Intra-Cluster. it must first register with a Primary Call Manager (and a secondary. and the call is between SCCP clients of the same cluster. if available). Its functions include defining. in which the Call Manager needs to communicate with another Call Manager using H. The connection between the client and the Call Manager is over TCP on port 2000. Inter-Cluster. providing a redundant database that contains addresses. Cluster A Cluster is a collection of SCCP clients and a Call Manager.providing initialization. UDP. phone numbers. In order for a Skinny client to make a call. and IP. There can be more than one Call Manager for backup in a cluster. admission and registration of devices on the network. and route plans. This connection is then used to establish calls to or from the client. and number formats. and initiating contact with called devices or their agents to establish logical sessions in which voice communication can flow. Call Manager The Call Manager is a Cisco H.

SCCP Transactions SCCP transactions are the processes that need to take place in order for an SCCP call to proceed. the SCCP client needs to know the IP address of the Call Manager.cnf (xml) from TFTP server. such as protocol and version. If the TFTP name is not given. and other information. The client registers by providing the Call Manager with its IP address. SCCP transactions include the following: Client Initialization Client Registration Call Setup Media Setup Client Initialization To initialize. after initialization. the MAC address of the phone. The client then downloads the configuration file .Concepts & Examples ScreenOS Reference Guide Call Manager behavior also varies with calls between an SCCP client and a phone in a Public Switched Telephone Network (PSTN). The client needs the TFTP server name to download the configuration file: sepmacaddr. Initialization takes place on the local LAN. Client Registration The SCCP client. and other information about the IP gateway and DNS servers. its own IP address. the DNS server address. registers with the Call Manager over a TCP connection on well-known default port 2000. With this information. Table 4 lists SCCP messages and indicates messages that are of interest to the security device. 84 About SCCP . and with calls between an SCCP client and a phone in another administrative domain that is using H323. and the TFTP server name and address.cnf. the client contacts the Call Manager to register. CNF files contain the IP address or addresses of the primary and secondary Cisco Call Manager. The client sends a Dynamic Host Control Protocol (DHCP) request to get an IP address. the client uses the default filename in the IP phone. Keepalive messages keep this TCP connection open between the client and Call Manager so that the client can initiate or receive calls at any time. The client cannot initiate or receive calls until it is registered. provided that a policy on the security device allows this.

and a policy on the security device allows the call. the Call Manager is informed and terminates the media streams. If call setup is successful. After media setup. Media is streamed directly between clients through RTP/UDP/IP. Messages for call setup are sent to the Call Manager.Chapter 4: Skinny Client Control Protocol Application Layer Gateway Table 4: SCCP Registration Messages From Client RegisterMessage IPortMessage RegisterAckMessage CapabilititsRequest CapabilitiesResMessage ButtonTemplateReqMessage ButtonTemplateResMessage SoftKeyTemplateReqMessage SoftKeyTemplateResMessage LineStatReqMessage LineStatMessage x x From Call Manager Of Interest to Security Device x x x Call Setup IP phone-to-IP phone call-setup using SCCP is always handled by the Call Manager. which returns messages appropriate to the status of the call. About SCCP 85 . Media Setup The Call Manager sends the IP address and port number of the called party to the calling party. The Call Manager also sends the media IP address and port number of the calling party to the called party. the Call Manager sends the media setup messages to the client. media is transmitted directly between clients. When the call ends. At no time during this process does the Call Manager hand over call-setup function to the client.

CID 16777332) CloseRcvChn1(PPID 16778577. ln 1. CID16777333) OffHook CallState(OffHook.10.10. 2001->2002.10. ln 1. CnfrnId:0 OpenRcvChnAck1(PPID 16778577. CID 16777332) CallInfo(Outbound.10. CID 16777333) CallInfo(Inbound. ln 1. ln 1. CnfrId:0) StopMediaX(PPID 16778561.10. ln 1.20/Port:30198) RTP/UDP (10.10. Except for the OffHook message initiating the call from Phone1 and the OnHook message signaling the end of the call.20/30198 -> 10.10.10. Orig: 2002.10. CID16777333) StartMediaX(PPID 16778577. 2001->2002. CID16777332) OpenRcvChnAck1(PPID 16778561. ln 1. IP:10. CnffId:0) CallState(Terminate.20/Port:30198).20/30198. Orig: 2002. ln 1. CID 16777332) CallInfo(outboundcall.10.10. CnfrId: 0) CallState(Connected. IP:10. CID 16777332) CallInfo(Outbound. 10. CID 16777332) CloseRcvChn1(PPID 16778561. ln 1. IP:10. ln 1. CnfrId: 0) OpenRcvChn1(PPID 16778561. CID 16777332) keypadbutton CallState(Proceed. ln 1. CnffId:0 CallState(Connected. Orig: 2002.10. CID16777332) CallState(Ringout. CnffId:0) 86 About SCCP . 2001->2002. Figure 24: Call Setup and Teardown Phone1 OffHook CallState(offhook. CnfrId:0) StopMediaX(PPID 16778577. IP:10. CID 16777333) CallInfo(Inbound.10/24038) CallState(OnHook. 2001->2002.Concepts & Examples ScreenOS Reference Guide SCCP Control Messages and RTP Flow Figure 24 shows the SCCP control messages used to set up and tear down a simple call between Phone1 and Phone2.10/Port:24038) StartMediaX(PPID 16778561.10/Port:24038). CID 16777333) OpenRcvChn1(PPID 16778577.10. all aspects of the call are controlled by the Call Manager. ln 1.10.10. ln 1. ln 1. ln 1. 2001->2002. CID16777332) Call Manager Phone2 Callstate(RingIn.10.10/24038 -> 10.

0 Messages and Post Skinny 6. Table 5: Station to Call Manager Messages Message #define STATION_REGISTER_MESSAGE #define STATION_IP_PORT_MESSAGE #define STATION_ALARM_MESSAGE #define STATION_OPEN_RECEIVE_CHANNEL_ACK Range 0x00000001 0x00000002 0x00000020 0x00000022 Table 6: Call Manager to Station Messages Message #define STATION_START_MEDIA_TRANSMISSION #define STATION_STOP_MEDIA_TRANSMISSION #define STATION_CALL_INFO_MESSAGE #define STATION_OPEN_RECEIVE_CHANNEL_ACK #define STATION_CLOSE_RECEIVE_CHANNEL Range 0x00000001 0x00000002 0x00000020 0x00000022 0x00000106 Table 7: Call Manager 4.Chapter 4: Skinny Client Control Protocol Application Layer Gateway SCCP Messages Table 5. Table 7. and Table 8 list the SCCP call message IDs in the four intervals allowed by the security device.2 Message #define STATION_REGISTER_TOKEN_REQ_MESSAGE #define STATION_MEDIA_TRANSMISSION_FAILURE #define STATION_OPEN_MULTIMEDIA_RECEIVE_CHANNEL_ACK Range 0x00000029 0x0000002A 0x00000031 Table 8: Call Manager to Station Message #define STATION_OPEN_MULTIMEDIA_RECEIVE_CHANNEL #define STATION_START_MULTIMEDIA_TRANSMISSION #define STATION_STOP_MULTIMEDIA_TRANSMISSION #define STATION_CLOSE_MULTIMEDIA_RECEIVE_CHANNEL Range 0x00000131 0x00000132 0x00000133 0x00000136 Examples This section contains the following sample scenarios: “Example: Call Manager/TFTP Server in the Trust Zone” on page 88 “Example: Call Manager/TFTP Server in the Untrust Zone” on page 90 “Example: Three-Zone. Call Manager/TFTP Server in the DMZ” on page 92 Examples 87 . Table 6.

Call Manager/TFTP Server in Untrust Zone” on page 99 “Example: Full-Mesh VPN for SCCP” on page 101 Example: Call Manager/TFTP Server in the Trust Zone In this example. so that when phone2 boots up it can contact the TFTP Server and obtain the IP address of the Call Manager.4 WebUI 1. then click OK: Interface Mode: route Network > Interfaces > Edit (for ethernet3): Enter the following.1. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.1. and phone2 is on the ethernet3 interface in the Untrust zone.1.1.3 Virtual Device MIP on ethernet3 1. Figure 25: Call Manager/TFTP Server in the Private Zone ethernet1 10.Concepts & Examples ScreenOS Reference Guide “Example: Intrazone.1/24 Interface Mode: route 88 Examples . phone1 and the Call Manager/TFTP Server are on the ethernet1 interface in the Trust (private) zone.1.1.1.1/24 Trust Security Device LAN ethernet3 1.4 phone1 10.1.1.1.1.4 phone2 1. (We recommend that you change the IP address of the Call Manager in the TFTP Server config file (sep <mac_addr>.2 -> 10.1.cnf) to the MIP IP address of the Call Manager. You put a MIP for the Call Manager/TFTP Server on the ethernet3 interface.1.1.1.1.1.1. Call Manager/TFTP Server in Trust Zone” on page 95 “Example: Intrazone.) You then create a policy allowing SCCP traffic from the Untrust to the Trust zone and reference that MIP in the policy.1/24 Enter the following. You also create a policy from the Trust to the Untrust zone to allow phone1 to call out. then click OK: Zone: Untrust IP Address/Netmask: 1. then click OK: Zone: Trust Static IP: (select this option when present) IP Address/Netmask: 10.1/24 Untrust Internet CM/TFTP Server 10.

1.4/24 Zone: Untrust Policy > Policy Elements > Addresses > List > New: Enter the following.255. 10. then click OK: Mapped IP: 1.1.1.1.4/24 Zone: Trust 3. 10.1.1.1. To: Untrust) New: Enter the following. 1. then click OK: Address Name: CM-TFTP_Server IP Address/Domain Name: IP/Netmask: (select).2) Service: SCCP Examples 89 .1.1.1. phone2 Destination Address: Address Book Entry: (select).3) > MIP > New: Enter the following.255 Host IP Address: 10. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): None (Use Egress Interface IP) Policies > (From: Untrust.4 Host Virtual Router Name: trust-vr 4. MIP Network > Interfaces > Edit (for loopback. then click OK: Source Address: Address Book Entry: (select).255. then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select). Policies Policies > (From: Trust.1. MIP(1. To: Trust) New: Enter the following. then click OK: Source Address: Address Book Entry: (select) any Destination Address: Address Book Entry: (select) phone2 Service: SCCP Action: Permit > Advanced: Enter the following.1.Chapter 4: Skinny Client Control Protocol Application Layer Gateway 2.2 Netmask: 255. then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select).3/24 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following.

Figure 26: Call Manager/TFTP Server in the Untrust Zone ethernet1 10.1. and phone2 and the Call Manager/TFTP Server are on the ethernet3 interface in the Untrust zone. After configuring interfaces and addresses.3/24 set address untrust phone2 1.1.3 90 Examples .4 4. Example: Call Manager/TFTP Server in the Untrust Zone In this example.4/24 3.4 CM/TFTP Server 1. than to use the keyword any. Addresses set address trust phone1 10.1/24 set interface ethernet1 route set interface ethernet3 zone untrust set interface ethernet3 ip 1. phone1 is on the ethernet1 interface in the Trust zone.Concepts & Examples ScreenOS Reference Guide Action: Permit CLI 1. as shown in this example configuration.1.1.1.1/24 Trust Security Device Untrust Internet LAN phone1 10. MIP set interface ethernet3 mip 1.1.1.1.1.1.1.2) sccp permit save NOTE: It is always more secure to specify a service explicitly.2 host 10. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10. Policies set policy from trust to untrust any phone2 sccp nat src permit set policy from untrust to trust phone2 mip(1.1.1.1. you create policy from the Trust zone to the Untrust.1.1.4/24 set address trust cm-tftp_server 10. This allows phone1 to register with the Call Manager/TFTP Server in the Untrust zone.1.1.1.1.1.1/24 ethernet3 1.1.1/24 set interface ethernet3 route 2.1.3 phone2 1.1.1.1.

then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select). To: Untrust) New: Enter the following. Policies Policies > (From: Trust.1.1/24 Enter the following. then click OK: Address Name: CM/TFTP Server IP Address/Domain Name: IP/Netmask: (select). then click Return to set the advanced options and return to the basic configuration page: Examples 91 .1. 10. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.1.3/24 Zone: Untrust 3.1.1/24 Interface Mode: route 2. then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select). then click Apply: Zone Name: Trust Static IP: (select this option when present) IP Address/Netmask: 10.1.1. 1. then click OK: Interface Mode: route Network > Interfaces > Edit (for ethernet3): Enter the following. then click OK: Source Address Address Book Entry: (select) phone1 Destination Address Address Book Entry: (select) any Service: SCCP Action: Permit > Advanced: Enter the following.1.3/24 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following. then click OK: Zone Name: Untrust Static IP: (select this option when present) IP Address/Netmask: 1.1.1. 1.1.Chapter 4: Skinny Client Control Protocol Application Layer Gateway WebUI 1.4/24 Zone: Untrust Policy > Policy Elements > Addresses > List > New: Enter the following.

than to use the keyword any. Call Manager/TFTP Server in the DMZ In this example. the media flows directly between phone1 and phone2.3/24 set address untrust phone2 1.1. Addresses set address trust phone1 10. Example: Three-Zone. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.1/24 set interface ethernet1 route set interface ethernet3 zone untrust set interface ethernet3 ip 1. The arrows in Figure 27 show the flow of SCCP signaling traffic when phone2 in the Untrust zone places a call to phone1 in the Trust zone. phone2 is on the ethernet3 interface in the Untrust zone. Policies set policy from trust to untrust phone1 any sccp nat src permit save NOTE: It is always more secure to specify a service explicitly.1. you create a policy from the Trust zone to the DMZ to allow phone1 to communicate with the Call Manager/TFTP Server. For transmission of media.1.1/24 set interface ethernet3 route 2.1. and you create a policy from the Untrust zone to the DMZ to allow phone2 to communicate with the Call Manager/TFTP Server. and the Call Manager/TFTP Server is on the ethernet2 interface in the DMZ.1.1. For signaling. as shown in this example configuration.3/24 3. you create a policy from Trust to Untrust to allow phone1 and phone2 to communicate directly.4/24 set address untrust cm-tftp_server 1. After the session is initiated. phone1 is on the ethernet1 interface in the Trust zone.1.1.1.Concepts & Examples ScreenOS Reference Guide NAT: Source Translation: (select) (DIP on): None (Use Egress Interface IP) CLI 1.1. 92 Examples .

2.1.1.1.2.2/24 Network > Interfaces > Edit (for ethernet3): Enter the following. then click OK: Zone Name: Untrust Static IP: (select when this option is present) IP Address/Netmask: 1. then click OK: Zone Name: DMZ Static IP: (select when this option is present) IP Address/Netmask: 2.2.1.1.2.1/24 DMZ Security Device LAN ethernet1 10.1.2.1.2/24 ethernet3 1.1/24 Examples 93 .Chapter 4: Skinny Client Control Protocol Application Layer Gateway Figure 27: Call Manager/TFTP Server in the DMZ Untrust phone2 1.1.3 Trust WebUI 1.4 Internet CM/TFTP Server 2. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following. then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet2): Enter the following.1/24 LAN phone1 10.1. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10.1.1.1.2.1/24 Enter the following.4 ethernet2 2.

phone2 Destination Address: Address Book Entry: (select).1. then click OK: Source Address: Address Book Entry: (select).1. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: Enable (DIP on): None (Use Egress Interface IP) Policies > (From: Untrust. phone1 Destination Address: Address Book Entry: (select). To: DMZ) New: Enter the following. phone1 Destination Address: Address Book Entry: (select).2. CM-TFTP_Server Service: SCCP Action: Permit Policies > (From: Trust.4/24 Zone: Untrust Policy > Policy Elements > Addresses > List > New: Enter the following. 10.3/24 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following. then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select). then click OK: Address Name: CM-TFTP_Server IP Address/Domain Name: IP/Netmask: (select). Policies Policies > (From: Trust. Address Policy > Policy Elements > Addresses > List > New: Enter the following.4/24 Zone: DMZ 3.2. then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select). CM-TFTP_Server Service: SCCP Action: Permit > Advanced: Enter the following.1. then click OK: Source Address: Address Book Entry: (select). To: DMZ) New: Enter the following. then click OK: Source Address: Address Book Entry: (select).1. phone2 94 Examples . 2. To: Untrust) New: Enter the following.Concepts & Examples ScreenOS Reference Guide 2. 1.

as shown in this example configuration.) And finally.1. and the Call Manager/TFTP Server is on the ethernet1 interface in the Trust zone. Examples 95 . Addresses set address trust phone1 10.Chapter 4: Skinny Client Control Protocol Application Layer Gateway Service: SCCP Action: Permit > Advanced: Enter the following.4 3. Call Manager/TFTP Server in Trust Zone In this example.4/24 set address dmz cm-tftp_server 2. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.1.2. phone1 is on the ethernet4 interface in the Untrust zone.3/24 set address untrust phone2 1. add ethernet3 and ethernet4 to a loopback group.1/24 set interface ethernet3 route set interface ethernet2 zone dmz set interface ethernet2 ip 2. see “MIP and the Loopback Interface” on page 8-73.1. you unset blocking in the Untrust zone to allow intrazone communication.1.2. Creating a loopback interface enables you to use a single MIP for the Call Manager/TFTP Server in the Trust zone.2/24 set interface ethernet2 route 2.2.1/24 set interface ethernet1 route set interface ethernet3 zone untrust set interface ethernet3 ip 1.1. than to use the keyword any. To allow intrazone SCCP traffic between the two phones in the Untrust zone. (For more information about using loopback interfaces. Policies set policy from trust to dmz phone1 cm-tftp_server sccp nat src permit set policy from untrust to dmz phone2 cm-tftp_server sccp permit set policy from trust to untrust phone1 phone2 sccp nat src permit save NOTE: It is always more secure to specify a service explicitly.1.1. then put a MIP on the loopback interface to the IP address of the Call Manager/TFTP Server.2. Example: Intrazone.1. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: Enable (DIP on): None (Use Egress Interface IP) CLI 1. because intrazone blocking is on by default. you create a loopback interface. phone2 is in a subnet on the ethernet3 interface in the Untrust zone.

1. Call Manager/TFTP Server in Trust Zone Untrust phone1 1. then click OK: Interface Mode: NAT Network > Interfaces > Edit (for ethernet4): Enter the following.1.1/24 Enter the following.1. then click OK: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 1.1.1. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10.1/24 loopback 1 1.4 Internet ehternet4 1.1.Concepts & Examples ScreenOS Reference Guide Figure 28: Intrazone.1/24 CM/TFTP Server 10.2.1.1.1/24 ehternet3 1.1/24 96 Examples . Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.5 LAN Trust WebUI 1.4.1/24 Security Device MIP on loopback 1 1.1.1.1.2.5 ehternet1 10.1.1.1.1.4.5 -> 10.4 phone2 1.1.1.1.

Loopback Group Network > Interfaces > Edit (for ethernet3): Enter the following. then click OK: As member of loopback group: (select) loopback.1.4/32 Zone: Untrust Policy > Policy Elements > Addresses > List > New: Enter the following. then click OK: Address Name: CM-TFTP_Server IP Address/Domain Name: IP/Netmask: (select).4/32 Zone: Untrust 3.4.2.255 Host IP Address: 10. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following. 10.255. 1.1 Zone Name: Untrust Network > Interfaces > Edit (for ethernet4): Enter the following.1 Zone Name: Untrust 4.5 Netmask: 255. then click OK: Interface Name: loopback.2. then click OK: As member of loopback group: (select) loopback.1.1 Zone: Untrust (trust-vr) IP Address/Netmask: 1. then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select). then click OK: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 1.4.1.1.1/24 2. then click OK: Mapped IP: 1.1.1) > MIP > New: Enter the following.1. 1. then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select).5/32 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following.1.1/24 Network > Interfaces > New Loopback IF: Enter the following.1.Chapter 4: Skinny Client Control Protocol Application Layer Gateway Network > Interfaces > Edit (for ethernet3): Enter the following.1. MIP Network > Interfaces > Edit (for loopback.5 Examples 97 .1.255.

Concepts & Examples ScreenOS Reference Guide Host Virtual Router Name: trust-vr 5. Addresses set address trust cm-tftp_server 10.2.1.1.1 zone untrust set interface loopback.1. To: Trust) New: Enter the following.1/24 set interface loopback.1.1/24 set interface ethernet1 route set interface ethernet3 zone untrust set interface ethernet3 ip 1. Policies Policies > (From: Trust.1/24 set interface ethernet4 route set interface loopback.5) Service: SCCP Action: Permit CLI 1. Any Destination Address: Address Book Entry: (select).4/32 set address untrust phone2 1. CM-TFTP_Server Destination Address: Address Book Entry: (select).1 route 2. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: Enable (DIP on): None (Use Egress Interface IP) Policies > (From: Untrust.5/32 set address untrust phone1 1. then click OK: Source Address: Address Book Entry: (select).1.1.1.1 ip 1.2.4. then click OK: Source Address: Address Book Entry: (select).1.1.1. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10. To: Untrust) New: Enter the following. Blocking Network > Zones > Edit (for Untrust): Enter the following.1 98 Examples . then click OK: Block Intra-Zone Traffic: (clear) 6. Loopback Group set interface ethernet3 loopback-group loopback. MIP(1.1/24 set interface ethernet3 route set interface ethernet4 zone untrust set interface ethernet4 ip 1. Any Service: SCCP Action: Permit > Advanced: Enter the following.4/32 3.1.1.4.1 set interface ethernet4 loopback-group loopback.

1.1/24 Examples 99 .1/24 ethernet3 3. phone1 is on the ethernet1 interface in the Trust zone.3/24 CM/TFTP Server 3. This would allow you to specify the SCCP service. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10.1.1.1/24 WebUI 1.2.1 mip 1.2. also. MIP set interface loopback.4. that it is always more secure to specify a service explicitly. for greater security.3 ethernet1 10. Blocking unset zone untrust block 6. Call Manager/TFTP Server in Trust Zone phone1 10.1.3. than to use the keyword any.1.3.1. Blocking is off by default in the Trust zone (as it is in custom zones you define).5 host 10. Figure 29: Intrazone.Chapter 4: Skinny Client Control Protocol Application Layer Gateway 4. and create a policy from Trust to Trust.3. as shown in this example configuration.1.1. you create a policy from Trust to Untrust to allow phone1 and phone2 to register with the Call Manager/TFTP Server in the Untrust zone.1. in this example. so it is not necessary to create. Policies set policy from trust to untrust cm/tftp_server any sccp nat src permit set policy from untrust to trust any mip(1. Example: Intrazone.4 Trust Security Device LAN Untrust Internet phone2 10. However. you can accomplish the same thing by creating the following policy: set policy from untrust to untrust any any sccp permit Note.5 5. After configuring interfaces and addresses.1. you unset blocking in the Untrust zone to allow intrazone communication. you could optionally turn blocking off. and the Call Manager/TFTP Server is on the ethernet3 interface in the Untrust zone. Call Manager/TFTP Server in Untrust Zone In this example.1. and restrict intrazone calls to phone1 and phone2. phone 2 is on the ethernet2 interface in a subnet in the Trust zone.3.5) sccp permit save NOTE: Although.2 ethernet2 10. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following.1.4.

3. Any Destination Address: Address Book Entry: (select). then click OK: Interface Mode: route Network > Interfaces > Edit (for ethernet3): Enter the following.1. then click Return to set the advanced options and return to the basic configuration page: 100 Examples .3. then click OK: Source Address: Address Book Entry: (select).1/24 Enter the following. 10. then click OK: Interface Mode: route Network > Interfaces > Edit (for ethernet2): Enter the following.3/24 2. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10. then click OK: Address Name: phone2 IP Address/Domain Name: IP/Netmask: (select).3. To: Untrust) New: Enter the following.1.Concepts & Examples ScreenOS Reference Guide Enter the following.3/24 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following.2. then click OK: Address Name: phone1 IP Address/Domain Name: IP/Netmask: (select). CM/TFTP Server Service: SCCP Action: Permit > Advanced: Enter the following. 10. then click OK: Address Name: CM/TFTP Server IP Address/Domain Name: IP/Netmask: (select).4/24 Zone: Untrust 3.2.2/24 Zone: Trust Policy > Policy Elements > Addresses > List > New: Enter the following.1.1. Policies Policies > (From: Trust.3. then click OK: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 3. 3. Addresses Policy > Policy Elements > Addresses > List > New: Enter the following.

the central office and two branch offices are linked by a full-mesh VPN. NOTE: The security devices used in this example must have at least three independently configurable interfaces available. and phone2 is in the Trust zone at Branch Office Two.3. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.3. one to each of the other devices. Each site has a single security device.1.1/24 set interface ethernet3 zone untrust set interface ethernet3 ip 3. All interfaces connecting the devices are in their respective Untrust zones. Addresses set address trust phone1 10.1.1/24 set interface ethernet2 zone trust set interface ethernet2 ip 10. On each device.2.1. Example: Full-Mesh VPN for SCCP In this example.1.3/24 set interface ethernet3 route 2.3/24 set address trust phone2 10. as shown in this example configuration.Chapter 4: Skinny Client Control Protocol Application Layer Gateway NAT: Source Translation: Enable (DIP on): None (Use Egress Interface IP) CLI 1. The Call Manager/TFTP Server is in the Trust zone at the Central Office.4/24 3.1. Examples 101 . Policies set policy from trust to untrust any cm-tftp_server sccp nat src permit save NOTE: It is always more secure to specify a service explicitly.3. phone1 is in the Trust zone at Branch Office One.2. you configure two tunnels. than to use the keyword any.3.1.2/24 set address untrust cm-tftp_server 3. to create a fully meshed network.

2.3.2.4 Untrust eth4-5.Concepts & Examples ScreenOS Reference Guide Figure 30: Full-Mesh VPN for SCCP Note: The Untrust Zone for each device is not shown Central Office Trust Zone CM/TFTP Server 10.1 6. as shown in this example configuration.2.4.1 Trust Zone Branch Office One phone1 10.3.1 interface unnumbered Central tunnel 2 7.1.1.2 Untrust eth3-2.1 Untrust eth4-4.1.3.3 tunnel.1. WebUI (for Central) 1.1.5.3 interface unnumbered Gateway Router To branch-1: 4.7 Untrust eth2/2-1.1.2. then click Apply: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 1.2.3.7.1 tunnel.1.1 Gateway Router To central: 1.1.5.3 NOTE: It is always more secure to explicitly specify a service. than to use the keyword any.5 Trust Zone tunnel.2 interface unnumbered Trust eth1 10.3 Untrust eth3 3.2.6.1 To branch: 2.4 To branch-2: 5.1.6 Untrust eth2/1: 1.4.6.1.7.1.5 Trust eth1 10.5.4.1/24 Network > Interfaces > Edit (for ethernet2/2): Enter the following.2.2.1.2.1. Interfaces Network > Interfaces > Edit (for ethernet2/1): Enter the following.2. VPN 1 VPN 2 Branch-1 VPN 3 Branch-2 tunnel.1/24 102 Examples .3.1.1.3 tunnel.5.4.1.1 Gateway Router To central: 1.3 Trust eth2/8-10.3.3 interface unnumbered Branch Office Two phone2 10. then click Apply: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 1.1 To branch: 3.1.

6.3/32 Zone: Trust 3. then click OK: Gateway Name: to-branch-1 Security Level: Standard IPvc4/v6 Address/Hostname: 3. then click OK: Interface mode: route Network > Interfaces > New Tunnel IF: Enter the following.6.3. then click Return to return to the basic Gateway configuration page: Bind to: (select) Tunnel Interface.Chapter 4: Skinny Client Control Protocol Application Layer Gateway Network > Interfaces > Edit (for ethernet2/8): Enter the following.1/24 Enter the following. then click OK: VPN Name: vpn-branch-1 Advanced: Enter the following advanced settings. VPN VPNs > AutoKey Advanced > Gateway > New: Enter the following. then click Apply: Tunnel Interface Name: 1 Zone (VR): Untrust IP Address / Netmask: 6.7.2. then click Apply: Tunnel Interface Name: 2 Zone (VR): Untrust IP Address / Netmask: 7.6/24 Network > Interfaces > New Tunnel IF: Enter the following.1. then click OK: Address Name: CM/TFTP Server IPv4/Netmask: 10.1 VPNs > AutoKey Advanced > Gateway > New: Enter the following. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10. Address Policy > Policy Elements > Addresses > List > New: Enter the following.3 Preshare Key: netscreen Outgoing Interface: ethernet2/1 VPNs > AutoKey IKE > New: Enter the following.3.7.7/24 2.3.1.3. then click OK: Gateway Name: to-branch-2 Security Level: Standard IPvc4/v6 Address/Hostname: 2.2. tunnel.2 Preshare Key: netscreen Outgoing Interface: ethernet2/2 Examples 103 .

then click OK: Network Address / Netmask: 10. Routing Network > Routing > Destination > New: Enter the following.7/24 Address set address trust cm-tftp_server 10. then click OK: Source Address (select) Address Book Entry: CM/TFTP Server Destination Address (select) Address Book Entry: Any-IPv4 Service: SCCP Action: Permit Policies > (From: Untrust.7.2. tunnel.6/24 interface tunnel.1.2 ip 7.1.7.2 4. To: Trust) > New: Enter the following.1.6.1/24 interface ethernet2/8 route interface tunnel. then click Return to return to the basic Gateway configuration page: Bind to: (select) Tunnel Interface.1 Network > Routing > Destination> New: Enter the following.1.1/24 interface ethernet2/2 zone untrust interface ethernet2/2 ip 1.1/24 interface ethernet2/8 zone trust interface ethernet2/8 ip 10. To: Untrust) New Enter the following. Policies Policies > (From: Trust.Concepts & Examples ScreenOS Reference Guide VPNs > AutoKey IKE > New: Enter the following.1 ip 6.3.1. interface ethernet2/1 zone untrust interface ethernet2/1 ip 1.1. then click OK: Network Address / Netmask: 10.3/32 104 Examples .2 zone untrust interface tunnel. then click OK: Source Address (select) Address Book Entry: Any-IPv4 Destination Address (select) Address Book Entry: CM/TFTP Server Service: SCCP Action: Permit CLI (for Central) 1.1.2 5.6. Interfaces set set set set set set set set set set set 2.0/24 Interface (select): tunnel.0/24 Interface (select): tunnel.1 zone untrust interface tunnel.3.1.2. then click OK: VPN Name: vpn-branch-2 Advanced: Enter the following advanced settings.

3 main outgoing-interface ethernet2/1 preshare netscreen sec-level standard set ike gateway to-branch-2 address 2.1/24 Interface mode: route Network > Interfaces > Edit (for ethernet3): Enter the following.3.Chapter 4: Skinny Client Control Protocol Application Layer Gateway 3.4. then click Apply: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 3.3/24 Network > Interfaces > Edit (for ethernet4): Enter the following.2.1.3.3.1.2 main outgoing-interface ethernet2/2 preshare netscreen sec-level standard set vpn vpn_branch-1 gateway to-branch-1 no-reply tunnel idletime 0 sec-level standard set vpn vpn-branch-1 id 1 bind interface tunnel. then click Apply: Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 4. Interfaces Network > Interfaces > Edit (for ethernet1): Enter the following. Policies set policy from trust to untrust cm-tftp_server any sccp permit set policy from untrust to trust any cm-tftp_server sccp permit save WebUI (for Branch Office 1) 1.1. Routing set route 10.1 5.2. then click Apply: Tunnel Interface Name: 2 Zone (VR): Untrust Unnumbered (select) Interface: ethernet3 Network > Interfaces > New Tunnel IF: Enter the following. then click Apply: Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10.0/24 interface tunnel.2 set route 10.1.4/24 Network > Interfaces > New Tunnel IF: Enter the following.1.4.3. then click Apply: Tunnel Interface Name: 3 Zone (VR): Untrust Unnumbered (select) Interface: ethernet4 Examples 105 .0/24 interface tunnel.2 4.2. VPN set ike gateway to-branch-1 address 3.1 set vpn vpn-branch-2 gateway to-branch-2 no-reply tunnel idletime 0 sec-level standard set vpn vpn-branch-2 id 2 bind interface tunnel.

then click OK: VPN Name: vpn-ns50 Advanced: Enter the following advanced settings.5 Preshare Key: netscreen Outgoing Interface: ethernet4 VPNs > AutoKey IKE > New: Enter the following.1 VPNs > AutoKey Advanced > Gateway > New: Enter the following.2. Address Policy > Policy Elements > Addresses > List > New: Enter the following.3 Network > Routing > Destination > New: Enter the following.1. then click OK: Address Name: phone1 IPv4/Netmask: 10.1 106 Examples .2.0/24 Interface (select): tunnel. then click OK: Gateway Name: to-central Security Level: Standard IPvc4/v6 Address/Hostname: 1. then click Return to return to the basic Gateway configuration page: Bind to (select): Tunnel Interface. then click OK: Gateway Name: to-ns50 Security Level: Standard IPvc4/v6 Address/Hostname: 5. Routing Network > Routing > Destination> New: Enter the following. tunnel. then click OK: Network Address / Netmask: 10.3 4.1.1.1 Preshare Key: netscreen Outgoing Interface: ethernet3 VPNs > AutoKey IKE > New: Enter the following.0/24 Interface (select): tunnel. then click OK: VPN Name: vpn-central Advanced: Enter the following advanced settings.1. then click Return to return to the basic Gateway configuration page: Bind to (select): Tunnel Interface.5. VPN VPNs > AutoKey Advanced > Gateway > New: Enter the following. tunnel. then click OK: Network Address / Netmask: 10.5.3.3/32 Zone: V1-Trust 3.Concepts & Examples ScreenOS Reference Guide 2.1.

2 zone untrust set interface tunnel. Routes set route 10. To: Trust) > New: Enter the following.3 zone untrust set interface tunnel.3 4. then click OK: Source Address (select) Address Book Entry: phone2 Destination Address (select) Address Book Entry: Any-IPv4 Service: SCCP Action: Permit Policies > (From: Untrust. then click OK: Source Address (select) Address Book Entry: Any-IPv4 Destination Address (select) Address Book Entry: phone2 Service: SCCP Action: Permit CLI (for Branch Office 1) 1.1.1 set vpn vpn-ns50 gateway to-ns50 no-replay tunnel idletime 0 sec-level standard set vpn vpn-ns50 bind interface tunnel. To: Untrust) > New: Enter the following.3/24 set interface ethernet4 zone untrust set interface ethernet4 ip 4.1.3. Address set address trust phone1 10.1. Policies Policies > (From: Trust.3.5.3.1 5.4.1. VPN set ike gateway to-central address 1.3/32 3.3 ip unnumbered interface ethernet4 2.1.3 set route 10. Policies set policy from trust to untrust phone1 any sccp permit set policy from untrust to trust any phone1 sccp permit save Examples 107 .2 ip unnumbered interface ethernet3 set interface tunnel.1.5 main outgoing-interface ethernet4 preshare netscreen sec-level standard set vpn vpncentral gateway to-central no-replay tunnel idletime 0 sec-level standard set vpn vpncentral bind interface tunnel.1 main outgoing-interface ethernet3 preshare netscreen sec-level standard set ike gateway to-ns50 address 5.4.1.Chapter 4: Skinny Client Control Protocol Application Layer Gateway 5.4/24 set interface tunnel.1/24 set interface ethernet1 route set interface ethernet3 zone untrust set interface ethernet3 ip 3.0/24 interface tunnel.1.2. Interfaces set interface ethernet1 zone trust set interface ethernet1 ip 10.5.0/24 interface tunnel.

Concepts & Examples ScreenOS Reference Guide

WebUI (for Branch Office 2)
1. Interfaces

Network > Interfaces > Edit (for ethernet1): Enter the following, then click Apply:
Zone: Trust Static IP: (select when this option is present) IP Address/Netmask: 10.1.2.1/24 Enter the following, then click OK: Interface mode: route

Network > Interfaces > Edit (for ethernet3): Enter the following, then click Apply:
Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 2.2.2.2/24

Network > Interfaces > Edit (for ethernet4): Enter the following, then click Apply:
Zone: Untrust Static IP: (select when this option is present) IP Address/Netmask: 4.4.4.4/24

Network > Interfaces > New Tunnel IF: Enter the following, then click Apply:
Tunnel Interface Name: 2 Zone (VR): Untrust Unnumbered (select) Interface: ethernet3

Network > Interfaces > New Tunnel IF: Enter the following, then click Apply:
Tunnel Interface Name: 3 Zone (VR): Untrust Unnumbered (select) Interface: ethernet4
2. Address

Policy > Policy Elements > Addresses > List > New: Enter the following, then click OK:
Address Name: phone2 IPv4/Netmask: 10.1.2.3/32 Zone: Trust
3. VPN

VPNs > AutoKey Advanced > Gateway > New: Enter the following, then click OK:
Gateway Name: to-central Security Level: Standard IPvc4/v6 Address/Hostname: 1.1.2.1 Preshare Key: netscreen Outgoing Interface: ethernet3

108

Examples

Chapter 4: Skinny Client Control Protocol Application Layer Gateway

VPNs > AutoKey IKE > New: Enter the following, then click OK:
VPN Name: vpn-central

Advanced: Enter the following advanced settings, then click Return to return to the basic Gateway configuration page:
Bind to (select): Tunnel Interface, tunnel.2

VPNs > AutoKey Advanced > Gateway > New: Enter the following, then click OK:
Gateway Name: to-ns50 Security Level: Standard IPvc4/v6 Address/Hostname: 4.4.4.4 Preshare Key: netscreen Outgoing Interface: ethernet4

VPNs > AutoKey IKE > New: Enter the following, then click OK:
VPN Name: vpn-ns50

Advanced: Enter the following advanced settings, then click Return to return to the basic Gateway configuration page:
Bind to (select): Tunnel Interface, tunnel.3
4. Routing

Network > Routing > Destination > New: Enter the following, then click OK:
Network Address / Netmask: 10.1.3.0/24 Interface (select): tunnel.2

Network > Routing > Destination > New: Enter the following, then click OK:
Network Address / Netmask: 10.1.1.0/24 Interface (select): tunnel.3
5. Policies

Policies > (From: Trust, To: Untrust) New Enter the following, then click OK:
Source Address (select) Address Book Entry: phone2 Destination Address (select) Address Book Entry: Any-IPv4 Service: SCCP Action: Permit

Policies > (From: Untrust, To: Trust) > New: Enter the following, then click OK:
Source Address (select) Address Book Entry: Any-IPv4 Destination Address (select) Address Book Entry: phone2 Service: SCCP Action: Permit

Examples

109

Concepts & Examples ScreenOS Reference Guide

CLI (for Branch Office 2)
1. Interfaces

set interface ethernet1 zone trust set interface ethernet1 ip 10.1.2.1/24 set interface ethernet1 route set interface ethernet3 zone untrust set interface ethernet3 ip 2.2.2.2/24 set interface ethernet4 zone untrust set interface ethernet4 ip 4.4.4.4/24 set interface tunnel.2 zone untrust set interface tunnel.2 ip unnumbered interface ethernet3 set interface tunnel.3 zone untrust set interface tunnel.3 ip unnumbered interface ethernet4
2. Address

set address trust phone1 10.1.2.3/32
3. VPN

set ike gateway to-central address 1.1.1.1 Main outgoing-interface ethernet3 preshare netscreen sec-level standard set ike gateway to-ns50 address 4.4.4.4 Main outgoing-interface ethernet4 preshare netscreen sec-level standard set vpn vpncentral gateway to-central no-replay tunnel idletime 0 sec-level standard set vpn vpncentral id 4 bind interface tunnel.2 set vpn vpn-ns50 gateway to-ns50 no-replay tunnel idletime 0 sec-level standard set vpn vpn-ns50 id 5 bind interface tunnel.3
4. Routes

set route 10.1.3.0/24 interface tunnel.1 set route 10.1.2.0/24 interface tunnel.3
5. Policies

set policy from trust to untrust phone2 any sccp permit set policy from untrust to trust any phone2 sccp permit save

110

Examples

Chapter 5

Apple iChat Application Layer Gateway
This chapter describes the Apple iChat application and provides examples for configuring the AppleiChat Application Layer Gateway (ALG) on a Juniper Networks security device. It contains the following sections: “Overview” on page 111 “Configuring the AppleiChat ALG” on page 112 “Configuration Examples” on page 113

Overview
Apple iChat is an Instant Messaging (IM) application that lets you chat with other iChat, Mac, or AOL Instant Messenger (AIM) users over the Internet using text, audio, or video. ScreenOS currently supports iChat applications up to version 3.15. The iChat application uses standard ports to send data to its servers and clients. The AppleiChat ALG provides support for iChat applications by opening pinholes on Juniper Networks security device, thereby allowing the text, audio, and video calls to pass through the security device. Without the AppleiChat ALG, the ports are blocked and need to be opened manually, which exposes the network to attack on these ports. Table 9 shows the standard ports iChat uses for various services.
Table 9: Standard iChat Service Ports Port Number
5190 5678 5060 16384 16403

Service Name
AOL SNATMAP server Session Initiation Protocol (SIP) Real-Time Transport Protocol (RTP) /Real-Time Control Protocol (RTCP)

Protocol
TCP UDP UDP/TCP UDP

Used For
iChat and AOL instant messenger, file transfer Determining the external Internet addresses of hosts. Initiating audio/video (AV) chat invitations. iChat audio RTP/RTCP video RTP/RTCP

Overview

111

During iChat operation. then click Apply: AppleiChat Enable (select) CLI set alg appleichat enable When you enable the AppleiChat ALG functionality. see http://docs. The call-answer-time is the duration of time for which the security device opens the pinholes for establishing iChat audio/video session.com/article. 112 Configuring the AppleiChat ALG . SIP is a predefined service in ScreenOS and uses port 5060 as the destination port. see http://docs. The number of iChat sessions that the security device can handle is limited to the maximum number of Network Address Translation (NAT) cookies available for that particular security device. NOTE: The NAT cookies available for a security device are shared by other ALGs like H.info. the security device opens pinholes for the configured call-answer-time to establish the iChat audio/video session.323 and P2P ALG. Select the following.apple. SIP is used for setting audio/video sessions between IM clients after they successfully negotiate ports.info. The default value of call-answer-time is 32 seconds. the security device creates separate sessions for AOL and SIP. When this timer expires. WebUI Security>ALG>Apple iChat.html?artnum=106439 The iChat service uses the AOL and SIP protocols for its audio/video operations. It uses the AIM protocol to connect to servers.apple. NOTE: The ALG does not open all ports when you enable the AppleiChat ALG on the security device. You can view the maximum number of NAT cookies available for a particular device using the following CLI command: get nat cookie For information about running iChat in NAT mode.Concepts & Examples ScreenOS Reference Guide For a list of well-known ports. ALG opens pinholes only for the ports that are exchanged during iChat signaling messages.html?artnum=93208 Configuring the AppleiChat ALG You configure the AppleiChat ALG with the WebUI or the CLI.com/article. The SIP ALG creates pinholes for audio/video sessions. The range for configuring the call-answer-time is 20 to 90 seconds. the device closes the pinholes.

one iChat user is on a private network. WebUI Security>ALG>AppleiChat. There is a NAT between the private and the public network. Enter the following. By default. and an iChat server on a public network An intra-zone call between two iChat users within a private network Users across different firewalls Scenario 1: Private–Public Network In Figure 31.Chapter 5: Apple iChat Application Layer Gateway To configure a call-answer-time of 30 seconds: WebUI Security>ALG>AppleiChat. Figure 31: AppleiChat Scenario 1—Users on Public and Private Networks Trust zone Ethernet Ethernet NAT iChat UserB iChat Server Untrust zone iChat UserA Juniper Networks Security Device Configuration Examples 113 . The MSS value depends on the network configuration of the receiver. Select the following. The MSS is the maximum amount of data. the reassembly option is disabled. in bytes. another iChat user on a public network. then click Apply: Call-Answer-Time: 30 CLI set alg appleichat call-answer-time 30 The iChat application fragments the packets it sends to the receiver based on the maximum segment size (MSS) of the receiver. and the iChat server is on public network. another iChat user is on a public network. You can enable reassembly with the WebUI or the CLI. The fragmented packet is reassembled at the ALG for address translation. a device can receive as a single unfragmented frame. then click Apply: Re-Assembly Enable (select) CLI set alg appleichat reassembly enable Configuration Examples This section includes the following configuration scenarios: One iChat user on a private network.

then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) 2. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) Policies > (From: Trust. Configuration for Logging into the Server in NAT Mode Policies > (From: Trust. then click OK: Source Address Address Book Entry: (select). we recommend that the user put "ANY" in the destination address field of the policy. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) 114 Configuration Examples . WebUI 1. iChatserver_IP_range Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. iChat UserA Destination Address Address Book Entry: (select). ANY Service: (select) AppleiChat Action: Permit > Advanced: Enter the following.Concepts & Examples ScreenOS Reference Guide NOTE: Because the administrator does not know the IP address details initially. iChat UserB Destination Address Address Book Entry: (select). To: Untrust) New: Enter the following. To: Untrust) New: Enter the following. then click OK: Source Address Address Book Entry: (select). To: Untrust) New: Enter the following. ANY Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. Configuration for File Transfer from iChat UserA to iChat UserB in NAT Mode Policies > (From: Trust. then click OK: Source Address Address Book Entry: (select). iChat UserA Destination Address Address Book Entry: (select).

iChat UserA Destination Address Address Book Entry: (select). To: Untrust) New: Enter the following.Chapter 5: Apple iChat Application Layer Gateway 3. then click OK: Source Address Address Book Entry: (select). Configuration for Making Audio/Video Calls from iChat UserB in Route Mode Policies > (From: Trust. To: Untrust) New: Enter the following. iChat UserA Destination Address Address Book Entry: (select). iChat UserA Destination Address 115 Configuration Examples . To: Untrust) New: Enter the following. iChatserver_IP_range Service: (select) AppleiChat Action: Permit Policies > (From: Trust. then click OK: Source Address Address Book Entry: (select). Configuration for Making Audio/Video Calls from iChat UserB in NAT Mode Policies > (From: Trust. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) Policies > (From: Trust. To: Untrust) New: Enter the following. iChat UserA Destination Address Address Book Entry: (select). then click OK: Source Address Address Book Entry: (select). iChat UserB Service: (select) AppleiChat Action: Permit 5. then click OK: Source Address Address Book Entry: (select). then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) 4. iChatserver_IP_range Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. iChat UserA Destination Address Address Book Entry: (select). Configuration for Making Audio/Video Calls from iChat UserA in NAT Mode Policies > (From: Trust. iChat UserB Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. then click OK: Source Address Address Book Entry: (select). To: Untrust) New: Enter the following.

iChatserver_IP_range Service: (select) AppleiChat Action: Permit Policies > (From: Trust. Configuration for Logging into the Server in NAT Mode set policy from trust to untrust "ichatUserA" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserA" "iChatserver_IP_range" apple-ichat nat src permit NOTE: Policies for route/transparent mode are same except the "nat src" option in policy. iChat UserA Destination Address Address Book Entry: (select). then click OK: Source Address Address Book Entry: (select). then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) Policies > (From: Trust. Configuration for Making Audio/Video Calls from iChat UserA in Route Mode Policies > (From: Trust. iChat UserB Service: (select) AppleiChat Action: Permit CLI 1. iChat UserA Destination Address Address Book Entry: (select). then click OK: Source Address Address Book Entry: (select). 116 Configuration Examples . To: Untrust) New: Enter the following. iChatserver_IP_range Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. then click OK: Source Address Address Book Entry: (select). iChat UserA Destination Address Address Book Entry: (select). To: Untrust) New: Enter the following.Concepts & Examples ScreenOS Reference Guide Address Book Entry: (select). To: Untrust) New: Enter the following. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) 6. iChat UserB Service: (select) AppleiChat Action: Permit > Advanced: Enter the following.

Chapter 5: Apple iChat Application Layer Gateway 2. iChat userA and iChat userB are in the same network and behind a firewall. Configuration for Making Audio/Video Calls from iChat UserB in NAT Mode set policy from trust to untrust "ichatUserA" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserA" "iChatserver_IP_range" apple-ichat nat src permit set policy from trust to untrust "iChatUserA" "iChatUserB" apple-ichat nat src permit 4. Configuration for Making Audio/Video Calls from iChat UserA in NAT Mode set policy from trust to untrust "ichatUserA" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserA" "iChatserver_IP_range" apple-ichat nat src permit set policy from trust to untrust "ichatuserA" "iChatUserB" apple-ichat nat src permit 6. There is a NAT between the private and the public networks. Configuration for File Transfer from iChat UserA to iChat UserB in NAT Mode set policy from trust to untrust "ichatUserA" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserA" "iChatserver_IP_range" apple-ichat nat src permit set policy from trust to untrust "ichatUserB" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserB" "iChatserver_IP_range" apple-ichat nat src permit 3. The iChat server is in public network. Configuration Examples 117 . Configuration for Making Audio/Video Calls from iChat UserB in Route Mode set policy from trust to untrust "ichatUserA" "ANY" apple-ichat permit OR set policy from trust to untrust "ichatUserA" "iChatserver_IP_range" apple-ichat permit set policy from trust to untrust "iChatUserA" "iChatuserB" apple-ichat permit 5. Configuration for Making Audio/Video Calls from iChat UserA in Route Mode set policy from trust to untrust "ichatUserA" "ANY" permit OR set policy from trust to untrust "ichatUserA" "iChatserver_IP_range" apple-ichat permit set policy from trust to untrust "ichatuserA" "iChatUserB" apple-ichat permit Scenario 2: Intrazone Call Within Private Network In the example shown in Figure 32.

To: Untrust) New: Enter the following. ANY Service: (select) AppleiChat Action: Permit 118 Configuration Examples . iChatserver_IP_range Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. To: Untrust) New: Enter the following. any Service: AppleiChat Action: Permit > Advanced: Enter the following. Configuration for File Transfer from iChat UserA to iChat UserB Policies > (From: Trust. Configuring iChat userA to Log In iChat server in NAT Mode Policies > (From: Trust. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) Policies > (From: Trust. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) 2. To: Untrust) New: Enter the following. then click OK: Source Address Address Book Entry: (select). iChat UserB Destination Address Address Book Entry: (select). then click OK: Source Address Address Book Entry: (select).Concepts & Examples ScreenOS Reference Guide Figure 32: AppleiChat Scenario 2—Intrazone Call Within a Private Network Trust zone Ethernet iChat UserA Juniper Networks Security Device iChat UserB iChat Server NAT Ethernet Untrust zone WebUI 1. then click OK: Source Address Address Book Entry: (select). iChat UserA Destination Address Address Book Entry: (select). iChat UserA Destination Address Address Book Entry: (select).

iChatServer Configuration Examples 119 . ichatServer Service: (select) AppleiChat Action: Permit 5. Configuration for Making Audio/Video Calls from iChat UserA in NAT Mode Policies > (From: Trust. iChat UserB Destination Address Address Book Entry: (select). ANY Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. To: Untrust) New: Enter the following. iChat UserA Destination Address Address Book Entry: (select). then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) 6. Configuration for Making Audio/Video Calls from iChat UserB in NAT Mode Policies > (From: Trust. Configuration for Making Audio/Video Calls from iChat UserB in Route Mode Policies > (From: Trust. To: Untrust) New: Enter the following. Configuration for Making Audio/Video Calls from iChat UserA in Route Mode Policies > (From: Trust. iChatServer Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. iChat UserA Destination Address Address Book Entry: (select). then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) 3. To: Untrust) New: Enter the following. then click OK: Source Address Address Book Entry: (select). then click OK: Source Address Address Book Entry: (select). then click OK: Source Address Address Book Entry: (select). then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) 4. then click OK: Source Address Address Book Entry: (select).Chapter 5: Apple iChat Application Layer Gateway > Advanced: Enter the following. iChat UserB Destination Address Address Book Entry: (select). To: Untrust) New: Enter the following.

Configuration for Making Audio/Video Calls from iChat UserA in Route Mode set policy from trust to untrust "ichatUserA" "iChatserver_IP_range" apple-ichat permit 5. Configuration for File Transfer Between UserA and UserB set policy from trust to untrust "ichatUserA" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserA" "iChatServer_IP_range" apple-ichat nat src permit set policy from trust to untrust "ichatUserB" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserB" "iChatServer_IP_range" apple-ichat nat src permit 3. 120 Configuration Examples . Configuration for Making Audio/Video Calls from iChat UserA in NAT Mode set policy from trust to untrust "ichatUserA" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserA" "iChatserver_IP_range" apple-ichat nat src permit 4. There is NAT between private networks and the public network. iChat userA is on a private network and iChat userB and userC are on another private network. The iChat server is on a public network. Configuring iChat UserA to Log Into iChat Server in NAT Mode set policy from trust to untrust "ichatUserA" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserA" "iChatServer_IP_range" apple-ichat nat src permit 2. Configuration for Making Audio/Video Calls from iChat UserB in Route Mode set policy from trust to untrust "ichatUserB" "iChatserver_IP_range" apple-ichat permit Scenario 3: Users Across Different Networks In Figure 33. Configuration for Making Audio/Video Calls from iChat UserB in NAT Mode set policy from trust to untrust "ichatUserB" "iChatserver_IP_range" apple-ichat nat src permit 6.Concepts & Examples ScreenOS Reference Guide Service: (select) AppleiChat Action: Permit CLI 1.

iChat UserA Destination Address Address Book Entry: (select).Chapter 5: Apple iChat Application Layer Gateway Figure 33: AppleiChat Scenario 3—Users Across Different Networks Ethernet NAT iChat User A Trust zones Device A Ethernet Untrust zone Ethernet iChat User B Device B iChat User C NAT iChat Server WebUI 1. Configuration on Firewall 1 for Login from iChat UserA in NAT Mode Policies > (From: Trust. any Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. iChatserver_IP_range Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. then click OK: Source Address Address Book Entry: (select). iChat UserA Destination Address Address Book Entry: (select). then click OK: Source Address Address Book Entry: (select). then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) 2. To: Untrust) New: Enter the following. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) Configuration Examples 121 . To: Untrust) New: Enter the following. Configuration on Firewall 1 for File Transfer from iChat UserA to iChat UserB in NAT Mode Policies > (From: Trust.

iChatserver_IP_range Service:(select) AppleiChat Action: Permit 5. then click OK: Source Address Address Book Entry: (select). iChatserver_IP_range Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. To: Untrust) New: Enter the following. iChat server Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. iChat UserA Destination Address Address Book Entry: (select).Concepts & Examples ScreenOS Reference Guide 3. iChat UserB Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. iChat UserA Destination Address Address Book Entry: (select). Configuration on Firewall 1 for Making Audio/Video Calls from iChat UserA in NAT Mode Policies > (From: Trust. iChat UserA Destination Address Address Book Entry: (select). then click OK: Source Address Address Book Entry: (select). To: Untrust) New: Enter the following. To: Untrust) New: Enter the following. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) Policies > (From: Trust. To: Untrust) New: Enter the following. Configuration on Firewall 1 for Making Audio/Video Calls from iChat UserA in Route Mode Policies > (From: Trust. then click OK: Source Address Address Book Entry: (select). Configuration on Firewall 2 for Making Audio/Video Calls from iChat UserB in NAT Mode Policies > (From: Trust. then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) 4. then click OK: Source Address Address Book Entry: (select). iChat UserB Destination Address Address Book Entry: (select). then click Return to set the advanced options and return to the basic configuration page: 122 Configuration Examples .

To: Untrust) New: Enter the following. then click OK: Source Address Address Book Entry: (select). To: Untrust) New: Enter the following. iChatserver_IP_range Service:(select) AppleiChat Action: Permit CLI 1. iChat UserB Destination Address Address Book Entry: (select). iChat UserB Destination Address Address Book Entry: (select). iChatserver_IP_range Service:(select) AppleiChat Action: Permit Policies > (From: Trust. Configuration on Firewall 1 for File Transfer from iChat UserA to iChat UserB in NAT Mode set policy from trust to untrust "ichatUserA" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserA" "iChatServer_IP_range" apple-ichat nat src permit Configuration Examples 123 . To: Untrust) New: Enter the following. then click OK: Source Address Address Book Entry: (select). Configuration on Firewall 1 for Login from iChat UserA in NAT Mode set policy from trust to untrust "ichatUserA" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserA" "iChatServer_IP_range" apple-ichat nat src permit 2. then click OK: Source Address Address Book Entry: (select). then click Return to set the advanced options and return to the basic configuration page: NAT: Source Translation: (select) (DIP on): (select) 6.Chapter 5: Apple iChat Application Layer Gateway NAT: Source Translation: (select) (DIP on): (select) Policies > (From: Trust. Configuration on Firewall 2 for Making Audio/Video Calls from iChat UserB in Route Mode Policies > (From: Trust. ichatUserA_public Service: (select) AppleiChat Action: Permit > Advanced: Enter the following. iChat UserB Destination Address Address Book Entry: (select).

Configuration on Firewall 2 for Making Audio/Video Calls from iChat UserB in Route Mode set policy from trust to untrust "ichatUserB" "ANY" apple-ichat permit OR set policy from trust to untrust "ichatUserB" "iChatserver_IP_range" apple-ichat permit set policy from trust to untrust ""iChatUserB" ichatUserA_public" apple-ichat permit 124 Configuration Examples . Configuration on Firewall 1 for Making Audio/Video calls from iChat UserA in Route Mode set policy from trust to untrust "ichatUserA" "ANY" apple-ichat permit OR set policy from trust to untrust "ichatUserA" "iChatserver_IP_range" apple-ichat permit set policy from trust to untrust "iChatUserA" "iChatuserB_public" apple-ichat permit 5. Configuration on Firewall 2 for Making Audio/Video Calls from iChat UserB in NAT Mode set policy from trust to untrust "ichatUserB" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserB" "iChatserver_IP_range" apple-ichat nat src permit set policy from trust to untrust "iChatUserB" "ichatUserA_public" apple-ichat nat src permit 6.Concepts & Examples ScreenOS Reference Guide 3. Configuration on Firewall 1 for Making Audio/Video calls from iChat UserA in NAT mode set policy from trust to untrust "ichatUserA" "ANY" apple-ichat nat src permit OR set policy from trust to untrust "ichatUserA" "iChatserver_IP_range" apple-ichat nat src permit set policy from trust to untrust "iChatuserA" "iChatuserB_public" apple-ichat nat src permit 4.

..........111 M messages GCF ..........19 SIP NAT call setup ................................19 to 20 service book.......................................19 request methods ................20 RTP ......... 88 proxy in public zone ..................................................64 P pinholes ..........15 pinholes ............ using incoming .............................................................................................................................................112 G Gatekeeper Confirm (GCF) messages ..........Index A ALGs ............................................34 incoming....16 Index IX-I ............................................................................................................................................................23............................................18 RTCP .........................................................................................................................55..........................................22 media inactivity ..........37.......................................................................................................... using interface ....................15 SIP NAT ...............................2 Apple iChat ALG ..............44 Trust intrazone .... 22 connection information ........................................................................................................................25 alternate gatekeepers .....................................................19.............. service groups (WebUI) ..33 DIP..................................................................................................................................................25 DIP pool.....113 response codes ... using full-mesh .............................................................21 R reassembly.. with MIP ...................... 101 SIP timeouts inactivity ....65 SIP ALG .............111 call-answer-time .........111 SIP ..................37 DIP. Apple iChat ALG ....................................................................................19 to 20 signaling ..........................................................................2 S SDP ........41............................................................................ 24 session inactivity ........112 reassembly ............. using a ............................... 39 proxy in DMZ ...............................................................22 signaling inactivity ...........................20 defined ............................................15 V voice-over IP bandwidth management ..................................................20 SDP ...........................................................2 I iChat ALG ................................................................................. 95 VPN...25.....2 RCF ......................46 proxy in private zone ........................................................................................................... 30 defined ...........................................................................................................16 multimedia sessions ..19 Apple iChat...............................................23......................................................................... Apple iChat ALG ....................................................................................................49..15 media announcements ........................................20 messages ........................................................113 Registration Confirm (RCF) messages ......... SIP ...................................................................53 untrust intrazone .......2 multimedia sessions....................... 24 C call-answer-time.......................................................

Concepts & Examples ScreenOS Reference Guide IX-II Index .

Sign up to vote on this title
UsefulNot useful