Home

Avaya Configuring Aura Messaging 6.1 as a Voice Messaging Solution User's Manual

1. I Originating Location Name 1 Oriainatmg Roung Poley ponk 2a poney Boitmgoley Beate Belleville Ont Ca Pelevile Tiy SM TO AAM o DevAAM_SM Routesfromistt PM Reviewed Solution amp Interoperability Test Lab Application Notes 30 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 9 Configure Avaya Aura Messaging Messaging was configured for SIP communication with Session Manager and also to add Avaya BCM Communication Manager Subscribers The procedures include the following areas e Administer Sites Administer Telephony Integration Administer Dial Rules Administer Class of Service to enable Message Waiting Administer Subscribers See references in Section 12 for standard installation and configuration information General knowledge of the configuration tools and interfaces is assumed 9 1 Administer Sites A Messaging access number and a Messaging Auto Attendant number needs to be defined Log into the Avaya Aura Messaging System Management Interface SMI and go to Administration gt Messaging gt Messaging System Storage gt Sites In the right panel fill in the following Under Main Properties e Messaging access number internal Enter a Messaging Pilot number AVAYA Administration Messaging Administration User Management Class of Service Sites Topology Storage Destinations Site Default System Policies Enhanced List Management Add New Delete
2. Active Sets Configuration Line Access Capabilities and Preferences Restrictions er DN Model Name Port Pub OLI Priv OLI Fwd No nswer Fwd Delay Fwd Busy Administrator Access 22232 j 50 22232 22232 22232 39990 2 39990 Resources 22233 2 39990 Telephony 2223 Es Global Settings 22235 2 39990 Sets 22236 2 39990 Templates 22237 2 39990 o 22441 22441 N A Active Applicatior 22268 9134400061 22268 j Inactive DNs 22263 9134400150 22263 96139675279 4 All DNs 22221 j 22301 4 22301 D Lines 22222 OE 2004 2007 2050 22222 0249 N A Active Physical Li ae Target Lines Inactive Lines Details for DN 22234 All Lines salad Line Assignment Line Pool Access Answer DNs MeetMe Conferencing Scheduled Services g O Dialing Plan Assigned Lines General Line Appearance Type Appearances Caller ID Set VmsgSet Priv Received Pub Received DNs 362 Appr amp Ring 1 22234 22234 Public Network Private Network Line Pools Pantina For Outgoing Call Select tab Line Pool Access tab click Add button to add BlocB Click OK from the Add Line Pool pop up to complete as shown below Task Navigation Panel _____________ Active Sets Configuration Line Access Capabilities and Preferences Restrictions bagel DN Model N
3. Switch Trunks Total 120 Maximum 120 PM Reviewed Solution amp Interoperability Test Lab Application Notes 34 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 9 3 Configure Dial Rules Navigate to Administration Messaging gt Server Settings Application gt Dial Rules to configure the dial rules Set the Dial plan handling style Site definition based as shown below User Activity Log Configuration Dial Rules Reports Storage Users Info Mailboxes Remote Users Dial Plan Handling Uninitialized Mailboxes Login Failures Dial plan handling style Site definition based Locked Out Users Server Information System Status Storage Dial plan handling testing System Status Application Alarm Summary Voice Channels Application Advanced Rules Cache Statistics Application Server Settings Storage EEA Advanced Dial out rules Trusted Servers P Networked Servers Siaki ukia system Request Remote Update O custom IMAP SMTP Settings Storage General Options Mail Options IMAP SMTP Status Heip Apply Reset Page Telephony Settings Application Telephony Integration Server Settings Application Next select the Edit Dial Out Rules button to verify the appropriate parameters for outbound dialing from Avaya Aura Messaging were set above These dial rules help Avaya Aura Messaging send the correct number and combination of digits when originating
4. 1 23 Total Administered Members 23 Port Code Sfx Name Night Sig Grp 001V601 MM710 B 1 001V602 MM710 001V603 MM710 001V604 MM710 001V605 MM710 001V606 MM710 001V607 MM710 PRPHPPH 7 5 Administer Route Pattern Create a route pattern for the new ISDN trunk group to use for routing Use the change route pattern n command where n is an available route pattern Enter the following values for the specified fields and retain the default values for the remaining fields Submit these changes add route pattern 1 Pattern Number 5 Pattern Name BCM Qsig Route SCCAN n Secure SIP n Grp FRL NPA Pfx Hop Toll No Inserted No Mrk Lmt List Del Digits Dgts 1 1 0 23 33 4 5 6 BCC VALUE TSC CA TSC ITC BCIE Service Featur Oo1l2M4W Request 1 yy yyyn_ y as needed rest Page 1 of 3 DCS IXC OSIG Intw n user n user n user n user n user n user PARM No Numbering LAR Dgts Format Subaddre PM Reviewed Solution amp Interoperability Test Lab Application Notes 22 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 7 6 Administer Public Unknown Numbering Use the change public unknown numbering 0 command to define the calling party number to be sent to Avaya Business Communication Manager Add an entry for the trunk group defined in Section 7 2 In the example shown below all calls originating from a 6 digit extension beginning with 7 a
5. General section e Enter a unique pattern in the Pattern field e g 399 e Inthe Min field enter the minimum number of digits e g 5 e Inthe Max field enter the maximum number of digits e g 5 e Inthe SIP Domain field drop down menu select the domain that will be contained in the Request URI received by Session Manager from BCM and AAM e Enter a description in the Notes field if desired Originating Locations and Routing Policies section e Click on the Add button and a window will open not shown e Click on the boxes for the appropriate Originating Locations and Routing Policies that pertain to this Dial Pattern o Location All o Routing Policies SM_to_AAM o Click on the Select button and return to the Dial Pattern window Click the Commit button to save the new definition The following screen shows the dial pattern used for Messaging during the compliance test Repeat the same for Avaya BCM with Pattern 222 Routing M Home Elements Routing Dial Patterns Dial Pattern Details Help Domains i p Dial Pattern Details Locations Adaptations p General SIP Entities Pattern 3999 Entity Links Min Time Ranges Min 5 Routing Policies Max 5 Dial Patterns Emergency Call R lar E i r Ue SIP Domain bywdev com v Defaults Notes Dial pattern to call AAM Originating Locations and Routing Policies 1 Item Refresh Filter Enable Routing
6. System Mailboxes System Ports and Access User Activity Log Configuration Main Properties Users Name Default Info Mailboxes Remote Users m z Uninitialized Mailboxes Messaging access number external 39991 Login Failures Locked Out Users Messaging access number internal 39990 PM Reviewed Solution amp Interoperability Test Lab Application Notes 31 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 Scroll down to the Site Internal Dial Plan section Under Site Internal Dial Plan e Short Extension Length e Short Mailbox Length Enter the number of digits in extensions Enter the number of digits in mailbox numbers AVAYA Administration Messaging Messaging System Storage User Management Class of Service Sites Topology Storage Destinations System Policies Enhanced List Management System Mailboxes System Ports and Access User Activity Log Configuration Reports Storage Users Info Mailboxes Remote Users Uninitialized Mailboxes Login Failures Pacleed Out Honre Administration Subscriber number length within this site s national destination code Outside line prefix Site Internal Dial Plan Describe the internal dial plan applicable to this site Short extension length 5 Short mailbox length fs Extension style for telephony integration Short z Example nnnnn Site prefix Choose One X National mailbox number conventi
7. e Select the SIP Entity that will be the destination for this call not shown e Click the Select button and return to the Routing Policy Details form Time of Day section e Leave default values Click Commit to save Routing Policy definition The following screen shows the Routing Policy used for the compliance test Renting i Home Elements Routing Routing Policies Routing Policy Details Domains EA Locations Adaptations General SIP Entities Name RouteToBCM450 Entity Links Disabled Time Ranges Notes RouteTOBCM4s0 Routing Policies Dial Patterns SIP Entity as Destination Defaults Name FQDN or IP Address Regular Expressions Repeat the steps to define routing policies to others Entities PM Reviewed Solution amp Interoperability Test Lab Application Notes 29 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 8 7 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 In the compliance test the following dial patterns are defined from Session Manager e 222xx SIP endpoints in BCM e 39990 Avaya Aura Messaging Pilot Number To add a Dial Pattern select Routing gt Dial Patterns and click on the New button not shown on the right During the compliance test 5 digit dial plan was utilized Provide the following information
8. Lines 018 Lredies Tagetlres 019 Lrs019 22231 inactive Lines 020 Lined20 02 Lined Copy J Pasw Rerurber j Priv Received Distinct Ring Nore Nore None None Nore Nore Nore None None None Nore None Detaik for Line 009 Preferences Restrictions Oistrct rings nuse Pattern 2 6 1 5 Assign a DN 22234 to an available target line Line 362 See Section 5 4 for detail procedure Administer Telephony Target Lines 6 1 6 User Telephone Sets Configuration for Incoming Outgoing Call This section show how to configure telephone sets to specific physical line for incoming outgoing calls to from a digital set Select Telephony gt Sets gt Active Sets In the Line Access select the available digital set which has the Model is T7316 M7310 Assign Priv OLI 22234 This will allow the delivery of the Calling Line Identification Display For incoming call Assign the line that configured in Section 6 1 5 o this phone by click on the Add button in Line Assignment tab Enter line number in this example 362 and click OK Modify the detail information of the line parameters as values highlighted in red boxes in the below figure e Caller ID Set checked Vmsg Set checked Priv Received 22234 Pub Received 22234 PM Reviewed Solution amp Interoperability Test Lab Application Notes SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved 15 of 47 AAM61SM61BCM60 Task Navigation Panel
9. Reserved AAM61SM61BCM60 9 2 Administer Telephony Integration A SIP trunk needs to be configured from Messaging to Session Manager Log into the Messaging System Management Interface SMI and go to Administration gt Messaging gt Telephony Settings Application gt Telephony Integration In the right panel fill in the following Under Basic Configuration e Extension Length Enter the length of extensions e Switch Integration Type SIP Under SIP Specific Configuration Transport Method TCP Connection 1 Enter the Session Manager signaling IP address and TCP port number Messaging Address Enter the Messaging IP address and TCP port number SIP Domain Enter the Messaging and Session Manager domain names Click Save to save changes Messaging System Storage J elephony integration User Management e The Telephony Integration page is used for administration of the switch link parameters of the messagng system BASIC CONFIGURATION System Poloes Enhan cod Ust Maenagemert Switeh Number System Maiboxes System Ports and Access Extension Length Switch Integration Type IP Address Version SIP SPECIFIC CONFIGURATION Transport Method Far end Connections nnels Appecabon Cache Stanstcs Appihcavon Connection 1 tp 135 10 Port 060 Messaging Address 1p 10 32 Port 5060 SIP Domain Messaging bywdev com Switch bywdev com Messaging Ports Call Answer Ports 100 Maximum 100 Transfer Ports 20
10. Routes Destination Codes Second Dial Tone t Welcome Routes HO System HO Administrator Access HO Resources HO Telephony H O Global Settings we ppe amp a e pa oo National Loops Scheduled Services S O Dialing Plan General DNs Public Network Private Network Line Pools Routing Route External Number Use Pool DN Type Service Type Service IC ooo A N A N A N A 6 1 3 Administer Destination Codes To assign Destination Codes to dial to PSTN via PRI Perform similar step as shown in section 5 3 2 for with the following information e Destination Code 4521 Extension on Avaya Communication manager is 52xxx Digit 4 to let Avaya BCM route the call through route 002 Normal Route 002 Absorbed Length 1 Drop the first digit 4 6 1 4 Administer Telephony Lines Assign the pool to telephone line by navigate to Telephony gt Lines gt Active Physical Lines Double click on a selected line under the Line Type choose Pool BlocB in this example as shown below PM Reviewed Solution amp Interoperability Test Lab Application Notes 14 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 Vekome Configuration Lire Truk Type Name CorrolSet Line Type Prime Set Pub Received rece rs 0 to AGmnet ator Access O11 at osoces 012 redi2 Teleghony 01 reois D Gkbal Settings ol redid D Ses 0 n015 Lre 016 re0i e 01 reoi7 Active VoIP
11. a call to Communication Manager whether the call is destined for another extension or ultimately expected to be routed to the PSTN For the sample configuration 7 digit extensions were used on Avaya Communication Manager so any time Avaya Aura Messaging originates a call to an extension it should send the 7 digit number and not attempt to insert or delete any digits Scroll down to the section titled Dial out Test Numbers Enter in a number in the appropriate section and select the Test button to see how Avaya Aura Messaging would dial that number As shown below the number 7785002 is treated as an internal number and is dialed intact whereas the test number 408 555 7086 is treated as a long distance national number which requires a 9 prefixed as an access code PM Reviewed Solution amp Interoperability Test Lab Application Notes 35 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 Dial Out Test Numbers S85 a aaae Add more phone numbers to test for your specific configuration Extension example 2001 7785002 212 555 7086 Local number example 555 7086 333 3030 Long distance number example 408 555 7086 4 Output Phone Number 2001 7785002 555 7086 arena 5557086 po 8833030 INTERNAL 3333030 408 555 7086 LONGDISTANCE 914085557086 PM Reviewed Solution amp Interoperability Test Lab Application Notes 36 of 47 SPOC 02 26 2013 2013 Avaya
12. e Administer DS1 circuit pack Administer trunk group Administer signaling group Administer trunk group members Administer route pattern Administer public unknown numbering Administer uniform dial plan Administer AAR analysis PM Reviewed Solution amp Interoperability Test Lab Application Notes 17 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 7 1 Administer DS1 circuit pack Log into the System Access Terminal SAT and administer a DS1 circuit pack to be used for Connectivity to BCM Use the add ds1 001v6 command Note that the actual slot number may vary In this case 001v6 is used as the slot number Enter the following values for the specified fields and retain the default values for the remaining fields Submit these changes Note The Interface field must be complementary on both switches For the sample configuration Avaya Communication Manager is administered as the network master peer master and Avaya BCM is administered as the user slave add dsl 001v 6 Page 1 of 2 DS1 CIRCUIT PACK Location 001V6 Name To BCM Bit Rate 1 544 Line Coding b8zs Line Compensation 1 Framing Mode esf Signaling Mode isdn pri Connect pbx Interface peer master TN C7 Long Timers n Peer Protocol Interworking Message PROGress Interface Companding mulaw Idle Code 11111111 DCP Analog Bearer Capability 3 1kHz T303 Timer sec 4 Disable Restarts n Slip Detection n Near
13. 0 217 Templates Active Sets pes pee Active Application Dr Local access code 6 Virtual Private Network ID J 1 s eNe R National access code Zone 1D 0 Is L Lines Special access code ETSI Active Physical Lines Network ICCL ote Active VoIP Lines TRO F Network Diversion J Target Lines p MCID Inactive Lines TAT V AllLines Loops Scheduled Services 2 Dialing Plan General DNs Public Networ eee Line Pools Routing Ring Groups H O Call Security Hospitality Hunt Groups Call Detail Recording Call Recording 5 4 Target Lines Configuration Done L 0 L__mi1 L__m 7 L__W 2 V Include ACKed alarms This section describes how to configure target lines which will be assigned to telephones that will be used as endpoints connected to the BCM PM Reviewed Solution amp Interoperability Test Lab Application Notes 9 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 5 4 1 Configure a target line to a selected set Navigate to Configuration gt Telephony gt Lines gt Target Lines In the Target Lines screen select a Line and enter DN to selected Line For example in the figure shown below e Line 4 3 has been selected e DN 22235 has been assigned by clicking on the Add button under the Assigned DNs tab Note Add unique set DN to one Target line Require one line assignment for every telephone device in the s
14. 43 IP 127 0 0 1 msgs 1 05 01 2012 8 50 inbox dsel id 6f778 port 55143 IP 127 0 0 1 msgs 1 05 01 2012 8 50 status changed from new to old for message received 5 01 12 at 8 50 10 2 2 Test calls can be made from Avaya Aura Messaging to phones that are configured with mailboxes To perform this test select Administration gt Messaging In the left panel under Diagnostics select Diagnostics Application In the right panel fill in the following e Select the test s to run Select Call out from the drop down menu e Telephone number Enter the number to call Click on Run Tests to start the test The phone will ring and when answered a test message is played The Results section of the page will update indicating that the call was ok as shown below PM Reviewed Solution amp Interoperability Test Lab Application Notes 43 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 Diagnostics Application Selection amp Configuration Select the test s to run Call out This calls out to the specified extension When the phone is picked up a test greeting should be heard Configuration of Call Out Test elephone number 22235 Port number optional Run Tests l Reset Page Results Test Call out Time 4 09 01 PM Usage testCALL extensionNumber portNumber Checking Call out calling 22237 OK Line 100 irapii00 Got dial t
15. AVAYA Avaya Solution amp Interoperability Test Lab Configuring Avaya Aura Messaging 6 1 as a Voice Messaging Solution for Avaya Business Communication Manager 450 Release 6 0 with SIP trunking through Avaya Aura Session Manager 6 1 Issue 1 0 Abstract These Application Notes describe a sample configuration of Avaya Aura Messaging 6 1 as a voice mail solution for Avaya Business Communication Manager 450 6 0 In this configuration Avaya Aura Messaging and Business Communication Manager 450 are connected to Avaya Aura Session Manager R6 1 over SIP trunks Avaya Aura Session Manager provides SIP proxy routing functionality routing SIP sessions across a TCP IP network with centralized routing policies Avaya Aura Messaging supports Business Communication Manager 450 endpoints for voice messaging features such as greeting menu user mailbox services and transfer functionalities These Application Notes provide information for the setup configuration and verification of the call flows tested for this solution PM Reviewed Solution amp Interoperability Test Lab Application Notes 1 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 1 Introduction These Application Notes describe a sample configuration of Avaya Aura Messaging 6 1 as a voice mail solution for Avaya Business Communication Manager BCM 450 6 0 In this configuration Avaya Aura Messaging and Avaya BCM are connected to Avaya Aur
16. Configuration ine Trunk Type Name Control Set Line Type Prime Set Pub Received Priv Received Welcome ar line Line361 22231 Public 22231 22441 cy System e Line362 22231 Public 22231 22234 22234 9 Administrator Acces Line363 22231 Public 22231 22235 S Resources ne Line364 Public 22221 Telephony arget line e365 2223 Public 2223 9 Global Settings i a e Line366 Public 22334 H O Sets l a n Line367 Public Lines a ne Line368 Public Active Physic i Line369 Public Active VoIP Lir e Line370 Public e et Lines E Line371 Public Inactive Lines e Line372 Public All Lines l Target line Line373 Public Loops r Scheduled Servic f Dialing Plan 1m Ring Groups Details for Line 365 O Call Security Hospitality Hunt Groups Paste __Renumber __ Preferences Assigned DNs call Recording nger ousytne O Call Recording Aociriposn If Busy Busy tone s Data Services Distinct rings in use Pattrn2 O O 00 Voice message center oOo A EE en Redirect to v PM Reviewed Solution amp Interoperability Test Lab Application Notes 10 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 5 5 Active Sets Configuration This section describes the steps to configure the sets that have been assigned to a line as explained in Section 5 4 5 5 1 Configure the Active sets Select Configuration gt
17. Inc All Rights Reserved AAM61SM61BCM60 9 4 Configure Class of Service Verify Messaging Waiting is enabled for all subscribers Use Administration gt Messaging gt Messaging System Storage gt Class of Service Select Standard from the Class of Service drop down menu Under General section enter the following value and use default values for remaining fields e Set Message Waiting Indicator MWD on user s desk phone checked e Dial out privilege Local Under Greetings section enter for Two Greetings different greetings for busy and noanswer field to allow subscribers to record different personal greetings for busy and no answer scenarios Click Save not shown to save changes The following screen shows the settings defined for the Standard Class of Service in the test configuration Class of Service Class of Service Standard v Add New Delete General Name Standard ID 0 Required seat license Mainstream VALUE_MSG_SEAT_MAINSTREAM Telephone User Interface Aria xj User can send to system distribution lists ELAs Fax support None Dial out privilege Local M User can use Reach Me M Allow voice recognition for addressing user can select recipients by saying their name IMAP4 POP3 access Full for Avaya Message Store users M Set Message Waiting Indicator MWI on user s desk phone oO Enable password aging oO User can send system broadcast messages PM
18. MI and go to Administration gt Messaging In the left panel under Logs select User Activity In the right panel fill in the following Under User Activity Log e Mailbox Number Enter the BCM extension that received the voicemail e Start Date Enter an appropriate start date and time e End Date Enter an appropriate end date and time Click Display button and verify that a listing of the detailed activities is displayed into the bottom portion of the right hand pane Verify that there is an entry showing the message left by a subscriber in this case 22234 Also verify that there is an entry showing the message being retrieved PM Reviewed Solution amp Interoperability Test Lab Application Notes 42 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 User Activity Log The User Activity Log page allows the selection of the Mailbox and Start and End times to display the activity log Mailbox Number 22234 Start Date april a 30 2012 M Time 09 13 x End Date may v ji 2012 Time o9 v 13 Name Bon Ba Mailbox Number 22234 Date Time Activity Description 05 01 2012 8 50 received VM message from 22232 new v 1 f 0 e 0 dsn 0 un 0 o 0 d 0 x 0 05 01 2012 8 50 inbox sel id 6f778 port 55143 IP 127 0 0 1 msgs 1 05 01 2012 8 50 inbox dsel id 6f778 port 55143 IP 127 0 0 1 msgs 1 05 01 2012 8 50 inbox sel id 6f778 port 551
19. None N A N A N A N A N A N A N A B IP Trunks Dial Up Interfaces Details for Module Main MBM 3 DTM PRI t Hunt Groups Call Detail Recording t Call Recording Nata Servire 9 Telephony B Global Settings cmm HO Sets Trunk Module Parameters Call by Call Service Selection Trunk Port Details Provision Lines F pee Trunk type PRI Send name display W T1 Parameters Scheduled Services Protocol NI 2 CO fail TIA 5474 p moore Plan NSF extension None Interface levels f ing Groups gt Ea P Call Security B channel selection Descending Sequential Framing f Hospitality Clock source Internal Line coding Internal CSU CSU line build 0 dB v PM Reviewed SPOC 02 26 2013 13 of 47 AAM61SM61BCM60 Solution amp Interoperability Test Lab Application Notes 2013 Avaya Inc All Rights Reserved 6 1 2 Routing Settings This section describes how to configure the dialing plan routes and pool that will be used by the Avaya BCM to connect to PSTN Navigate to Telephony gt Dialing Plan gt Routing In Routes tab to add a new route to PSTN by click on the Add button Enter the route number 002 and click OK when Done Double click on new created Route and assign value to the route as below other leave as default e Use Pool BlocB e DN Type Private e Service Type Tie Dialing Plan Routing Configuration
20. Reviewed Solution amp Interoperability Test Lab Application Notes 37 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 9 5 Administer Subscribers Log into the Messaging System Management Interface SMI and go to Administration gt Messaging In the left panel under Messaging System Storage select User Management In the right panel fill in the following e First Name Last Name Display Name ASCII name Site Mailbox Number Internal identifier Numeric address Extension Administration Messaging Messaging System Storage Class of Service Sites Topology Storage Destinations System Policies Enhanced List Management System Mailboxes System Ports and Access User Activity Log Configuration Reports Storage Users Info Mailboxes Remote Users Uninitialized Mailboxes Login Failures Locked Out Users Server Information System Status Storage System Status Application Alarm Summary Voice Channels Application Cache Statistics Application Server Settings Storage External Hosts Trusted Servers Networked Servers Request Remote Update IMAP SMTP Settings Storage General Options Mail Options IMAP SMTP Status Telephony Settings Application Telephony Integration PM Reviewed SPOC 02 26 2013 Enter first name Enter last name Enter display name Enter the ASCII name Enter site defined in Section 9 1 Enter desired mailbox number i e 22235 Ente
21. Telephony gt Sets gt Active Sets Example configuration for Line Access tab of selected active set e Select DN 22235 e Fwd No Answer 39990 e Fwd Busy 39990 Note 39990 is the pilot number of Avaya Messaging Example configuration for Line Assignment tab of selected active set e Vmsg Set checked so that voice mail can be accessed by the DN 22235 e Priv Received 22235 e Pub Received 22235 Task Navigation Panel Configuration Welcome H O System HE Administrator Acce H Resources 49 Telephony H O Global Settings EHO Sets Templates PT sctive Sots Active Applic Inactive DNs All DNs S O Lines Active Physic Active VoIP L Target Lines Inactive Lines All Lines Loops Scheduled Servi w Dialing Plan Ding Crone Active Sets Line Access Capabilities and Preferences Restrictions DN Name Port Pub OLI Priv OLI Fwd No Answer Fwd Delay Fwd Busy 22229 22229 1006 N A 22230 22230 1007 N A 22231 22231 22301 3 22232 0 22232 22232 22232 39990 4 39990 422233 22233 22233 22233 39990 4 39990 22234 22234 22234 39990 2 39990 22236 22236 22236 22237 Analog 22237 22237 22237 22254 1140E 2004 200 22254 0243 Copy Paste Renumber Details for DN 22235 Line Assignment Line Pool Access Answer DNs MeetMe Conferencing Assigned Lines Line Appearance Type Appr amp Ring Appearances Call
22. a Session Manager over SIP trunks Avaya Aura Session Manager provides SIP proxy routing functionality routing SIP sessions across a TCP IP network with centralized routing policies Avaya Aura Messaging provides unified communications features such as greeting menu user mailbox services and transfer functionalities Avaya Aura Communication Manager is setup as an emulated PSTN connected to Avaya BCM through T1 connection 2 Interoperability Testing and Test Result Interoperability was tested between Avaya Business Communication Manager and Avaya Aura Messaging with SIP trunking through Avaya Aura Session Manager 2 1 Interoperability Compliance Testing Interoperability testing was executed between a variety of Avaya telephones such as Digital UNIStim registered to Business Communication Manager Avaya SIP phones registered to Session Manager and Avaya H323 Digital phones registered to Communication Manager The focus was to verify call and messaging functionality between Communication Manager Business Communication Manager and Avaya Aura Messaging in a SIP network with trunking through Session Manager The following Avaya Aura Messaging capabilities were covered No Answer Personal Greetings Bypass Greetings Message Waiting Indication Reply Call Forwarding Multiple Call Forwarding Call Transfer Simultaneous Calls Personal Operator Personal Operator No Answer Auto Attendant Auto Attendant No Answe
23. ame Port Pub OLI Priv OLI Fwd No Answer Fwd Delay Fwd Busy Administrator Access 22232 22232 22232 39990 2 39990 Resources 22233 22233 22233 39990 2 39990 Telephony 22234 22234 l2 29990 Global Settings 22235 2223 39990 2 39990 Sets 22236 22236 22236 22236 39990 2 39990 Templates 22237 22237 22237 22237 39990 2 39990 o amase 22441 22441 22441 Active Applicatior 22268 22268 9134400061 22268 N A Inactive DNs 22263 22263 9134400150 22263 96139675279 4 All DNs 22221 0 22221 22301 4 22301 Lines 22222 050 22222 0249 N A Active VolP Lines Target Lines Inactive Lines Details for DN 22234 All Lines Loops Teen E r ine Pool Access S credid Saris Line Assignment Answer DNs MeetMe Conferencing Dialing Plan Line Pools General Line Pool DNs Public Network Private Network Line Pools Routing Ring Groups Call Security Hospitality PM Reviewed Solution amp Interoperability Test Lab Application Notes 16 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 7 Configure Avaya Aura Communication Manager as Emulated PSTN PRI Trunk Configuration This section focuses on configuring the T1 trunks on Avaya Communication Manager to serve as service provider to Avaya Business Communication Manager and provides a sample routing using Automatic Alternate Routing AAR The configuration procedures include the following areas
24. aya Inc All Rights Reserved AAM61SM61BCM60 8 2 Configure Locations Locations are used to identify logical and or physical locations where SIP Entities reside for purposes of bandwidth management or location based routing Navigate to Routing gt Locations and click on the New button not shown to create a new SIP endpoint location General section Enter the following values and use default values for remaining fields e Enter a descriptive Location name in the Name field e Enter a description in the Notes field if desired Location Pattern section Click Add and enter the following values e Enter the IP address information for the IP address Pattern e g 10 1 2 e Enter a description in the Notes field if desired Repeat steps in the Location Pattern section if the Location has multiple IP segments Modify the remaining values on the form if necessary otherwise retain the default values Click on the Commit button Repeat all the steps for each new Location The following screen shows the Locations page used during the compliance test Routing M Home Elements Routing Locations Location Details Domains Location Details Adaptations Call Admission Control has been set to ignore SDP All calls will be counted using the Default Audio Bandwidth SIP Entities See Session Manager gt Session Manager Administration gt Global Setting Entity Links General Time Ranges Name Belleville Ont Ca Rou
25. ber 2011 7 Using Avaya Aura Messaging 6 1 December 2011 8 Implementing Avaya Aura Messaging 6 1 CID 150976 October 2011 Avaya Business Communication Manager 450 9 Avaya Business Communication Manager 6 0 Planning and Engineering NN40170 200 10 Avaya Business Communication Manager 6 0 Configuration Telephony NN40170 502 Avaya Communication Manager 11 Avaya Aura Communication Manager Screen Reference Release 6 2 03 602878 Issue 3 0 February 2012 PM Reviewed Solution amp Interoperability Test Lab Application Notes 46 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 2013 Avaya Inc All Rights Reserved Avaya and the Avaya Logo are trademarks of Avaya Inc All trademarks identified by and T 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 Solution amp Interoperabi
26. describes how to configure the dialing plan routes and pool that will be used by the Avaya BCM to communicate with the Avaya Aura Messaging 5 3 1 Configure the routing Navigate to Configuration gt Telephony gt Dialing Plan gt Routing In Routes tab to add a new route by click on the Add button Enter the route number 001 and click OK when Done Double click on new created Route and assign value to the route as below e Use Pool BlocA e DN Type Private The rest of the values leave them as default Task Navigation Panel Dialing Plan Routing Configuration Routes Destination Codes Second Dial Tone IE gait Routes e ag Route External Number Use Pool DN Type Service Type 2 Lines 000 A N A N A Loops i i Scheduled Servi We Po erva kA 2 Dialing Plan 003 Bloc Public Unknown N A General DNs Public Netwo Private Netwi Line Pools Routing 5 3 2 Configure the destination code Navigate to Configuration gt Telephony gt Dialing Plan gt Routing In Destination Codes tab add a destination code as shown in figure below e Destination Code 399 The destination code 399 is chosen because the AAM pilot number used in the example is 39990 e Normal Route 001 e Absorbed Length 0 Task Navigation Panel Dialing Plan Routing ee eiie sola Routes Destination Codes Second Dial Tone E Sree Settings Dest
27. e Name field In the SIP Entity 1 drop down menu select the Session Manager SIP Entity created in Section 0 In the Protocol drop down menu select the protocol to be used e g UDP or TCP In the Port field enter the port to be used e g 5060 In the SIP Entity 2 drop down menu select an entity In the Port field enter the port to be used e g 5060 Check the Trusted box Enter a description in the Notes field if desired Click on the Commit button to save each Entity Link definition The following screen shows an Entity Links page between Session Manager and Messaging used during the compliance test Routing Home Elements Routing Entity Links Entity Links Domains Hep Entity Links Locations Adaptations SIP Entities 1 Item Refresh Filter Enable Time Ranges Name SIP Entity 1 Protocol Port SIP Entity 2 Port Trusted Notes Routing Policies DevASM_DevAaM_S DevASM v TCP 5060 Dev4aM_SM v 5060 v Dial Patterns Regular Expression Dial Patterns Defaults Input Required Repeat the steps to define Entity Links between Session Manager and Avaya BCM PM Reviewed Solution amp Interoperability Test Lab Application Notes 27 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 8 5 Time Ranges The Time Ranges form allows admission control criteria to be specified for Routing Policies In the reference c
28. end CSU Type other Echo Cancellation n 7 2 Administer Trunk Group Administer an ISDN trunk group to interface with Avaya BCM Use the add trunk group n command where n is an available trunk group number Enter the following values for the specified fields and retain the default values for the remaining fields add trunk group 1 Page 1 of 21 TRUNK GROUP Group Number 1 Group Type isdn CDR Reports y Group Name Tie Route to BCM COR 1 TN 1 TAC 100 Direction two way Outgoing Display n Carrier Medium PRI BRI Dial Access n Busy Threshold 255 Night Service Queue Length _0 Service Type tie Auth Code n TestCall ITC rest Far End Test Line No TestCall BCC 4 PM Reviewed Solution amp Interoperability Test Lab Application Notes 18 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 Navigate to Page 2 For the Supplementary Service Protocol field enter b for Q SIG For the Format field enter unk unk Retain the default values for the remaining fields add trunk group 1 Group Type isdn TRUNK PARAMETERS Page 2 of 21 Codeset to Send Display 6 Codeset to Send National IEs 6 Max Message Size to Send 260 Charge Advice none Supplementary Service Protocol r Handling in out enbloc enbloc Trunk Hunt cyclical Digital Loss Group 13 Incoming Calling Number Delete Insert Format unk unk Bit Rate 1200 Synchronizat
29. er ID Set Ymsg Set Priv Received Pub Received Figures below show the additional configurations to be done to the selected DN which has to be member of the BlocA pool found in the Line Pool Access tab PM Reviewed SPOC 02 26 2013 Solution amp Interoperability Test Lab Application Notes 2013 Avaya Inc All Rights Reserved 11 of 47 AAM61SM61BCM60 Task Navigation Panel Configuration Welcome System Administrator Access Resources Application Resources Media Gateways Port Ranges Telephony Resources IP Trunks Dial Up Interfaces Telephony Global Settings Sets Templates TEN Active Application DI Inactive DNs All DNs O Lines Loops Scheduled Services Dialing Plan General DNs Public Network Private Network Active Sets 22225 22226 22227 22228 22229 22230 22231 22232 22233 22234 22236 DN Line Access Capabilities and Preferences Restrictions Name Port 22225 1002 22226 1003 22227 1004 22228 1005 22229 1006 22230 22231 v 22232 22233 cere 22236 4001 Pub OLI Priv OLI Fwd No Answer 22301 22301 22236 39990 Ea Delay Fwd Busy 22301 Details for DN 22235 Line Pools Line Pool Line Pools Routing Ring Groups Call Security Hospitality Add Line Assignment Line Pool Acces
30. ession Manager as provisioned in the reference configuration Session Manager is comprised of two functional components the Session Manager server and the System Manager server All SIP call provisioning for Session Manager is performed through the System Manager Web interface and is then downloaded into Session Manager The following sections assume that Session Manager and System Manager have been installed and that network connectivity exists between the two platforms In this section the following topics are discussed e SIP Domains Locations SIP Entities Entity Links Time Ranges Routing Policy Dial Patterns Synchronization 8 1 Configure SIP Domain Launch a web browser enter http lt IP address of System Manager gt SMGR in the URL and log in with the appropriate credentials Navigate to Routing gt Domains and click on the New button not shown to create a new SIP Domain Enter the following values and use default values for remaining fields e Name Enter the Authoritative Domain Name e g bvwdev com e Type Select SIP Click Commit to save The following screen shows the Domains page used during the compliance test Routing Home Help Locations Domain Management Adaptations SIP Eatities Emtity Links Time Ranges Routing Policies Disl Patterns Regular I xpressions Detaults PM Reviewed Solution amp Interoperability Test Lab Application Notes 24 of 47 SPOC 02 26 2013 2013 Av
31. hutdown System As of 1 51PM 1 Item Refresh Show ALL Mi Filter Enable Session Tests Security Service Entity arnyn a s 5 E Manager Type Alarms Pass Module State Monitoring eal peiris pann Accept DevASM Core 24069 2177 2118 V Up New 12 44 o 9 6 1 1 0 611023 Service Session Manager Instances status Navigate to Elements gt Session Manager gt System Status gt Security Module Status not shown to view more detailed status information on the status of Security Module for the specific Session Manager Verify the Status column displays Up as shown below Security Module Status This page allows you to view the status of each Session Manager s Security Module and to perform certain actions Certificate Management Connection Status 1Item Refresh Show ALL Filter Enable Entity p Details EE Type Status Connections IP Address LAN edict NIC Bonding Canned se laa actual Show Dev SM SM Up 46 135 10 26 aks yal i Disabled 57 57 SIP CA PM Reviewed Solution amp Interoperability Test Lab Application Notes 40 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 10 1 2 Verify SIP Entity Link Status Navigate to Elements gt Session Manager gt System Status gt SIP Entity Monitoring not shown to view more detailed status information for one of the SIP Entity Links Select the SIP Entity for BCM from the All Monitored SIP Entities table
32. ination Codes O Lines Destination Code Normal Route Absorbed Length Loops a E Scheduled Servi 525 001 0 Dialing Plan 593 002 0 General 9411 003 1 DNs 9416 003 1 Public Netwo 9613 003 1 Private Netwi 9647 003 I Line Pools 9905 003 1 e 9911 003 1 Busai ann 4 PM Reviewed Solution amp Interoperability Test Lab Application Notes 8 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 5 3 3 Configure the dialing plan private network Configuration gt Telephony gt Dialing Plan gt Private Network Configure the private network as shown in figure below e Private Received number length 5 e Private network type CDP e Private DN length 5 A Avaya Business Element Manager 47 248 100 217 File Edit View Network Session Tools Help la x Bp ext Element Navigation Panel 4 Task Navigation Panel E Network Elements Configuration Administration 47 11 5 200 General Private Network Settings 47 248 100 215 r LLa SIP Trunking Private Received number leng Private network typei cor z H323 Trunking Dial Up Interfaces Private Auto DN Private network ID fi EQ Telephony Private DISA DN Location code H Global Settings ic O sets i HEE sos code 6 i Private DN lenathefs Z 4 X cut My copy a Paste Web Page v Validate Device Y Disconnect fy Refresh f Auto refresh Dialing Plan Private Network a5 247 248 10
33. ion async Duplex full Disconnect Supervision In y Out n Answer Supervision Timeout 0 Administer Timers n CONNECT Reliable When Call Leaves ISDN n Delay Call Setup Wh en Accessed Via IGAR n PM Reviewed Solution amp Interoperability Test Lab Application Notes 19 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 Navigate to Page 3 Enable the Send Name Send Calling Number and Send Connected Number fields For the Format field enter unknown Submit these changes add trunk group 1 Page 3 of 21 TRUNK FEATURES ACA Assignment n Measured none Wideband Support n Internal Alert n Maintenance Tests y Data Restriction n NCA TSC Trunk Member 23 Used for DCS n Hop Dgt n Send EMU Visitor CPN n Suppress Outpulsing n Format Outgoing Channel ID Encoding preferred UUI IE Treatment service provider Replace Restricted Numbers n Replace Unavailable Numbers n Hold Unhold Notifications y Modify Tandem Calling Number no Send UUI IE Send UCID Send Codeset 6 7 LAI IE Apply Local Ringback Show ANSWERED BY on Display y Network Japan Needs Connect Before Disconnect n Dsl Echo Cancellation n pkg Ok 7 3 Administer Signaling Group Administer an ISDN signaling group for the new trunk group to use for signaling Use the add signaling group n command where n is an available signaling group numbe
34. ister Application Resource for PRI Trunks These Application Notes assume that the basic configuration has already been administered This section describes steps for configuring Application Resource for PRI Trunks on BCM to work with Service Provider system For further information on Avaya Business Communication Manager 450 configuration please consult references in Section 12 Enable the PRI device on Avaya BCM by select Resources gt Telephony Resources Under Configured Device column select DTM PRI and then click Enable button if it is not already enable as show in figure below Configure PRI trunk parameter as highlighted in red box Others are left as default e Trunk type PRI Protocol NI 2 NSF extension None B channel selection Descending Sequential Clock source Internal CO fail TIA 547A Interface levels ISDN Framing ESF Line config B8ZS Task Navigation Panel Telephony Resources Configuration Modules j Welcome Location Configured Device Dip Switch Bus State Low High Active Busy 9 System Interna IP Trunk N J A Enabled 001 008 Identification Intern gt Date and Time Internal f Keycodes IP Subsystem H Telephony Regions D Administrator Access D Resources f Application Resources Media Gateways gt Port Ranges ey Telephony Resources IP Set Applicatior V A ASM ASM MBM All On DSM16 DSM16 MBM Allon DTM PRI All On ASM ASM MBM All On 40 z 223 0
35. lity Test Lab at interoplabnotes list avaya com PM Reviewed Solution amp Interoperability Test Lab Application Notes 47 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60
36. nd routed to trunk group 1 will result in the 5 digit calling number to be sent Submit these changes change public unknown numbering 0 Page 1 of 2 NUMBERING PUBLIC UNKNOWN FORMAT Total Ext Ext Trk CPN CPN Len Code Grp s Prefix Len Total Administered 1 6 7222 1 6 Maximum Entries 9999 7 7 Administer Uniform Dial Plan This section provides a sample AAR routing used for routing calls with dialed digits 7xxxxx to Avaya BCM Use the change uniform dialplan 0 command and add an entry to specify use of AAR for routing of digits 7xxxxx Enter the following values for the specified fields and retain the default values for the remaining fields Submit these changes change uniform dialplan 0 Page 1 of 2 UNIFORM DIAL PLAN TABLE Percent Full 0 Matching Insert Node 7222 7 8 Administer AAR Analysis Use the change aar analysis 0 command and add an entry to specify how to route the calls to Avaya BCM Enter the following values for the specified fields and retain the default values for the remaining fields Submit these changes change aar analysis 0 Page 1 of 2 AAR DIGIT ANALYSIS TABLE Location all Percent Full 1 PM Reviewed Solution amp Interoperability Test Lab Application Notes 23 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 8 Configure Avaya Aura Session Manager This section provides the procedures for configuring S
37. nfigure Active Sets The highlights in the following screens indicate the values used during the compliance test Default values may be used for all other fields Please keep in mind that the values used in this guide may be unique to the example shown User will have to use values unique to their site where this solution is being deployed e g site s IP address extension numbers etc Avaya BCM configurations can be performed through Business Element Management only PM Reviewed Solution amp Interoperability Test Lab Application Notes 5 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 5 1 SIP Trunking Configuration This section explains the steps to configure a SIP trunk routing entry that will access the Messaging via Session Manager from the Avaya BCM 5 1 1 Configure Proxy for Private SIP Trunking After logging into the BCM element manager configure a private proxy for the SIP trunking by selecting Configuration gt Resources gt IP Trunks gt SIP Trunking Select the tab Private gt Proxy to add a proxy as shown in figure below e Domain the defined domain that the Avaya Aura Messaging and Avaya Aura Session Manager system is assigned to During compliance test bywdev com domain is used e IP Address is Session Manager s IP Task Navigation Panel SIP Trunking Configuration Administration Welcome a Public 2 Global Set
38. not shown to open the SIP Entity Entity Link Connection Status page In the All Entity Links to SIP Entity BCM450_34table verify the Conn Status for the link is Up as shown below 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 Links to SIP Entity BCM450_34 1 Item Refresh Filter Enable Details Session Manager Name SIP Entity Resolved IP Port Proto Conn Status Reason Code Link Status Show DevASM 135 10 5060 UDP Up 200 OK Up As described above the Entity link connection status can also be viewed for the AAM Verify that the Conn Status is also Up not shown PM Reviewed Solution amp Interoperability Test Lab Application Notes 41 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 10 2 Verify Avaya Aura Messaging 10 2 1 Verify no answer call Make a call from a Avaya BCM endpoint to another Avaya BCM endpoint and verify that the call covers to Messaging upon no answer Leave a voice message Verify that the MWI light of the called phone turns on From the receiving Avaya BCM endpoint dial the Messaging access number to retrieve the message Verify that the Messaging system identifies the Avaya BCM endpoint and that the voice message can be retrieved Verify that the MWI light turns off Log into the Messaging System Management Interface S
39. on PM Reviewed SPOC 02 26 2013 32 of 47 AAM61SM61BCM60 Solution amp Interoperability Test Lab Application Notes 2013 Avaya Inc All Rights Reserved Scroll down to the Auto Attendant section Under Auto Attendant e Auto Attendant Select Enabled Auto Attendant pilot number Enter an Auto Attendant number e e Keypad entry Select ENHANCED e Speech recognition Select Enabled Click Save to save changes AVAYA Administration Messaging Administration essaging System Storage User Management Class of Service Sites Topology Storage Destinations System Policies Enhanced List Management System Mailboxes System Ports and Access User Activity Log Configuration Reports Storage Users Info Mailboxes Remote Users Uninitialized Mailboxes Login Failures Locked Out Users System Status Storage System Status Application Alarm Summary Cancel Voice Channels Application Operator live attendant extension General mailbox l Auto Attendant Auto Attendant enabled disabled Auto Attendant pilot number 39995 Additional sites included in the directory None Keypad entry ENHANCED BASIC Enter extension only ENHANCED Enter extension or spell name Speech recognition enabled disabled PM Reviewed Solution amp Interoperability Test Lab Application Notes 33 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights
40. one Dialing is done Connected Near End disconnected CP NEAR_END DISCONNECT 10 2 3 Message Waiting Indicator MWI light on phones To perform this test select Administration gt Messaging In the left panel under Diagnostics select Diagnostics Application In the right panel fill in the following e Select the test s to run Select MWI from the drop down menu e Extension number Enter the number of the phone to test Click on Run Tests to start the test The phones MWI light will turn on and off The Results section of the page will update with information about the test as shown below PM Reviewed Solution amp Interoperability Test Lab Application Notes 44 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 Diagnostics Selection amp Configuration Select the test s to run MWI This tests the Message Waiting Indicator MWI It will turn on and off few times the MWI light for the extension Configuration of MWI Test Extension number MWI port number optional Results Test MWI Time 9 20 47 AM Checking MWI PLEASE NOTE An OK result does not necessarily confirm that the Message Waiting Indicator MWI was successfully set Always verify on the actual phone that the MWI was turned on and off twice Some PBXs require that the MWI is switched off from the same line that was used to switch it on On these PBXs perform the tes
41. onfiguration no restrictions were used To add a Time Range navigate to Routing gt Time Ranges and click on the New button not shown Provide the following information Enter a descriptive Location name in the Name field e g 24 7 Check each day of the week In the Start Time field enter 00 00 In the End Time field enter 23 59 Enter a description in the Notes field if desired Click the Commit button The following screen shows the Time Range page used during the compliance test Time Ranges 1 Item Refresh Filter Enable E Name Mo Tu We Th Fr Sa Su Start Time End Time Notes 24 7 M Mw M a v M M 00 00 23 59 Time Range 24 7 Select All None PM Reviewed Solution amp Interoperability Test Lab Application Notes 28 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 8 6 Configure Routing Policy Routing Policies associates destination SIP Entities with Time of Day admission control parameters and Dial Patterns In the reference configuration Routing Policies are defined for Business Communication Manager To add a Routing Policy navigate to Routing gt Routing Policy and click on the New button not shown on the right Provide the following information General section e Enter a descriptive name in the Name field e Enter a description in the Notes field if desired SIP Entity as Destination section e Click the Select button
42. otes 3 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 4 Equipment and Software Validated The following equipment and software were used for the sample configuration provided Equipment Software S8800 Server Avaya Aura Messaging Release 6 1 S8800 Server Avaya Aura Session Manager Release 6 1 S8800 Server Avaya Aura System Manager Release 6 1 G450 with S8300D emulated PSTN Avaya Aura Communication 6 0 PRI Digital Trunk Interface Module Business Communication Manager 450 Avaya BCM450 R6 SU 011 201205 2 Avaya 1140E IP Telephone SIP Firmware Version 0625C8J 2 Digital Phones T7316 n a 2 Analog Phones n a PM Reviewed SPOC 02 26 2013 Solution amp Interoperability Test Lab Application Notes 2013 Avaya Inc All Rights Reserved 4 of 47 AAM61SM61BCM60 5 Configure Avaya Business Communication Manager with SIP Trunking to Avaya Aura Session Manager This section describes the procedure for setting up Avaya BCM The following administration activities will be described Configure Proxy for Private SIP Trunking Configure the Global setting for SIP Trunking Configure general info for IP Trunks Configure the routing Configure the destination code Configure the private network for dialing plan Configuring the Public network for the dialing plan Configure Target Lines Assign a target line to a selected set Co
43. r Call to Forward All forward to messaging access number endpoint Call to Busy endpoint messaging access number is set if this endpoint busy All the call is forwarded to pilot number The following Avaya Aura Messaging capabilities were not in scope for this testing e Call Sender e Reach Me e Notify Me PM Reviewed Solution amp Interoperability Test Lab Application Notes 2 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 2 2 Test Results and Observations Interoperability testing of Avaya Aura Messaging 6 1 Single Server as a voice mail solution for Avaya Business Communication Manager with SIP Trunking through Avaya Aura Session Manager R6 1 was successful 3 Reference Configuration Figure 1 below illustrates the configuration used in these Application Notes The sample configuration shows an enterprise with Avaya BCM communicating with the Avaya Aura Messaging via a SIP trunk The Avaya BCM has an analog a digital and an IP Telephone connected as endpoints For security purposes public IP addresses have been masked out or altered in this document TLISDON PRI T1 Crossover Cable Avaya Aura System Manager Release 6 1 0 SU 10 1 1774 Avaya Aura Messaging Release 6 1 LT _ eeeeeeeeeee trunk Avaya Aura Session Manager trunk Release 6 1 6 0 616008 135 10 xx xxx Figure 1 Network Configuration PM Reviewed Solution amp Interoperability Test Lab Application N
44. r For the Primary D Channel field enter the slot number for the DS1 circuit pack from Section 7 1 For the Trunk Group for NCA TSC and Trunk Group for Channel Selection fields enter the ISDN trunk group number For the Supplementary Service Protocol field enter b for QSIG Maintain the default values for the remaining fields and submit these changes add signaling group 1 SIGNALING GROUP Group Number 1 Group Type isdn pri Associated Signaling y Max number of NCA TSC 10 Primary D Channel 001V624 Max number o A TSC 10 Trunk Group for Channel Selection X Mobility Wireless Type NONE Network Call Transfer n PM Reviewed Solution amp Interoperability Test Lab Application Notes 20 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 7 4 Administer Trunk Group Members Use the change trunk group n command where n is the trunk group number added in Section 7 2 Navigate to Page 3 For the NCA TSA Trunk Member field enter the highest trunk group member number to use for routing of tandem QSIG call independent signaling connections change trunk group 1 21 TRUNK FEATURES ACA Assignment n Used for DCS n Suppress Outpulsing n Outgoing Channel ID Encoding provider Send UUI IE Send UCID Send Codeset 6 7 LAI IE Apply Local Ringback Show ANSWERED BY on Display y Net Pe BK Page 3 0f Measured none Wideband S
45. r the name for internal use Enter the mailbox number Enter desired extension number i e 22235 User Management gt Properties for BCM 22235 User Properties First name BCM Last name 22235 Display name ASCII name Mailbox number Internal identifier Numeric address Extension Include in Auto Atten Class of Service BCM 22235 BCM 22235 Default 22235 BCM 22235 22235 22235 sp aamessl avaya com dant directory Standard Pronounceable name BCM 22235 MWI enabled Solution amp Interoperability Test Lab Application Notes 2013 Avaya Inc All Rights Reserved 38 of 47 AAM61SM61BCM60 Scroll down on the page to Class of Service e Class of Service Select a Class of Service e Pronounceable Name Enter a pronounceable name to be used when dialing the extension using voice commands e MWI Enabled Select Yes to enable the MWI light on phones e New Password Confirm Password Enter desired extension password e Next logon password change Select the Checkbox Click Save to save changes AVAYA Help Log Off Administration Administration Messaging Messaging System Storage User Management Class of Service Standard Class of Service Sites Topology Pronounceable name BCM 22235 Storage Destinations System Policies Enhanced List Management MWI enabled Sys
46. ropriate time zone e Accept the other default values Click on the Commit button to save each SIP entity The following screens show the SIP Entity page used during the compliance test Routing Home Elements Routing SIP Entities SIP Entity Details Domains SIP Entity Details Locations Bineri Adaptations SIP Entities Name BCM450_34 FQDN or IP Address 135 10 Entity Links Type Other Time Ranges Routing Policies Notes Dial Patterns Adaptation Regular r i ion Belleville 4 Expressions Location Belleville Defaults Time Zone America New_York Override Port amp Transport with DNS SRY SIP Timer B F in seconds Credential name Call Detail Recording SIP Link Monitoring SIP Link Monitoring Use Session Manager Configuration Y Repeat all the steps for each new entity PM Reviewed Solution amp Interoperability Test Lab Application Notes 26 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 8 4 Configure Entity Links Entity Links define the connections between the SIP Entities and Session Manager In the compliance test the following entity links are defined from Session Manager e Session Manager BCM e Session Manager Avaya Aura Messaging Navigate to Routing gt Entity Links and click on the New button not shown to create a new entity link Provide the following information Enter a descriptive name in th
47. s Answer DNs Meete Conferencing In the Capabilities and Preferences tab make sure the following options are selected e DND on Busy checked e Allow redirect checked Task Navigation Panel Configuration Active Sets Welcome System Administrator Access Resources Application Resources Media Gateways Port Ranges Telephony Resources IP Trunks Dial Up Interfaces Telephony Global Settings O Sets Templates Active Application D Inactive DNs All DNs Lines Loops Scheduled Services Analog eee Line Access Capabilities and Preferences Restrictions Name PrimeLine Intercom K Control FirstDis Auto Called 22234 I C 2 22251 pec wv I C TE a _ N A 22231 ie Handsfree Pickup group Page zone Direct dial Intrusion protection level Auto v 1 1 None v Auto hold for incoming page _ Priority call _ Auto hold Silent monitor supervisor go Allow redirect Redirect ring Receive short tones PM Reviewed SPOC 02 26 2013 Solution amp Interoperability Test Lab Application Notes 2013 Avaya Inc All Rights Reserved 12 of 47 AAM61SM61BCM60 6 Configure Avaya Business Manager 450 with PRI trunk to PSTN 6 1 Administer Resources This section describes how to configure a PRI Trunk on BCM to PSTN 6 1 1 Admin
48. signaling port 5060 General PIEI Trunking H323 Trunkir Dial Up Interface 5 Telephony E Telephony Settings RFC2833 Global Settings Fallback to circuit switched Disabled v Dynamic Payload 101 S O Sets Templates Status Gateway is running 5 2 IP Trunks Configuration This section describes how to configure the general settings for IP trunk 5 2 1 General IP trunk settings Navigate to Configuration gt Resources gt IP Trunks gt General DIP Trunk Settings Setup the general information for the IP trunk as below e Forward redirected OLI First Redirect e Remote capability MWI checked e Send name display checked Note for detail of these setting please refer to Avaya BCM documentation listed in reference Section 12 Task Navigation Panel s General Configuration Administration Welcome Call Routing Summary IP Trunk Settings System Telephony Settings Administrator Access gt Resources Application Resources i a Forward redirected OLI First Redirect Remote capability MWI JV Ignore in band DTMF in RTP J Send name display JV Media Gateways Port Ranges Telephony Resources H O IP Trunks SIP Trunking PM Reviewed Solution amp Interoperability Test Lab Application Notes 7 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 5 3 Dialing Plan Configuration This section
49. t on a phone for which MWI is not switched on Turn MWI 1 for 22232 1 second Turn MWI 0 for 22232 1 second Turn MWI 1 for 22232 1 second Turn MWI 0O for 22232 1 second 10 2 4 Other call scenarios e Call to Forward All forward to messaging access number endpoint e Call to Busy endpoint messaging access number is set if this endpoint busy All the call is forwarded to pilot number PM Reviewed Solution amp Interoperability Test Lab Application Notes 45 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 11 Conclusion Interoperability testing of Avaya Aura Messaging 6 1 Single Server as a voice mail solution for Avaya Business Communication Manager with SIP Trunking through Avaya Aura Session Manager R6 2 was successfulm See section 2 2for detail of test result and observation 12 Additional References This section provides references to the product documentation relevant to this Application Note Documentation for Avaya products may be found at http support avaya com Avaya Aura Session Manager 1 Avaya Aura Session Manager Overview Doc ID 03 603323 2 Installing and Configuring Avaya Aura Session Manager 3 Avaya Aura Session Manager Case Studies 4 Maintaining and Troubleshooting Avaya Aura Session Manager Doc ID 03 603325 5 Administering Avaya Aura Session Manager Doc ID 3 603324 Avaya Aura Messaging 6 Administering Avaya Aura Messaging 6 1 CID 151610 Decem
50. tem Mailboxes System Ports and Access User Activity Log Configuration Reports Storage Users Miscellaneous 2 Info Mailboxes Miscellaneous 1 Remote Users Uninitialized Mailboxes New password ey Login Failures Locked Out Users Confirm password eoccece Server Information System Status Storage System Status Application User must change voice messaging password at next logon Alarm Summary vomen Stopes AN Voice messaging password expired Cache Statistics Application C Locked out from voice messaging Server Settings Storage External Hosts Trusted Servers Networked Servers PM Reviewed Solution amp Interoperability Test Lab Application Notes 39 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 10 Verification Steps 10 1 Verify Avaya Aura Session Manager Operational Status 10 1 1 Verify Avaya Aurae Session Manager is Operational Navigate to Elements gt Session Manager gt Dashboard not shown to verify the overall system status for Session Manager Specifically verify the status of the following fields as shown below e Tests Pass Y e Security Module UP e Service State Accept New Service Pa Home Elements Session Manager Session Manager Help Session Manager Dashboard This page provides the overall status and health summary of each administered Session Manager Session Manager Instances Service State S
51. ting Policies Dial Patterns Notes Belleville DeyConnect lab Regular Expressions Defaults Overall Managed Bandwidth Managed Bandwidth Units Kbit sec Total Bandwidth 1000000 Per Call Bandwidth Parameters Default Audio Bandwidth 80 Kbit sec Location Pattern 2 Items Refresh Filter 4 IP Address Pattern Notes 10 1 2 10 1 1 PM Reviewed Solution amp Interoperability Test Lab Application Notes 25 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 8 3 Configure SIP Entities A SIP Entity must be added for Session Manager and for each network component that has a SIP trunk provisioned to Session Manager During the compliance test the following SIP Entities were configured e Session Manager itself e Avaya Aura Messaging e BCM Navigate to Routing gt SIP Entities and click on the New button not shown to create a new SIP entity Provide the following information General section Enter the following values and use default values for remaining fields e Enter a descriptive Location name in the Name field e Enter IP address for signaling interface on each BCM Avaya Aura Messaging e From the Type drop down menu select a type that best matches the SIP Entity o For Session Manager select Session Manager o For Messaging select Modular Messaging o For BCM select Others e Enter a description in the Notes field if desired e Select the app
52. tings Media Parameters H O System H O Administrator Access Routing Table Settings Proxy URI Map Authentication 3 Resources Application Resources SIP Proxy Optional IP Address for legacy routing Media Gateways Domain bywdey com IP Address 135 10 Port Ranges e n Telephony Resources Route all calls using proxy _ Port OOo 5060 IP Trunks MCDN Protocol None E General kol Trunking Outbound Proxy Table H323 Trunking Dial Up Interfaces Telephony H O Global Settings Sets Templates Active Sets Active Application DNs Inactive DNs All DNs Lines Active Physical Lines Active VoIP Lines Target Lines Add PM Reviewed Solution amp Interoperability Test Lab Application Notes 6 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 5 1 2 Configure the Global settings for SIP Trunking Navigate to Configuration gt Resources gt IP Trunks gt SIP Trunking Select the tab Global Settings as shown in figure below e Local Domain is the defined domain that the AAM and ASM system is assigned to e Call Signaling port 5060 Task Navigation Panel SIP Trunking eoan Public Private Global Settings Media Parameters Resources a Application Resc SIP Settings RTP Keepalives Media Gateways Local Domain SE Scope None vi Port Ranges 7 A L Telephony Reso Service Impacting SIP Settings S O IP Trunks Call
53. upport n Internal Alert n Maintenance Tests Send Name y Send Calling Number y Hop Dgt n Send EMU Visitor CPN n Format unknown preferred UUI IE Treatment service Replace Restricted Numbers Replace Unavailable Numbers Send Connected Number Hold Unhold Notifications Modify Tandem Calling Number no KeK_ 58 5 Dsl Echo Cancellation n work Japan Needs Connect Before Disconnect n Navigate to Page 4 Shown below are default values that were used during testing change trunk group 1 TSC Method for Auto Callbac Diversion by Rerout Path Replacemen Path Replacement with Retentio Path Replacement Metho SB QSIG Value Adde Page 4 of 21 QSIG TRUNK GROUP OPTIONS k drop if possible e y t y n n d better route S n Display Forwarding Party Name y Character Set for QSIG Name eurofont d i PM Reviewed Solution amp Interoperability Test Lab Application Notes 21 of 47 SPOC 02 26 2013 2013 Avaya Inc All Rights Reserved AAM61SM61BCM60 Navigate to Page 5 and 6 Enter all 23 ports of the DS1 circuit pack into the Port fields and the corresponding Code and Sfx fields will be populated automatically Enter the ISDN signaling group number into the Sig Grp fields as shown below Submit these changes change trunk group 1 GROUP MEMBER ASSIGNMENTS NAO UB WDNR w w w w w w TRUNK GROUP Administered Page 5 of 21 Members min max
54. ystem Task Navigation Panel i Target Lines Configuration Line Trunk Name Control Set Line Type Prime Set Pub Received Priv Received Distinct Ring Welcome 365 Target line Line365 22231 Public 22231 22232 22232 H System Public 2 H O Administrator Access 999 Target line Line999 22263 Public 22263 9134400150 22263 H O Resources 896 Target line Line896 20224 Public 22231 22264 5 Telephony 998 Target line Line998 22263 Public 22263 9134400061 22268 H O Global Settings 994 Target line Line994 20224 Public 22231 22349 H D Sets 997 Target line Line997 22263 Public 22263 22524 Lines 426 Target line Line426 22231 Public 22231 22525 22525 Active Physical 995 Target line Line995 22263 Public 22263 22624 22624 Active VoIP Line 996 Target line Lineg96 22263 Public 22263 9134404664 Target Lines e TEE Lines Copy Paste Renumber All Lines Loops Details for Line 413 Scheduled Services ji ae Preferences Assigned DNs sb pheelinacly DN Appearance Type Appearances Caller ID Set Vmsg Set dail E ES SS a Hunt Groups Call Detail Recording Call Recording w Data Services 4 Applications Appr amp Ring Add Delete Also for the assigned set to generate busy tone while it is busy Select Preferences tab e If Busy field Busy tone has to be selected as shown in figure below Task Navigation Panel Target Lines Administration

Avaya Configuring Aura Messaging 6.1 as a Voice Messaging Solution User's Manual

Contents

Download Pdf Manuals

Related Search

Related Contents