Configuration Guide For An Avaya CM-SES With SIP Trunking

1y ago
36 Views
2 Downloads
1.21 MB
32 Pages
Last View : 4d ago
Last Download : 4m ago
Upload by : Vicente Bone
Transcription

Avaya Solution & Interoperability Test LabApplication Notes for Configuring the Ingate SIParator withAvaya SIP Enablement Services and Avaya CommunicationManager to Support SIP Trunking - Issue 1.0AbstractThese Application Notes describe the procedures for configuring the Ingate SIParator withAvaya SIP Enablement Services and Avaya Communication Manager.The Ingate SIParator is a SIP session border controller (SBC) that manages and protects theflow of SIP signaling and related media across an untrusted network. The compliance testingfocused on telephony scenarios between two enterprise sites connected via a SIP trunk acrossan untrusted network.Information in these Application Notes has been obtained through DevConnect compliancetesting and additional technical discussions. Testing was conducted via the DevConnectProgram at the Avaya Solution and Interoperability Test Lab.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.1 of 32Ingate-CM5-Trk

1. IntroductionThese Application Notes describe the procedures for configuring the Ingate SIParator with AvayaSIP Enablement Services (SES) and Avaya Communication Manager.The Ingate SIParator is a SIP session border controller (SBC) that manages and protects the flow ofSIP signaling and related media across an untrusted network. The compliance testing focused ontelephony scenarios between two enterprise sites connected via a SIP trunk across an untrustednetwork.1.1. ConfigurationFigure 1 illustrates the test configuration. The test configuration shows two enterprise sitesconnected via a SIP trunk across an untrusted IP network. Alternatively, the test configuration couldhave shown a SIP service provider connected via a SIP trunk to the main site and the configurationof the main site equipment would have been very similar. The main site has a Juniper NetworksNetscreen-50 firewall at the edge of the network restricting unwanted traffic between the untrustednetwork and the enterprise. Also connected to the edge of the main site is a SIParator SBC. Thepublic side of the SIParator is connected to the untrusted network and the private side is connected tothe trusted corporate LAN. The SIParator could also reside in the demilitarized zone (DMZ) of theenterprise but this configuration was not tested.All SIP traffic between sites flows through the SIParator. In this manner, the SIParator can protectthe main site’s infrastructure from any SIP-based attacks. The voice communication across theuntrusted network uses SIP over UDP and RTP for the media streams. All non-SIP traffic bypassesthe SIParator and flows directly between the untrusted network and the private LAN of theenterprise if permitted by the data firewall.Connected to the corporate LAN at the main site is an Avaya SES and an Avaya S8300 Serverrunning Avaya Communication Manager in an Avaya G700 Media Gateway. Avaya IA 770 IntuityAudix is also running on the Avaya S8300 Server. Endpoints include both SIP and non-SIPendpoints. An ISDN-PRI trunk connects the media gateway to the PSTN.Located at the branch site is an Avaya SES and an Avaya S8300 Server running AvayaCommunication Manager in an Avaya G350 Media Gateway. Avaya IA 770 Intuity Audix is alsorunning on the Avaya S8300 Server. Endpoints include both SIP and non-SIP endpoints. Forsimplicity, there is no network address translation (NAT) being performed at the branch site. All IPaddresses located at the branch are routable across the untrusted network.The SIP endpoints located at both sites are registered to the local Avaya SES. Each site has aseparate SIP domain: business.com for the main site and dev4.com for the branch. SIP and H.323telephones at both sites use the local TFTP server to obtain their configuration files.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.2 of 32Ingate-CM5-Trk

Figure 1: SIParator SIP Trunking Test ConfigurationCTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.3 of 32Ingate-CM5-Trk

2. Equipment and Software ValidatedThe following equipment and software/firmware were used for the sample configuration:EquipmentAvaya S8300B Server with Avaya G700Media Gateway (Main Site)Avaya IA 770 Intuity AudixAvaya S8500B Server (Main Site)Avaya S8300B Server with Avaya G350Media Gateway (Branch Site)Avaya IA 770 Intuity AudixAvaya S8500A Server (Branch Site)Avaya 4621SW IP Telephones (H.323)Avaya 4625SW IP Telephones (H.323)Avaya 4610SW IP Telephone (SIP)Avaya 4620SW IP Telephones (SIP)Avaya 9620 IP Telephones (H.323)Avaya 9620 IP Telephones (SIP)Avaya 9630 IP Telephones (SIP)Avaya one-X Desktop Edition (SIP)Avaya 6408D Digital TelephoneAvaya 6210 Analog TelephoneAnalog TelephoneWindows PCs (TFTP/HTTP Server)Juniper Networks Netscreen-50Ingate SIParatorSIP Trunking ModuleQoS Module (optional)CTM; Reviewed:SPOC 6/18/2008Software/FirmwareAvaya Communication Manager 5.0Service Pack (R015x.00.0.825.4-15175)Avaya SIP Enablement Services 5.0Avaya Communication Manager 4.0.1Service Pack (R014x.00.0.731.2-14300)Avaya SIP Enablement Services 4.0H.323 version 2.8.3SIP version 2.2.2Avaya one-X Deskphone Edition 1.5Avaya one-X Deskphone Edition SIP2.0.32.1 Service Pack 2Windows XP Professional SP 25.4.0r9.04.6.2Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.4 of 32Ingate-CM5-Trk

3. Configure Avaya Communication ManagerThis section describes the Avaya Communication Manager configuration at the main site to supportthe network shown in Figure 1. It assumes the procedures necessary to support SIP andconnectivity to Avaya SES have been performed as described in [3]. It also assumes that an offPBX station (OPS) has been configured on Avaya Communication Manager for each SIP endpoint inthe configuration as described in [3] and [4].This section is divided into two parts. Section 3.1 will summarize the user-defined parameters usedin the installation procedures that are important to understanding the solution as a whole. It will notattempt to show the installation procedures in their entirety. It will also describe any deviations fromthe standard procedures, if any.Section 3.2 will describe procedures beyond the initial SIP installation procedures that are necessaryfor interoperating with the SIParator.The configuration of Avaya Communication Manager was performed using the System AccessTerminal (SAT). After the completion of the configuration, perform a save translation command tomake the changes permanent.This configuration must be repeated for Avaya Communication Manager at the branch using valuesappropriate for the branch from Figure 1. This includes but is not limited to the IP addresses, SIPdomain and user extensions.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.5 of 32Ingate-CM5-Trk

3.1. Summary of Initial SIP InstallationThis section summarizes the applicable user-defined parameters used during the SIP installationprocedures.Step1.DescriptionIP network regionThe Avaya S8300 Server, Avaya SES and IP (H.323/SIP) endpoints were located in asingle IP network region (IP network region 1) using the parameters described below.Use the display ip-network-region command to view these settings. The examplebelow shows the values used for the compliance test. Authoritative Domain: business.com This field was configured to match thedomain name configured on Avaya SES. This name will appear in the “From”header of SIP messages originating from this IP region.Name: Default Any descriptive name may be used.Intra-region IP-IP Direct Audio: yesInter-region IP-IP Direct Audio: yesBy default, IP-IP direct audio (media shuffling) is enabled to allow audio traffic tobe sent directly between IP endpoints without using media resources in the AvayaMedia Gateway. Shuffling can be further restricted at the trunk level on theSignaling Group form.Codec Set: 1 The codec set contains the set of codecs available for calls withinthis IP network region. This includes SIP calls since all necessary components arewithin the same region.display ip-network-region 1Page1 of19IP NETWORK REGIONRegion: 1Location:Authoritative Domain: business.comName: DefaultMEDIA PARAMETERSIntra-region IP-IP Direct Audio: yesCodec Set: 1Inter-region IP-IP Direct Audio: yesUDP Port Min: 2048IP Audio Hairpinning? nUDP Port Max: 3329DIFFSERV/TOS PARAMETERSRTCP Reporting Enabled? yCall Control PHB Value: 46RTCP MONITOR SERVER PARAMETERSAudio PHB Value: 46Use Default Server Parameters? yVideo PHB Value: 26802.1P/Q PARAMETERSCall Control 802.1p Priority: 6Audio 802.1p Priority: 6Video 802.1p Priority: 5AUDIO RESOURCE RESERVATION PARAMETERSH.323 IP ENDPOINTSRSVP Enabled? nH.323 Link Bounce Recovery? yIdle Traffic Interval (sec): 20Keep-Alive Interval (sec): 5Keep-Alive Count: 5CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.6 of 32Ingate-CM5-Trk

Step2.DescriptionCodecsIP codec set 1 was used for the compliance test. Multiple codecs were listed in priorityorder to allow the codec used by a specific call to be negotiated during callestablishment. The list includes the codecs the enterprise wishes to support within thenormal trade-off of bandwidth versus voice quality. The example below shows thevalues used in the compliance test. It should be noted that when testing the use ofG.729AB, G.711MU was removed from the list.display ip-codec-set 1Page1 of2IP Codec SetCodec Set: 1AudioCodec1: G.711MU2: G.729AB3:CTM; Reviewed:SPOC 6/18/2008SilenceSuppressionnnFramesPer Pkt22PacketSize(ms)2020Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.7 of 32Ingate-CM5-Trk

Step3.DescriptionSignaling GroupFor the compliance test, signaling group 1 was used for the signaling group associatedwith the SIP trunk group between Avaya Communication Manager and Avaya SES.Signaling group 1 was configured using the parameters highlighted below. All otherfields were set as described in [3]. Near-end Node Name: procr This node name maps to the IP address of the AvayaS8300 Server. Node names are defined using the change node-names ipcommand. Far-end Node Name: SES This node name maps to the IP address of Avaya SES. Far-end Network Region: 1 This defines the IP network region which containsAvaya SES. Far-end Domain: blank This domain will default to the domain specified in the IPnetwork region form in Step 1. This domain is sent in the “To” header of SIPmessages of calls using this signaling group. Direct IP-IP Audio Connections: y This field must be set to y to enable mediashuffling on the SIP trunk.display signaling-group 1SIGNALING GROUPGroup Number: 1Group Type: sipTransport Method: tlsNear-end Node Name: procrNear-end Listen Port: 5061Far-end Node Name: SESFar-end Listen Port: 5061Far-end Network Region: 1Far-end Domain:Bypass If IP Threshold Exceeded? nDTMF over IP: rtp-payloadDirect IP-IP Audio Connections? yIP Audio Hairpinning? nEnable Layer 3 Test? nSession Establishment Timer(min): 3CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.8 of 32Ingate-CM5-Trk

Step4.DescriptionTrunk GroupFor the compliance test, trunk group 1 was used for the SIP trunk group betweenAvaya Communication Manager and Avaya SES. Trunk group 1 was configured usingthe parameters highlighted below. All other fields were set as described in [3]. Signaling Group: 1 This field is set to the signaling group shown in the previousstep. Number of Members: 10 This field represents the number of trunks in the SIPtrunk group. It determines how many simultaneous SIP calls can be supported bythe configuration. Each SIP call between two SIP endpoints (whether internal orexternal) requires two SIP trunks for the duration of the call. Thus, a call from aSIP telephone to another SIP telephone will use two SIP trunks. A call between anon-SIP telephone and a SIP telephone will only use one trunk.display trunk-group 1Page1 of21TRUNK GROUPGroup Number:Group Name:Direction:Dial Access?Queue Length:Service Type:1SES Trk Grptwo-wayn0tieGroup Type: sipCOR: 1Outgoing Display? nTN: 1CDR Reports: yTAC: 101Night Service:Auth Code? nSignaling Group: 1Number of Members: 105.Trunk Group – continuedOn Page 3: Verify the Numbering Format field is set to public. This field specifies theformat of the calling party number sent to the far-end. The default values may be retained for the other fields.display trunk-group 1TRUNK FEATURESACA Assignment? nPage3 of21Measured: noneMaintenance Tests? yNumbering Format: publicUUI Treatment: service-providerReplace Unavailable Numbers? nShow ANSWERED BY on Display? yCTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.9 of 32Ingate-CM5-Trk

Step6.DescriptionPublic Unknown NumberingPublic unknown numbering defines the calling party number to be sent to the far-end.An entry was created for the trunk group defined in Step 4. In the example shownbelow, all calls originating from a 5-digit extension beginning with 3 and routed acrosstrunk group 1 will be sent as a 5 digit calling number. This calling party number is sentto the far-end in the SIP “From” header.change public-unknown-numbering 0Page1 ofNUMBERING - PUBLIC/UNKNOWN FORMATTotalExt ExtTrkCPNCPNLen CodeGrp(s)PrefixLenTotal Administered: 25 315Maximum Entries: 24023.2. Configure SIP Trunk and Routing to the Branch SiteTo communicate to the branch site, a second SIP trunk with the appropriate call routing must beconfigured on Avaya Communication Manager. This SIP trunk will be used to route SIP calls toAvaya SES that are destined to the branch site SIP domain.Step1.DescriptionSignaling GroupFor the compliance test, signaling group 6 was used for the signaling group associatedwith the SIP trunk group defined for branch site calls (see Step 2). Signaling group 6was configured using the same parameters as signaling group 1 in Section 3.1 with theexception of the far-end domain. The Far-end Domain field is set to the SIParatorprivate side IP address. In the case of the branch site, the Far-end Domain fieldwould be set to the SIParator public IP address at the main site.display signaling-group 6SIGNALING GROUPGroup Number: 6Group Type: sipTransport Method: tlsNear-end Node Name: procrNear-end Listen Port: 5061Far-end Node Name: SESFar-end Listen Port: 5061Far-end Network Region: 1Far-end Domain: 10.75.5.63Bypass If IP Threshold Exceeded? nDTMF over IP: rtp-payloadDirect IP-IP Audio Connections? yIP Audio Hairpinning? nEnable Layer 3 Test? nSession Establishment Timer(min): 3CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.10 of 32Ingate-CM5-Trk

Step2.DescriptionTrunk GroupFor the compliance test, trunk group 6 was used for the SIP trunk group defined forbranch site calls. Trunk group 6 was configured using the same parameters as trunkgroup 1 in Section 3.1, Step 4 except the Signaling Group field is set to 6. Thisincludes the settings on Page 3 of the trunk group form (not shown).display trunk-group 6Page1 of21TRUNK GROUPGroup Number:Group Name:Direction:Dial Access?Queue Length:Service Type:6Site2SEStwo-wayn0tieGroup Type: sipCOR: 1Outgoing Display? nTN: 1CDR Reports: yTAC: 106Night Service:Auth Code? nSignaling Group: 6Number of Members: 103.Public Unknown NumberingA new entry was created for the trunk group defined in Step 2. In the example shownbelow, all calls originating from a 5-digit extension beginning with 3 and routed acrosstrunk group 6 will be sent as a 5-digit calling number. This calling party number issent to the far-end in the SIP “From” header.change public-unknown-numbering 0Page1 ofNUMBERING - PUBLIC/UNKNOWN FORMATTotalExt ExtTrkCPNCPNLen CodeGrp(s)PrefixLenTotal Administered: 35 315Maximum Entries: 2405 3654.2Automatic Alternate RoutingAutomatic Alternate Routing (AAR) was used to route calls to the branch site. In theexample shown, numbers that begin with 4 and are 5 digits long use route pattern 6.Route pattern 6 routes calls to the SIP trunk defined for branch site calls.display aar analysis 4Page1 of2AAR DIGIT ANALYSIS TABLEPercent Full:DialedString4CTM; Reviewed:SPOC 6/18/2008TotalMin ion & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.11 of 32Ingate-CM5-Trk

Step5.DescriptionRoute PatternFor the compliance test, route pattern 6 was used for calls destined for the branch site.Route pattern 6 was configured using the parameters highlighted below. Pattern Name: Any descriptive name. Grp No: 6 This field is set to the trunk group number defined in Step 2. FRL: 0 This field is the Facility Restriction Level of the trunk. It must be set to anappropriate level to allow authorized users to access the trunk. The level of 0 is theleast restrictive.change route-pattern 6Pattern Number: 6Pattern Name: Site2SESSCCAN? nSecure SIP? nGrp FRL NPA Pfx Hop Toll No. InsertedNoMrk Lmt List Del DigitsDgts1: 602:3:4:5:6:1:2:3:4:5:6:BCC VALUE TSC CA-TSC0 1 2 M 4 WRequestITC BCIE Service/Feature PARMyyyyyyrestrestrestrestrestrestCTM; Reviewed:SPOC 6/18/2008yyyyyyyyyyyyyyyyyyyyyyyynnnnnnnnnnnnPage1 . Numbering LARDgts FormatSubaddressnonenonenonenonenonenoneSolution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.12 of 32Ingate-CM5-Trk

4. Configure Avaya SIP Enablement ServicesThis section covers the configuration of Avaya SES at the main site. Avaya SES is configured viaan Internet browser using the administration web interface. It is assumed that the Avaya SESsoftware and the license file have already been installed on the server. During the softwareinstallation, an installation script is run from the Linux shell of the server to specify the IP networkproperties of the server along with other parameters. In addition, it is assumed that the setup screensof the administration web interface have been used to initially configure Avaya SES. For additionalinformation on these installation tasks, refer to [5].Each SIP endpoint used in the compliance test that registers with Avaya SES requires that a user andmedia server extension be created on Avaya SES. This configuration is not directly related to theinteroperability of the SIParator so it is not included here. These procedures are covered in [5].This section is divided into two parts. Section 4.1 will summarize the user-defined parameters usedin the installation procedures that are important to understanding the solution as a whole. It will notattempt to show the installation procedures in their entirety. It will also describe any deviations fromthe standard procedures, if any.Section 4.2 will describe procedures beyond the initial SIP installation procedures that are necessaryfor interoperating with the SIParator.This configuration must be repeated for Avaya SES at the branch using values appropriate for thebranch from Figure 1. This includes but is not limited to the IP addresses, SIP domain and userextensions.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.13 of 32Ingate-CM5-Trk

4.1. Summarize Initial Configuration ParametersThis section summarizes the applicable user-defined parameters used during the SIP s the Avaya SES administration web interface by enteringhttp:// ip-addr /admin as the URL in an Internet browser, where ip-addr is the IPaddress of the Avaya SES server.Log in with the appropriate credentials and then select the Launch AdministrationWeb Interface link from the main page as shown below.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.14 of 32Ingate-CM5-Trk

Step2.3.DescriptionTop PageThe Avaya SES Top page will be displayed as shown below.Initial Configuration ParametersAs part of the Avaya SES installation and initial configuration procedures, thefollowing parameters were defined. Although these procedures are out of the scope ofthese Application Notes, the values used in the compliance test are shown below forreference. After each group of parameters is a brief description of how to view thevalues for that group from the Avaya SES administration home page shown in theprevious step. SIP Domain: business.com(To view, navigate to Server ConfigurationÆSystem Parameters) Host IP Address (SES IP address): 10.75.5.6Host Type: SES combined home-edge(To view, navigate to HostÆList; click Edit) Media Server (Avaya Communication Manager) Interface Name: CMeastSIP Trunk Link Type: TLSSIP Trunk IP Address (Avaya S8300 Server IP address): 10.75.5.2(To view, navigate to Media ServerÆList; click Edit)CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.15 of 32Ingate-CM5-Trk

4.2. SIParator Specific ConfigurationThis section describes additional Avaya SES configuration necessary for interoperating with theSIParator.Step1.DescriptionTrusted HostThe IP address of the SIParator must be configured as a trusted host in Avaya SES sothat SIP messages from the SIParator are not challenged by Avaya SES. To view thetrusted host settings, navigate to Trusted HostsÆList from the left pane of the AvayaSES window. Click Edit next to the trusted host entry associated with the SIParator(not shown). The Edit Trusted Host screen will appear. The parameters are describedbelow: IP Address: The private side IP address of the SIParator. Comment: Any descriptive comment.In the case of the branch site, the public IP address of the SIParator will be set up as atrusted host on the branch site Avaya SES.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.16 of 32Ingate-CM5-Trk

Step2.DescriptionMedia Server Address MapA media server address map is needed to route calls from the remote site to a non-SIPphone at the local site. This is because neither the caller nor the called party is aregistered user on Avaya SES with a media server extension assigned to it. Thus,Avaya SES does not know to route this call to Avaya Communication Manager.Thus to accomplish this task, a media server address map is needed.To view the configured media server address maps, navigate to Media ServerÆList inthe left pane. Click the Map link next to the Avaya S8300 Server name (not shown).The list of media server address maps will appear. Each map defines criteria formatching calls to Avaya SES based on the contents of the SIP Request-URI of the call.If a call matches the map, then the call is directed to the Contact.In the example below, three maps are shown. Only the maps named ToMainCM andToPSTN were used for the compliance test. Both of these maps were associated to aContact that directs the calls to the IP address of the Avaya S8300 Server (10.75.5.2)using port 5061 and TLS as the transport protocol. The user portion in the originalrequest URI is substituted for (user) in the Contact expression shown below.sip: (user)@10.75.5.2:5061;transport tlsTo view or edit the call matching criteria of the map, click the Edit link next to themap name.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.17 of 32Ingate-CM5-Trk

Step3.DescriptionMedia Server Address Map – continuedThe content of the media server address map is described below. Name: Contains any descriptive name Pattern: Contains an expression to define the matching criteria for calls to berouted from the remote site to the local Avaya Communication Manager. Forthe address map named ToMainCM, the expression will match any URI thatbegins with sip:3 followed by any digit between 0-9 for the next 4 digits.Additional information on the syntax used for address map patterns can befound in [5]. Replace URI: Check the box.If any changes are made, click Update.For the address map named ToMainCM:For the address map named ToPSTN:CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.18 of 32Ingate-CM5-Trk

5. Configure the Avaya SIP TelephonesThe SIP telephones at each site will use the local Avaya SES as the call server. The table belowshows an example of the SIP telephone network settings for each site.ExtensionIP AddressSubnet MaskRouterFile ServerDNS ServerSIP DomainCall Server or SIPProxy ServerMain 50.1.1.506. Configure the Ingate SIParatorThis section describes the configuration of the Ingate SIParator. It assumes the SIP Trunkingmodule has been installed. In addition, to support the setting of the Differentiated Services CodePoint (DSCP) bits for quality of service, the QoS module must be installed and requires additionallicensing.The SIParator is configured initially with the Ingate Startup Tool. Based on the provided input, theStartup Tool will create an initial configuration that can be uploaded to the SIParator. The results ofthis configuration can then be viewed or expanded using the SIParator web interface. To access theweb interface, enter the IP address of the SIParator as the destination address in a web browser.When prompted for login credentials, enter an appropriate user name and password.Much of the detailed SIP configuration is not visible from the Startup Tool but is driven by the typeof IP-PBX and Service Provider chosen in the Startup Tool. The detailed SIP configuration resultingfrom the following procedure is captured in Appendix A for reference.Step1.DescriptionLaunch Startup ToolThe Ingate Startup Tool is a windows application which is launched from the WindowsStart Menu by navigating to StartÆAll ProgramsÆShortcut to StartupTool.exe.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.19 of 32Ingate-CM5-Trk

Step2.DescriptionSelect Product TypeThe initial Ingate Startup Tool screen is shown below. Verify the PC is running on thesame LAN subnet as the SIParator as shown in the diagram. This is necessary in orderto assign the initial IP address to the SIParator from the Startup Tool. Select theSIParator model from the Ingate model drop-down menu. Click the Next button.3.Select Configuration Options and Assign Private IPSelect options for Configure the unit for the first time and Configure SIP trunking.Enter the inside IP address and a password. Click the Contact button to establish aconnection to the SIParator.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.20 of 32Ingate-CM5-Trk

Step4.DescriptionNetwork TopologyOn the next page, select the Network Topology tab. Select Standalone SIParatorfrom the Product Type drop-down menu. Enter an IP address and subnet mask forboth the inside and outside interfaces as shown in Figure 1. The Gateway field is setto the IP address of the default gateway on the public side of the SIParator. A DNSserver was not used for the compliance test so the DNS server values were left blank.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.21 of 32Ingate-CM5-Trk

Step5.DescriptionIP-PBX SettingsSelect the IP-PBX tab. Select Avaya from the Type drop-down menu. This willinstruct the Startup Tool to configure the SIP parameters on the internal interface to becompatible with the Avaya SES. Enter the Avaya SES IP address in the IP Addressfield.6.Service Provider SettingsSelect the ITSP 1 tab. Select Generic ITSP from the Name drop-down menu. Thiswill instruct the Startup Tool to configure the SIP parameters on the external interfaceto be compatible with a generic SIP service provider. In the IP Address field, enterthe remote Avaya SES IP address on the untrusted side of the SIParator.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.22 of 32Ingate-CM5-Trk

Step7.8.DescriptionUpload ConfigurationSelect the Upload Configuration tab to upload the configuration to the SIParator.Click the Upload button to begin the upload.Apply ConfigurationAfter uploading the configuration, the Startup Tool opens a web browser to theAdministrationÆSave/Load Configuration page of the SIParator. Click the Applyconfiguration button to apply the configuration. The Startup Tool configuration iscomplete at this point. However, additional configuration was required to support allthe test cases in the compliance test. This configuration is performed using theSIParator web interface and is covered in the remaining steps.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Test Lab Application Notes 2008 Avaya Inc. All Rights Reserved.23 of 32Ingate-CM5-Trk

Step9.DescriptionConfigure Static RoutesIn order to support endpoints on other networks within the enterprise other than thesubnet to which the SIParator is directly connected, then a static route must beconfigured on the internal interface. In the case of the compliance test, one endpointwas located on the 10.75.10.0/24 network. Thus, to view the static route configured forthis network, navigate to NetworkÆEth0. Scroll down to the Static Routing section.In this case, the routed network with Network Address 10.75.10.0 and Netmask of255.255.255.0 is reached using Router IP address 10.75.5.1.CTM; Reviewed:SPOC 6/18/2008Solution & Interoperability Tes

Avaya 4610SW IP Telephone (SIP) Avaya 4620SW IP Telephones (SIP) SIP version 2.2.2 Avaya 9620 IP Telephones (H.323) Avaya one-X Deskphone Edition 1.5 Avaya 9620 IP Telephones (SIP) Avaya 9630 IP Telephones (SIP) Avaya one-X Deskphone Edition SIP 2.0.3 Avaya one-X Desktop Edition (SIP) 2.1 Service Pack 2 Avaya 6408D Digital Telephone - Avaya .

Related Documents:

Avaya Avaya Aura Session Manager 7.0.0.0.700007 Avaya Aura System Manager 7.0.0.0.16266 Avaya Aura Communication Manager 7.0-441 Build 0.22477 Avaya Session Border Controller for Enterprise 7.-21-6602 Avaya G430 Media Gateway 37.19. Avaya 96x0 Phone (SIP) 2_6_14_5 Avaya 9608 Phone (SIP) 7.0.0 R39 Avaya 96x0 Phone (H.323) 3.230A

avaya ip office Video Softphone aCm ip Softphone avaya ip agent avaya one-x Communicator avaya Communicator 2.1 avaya Communicator for microsoft lync 6.4.0.2 avaya one-x agent avaya aura agent desktop e169 media Station i2050 softphone Flare experience H175 Video phone 2 linK o

Avaya PARTNER Advanced Communications System Avaya MERLIN MAGIX Avaya IP Office Avaya S8100 Media Server on Avaya G600 Media Gateway or CMC1 Gateway Avaya S8300 Media Server and an Avaya G700 Media Gateway Market Segment Small to Mid Stand Alone or Small of Large 2-48 stations Small/mid standalone Target 20-80 station size

Avaya S8300 Server with Avaya G700 Media Gateway Avaya Communication Manger 4.0 (R014x.00.0.730.5) Avaya 9650 IP Telephone Avaya one-X Deskphone Edition 1.5 (H.323) Avaya 9640G IP Telephone Avaya one-X Deskphone Edition 1.5 (H.323) Avaya 9640 IP Telephone

Avaya IP Office solution A vaya IP Office 500 V2 Embedded Voicemail Avaya Web RTC Gateway Avaya one -X Portal Avaya IP Office Manager Avaya IP Office Analogue PHONE 8 Avaya IP Office VCM64/PRID U Avaya IP Office DIG DCPx16 V2 10.0.0.1.0 build 53 10.0.0.1.0 build 53 10.0.0.1.0 bui ld 3

The following Avaya PDS documents may also be helpful: Avaya Predictive Dialing System User's Guide Volume 1 Avaya Predictive Dialing System User's Guide Volume 2 Avaya Predictive Dialing System Safety and Regulatory Information Avaya PG230 Proactive Contact Gateway Safety and Regulatory Information

from Avaya to install and configure Avaya components. Configure the CTI Link on the Avaya CM A CTI Link (also known as a T-Link) between the Avaya Communication Manager and AES is required for communication of events via TSAPI. The Avaya CM can be configured via the Avaya Site Administration tool (GEDI) or through a telnet session.

The American Revolution DID inspire other revolutions to follow. French Revolution (1789-1799) –partly because France was broke after helping us (and we broke our alliance partly thanks to George Washington’s advice against “entangling alliances”) Haitian Revolution (1791-1804) Mexican War of Independence (1810-1821)