Home

Avaya Aura - Config Guide

1. Name IP Address Type Adaptation Location Port Protocol Default Domain S8300_G450_AE 10 64 21 41 CM 10 64 20 21 0 CM8800_G430_FS 10 64 20 25 CM 10 64 20 21 0 Acme Packet 10 64 20 106 Other Metaswitch 10 64 20 21 0 SM 01 10 64 20 31 SM 10 64 20 21 0 5060 TCP avaya com 5060 UDP 5061 TLS Table 2 SIP Entities Provisioning MJH Reviewed Solution amp Interoperability Test Lab Application Notes 50 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 6 3 5 Entity Links Entity Links defined the connections between the SIP Entities and Avaya Aura Session Manager In the reference configuration Entity Links are defined between Avaya Aura Session Manager and e The Avaya Aura Communication Manager e The Avaya Aura Communication Manager Feature Server e Acme Packet To add an Entity Link select Entity Links on the left Network Routing Policy menu and click on the New button on the right The screen shown below is displayed 1 Enter a descriptive name in the Name field 2 Inthe SIP Entity 1 drop down menu select the Avaya Aura Session Manager SIP Entity created in Section 6 3 4 e g SM 01 In the Port field enter the port to be used e g 5060 or 5061 In the SIP Entity 2 drop down menu select the one of the three entities in the bullet list above which were created in Section 6 3 4 In the Port field enter the por
2. The IP Codec Set form is modified with the change ip codec set x command where x is the codec set number 1 On Page 1 of the form e Configure the Audio Codec field 1 to G 711MU During compliance testing G 729B and G 729AB were also tested change ip codec set 1 Page al Qi 2 WP Coclee Seu Codec Set 1 Audio Silence Frames Packet Codec Suppression Per Pkt Size ms 1 G 711MU n 2 20 De Figure 11 IP Codec Set 1 2 On Page 2 of the form e Configure the Fax field to t 38 standard e Configure the Fax Redundancy field to 0 e Use the default settings for all other fields change ip codec set 1 Page 2 of 2 1 Codes Ser Allow Direct IP Multimedia n Mode Redundancy FAX t 38 standard 0 Modem off 0 TDD TTY US 3 Clear channel n 0 Figure 12 IP Codec Set 1 Page 2 4 1 6 SIP Trunk Groups SIP trunks are defined for internal calls as well as off network calls to and from the PSTN via Metaswitch A SIP trunk is created in Avaya Aura Communication Manager by provisioning a SIP Trunk Group as well as a SIP Signaling Group Note In the SIP trunk configurations below and in the corresponding Avaya Aura Session Manager configuration TLS was selected as the transport protocol in the reference configuration The TCP protocol could have been used instead MJH Reviewed Solution amp Interoperability Test Lab Application Notes 16 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights
3. MJH Reviewed Solution amp Interoperability Test Lab Application Notes 44 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM AVAYA Avaya Aura System Manager 5 2 Welcome admin Last Logged on at Apr 28 2010 2 43 PM Help Log off Home Network Routing Policy SIP Domains Asset Management Domain Management gt Communication System Manane gt User Management gt Monitoring 1 Item Refresh Filter Enable Y Network Routing Policy O Name Type Default Notes Adaptations avaya com sip o Dial Patterns Select All None 0 of 1 Selected Entity Links Locations Regular Expressions Routing Policies SIP Domains SIP Entities Time Ranges Personal Settings gt Security Applications gt Settings Session Manager Shortcuts Change Password Help for NRP SIP Domains Help for SIP Domains fields Help for New SIP Domains Help for Delete Confirmation fields Help for Creating NRP SIP domains Help for Modifying NRP SIP Figure 50 SIP Domain Menu 6 3 2 Adaptations Avaya Aura Session Manager provides for specialized code modules to process specific call processing requirements of various vendors and or services These modules are called adaptations 6 3 2 1 DigitConversionAdapter This adaptation allows Avaya Aura Session Manager to convert inbound and or outbound digits in SIP Request URI History Info header P Asserted Identity header and
4. 7 3 8 1 Metaswitch Session group 1 Configure session router gt session group to create a session group for the Metaswitch network with the following settings groupname gt SERV_PROVIDER state gt enabled app protocol gt SIP strategy gt Hunt dest gt 208 xxx xxx 135 eno Tp 7 3 8 2 Avaya CPE Session group 1 Configure session router gt session group to create a session group for the Avaya CPE network with the following settings groupname gt ENTERPRISE state gt enabled app protocol gt SIP strategy gt Hunt dest gt 10 64 20 31 Pao op 7 3 9 SIP Configuration This command sets the values for the Acme Packet SIP operating parameters The home realm defines the SIP daemon location and the egress realm is the realm that will be used to send a request if a realm is not specified elsewhere 1 Configure session router gt sip config with the following settings a state gt enabled b operation mode gt dialog c home realm id gt INSIDE d egress realm id gt OUTSIDE MJH Reviewed Solution amp Interoperability Test Lab Application Notes 75 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 7 3 10 SIP Interfaces The SIP interface defines the signaling interface IP address and port to which the Acme Packet sends and receives SIP messages 7 3 10 1 l 7 3 10 2 Outside SIP interface Configure session router gt sip interface to create a sip interface
5. Maximum Connection per PPM client 3 PPM Connection Timeout mins 5 PPM Packet Rate Limiting Y PPM Packet Rate Limiting Threshold 50 Event Server Clear Subscription on Notification Failure No v Required Figure 58 Completed Session Manager Form MJH Reviewed Solution amp Interoperability Test Lab Application Notes 59 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 6 5 Feature Server In order for Communication Manager to provide configuration and Feature Server support to the Avaya 9600 Series SIP Telephones when they register to Session Manager Communication Manager must be added as an application for Session Manager 1 Select Applications gt Entities on the left Click on New not shown Select CM Type and in the displayed page enter the following fields Use defaults for the remaining fields a Enter a descriptive name in the Name field b Select CM for Type c Inthe Node field Select IP address for Communication Manager SAT access Under the Attributes section enter the following fields and use defaults for the remaining fields d Enter the login used for SAT access in the Login field e Enter the password used for SAT access in the Password field f Enter the password used for SAT access in the Confirm Password field 2 Click the Commit button MJH Reviewed Solution amp Interoperability Test Lab Application Notes 60 of 91
6. Messaging Profile Roles Override Permissions Group Membership Figure 65 New User Profile Form cont d 4 Click on Session Manager in the above screen to expand that section Select the appropriate Session Manager server for Session Manager Instance For Origination Application Sequence and Termination Application Sequence select the Application Sequence configured in Section 6 5 5 Click on Station Profile in the above screen to expand that section Enter the following fields and use defaults for the remaining fields a System Select the Communication Manager entity b Use Existing Stations Check this box c Extension Enter the extension d Template Select an appropriate template matching the telephone type e Port Click on the Search icon to pick a port in this case IP 6 Click on Commit not shown MJH Reviewed Solution amp Interoperability Test Lab Application Notes 67 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM Y Session Manager Session Manager Instance sm 01 9 Origination Application Sequence cm_eeoo Termination Application Sequence cm_8800 x Station Profile Yi System CM8800_G430_FS Use Existing Stations Extension Q 53102 Template Select Reset 57 962051P Set Type Security Code eee Port Q soo008 Delete Station on Unassign of Station from User
7. Messaging Profile Roles Override Permissions Group Membership Attribute Sets Figure 66 New User Profile Form cont d 7 Repeat the above procedures to add each SIP user MJH Reviewed Solution amp Interoperability Test Lab Application Notes 68 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 7 Acme Packet 3800 Net Net Session Director In the reference configuration an Acme Packet Session Border Controller SBC was used to provide access to the Metaswitch network 7 1 Acme Packet Service States Acme Packet requests and provides service states by sending out and responding to SIP OPTIONS messages Acme Packet sends the OPTIONS message with the hop count SIP Max Forwards set to zero e Acme Packet Avaya Aura Session Manager o Acme Packet sends OPTIONS gt Avaya Aura Session Manager responds with 200 OK o Avaya Aura Session Manager sends OPTIONS gt Acme Packet responds with 200 OK e Acme Packet Metaswitch o Acme Packet sends OPTIONS gt Metaswitch responds with 200 OK o Metaswitch sends OPTIONS gt Acme Packet responds with 200 OK 7 2 Acme Packet Network Interfaces The physical and network interface provisioning for the OUTSIDE to Metaswitch and INSIDE to Avaya CPE interfaces is described in Sections 7 3 3 and 7 3 4 7 3 Acme Packet Provisioning Note Only the Acme Packet provisioning required for the reference config
8. 2010 Avaya Inc All Rights Reserved Metaswitch_SM source address gt 208 xxx xxx 135 5060 application protocol gt SIP transport protocol gt UDP access gt permit 2053 7 3 12 2 Media Manager Verify that the media manager process is enabled 1 Navigate to media manager gt media manager Enter select gt show gt Verify that the media manager state is enabled If not configure the following settings a state gt enabled 7 3 12 3 System config In the system config specify a hostname and the default gateway of the management interface 1 Configure system gt system config with the following settings a hostname gt acmesbe b default gateway gt 10 64 20 1 8 Metaswitch Configuration During the test effort the Metaswitch network was protected by a pair of Acme Packet Net Net SD 3820 session border controllers The session border controllers are not required as part of the solution For brevity only the configuration of the MetaSphere CFS is discussed below If a session border controller is used between the MetaSphere CFS solution and the Avaya solution contact a Metaswitch Networks support representative for additional configuration details 8 1 Media Gateway Model A truncated text dump of the Remote Media Gateway Model used for the testing is shown below For an importable version contact a Metaswitch customer service representative begin MediaGatewayModel MediaGatewayModel 176 Remote Media Ga
9. Language Preference Time Zone Address Choose New Shared Address D Items Name Address Type Street No Records found Communication Profile Roles Override Permissions Group Membership 53102 avaya com Basic coccccccccccocccees Edit al 53102 LD 53102 ED English Select the appropriate language preference Select the appropriate time zone Locality Name Postal Code Province Figure 64 New User Profile Form cont d Country 3 Click on Communication Profile to expand that section in the above screen Then click on Communication Address to expand that section Enter the following fields and use defaults for the remaining fields a Type Select sip b SubType c Fully Qualified Address Select username Enter the extension and select the domain as specified in Section 6 3 1 d Click on Add to add the record with the above information MJH Reviewed RRR xx xx xxxx Solution amp Interoperability Test Lab Application Notes 2010 Avaya Inc All Rights Reserved 66 of 91 Metaswitch_SM Communication Profile l New Done cancel Name Primary Select None Name Primary o Default M Communication Address New Type SubType Handle Domain sip username 53102 avaya com Select All None 0 of 1 Selected Y Session Manager Y Station Profile
10. Maximum call appearances 1 2147483647 Override 20 Line usage Yoice and fax PBX plays ringback True 8 3 3 DID objects Two DID ranges were configured during compliance testing due to the setup in Metaswitch s test lab Two DID ranges are not required Name Yalue Type DID range Description normal Range size 1 1000000000 a First Directory number 6046982011 Last Directory number 6046982019 First code 6046982011 Last code 6046982019 Type DID range Description PSTN Range size 1 1000000000 1 First Directory number 5102174567 Last Directory number 5102174567 First code 5102174567 Last code 5102174567 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 83 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 9 General Test Approach and Test Results This section describes the interoperability compliance testing used to verify SIP trunking interoperability between Metaswitch and the Avaya CPE This section covers the general test approach and the test results The Avaya CPE was connected using SIP trunking to the Metaswitch network The general test approach included the following e Inbound Calls Verify that calls placed from a PSTN telephone to a DID number are properly routed via the SIP trunk to the expected extension on Communication Manager Verify the talk path exists in both directions that calls remain stable for several minutes and disconnect properly e O
11. RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM Welcome admin Last Logged on at Apr 30 2010 3 20 PM Help Log off Asset Management Communication System Management User Management Monitoring Network Routing Policy Security Y Applications Other Applications Session Manager 5 2 SMGR SIP AS 8 0 Entities gt Settings Session Manager Shortcuts Change Password Application Instance Fields MJH Reviewed RRR xx xx xxxx Edit CM CM8800_G430_FS Application Port Access Point Attributes Expand All Collapse All Application Name Type Description Node Port Access Point Attributes Login Password Confirm Password Is SSH Connection Port Alternate IP Address RSA SSH Fingerprint Primary IP RSA SSH Fingerprint Alternate IP Is ASG Enabled ASG Key Confirm ASG Key E Location Required Figure 59 Application Entities Form Solution amp Interoperability Test Lab Application Notes 2010 Avaya Inc All Rights Reserved CM8800_G430_FS 10 64 20 25 init lecccee 5022 61 of 91 Metaswitch_SM 3 Select Session Manager gt Application Configuration gt Applications on the left Click on New not shown Enter the following fields and use defaults for the remaining fields a Enter a descriptive name in the Name f
12. 2 Acme Packet Network Ti 69 7 3 Acme Packet PLOMO A R E esi 69 7 3 1 Acme Packet Mata Serie at rririk A 70 1 3 2 Local POS ishte aoan a a depend aude iw a A R E N ai 71 7 3 3 Network MACS a a ee ae as 71 7 3 4 Physical MICU O E ayaa eas casas 12 7 3 5 Realms a a E E ES 13 7 3 6 RCSLT PO Sad sh seh ea css ge de eigen E A aly ead eased EE Bice aI me wae eda ASES 73 1 3 7 Session A ia 74 7 3 8 ESOO acia 75 7 3 9 A onei era oases ap e vga a eaa E REE a aai 75 TNO SIP MICE ACE O aaa 76 LIL SIP MA UN Sa 76 7 3 12 Other Acme Packet PEONES ia 78 8 Metaswitch Configuration AA ca eRe Aut es alata dg ELIE Suede eee ce 79 8 1 Media Gateway NIG lease iinan n iana io 79 8 2 Configured SIP Bindit Sni SN ENS 81 8 3 dl CCl COMMON A A A Edasine 82 8 3 1 PROD srta o a le a ota llo SUD 82 8 3 2 IN A vce eae nek eee gine ta ea gee c aaa eaaa a aCei 83 8 3 3 1B WB 0 5 sc keeper tree an eens ahaa Pr PO a RAN A TS 83 9 General Test Approach and Test Result Ri 84 10 Verification e a daa ati Goat 84 10 1 Verify Avaya Aura Communication Manager 5 2 00 cece eeseceeeesseeeseeeeeenaeeens 85 10 2 Verify Avaya Aura Session Manager ai A Rind amen a 87 10 2 1 Vertify SIP Entity Tank Stauis a ie 87 2 2 ES o Mal dae dedo 88 10 3 Verification Call STE O Ed 89 10 4 SONIC HIST OR dl ccd Sane Coton 90 11 PROPEL CIN O A A Ca ddaseen st Swudetees oatgenecaae 90 11 1 Ava yaeua pene hatte eM sia Does oat I a Nee sere a etal hah ia can 90
13. 2 Inside Realm l Configure media manager gt realm config to create a realm for the inside network with the following settings Sra ete ho ao oS identifier gt INSIDE addr prefix gt 0 0 0 0 network interfaces gt Private 0 out manipulationid gt NAT_IP mm in realm gt enabled mm in network gt enabled mm same ip gt enabled mm in system gt enabled access control trust level gt high invalid signal threshold gt 0 maximum signal threshold gt 0 untrusted signal threshold gt 0 7 3 6 Steering Pools Steering pools define sets of ports that are used for steering media flows thru the Acme MJH Reviewed Solution amp Interoperability Test Lab Application Notes 73 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 7 3 6 1 Outside Steering Pool 1 Configure media manager gt steering pool to create a steering pool for the outside network with the following settings a ip address gt 205 xxx xxx 106 b start port gt 49152 c end port gt 65535 d realm id gt OUTSIDE 7 3 6 2 Inside Steering Pool 1 Configure media manager gt steering pool to create a steering pool for the inside network with the following settings a ip address gt 10 64 20 106 b start port gt 49152 c end port gt 65535 d realm id gt INSIDE 7 3 7 Session Agents A session agent defines an internal next hop signaling entity for the SIP traffic A realm is associated with a session agent to i
14. 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM e ECS500 Features e Calls using Avaya one X Communicator softphone 1 2 Support For technical support for Metaswitch contact your Metaswitch Networks support representative 2 Reference Configuration Figure 1 illustrates the reference configuration used for the DevConnect compliance testing The reference configuration is comprised of Avaya Customer Premises Equipment CPE located in the Solution Interoperability Test Lab in Westminster Colorado The Avaya CPE location simulates an enterprise customer site and uses private IP addressing At the edge of the Avaya CPE location an Acme Packet Session Border Controller SBC provides Network Address Translation NAT functionality that converts the private IP addressing to public addressing that is passed to Metaswitch The inside interface of the Acme Packet SBC is connected to a private subnet The outside interface of the Acme Packet SBC is connected to a Juniper edge router providing access to the Metaswitch Test Lab network via the public network Metaswitch provided a Direct Inward Dial DID 10 digit number for use during the testing The DID was mapped by Avaya Aura Session Manager to an associated Avaya Aura Communication Manager extension Metaswitch used the domain 208 xxx xxx 135 The Avaya CPE environment was assigned the domain avaya com See Section 2 1 for more details regarding the d
15. DID e g 51021 Set the Total CPN Len field to 10 This is the total number of digits in the DID With this configuration Avaya Aura Communication Manager will insert 51021 for calls from a 5 digit extension starting with digit 7 going over trunk 9 This allows the station with the extension that matches the last 5 digits of the Metaswitch DID to place calls to the PSTN For internal calls Set the Ext Len field to 5 Set the Ext Code field to 7 Set the Trk Grp s field to 8 Set the Total CPN Len field to 5 This is the total number of digits in the extension All provisioned public unknown numbering entries can be displayed by entering the command display public unknown numbering 0 as show below display public unknown numbering 0 Page il OF A NUMBERING PUBLIC UNKNOWN FORMAT Motani Ext Ext Trk CPN CPN Len Code Grp s Prefix Len Total Administered 4 ES 5 Maximum Entries 240 By ud 8 5 577 9 51021 10 Figure 19 Public unknown numbering Form Basic Configuration MJH Reviewed Solution amp Interoperability Test Lab Application Notes 21 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 4 1 8 Call Routing 4 1 8 1 Outbound Calls The following sections describe the Avaya Aura Communication Manager provisioning required for outbound dialing Although Avaya Aura Session Manager routes all inbound and outbound SIP trunk calls Avaya Aura Communication M
16. Echo Cancellation Maximum TN2501 VAL Boards Maximum Media Gateway VAL Sources Maximum TN2602 Boards with 80 VoIP Channels Maximum TN2602 Boards with 320 VoIP Channels Maximum Number of Expanded Meet me Conference Ports w o Se Sree oS SOM oS 1 ul o PS Gre S Cre SV Crore Gaye N o NOTE You must logoff login to effect the permission changes Figure 2 System Parameters Customer Options Form Page 2 Note If any changes are made to the system parameters customer options form you must log out of the SAT and log back in for the changes to take effect MJH Reviewed Solution amp Interoperability Test Lab Application Notes 10 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 2 On Page 3 of the System Parameters Customer Options form verify that the ARS feature is enabled display system parameters customer options Page 3 of OPTIONAL FEATURES Abbreviated Dialing Enhanced List Access Security Gateway ASG Analog Trunk Incoming Call ID A D Grp Sys List Dialing Start at 01 Answer Supervision by Call Classifier ARS ARS AAR Partitioning Dialing without FAC k Core Capabilities Link Plus Capabilities Async Transfer Mode ATM PNC Async Transfer Mode ATM Trunking AIM WAN Spare Processor ATMS Attendant Vectoring ARS AAR ASAI Lin ASAI NOTE You must logoff amp login Au
17. IP Direct Audio media shuffling is set to yes to allow audio traffic to be sent directly between IP endpoints to reduce the use of media resources e Set the Codec Set to 1 for the corresponding calls within the IP Network Region e All other values are the default values change ip network region 1 Page iL i 19 IP NETWORK REGION Region 1 Location 1 Authoritative Domain avaya com Name MEDIA PARAMETERS Intra region IP IP Direct Audio yes Codec Set 1 Inter region IP IP Direct Audio yes UDP Port Min 2048 IP Audio Hairpinning n UDP Port Max 3329 DIFFSERV TOS PARAMETERS RTCP Reporting Enabled y Call Control PHB Value 46 RTCP MONITOR SERVER PARAMETERS Audio PHB Value 46 Use Default Server Parameters y Video PHB Value 26 802 1P Q PARAMETERS Call Como 302 19 Peiori 6 ACCO GOZ iio wWieskoueskteys 6 WalCleyo 02 19 Menorca 5 AUDIO RESOURCE RESERVATION PARAMETERS H 323 IP ENDPOINTS RSVP Enabled n H 323 Link Bounce Recovery y Idle Traffic Interval sec 20 Keep Alive Interval sec 5 Keep Alive Count 5 Figure 36 IP Network Region 1 Page 1 5 1 5 IP Codec Sets One codec set is defined in the reference configuration 5 1 5 1 IP Codec Set 1 G 711MU is typically used within the same location and is often specified first Other codecs could be specified as well depending on local requirements Codec set 1 is
18. Links to SIP Entity S8300_G450_AE Refresh Summary View J 1 Item Filter Enable Details Session Manager Name SIP Entity Resolved IP Port Proto Conn Status Reason Code Link Status A SM 01 10 64 21 41 5061 TLS Up 200 OK Up Figure 72 SIP Entity Link Connection Status 10 2 2 Verify System State Expand the Session Manager menu and click System State Administration Verify that the Management State is Management Enabled and the Service State is Accept New Service MJH Reviewed RRR xx xx xxxx Solution amp Interoperability Test Lab Application Notes 88 of 91 2010 Avaya Inc All Rights Reserved Metaswitch_SM AVAYA Avaya Aura System Manager 5 2 Welcome admin Last Logged on at May 03 2010 12 25 PM Help Log off ession Manager System Status System State Administration psa enone System State Administration 13 Communication Sisa This page shows the current service and management state of configured Session Managers You can use this page to make state changes in the context of an g upgrade or necessary maintenance gt User Management Es Session Manager Instances Monitoring Network Routing Policy Refresh Management State _ Service state Shutdown System Security 1 Item Applications ARA RA EI A AA APA AA E Session Management Last Service State Active Call gt Settings O p State Service State Change Version y Session Manager SM 01 Management Acc
19. Location fields Help for Committing configuration changes Figure 57 Dial Pattern Details 6 4 Avaya Aura Session Manager To complete the Avaya Aura Session Manager configuration add an Avaya Aura Session Manager instance To add an Avaya Aura Session Manager select Session Manager on the left Network Routing Policy menu and click on the New button The screen shown below is displayed 1 General section a Enter a name in the SIP Entity Name field e g SM 01 b Enter an optional description in the Description field c Inthe Management Access Point Host Name IP field enter the IP address of the management interface of the Avaya Aura Session Manager server e g 10 64 20 30 2 Security Module section Note The SIP Entity IP address is automatically populated with the IP address defined for this SIP Entity SM 01 in Section 6 3 4 a Enter the Network Mask e g 255 255 255 0 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 57 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM b Enter the Default Gateway e g 10 64 20 1 c Inthe Speed amp Duplex drop down menu verify Auto is selected default 3 Use all other default parameters 4 Click the Save button and the completed form will be displayed MJH Reviewed Solution amp Interoperability Test Lab Application Notes 58 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metasw
20. Node Name tt rita 31 5 1 4 IP Network RG SIONS dias 31 5 1 5 IP Codec Sets ass chan Tna a a e a CR O 33 5 1 6 SUP ak Gru PS ibi 34 5 1 7 Private Unknown Numbering Basic Configuration oconoccconnnonononononononananananccnacnno 39 5 1 8 Call ruti di 40 5 1 9 Save Avaya Aura Communication Manager Provisioning oooooncnoncnoncnonananininannnos 41 6 Avaya Aura Session Manager Provisioning eesesseeseresresresresresresresresrerresrerresree 42 6 1 Network A cerns cteptuten lettin aS 42 6 2 Lossuto into System Manager oia dalla 42 6 3 Network Routing POMCY ta tala 44 6 3 1 SIP Doman seen eae a O 44 6 3 2 Adaptations tala 45 6 3 3 TOC AU OS a a a a E A T AEE O Eai 47 6 3 4 A A a N aa e a e a e e a ais 48 6 3 5 Entity Linkse e ease eel MRA oad Ore ae aaa 51 6 3 6 TIME Ranges E Ee a aaa eaaa eaa a ey an 52 6 3 7 Routing POLICIES en e aaae a ase ea aes 53 6 3 8 Di l Patterns onn ar a a A a par A dd 55 6 4 Avaya Aura Session Manager iveco liada den dada dnd idad 57 6 5 A A debe EEEa E iai 60 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 2of91 RRR xx xx XXXxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 6 6 User Management for Adding SIP Telephone US TS ooocccnnoconocccnonccconaccnnnconannnnonos 65 de Acme Packet 3800 Net Net Session Director oooocccnonccconccnonccnoncnonnncnonncnnnccnonacnnnos 69 7 1 Acme Packet Seryice States miric eenen e sania ie A A E R E N siis 69 1
21. Reserved Metaswitch_SM 4 1 6 1 Configure SIP Trunk for internal calls 1 Using the change signaling group 8 command configure the Signaling Group as follows e Set the Group Type field to sip e Set the Transport Method field to tls Note This specifies the transport method used between Avaya Aura Communication Manager and Avaya Aura Session Manager not the transport method used to the Metaswitch network e Specify the procr or C LAN used for SIP signaling node name procr and the Avaya Aura Session Manager node name SM2 as the two ends of the signaling group in the Near end Node Name and Far end Node Name fields respectively These field values are taken from the IP Node Names form shown in Section 4 1 3 e Specify 5061 in the Near End and Far end Listen Port fields e Enter the value 1 into the Far end Network Region field This value is for the IP Network Region defined in Section 4 1 4 1 e Set the Far end Domain field to avaya com The Direct IP IP Audio Connections field should be set to y to allow RTP voice paths to be established directly between IP telephones and the Metaswitch network The DTMF over IP field should remain set to the default value of rtp payload This value enables Avaya Aura Communication Manager to send DTMF tones using RFC 2833 e The default values for the other fields may be used change signaling group 8 Page iL OE il SIGNALING GROUP Group Number 8 Gr
22. Trunks n Enterprise Wide Licensing n ISDN PRI y ESS Administration n Local Survivable Processor n Extended Cvg Fwd Admin n Malicious Call Trace n External Device Alarm Admin n Media Encryption Over IP n Five Port Networks Max Per MCC n Mode Code for Centralized Voice Mail n Flexible Billing n Forced Entry of Account Codes n Multifrequency Signaling y Global Call Classification n Multimedia Call Handling Basic n Hospitality Basic y Multimedia Call Handling Enhanced n Hospitality G3V3 Enhancements n Multimedia IP SIP Trunking n IP Trunks y Figure 30 System Parameters Customer Options Form Page 4 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 29 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 5 1 1 Dial Plan In the reference configuration five digit extensions for analog digital and H 323 stations were provisioned with the format 7xxxx Five digit extensions for SIP stations were provisioned with the format 531xx Trunk Access Codes TAC are 3 digits in length and begin with 1 The Feature Access Code FAC to access ARS is one digit in length the number 9 The dial plan is modified with the change dialplan analysis command 1 On Page 1 of the form e Local extensions analog digital and H 323 stations 1 In the Dialed String field enter 7 2 In the Total Length field enter 5 3 In the Call Type field enter ext e Local extensions SI
23. changed through PHY and Network Interface Configurations D At the configure prompt enter exit 7 Reboot the Acme Packet by entering reboot at the Superuser ff prompt MJH Reviewed Solution amp Interoperability Test Lab Application Notes 70 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 7 3 2 Local Policies Allows any SIP requests from the INSIDE realm to be routed to the SERV_PROVIDER Session Agent Group in the OUTSIDE realm and vice versa 7 3 2 1 INSIDE to OUTSIDE From the configure prompt steps 1 thru 3 in Section 5 3 1 Configure session router gt local policy to create a local policy for the INSIDE realm with the following settings from address gt to address gt source realm gt INSIDE state gt enabled policy attributes E 1 ii iii iv V vi vii next hop gt SAG SERV_PROVIDER realm gt OUTSIDE start time gt 0000 end time gt 2400 days of week gt U S app protocol gt SIP state gt enabled 7 3 2 2 OUTSIDE to INSIDE 1 Configure session router gt local policy to create a local policy for the OUTSIDE realm with the following settings from address gt to address gt source realm gt OUTSIDE state gt enabled eae rf policy attributes i ii iii iv v vi vii next hop gt SAG ENTERPRISE realm gt INSIDE start time gt 0000 end time gt 2400 days of week gt U S app protocol gt
24. description in the Notes field if desired Under the Location Pattern heading click on Add Enter the IP address information for the Location e g 10 64 20 Enter a description in the Notes field if desired Repeat steps 3 thru 5 if the Location has multiple IP segments Modify the remaining values on the form if necessary otherwise use all the default values Click on the Commit button 9 Repeat all the steps for each new Location ADA ES MJH Reviewed Solution amp Interoperability Test Lab Application Notes 47 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM Welcome admin Last Logged on at Apr 28 2010 2 43 PM Avaya Aura System Manager 5 2 Help Log off cations Location Details gt Asset Management Location Details Commit R Communication System Management gt User Management General 7 Monitoring Name 10 64 20 21 0 Y Network Routing Policy Notes Adaptations Dial Patterns Managed Bandwidth E Entity Links Average Bandwidth per Call 80 Kbit sec Locations Gm Time to Live secs 3600 Regular Expressions Routing Policies Location Pattern SIP Domains SIP Entities Remove z 2 Items Refresh Filter Enable Time Ranges EE O IP Address Pattern Notes I zs hazara 2 Personal Settings DO gt 110 64 21 hisccuity O 10 64 20 Applications Select All None O of 2 Selected gt S
25. for the outside network with the following settings a state gt enabled b realm id gt OUTSIDE c sip port gt i address gt 205 xxx xxx 106 ii port gt 5060 iii transport protocol gt UDP Inside SIP interface Configure session router gt sip interface to create a sip interface for the inside network with the following settings a state gt enabled b realm id gt INSIDE c sip port i address gt 10 64 20 106 ii port gt 5060 iii transport protocol gt TCP 7 3 11 SIP Manipulation SIP manipulation specifies rules for manipulating the contents of specified SIP headers In the reference configuration the following header manipulations are performed NAT IP addresses in the From header of SIP requests NAT IP addresses in the To header of SIP requests NAT IP addresses in the Remote Party ID header of SIP requests NAT IP addresses in the History Info header of SIP requests NAT IP addresses in the Alert Info header of SIP requests This is different from other rules because it will NAT CID caller ID URIs in addition to SIP URIs 1 Configure session router gt sip manipulation with the following settings a name gt NAT_IP b description gt Topology hiding for SIP headers 2 Proceed to the following sections MJH Reviewed Solution amp Interoperability Test Lab Application Notes 76 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 7 3 11 1 From Header 1 Configur
26. forking 00000 0 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 89 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 10 4 Conclusion As illustrated in these Application Notes Avaya Aura Communication Manager 5 2 1 Avaya Aura Session Manager 5 2 1 1 and Acme Packet Session Border Controller 6 1 0 can be configured to interoperate successfully with Metaswitch MetaSphere CFS This solution provides users of Avaya Aura Communication Manager the ability to support inbound and outbound as well as on net and off net calling over a SIP trunk 11 References 11 1 Avaya The following Avaya product documentation is available at http support avaya com 1 SIP Support in Avaya Aura Communication Manager Running on Avaya S8xxx Servers Doc ID 555 245 206 May 2009 2 Administering Avaya Aura Communication Manager Doc ID 03 300509 May 2009 3 Avaya Aura Session Manager Overview Doc ID 03 603323 Issue 2 Release 5 2 March 2010 4 Installing Avaya Aura Session Manager Doc ID 03 603473 Issue 1 3 Release 5 2 January 2010 5 Administering Avaya Aura Session Manager Doc ID 03 603324 Issue 2 Release 5 2 November 2009 6 Administering Avaya Aura Communication Manager as a Feature Server Doc ID 03 603479 Issue 1 3 Release 5 2 March 2010 7 Maintaining and Troubleshooting Avaya Aura Session Manager Doc ID 03 603325 8 Feature
27. route calls a the SIP trunk configured in Section 4 1 6 1 to the Avaya Aura Session Manager which in turn completes the calls to local SIP stations AAR matches on the called number and sends the call to a specified route pattern 1 Use the change aar analysis command to configure the route pattern selection rule based upon the number dialed In the reference configuration 5 digit SIP stations were provisioned with the extension format 531xx change aar analysis 531 Page lor 2 AAR DIGIT ANALYSIS TABLE Location all Percent Full 2 Dialed Total Route Call Node ANI SHOEI ING Min Max Pattern Type Num Reqd 531 5 5 8 aar n Figure 22 AAR Analysis Form MJH Reviewed Solution amp Interoperability Test Lab Application Notes 23 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 4 1 8 1 3 Route Patterns The reference configuration used route pattern 9 for ARS calls to Session Manager Note Route patterns may also be used to add or delete digits prior to sending them out the specified trunk s This feature was not used in the reference configuration 1 Use the change route pattern command to define the SIP trunk group to be used in the route pattern that ARS selects e Set the Grp No field to 9 e Set the FRL field to 0 e The default values for the other fields may be used change route pattern 9 Page i Oi 3 Pattern Number 9 Pattern Name Outbound SM2 SCCAN n Seeve Eo
28. testing the configured SIP binding was configured as follows Name Value Name Customer information Customer information 2 Customer information 3 Customer information 4 Customer information 5 Customer information 6 Usage Use DN for identification SIP authentication required SIP domain name IP address match required Contact IP address Format w x y z Contact IP port 0 65535 Supported incoming trunk group parameter type Trunk group parameter type on outgoing messages Proxy IP address Format w x z Proxy IP port 0 65535 Transport protocol Media Gateway model Avaya CM SM is vl Subscriber True x False x 208 MN 135 False i x 205 B 106 5060 None x None iv 10 220 20 25 5060 UDP x Media Gateway Model Avaya CM SM iss Network Node C Override None Default Preferred location of Trunk Gateway None m ESA Protection Domain None m Trusted True iv Use caller name provided by SIP device False x Play announcements when error conditions occur True iv Use static NAT mapping False y Maximum call appearances 1 2147483647 1024 Maximum concurrent high bandwidth call appearanc D Poll peer device True Polling interval 1 3600 seconds 30 Current number of call appearances in use 0 MJH Reviewed Solution amp Interoperability Test Lab Application Notes RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved E Ill 81 of 91 Metaswitch_SM
29. 112 MA A A ie anh eaa oe eaa aeaa hay ced cae 90 11 3 O A O A a a a a vals Raat dita 90 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 3 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 1 Introduction These Application Notes describe the steps to configure an Avaya Aura SIP trunk solution with Metaswitch MetaSphere CFS The Avaya SIP trunk architecture consists of Avaya Aura Communication Manager version 5 2 1 and Avaya Aura Session Manager version 5 2 1 1 and an Acme Packet 4500 Net Net Session Director 6 1 0 Various Avaya analog digital H 323 and SIP stations are also included in the configuration The Acme Packet 4500 Net Net Session Director is used as an edge device between the Avaya Customer Premises Equipment CPE and the Metaswitch MetaSphere solution Avaya Aura Session Manager performs as the SIP trunking hub where all inbound and outbound SIP call routing and other call processing decisions are made Avaya Aura Communication Manager SIP trunks and Acme Packet session agents are provisioned to terminate at Avaya Aura Session Manager The Metaswitch MetaSphere CFS solution described in these Application Notes is designed for customers using Avaya Aura Communication Manager and Avaya Aura Session Manager The Metaswitch MetaSphere CFS solution provides access to service providers for local and or long Distance PSTN calling via
30. 8 3 PBX object configuration The Avaya solution is modeled in MetaView as a PBX The settings used during testing are shown below 8 3 1 PBX Object Settings Subscriber Group 604 698 Remote Subscribers Whistler BC Number status Normal Recently moved from old number False y Isignaling type SIP Fix bits ISend DID sequence for Listed Directory Number True DNIS used in DID sequence for Listed Directory Num 6046982010 Calling number connected line ID screening C Override Owned DN Default Default maximum call appearances for PBX lines 1 C Override 64 Default Long distance carrier Override 0001 IntraLATA carrier Override 0001 International carrier Override 0001 PIN 0000 Locale English US lv Second locale None Iv Biling type C Override Flat rate Default Number Yalidation and routing attributes C Override Deny all usage sensitive features C Override False Default Service suspended None x lForce LNP lookup C Override False Default Subscriber timezone C Override US Pacific Default Line Traffic Study False iv Enabled date PDT 4 14 10 11 50 04 AM charge indication C Override None Default Category C Override Ordinary calling subscriber Default MJH Reviewed Solution amp Interoperability Test Lab Application Notes 82 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 8 3 2 PBX Line Object Settings Configured SIP Binding Avaya CM SM
31. 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM Name SIP Entity as Time Of Dial Notes Destination Day Pattern s to S8300_G450_AE S8300_G450_AE Anytime 7xxxx Any call to a 5 digit extension beginning with 7 will be routed to Avaya Aura Communication Manager to Acme_Packet Acme Packet Anytime 303xxxxxxx Any call to a 10 digit 732xxxxxxx number beginning with 303 or 732 will be routed to Acme Packet Table 4 Routing Policy Provisioning To add a Routing Policy select Routing Policies on the left Network Routing Policy menu and click on the New button on the right The Routing Policy Details window will open General section a Enter a descriptive name in the Name field b Enter a description in the Notes field if desired SIP Entity as Destination section a Click the Select button b Select the SIP Entity that will be the destination for this call c Click the Select button and return to the Routing Policy Details form Time of Day section a Leave default values Note Multiple time ranges may be selected and a Ranking value applied 0 is the highest Dial Pattern section Note Step 4 may be skipped Dial Patterns will be mapped to Routing Policies in the Section 6 3 8 a Click the Add button and select the Dial Pattern for this Routing Policy b Click on Select and return to the Routing Policy Details form MJH
32. AC address assigned to the Acme This MAC address is found by entering the command gt show prom info mainboard e g 00 08 25 A0 E2 20 To define a virtual MAC address replace the last digit with 8 thru f duplex mode gt FULL g speed gt 100 7 3 4 2 Private Physical Interface l Configure system gt phy interface to create a phy interface to the private Avaya CPE side of the Acme Packet with the following settings papp name gt Private operation type gt media port gt 0 slot gt 1 virtual mac gt 00 08 25 A0 E2 2e MJH Reviewed Solution amp Interoperability Test Lab Application Notes 72 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM f duplex mode gt FULL g speed gt 100 7 3 5 Realms Realms are used as a basis for determining egress and ingress associations between physical and network interfaces as well as applying header manipulation such as NAT 7 3 5 1 Outside Realm l Configure media manager gt realm config to create a realm for the outside network with the following settings cro ge mo Af of identifier gt OUTSIDE addr prefix gt 0 0 0 0 network interfaces gt Public 0 out manipulationid gt NAT_IP mm in realm gt enabled mm in network gt enabled mm same ip gt enabled mm in system gt enabled access control trust level gt medium invalid signal threshold gt 1 maximum signal threshold gt 1 untrusted signal threshold gt 1 7 3 5
33. AVAYA Avaya Solution amp Interoperability Test Lab Application Notes for Avaya Aura Communication Manager 5 2 1 Avaya Aura Session Manager 5 2 1 1 and Acme Packet 4500 Net Net Session Director integration with Metaswitch MetaSphere CES Issue 0 1 Abstract These Application Notes describe the steps to configure an Avaya Aura SIP trunk solution with Metaswitch MetaSphere CFS The Avaya SIP trunk architecture consists of Avaya Aura Communication Manager version 5 2 1 and Avaya Aura Session Manager version 5 2 1 1 and an Acme Packet 4500 Net Net Session Director 6 1 0 The Metaswitch MetaSphere CFS solution referenced within these Application Notes is designed for customers with an Avaya SIP trunk solution The Metaswitch MetaSphere CFS solution provides access to service providers for local and or long Distance PSTN calling via standards based SIP trunks directly without the need for additional TDM enterprise gateways or TDM cards and the associated maintenance costs Information in these Application Notes has been obtained through DevConnect compliance testing and additional technical discussions Testing was conducted in the Avaya Interoperability Test Lab utilizing a connection to the Metaswitch Test Lab over the public network MJH Reviewed Solution amp Interoperability Test Lab Application Notes 1 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM Table of Contents 1 WAVE O
34. Avaya 9600 Series IP Telephones SIP 2 5 0 Avaya 9600 Series IP Telephones H 323 3 0 Avaya one X Communicator H 323 softphone 5 2 Avaya 64xx Digital Telephone Avaya 6210 Analog Telephone Fax Machine Acme Packet Net Net 4500 Session Director SCX6 1 0 MR 1 Patch 1 WS Build 282 Metaswitch Networks MetaSphere CFS 7 1 01 SUO Table 1 Equipment and Software Used in the Reference Configuration MJH Reviewed Solution amp Interoperability Test Lab Application Notes 8 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 4 Configure Avaya Aura Communication Manager for SIP Trunking This Section describes the steps for configuring Avaya Aura Communication Manager with the necessary signaling and media characteristics for the SIP trunk connection with the Metaswitch solution Note The initial installation configuration and provisioning of the Avaya servers for Avaya Aura Communication Manager Avaya Media Gateways and their associated boards as well as the Avaya telephones are presumed to have been previously completed and are not discussed in these Application Notes The Avaya CPE site utilized an Avaya Aura Communication Manager running on an Avaya S8300 server with an Avaya G450 Media Gateway Note The Avaya Aura Communication Manager commands described in these Application Notes were administered using the System Access Terminal SAT S
35. D CLO aiid ea goa cia cease adc aaa EE EE EEE E api E E E 4 1 1 Interoperability Compliance Testing nda aero 4 1 2 UI A a 5 2 Reference COMET OU AU ON series nin ven taosi o 5 2 1 Local to Foreign Domain Conversion for Outbound CallS oooonoconiccnnccnocanicnnanananos 7 3 Equipment and Software Validated ccoo nioninoiodanobiniacincain cial dagas 8 4 Configure Avaya Aura Communication Manager for SIP Trunking 9 4 1 Verify System Capacity and Features c 0 c si sesccccesscesectstanesedevevsntsedersucecsveassieseuscesses 10 4 1 1 ANT AAA A II ET EEEE E RE RE 12 4 1 2 Win Or Dial plait AAA A E E RA ESEO ES 13 4 1 3 Node Name Seinstra iste areo a E a Aro e oE Ea EES 13 4 1 4 IRENE YOR Re BIOS dia 14 4 1 5 JIE Codec Sets td ei alias 15 4 1 6 SIP Munk GROUPS eener aa a E aA ev Ea E aA a Ea a aaa aioa 16 4 1 7 Public Unknown Numbering Basic Configuration coconoccnonononononanonononananananacnacano 21 4 1 8 CARA ide 22 4 1 9 Avaya Aura Communication Manager Stations non SIP oconnconiconocanincnanccanannno 25 4 1107 ECO PEO A ca 27 4 1 11 Save Avaya Aura Communication Manager Provisioning oconocnnocnnonanonaninnnananano 21 5 Configure Avaya Aura Communication Manager as a Feature Server for SIP A a a e a a a e Eee A eaa Aa a ORAE ES 28 5 1 Verify System Capacity and Features seseseeeseeeeeeeeeeeeeeseesersreseeseesresresrerresrerresresee 28 5 1 1 A E a aE n 30 5 1 2 AD AAA A II E E E leah dates 31 5 1 3
36. Description and Implementation for Avaya Communication Manager Doc ID535 245 205 Issue 7 Release 5 2 May 2009 11 2 Metaswitch Metaswitch product documentation is available at http www metaswitch com support 11 3 Acme Packet The following Acme Packet product documentation is available at https support acmepacket com 9 Net Net 4000 ACLI Reference Guide Release Version S C6 1 0 10 Net Net 4000 ACLI Configuration Guide Release Version S C6 1 0 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 90 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 2010 Avaya Inc All Rights Reserved Avaya and the Avaya Logo are trademarks of Avaya Inc All trademarks identified by and TM are registered trademarks or trademarks respectively of Avaya Inc All other trademarks are the property of their respective owners The information provided in these Application Notes is subject to change without notice The configurations technical data and recommendations provided in these Application Notes are believed to be accurate and dependable but are presented without express or implied warranty Users are responsible for their application of any products specified in these Application Notes Please e mail any questions or comments pertaining to these Application Notes along with the full title name and filename located in the lower right corner directly to the Avaya DevConnect Program a
37. If desired the System Manager Avaya Aura Session Manager management connection may use a different network than the SM 100 connection 6 2 Logging into System Manager The following provisioning is performed via System Manager to enable SIP trunking e Network Routing Policy o SIP Domains Define domains that may send calls to Avaya Aura Session Manager o Locations Logical physical areas that may be occupied by SIP Entities o SIP Entities Typically devices corresponding to the SIP telephony systems including Avaya Aura Session Manager itself however they may includes other devices such as SBCs o Entity Links Connection information which define the SIP trunk parameters used by Avaya Aura Session Manager when routing calls to from other SIP Entities o Dial Patterns Matching digit patterns which govern to which SIP Entity a call is routed MJH Reviewed Solution amp Interoperability Test Lab Application Notes 42 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM o Routing Policies Policies that determine which control call routing between the SIP Entities based on applicable Dial Patterns o Time Ranges Specified windows during which SIP call processing is permitted for a particular Routing Policies e Avaya Aura Session Manager Information corresponding to the Avaya Aura Session Manager Server to be managed by System Manager Configuration is accomplished by a
38. M Grp FRL NPA Pfx Hop Toll No Inserted DES IKE No Mrk Lmt List Del Digits OSME Dgts Intw abe 0 n user Des n user Figure 23 Route Pattern 9 Outbound Calls to Metaswitch 2 Use the change route pattern command to define the SIP trunk group to be used in the route pattern that AAR selects e Set the Grp No field to 8 e Set the FRL field to 0 e The default values for the other fields may be used change route pattern 8 Page ots 3 Pattern Number 8 Pattern Name to SIP stations SCCAN n SECUELA Grp FRL NPA Pfx Hop Toll No Inserted SSA No Mrk Lmt List Del Digits QSIG Dgts Intw 1 8 0 n user AE n user Figure 24 Route Pattern 8 Calls to SIP stations MJH Reviewed Solution amp Interoperability Test Lab Application Notes 24 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 4 1 8 2 Incoming Calls Avaya Aura Session Manager is used to convert the inbound Metaswitch DID number to an Avaya Aura Communication Manager extension Therefore no incoming digit manipulation was required on Avaya Aura Communication Manager Note Incoming called numbers may be changed to match a provisioned extension if necessary with the Avaya Aura Communication Manager change inc call handling trmt trunk group x command where x is the receiving trunk 4 1 9 Avaya Aura Communication Manager Stations non SIP In the reference configuration 5 digit non SIP stations were provisio
39. Notify messages based on the SIP Entities to which this adaptation is defined This functionality is similar to the Avaya Aura Communication Manager public unknown numbering and incoming call handling treatment capabilities Avaya Aura Session Manager will perform digit conversion based on whether the digits are being received incoming or sent outgoing by Avaya Aura Session Manager with another SIP Entity For example on a call from Avaya Aura Communication Manager to Metaswitch the call leg from Avaya Aura Communication Manager to Avaya Aura Session Manager is incoming while the call leg from Avaya Aura Session Manager to the Acme Packet is outgoing MJH Reviewed Solution amp Interoperability Test Lab Application Notes 45 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 1 Select Adaptations from the menu 2 Select New Enter a descriptive name e g Metaswitch Specify DigitConversionAdapter in the Adaptation Module field Set Module parameter to the domain of Metaswitch The reference configuration required that domain contained in the Request URI to be replaced with the Metaswitch domain before being sent out to Metaswitch via the Acme Packet The domain replacement was performed by specifying the Metaswitch domain here Leave the Egress URI Parameters field blank this is for adding additional parameters such as user phone Enter a description in the Notes field if desired F
40. P Early Media n H 323 Station Outgoing Direct Media n Alternate Route Timer sec 6 Figure 16 Off network calls SIP Trunk Signaling Group 9 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 19 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 2 Using the change trunk group 9 command change the Trunk Group as follows a On Page 1 of the Trunk Group form e Set the Group Type field to sip e Choose a descriptive Group Name e Specify an available trunk access code TAC e g 109 e Set the Service Type field to public ntwrk e Enter 9 as the Signaling Group number e Specify the Number of Members used by this SIP trunk group e g 10 change trunk group 9 Page ib i Bil TRUNK GROUP Group Number 9 Group Type sip CDR Reports y Group Name to SM blank CORE TN 1 TAC 109 Direction two way Outgoing Display n Dial Access n Night Service Queue Length 0 Service Type public ntwrk Auth Code n Signaling Group 9 Number of Members 10 Figure 17 Off network calls Trunk Group 9 Page 1 b On Page 3 of the Trunk Group form e Set the Numbering Format field to public This field specifies the format of the calling party number sent to the far end change trunk group 9 Page a oz Bil TRUNK FEATURES ACA Assignment n Measured none Maintenance Tests y Numbering Format public UUI Treatment service provider Replace Restricted Numb
41. P stations 1 In the Dialed String field enter 5 2 In the Total Length field enter 5 3 In the Call Type field enter ext e TAC codes 1 In the Dialed String field enter 1 2 In the Total Length field enter 3 3 In the Call Type field enter dac e FAC code ARS access 1 In the Dialed String field enter 9 2 In the Total Length field enter 1 3 In the Call Type field enter fac change dialplan analysis Page al ie aZ DIAL PLAN ANALYSIS TABLE Location all Percent Full TE Dialed otal Call Dialed Total Call Dialed Towel Cenk String Length Type String Length Type String Length Type 1 3 dac 2 5 ext 4 4 ext 5 5 ext 6 5 aar 7 5 ext 8 5 aar 9 1 fac Figure 31 Change Dialplan Analysis Form Page 1 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 30 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 5 1 2 Uniform Dialplan The uniform dial plan is modified with the change uniform dialplan command 1 On Page 1 of the form configure the following e Local extensions SIP stations 1 In the Matching Pattern field enter 7 2 Inthe Len field enter 5 3 Inthe Del field enter 0 4 Inthe Net field enter aar 5 Inthe Conv field enter n change uniform dialplan 0 Page il O 2 UNIFORM DIAL PLAN TABLE Percent Full 0 Matching Insert Node Pattern Len Del Digits Net Conv Num 7 5 0 aar n Figure 32 Change Uniform Dialplan Form
42. Page 1 5 1 3 Node Names In the IP Node Names form verify or assign the node names to be used in this configuration using the change node names ip command e SMO01 and 10 64 20 31 are the Name and IP Address of Avaya Aura Session Manager e procr and 10 64 20 25 are the Name and IP Address of the processor for Avaya Aura Communication Manager display node names ip IP NODE NAMES Name IP Address SM01 10 64 20 31 default OOOO procr 10 64 20 25 Figure 33 IP Node Names Form 5 1 4 IP Network Regions One network region was defined in the reference configuration The SIP trunk ip network regions are defined in the SIP Signaling Group form with the Far end Region parameter see Section 4 1 6 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 31 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM Network region assignments for ip interfaces may be verified with the list ip interface all command list ip interface all IP INTERFACES Net ON Type Slot Code Sfx Node Name Mask Gateway Node Rgn VLAN IP Address y PROCR 10 64 20 25 24 10 64 20 1 1 Figure 34 IP Interface IP Network Region Assignments The network region for an ip interface may be modified with the change ip interface x command where x is the board location or procr change ip interface procr Page iL Or ll IP INTERFACES Tyioes IPINOCIR Target s
43. Reviewed Solution amp Interoperability Test Lab Application Notes 54 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM AVAYA Avaya Au ra System Manager 5 E 2 Welcome admin Last Logged on at Apr 28 2010 2 43 PM Help Log off Home Network Routing Policy Routing Policies Routing Policy Details Asset Management Routing Policy Details Communication System Management General gt User Management Monitoring Name to Acme_Packet Network Routing Policy Disabled Adaptations Notes Dial Patterns SIE SIP Entity as Destination Locations Select Regular Expressions T Routing Policies Name FQDN or IP Address Type Notes SIP Domains Acme Packet 10 64 20 106 Other SIP Entities Time Ranges Time of Day Personal Settings add Remove View Gaps Overlaps Security 1 Item Refresh Filter Enable Applications Ranking 1 Name Mon Tue Wed Thu Fri Sat Sun StartTime EndTime Notes gt Settings lo 24 7 00 00 23 59 Time Range 24 7 Session Manager Select All None O of 1 Selected Shortcuts Change Password Dial Patterns Help for Routing Policy Details fields Help for SIP Entity List 2 Items Refresh E E E A i Filter Enable T Help for Time Range List a Patam 2 Min Max Emergency Call osip Domain Originating Location Notes Help for Pattern List oO 303 10 10 avaya com 10 64 20 21 0 to Acme Packet Hel
44. SH was used to connect to the SAT via the appropriate IP address login and password MJH Reviewed Solution amp Interoperability Test Lab Application Notes 9 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 4 1 Verify System Capacity and Features The Avaya Aura Communication Manager license file controls the customer capabilities Contact an authorized Avaya representative for assistance if a required feature needs to be enabled 1 On Page 2 of the display system parameters customer options form verify that the Maximum Administered SIP Trunks value is sufficient for the combination of trunks to the Metaswitch solution and any other SIP trunking applications Be aware that for each call from a non SIP endpoint to the Metaswitch solution one SIP trunk is used for the duration of the call display system parameters customer options Page 7A ie LiL OPTIONAL FEATURES ERE ORIACADA CIS q n E iw al S Maximum Administered H 323 Trunks 450 Maximum Concurrently Registered IP Stations 450 Maximum Administered Remote Office Trunks Maximum Concurrently Registered Remote Office Stations Maximum Concurrently Registered IP eCons Max Concur Registered Unauthenticated H 323 Stations Maximum Video Capable H 323 Stations Maximum Video Capable IP Softphones Maximum Administered SIP Trunks Maximum Administered Ad hoc Video Conferencing Ports Maximum Number of DS1 Boards with
45. SIP state gt enabled 7 3 3 Network Interfaces This Section defines the network interfaces to the private Avaya CPE and public Metaswitch IP networks MJH Reviewed RRR xx xx xxxx 71 of 91 Metaswitch_SM Solution amp Interoperability Test Lab Application Notes 2010 Avaya Inc All Rights Reserved 7 3 3 1 Public Network Interface l Configure system gt network interface to create a network interface to the public Internet Metaswtich side of the Acme Packet with the following settings a b c d name gt Public ip address gt 205 xxx xxx 106 netmask gt 255 255 255 128 gateway gt 205 xxx xxx 1 7 3 3 2 Private Network Interface 1 Configure system gt network interface to create a network interface to the private Avaya CPE side of the Acme Packet with the following settings a b c d name gt Private ip address gt 10 64 20 106 netmask gt 255 255 255 0 gateway gt 10 64 20 1 7 3 4 Physical Interfaces This Section defines the physical interfaces to the private Avaya CPE and public Metaswitch networks 7 3 4 1 Public Physical Interface Configure system gt phy interface to create a network interface to the public Internet Metaswitch side of the Acme Packet with the following settings 1 Pao Tp name gt Public operation type gt media port gt 0 slot gt 0 virtual mac gt 00 08 25 A0 E2 28 i Virtual MAC addresses are assigned based on the M
46. SIP Domains SIP Entities Time Ranges Personal Settings Security Applications gt Settings Session Manager Shortcuts Change Password Help for NRP Entity Links Help for Entity Links fields Help for Delete Confirmation fields Help for Creating NRP Entity Links Help for Deleting NRP Entity Links Figure 54 Entity Link Communication Manager 6 3 6 Time Ranges The Time Ranges form allows admission control criteria to be specified for Routing Policies Section 6 3 7 In the reference configuration no restrictions were used To add a Time Range select Time Ranges on the left Network Routing Policy menu and click on the New button on the right The screen shown below is displayed 1 Enter a descriptive Location name in the Name field e g Anytime 2 Check each day of the week 3 In the Start Time field enter 00 00 4 In the End Time field enter 23 59 5 Enter a description in the Notes field 1f desired 6 Click the Commit button MJH Reviewed Solution amp Interoperability Test Lab Application Notes 52 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM AVAYA Avaya Aura System Manager 5 2 Welcome admin Last Logged on at Apr 28 2010 2 43 PM Help Log off Home Network Routing Policy Time Ranges gt Asset Management Time Ranges Communication System gt Management gt User Management gt Mo
47. SM01 Near end Listen Port 5060 Far end Listen Port 5060 Far end Network Region 1 Far end Domain Bypass If IP Threshold Exceeded n Incoming Dialog Loopbacks eliminate RFC 3389 Comfort Noise n DTMF over IP rtp payload Direct IP IP Audio Connections y Session Establishment Timer min 3 IP Audio Hairpinning n Enable Layer 3 Test n Direct IP IP Early Media n H 323 Station Outgoing Direct Media n Alternate Route Timer sec 6 Figure 42 Off network calls SIP Trunk Signaling Group 2 2 Using the change trunk group 2 command change the Trunk Group as follows a On Page 1 of the Trunk Group form e Set the Group Type field to sip e Choose a descriptive Group Name e Specify an available trunk access code TAC e g 102 e Set the Service Type field to tie e Enter 2 as the Signaling Group number e Specify the Number of Members used by this SIP trunk group e g 10 change trunk group 2 Page al Oe Zi TRUNK GROUP Group Number 2 Group Type sip CDR Reports y Group Name to SM blank COREA Ne AL TAC 102 Direction two way Outgoing Display n Dial Access n Night Service Queue Length 0 Service Type tie Auth Code n Signaling Group 2 Number of Members 10 Figure 43 Off network calls Trunk Group 2 Page 1 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 38 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM b On Page 3
48. The IP Network Region form specifies the parameters used by the Avaya Aura Communication Manager components and how components defined to different regions interact with each other In the reference configuration only one ip network region was used however other combinations are possible Note Avaya IP telephones inherit the ip network region of the procr or C LAN they register to As a result if an IP phone registers to the procr in the reference configuration that phone will become part of region 1 If an IP phone needs to be defined to a different region regardless of registration this may be performed with the ip network map command not shown MJH Reviewed Solution amp Interoperability Test Lab Application Notes 14 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 4 1 4 1 IP Network Region 1 Ip network region 1 is defined for Avaya Aura Communication Manager components The network regions are modified with the change ip network region x command where x is the network region number 1 On Page 1 of the IP Network Region form e Configure the Authoritative Domain field to avaya com e By default Intra region and Inter region IP IP Direct Audio media shuffling are set to yes to allow audio traffic to be sent directly between IP endpoints to reduce the use of media resources e Set the Codec Set to 1 for the corresponding calls within the IP Network Region e All other values ar
49. UP Group Number 1 Group Type sip CDR Reports y Group Name to SM avaya com CORE Ne AL TAC 101 Direction two way Outgoing Display n Dial Access n Night Service Queue Length 0 Service Type tie Auth Code n Signaling Group 1 Number of Members 10 Figure 40 Internal calls Trunk Group 1 Page 1 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 36 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM b On Page 3 of the Trunk Group form e Set the Numbering Format field to private This field specifies the format of the calling party number sent to the far end change trunk group 1 Page S Gi Bil TRUNK FEATURES ACA Assignment n Measured none Maintenance Tests y Numbering Format private UUI Treatment service provider Replace Restricted Numbers n Replace Unavailable Numbers n Show ANSWERED BY on Display y Figure 41 Internal calls Trunk Group 1 Page 3 5 1 6 2 Configure SIP Trunk for off network calls The SIP trunk for off network calls is configured in the same fashion as the internal call SIP Trunk except that the Far end Domain is set to blank 1 Using the change signaling group 2 command configure the Signaling Group as follows e Set the Group Type field to sip e Set the Transport Method field to tcp Note This specifies the transport method used between Avaya Aura Communication Manager and Ava
50. a Aura Communication Manager on a S8300 Server in a G450 Media Gateway SIP Trunk RTP Packets e Avaya Aura System Manager amp TCP UDP or TLS Avaya Aura Session Manager on Avaya S8800 Servers A SIP Trunk v Des AO Feature Server Avaya Aura Communication Manager on 8800 Server with G430 Media Gateway RTP packetswill be sent from Avaya Communication Manager when shuffling is disabled or directly from the endpoints when shuffling is enabled Public f SIP Transport using E mA Metaswitch Service Provider IP Network MetaSphere CFS MetaSphere UMG Figure 1 Avaya Interoperability Test Lab Reference Configuration MJH Reviewed Solution amp Interoperability Test Lab Application Notes 6 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 2 1 Local to Foreign Domain Conversion for Outbound Calls The Avaya CPE environment was assigned the domain avaya com and the Metaswitch domain is 208 xxx xxx 135 For outbound calls from the Avaya CPE the destination specified in the SIP request URI should be 208 xxx xxx 135 There are two methods to accomplish this l Avaya Aura Communication Manager method Avaya Aura Communication Manager would specify the Metaswitch domain in the Far End Domain field of the Signaling Group form This would result in Avaya Aura Communication Manager sending a SIP request URI to Avaya Aura Session Man
51. a Aura Session Manager Provisioning This section provides the procedures for configuring Avaya Aura Session Manager as provisioned in the reference configuration Avaya Aura Session Manager is comprised of two functional components the Avaya Aura Session Manager server and the System Manager management server All SIP call provisioning for Avaya Aura Session Manager is performed via the System Manager web interface and is then downloaded into Avaya Aura Session Manager Note The following sections assume that Avaya Aura Session Manager and System Manager have been installed and that network connectivity exists between the two platforms 6 1 Network Interfaces Avaya Aura Session Manager is comprised of two main components the server itself and the SM 100 card The Avaya Aura Session Manager SM 100 card has four network interface ports with one being the connection to the SIP VoIP network This interface is used for all inbound and outbound SIP signaling and must have network connectivity to all provisioned SIP Entities The Avaya Aura Session Manager server has two network interface ports with one being the port used for management provisioning of Avaya Aura Session Manager This port must have network connectivity to System Manager Note In the reference configuration the SM 100 interface and the Avaya Aura Session Manager server interface were both connected to the same IP network
52. ager with the following format lt called number gt 208 xxx xxx 135 Avaya Aura Session Manager would forward this URI to the Acme Packet for transmission to Metaswitch Avaya Aura Session Manager method Avaya Aura Communication Manager would specify the Avaya domain or blank in the Far End Domain field of the Signaling Group form This would result in Avaya Aura Communication Manager sending a SIP request URI to Avaya Aura Session Manager with the following format lt called number gt avaya com By assigning an adaptation to the Acme Packet SIP Entity see Sections 6 3 2 and 6 3 4 Avaya Aura Session Manager will convert the Avaya CPE domain to the Metaswitch domain and send the following request URI to the Acme Packet lt called number gt 208 xxx xxx 135 Note In the reference configuration method 2 was chosen MJH Reviewed Solution amp Interoperability Test Lab Application Notes 7 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 3 Equipment and Software Validated The following equipment and software were used in the reference configuration Equipment Software Firmware Avaya Aura Session Manager Avaya S8800 Server w 5 2 1 1 SM100 Board Avaya Aura System Manager Avaya S8800 Server 5 2 1 1 Avaya Aura Communication Manager Avaya S8300 5 2 1 Server with Avaya IA 770 Intuity Audix Avaya G450 Media Gateway
53. anager as a Feature Server for SIP Trunking This Section describes the steps for configuring Avaya Aura Communication Manager as a Feature Server with the necessary signaling and media characteristics for the SIP trunk connection with the Metaswitch solution The Feature Server provides advanced feature capabilities to Avaya 9600 Series SIP Telephones Note The initial installation configuration and provisioning of the Avaya servers for Avaya Aura Communication Manager Avaya Media Gateways and their associated boards as well as Avaya telephones are presumed to have been previously completed and are not discussed in these Application Notes The Avaya CPE site utilized Avaya Aura Communication Manager running on an Avaya S8800 server with an Avaya G430 Media Gateway as a Feature Server for SIP endpoints Note The Avaya Aura Communication Manager commands described in these Application Notes were administered using the System Access Terminal SAT SSH was used to connect to the SAT via the appropriate IP address login and password 5 1 Verify System Capacity and Features The Avaya Aura Communication Manager license file controls the customer capabilities Contact an authorized Avaya representative for assistance if a required feature needs to be enabled 1 On Page 2 of the display system parameters customer options form verify that the Maximum Administered SIP Trunks is sufficient for the combinatio
54. anager uses ARS and AAR to direct outbound calls to Avaya Aura Session Manager 4 1 8 1 1 ARS The Automatic Route Selection feature is used to route calls via a SIP trunk configured in Section 4 1 6 2 to Avaya Aura Session Manager which in turn completes the calls to the Metaswitch In the reference configuration ARS is triggered by dialing a 9 feature access code or FAC and then dialing the called number ARS matches on the called number and sends the call to a specified route pattern 1 Use the change feature access codes command to specify 9 as the access code for external dialing e Set Auto Route Selection ARS Access Code 1 to 9 change feature access codes Page Al ie 8 FEATURE ACCESS CODE FAC Abbreviated Dialing Listl Access Cod Abbreviated Dialing List2 Access Cod Abbreviated Dialing List3 Access Cod Abbreviated Dial Prgm Group List Access Cod Announcement Access Cod Answer Back Access Cod Attendant Access Cod Auto Alternate Routing AAR Access Code 0000000 Auto Route Selection ARS Access Code 1 9 Access Code 2 Automatic Callback Activation Deactivation Call Forwarding Activation Busy DA 11 IRIEL 5222 Deactivation 33 Call Forwarding Enhanced Status Act Deactivation Call Park Access Code Call Pickup Access Code CAS Remote Hold Answer Hold Unhold Access Code CDR Account Code Access Code Change COR Access Code Change Coverage Access Code Co
55. ange Password Help for SIP Entity Details fields Help for Committing configuration changes Avaya Aura System Manager 5 2 SIP Entities SIP Entity Details Welcome admin Last Logged on at Apr 28 2010 2 43 PM Help Log off SIP Entity Details General Name SM 01 gt FQDN or IP Address 10 64 20 31 Type Session Manager 4 Notes Session Manager Location 10 64 20 21 0 gt Outbound Proxy C2 Time Zone America Denver Credential name SIP Link Monitoring SIP Link Monitoring Use Session Manager Configuration Entity Links Add Remove 4 Items Refresh Filter Enable O SIPENtity1 Protocol Port SIP Entity 2 Port Trusted smo TCP 5060 Acme Packet w sos0 Y oO smo E Te 4 5060 cm8800_6430_Fs 5060 nd smo1 vw TLs 5061 8300_G450_AE 5061 sMo1 m Ts 5061 AE CLAN w s061 x Select All None 0 of 4 Selected Port 3 Items Refresh E E o Filter Enable O Port Protocol Default Domain Notes O 5060 TCP avaya com soso UDP avaya com Y 5061 TLS w avaya com Y Select All None O of 3 Selected Input Required Cancel Figure 53 Session Manager SIP Entity Details The following SIP Entity values were specified in the reference configuration
56. associated with ip network region 1 see Section 5 1 4 1 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 33 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM The IP Codec Set form is modified with the change ip codec x command where x is the codec set number 1 On Page 1 of the form e Configure the Audio Codec field 1 to G 711MU During compliance testing G 729B and G 729AB were also tested change ip codec set 1 Page al OE 2 1 Codes ser Codec Set 1 Audio Silence Frames Packet Codec Suppression Per Pkt Size ms 1 G 711MU n 2 20 De Figure 37 IP Codec Set 1 2 On Page 2 of the form e Configure the Fax field to t 38 standard e Configure the Fax Redundancy field to 0 e Use the default settings for all other fields change ip codec set 1 Page 2 of 2 i COd Cem SE Allow Direct IP Multimedia n Mode Redundancy FAX t 38 standard 0 Modem DEAL 0 TDD TTY US 3 Clear channel n 0 Figure 38 IP Codec Set 1 Page 2 5 1 6 SIP Trunk Groups SIP trunks are defined for internal calls as well as network calls to and from the PSTN via Metaswitch A SIP trunk is created in Avaya Aura Communication Manager by provisioning a SIP Trunk Group as well as a SIP Signaling Group Note In the SIP trunk configurations below and in the corresponding Avaya Aura Session Manager configuration TCP was selected as the transport protocol in the
57. ccessing the browser based GUI of System Manager using the URL https lt ip address gt SMGR where lt ip address gt is the IP address of System Manager Log in with the appropriate credentials AVAYA Avaya Aura System Manager 5 2 Log On Help Username Password Figure 48 System Manager GUI Log On Screen MJH Reviewed Solution amp Interoperability Test Lab Application Notes 43 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 6 3 Network Routing Policy After logging in expand the Network Routing Policy Link on the left side as shown Welcome admin Last Logged on at Apr 28 2010 2 43 PM AVAYA Avaya Aura System Manager 5 2 Help Log off Asset Management Communication System Management User Management Monitoring Network Routing Policy Security Applications gt Settings Session Manager Shortcuts Change Password Figure 49 Network Routing Policy Menu 6 3 1 SIP Domains In the reference configuration one SIP domain was used The Avaya CPE location domain is avaya com Select SIP Domains from the menu Select New Enter the SIP Domain avaya com in the Name field Enter a description in the Notes field if desired Click on the Commit button AHD Note On most of the following forms to edit or delete an entry click the box next to the item to select it and to make the Edit and Delete buttons available
58. dentify sessions coming from or going to the session agent A session agent is defined for the Metaswitch service node outside and for the Avaya Aura Session Manager inside 7 3 7 1 Outside Session Agent 1 Configure session router gt session agent to create a session agent for the outside network with the following settings hostname gt 208 xxx xxx 135 ip address gt 208 xxx xxx 135 port gt 5060 state gt enabled app protocol gt SIP transport method gt UDP realm id gt OUTSIDE description gt To_Metaswitch ping method gt Options hops 0 ping interval gt 60 ping send mode gt keep alive wor poe mo Go Se 7 3 7 2 Inside Session Agent 1 Configure session router gt session agent to create a session agent for the inside network with the following settings a hostname gt 10 64 20 31 b ip address gt 10 64 20 31 c port gt 5060 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 74 0f 91 RRR xx xx xxxXx 2010 Avaya Inc All Rights Reserved Metaswitch_SM state gt enabled app protocol gt SIP transport method gt staticTCP realm id gt INSIDE description gt To_Session Manager ping method gt Options hops 0 ping interval gt 60 ping send mode gt keep alive tcp keepalive gt enabled m tcp reconn interval gt 10 marc aoe Appa 7 3 8 Session Groups Session groups SAG define single or multiple destinations that are referenced in provisioning session agents
59. dible Message Waiting Authorization Codes CAS Branch CAS Main Change COR by FAC Computer Telephony Adjunct Links Cvg Of Calls Redirected Off net DCS Basic DCS Call Coverage DCS with Rerouting a era ale at tek a dal e Digital Loss Plan Modification BSL MSE Echo Cancellation a DS1 A 4S qe SEN IS to effect the permission changes del Figure 3 System Parameters Customer Options Form Page 3 3 On Page 4 of the System Parameters Customer Options form verify that the Enhanced EC500 IP Trunks and ISDN PRI features are enabled display system parameters customer options Page 4 of OPTIONAL FEATURES Emergency Access to Attendant Enable dadmin Login Enhanced Conferencing Enhanced EC500 Enterprise Survivable Server Enterprise Wide Licensing ESS Administration Extended Cvg Fwd Admin External Device Alarm Admin Five Port Networks Max Per MCC Flexible Billing Stars al la a teh eh a da a eh E tar Re Re Forced Entry of Account Codes Global Call Classification Hospitality Basic Hospitality G3V3 Enhancements IP Trunks IP Attendant Consoles n NOTE You must logoff amp login IP Stations ISDN Feature Plus ISDN SIP Network Call Redirection ISDN BRI Trunks ISDN PRI Local Survivable Processor Malicious Call Trace Media Encryption Over IP Mode Code for Centralized Voice Mail Multifrequency Sig
60. e Security Module Status Data Replication Status RegistrationSummary User Registrations System Tools Shortcuts Change Password Help for SIP Monitoring Help for Page Fields Figure 71 SIP Entity Link Monitoring Summary Selecting a monitored SIP Entity from the list will display its status e g S8300_G450_AE MJH Reviewed Solution amp Interoperability Test Lab Application Notes 87 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM gt Asset Management Communication System Management gt User Management Monitoring gt Network Routing Policy gt Security Applications gt Settings Session Manager Session Manager Administration Network Configuration Device and Location Configuration Application Configuration System Status A System State Administration SIP Entity Monitoring Managed Bandwidth Usage Security Module Status Data Replication Status RegistrationSummary User Registrations System Tools Shortcuts Change Password Help for SIP Monitoring Help for Page Fields Welcome admin Last Logged on at May 03 2010 12 25 PM Avaya Aura System Manager 5 2 Help Log off em Status SIP Entity Monitoring SIP Entity Link Status SIP Entity Entity Link Connection Status This page displays detailed connection status for all entity links from all Session Manager instances to a single SIP entity All Entity
61. e DigitConversionAdapter Y Adaptations Module parameter 208 135 PS Egress URI Parameters Entity Links Notes Locations Regular Expressions Rona robes Digit Conversion for Incoming Calls to SM SIP Domains Remove SIP Entities 1 Item Refresh B AN A E y A IA A Filter Enable C Matching Pattern gt Min Max Delete Digits Insert Digits Address to modify Notes Time Ranges 51021745657 Ro ho 5 boh ie Personal Settings Security Select All None 0 of 1 Selected Applications gt Settings Digit Conversion for Outgoing Calls from SM gt Session Manager O Items Refresh Filter Enable Shortcuts Matching Pattern Min Max Delete Digits Insert Digits Address to modify Notes Change Password DS y E o o o o o Help for Adaptation Details fields Input Required Commit Help for Committing configuration changes Figure 51 DigitConversionAdapter Adaptation 6 3 3 Locations Locations are used to identify logical and or physical locations where SIP Entities reside by specifying the IP addressing for the locations as well as for purposes of bandwidth management if required In the reference configuration only the Avaya CPE site was defined as a Location To add a Location select Locations in the left Network Routing Policy menu and click on the New button on the right The screen shown below will open Enter a descriptive Location name in the Name field e g 10 64 20 21 0 Enter a
62. e name SM2 as the two ends of the signaling group in the Near end Node Name and Far end Node Name fields respectively These field values are taken from the IP Node Names form shown in Section 4 1 3 e Specify 5061 in the Near End and Far end Listen Port fields e Enter the value 1 into the Far end Network Region field This value is for the IP Network Region defined in Section 4 1 4 1 e Leave the Far end Domain field blank This permits inbound calls from any foreign domain e g the Metaswitch network The Direct IP IP Audio Connections field should be set to y to allow RTP voice paths to be established directly between IP telephones and the Metaswitch network The DTMF over IP field should remain set to the default value of rtp payload This value enables Avaya Aura Communication Manager to send DTMF tones using RFC 2833 e The default values for the other fields may be used change signaling group 9 Page il OE ll SIGNALING GROUP Group Number 9 Group Type sip Transport Method tls IMS Enabled n Near end Node Name procr Far end Node Name SM2 Near end Listen Port 5061 Far end Listen Port 5061 Far end Network Region 1 Far end Domain Bypass If IP Threshold Exceeded n Incoming Dialog Loopbacks eliminate RFC 3389 Comfort Noise n DTMF over IP rtp payload Direct IP IP Audio Connections y Session Establishment Timer min 3 IP Audio Hairpinning n Enable Layer 3 Test n Direct IP I
63. e serial port 115200 8 None 1 None Network management is enabled by provisioning interface Wancom0 In the reference configuration the management IP address 169 254 1 1 is assigned From the configure prompt steps 1 thru 3 in Section 7 3 1 Enter bootparam Note This command will prompt one line at a time showing the existing value Enter the new value next to the existing value If there is no change to a value hit the enter key and the next line will be presented Be careful not to modify any values other than those listed below or the Acme Packet may not recover after a reboot Console output will appear as follows acmesbc pri configure bootparam clear field go to previous field q quit boot device wancom0 2 Press Enter at the boot device wancom0 line and the next 4 lines until the following is displayed inet on ethernet e 3 Enter the IP address and mask in hex to be used for network management e g 169 254 1 1 ffffff00 and press Enter 3 more times until the following is displayed gateway inet g 4 Enter the management network gateway IP address e g 169 254 1 1 and press Enter 5 Continue to press Enter until returned to the configure prompt After the last bootparam line the following message is displayed NOTE These changed parameters will not go into effect until reboot Also be aware that some boot parameters may also be
64. e session router gt sip manipulation gt header rule with the following settings ES name gt manipFrom action gt manipulate comparison type gt case sensitive msg type gt request element rule 1 ii iii iv v vi name gt FROM type gt uri host action gt replace match val type gt ip comparison type gt case sensitive new value gt LOCAL_IP 7 3 11 2 To Header 1 Configure session router gt sip manipulation gt header rule with the following settings Sap name gt manipTo action gt manipulate comparison type gt case sensitive msg type gt request element rule i ii iii iv v vi name gt TO type gt uri host action gt replace match val type gt ip comparison type gt case sensitive new value gt REMOTE_IP 7 3 11 3 Remote Party ID Header 1 Configure session router gt sip manipulation gt header rule with the following settings monoss MJH Reviewed RRR xx xx xxxx name gt manipRpid header name gt Remote Party ID action gt manipulate comparison type gt case sensitive msg type gt request element rule i ii iii iv v name gt RPID type gt uri host action gt replace match val type gt ip comparison type gt case sensitive Solution amp Interoperability Test Lab Application Notes 77 of 91 2010 Avaya Inc All Rights Reserved Metaswitch_SM 7 3 11 4 7 3 11 5 vi new value gt LOCAL_IP Histo
65. e the default values change ip network region 1 Page i oe 19 IP NETWORK REGION Region 1 Location 1 Authoritative Domain avaya com Name Compliance Testing MEDIA PARAMETERS Intra region IP IP Direct Audio yes Codec Set 1 Inter region IP IP Direct Audio yes UDP Port Min 2048 IP Audio Hairpinning n UD Rowe Mexs 3329 DIFFSERV TOS PARAMETERS RTCP Reporting Enabled y Call Control PHB Value 46 RTCP MONITOR SERVER PARAMETERS Audio PHB Value 46 Use Default Server Parameters y Video PHB Value 26 802 1P Q PARAMETERS call Como 302 19 Peiori 6 Mulley G02 19 wWieskoesheys 6 Wille 802 19 Preseresiicyys 5 AUDIO RESOURCE RESERVATION PARAMETERS Bl 323s IE TAINIDIEYO IEIN IES RSVP Enabled n H 323 Link Bounce Recovery y Idle Traffic Interval sec 20 Keep Alive Interval sec 5 Keep Alive Count 5 Figure 10 IP Network Region 1 Page 1 4 1 5 IP Codec Sets One IP codec set is defined in the reference configuration 4 1 5 1 IP Codec Set 1 G 711MU is typically used within the same location and is often specified first Other codecs could be specified as well depending on local requirements Codec set 1 is associated with ip network region 1 see Section 4 1 4 1 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 15 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM
66. ed up to the Applications in this Sequence section 6 Click the Commit button Welcome admin Last Logged on at Apr 30 2010 3 20 PM AVAYA Avaya Aura System Manager 5 2 j i Help Log off sion Manager Application Configuration Application Sequence Editor gt Asset Management a a m Communication System Application Sequence Editor Commit J Cancel Management gt User Management Sequence Name gt Monitoring gt Network Routing Policy Name CM_8800 Security Description Applications gt Settings Applications in this Sequence Session Manager Session Manager Administration Network Configuration 1 Item Device and Location Sequence Configuration O Order firstto Name SIP Entity Mandatory ASEEN Application Configuration last Applications o CM 8800 CM8800_G430_FS E Application Sequences Implicit Users Select All None O of 1 Selected System Status System Tools Available Applications Shortcuts 1 Item Refresh Filter Enable Change Password M z Help for Application Sequences name STEEN Rests Help for Page Fields CM 8800 CM8800_G430_FS Required Figure 61 Application Sequence Editor Form 7 Select Communication System Management gt Telephony on the left a Select the appropriate Element Name b Select Initialize data for selected devices radio button c Click the Now button This will cause a data synchronization task to star
67. ept New No last service state 0 Development Patch on Version 5 2 1 1 18 Enabled Service change Mar 10 20 45 Session Manager Administration Select All None O of 1 Selected Network Configuration Device and Location Configuration Application Configuration System Status System State Administration SIP Entity Monitoring z Managed Bandwidth Usage Security Module Status Data Replication Status RegistrationSummary User Registrations System Tools Shortcuts Change Password Help for System State Administration Help for Page Fields Figure 73 System State 10 3 Verification Call Scenarios Verification scenarios for the configuration described in these Application Notes included e Inbound and outbound basic voice calls between various telephones on the Avaya Aura Communication Manager and PSTN can be made in both directions o Avaya One X Communicator H 323 Softphone as well as traditional analog digital and SIP phones e Inbound and outbound Fax calls between Avaya Aura Communication Manager and PSTN can be made in both directions Direct IP to IP Media also known as Shuffling when applicable DTMF Tone Support Additional PSTN numbering plans Supplementary calling features were verified The supplementary calling features verified are Hold Call transfer Conference Voicemail Coverage and Retrieval Call Forwarding Call Coverage Extend Call ECS500 call
68. ers n Replace Unavailable Numbers n Show ANSWERED BY on Display y Figure 18 Off network calls Trunk Group 9 Page 3 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 20 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 4 1 7 Public Unknown Numbering Basic Configuration In the reference configuration Avaya Aura Communication Manager uses a 5 digit dialing plan with extensions 7xxxx for analog digital and H 323 stations The Public Unknown Numbering form allows Avaya Aura Communication Manager to use these extensions as the calling party number for outbound calls Otherwise Anonymous is displayed as the calling number Each extension string is defined for the trunk group s that the extensions may use These trunks may be defined individually or in contiguous ranges In the reference configuration in order for a station to place off network calls to the PSTN the calling number must match the DID provided by Metaswitch or the call will be rejected by Metaswitch The public unknown numbering form was configured to convert a local calling extension to its associated Metaswitch DID Use the change public unknown numbering x command where x is the leading digit of the dial plan extensions e g 7 Set the Ext Len field to 5 Set the Ext Code field to 7 Set the Trk Grp s field to 9 Set the CPN Prefix field to the leading digits of the Metaswitch
69. ettings gt Session Manager Input Required Commit Shortcuts Change Password Help for Locations Details fields Help for Committing configuration changes Figure 52 Locations Menu 6 3 4 SIP Entities A SIP Entity must be added for Avaya Aura Session Manager and for each network component that has a SIP trunk provisioned to Avaya Aura Session Manager In the reference configuration the SIP Entities are provisioned for e Avaya Aura Communication Manager e Avaya Aura Communication Manager Feature Server e Acme Packet e Avaya Aura Session Manager itself To add a SIP Entity select SIP Entities on the left Network Routing Policy menu and click on the New button on the right The screen shown below is displayed 1 General Section a Enter a descriptive Location name in the Name field b Enter the IP address for the SIP Entity c From the Type drop down menu select a type that best matches the SIP Entity e g CM d Enter a description in the Notes field if desired e From the Adaptations drop down menu select the adaptation required for this Entity see Section 6 3 2 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 48 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM e For the Acme Packet Entity the Metaswitch adaptation is selected This function is applied to convert the Metaswitch DID to a Communication Manager extension It also con
70. figure Options Form MJH Reviewed Solution 4 Interoperability Test Lab Application Notes 64 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 6 6 User Management for Adding SIP Telephone Users SIP users must be added to Session Manager 1 Select User Management gt User Management on the left Then click on New not shown to open the New User Profile page a Enter a First Name and Last Name for the user AVAYA Avaya Aura System Manager 5 2 e E Help Log off it User Edit Asset Management Communication System User Profile Edit 53102 avaya com Management User Management General Identity Communication Profile Roles Override Permissions Group Membership Attribute Sets Default Contact List Private Contacts Manage Roles Expand All Collapse All User Management Global User Settings General vi Group Management Last Name 53102 7 Monitoring E o First Name Station Network Routing Policy 5 Middle Name gt Security a Applications oe BUBDD Description gt Settings gt Session Manager administrator communication_user Shortcuts agent User Type i Change Password yP Superar resident_expert Help for Edit User service_technician Help for New Private Contact lobby_phone Help for Edit Private Contact Status Offline Corta Help for Delete Private Contact Update Time Mar 22 2010 18 08 3 He
71. he conversion from the Metaswitch DID to the Avaya Aura Communication Manager extension is performed before the dial pattern match for inbound calls To add a Dial Pattern select Dial Patterns on the left Network Routing Policy menu and click on the New button on the right The screen shown below is displayed In this example a Request URI to a 10 digit number beginning with 732xxxxxxx and sent by avaya com is defined this would be an outbound call from Avaya Aura Communication Manager to Avaya Aura Session Manager destined for Metaswitch 1 General section a Enter a unique pattern in the Pattern field e g 732 b In the Min column enter the minimum number of digits e g 10 c In the Max column enter the maximum number of digits e g 10 d In the SIP Domain field drop down menu select the domain that will be contained in the Request URI received by Avaya Aura Session Manager from Avaya Aura Communication Manager e Enter a description in the Notes field if desired 2 Originating Locations and Routing Policies Section a Click on the Add button and a window will open not shown b Click on the boxes for the appropriate Originating Locations see Section 6 3 3 and Routing Policies see Section 6 3 7 that pertain to this Dial Pattern i Location 10 64 20 21 0 ii Routing Policies to Acme_Packet c Click on the Select button and return to the Dial Pattern window 3 Click the Commit button 4 Repeat steps 1 t
72. hru 3 for the remaining Dial Patterns MJH Reviewed Solution amp Interoperability Test Lab Application Notes 56 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM AVAYA Avaya Aura System Manager 5 2 Welcome admin Last Logged on at Apr 28 2010 2 43 PM Help Log off Home Network Routing Policy Dial Patterns Dial Pattern Details gt Asset Management Dial Pattern Details Commit gt Communication System Management 7 i gt User Management enera gt Monitoring Pattern 732 Y Network Routing Policy Min 10 Adaptations Max 10 ial a Dial Patterns Emergency Call Entity Links SIP Domain avaya com Locations E z Notes to Acme Packet Regular Expressions ar Routing Policies SIP Domains Originating Locations and Routing Policies SIP Entities Time Ranges 1 Item Refresh Filter Enable ene 7 Originating Routing Policy Routing Routing Policy Routing Personal Settings C Originating Location Name _ cation Not N Rank 2 Policy ES Policy Notes gt Security Disabled Destination 10 64 20 21 0 to Acme Packet o Acme Packet Applications gt Settings Select All None O of 1 Selected Session Manager Shortcuts Denied Originating Locations Change Password Help for Dial Pattern Details O Items Refresh Filter Enable fields Originating Location Notes Help for Location and Routing Policy Lists Input Required Commit Help for Denied
73. ice idle state as shown below status trunk 9 Member Port 0009 001 T00334 0009 002 T00335 0009 003 T00336 0009 004 T00337 0009 005 T00338 0009 006 T00339 0009 007 TOO340 0009 008 T00341 0009 009 T00342 0009 010 T00343 TRUNK GROUP STATUS Service State in service idle in service idle in service idle in service idle in service idle in service idle in service idle in service idle in service idle in service idle Mtce Connected Ports Busy no no no no no no no no no no Figure 67 Status Trunk Verify the status of the SIP signaling groups by using the status signaling group n command where n is the administered signaling group number Verify the signaling group is in service as indicated in the Group State field shown below status signaling group 9 Group ID Group Type Signaling Type Group State STATUS SIGNALING GROUP 9 sip Active NCA TSC Count 0 talves mAs Gm Comares 10 facility associated signaling in service MJH Reviewed RRR xx xx xxxx Figure 68 Status Signaling Group Solution amp Interoperability Test Lab Application Notes 85 of 91 2010 Avaya Inc All Rights Reserved Metaswitch_SM Make a call between an Avaya Aura Communication Manager H 323 station and the PSTN Verify the status of connected SIP trunk by using the status trunk x y command where x is the number of the SIP trunk group and y is the ac
74. ield b Select the Communication Manager SIP Entity see Section 6 3 4 for SIP Entity 4 Click the Commit button Welcome admin Last Logged on at Apr 30 2010 3 20 PM AVAYA Avaya Aura System Manager 5 2 i i Help Log off sion Manager Application Configuration Application Editor gt Asset Management gt Communication System Application Editor commit Management gt User Management Application Editor Monitoring gt Network Routing Policy Name CM_8800 gt Security SIP Entity CM8800_G430_FS vw gt Settings Session Manager Application Attributes optional Session Manager Administration Name Value Network Configuration Device and Location Application Handi Configuration URI Parameters Application Configuration Applications Application Sequences Implicit Users Required System Status System Tools Shortcuts Change Password Help for Applications Help for Page Fields Figure 60 Application Editor Form MJH Reviewed Solution amp Interoperability Test Lab Application Notes 62 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 5 Select Session Manager gt Application Configuration gt Application Sequences on the left Click on New not shown a Enter a descriptive name in the Name field b Click on the sign next to the appropriate Available Applications and the selected available application will be mov
75. ion Manager to the provisioned EC500 destination endpoint Note Only the basic EC500 call redirection functionality was used in the reference configuration ECS500 supports significantly more features 1 Use the command change off pbx telephone station mapping x where x is the Avaya Aura Communication Manager station e g 74567 e Station Extension This field will automatically populate e Application Enter EC500 e Phone Number Enter the phone that will also be called e g 7325555555 e Trunk Selection Enter 9 to route the call over trunk 9 Note ARS could also be entered depending on the configuration This means ARS will be used to determine how Avaya Aura Communication Manager will place the new outbound call e Config Set Enter 1 e Use the default values for all other fields change off pbx telephone station mapping 74567 Page il ie 3 STATIONS WITH OFF PBX TELEPHONE INTEGRATION Station Application Dial CC Phone Number Trunk Config Dual Extension Prefix selection SEL Mode 74567 EC500 7325555555 9 1 Figure 27 EC500 Station Mapping 4 1 11 Save Avaya Aura Communication Manager Provisioning Enter the save translation command to make the changes permanent MJH Reviewed Solution amp Interoperability Test Lab Application Notes 27 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 5 Configure Avaya Aura Communication M
76. itch_SM Welcome admin Last Logged on at Apr 28 2010 2 43 PM AVAYA Avaya Aura System Manager 5 2 Help Log off Edit Session Manager Asset Management i Communication System Edit Session Manager Management User Management General Security Module Monitoring CDR Personal Profile Manager PPM Connection Settings Event Server Monitoring Expand All Collapse All Network Routing Policy Security General Applications SIP Entity Name bacina Description Session Manager Management Access Point Host Name IP 10 64 20 30 Session Manager A a Administration Network Configuration Device and Location Direct Routing to Endpoints Enable x Configuration Application Configuration Security Module System Status i 64 20 31 System Tools SIP Entity IP Address 10 64 20 31 Network Mask 255 255 255 0 Shortcuts Default Gateway 10 64 20 1 Change Password Call Control PHB 46 Help for Session Manager Administration QOS Priority 6 Help for Page Fields Speed amp Duplex Auto Y VLAN ID Monitoring Enable Monitoring Y Proactive cycle time secs 900 Reactive cycle time secs 120 EiS Number of Retries fa CDR Enable COR User CDR_User Password Confirm Password Personal Profile Manager PPM Connection Settings Limited PPM client connection y
77. ith 5 digit extensions 7xxxx change aar analysis 7 Page ik oe 2 AAR DIGIT ANALYSIS TABLE Location all Percent Full 1 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd 7 5 5 1 aar n Figure 46 AAR Analysis Form MJH Reviewed Solution amp Interoperability Test Lab Application Notes 40 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 5 1 8 1 2 Route Patterns The reference configuration used route pattern 1 for internal calls Note Route patterns may also be used to add or delete digits prior to sending them out the specified trunk s This feature was not used in the reference configuration 1 Use the change route pattern command to define the SIP trunk group included in the route pattern that AAR selects e Set the Grp No field to 1 e Set the FRL field to 0 e Let all other parameters default change route pattern 1 Page iL ie 3 Pattern Number 1 Pattern Name to SM SCCAN n Secure SIE im Grp FRL NPA Pfx Hop Toll No Inserted DES TC No Mrk Lmt List Del Digits QSIG Dgts Intw Tor 0 n user Be n user Figure 47 Route Pattern 1 Internal Calls 5 1 9 Save Avaya Aura Communication Manager Provisioning Enter the save translation command to make the changes permanent MJH Reviewed Solution amp Interoperability Test Lab Application Notes 41 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 6 Avay
78. lp for adding contact into contact list Help for editing contact from contact list Identity Help for deleting contact from Login Name 53102 avaya com contact list Authentication Type Basic Y Change Password Shared Communication Profile Password seeseessossossooso Edit Figure 63 New User Profile Form 2 Click on Identity to expand that section Enter the following fields and use defaults for the remaining fields a Login Name lt extension gt O avaya com b SMGR Login Password c Password Password to log into System Manager d Confirm Password Password to log into System Manager e Shared Communication f Profile Password Password to be entered by the user when logging onto the telephone g Confirm Password Password to be entered by the user when logging onto the telephone h Localized Display Name Name to be used as calling party i Endpoint Display Name Full name of user MJH Reviewed Solution amp Interoperability Test Lab Application Notes 65 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM j Language Preference k Time Zone Help for adding contact into contact list Help for editing contact from contact list Identity Help for deleting contact from contact list Login Name Authentication Type Change Password Shared Communication Profile Password Source loc Localized Display Name Endpoint Display Name Honorific
79. n of trunks to the Metaswitch solution and any other SIP trunking applications display system parameters customer options Page 4 ie Lil OPTIONAL FEATURES MERO CADA CIA Maximum Administered H 323 Trunks 450 Maximum Concurrently Registered IP Stations 18000 Maximum Administered Remote Office Trunks Maximum Concurrently Registered Remote Office Stations Maximum Concurrently Registered IP eCons Max Concur Registered Unauthenticated H 323 Stations Maximum Video Capable H 323 Stations Maximum Video Capable IP Softphones Maximum Administered SIP Trunks Maximum Administered Ad hoc Video Conferencing Ports Maximum Number of DS1 Boards with Echo Cancellation Maximum TN2501 VAL Boards Maximum Media Gateway VAL Sources Maximum TN2602 Boards with 80 VoIP Channels Maximum TN2602 Boards with 320 VoIP Channels 128 Maximum Number of Expanded Meet me Conference Ports 0 O E Sere Bere SS a o o o E N 00 Sees eQaoegOoogoqooqgoqoe c Figure 28 System Parameters Customer Options Form Page 2 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 28 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM Note If any changes are made to the system parameters customer options form you must log out of the SAT and log back in for the changes to take effect 2 On Page 3 of the System Parameters Customer Options form verify tha
80. naling Multimedia Call Handling Basic Multimedia Call Handling Enhanced Multimedia IP SIP Trunking to effect the permission changes Li K BS po Bl eB BB i py Bis Figure 4 System Parameters Customer Options Form Page 4 MJH Reviewed RRR xx xx xxxx Solution amp Interoperability Test Lab Application Notes 2010 Avaya Inc All Rights Reserved Metaswitch_SM 4 1 1 Dial Plan In the reference configuration five digit extensions for analog digital and H 323 stations were provisioned with the format 7xxxx Five digit extensions for SIP stations were provisioned with the format 531xx Trunk Access Codes TAC are 3 digits in length and begin with 1 The Feature Access Code FAC to access ARS is one digit in length the number 9 The dial plan is modified with the change dialplan analysis command 1 On Page 1 of the form configure the following e Local extensions analog digital and H 323 stations 1 In the Dialed String field enter 7 2 Inthe Total Length field enter 5 3 In the Call Type field enter ext e Local extensions SIP stations 1 In the Dialed String field enter 5 2 In the Total Length field enter 5 3 In the Call Type field enter ext e TAC codes 1 In the Dialed String field enter 1 2 In the Total Length field enter 3 3 In the Call Type field enter dac e FAC code ARS access 1 In the Dialed String field enter 9 2 In the Total Leng
81. nditional Call Extend Activation Contact Closure Open Code Deactivation Close Code Figure 20 Feature Access Codes Form Page 1 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 22 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 2 Use the change ars analysis command to configure the route pattern selection rule based upon the number dialed following the ARS access digit 9 In the reference configuration outbound calls are placed to the following numbers e 1732 calls to area code 732 by dialing 9 1 732 xxx xxxx e 1303 calls to area code 303 by dialing 9 1 303 xxx xxxx For example to specify 732 area code calls enter the command change ars analysis 173 and enter the following values e Set the Dialed String field to 173 e Set the Total Min field to 11 e Set the Total Max field to 11 e Set the Route Pattern field to 9 will direct to off network calls trunk e Set the Type field to fnpa Different values may be used These were the values used for the reference configuration display ars analysis 173 Page il ie 2 ARS DIGIT ANALYSIS TABLE Location all Percent Full 2 Dialed Total Route Call Node ANI String Min Max Pattern Type Num Reqd 173 11 11 9 fnpa n Figure 21 ARS Analysis Form 3 Using the same procedure specify the other called number patterns in the ARS table 4 1 8 1 2 AAR The Automatic Alternate feature is used to
82. ned with the extension format TXXXX 4 1 9 1 Voice Stations The figures below show an example of an extension Avaya H 323 IP phone Since the phone is an IP device a virtual port S00027 is automatically assigned by the system By default three call appearances are defined on Page 4 of the form 1 On Page 1 of the form e Set the Type field to match the station type e g 9620 e Set the Name field to a desired value e g Metaswitch e Set the Security Code optional to a desired value e g 123456 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 25 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM change station 74567 Page Al Oye 5 STATION Extension 74567 Lock Messages n eee 0 Type 9620 Security Code 123456 uv Port S00027 Coverage Path 1 CORSA Name Metaswitch Coverage Path 2 COSTA BILIME EO Sie elic lolas STATION OPTIONS Time of Day Lock Table Loss Group 19 Personalized Ringing Pattern 1 Message Lamp Ext 74567 Speakerphone 2 way Mute Button Enabled y Display Language english Survivable GK Node Name Survivable COR internal Media Complex Ext Survivable Trunk Dest y IP SoftPhone y IP Video Softphone n Customizable Labels y Figure 25 Avaya H 323 IP Phone Page 1 2 On Page 4 of the form e Select an empty button assignment and enter ec500 Let the timer field default to n This button will enable the EC500 capabilit
83. nitoring 1 Item Refresh Filter Enable Network Routing Policy C Name Mo Tu We Th Fr Sa Su Start Time End Time Notes Adaptations O 24 7 m u v 00 00 23 59 Time Range 24 7 Dial Patterns Select All None O of 1 Selected Entity Links Locations Regular Expressions Routing Policies SIP Domains SIP Entities Time Ranges Personal Settings gt Security Applications Settings Session Manager Shortcuts Change Password Help for NRP Time Ranges Help for Time Ranges fields Help for Delete Confirmation fields Help for Creating NRP Time Ranges Help for Modifying NRP Time Ranges Figure 55 Time Ranges 6 3 7 Routing Policies Routing Policies associate destination SIP Entities Section 6 3 4 with Time of Day admission control parameters Section 6 3 6 and Dial Patterns Section 6 3 8 In the reference configuration Routing Policies are defined for e Inbound calls to Avaya Aura Communication Manager e Outbound calls to the Metaswitch network Note Since the SIP endpoints in the reference configuration register with Avaya Aura Session Manager Session Manager knows how to route calls to those extensions and it is not necessary to create a routing policy for Avaya Aura Communication Manager Feature Server Note In the reference configuration the Regular Expressions parameters was not used MJH Reviewed Solution amp Interoperability Test Lab Application Notes 53 of
84. ocket load 1700 Enable Interface y Allow H 323 Endpoints y Allow H 248 Gateways y Network Region 1 Gatekeeper Priority 5 IPV4 PARAMETERS Node Name procr Subnet Mask 24 Figure 35 IP Interface IP Network Region Assignment The IP Network Region form specifies the parameters used by the Avaya Aura Communication Manager components and how components defined to different regions interact with each other In the reference configuration only one ip network region was used however other combinations are possible Note Avaya IP telephones inherit the ip network region of the procr or C LAN they register to As a result if an IP phone registers to the procr in the reference configuration that phone will become part of region 1 If an IP phone needs to be defined to a different region regardless of registration this may be performed with the ip network map command MJH Reviewed Solution amp Interoperability Test Lab Application Notes 32 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 5 1 4 1 IP Network Region 1 Ip network region 1 is defined for Avaya Aura Communication Manager components The network regions are modified with the change ip network region x command where x is the network region number 1 On Page 1 of the IP Network Region form e Configure the Authoritative Domain field to avaya com e By default Intra Region and Inter Region IP
85. of the Trunk Group form e Set the Numbering Format field to private This field specifies the format of the calling party number sent to the far end change trunk group 2 Page S Gi Bil TRUNK FEATURES ACA Assignment n Measured none Maintenance Tests y Numbering Format private UUI Treatment service provider Replace Restricted Numbers n Replace Unavailable Numbers n Show ANSWERED BY on Display y Figure 44 Off network calls Trunk Group 2 Page 3 5 1 7 Private Unknown Numbering Basic Configuration In the reference configuration Avaya Aura Communication Manager uses a 5 digit dialing plan with extensions 531xx for SIP stations The Private Unknown Numbering form allows Avaya Aura Communication Manager to use these extensions as the calling party number for outbound calls Otherwise Anonymous is displayed as the calling number Each extension string is defined for the trunk group s that the extensions may use These trunks may be defined individually or in contiguous ranges Use the change private unknown numbering x command where x is the leading digit of the dial plan extensions e g 5 e Set the Ext Len field to 5 e Set the Ext Code field to 5 e Set the Trk Grp s field to 1 e Set the Total CPN Len field to 5 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 39 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM All provi
86. omains The following components were used in the reference configuration and are discussed in detail in subsequent sections Avaya Aura Session Manager on a Avaya S8800 Server Avaya Aura System Manager non an Avaya S8800 Server Avaya Aura Communication Manager on an Avaya S8300 Server with an Avaya G450 Media Gateway e Avaya Aura Communication Manager on an Avaya S8800 Server with an Avaya G430 Media Gateway Note This Communication Manager serves as a Feature Server in the reference configuration for the Avaya 9600 Series SIP Telephones SIP phones requiring advanced calling features and non SIP phones configured on the same Communication Manager is currently not supported This restriction will be lifted in future releases of Session Manager and Communication Manager e Avaya 9600 Series IP Telephones SIP MJH Reviewed Solution amp Interoperability Test Lab Application Notes 5 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM Avaya 9600 Series IP Telephones H 323 Avaya one X Communicator H 323 softphone Avaya 64xx Digital Telephone Avaya 6210 Analog Telephone Fax Machine Acme Packet Net Net 4500 Session Director Metaswitch Networks MetaSphere CFS Avaya Labs simulating an Enterprise Customer Site o BD H FAX or Avaya 6400 Avaya 9600 Avaya 1600 Analog Series Series Series Avaya one X Phones Digital Phones H 323 and SIP H 323 Communicator Phones Phones Avay
87. or outgoing calls from Avaya Aura Communication Manager to the PSTN extension 74565 is converted to the Metaswitch DID 5102174567 via the public unknown numbering form on Communication Manager see Section 4 1 7 For incoming calls the Metaswitch DID 5102174567 is converted to Avaya Aura Communication Manager extension 74567 via this adaptation 3 Click the Add button and enter Matching Pattern The digit string to match gt 5102174567 Min The minimum number of digits gt 10 Max The maximum number of digits gt 10 Delete Digits The number of digits to delete gt 5 Insert Digits The digit to be inserted gt 0 Address to Modify origination destination both Associated headers to be monitored for matching digits gt Both Notes Enter a description in the Notes field if desired 4 When completed the Adaptation Details window for DigitConversionAdapter will look like Figure 51 5 Click on the Commit button MJH Reviewed Solution amp Interoperability Test Lab Application Notes 46 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM Welcome admin Last Logged on at Apr 28 2010 2 43 PM Avaya Aura System Manager 5 2 Help Log off Adaptation Details Asset Management Adaptation Details Commit R Communication System Management User Management General a Monitoring Adaptation name Metaswitch Y Network Routing Policy Module nam
88. oup Type sip Transport Method tls IMS Enabled n Near end Node Name procr Far end Node Name SM2 Near end Listen Port 5061 Far end Listen Port 5061 Far end Network Region 1 Far end Domain avaya com Bypass If IP Threshold Exceeded n Incoming Dialog Loopbacks eliminate RFC 3389 Comfort Noise n DTMF over IP rtp payload Direct IP IP Audio Connections y Session Establishment Timer min 3 IP Audio Hairpinning n Enable Layer 3 Test y Direct IP IP Early Media n H 323 Station Outgoing Direct Media n Alternate Route Timer sec 6 Figure 13 Internal calls SIP Trunk Signaling Group 8 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 17 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 2 Using the change trunk group 8 command change the Trunk Group as follows a On Page 1 of the Trunk Group form e Set the Group Type field to sip e Choose a descriptive Group Name e Specify an available trunk access code TAC e g 108 e Set the Service Type field to public ntwrk e Enter 8 as the Signaling Group number e Specify the Number of Members used by this SIP trunk group e g 10 change trunk group 8 Page al ie Bil TRUNK GROUP Group Number 8 Group Type sip CDR Reports y Group Name to SM avaya com COIS iL aye TAC 108 Direction two way Outgoing Display n Dial Access n Night Service Queue Length 0 Service Type public ntwrk A
89. p for Regular Expressions List El 732 10 10 avaya com 10 64 20 21 0 to Acme Packet Help for Committing configuration changes Select All None 0 of 2 Selected Regular Expressions O Items Refresh s Filter Enable Pattern Rank Order Deny Notes Input Required Cancel Figure 56 Routing Policy Details Click the Commit button Repeat steps 1 thru 5 for each Routing Policy Click the Commit button an 6 3 8 Dial Patterns Dial Patterns define digit strings to be matched for inbound and outbound calls In addition the domain in the request URI is also examined Note The Dial Pattern digit string with the most complete match will be selected For example if the 5 digit string 700 is defined first in the list and the 5 digit string 70001 is defined last a call for 70001 will match on the 70001 string MJH Reviewed Solution amp Interoperability Test Lab Application Notes 55 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM The following Dial Patterns were provisioned in the reference configuration Pattern Min Max SIP Domain Originating Location Routing Policy Name 7 5 5 avaya com ALL to S8300_G450_AE 303 10 10 avaya com 10 64 20 21 0 to Acme_Packet 132 10 10 avaya com 10 64 20 21 0 to Acme_Packet Table 5 Routing Policy Provisioning Note The Metaswitch adaptation is provisioned on the Acme Packet SIP Entity This means that t
90. payload This value enables Avaya Aura Communication Manager to send DTMF tones using RFC 2833 e The default values for the other fields may be used MJH Reviewed Solution amp Interoperability Test Lab Application Notes 35 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM change signaling group 1 Page Tof 1 SIGNALING GROUP Group Number 1 Group Type sip Transport Method tcp IMS Enabled y Near end Node Name procr Far end Node Name SM01 Near end Listen Port 5060 Far end Listen Port 5060 Far end Network Region 1 Far end Domain avaya com Bypass If IP Threshold Exceeded n Incoming Dialog Loopbacks eliminate RFC 3389 Comfort Noise n DTMF over IP rtp payload Direct IP IP Audio Connections y Session Establishment Timer min 3 IP Audio Hairpinning n Enable Layer 3 Test y Direct IP IP Early Media n H 323 Station Outgoing Direct Media n Alternate Route Timer sec 6 Figure 39 Internal calls SIP Trunk Signaling Group 1 2 Using the change trunk group 1 command change the Trunk Group as follows a On Page 1 of the Trunk Group form e Set the Group Type field to sip e Choose a descriptive Group Name e Specify an available trunk access code TAC e g 101 e Set the Service Type field to tie e Enter 1 as the Signaling Group number e Specify the Number of Members used by this SIP trunk group e g 10 change trunk group 1 Page al O Zi TRUNK GRO
91. reference configuration The TES protocol could have been used instead MJH Reviewed Solution amp Interoperability Test Lab Application Notes 34 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 5 1 6 1 Configure SIP Trunk for internal calls 1 Using the change signaling group I command configure the Signaling Group as follows e Set the Group Type field to sip e Set the Transport Method field to tcp Note This specifies the transport method used between Avaya Aura Communication Manager and Avaya Aura Session Manager not the transport method used to the Metaswitch network e Set the IMS Enabled field to y e Specify the procr or C LAN used for SIP signaling node name procr and the Avaya Aura Session Manager node name SM01 as the two ends of the signaling group in the Near end Node Name and Far end Node Name fields respectively These field values are taken from the IP Node Names form shown in Section 5 1 3 e Specify 5060 in the Near End and Far end Listen Port fields e Enter the value 1 into the Far end Network Region field This value is for the IP Network Region defined in Section 5 1 4 1 e Set the Far end Domain field to avaya com The Direct IP IP Audio Connections field should be set to y to allow RTP voice paths to be established directly between IP telephones and the Metaswitch network The DTMF over IP field should remain set to the default value of rtp
92. ry Info Header Configure session router gt sip manipulation gt header rule with the following settings FARO ae FS name gt manipHistInfo header name gt History Info action gt manipulate comparison type gt case sensitive msg type gt request element rule i name gt HISTORYINFO ii type gt uri host iii action gt replace iv match val type gt ip v comparison type gt case sensitive vi new value gt REMOTE_IP Alert info Header Configure session router gt sip manipulation gt header rule with the following settings D2o0T3p f name gt storeAlertInfo header name gt Alert Info action gt store comparison type gt pattern rule match value gt 0 9 msg type gt request Configure session router gt sip manipulation gt header rule with the following settings g meaoge name gt manipAlertInfo header name gt Alert Info action gt manipulate comparison type gt boolean match value gt storeAlertInfo msg type gt request new value gt storeAlertInfo 1 REMOTE_IP storeAlertInfo 3 7 3 12 Other Acme Packet provisioning 7 3 12 1 Access control This is a static Access Control List that is used to limit SIP access to only known devices 1 Configure session router gt access control with the following settings a realm id gt OUTSIDE MJH Reviewed Solution amp Interoperability Test Lab Application Notes 78 0f 91 RRR xx xx xxxx
93. sioned private unknown numbering entries can be displayed by entering the command display private unknown numbering 0 as show below display private numbering 0 Page iL One 2 NUMBERING PRIVATE FORMAT Boch Eat Tek Private Total Len Code Grp s Prefix Len a a T 4 Total Administered 3 4 4 2 4 Maximum Entries 540 5in5 1 5 Figure 45 Private unknown numbering Form Basic Configuration 5 1 8 Call routing 5 1 8 1 Internal Calls The following sections describe the Avaya Aura Communication Manager provisioning required for dialing internal non SIP extensions Note Metaswitch only assigned one DID number that had access to the PSTN The configuration required for inbound and outbound PSTN calls to and from an H 323 station on Avaya Aura Communication Manager was shown in Section 4 1 8 Although not shown here similar administration can be done for a SIP station on Avaya Aura Communication Manager as a Feature Server 5 1 8 1 1 AAR The Automatic Alternate feature is used to route calls via a SIP trunk configured in Section 5 1 6 1 to the Avaya Aura Session Manager which in turn completes the calls to local stations AAR matches on the called number and sends the call to a specified route pattern 1 Use the change aar analysis command to configure the route pattern selection rule based upon the number dialed In the reference configuration calls are placed to non SIP stations w
94. standards based SIP trunks directly without the need for additional TDM enterprise gateways or TDM cards and the associated maintenance costs 1 1 Interoperability Compliance Testing A simulated enterprise site consisting of Avaya Aura Communication Manager version 5 2 1 Avaya Aura Session Manager version 5 2 1 1 Avaya Aura System Manager version 5 2 1 1 and an Acme Packet 4500 Net Net Session Director version 6 1 0 supporting SIP trunking was connected to the public network The enterprise site was configured to use a generally available SIP trunking solution provided by Metaswitch This allowed the enterprise site to use SIP trunking for calls to and from the PSTN The following features and functionality were covered during the SIP trunking interoperability compliance testing e Incoming calls to the enterprise site from the PSTN using the DID numbers assigned by Metaswitch Outgoing calls from the enterprise site to PSTN destinations via Metaswitch Calls using various analog digital H 323 and SIP endpoints supported by the Avaya IP telephony solution Various call types including local long distance and toll free calls Calls using various codecs Inbound and outbound fax calls DTMF tone transmission using RFC 2833 with successful voice mail navigation Telephone features such as hold transfer conference and call forwarding MJH Reviewed Solution amp Interoperability Test Lab Application Notes 4 of
95. t This may take some time to complete MJH Reviewed Solution amp Interoperability Test Lab Application Notes 63 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM Welcome admin Last Logged on at Apr 30 2010 3 20 PM AVAYA Avaya Aura System Manager 5 2 paa Management Telephony Asset Management Synchronize CM Data and Configure Options Communication System Management Telephony Synchronize CM Data Launch Element Cut Through Configuration Options Call Center Expand All Collapse All E Coverage Groups Synchronize CM Data Launch Element Cut Through Network Parameters 1 Item Refresh Filter Enable Stations E System Element Name FQDN IP Address Last Sync Time Sync Type Sync Status Location Software Version Templates Y CM8800_G430_FS 10 64 20 25 O 06 00 incremental Completed RO15x 02 1 016 4 Messaging Select All None 1 of 1 Selected User Management Monitoring O Initialize data for selected devices Network Routing Policy O Incremental Sync data for selected devices Security Applicati pplications Now Schedule Cancel Launch Element Cut Through Settings Session Manager Shortcuts Configuration Options Change Password Help for Configuration Options 1 Item Refresh Filter Enable Help for Synchronize CM Data System Configuration Type wake Bed he Beret ee dieta CM8800_G430_FS Consider UDP O Figure 62 Synchronize CM Data and Con
96. t devconnect avaya com MJH Reviewed Solution amp Interoperability Test Lab Application Notes 91 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM
97. t the ARS feature is enabled display system parameters customer options Page Sox iil OPTIONAL FEATURES Abbreviated Dialing Enhanced List n Audible Message Waiting n Access Security Gateway ASG n Authorization Codes n Analog Trunk Incoming Call ID n CAS Branch n A D Grp Sys List Dialing Start at 01 n CAS Main n Answer Supervision by Call Classifier n Change COR by FAC n ARS y Computer Telephony Adjunct Links y ARS AAR Partitioning y Cvg Of Calls Redirected Off net n ARS AAR Dialing without FAC y DCS Basic n ASAI Link Core Capabilities y DCS Call Coverage n ASAI Link Plus Capabilities y DCS with Rerouting n Async Transfer Mode ATM PNC n Async Transfer Mode ATM Trunking n Digital Loss Plan Modification n ATM WAN Spare Processor n DSi ISIE iat ATMS n DS1 Echo Cancellation n Attendant Vectoring n NOTE You must logoff amp login to effect the permission changes Figure 29 System Parameters Customer Options Form Page 3 3 On Page 4 of the System Parameters Customer Options form verify that the IP Trunks feature is enabled display system parameters customer options Page CY e ALL OPTIONAL FEATURES Emergency Access to Attendant y TERS Ua CONS AEV Enable dadmin Login y Enhanced Conferencing y SONES acusan Enhanced EC500 y ISDN SIP Network Call Redirection n Enterprise Survivable Server n ISDN BRI
98. t to be used e g 5060 or 5061 Check the Trusted box In the Protocol drop down menu select the protocol to be used Enter a description in the Notes field if desired not shown Click on the Commit button 10 Repeat steps 1 9 for each Entity Link ER OPNDY The following Entity Links were specified in the reference configuration Name SIP Entity 1 Protocol Port SIP Entity 2 Port SM 01_S8300_G450_AE_5061_TLS SM 01 TLS 5061 S8300_G450_AE 5061 SM 01_CM8800_FS_5060_TCP SM 01 TCP 5060 CM8800_G430_FS 5060 SM 01_Acme_Packet_5060_TCP SM 01 TCP 5060 Acme Packet 5060 Table 3 Entity Link Provisioning MJH Reviewed Solution amp Interoperability Test Lab Application Notes 51 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM AVAYA Avaya Aura System Manager 5 2 Welcome admin Last Logged on at Apr 28 2010 2 43 PM Help Log off Home Network Routing Policy Entity Links gt Asset Management Entity Links Commit gt Communication System Management gt User Management Monitoring 1 Item Refresh Filter Enable Name SIP Entity 1 Protocol Port SIP Entity 2 Port Trusted Notes Network Routing Policy Adaptations 5M 01_58300_G450 smor TLS 5061 ss300_G450_AE 5061 z Ho Dial Patterns Entity Links Locations Input Required Regular Expressions Routing Policies
99. teway Model Avaya CM SM Category STP ModelName Avaya CM SM ControlProtocol SIP DefaultModel False SupportedHighBandwidthMediaFormats G 711 u law G 711 A law SupportedLowBandwidthMediaFormats G 729 AB PreferredLowBandwidthMediaFormats G 729 AB AdvancedVoiceCodecsPermitted VideoCodecsPermitted PacketizationInterval Any codecs Any codecs 0 SilenceSuppressionAllowed False MaximumSimultaneousTransactionsOutstanding 100 DigitOverhangTime 250 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 79 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM FixBitsMGCPMeGaCoSIP DynamicFixBitsMGCPMeGaCoSIP FixBitsSIP Cannot be hub Simple contexts Cannot control endpoint connectivity Cannot move contexts Connections always receive Cannot report detection of call type discrimination tones T 38 supported Supports SDP connectivity requests Supports receiving INVITEs with no SDP Supports receiving SIP Reason header over tandem trunk calls FixBitsSIP2 ReferenceCount 1 UpToDateCount 1 ExportHeading Export StatusHeading Status RequestedStatus Enabled end MediaGatewayModel MJH Reviewed Solution amp Interoperability Test Lab Application Notes 80 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 8 2 Configured SIP Binding The connection to the Avaya solution is modeled as a configured SIP binding During compliance
100. th field enter 1 3 In the Call Type field enter fac change dialplan analysis Page al ie IZ DIAL PLAN ANALYSIS TABLE Location all Percent Full 2 Dialed Towal Cali Dialed toral Call Dialed toral adil String Length Type String Length Type String Length Type 1 3 dac 2 5 ext 4 4 ext 5 5 ext 7 5 ext 8 5 ext 9 1 fac i 3 fac Figure 5 Change Dialplan Analysis Form Page 1 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 12 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 4 1 2 Uniform Dialplan The uniform dial plan is modified with the change uniform dialplan command 1 On Page 1 of the form configure the following e Local extensions SIP stations 1 In the Matching Pattern field enter 531 2 Inthe Len field enter 5 3 Inthe Del field enter 0 4 Inthe Net field enter aar 5 Inthe Conv field enter n change uniform dialplan 0 Page il O 2 UNIFORM DIAL PLAN TABLE Percent Full 0 Matching Insert Node Pattern Len Del Digits Net Conv Num 531 5 0 aar n Figure 6 Change Uniform Dialplan Form Page 1 4 1 3 Node Names In the IP Node Names form verify or assign the node names to be used in this configuration using the change node names ip command e SM2 and 10 64 20 31 are the Name and IP Address of Avaya Aura Session Manager e procr and 10 64 21 41 are the Name and IP Address of the processor for Avaya Aura Comm
101. tive member number of a connected trunk Verify on Page 1 that the Service State is in service active On Page 2 verify that the IP addresses of the procr or C LAN and Avaya Aura Session Manager are shown in the Signaling section In addition the Audio section shows the G 711 codec and the IP address of the Avaya H 323 endpoint and the Acme Packet SBC The Audio Connection Type displays ip direct indicating direct media between the two endpoints status trunk 9 7 Page iL Ole 3 TRUNK STATUS Trunk Group Member 0009 007 Service State in service active Port T00340 Maintenance Busy no Signaling Group ID 9 IGAR Connection no Connected Ports S00027 Figure 69 Status Trunk Active Call Page 1 status trunk 9 7 Page 73 jie 3 CALL CONTROL SIGNALING Near end Signaling Loc 01A0017 Signaling IP Address Port Near end 10 64 21 41 5061 Far end 10 64 20 31 5061 H 245 Near bls Aas ewes H 245 Signaling Loc H 245 Tunneled in 0 931 no Audio Connection Type ip direct Authentication Type None Near end Audio Loc Codec Type G 711MU Audio IP Address RORE Near end 10 64 21 71 8 MS Far end 10 64 20 106 50248 Video Near Video Far Video Port Video Near end Codec Video Far end Codec Figure 70 Status Trunk Active Call Page 2 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 86 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metas
102. unication Manager change node names ip IP NODE NAMES Name IP Address CM B1 192745710755 CM B2 OZ a O 5 5 7 SES A ILO SAA al SM1 10 64 40 42 SM2 10 64 20 31 default 0 00 0 procr 10 64 21 41 Figure 7 IP Node Names Form MJH Reviewed Solution amp Interoperability Test Lab Application Notes 13 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 4 1 4 IP Network Regions One network region was defined in the reference configuration The SIP trunk ip network regions are defined in the SIP Signaling Group form with the Far end Region parameter see Section 4 1 6 Network region assignments for ip interfaces may be verified with the list ip interface all command list ip interface all IP INTERFACES Net ON Type Slot Code Sfx Node Name Mask Gateway Node Rgn VLAN IP Address y PROCR 10 64 21 41 24 10 64 21 1 1 Figure 8 IP Interface IP Network Region Assignments The network region for an ip interface may be modified with the change ip interface x command where x is the board location or procr change ip interface procr Page iL OE il IP INTERFACES Type PROCR Target socket load 1700 Enable Interface y Allow H 323 Endpoints y Allow H 248 Gateways y Network Region 1 Gatekeeper Priority 5 IPV4 PARAMETERS Node Name procr Subnet Mask 24 Figure 9 IP Interface IP Network Region Assignment
103. uration is described in these Application Notes The Acme Packet SBC was configured using the Acme Packet CLI via a serial console port connection An IP remote connection to a management port is also supported The following are the generic steps for configuring various elements 1 Log in with the appropriate credentials 2 Enable the Superuser mode by entering enable command and the appropriate password prompt will end with 3 In Superuser mode type configure terminal and press lt ENTER gt The prompt will change to configure Type the name of the element that will be configured e g session router Type the name of the sub element if any e g session agent Type the name of the parameter followed by its value e g ip address Type done Type exit to return to the previous menu Repeat steps 4 8 to configure all the elements When finished exit from the configuration mode by typing exit until returned to the Superuser prompt OAS SOS MJH Reviewed Solution amp Interoperability Test Lab Application Notes 69 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 10 Type save configuration to save the configuration 11 Type activate configuration to activate the configuration Once the provisioning is complete the configuration may be verified by entering the show running config command 7 3 1 Acme Packet Management Initial Acme Packet provisioning is performed via the consol
104. utbound Calls Verify that calls placed to a PSTN telephone are properly routed via the SIP trunk Verify that the talk path exists in both directions and that calls remain stable and disconnect properly e Inbound DTMF Digit Navigation Verify inbound DID calls can properly navigate voice mail menus 2 Outbound DTMF Digit Navigation Verify outbound calls can properly navigate a voice mail or interactive response system reached via a PSTN number Interoperability testing of the reference configuration was completed with successful results The following observations were noted 1 The Metaswitch test lab did not support x11 calls e g 411 911 international etc 2 Due to limitations of the Metaswitch test lab configuration the caller id did not always display the proper calling party number for calls to and from the PSTN rather an administered 10 digit number was display 10 Verification Steps This Section provides the verification steps that may be performed to verify basic operation of the Avaya Aura SIP trunk solution with Metaswitch MJH Reviewed Solution amp Interoperability Test Lab Application Notes 84 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 10 1 Verify Avaya Aura Communication Manager 5 2 Verify the status of the SIP trunk group by using the status trunk n command where n is the administered trunk group number Verify that all trunks are in the in serv
105. uth Code n Signaling Group 8 Number of Members 10 Figure 14 Internal calls Trunk Group 8 Page 1 b On Page 3 of the Trunk Group form e Set the Numbering Format field to public This field specifies the format of the calling party number sent to the far end change trunk group 8 Page S Or Bil TRUNK FEATURES ACA Assignment n Measured none Maintenance Tests y Numbering Format public UUI Treatment service provider Replace Restricted Numbers n Replace Unavailable Numbers n Show ANSWERED BY on Display y Figure 15 Internal calls Trunk Group 8 Page 3 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 18 0f 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 4 1 6 2 Configure SIP Trunk for off network calls The SIP trunk for off network calls is configured in the same fashion as the internal call SIP Trunk except that the Far end Domain is set to blank 1 Using the change signaling group 9 command configure the Signaling Group as follows e Set the Group Type field to sip e Set the Transport Method field to tls Note This specifies the transport method used between Avaya Aura Communication Manager and Avaya Aura Session Manager not the transport method used to the Metaswitch network e Specify the procr or C LAN used for SIP signaling node name procr and the Avaya Aura Session Manager nod
106. vert the outbound call Avaya Aura Session Manager to Acme request URI domain from the Avaya CPE domain used by Avaya Aura Communication Manager to the Metaswitch domain f From the Locations drop down menu select 10 64 20 21 0 g Select the appropriate time zone h Accept the other default values 2 Sip Link Monitoring section a Select the desired option 3 Port section a When defining a SIP Entity for Avaya Aura Session Manager itself and SM is selected from the Type drop down menu an additional section called Ports will appear Click Add then edit the fields in the resulting new row e Enter the Port number on which the system listens for SIP requests e Select the transport Protocol to be used e Select the SIP Domain configured in Section 6 3 1 for the Default Domain b Repeat step 3 for each Port to be configured 4 Click on Commit 5 Repeat these steps for each SIP Entity MJH Reviewed Solution amp Interoperability Test Lab Application Notes 49 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM AVAYA Home Network Routing Policy Asset Management Communication System Management User Management Monitoring Network Routing Policy Adaptations Dial Patterns Entity Links Locations Regular Expressions Routing Policies SIP Domains SIP Entities Time Ranges Personal Settings Security Applications Settings gt Session Manager Shortcuts Ch
107. witch_SM 10 2 Verify Avaya Aura Session Manager Monitoring of Avaya Aura Session Manager is performed via Avaya Aura System Manager 10 2 1 Verify SIP Entity Link Status Expand the Session Manager menu and click SIP Monitoring Verify that none of the links to the defined SIP entities are down as indicated by 0 4 in the figure below indicating that they are all reachable for call routing Welcome admin Last Logged on at May 03 2010 12 25 PM AVAYA Avaya Aura System Manager 5 2 Help Log off Hoi n Manag SIP Entity Monitoring ba Asset Management SIP Entity Link Monitoring Status Summary Communication System Management gt User Management This page provides a summary of Session Manager SIP entity link monitoring status Entity Link Status for All Session Manager Instances gt Monitoring Network Routing Policy Security Session Manager Entity Links Entity Links Partially SIP Entities Monitoring Not _ SIP Entities Not Down Total Down Started Monitored Applications a ee eT SM 01 0 4 o o o gt Settings y Session Manager All Monitored SIP Entities Session Manager Administration Network Configuration Device and Location 4 Items Filter Enable Configuration SIP Entity Name Acme Packet Application Configuration System Status System State AE CLAN Administration CM8800 G430 FS SIP Entity Monitoring i Managed Bandwidth 8300 G450 AE Usag
108. y on the phone see Section 4 1 10 e Select an empty button assignment and enter extnd call This button will allow a user of this station to extend an active call to another phone number mapped to this extension see Section 4 1 10 change station 74567 Page 4 of 5 STATION SITE DATA Room Headset n Jack Speaker n Cable Mounting d Floor Cord Length 0 Building Sst C Oso ta ABBREVIATED DIALING Listl ESER List3 BUTTON ASSIGNMENTS 1 call appr 4 ec500 Timer n 2 call appr extnd call 3 call appr anu voice mail Number Figure 26 Avaya H 323 IP Phone Page 4 MJH Reviewed Solution amp Interoperability Test Lab Application Notes 26 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM 4 1 10 EC500 Provisioning The Avaya Aura Communication Manager EC500 feature was used to during compliance testing EC500 provides call coverage for an Avaya Aura Communication Manager station to a second destination endpoint Typically this endpoint is a cell phone When EC500 is enabled on the Avaya Aura Communication Manager station by pressing the EC500 button any inbound call to that station will generate a new outbound call from Avaya Aura Communication Manager to the provisioned EC500 destination endpoint Similarly if there is an existing active call at the station pressing the extnd call button will generate a new outbound call from Avaya Aura Communicat
109. ya Aura Session Manager not the transport method used to the Metaswitch network Set the IMS Enabled field to y Specify the procr or C LAN used for SIP signaling node name procr and the Avaya Aura Session Manager node name SMO01 as the two ends of the signaling group in the Near end Node Name and Far end Node Name fields respectively These field values are taken from the IP Node Names form shown in Section 5 1 3 Specify 5060 in the Near End and Far end Listen Port fields Enter the value 1 into the Far end Network Region field This value is for the IP Network Region defined in Section 5 1 4 1 Leave the Far end Domain field blank This permits inbound calls from any foreign domain e g the Metaswitch network The Direct IP IP Audio Connections field should be set to y to allow RTP voice paths to be established directly between IP telephones and the Metaswitch network MJH Reviewed Solution amp Interoperability Test Lab Application Notes 37 of 91 RRR xx xx xxxx 2010 Avaya Inc All Rights Reserved Metaswitch_SM e The DTMF over IP field should remain set to the default value of rtp payload This value enables Avaya Aura Communication Manager to send DTMF tones using RFC 2833 e The default values for the other fields may be used change signaling group 2 Page I OE 1 SIGNALING GROUP Group Number 2 Group Type sip Transport Method tcp IMS Enabled y Near end Node Name procr Far end Node Name

Avaya Aura - Config Guide

Contents

Download Pdf Manuals

Related Search

Related Contents