Home

AudioCodes Gateway with Avaya/Nortel Communications Server 1000

Contents

1. Save Configuration File Maintenance Status Mediant 1000 MSBG HomePage aset amp Diagnostics ese Software Upgrade Wizard Search Admin Tip When do you have to reset the Mediant Gateway If you see a bolt symbol next to an option it means that the Mediant Gateway has to be reset before that option takes effect 2 Feature Key License Verification and Upgrade Ensure you have the features required for Mediant Gateway implementation Upgrade as needed Verify License keys feature 1 Click Full to expand the list of drop down menu options 2 Using your web browser log into the Mediant Gateway select the Maintenance tab gt Software Update gt Software Upgrade Key 3 Select Software Upgrade Key Minimum requirements for the License PSTN Protocols ISDN T1 E1Trunks 1 Channel Type RTP DspCh 31 Control Protocols SIP SASurvivability If you do not have this minimum feature key contact the Polycom support number Example the screen shown includes more features than the minimum 39 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 7a W z Submit Burn Device Actions w f Home Help Log off 3 Audi oCodes Mediant 1000 MSBG v4 Q
2. eere eene nnn 21 How Stand Alone Survivability Application Works cccccccccsecccsececeecceeceeeeceeneeteuseeeeseeseeteuseeeeseues 22 SAS EC CC SEITE avast tone E peu E ui este due c Use en M S MC cL ides cet URe End EE 22 User AUC n CATON E 22 Chapter 3 Features and Capacity ccccsccccccscsccccccscsccccccscsccccccscsccscccscsceece 23 System Capacity Requirements iuactiesccessvepescxut eria e ecestucbosuid sme uua EiaPe E pes Qutl NV ms a Peta Lire a eic aa pat 23 CaCI EN a A T 23 Features Tested and Validated eese enne nnne nsns nnns 24 FOO CIO o lt 26 Chapter 4 Unpacking and Familiarizing Yourself with the Mediant Gateway 29 Packages COPDPeHTUShsacecdetemdasivi sss bes teniente M PII E TEE dete RR Renee uma Rn UbisUS UM Don opa Redi cep Dod CES UON 29 del m Meis EB ege uo RN TT Imm 29 TE I eo IINE ee 29 BU Sic T c CC E 30 Rear Paner Description uias tediee vata ardevntanzsoadactoctabaataswalantactdoslaasasactaavabedtocvebassaseatsiaseatadencaadeeaaealeds 31 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Chapter 5 Preparing the Mediant Gateway for Initial Configuration 33 Insert che
3. Contiguration Maintenance Ola gros Search Add Phone Context As Prefix m SE Basic Full Trunk Group Index 2 10 E System SM Voip GS Network lPSTN Media ii services S Applications Enabling SE Control Network E sip Definitions El Coders And Profiles cw and IP to IP C liTrunk Group Trunk Group Trunk Group Settings H manipulations Routing I DTMF and Supplementary Hl Digital Gateway Advanced Applications S Data amp Submit 3 Press the Submit button and Burn 97 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes b Add Second PRI as Clock Source When using Multiple PRI s we will also want to allow the PRI to use the secondary PRI as a clock source With this configured if the first PRI becomes out of service for some reason the Mediant Gateway can use the second PRI for clocking 1 Select the Configuration tab and navigate to VOIP gt TDM gt TDM Bus Settings 2 Enable TDM Bus PSTN Auto Fallback Clock 3 Enable TDM Bus PSTN Auto Clock Reverting ra AudioCodes Mediant 1000 MSBG vy Q9 Dum Reset Device Actions n Home e Help ae Log off Maintenance a Digia Besnii i Basic Parameter List a Basic Full
4. Click the reset button and the Mediant Gateway will reset 117 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Firefox 7 Software Upgrade Wizard Mozilla Firefox m PEL LLL LLL CMP file INI file DATA file CPT file VP file j IMPORTANT P PRT file ae Firmware upgrade was chosen CASfile fe configuration is allowed at this stage USRINF file Burn and reset in progress se AMD file FINISH 2 Previous Next After the Mediant Gateway resets this screen displays Firefox 7 Sisi Mozilla Firefox a o Oe Cea eo P CMP Version ID 6 204 045 001 Call Progress Tone File Name usa tones 13 dat IMPORTANT Firmware upgrade was chosen e configuration is allowed at this stage Click the End Process button 118 Appendix C Sample Files These sample files are provided for reference and orientation Your files will be different but will have similar elements Sample AudioCodes ini file This sample board ini file should be representative of the type of configuration you should see ina customer s board ini file however the configuration will vary with the number of PRI s and type of modules installed the number ranges being used to avoid routing loops the Mediant Gateway s IP address and other configuration that will be site specific This file is for reference o
5. 88 Chapter 10 Expanding your System Adding a Second Trunk Group on the Same PBX One method of expansion is to simply add another Mediant Gateway with one T1 module This section covers the configuration of the two Mediant Gateway system Admin Tip Configuring the second Mediant Gateway In this configuration the second Mediant Gateway is configured just like the first one Only PBX changes are needed Communications l Server 1000 Two Mediant 1000 Gateways Each with one T1 modula SpectraLink 6440 Wireless Handsets Admin Tip Allocate a second PRI card in the PBX You will need to install or allocate a second PRI card in the PBX for this configuration 89 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 1 Add another DS1 to the PBX Earlier in this guide we detailed the process for building a single PRI circuit to a Mediant Gateway The process for building a second PRI will be exactly the same except you will use a different TMDI card and define a new loop route and trunk numbers appropriate to your environment am including only the portions that we changed for this second PRI in the examples below otherwise follow the format we used to build the first PRI 2 Adding a PRI card The programming example below shows only the differences between the second and the first PRI card we added using LD 17 Prom
6. Log off v 2 Basic Full Add Phone Context As Prefix Trunk Group Index Disable 1 10 D System Svor H network amp liTOM S Security cl lipsTN CAs State Machines Trunk Settings signaling amp S Media GS services S Applications Enabling S Control Network osip Definitions H Coders And Profiles Gw and IP to IP Trunk Group _ Trunk Group Trunk Group Settings GS Manipulations H Routing E DTMF and Supplementary Digital Gateway S Advanced Applications osas S iP Media HE Data 96 Group From h Index Module zrunk To Trunk Channels Phone Number Trunk Group ID Tel Profile ID io Moduie 1 PRI Mara hz ooo O h eC w a a C OOOO eee s gi mu Hi AJhAPlJ jl j l ae Ca 7 L E L s HI HI a O O O M oY Submit Expanding your System 3 Press Submit and Burn Two PRI interfaces in two T1 modules 1 Select the Configuration tab and navigate to VOIP gt GW and IP to IP gt Trunk Group gt Trunk Group 2 Change these settings Module Select the module for the second PRI From Trunk 1 To Trunk 1 Channels 1 23 Phone Number 100024 Begin with the next available channel number Trunk Group ID 1 Tel Profile ID 0 PG Au di J Mediant 1000 MsaG Ww Senit em Device Actions w f tome 9 r e Log off
7. 2 Locate the four anti slide grooves on the underside one on each of the four corners 71 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 3 Peel each anti slide rubber foot off the adhesive backing and stick one in each anti slide groove 4 Turn the device over so that it rests on its underside and place it in the required position on a desktop 72 Installing the Mediant Gateway 19 inch Rack Mounting You can install the Mediant Gateway in a standard 19 inch rack that has pre installed shelves recommended or by attaching it directly to the rack frame using the front mounting brackets and user adapted rear mounting brackets not supplied Warning Rack Mount Safety Instructions When installing the chassis in a rack implement the following safety instructions Elevated Operating Temperature If installed in a closed or multi unit rack assembly the operating ambient temperature of the rack environment may be greater than room ambient temperature Therefore consideration should be given to installing the equipment in an environment compatible with the maximum ambient temperature Tma of 40 C 104 F Reduced Air Flow Installation of the equipment in a rack should be such that the amount of air flow required for safe operation on the equipment is not compromised Airflow is side to side so ensure sides are clear Mechanical Load
8. Disabte the DHEPICUETE ere ne eee ene ne Tn mE ene RESI IN EDU SU ERE DR NDS ere 42 4 Set Mediant Gateway IP AdQf 888 oec tonto bn nC mte Be Pv QR aao e Er b Ee ER n UE Vy Lirbad sudes En Ulr PEv V VU NU ins God tao 43 Vel the ser carson avenge QEON DI mE UNUM FI DEMNM MM MU FUIMUS 45 se M I SCULIINE RT ities 46 Koa 5USIOB POERITIBEBES ee TEA ene ee 47 Sel CDR REPDOTUNO s M 48 Configure additional syslog trace settings eiie tirinte tri uii a ONENEN nnns nans 49 Z Enable SAS ADD MIC ALON AEE vacesavenanaciatincs Cove tud d cuoi LU Parure aU O EETA PURUS EU 51 COLO SAS ROTER em 52 8 Configure Mediant Gateway Application SIP parameters eseeeeeenennnns 54 9 Configure Mediant Gateway Trunk Group ceccccccsssecccseseccceescceseessececeeeeceeeeueeesausecesseneeceesenes 55 10 Configure Mediant Gateway Trunk Group SettingS ccccccsssecccesseccccesscceceeseceeseeeeceeseeceetenseeeees 57 TI COMMUN Tel t0 IP ROLE 2ossctus c eic see tant inc tue und ced Pau e dor dis tacta ed Sag er a c Id or dtes 59 12 Configure IP to Trunk ROUELIDB uii oes edis Pec tbv bes ex itus coa vno tavi onec PPut Sub Rudd d bon exis Pup diria 60 AVOICING a Routing LOOP EE 60 Detecting a routing TODD esiessissexsesete ss tsetastostabutiatsalenteds unes EAEEREN EENAA EAEN 62 13 Configure Deiault Cod
9. FFMT LCMT YALMT ESF B8Z FDL Enabling the Digital Loop Since our Digital Loop is in the Disabled State we will need to enable it You do this through LD 60 as well Note that when enabling the digital loop the system will attempt to establish the D channel too 86 Configuration Requirements of the CS1K though D channel maintenance is typically performed in LD 96 and the D channel can be controlled separately in that LD gt ld G0 DTIOOO enll 33 This is the command to enable loop 33 ERTUDOI 353 5 PRIDOD 33 5 DTAUZS 33 You may see some messages like these as the circuit comes up They typically show the system going through yellow alarm and then circuit establishment OK DCH 33 EST CONFIRM TIME 0 14 39 26 07 2000 If everything is setup correctly you will see a message like this within a minute or so this indicates the D channel has been established Disabling The Digital Loop Not Required This section is not required as part of the PRI turn up It is provided for reference only Through the course of troubleshooting it may also be desirable to disable the Digital Loop at some time You do this through LD 60 as well Note that you will not be able to disable the Digital Loop while the D channel is still enabled so if you are not successful in disabling the loop you would want to use LD 96 to disable the D channel and then come back to LD 60 to disable the Digital Loop gt ld 60 DTIOOO OLS I 33 He
10. Have you collected all the relevant logs and configuration files Required Board INI file Required Extract from Web interface Syslog Required Ethernet Capture Optional Readable by Ethereal or Wireshark DSP Trace Optional PSTN Trace Optional 129
11. Svor Network Gl TDM l Security al PSTN lE Signaling media lE Services G9 Applications Enabling IG Control Network lisIP Definitions L JGeneral Parameters Advanced Parameters fe ke itl HI bI i l Li El Account Table Proxy amp Registration HE Coders And Profiles amp lGw and IP to IP osas amp itP Media HE Data A Detect Fax on Answer Tone SIP Transport Type SIP UDP Local Port SIP TCP Local Port SIP TLS Local Port Enable SIPS Enable TCP Connection Reuse TCP Timeout SIP Destination Port Use user phone in SIP URL Use user phone in From Header Use Tel URI for Asserted Identity Tel to IP No Answer Timeout Enable Remote Party ID Add Number Plan and Type to RPI Header Enable History Info Header Use Source Number as Display Name Use Display Name as Source Number Enable Contact Restriction Play Ringback Tone to IP Play Ringback Tone to Tel Alli lt L Prefer IP Initiate T 38 on Preamble UDP v Disable v Enable v 0 5060 Yes v No v Disable v Disable v Yes v Disable v No v No v Disable v Dont Play v v rz Basic Parameter List WI Lil K wo LS c 3 54 Initial Configuration of the Mediant Gateway 3 Click the Submit button 9 Configure Mediant Gateway Trunk
12. in our example we have only one 70xx 3 Configure Destination Prefix This is the block of numbers you are sending to the Mediant Gateway followed by a sign Note that the Mediant Gateway will not look at this table to route these calls unless it has already checked the SAS proxy and determined that the phone is currently unregistered In our example we used 70x Source Prefix Source IP Address T Stripped Digits From Left Enter the extension s length We stripped all four digits in our example Stripped Digits From Right 0 Prefix to Add Enter the extension number you wish the call to re route to For our testing purposes we pointed them to a CCMS station x 3044 residing on the PBX 4 Theremaining fields should stay at the default value 61 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Va Vl Submit Burn Device Actions v Home Help Log off K wl AudioCodes Medien 100 MODO V o Hy e t x Status Configuration Maintenance amp Diagnostics Gesn Note Select row index to modify the relevant row Basic Full f _Ad S System Stripped Stripped JS VoIP ger sees Prefix to Add Suffix to Add m From From lal Network NN end Left Right a aM PSTN That E E Media HE Services S Applications Enabling H Control Network lisiP Definitions H Coders And Profiles GW and IP to
13. 172 29 102 1 ALA Digital Port Number 1 sales ham La Firmware Version 6 204 054 LOS LOF Alarm D Protocol Type SIP AIS Alarm d way j Gateway Operational State UNLOCKED Did up The Toolbar and Navigation pane Elementary functionality is accessed through the toolbar along the top of the interface and the navigation pane along the left The Burn button The Burn button writes configuration changes to flash memory Do this periodically so that you do not lose your work due to a power outage or other system problem Navigation Pane The Navigation Pane on the left side of the window provides the menus to the screens you see illustrated in this document Ensure that the Full radio button is selected so that you can see all available options The Search option You can find settings by searching with the Search button located on the Nav pane 38 Initial Configuration of the Mediant Gateway Device Actions Use the Reset option on the dropdown menu to reset the Mediant Gateway and activate configuration settings Certain settings require a reset of the Mediant Gateway to take effect and these are marked with a lightning bolt icon The Device Actions menu is also where you will find the Software Upgrade Wizard r 3 AudioCodes Mediant 1000 MSBG v Submit p Burn Device Actions 4 Bi Home Help m Load Configuration File e
14. Coders And Profiles I Gw and IP to IP HE sas Slp Media alata WAN Interface Name 8 Restart the Mediant Gateway to apply the settings by using the Device Actions dropdown menu and selecting Reset p a p a m SS adus _ s Submit Burn Device Actions A Home Help a Log off ca Mediant 1000 MSBG v Q n ae Load Configuration File AudioCodes Save Configuration File n Status i 7 Configuration Maintenance irem p Search v Submit 9 Burn Device Actions w A Home G Help Log off wi AudioCodes I a Ns e MM Status Basic Full wv Reset Configuration Reset Board Burn To FLASH Yes na Graceful Option w LOCK UNLOCK Lock Graceful Option Gateway Operational State UNLOCKED v Save Configuration For Reset Board If you choose not to save the device s configuration to flash memory all changes made since the last time the configuration was saved will be lost after the device is reset For Save Configuration Saving configuration to flash memory may cause some temporary degradation in voice quality therefore it is recommended to perform this during low traffic periods 9 The Mediant Gateway will reboot and restart using the new IP address 44 Initial Configuration of the Mediant Gateway Verify the settings 1 Log into the Mediant Gateway using your web browser changing
15. Group Trunk group is a local entity that the Mediant Gateway will use for call routing For most applications all available channels will be aggregated into one trunk group Admin Tip Adding multiple PRIs to a trunk group If you are configuring multiple PRIs review Chapter 10 Expanding your System You will need to go through the configuration sequence below regardless of how many trunks are configured 1 Select the Configuration tab and navigate to VOIP gt GW and IP to IP gt Trunk Group gt Trunk Group r i i E ia AudioCodes Mediant 1000 MSBG v Submit Q9 Burn Device Actions w Home Help o r f B Status Configuration Maintenance 3 Diagnostics Search v Add Phone Context As Prefix Disable vv OBasic Full 9 Trunk Group Index 1 10 b S system E D Network O EE aue D Security amp llesTN signaling H Media H services HE Applications Enabling HE control Network H sip Definitions Hl Coders And Profiles Gw and IP to IP trunk Group Trunk Group _L JTrunk Group Settings H Manipulations Dl Routing amp libTMF and Supplementary SE analog Gateway Digital Gateway S Advanced Applications osas HiP Media H Data K Submit 2 Add Phone Context as Prefix Ensure parameter is set to Disable 3 Trunk Group Index Using the drop down menu ensure the parameter is set to 1 10 4 For Group I
16. SpectraLink 8400 series handsets with a legacy PBX using the Mediant Gateway it is vital to select the right line interface between the Mediant Gateway and PBX The recommended and supported line interface is Q SIG PRI Q SIG has a richer signaling capability than T1 Channel Associated Signaling CAS or Analog line interfaces enabling the broadest telephony feature set on the SpectraLink 8400 using the Mediant Gateway solution A Word about Wi Fi Many customers install a single wireless network to support both voice and data Deploying a Wi Fi network that supports voice is not difficult but there are guidelines that should be followed Polycom has documented these best practices and it is important that the wireless network meets these guidelines to achieve user satisfaction Although not specifically covered in this document for optimum performance the deployed access points should conform to the VIEW program as documented in the Polycom best practices references and listed in the Polycom VIEW Certified Products Guide 20 Chapter 2 What the Mediant Gateway Does In a typical deployment the Polycom SpectraLink 8400 Series Wireless Handsets use 802 11 a b g n Wi Fi with the open standard Session Initiated Protocol SIP for telephony signaling to and from the call server i e PBX In a facility where the call server does not recognize the SIP protocol the Mediant Gateway provides protocol translation for smooth call operations
17. TI ETLIMOGQUIE ne a Pee ee eee ee 33 Connect to Power Connect to Computer eee cece ssccseceeccesccseceecceeceeccseceeccseceeceeeesseeeeceseeeeeeseceeeeaes 34 Part Il Configuring the Components 4 35 Chapter 6 Initial Configuration of the Mediant Gateway 37 1 Connect Mediant Gateway to a single computer esssesesseeeeeeenneee nennen nnne nnns 37 Theme SOOO seite E fusum AU A dee a se DO PME MD PME DN E 38 The Toolbar ana Navigation DUM mirisnih E Sv ta nenia INR E aad Y paved EEE E Ro DERE EFL E Es 38 erum OU OID PET M 38 INV IO OID PC ccc recs 38 Ie SARC ll ODON raaro TETTE 38 DEVE PVCU OI S arse cT M 39 2 Feature Key License Verification and Upgrade ccccccccccccccccceeeeceeeeeeeeeeeseeseeecececeseseeeeeeeeeeeaaaeegs 39 VeHnVEicensg koy ax 0 On Ate Pc averide RE or End pA SUR cotE and eee 39 Minimum requirements for the License cccccccssseccccessccceeessececeuececeenecceseusecessuesecesseneceeseeas 39 Add Software upgrade key optional if key needs to be installed eee 40 3 Disable DACP Cli nt and Servel sssosesnkso eiua Ea FEES eNE VPE RAE YE PAPE P EEE 41 Disable the Device s DHCP Server ccscsseusccnsesescsescsosssencussenncesesceseneuesencusssncesssecsesencussencesssnsesesees 41
18. WS G Lu P Configuration Maintenance 2 Dearest Search Current Key O Basic Full Key features Di Maintenance Board Type Mediant 1000 MSBG JE software Update IP Media Conf VXML VoicePromptA nnounc H248 9 ExtVoicePrompt 1MB DSP Voice features IpmDetector Coders G723 G729 GSM FR G727 ILBC EiTrunks 4 4 DATA features Routing FireWall VPN WAN Advanced Routing PSTN Protocols ISDN IUA 4 CAS ER 2 40 IPMediaDspCh 240 iSecurity IPSEC MediaEncryption StrongEncryption EncryptControlProtocol MGCP MEGACO SIP SASurvivability MSFT __ Load Auxiliary Files Software Upgrade Key i ISoftware Upgrade Wizard i IConfiguration File iDefault features Add a Software Upgrade Key Add Key Send Upgrade Key file from your computer to the device SendFile Reset with flash burn is required after file is loaded Add Software upgrade key optional if key needs to be installed You will get a file from your representative that will look something like this LicenseKeys Run Id 142251 BoardType Mediant1000 S N3593541 okRqr5topD458Btxxzw381421id5cOda9gZzlhYg9j8aaRdlhSA4aiY3mOjaL21c80MfeufIxxx qvGatewayq4PQba2celOF4cyB4rQceeeLA9j8ealJ9YZQba388nil5cOlc80MA4f9uocykfa5Ne4 PQSaz8un2 6WeOSTSM00 Your key will look different than the one above Your key is encrypted with the serial number of the Mediant Gateway you are using Each Mediant Gateway will require its o
19. are state of the art SIP endpoints The extensive feature set and configuration possibilities create a custom telephony environment only available within the SIP protocol Many of these features if not most are available within this solution However some features do not survive the translation from one protocol to another and cannot be expected in this hybrid environment See the table on the next page and the footnotes that follow 24 Features and Capacity Handset Features eean SIP Gateway Incoming Outgoing calls Y Y Call waiting Y Y Caller ID Y Y Codec G 711 G 729 Y Y Conference 3 way Y Y Do not disturb Y Y Forward busy no answer and manual Y Y Hold and Resume Y Y Registration Y Y Transfer blind and attended Y Y Up to 6 call appearances per line Y Y Speed dial Y Y Contacts Directory Y Y User Profiles Y Y Lines per phone Y Y Redial Y Y Call history Y Y Distinctive ring Y Y PTT Y Y OAI Y Y XML API applications Y Y Exchange calendar integration Y Y IM Y Y SIP URL calls Y Y Speaker and Mute Y Y Paging off PBX 8400s only Y Y Voicemail N Y Message waiting indication N Y PBX based features N Y Paired lines shared line bridged line etc ring both phones generally N N Music on hold N Y Hold recall N Y Park Pickup Directed Pickup N Y Busy lamp field N Y Camp on automatic callback N Y Authentication N Y Hunt groups N Y Group paging integrated with PBX i N Y Call Park N Y Di
20. difficult to tell this was occurring without looking at syslog output from the Mediant Gateway In our testing our syslogs showed many repeated attempts to set up calls to the same number going back and forth between the Mediant Gateway and the PBX The above configuration would resolve this 62 Initial Configuration of the Mediant Gateway 13 Configure Default Coder Group 1 Select the Configuration tab and navigate to VOIP gt Coders and Profiles gt Coders 2 Using the drop down set the Coder Name to G 711U law G 711A law and G729 as shown below 3 Set Silence Suppression to Disabled Mediant 1000 MSBG v Submit Q Burn _ Device Actions v e Home e Help oo Log off I 7a w el AudioCodes oo Status s exeun Packetization Coder Name i 5 O Time h e 4 G 711U law BB system G 711A la 20 Svor Network G 729 aTom amp lil Security amp llesTN Sl signaling media P Services HE Applications Enabling El Control Network amp lisiP Definitions El coders And Profiles Coders Group Settings Tel Profile Settings _ IIP Profile Settings Sl Gw and IP to IP B osas Submit ae i amp 4 Click Submit Admin Tip G 722 restriction G 722 High Definition audio will only work on intra Mediant Gateway calls 63 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deploymen
21. for IP to Tel Enable ISDN Tunneling Tel to IP Enable QSIG Tunneling Enable ISDN Tunneling IP to Tel ISDN Transfer on Connect Remove CLI when Restricted Remove Calling Name Tdm Over IP Minimum Calls For Trunk Activation Default Cause Mapping From ISDN to SIP Add Prefix to Redirect Number Copy Destination Number to Redirect Number Device Actions v fs Hone AE a kj Aa ar IR G Help eo Log off Basic Parameter List Submit gt 3 Click Submit Initial Configuration of the Mediant Gateway 17 Setting up the PRI The parameters you set in the Mediant Gateway will depend on your PBX s PRI settings but these can be used as areference 1 Select the Configuration tab and navigate to VOIP gt PSTN gt Trunk Settings 2 Inthe Protocol Type field select T1 Q SIG Admin Tip If the trunk is already started If the trunk is already started you will not be able to edit trunk parameters unless you shut down the trunk If this is the case click the Stop Trunk button 3 When you first set up the Mediant Gateway or change the Protocol type field click the Apply Trunk Settings and Burn 4 Verify the following settings Clock Master Recovered this means that the Mediant Gateway will recover the clock from the T1 signal instead of using the Mediant Gateway internal clock leave at default O Auto Clock Trunk Priority Li
22. phones to the Mediant Gateway as four digit extensions This worked well when communicating with other extensions on the PBX or extensions on another Mediant1000 Mediant Gateway attached to the PBX However when you begin calling to other off PBX locations a four digit Caller ID may not be appropriate Consider the case where you wish to send an entire 10 digit Caller ID such as when you are planning on placing calls out to the PSTN For on PBX stations in the CS1000 you might modify your Caller ID using theCLID features within the CS1000 In the example below we show you where you would go to modify your outbound Caller ID for stations registered to the Mediant Gateway 1 AUDC Navigate to VOIP gt GW and IP to IP gt Manipulation gt Source Number P gt Tel In our example below all of our DID numbers registered to the CS1000 begin with 303 583 followed by the number we used for registration Our CS1000 is also configured to use 9 as the NARS Access Code 1 2 Configure a Destination prefix 9 b Prefix to Add 303583 adds a 6 digit prefix to the existing 4 digit extension of the phone SEP ESS ES SSS SITTE PSO SEP RP SESS 3 Submit and Burn Troubleshooting Monitoring a D channel In the course of Troubleshooting we may wish to watch the messaging on the D channel of a particular PRI This would help determine whether or not the CS1000 or the AudioCodes Gateway is truly trying to send or receive calls
23. routes the call across the TDM trunk to the PBX User Authentication Access to the Mediant Gateway from the Wi Fi handsets is screened by the security mechanisms of Wi Fi access points Basic SAS functionality does not authenticate users It accepts all valid registrations which would theoretically allow one handset to emulate a different one 22 Chapter 3 Features and Capacity System Capacity Requirements There are several relevant capacity metrics that must be determined before determining what resources are required in the type of system we have tested the number of users the number of simultaneous connections required to the PBX and the various call configurations that are used in any particular facility The number of users is straightforward how many simultaneously registered users are required Multiple users of a single wireless handset that are never registered at the same time do not need to be factored in just the maximum number of simultaneously registered users The next relevant metric the number of simultaneous connections required to the PBX is not so easily calculated A dedicated voice channel is not required for every user since all of the users would likely never be connected to the PBX at the same time in the same way that all the PBX users would be unlikely to be connected at the same time Although endpoints registered to a single Mediant Gateway will not need a PBX channel when calling another
24. station attached directly to the PBX Answer the call and initiate a hold from the 8400 to the PBX station The held party will not hear any Music on Hold or Comfort Tone Retrieve the call using the Resume softkey Next place the 8400 on hold from the PBX station and then resume the call The held party will hear Music On Hold if supplied by the PBX 103 Chapter 12 Troubleshooting Features Path Replacement Path replacement the freeing of used T1 bearer channels provided by QSIG was disabled on the Mediant Gateway in order to resolve a forwarding issue discovered in the course of testing Therefore transfers forwards or conferences that must traverse the PRI will continue to consume bearer channels after the transfer forward or conference is complete and until the parties involved in the transfer forward or conference end the call Transfer If you are just transferring between extensions attached to the Mediant Gateway then the PBX s configuration shouldn t matter but if you are transferring to and from extensions attached to the PBX the PSTN or another Mediant Gateway then the PBX s settings are very important You must configure access restrictions on the CS1000 in a manner that will allow trunk to trunk transfers to take place One way to monitor whether or not a transfer or other call from a PBX station is indeed being sent out would be to monitor the D channel s or PRI going between the CS1000 PBX and the Mediant Ga
25. your extension number goes here reg l server l address ip address of your mediant 1000 gateway reg l server l port 5060 gt lt dialplan dialplan removeEndOfDial 0 dialplan digitmap gt lt PHONE_CONFIG gt Filename fwd cfg lt PHONE CONP IG gt SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes lt divert divert 1 contact the number you wish the phone to forward to when you are unavailable goes here gt divert dnd divert dnd l enabled 1 divert ond lt divert fwd divert fwd l enabled 1 gt lt divert fwd gt lt divert noanswer divert noanswer 1 enabled 1 divert noanswer 1 timeout 30 gt divert noanswer lt divert gt lt PHONE_CONFIG gt 128 Appendix D Information needed when you Contact Polycom Support To ensure that you get the best service possible certain information about your system is required so that any service issue can be speedily resolved Before logging a Service Request The following checklist identifies tasks that you should complete prior to logging a Service Request with Polycom Technical Support Describe the application network Optional provide network diagram Describe when the problem started and what has recently changed Required What is the software version Required Have you reproduced the issue and documented the procedure Required
26. 000 Deployment Application Notes Caution Assembling rear brackets If you are assembling the rear brackets please note the following e The distance between the screws on each bracket is 28 mm 1 1 inches e To attach the brackets use 4 40 screws with a maximal box penetration length of 3 5 mm 0 14 inch Cabling the Mediant Gateway Note Ethernet Cable Type Any type of Ethernet cable can be used not necessarily cross connect because gigabit connect detects cable type and adjusts settings accordingly Older systems may require cross cable Connecting to Ground The device must be permanently connected to ground using an equipment grounding conductor Caution Protective Grounding The equipment is classified as Class EN60950 and UL60950 and must be grounded at all times To ground the device 1 Connectan electrically grounded strap of 16 AWG wire minimum to the chassis grounding screw located on the rear panel using the supplied washer 2 Connect the other end of the strap to a protective grounding This should be in accordance with the regulations enforced in the country of installation Grounding cable 74 Installing the Mediant Gateway Connecting to the LAN The CRMX module provides three 10 100 1000Base T Gigabit Ethernet RJ 45 ports for connection to the LAN To connect the device to the LAN using the GbE port 1 Attach one end of a straight through RJ 45 Ethernet Cat 6 o
27. 1 IP Profile ID 0 Source IP Group ID 1 TS AudioCodes Median 4000 MSRC of Sent Gem Denans we Home yeh tog of bus Te Teun Gren me Res Tab ic nfigurabon MardenAoR b nisnannes Seach Bred Parnmeber List a Los Ph e Basic Full Reubnig Index 1 30 yi 3 IP Te Tel Routing Mode Reute cabs tedere mangulaties se H System z pi T Bast Heat Preh Snurce Hast Prete Dash Phone Pres Source Phone Prete Bouree IP Address a Tne Group ETP Profile 1O Source TForaup Tol x dal rM Tall te ursa ll per signaling Pi Mecha HUB Services US Applications Enabling r ices trol Hetwark Sisi S1P Definibians P Coders and Profiles Gl Gu and iP re 15 llTrunk Group i A 1 dall Ma rsniiiarinns F ll Routing general Parameters Tel ta IF Rautirg IT tn Trunk Group amp rating t Alte natrye Routing Reasons brit Forward Cn Busy Trunk m 3 Click Submit Avoiding a Routing Loop In the last section we told the Mediant Gateway to route all calls that are not found registered to the SAS to the PRI and on to the PBX This keeps our routing rules in the Mediant Gateway relatively simple and allows almost all of our dialplan and routing rules to be maintained on the PBX However we must tell the Mediant Gateway what to do if it receives a call from the PBX intended for a station that is not 60 Initial Configuration of the Mediant Gateway found to be currently registered to the SAS This could occur if an extensi
28. 1 in order to verify that ISDN is already set to a value of Yes for the customer If not follow the procedure below to enable it The programming example below shows how to define a PRI customer using LD 15 For all other fields not listed in the example press RETURN to use default values Prompt Response Description REQ CHG Change existing data TYPE CDB Customer data block CUST 0 Customer number ISDN YES Customer is equipped with ISDN 4 Defining a PRI route The programming example below shows how to add a PRI route using LD 16 For all other fields not listed in the example press RETURN to use default values Prompt Response Description REQ NEW Create new data TYPE RDB Route data block CUST 0 Customer number ROUT Route number you wish to create For our example we matched the Route and D channel numbers and created ROUT 33 DES ACODE1 This is a name for the route You may call it whatever you want TKTP TIE Trunk type DTRK YES Digital trunk route DGTP PRI Digital trunk type for route PRI for T1 PRI2 for E1 ISDN YES ISDN option MODE PRA Route used for PRI only IFC ISGF Interface type Pi i Customer private network identifier Is the same as the CDB PNI at far end ICOG IAO Incoming and outgoing ACOD cox Trunk access code This will need to fit into your dialplan and will be unique for each site For our example we used 2033 82 Configuration Requirements of the CS1K 5 Defining PRI trunks The pro
29. 17 Prompt DLOP MG_CARD Response 34 Supl sh card Description This will be another available Loop Number in your system pick one appropriate to your environment Loop shelf and card number of your TMDI card For our example we used 004 0 04 3 Adding a PRI D channel The programming example below shows only the differences between the second and the first D channel we added using LD 17 Prompt ADAN MG Card DES DCHL 94 Response NEW DCH X Supl sh card ACODE2 XX Description Add a primary D channel any unused SDI port x 0 79 Primary D channel Number Choose a D Channel Number appropriate to your environment For our example we used D channel 34 Loop shelf and card number of your TMDI card For our example we used 004 0 04 A name for the D channel Use something appropriate for your installation The D channel Number you are assigning for this D channel For our example we used D channel 34 Expanding your System 4 Defining a PRI route There is no need to define a new Route for these trunks They will just become members of the existing Route so we can skip to the next step 5 Defining PRI trunks The programming example below shows only the differences between the trunks we are created for the second Route and the trunks we created for the first Route in LD 14 Prompt Response Description Loop and channel number for digital trunks For o
30. 89 T POC ano ner DST TO The T DA airnn n a e dien an teriM be RUM Se dMNA DES DU SM irc RE UEUE 90 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes mT COLO leo ie Ie isi Ae 0 MERE E EA ne en ee Ee eer ee ee eee 90 S Ame QPRIDSEBODEL eee E nT A ne Se ee ae ne eee MD Spo NE 90 By FIO OP OU UC grasa RT T D T 91 SRP SFA EUST ERR TENTER 91 6 Defining a Route List Index RLI ccccccssecccccccceeseccccccceeseecscccueeecsssscuesecsesscuueeeesesseueeessesueeeessessuenss 91 7 Defining a Distance Steering Code DSC isses nnne nnne nennen nnne 92 8 Completing the Turn up of the PRl essen nnne shes essa sneak sarda 92 Adding a Second PRI to an Existing Trunk Group on the PBX ccccceseccceseceeeeeeeeeeseeeaeeceeeeceneeeeeees 93 T Addanoner ST YO PBX rcvira m mU I ra EEEE EE tav tebdn IM dU epi UP EUER 93 ZA dana OA COO asseeisementisstoetua E OE ENEE DIe LEM M eR TE CREE SE 94 B PAGING SP REDI emitted nip T ure elm eid UTI A NM DEM deri 94 q DEO Q PRIOULO aio E E NEU au EE E Non dene e d DN Ded DIEN E 95 SW BS FTO MS ERU CENT TETTE mm 95 6 Completing the Turn up of the PRL sisse oe nain xv oap qU po queda vo AERE bad RE SUR EO UR pH rb ea N B Od Nin 95 7 Configure the Mediant Gateway l sees eese nnne nnne sentes sn annees sane seats aaa seen 96 a Change the Trunk Group settings ccccccssecccsseccessccceececenseceeeseeeaesces
31. 96 DCHOO0 das tmdi 4 0 3 all DCH 34 DISABLED TMDI 4 0 3 MAN DSBL OK 85 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 9 Working with the Digital Loop Getting the Status of the Digital Loop We may want to see whether our Digital Loop T1 is up or down The example below shows how to use LD 60 to determine the current status of the Digital Loop gt ld 60 DTIOOO Jota This command will show the status of all digital loops in the system You might use stat 33 to see just the loop of interest to you PRI TRK LOOP 1 ENBL This is an example of a T1 that is already up and running FFMT LCMT YALMT ESF B82 FDL TRACKING SERVICE RESTORE YES YEL ALM PROCESS YES ALARM STATUS NO ALARM CH Qu IDLE DID MOLY 5 CH 02 IDLE DID VOD CH Os IDLE DID VOR CH 04 IDLE DID MOD CH 05 IDLE DID VOD CH U0 c IDLE DID VOD CH QT IDLE DID MOD CH U8 IDLE DID VOD CH 09 IDLE DID MODE CH 10 IDLE DID VOD Ch LL IBLE DID VOD CH 12 TULE DID VOD CH Lo e DEB DID VOD CH 14 IDLE DID VOD 5 CH is IDLE DID VOLD A CH 1g IDLE DID VOD CH L17 IDLE DID VoD CH I9 IDLE DID VOD CH 19 IDLE DID VOD CH 20 IDLE DID VOR CH 24 IDLE DID VOD CH 22 IDLE DID VOL s GH 29 ZIDDBE DID VOD CH 24 DCH 1 PRI TRK LOOP 33 DSBL This is our new Tl You can see it is still in the disabled state
32. Accounts 2 Create an Admin account for each user who will need access to the Mediant Gateway f fad AudioCodes Search f B iu Status Configuration il Maintenance 3 Diagnostics Mediant 1000 MSBG v Submit Q Burn O Basic Full O system Application Settings Syslog Settings JRegional Settings Certificates Sl Management WEB User Accounts WEB Security Settings Telnet SSH Settings WEB amp Telnet Access List RADIUS Settings W lisNwP 2G VoIP H Data 70 Device Actions w f Hone Help Current Logged User Admin w Account Data for User Admin User Name Access Level Current Password New Password Confirm New Password User Name Access Level Current Password New Password Confirm New Password Deny Authentication Timer Deny Access On Fail Count Display Login Information oS Log off Q Submit Chapter 7 Installing the Mediant Gateway Mount the Mediant Gateway Desktop mounting The device can be mounted on a desktop by attaching the four anti slide bumpers supplied to the underside of the device Once you have attached these bumpers simply place it on a desktop in the desired position Underside E eo ae of Chassis GAOT EEEa m sis ds e s E spogopny EN J To attach the anti slide rubber bumpers to the device 1 Turn the Mediant Gateway over so that its underside faces up
33. Card DES USR IFC DCHL SIDE RCAP PR TRIGS PR TRIGS PR TRIGS PR TRIGS Response TMDI Supl sh card ACODE1 PRI ISGF XX NET CCBI CCNI PRI DV3I CTI NDI COLP DIV 23 CNG23 CON23 CTR2 2 3 Configuration Requirements of the CS1K Description Card type where MSDL The NTBK51BA Downloadable D Channel Daughterboard TMDI TMDI NTRB21 card Loop shelf and card number of your TMDI card For our example we used 004 0 03 A name for the D channel Use something appropriate for your installation D channel is for ISDN PRI only Interface type The D channel Number you are assigning for this D channel For our example we used D channel 33 NET network the controlling switch We will make the CS1000 the Network side of the D channel and the Mediant Gateway the User Side of the D channel USR slave Remote Capabilities Path Replacement Triggers Note There is currently an interop issue between the CS1000 and the Mediant Gateway and Path Replacement is not working as desired at this time Polycom hopes this will be resolved in the future 81 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 3 Defining a PRI customer It is likely that this step will already be completed for any customer already using ISDN but it is included in this guide in case that is not true You may print the CDB in LD 2
34. D 96 Working with the TMDI Card 9 LD 60 Working with the Digital Loop 10 LD 96 Working With the D channel 79 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 1 Adding a PRI card The programming example below shows how to add a PRI card using LD 17 For this example we used a TMDI card rather than a MSDL card If you are using a MSDL card please consult the NTP s for appropriate values for your system For all other fields not listed in the example press RETURN to use default values Prompt Response Description REQ CHG Change data TYPE CFN Configuration data block CEQU YES Changes to common equipment DLOP 33 Digital Trunk Loop number pick one appropriate to your environment MG CARD saphena Loop shelf and card number of your TMDI card For our example we used 004 0 03 MODE PRI Mode of operation TMDI YES Card is TMDI card TRSH 0 Threshold 2 Adding a PRI D channel The programming example below shows how to add a PRI D channel using LD 17 For all other fields not listed in the example press RETURN to use default values Prompt Response Description REQ CHG Change existing data TYPE CFN Configuration data block Add a primary D channel any unused SDI port NEW DCH 0 79 Pri ADAN x 0 79 Primary D channel Number X 80 Choose a D Channel Number appropriate to your environment For our example we used D channel 33 Prompt CTYP MG_
35. E Media E HE Services HE Applications Enabling ui HE Control Network submit Xii erp Nefinitinne wi 65 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 16 B Channel negotiation Configures the most flexible behavior for the B channel negotiation 1 Select the Configuration tab and navigate to VOIP gt GW and IP to IP gt Digital Gateway gt Digital Gateway Parameters 2 Set B channel negotiation to Preferred F Fa 3 AudioCodes Search Mediant 1000 MSBG F Status eentiomation maintenance Biagnostes S 66 O Basic Full H system Svor H Network amp lkroM Sl Security amp llesTN H signaling HE Media H Services S Applications Enabling H Control Network Ssp Definitions HE Coders And Profiles 21 cw and IP to IP amp lTrunk Group E Manipulations eus Routing og DTMF and Supplementary Sl Analog Gateway Sl Digital Gateway ison Supp Services HE Advanced Applications osas HiP Media H Data v Submit Q Burn B channel Negotiation Swap Redirect and Called Numbers MFC R2 Category Disconnect Call on Busy Tone Detection CAS Disconnect Call on Busy Tone Detection ISDN Enable TDM Tunneling Send Screening Indicator to IP Send Screening Indicator to ISDN Add IE in SETUP Trunk Groups to Send IE Enable User to User IE for Tel to IP Enable User to User IE
36. EST 82 a Delininpa Ph WOU Sa etia icis EE TANI E PIT Ed NE m icu MN 82 STRE PRITE Tm 83 6 Defining a Route ist Index RUD cuscciskndveuttenV eeu uUFV EN pu Te E ea EC RP V ENS ERU ECu SAVER EUER PARVERE Sad Co vein ELO v V YS 83 7 Defining a Distance Steering Code DSC sseseesssseeeennneeeenen nnne enne 84 8 Working with the TMDI Card ccccsscccssscccessccceesecceesceceescecaececeececeesceseuecesseceseueeesencessuesensneeees 85 Get ng the Status or the TMD ovii ote eo rte s vao d E EE 85 Enabling a TMDI Card and Forcing a Download to it This loads the New D channel s een GUILE OUR ERR m 85 Disabling a TMDI Card Not R QuIre sssccccseeeescceesececccsecscsueeeseccsecessusecsssuueseseususecssseseesssensess 85 9 Working with the Digital Loop ceccccsscccsseccceesececeneeeescecaececeeceeeesceeeeecessneceseueeeseneeseueesensneeees 86 Getting the Status of the Digital Loop sesenta anrea 86 Enabling the Digital LOOP E 86 Disabling The Digital Loop Not Required isses nennen 87 10 Working with the D Channel Not required 88 DOD NOG DC ONNE MRE 88 EVO AO EPEE ii TEENE ns A E N E A A IE T 88 Chapter 10 Expanding your System sesesesesesesesesesesesesesescscscscececessossesececeoe 89 Adding a Second Trunk Group on the Same PBX cccccssecccesecccesseccesceceececeececeneessuecessecetsneceeens
37. IP t Trunk Group Manipulations General Settings Dest Number IP gt Tel 4 gt i IDest Number Tel gt IP N Source Number IP gt Tel Source Number Tel gt IP xl Done mig La e Internet R10 7 5 Submit and Burn Note Ensure correspondence between PBX and Mediant Gateway Configure a destination index for every unique set of numbers that you define in the AAR routing table as a Distance Steering Code see Chapter 9 section 7 Using this method you will have a one to one correspondence between patterns entered into the AAR table destined for this Mediant Gateway and pattern indices you create here Detecting a routing loop Routing loops are detected by the appearance of certain patters in the syslog By way of explanation consider the following example Using our example number ranges we will define extensions 7xxx to reside on the Mediant Gateway and tell the PBX to send all calls destined for extensions in the 7xxx range out the PRI circuit to the Mediant Gateway Imagine if extension 7001 was not currently registered on the Gateway Without providing an alternate number to route such calls to the Mediant Gateway would just send the request back to the PBX The PBX would look at the invite and route the call back to the Mediant Gateway This is a loop Here we have the D channel attempting to set up this call but since no one is around to accept it the call would never get set up It would be rather
38. PolycomService support us support voice wi fi spectralink 8400 wireless html For Return Material Authorization mailto rmacoordinator polycom com Polycom References This document does not presume to cover the complete range of deployment requirements for SpectraLink 8400 Series Wireless Handsets Please refer to the Polycom Deploying Enterprise Grade Wi Fi Telephony white paper which is available at http www polycom com products voice wireless solutions wifi communications index html This document covers the security coverage capacity and QoS considerations necessary for ensuring excellent voice quality with enterprise Wi Fi networks For more detailed information on wireless LAN layout network infrastructure QoS security and subnets please see the Best Practices Guide to Network Design Considerations for SpectraLink Wireless Telephones which is available at http www polycom com global documents products voice datasheets best practices for deploying plcm spectralink 8400 pdf This document identifies issues and solutions based on Polycom s extensive experience in enterprise class Wi Fi telephony It provides recommendations for ensuring that a network environment is adequately optimized for use with SpectraLink Wireless Telephones Deployment of the SpectraLink 8400 Series Wireless Handsets is fully outlined in the Polycom SpectraLink 8400 Series Deployment Guide available at 11 SpectraLink 8400 Series with AudioCodes Ga
39. The Mediant Gateway and handsets communicate using SIP and the handsets are configured to register with the Mediant Gateway The Mediant Gateway communicates with the PBX via the signaling protocol supported by the telephony lines SpectraLink 8400 Series ee Wireless Handset AudioCodes Communications Mediant 1000 Gateway server 1000 _ t QSIG Wired Ethernet Fundamentally the SIP User Agent in the SpectraLink 8400 Wi Fi handset must register with a SIP Proxy for operation and this SIP Proxy must provide routing capability for both outgoing calls from the handsets as well as incoming calls to them For this solution a SIP Proxy within the Mediant Gateway serves this role This proxy is a component of a feature called Standalone Survivability SAS The primary application of SAS is to provide routing capability to SIP handsets that register to a Hosted SIP Proxy when connectivity to that SIP Proxy becomes unavailable In our application of this feature the Mediant Gateway is configured for continual SAS operation and the Mediant Gateway permanently operates in Standalone Mode with its local SIP Proxy enabled The Mediant Gateway creates a database of user Registrations as handsets contact the Mediant Gateway It uses this database to function as a local SIP Proxy and facilitate user to user calls On the other side of the translation the Mediant Gateway operates as a PRI gateway providing connectivity to the PBX Conse
40. VoIP Monitoring Mode amp Submit 42 Initial Configuration of the Mediant Gateway 4 Set Mediant Gateway IP Address By default the Mediant Gateway has the following settings IP Address 192 168 0 1 Sub net 255 255 255 0 Default Gateway 192 168 0 1 2 Select the Configuration tab and navigate to VOIP gt Network gt IP Settings 3 Select the Index to edit by doing one of the following a Click the O zero Index radio button and then click the Edit button b Addan Index by entering 1 in the box and pressing Add Index 4 Configure these settings Application Type OAMP Media Control IP Address The Mediant Gateway s IP address Prefix length The subnet mask length in CIDR notation Gateway The default gateway s IP address The VLAN ID 1 Interface Name Voice 5 Click the Apply button 6 Click the Done button when finished 7 Click the Burn button 43 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes e Help ar j n Status Maintenance amp Diagnostics f Search ame nne eae oeeo caer usw ereere OAMP Meda Control 17229 102 136 fs T zam i we LiP Settings rp Routing Table JQoS Settings SCTP Settings alons t Bl security a PSTN Sl signaling 2 Media HE Services Gill applications Enabling HE Control Network amp llsIP Definitions SiE
41. We POLYCOM Polycom SpectraLink 8400 Series with AudioCodes Mediant 1000 MSBG Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes April 2012 1725 36972 001 RevA Trademarks 2012 Polycom Inc All rights reserved POLYCOMB the Polycom Triangles logo and the names and marks associated with Polycom s products are trademarks and or service marks of Polycom Inc and are registered and or common law marks in the United States and various other countries All other trademarks are property of their respective owners No portion hereof may be reproduced or transmitted in any form or by any means for any purpose other than the recipient s personal use without the express written permission of Polycom Disclaimer While Polycom uses reasonable efforts to include accurate and up to date information in this document Polycom makes no warranties or representations as to its accuracy Polycom assumes no liability or responsibility for any typographical or other errors or omissions in the content of this document Limitation of Liability Polycom and or its respective suppliers make no representations about the suitability of the information contained in this document for any purpose Information is provided as is without warranty of any kind and is subject to change without notice The entire risk arising out of its use remains with the recipient In no event shall Polycom and or its respective suppliers b
42. X9 v PCM Law Select maw x System N TDM Bus Clock Source Netwok s nines TDM Bus PSTN Auto FallBack Clock Enable s inedia Satis TDM Bus PSTN Auto Clock Reverting Enable o l Iul sificotnn Idle PCM Pattern 255 Management Idle ABCD Pattern OxOF X Svor TDM Bus Local Reference b OO 7 oo TDM Bus Type ems pd TDM Bus Settings S Security c liPsTN cAS State Machines Trunk Settings H signaling HE Media S services HE Applications Enabling S Control Network Q sIP Definitions S Coders And Profiles cw and IP to IP S Trunk Group L Trunk Group Trunk Group Settings SE Manipulations _ General Settings Dest Number IP gt Tel Dest Number Tel gt IP M bu Source Number IP 7 Tel Submit moo mont Tel gt IP xj 4 Press Submit and Burn 98 Expanding your System c Modify PSTN Trunk Settings The Trunk Settings for the second PRI need to be modified Navigate to VoIP gt PSTN gt Trunk Settings and click on the 2nd trunk at the top of the screen This will apply regardless of whether the additional trunks are in the same module or two separate modules We now need to configure the same settings that we applied to the first trunk 1 Select the Configuration tab and navigate to VOIP gt PSTN gt Trunk Settings 2 Click the second trunk at the top of the screen 3 Modify these parameters Local ISDN Tone Ringback Source Gateway ff ppm OOO AI aa Na er n hn Py o
43. You can monitor D channel messages as well as see the digits that are sent and received for call setup in LD 96 of the CS1000 A 96 DCHOO0 enl msgi 33 This turns on D channel messaging monitoring for inbound calls on D channel 33 OUTPUT TARGETS TTY enl msgo 33 This turns on D channel messaging monitoring for outbound calls on D channel 33 OUIPUT TARGETS TIX The below shows the system s output when initiating a call from Unistim Extension 3404 to extension 7010 that resides on the AudioCodes Gateway DCH 33 UIPE OMSG CC SETUP RED REF 0000000B CH 325 235 TOD Orar CR SF 39B893 You may also gather a great deal of information about calls to and from the Mediant Gateway by examining the output of the Mediant Gateway s syslogs Syslog output will show called and received numbers on the PRI as well 107 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Resetting the Mediant Gateway Clearing the configuration Manual method If you have a situation where the box completely freezes you can reset it to factory defaults by inserting a paperclip in the tiny hole on the CPU board Hold it in for about 6 seconds until the LAN LED starts blinking and then release the clip The box will reboot and search for a new ini file Software method You may also reset the Mediant Gateway s configuration by loading an empty board ini file using the Web interfac
44. a LAN port on the CRMX module 34 Part II Configuring the Components Part Il covers the steps to configure the Mediant Gateway testing the handsets against the configuration and installing the Mediant Gateway in its permanent location Configuration requirements of the Communication Server 1000 are then covered in detail Some facilities may require additional capacity and expanding the system to increase capacity is covered in Chapter 10 Expanding your System 35 Chapter 6 Initial Configuration of the Mediant Gateway This chapter describes the procedure for initial configuration of a Mediant Gateway running software version 6 20 The default Mediant Gateway username and password is Admin and Admin respectively this is required when web browsing to the Mediant Gateway Instructions for changing it are in the last section of this chapter TN Caution Backup your configuration Save and backup your configuration when you complete the configuration steps below 1 Connect Mediant Gateway to a single computer Warning Do not connect the Mediant Gateway to the network Do not connect the Mediant Gateway to your corporate network before configuring it per the instructions in this chapter 1 Establish a connection between the Mediant Gateway and a single computer or laptop By default the Mediant Gateway has the following settings IP Address 192 168 0 1 Sub net 255 255 255 0 2 Change the Net
45. ach iub a Les a QC Basic Ful f Reting Index 1 80 v g eec m Tel To IF Routing Made Route calle betice manipulate w hal Se res Gi 1 4 M T x P Applvcetors Enebling er M M T I os et 1 i Sre Trunk a s Cech Desi IP Prolde x Sic satrol Network Group fb Dasi Phone Prefix Source Prone Prela E Cesi P Address Part Traraport Tree teGroup ID SR to Status isi Definitions 1 1 172 23 102 137 Bhan Het Cochgured wr 1 3 ji i ders And Profiles z iiw and iF fo iF r het Cesfigqures f 1 Si Trunk Group 4 Cesheures s i Marenulstinns i 1 2i cutng Hel Configured yy 7 iben red dolendi 5 ligt Configured cw SR v Tel t IF Routing Ra i m Trunk Group eating Subai Alte native Routing Reasons 5 Click Submit 59 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 12 Configure IP to Trunk Routing Configure IP to Trunk Routing is used to set up routing from IP telephony to PRI All calls that would not be routed internally to another SIP registration will be routed to the PBX 1 Select the Configuration tab and navigate to VOIP gt GW and IP to IP gt Routing gt IP to Trunk Group Routing 2 Set the following parameters Dest Host Prefix Source Host Prefix Dest IP Phone Prefix Source Phone Prefix Source IP Address i Trunk Group ID
46. all between two handsets then using the phone softkey redirect the call to the third handset using blind or attended transfer Verify the call is handed off to the third handset 77 Chapter 9 Communication Server 1000 Configuration Requirements You will need to verify that your system has the appropriate licensing installed to support the QSIG interface referenced in this guide Testing performed in Polycom s labs was performed using a system with the following Feature Packages related to QSIG Please contact your CS1000 service representative to help ensure you have all the packages installed on your system that may be required to allow the fullest interoperation and functionality e Feature Package 145 Integrated Services Digital Network e Feature Package 263 Q sig Interface e Feature Package 305 Q sig General Functional Protocol e Feature Package 316 Q sig Supplementary Service This configuration also assumes that the Communication Server 1000 is already installed in the facility and has at least one available PRI card Program the QSIG PRI The following is a brief overview of the steps taken to build and turn up a new QSIG PRI circuit on the Nortel CS1000 No Overlay Action 1 LD 17 Adding a PRI card 2 LD 17 Adding a PRI D Channel 3 LD 15 Defining a PRI customer 4 LD 16 Defining a PRI route 5 LD 14 Define PRI trunks 6 LD 86 Defining a Route List Index RLI 7 LD 87 Defining a Distance Steering Code 8 L
47. and Alone Survivability S1P Media Fl Data t l l E l l l HI l e l b 2 Configure these options SAS Local SIP UDP Port SAS Default Gateway IP SAS Registration Time SAS Local SIP TCP Port SAS Local SIP TLS Port SAS Binding Mode SAS Survivability Mode 3 Click the Submit button 52 SAS Local SIP UDP Port SAS Default Gateway IP SAS Registration Time SAS Local SIP TCP Port SAS Local SIP TLS Port SAS Proxy Set SAS Emergency Numbers SAS Binding Mode SAS Survivability Mode Enable ENUM Enable Record Route SAS Block Unregistered Users Redundant SAS Proxy Set SAS Inbound Manipulation Mode 1 Disable v Disable w Un Block v 1 M None v 5060 T lt Basic Parameter List Ka wo z a 3 Ld This allows the SAS application to send and receive SIP signaling on the Mediant Gateway s port 5060 The Mediant Gateway application s IP address and port i e ip address 5080 60 seconds When the phone is powered off or becomes unavailable this is the amount of time that elapses before the Mediant Gateway will provide a busy alert to caller See note below 5060 5061 1 User Part Only Always Emergency Initial Configuration of the Mediant Gateway Caveat What happens during the timeout Necessarily we have to set a time period for the Mediant Gat
48. and will be unique for each site For our example we used 2034 5 Defining PRI trunks The programming example below shows only the differences between the trunks we are created for the second Route and the trunks we created for the first Route in LD 14 Prompt Response TN XX y DES ACODE2 RTMB X y Description Loop and channel number for digital trunks For our example we used 341 Designator field for trunk Service route number and trunk member number For our example we used 34 1 6 Defining a Route List Index RLI The programming example below shows only the differences between the RLI created for the calls we wish to send to the first Mediant Gateway in LD 86 and the RLI we created for the calls we wish to send to the second Mediant Gateway Prompt Response RLI X ENTR 0 ROUT X Description Route List Index Number To Be Accessed For our example we created RLI 4 Use an available RLI This will be the first entry in the Route List Route number to be accessed This is the Route number you created in LD 16 For our example we used Route 34 91 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 7 Defining a Distance Steering Code DSC The programming example below shows only the differences between the DSC created for the calls we wish to send to the first Mediant Gateway in LD 87 and the DSC we created for the calls we wish to sen
49. ario Communication Communications Mir Server 1000 ji T1 Lines Mediant 1000 Gateway with two T1 modules 05 MM SpectraLink 8440 Wireless Handsets OR SpectraLink 8440 Wireless Handsets Admin Tip Allocate a second PRI card in the PBX You will need to install or allocate a second PRI card in the PBX for this configuration We will add the trunks on this card to the same route as one of our existing PRI s In this case Route 33 This will give us 23 additional channels in this trunk group Note that we are using FAS Facility Associated Signaling for this integration and consider that this provides better service should a single PRI failure occur 1 Add another DS1 to the PBX Earlier in this guide we detailed the process for building a single PRI circuit to a Mediant Gateway The process for building a second PRI that will be a part of the same route will be exactly the same except you will use a different TMDI card and define a new loop and trunk numbers appropriate to your environment am including only the portions that we changed for this second PRI in the examples below otherwise follow the format we used to build the first PRI 93 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 2 Adding a PRI card The programming example below shows only the differences between the second and the first PRI card we added using LD
50. ash Hook Period Enable Early Media Progress Indicator to IP Disconnect Call an Netectinn nf Rusv Tone No Fax Enable Not Configured Fnahle n Z Submit Initial Configuration of the Mediant Gateway 15 TDM configuration TDM Bus settings is used to configure the signal encoding used between the Mediant Gateway and the PBX 1 Select the Configuration tab and navigate to VOIP gt TDM gt TDM Bus Settings 2 If your physical channel is T1 set PCM Law Select to MuLaw For E1 set ALaw Note that there are very rare exceptions but this setting must match the configuration you create on the PBX side 3 Set TDM Bus Clock Source to Network Note Multiple Trunks If you have multiple trunks please see Chapter 10 Expanding your System 4 Click Submit E fg AudioCodes Mediant 1000 MSBG v Submit Q Burn Device Actions v A Home G Help ae Log off Status i ing Configuration Maintenance amp Diagnostics Basic Parameter List a Search O Basic Full v i PCM Law Select MuLaw v Dl system i TDM Bus Clock Source Network v Svor E i TDM Bus PSTN Auto FallBack Clock Disable v i Network aTom TDM Bus PSTN Auto Clock Reverting Disable v Tom Bus Settings Idle PCM Pattern 255 H Security Idle ABCD Pattern Ox OF v iin TDM Bus Local Reference 1 Signaling iea TDM Bus Type Framers v H
51. at sometimes the phone will give an unexpected response to a caller during this 60 second window 3 Caller ID display 26 Caller ID can also be confusing Let s look at three scenarios while referring to the diagram below in which Alice and Ben have 8400 phones on the same Mediant Gateway Dave has an 8400 phone on another Mediant Gateway and Cindy has a deskphone Rule On calls that traverse the PRI circuit the Called Party name is not passed back to the Calling party Scenario 1 Alice calls Ben Alice will see Ben s name since they are both registered on the same Gateway Scenario 2 Alice calls Cindy or Dave Alice will not see their name display unless previous calls to Alice from Cindy or Dave have already populated Alice s Call Log with these callers names Scenario 3 Cindy calls Dave Cindy will see Dave s number only Dave will see Cindy s name and number Features and Capacity AudioCodes Gateway B a a e 2 Scenario 1 ES ce Ben minm za Scenario 2 A I I i AudioCodes Gateway A Wired Ethernet i C m m i a rena 4 Music on Hold The Mediant Gateway does not provide music on hold or periodic tones to a caller placed on hold If a PBX station places an 8400 Series phone attached to the Mediant Gateway on hold music on hold will be heard if the PBX is configured to provide it 5 Calls per line Calls per line is an und
52. ateIndex REEL LL LL T tellN c P CMP file Load a CMP file from your computer to the device j gm Y CADocuments and Settings sanders Browse ile ee _Send File DATA file CPT file VP file a IMPORTANT 4 PRT file un Firmware upgrade was chosen CAS file e configuration is allowed at this stage USRINF file AMD file FINISH o 9 9 Previous Next Cancel Reset The software will load 116 Software Upgrade Procedure Firefox Y al i WE T mE ndr o o ZI Yess INI file DATA file CPT file VP file IMPORTANT PRT file ae Firmware upgrade was chosen CAS file e configuration is allowed at this stage USRINF file AMD file FINISH 999 Previous Cancel Reset The screen will display Firefox a m x MpiiT229 102 109SoftwareUpdetelndex lt 70 http 172 29 102 109 SoftwareUpdateIndex MpiiT229 102 109SoftwareUpdetelndex lt 70 o w e E Googe CMP file INI file mm File DATA file MP 500 MSBG SIP F6 204 045 001 cmp was ERA successfully loaded into the device CPT file VP file IMPORTANT p PRT file S 4 Firmware upgrade was chosen CAS file e configuration is allowed at this stage 4 USRINF file q AMD file b FINISH 2222 Previous Next Cancel Reset
53. ce not used in this deployment The LAN ports provide a LED that indicates operating status Color State Description On Ethernet link established Flashing Data is being received or transmitted Off No Ethernet Link Rear Panel Description 31 32 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Item Label L ESD 100 240V 1A Description Protective grounding screw Electrostatic Discharge ESD socket Dual AC Power Supply Entries Slots for housing optional components not used in this deployment Slots reserved for future use Chapter 5 Preparing the Mediant Gateway for Initial Configuration The Mediant Gateway must be configured with a direct connection to a provisioning computer before being connected to the LAN Insert the T1 E1 Module The T1 E1 module is shipped separately and must be installed Clear Kapton tape covers the gold edge of the module and protects the module s BUS line It must be removed before the module is inserted into the chassis Warning Remove the Kapton tape If the Kapton tape is not removed the module will not function and irreversible damage may be caused to the chassis Installing the T1 module into slot one 1 Ensure the Kapton tape is removed 2 On the device s front panel using a Phillips screwdriver remove the black metal cover plate protecting the module slot 3 In
54. ce path Check that the Caller ID is also appropriate From a station attached to the PBX dial an 8400 Ensure the calling party hears ringback and the called party s phone rings Answer the call and verify two way voice path Check that the Caller ID is also appropriate From an 8400 registered to the Mediant Gateway dial a station attached directly to the PBX Answer the call and initiate a transfer to another 8400 phone Verify you can successfully transfer the call From an 8400 registered to the Mediant Gateway dial a PSTN number such as your cell phone Remember to include the NARS code necessary to reach an outside line from the PBX just as you would from a station directly attached to the PBX Verify the PSTN number rings and can be answered with two way voice path Check Caller ID on both the 8400 and the PSTN phone If you register the 8400 phones as 4 digit extension numbers and then place calls to the PSTN the PBX may simply pass our 4 digit caller id from the 8400 phones to the PSTN dependent on the CS1000 s configuration The PSTN is likely to insert the Trunks Billed Telephone Number into this field as a response to what it perceives as an invalid Caller ID In this case the caller s actual DID number will not be presented Please refer to Chapter 12 Troubleshooting Section Program a 10 digit Caller ID in for a suggestion of one way to resolve this issue From an 8400 registered to the Mediant Gateway dial a
55. d to the second Mediant Gateway In the below example we set the DSC to a value of 71 with a length of 4 digits This would result in the PBX sending any number of the form 71xx to the RLI we built in the last step You might build several different DSC s to allow for several different number ranges to all be provisioned on the Mediant Gateway Prompt Response Description Enter as much of the unique pattern as you can easily define This example is assuming that all extensions on the Mediant Gateway will be of the form 71xx and as such we entered a value of 71 for our DSC DSC 5 value If for example we wanted all 7xxx numbers to be sent to this RLI we would just use a 7 If we wanted only calls to numbers of the form 701x to go out this PRI we would use 701 RLI Route List to be accessed for Distant Steering Code This is the Route List Index we built in the previous step In our Example it is RLI 4 8 Completing the Turn up of the PRI Follow the steps in the single PRI setup to enable and download this information to your TMDI card then enable the new Digital Loop you have built 92 Expanding your System Adding a Second PRI to an Existing Trunk Group on the PBX Another method of expansion is to add another trunk to the existing Mediant Gateway by either having a 2 port T1 module or adding a second T1 module The PBX does not recognize the difference but the Mediant Gateway will need to be configured differently for each scen
56. d previously Stripped Digits from Left 6 Stripped Digits from Right 0 Prefix to Add unknown Suffix to Add leave blank Initial Configuration of the Mediant Gateway E e AudioCodes Mediant 1000 MSBG y Submit Q Burn Device Actions w A Home G Help ae Log off mM DIAS Configuration Maintenance amp Diagnostics Search O Basic Full Oo Arey J lt HE system Svor H Network HTM security lPsTN HE signaling HE Media E HE Services HE Applications Enabling HE Control Network L siP Definitions H coders And Profiles Gw and IP to IP il Trunk Group cim ads Y Basic Parameter List gt Destination Prefix mm llli lw lt A v 3 Click Apply 10 Configure Mediant Gateway Trunk Group Settings 1 Select the Configuration tab and navigate to VOIP GW and IP to IP Trunk Group Trunk Group Settings 2 Set Index to 1 10 using the dropdown menu 3 Forrow 1 Trunk Group ID 1 Channel Select Mode Ascending Ascending assumes that the PBX uses Descending mode Therefore we are setting the opposite channel mode Double check with the PBX to ensure the opposite setting is used here Refer to the AudioCodes user manual for explanation about all supported channel select modes Registration Mode blank Serving IP Group ID blank 57 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Commun
57. e Firefox Admin Page Image Load to Device Parameters Output Window um e J Google Back to Main Parameter Name PSTNRESERVEDS Parameter New Value Parameter Description For future use 49 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Facility Trace Setting this parameter allows you to display the description of the facility messages in the syslog 1 Type FacilityTrace in the Parameter Name field and 1 in the Enter Value field 2 Click the Apply New Value button Firefox Lj Admin Page X EA Product Documentation amp Software Aud ParameterName FACLITYTRACE JEntervaueh PRESETS gt A amp nipuiizz 29102 108 AdminPage M Lr v 84 soogle Output Window Parameter Name FACILITYTRACE Parameter New Valus i1 Parameter Description Enable ISDN Facility Trace 3 Click Back to Main when finished 50 Initial Configuration of the Mediant Gateway 7 Enable SAS Application 1 Select the Configuration tab and navigate to VOIP gt Applications Enabling gt Applications Enabling 2 Using the drop down for the Enable SAS field choose Enable User Tip View the SAS option Tip If you do not see the SAS option as the last item on the VOIP menu ensure you have the Full radio button checked If it is still not visible return to the License section and double check to
58. e Save the Data configuration file to the PC Send the Data configuration file to the device a a _ Send Fite a 4 Click the Browse button corresponding to the Send INI File button navigate to the empty ini file select the file and then click Open Click the Send INI File button and then at the prompt click OK the device uploads the ini file and then resets the device to default settings based on the cmp file currently running on the device After a few minutes you should be able to browse back into the device using the same IP address the device had prior to restoring defaults Using the serial adapter cable see AudioCodes document LTRT 30300 Restoring Factory Defaults Technical Note A serial adapter cable ships with the Mediant Gateway and it is used when you cannot access the Mediant Gateway through the network It has a proprietary com port connector which is not commercially available through other sources Please keep this cable close to the Mediant Gateway in case troubleshooting is needed 109 Part IV Appendices Part IV contains Appendices Module Maintenance Software Upgrade Procedure and a sample ini file are included 111 Appendix A Module Maintenance The T1 module can be removed or added while the GW is operational but will not be activated until the Mediant Gateway is rebooted On the home screen select the module by pointing to the slot title Digital and double click A pop
59. e The only settings that are not restored to default using this method are the management OAMP LAN IP address the Default Gateway address and the Web interface s login user name and password How to prepare an empty ini file The ini file to be loaded must be empty i e contain no parameters or include comment signs i e semicolons preceding lines parameters One method to create this file 1 Open a new notepad doc do not type anything into it as text 2 Savethe document naming it empty ini The result should be a Okb file named empty ini To restore defaults using the Web interface 1 Prepare an empty ini file empty ini and save it in a folder on your PC 2 Logonto the Web interface 3 Open the Configuration File by doing one of the following a Onthe toolbar click Device Actions and then choose Load Configuration File Or b Open the Maintenance tab and navigate to Software Update gt Configuration File Troubleshooting Fa E prm erre re Submit Burn Device Actions UN Home Help de ed AudioCodes Mediant 1000 MsB6 A Q e 3 E Status a i Configuration haintenance amp Diagnostics i Search Save the INI file to the PC c Basic e Full Save INI File t ug Maintenance ciii Softwa re Update Send the INI file to the device i ILoad Auxiliary Files HiSoftware Upgrade Wizard i 5 i The device will perform a reset after sending the INI file L IConfiguration Fil
60. e liable for any direct consequential incidental special punitive or other damages whatsoever including without limitation damages for loss of business profits business interruption or loss of business information even if Polycom has been advised of the possibility of such damages Customer Feedback We are constantly working to improve the quality of our documentation and we would appreciate your feedback Please send email to VoiceDocumentationFeedback polycom com WE POLYCOM Support Visit support polycom com for software downloads product document product licenses troubleshooting tips service requests and more Contents BUYER COUR aoe ees ace ps E sess cans 9 Who Spould Read this GUJE rr sQ 9 Conventions Used in TNS GUNG M E E Are ER ERETT 9 Produ e UOO e A E E 11 A a E E E E A E 11 o ias aae A AAE A EA EA EAE AA 11 Polycom ReferenC ES ursssrriis ra a T E T E bd dn TH EMI NS Ed UPS 11 Pdo odes Rorer NCE eeraa S E EE INE EA E EE ENE saat ET 13 Part I The AudioCodes Solution eee eee 15 Chapter 1 Test OVER VIG Wissen scxexuc n susFxue uso kr ege EERAEEKECFERFEESRSEFEPEE CRF KE OME ENS NS EIE 17 Results OVEPVICW RR 17 me TeSt EO UM ONIC NG NIRE TT 18 Network a ero o ERIT TET TTE 18 OST GE c 20 AWO apol WIFI M 20 Chapter 2 What the Mediant Gateway Does
61. e ports are labeled I II Ill and III The maximum number of ports that can be utilized in any given system is four 29 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Note T1 Module The T1 Module is shipped separately from the chassis Each port provides a LED that indicates operating status Color State Description On Trunk is synchronized normal operation On Loss due to LOS Loss of Signal LOF Loss of Frame AIS Alarm Indication Signal the Blue Alarm RAI Remote Alarm Indication the Yellow Alarm Off Failure or disruption in the AC power supply or the power is currently not being supplied to the device through the AC power supply entry CRMX Module The single CRMX Module supports data routing switching security and voice security SBC capabilities The module provides three LAN ports a WAN port not used in this deployment and an RS 232 interface port Note CRMX Module The CRMX Module is installed in the chassis 30 Unpacking the Mediant Gateway Label Component Description I Ul Ul 10 100 1000Base T Ethernet LAN ports for connecting computers and or switches lolo RS 232 port for accessing the CLI A 9 pin DB adaptor cable is supplied Reset pinhole button for resetting the device and restoring the device to factory defaults See Resetting the Mediant Gateway 0 0 WAN WAN Interfa
62. egional Settings Certificates S Management 2 VoIP H pata 4 Click Submit 46 wv NTP Settings NTP Server IP Address NTP UTC Offset NTP Updated Interval 172 29 0 37 Hours Minutes o Minutes w Day Light Saving Time Day Light Saving Time Start Time End Time Offset min o f e v NFS Settings NFS Table gt w DHCP Settings Enable DHCP Disable v w VoIP Monitoring Settings VoIP Monitoring Mode Disabled v S 4 t Pes c Ld Initial Configuration of the Mediant Gateway 6 Set Syslog Parameters Syslog traces are important tools for troubleshooting issues and it is strongly recommended that you have a syslog server set up The recommended setting allow for maximum logging without sacrificing system quality 1 Select the Configuration tab and navigate to System gt Syslog Settings 2 Enable Syslog 3 Set the Syslog Server IP address and the Syslog Server Port Leave the Port setting at the 514 default 4 Set Debug Level to 7 5 Ensure all checkboxes are checked as in screen below Fa UH Submit Burn Device Actions w 4 Home Help e Lo g off we AudioCodes Mediant 1000 MSBG v y G 5 n Status i Configuration Maintenance s Diagnostics Search w Syslog Settings O Basic Full Enable Syslog i system Syslog Ser
63. en aran EE TAA T I EEO ATANT EANO E A 109 Part IV Appendices ssessessessossossossossossoessessessessessessessess LLL Contents Appendix A Module Maintenance cscscscsscscscsccccscsccccccscsccccccscsccccscncess 113 Appendix B Software Upgrade Procedure ccccscsssscscescscescscsccccsceccsceees 115 Appendix C Sample Files eere eee nenne nennen nennen nennen ones 119 Sample AtudioCodss ni TING erasini E Econ Er Eu ed pe RERUPPENERI seus EEEE AEEA 119 Sample Phone Configuration Files seen e x Fex etum Px Ix eo PrPK HEY eK Pe Co FxUAT FONS PUn IR M03 Tan ua up FI IY TRE n a En cx rsen Uu E 127 Appendix D Information needed when you Contact Polycom Support 129 Introduction This guide will help you understand how the Mediant Gateway functions and offers configuration parameters for the Avaya PBX to establish interoperability This document describes a solution developed in Polycom s wireless laboratories to deploy its advanced SIP wireless handsets the 8400 Series within non SIP telephony facilities This solution is comprised of an Avaya Nortel Communication Server 1000 and an AudioCodes Mediant 1000 MSBG Gateway which provides SIP service to Polycom SpectraLink 8400 Series SIP handsets SpectraLink 8400 Series a Wireless Handset AudioCodes Communications Mediant 1000 Gateway server 1000 T QSIG Wired Ethemet The general test approach had the Spect
64. endpoint registered to the same Mediant Gateway a multiple Mediant Gateway system will require PBX channels to place calls between phones registered to different Mediant Gateways The third measurement to consider is the number of endpoint to endpoint calls to from handsets registered to a single Mediant Gateway We have seen that the Mediant Gateway will directly connect locally registered SpectraLink 8400 handsets with each other and this type of call does not require connection through a PBX In some environments this type of call could be the most prevalent In other facilities we would expect heavier use of a PBX Every installation is unique and must be evaluated accordingly Capacity Analysis The Mediant Gateway can support up to 600 handsets on the SIP side of the system This means that if all calls were placed only between SIP handsets 300 simultaneous calls would be possible However the T1 trunk has 23 channels and this is the limiting factor when calls are routed through the PBX Each call uses at least one of these channels and if multiple lines are deployed then one handset could potentially utilize as many channels as it has lines Therefore any analysis of capacity requirements must study the ratio of the endpoint to endpoint usage against the demands that will placed upon the PBX and the T1 line Multiple PRIs installed in the Mediant Gateway solve the capacity issue to some degree Each T1 module can support up to four T1 tru
65. eneceseueceeeuseeeaeecesseeenens 96 TWO PRI interfaces in one FAL nodUle xscsesisvorcsicrktue teur tni gor adii 96 Two PRI interfaces in two T1 modules eeeeseeeeseeeneeenen nennen nnns 97 b Add Second PRI as Clock SOUTEB iso arie M pRe vuU EXE Cet PN FUE Sex ER POSU S OP CEEE GA EE RNV ge VU pU RUM nNE 98 c Modify PSTN Trunk SettihBScccesedeveurstbeiuvente pube rra uS UE Omne PUE nIu caieswvei Pc En EE Pu us Er FT En eu PU MMC PS 99 Part Ill Deployment Testing and Troubleshooting 101 Chapter 11 Testing Mediant Gateway to PBX Functionality 103 Chapter 12 Troubleshooting ecce eene eee rennen nnne nnn nnne 105 gc m 105 Pat Renigcemellbi oos quu etc sins sees dibUtu diputado sto Manera RUNE Pp MESE D MM D DRM MEM EES A 105 TTY OM STRE 105 Qoi 202701 tt e 105 Qoigrt X1 O 106 Program a 10 digit Caller D s r 106 perito gis eee 010 2 RENTE raria eni ian EEEE EEE REEE A 107 Resetting the Mediant Gateway cccccsccssscccsscccseccceseecenceeeucceeceeecseueeteusceeeeeeueeeenseeeuceeeseeeneeneess 108 RIoidTetopus cmooeiieiatisio tT eirian nN NE ENERE E EN ANE NENEA RAAE 108 EIIE TYAS CIO e A E E e 108 S OTe Ee O NNI TT AA AA I AEA 108 Using ne senal adop er CODE orrir
66. er GOL sesacssesecnsciessevaivenbyunstasebuesivnasdvorbues uasteduousaveavuvnstiesulunesasiuetieaedenstidsveeuss 63 TA EWA OVE arny MEU Em 64 TONK OU IL ON Rm 65 16 B Channel negotiation MET 66 Contents DF ce SOCEM CPO GINS FIR MR IT 67 Q931 Layer Response Bea VIO st sanacaiassetectacetinvetsctetansadeteninesdasntacernnatacaueiennstesetocssinesaactoteiuccuunttes 69 ler CHG Gi WIV PAS Tolo 70 Chapter 7 Installing the Mediant Gateway ccccccscscssscsscscecsccscsccccccscsseece 71 Mo nt tne Mediant St BO auae UST Isi Dreves emet eras ena Evae T EH EN died brc p e Ubi Pa e MR snc 71 POS ICO TI OU 1075 PRRRERRRTN RR E EEE TEE EE TE OIE EEE EET A EE EEEE 71 TIA ROC MOUNTO TR REENE AEEA E TETEE ENEE EEEE AEE EEEE EE 73 Cabling the Mediant GateWOV caicicsintdccssaccecaccdestesevesdccscrntesasanddaniewsiveieseavaceanend sautunvardsousicbapanibessvnadncnt 74 Mol na cesa e TOG Colleen Tm 74 COTO CHINO TOC IAIN 75 Connecting TO ELTI TANS TT EE 75 Connecting TO oc CT T M 76 Chapter 8 Test Basic FUNCtIONALItTY scsccccscsceccccscsccccccscsccccccscsccccecscsseecs 77 Chapter 9 Communication Server 1000 Configuration Requirements 79 POS Te Cl Pi CR d d MER T 79 CAE a PREESPU S et nt an er re ener er eter eee ere ee 80 VINE 01 aor Reds RD Ero ats 1a g Emm 80 BS Fi er re ice Ri T R
67. erlying capability needed for several of the above features but is not considered a feature in its own right 6 Speed dial Speed dial is configured locally at the 8400 PBX configured speed dial for groups for example are listed separately 7 Contacts Directory Contacts are configured locally at the 8400 PBX configured Directory is listed separately 8 PBX based features PBX features include forward conference transfer do not disturb system group speed dials 9 Caller ID during transfers Let s look at three scenarios while referring to the diagram below in which Alice and Ben have 8400 phones on the same Mediant Gateway Dave has an 8400 phone on another Mediant Gateway and Cindy has a deskphone Scenario 1 Alice calls Ben who transfers the call to Dave When the transfer is complete Dave s phone will see Ben s caller ID not Alice s displayed on his screen Alice s phone will show that she is talking to Dave Scenario 2 Alice calls Dave who transfers the call to Cindy When the transfer is complete Alice continues to see Dave s caller ID not Cindy s displayed on his screen Cindy s phone also shows Dave s Caller ID not Alice s 27 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Scenario 3 Alice calls Cindy who transfers the call either to Ben or to Dave When the transfer is complete Ben or Dave then see Cind
68. eway to realize that the handset is not available Any timeout creates a window of time where the phone could be turned off or out of range during which calls that come to it will not respond in the usual way The caller will hear only silence not a busy tone or a ring Too short a timeout will over burden the Mediant Gateway with repeated registration requests In this document we have recommended a 60 second timeout with the understanding that sometimes the phone will give an unexpected response to a caller 53 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 8 Configure Mediant Gateway Application SIP parameters 1 Select the Configuration tab and navigate to VOIP SIP Definitions General Parameters 2 Configure these options SIP UDP Local Port SIP TCP Local Port SIP TLS Local Port Tel to IP No Answer Timeout 5080 5080 5081 Change this value to 60 seconds to match the SAS Registration Time Note What happens during the timeout silence not a busy tone or a ring r ed AudioCodes Status Submit Burn Mediant 1000 MSBG aS j Q Device Actions v A Home The 60 second timeout creates a window of time where the phone could be turned off or out of range during which calls that come to it will not respond in the usual way The caller will hear only gt Search O Basic 9 Full H system
69. files GS Gw and IP to IP SS Data i H HA Click Start Software Upgrade ed AudioCodes Mediant 800 v Submit Q Burn Device Actions Yv i Home e Help 7 Log off Configuration Maintenance S DANS Search O Basic Full amp lE Maintenance Start Software Upgrade I software Update Load Auxiliary Files L Software Upgrade Key _ Software Upgrade Wizard lL Configuration File Click the button to start the software upgrade process Warning Once software upgrade commences the upgrade process cannot be cancelled In case of an upgrade failure the device will reset and the previous configuration saved to flash will be restored You will be prompted for the cmp file Browse to the location and click the file 115 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Firefox 7 Software Upgrade Wizard Mozilla Firefox http 172 29 102 109 SoftwareUpdateIndex E CNP file j Load a CMP file from your computer to the device ile Se Send File DATA file CPT file a oe VP file IMPORTANT PRT file C Firmware upgrade was chosen CAS file e configuration is allowed at this stage USRINF file AMD file FINISH 599 Previous Cancel Reset press Send file Firefox 7 L http 172 29 102 109 SoftwareUpd
70. g Si om cim aal ncoming s Behavior C609 o uL za system Tem aie T S vorp General Call Control Behavior G l Network ISDN NS Behaviour 2 gt HTM NFAS Group Number Ht security IUA Interface ID pst n P NFAS Interface ID CAS State Machines Trunk Settings D channel Configuration PRIMARY l GS signaling Hl Media US services l ED Applications Enabling m it sip Definitions Transfer Mode Disable v Rings And Profiles Local ISDN Ringback Tone Source Gateway v z a and IP to IP Set PI in Rx Disconnect Message Not Configured CUMSAS i xe Not Confi v t ip Media ISDN eens Capabilities igured u r g Ar AX LD prn 4 Press Submit and Burn Reboot the Mediant Gateway 99 Part III Deployment Testing and Troubleshooting Part Ill covers the deployment of the solution in a functional environment and adjusting the configuration to provide specific functionality for certain features as needed Testing features and resetting the Mediant Gateway are also covered here 101 Chapter 11 Testing Mediant Gateway to PBX Functionality Outgoing Call to PBX Station Incoming Call from the PBX Transferring a call from a PBX Station to the 8400 Outgoing Call to the PSTN Call Hold amp Resume From an 8400 registered to the Mediant Gateway dial a station attached directly to the PBX Ensure the calling party hears ringback and the called party s phone rings Answer the call and verify two way voi
71. git extensions i e 70xx so we used a value of 4 here If your extensions were 5 digits long define FLEN as 5 Route List to be accessed for Distant Steering Code This is the Route List Index we built in the previous step In our Example it is RLI 3 Configuration Requirements of the CS1K 8 Working with the TMDI card After building our TMDI MSDL Card in the CS1000 s configuration we will want to enable the card and force a download to it The example below shows how to enable a TMDI card using LD 96 In this example 4 0 3 is the Loop shelf and card number of the TMDI card we installed After the download the TMDI card should show as enabled if you stat it again Note If using a MSDL card instead of a TMDI card please consult the NTP s for the equivalent commands Getting the Status of the TMDI cL 96 DCH000 Db tmdi TMDI 004 0 3 MAN DSBL Here we can see our new card is disabled Enabling a TMDI Card and Forcing a Download to it This loads the New D channel s configuration Ald 96 DCH000 enl tmdi 4 0 3 fdl This enables the TMDI card in slot 3 shelf O loop 4 and forces a download OK Disabling a TMDI Card Not Required This section not required as part of the PRI turn up It is provided for reference only You may need to do this if you make changes to a D channel and then want to load the new configuration into the card You would follow this up by re enabling the TMDI and forcing a download gt ld
72. gramming example below shows how to create service channels and PRI trunks using LD 14 For all other fields not listed in the example press RETURN to use default values Prompt REQ TYPE TN PCML DES CUST RTMB CLS Response NEW 23 TIE XX y MU ACODE1 0 XY UNR DTN Description Create 23 new trunks Trunk type Loop and channel number for digital trunks For our example we used 331 System PCM law Designator field for trunk Customer number Service route number and trunk member number For our example we used 331 Trunk Class Of Service 6 Defining a Route List Index RLI This step describes the creation of a Route List Index that we will use to allow callers dialing extensions that will reside on the Mediant Gateway out the Route we created previously The programming example below shows how to define the Route List Index RLI using LD 86 For all other fields not listed in the example press RETURN to use default values Prompt REQ CUST FEAT RLI ENTR ROUT Response new 0 RLB Description Create a new route list Customer Number Route List Block Route List Index Number To Be Accessed For our example we created RLI 3 Use an available RLI This will be the first entry in the Route List Route number to be accessed This is the Route number you created in LD 16 For our example we used Route 33 83 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Comm
73. guration Maintenance amp Diagnostics Basic Parameter List a Search Broken Connection Timeout 100 msec 100 O Basic Full Disconnect Call on Silence Detection No v Sl System i Silence Detection Period sec 120 l Svor Silence Detection Method Voice Energy Detectors v F ll Network Enable Fax Re Routing Disable v ToM Sl Security v CDR and Debug llesTN CDR Server IP Address Sidi es 3 mo CDR Report Level Start amp End amp Connect Call v H Media Gi Debug Level 7 v a Services H Applications Enabling cg p E p Progress Indicator to IP Not Configured v c sip Definitions a Enable X Channel Header Disable v General Parameters Le Advanced Parameters Enable Early 183 Disable v Account Table Enable Busy Out Disable v E Proxy amp Registration Graceful Busy Out Timeout sec 0 B Coders And Profiles Default Release Cause 3 Sl Gw and IP to IP i osas Max Number of Active Calls 200 v EP Media H Data Nu Submit wi 48 v Initial Configuration of the Mediant Gateway Configure additional syslog trace settings Additional trace settings should be set on the Admin Page PSTNreserved3 Configures the low level PSTN i e Q931 trace messages to be sent to syslog 1 Enter AdminPage after the IP address in the browser as shown in the screen below 2 Select ini Parameters in the Nav pane on the left 3 Enter PSTNReserved3 and the value 8 4 Click Apply New Valu
74. hazard that Caution A Warning could potentially impact device performance application functionality or successful feature configuration The Warning icon highlights an action you must perform or avoid to prevent issues that may cause you to lose information or your configuration setup and or affect phone or network performance The Troubleshooting icon highlights information that may help you solve a Settings relevant problem or to refer you to other relevant troubleshooting resources The Settings icon highlights settings you may need to choose for a specific behavior to enable a specific feature or to access customization options A few typographic conventions listed next are used in this guide to distinguish types of in text information Convention Bold Description Highlights interface items such as menus soft keys file names and directories Italics Also used to represent menu selections and text entry to the phone Used to emphasize text to show example values or inputs and to show titles of Underlined Blue reference documents available from the Polycom Support Web site and other reference sites Used for URL links to external Web pages or documents If you click on text in Blue Text this style you will be linked to an external document or Web page Used for cross references to other sections within this document If you click on Fixed width font text in this style
75. ications Server 1000 Deployment Application Notes tS AudioCodes of Status zoc m Basic Parameter List arom Sal Security estn Sl signaling Sl media HE Services Gl Applications Enabling Sl Control Network SIP Definitions Sl coders And Profiles Cl GW and IP to IP C liTrunk Group Group Trunk Group Settings Sli Manipulations H Routing SIE DTMF and Supplementary HE Analog Gateway Sl Digital Gateway Sl advanced Applications asas 4 Click Submit 58 Initial Configuration of the Mediant Gateway 11 Configure Tel to IP Routing Configure Tel to IP Routing is used to set up routing from PRI to the SAS application which manages the IP phone registration 1 Select the Configuration tab and navigate to VOIP gt GW and IP to IP gt Routing gt Tel to IP Routing 2 Set Routing Index to 1 10 using the dropdown menu 3 Set Tel to IP Routing Mode to Route calls before manipulation 4 For Index 1 set or ensure Source Trunk Group ID 1 Destination Phone Prefix Source Phone Prefix Dest IP Address Mediant Gateway IP Address Port Set to the configured SAS port i e 5060 Transport Type Not Configured Dest IP Group ID 1 a Payee Sumit Q Bum Diken ations oF ga Home Help 2 Mindiunt dod MERG n7 y Lag nif E wl AudioC odes Y amp sad tabs conn gure HINHBIHEKS o Diago Basar lP oramnterit Se
76. ing Mounting of the equipment in the rack should be such that a hazardous condition is not achieved due to uneven mechanical loading Circuit Overloading Consideration should be given to the connection of the equipment to the supply circuit and the effect that overloading of the circuits might have on overcurrent protection and supply wiring Appropriate consideration of equipment nameplate ratings should be used when addressing this concern Reliable Grounding Reliable grounding of rack mounted equipment should be maintained Particular attention should be given to supply connections other than direct connections to the branch circuit e g use of power strips To mount the device on a pre installed shelf in the rack Place the device on a pre installed shelf in the rack We recommend attaching the device s integral front mounting brackets to the rack s frame to prevent it from sliding off the shelf during cabling Use standard 19 inch rack bolts not provided to fasten the front of the device to the frame of the rack To install the device in a rack without shelves 1 Position the device in a 19 inch rack and align the front and rear refer to note below bracket holes to the holes of your choosing in the vertical tracks of the 19 inch rack 2 Use standard 19 inch rack bolts not provided to fasten the brackets to the frame of the rack 73 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1
77. ior ISDN NS Behaviour 2 NFAS Group Number IUA Interface ID NFAS Interface ID D channel Configuration v Trunk Configuration Basic Parameter List a Local ISDN Ringback Tone Source and set it to Gateway asig ling Sl Media Sil services S Applications Enabling Sl Control Network SIP Definitions Sl coders And Profiles amp liGw and IP to IP ncoming Calls iim V oacri000 aa 05 cC General Call Control Behavior x0 ISDN NS Behaviour 2 x NFAS Group Number 0 IUA Interface ID 1 NFAS Interface ID 255 D channel Configuration PRIMARY t T PSTN Alert Timeout Transfer Mode Local ISDN Ringback Tone Source Gateway Set PI in Rx Disconnect Message lt Not Configured ISDN Transfer Capabilities Not Configured b Click Apply Trunk Settings 68 v S Apply Trunk Settings Initial Configuration of the Mediant Gateway Q931 Layer Response Behavior A m LPL S m a Pa tT SR UH Nn Te pi Vor NYSE ig lia SI cg fF EN pe IN iti MP na SGW and IP to IP osas w ISDN Configuration Sibi Medis ISON Termination Side S pata Q931 Layer Response Behavior Outgoing Calls Behavior 1 Scroll up to the Q931 Layer Response Behavior option and click the arrow to the right of the Q931 Layer Response Behavior row 2 Set QSI ENCODE INTEGER to 1 This is the usual setting for an Ava
78. l SrcIPGroupID Nu umberMaplpZTe L e TORF wu cte A905 4e Us oor eday 9o Cd eds NNumberMapIp2Tel 123 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes TABLE SourceNumberMapIp2Tel SourceNumberMapIp2Tel FORMAT SourceNumberMapIp2Tel Index SourceNumberMapIp2Tel DestinationPrefix SourceNumberMapIp2Tel SourcePrefix SourceNumberMapIp2Tel SourceAddress SourceNumberMapIp2Tel NumberType SourceNumberMapIp2Tel NumberPlan SourceNumberMapIp2Tel RemoveFromLeft SourceNumberMapIp2Tel RemoveFromRight SourceNumberMapIp2Tel_LeaveFromRight SourceNumberMapIp2Tel_Prefix2Add SourceNumberMapIp2Tel Suffix2Add SourceNumberMapIp2Tel IsPresentationRestricted SourceNumberMapIp2Tel SrcTrunkGroupID SourceNumberMapIp2Tel SrcIPGroupID oourceNumberMaprlo2Tel b e 95 Sy Te 299p 299p 05 0595 309599y 4 Zoos l SourceNumberMapIp2Tel p TABLE SourceNumberMapTel2lIp SourceNumberMapTel2Ip FORMAT SourceNumberMapTel2Ip Index SourceNumberMapTel2Ip DestinationPrefix SourceNumberMapTel2lIp SourcePrefix SourceNumberMapTel21Ip SourceAddress SourceNumberMapTel2Ip NumberType SourceNumberMapTel2Ip NumberPlan SourceNumberMapTel2lIp RemoveFromLeft SourceNumberMapTel21p RemoveFromRight SourceNumberMapTel2Ip LeaveFromRight SourceNumberMapTel2Ip Prefix2Add SourceNumberMapTel2Ip Suffix2Adad SourceNumberMapTel2Ip IsPrese
79. ll D system ldk 4 Click Apply and Burn Mediant 1000 MSBG v Submit Q Burn Option 2 Time offset Option 42 NTP server Option 150 TFTP server Qos Aim Use Additional DNS Server bata SENS Additional DNS Server 0 0 fo o DDNS Option 66 TFTP Server Name Pee DNS Server Option 67 Boot File Name fo Ho le Jo Ho je IP Address Distribution 4 Device Actions G7 Home e Help Log off Disabled SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Disable the DHCP Client 1 Select the Configuration tab and navigate to System gt Application Settings 2 Under DHCP Settings gt Enable DHCP select Disable 3 Click Submit r 3 TTE e Cuusem Vids ex vd AudioCodes Device Actions x i ome e elp 3 Log off 4 Mediant 1000 MSBG Gy sent Q 9 Status eonun erence oues NTP Server IP Address 172 29 0 37 NTP UTC Offset Hours Minutes 0 NTP Updated Interval Hours Minutes p w Day Light Saving Time Day Light Saving Time Disable Start Time Jan l 01 i Regional Settings _ Certificates Sl Management VoIP Data a a End Time Jan w 01 i Offset min NFS Table m w DHCP Settings Enable DHCP Disable wv VoIP Monitoring Settings
80. munications Server 1000 Deployment Application Notes 126 SASRegistrationManipulation FORMAT SASRegistrationManipulation Index SASRegistrationManipulation RemoveFromRight SASRegistrationManipulation LeaveFromRight SASRegistrationManipulation 0 QO 0 NSASRegistrationManipulation w TABLE COdersGroupU CodersGroupO FORMAT CodersGroupO Index CodersGroupO Name CodersGroup0_pTime CodersGroupO rate CodersGroupO PayloadType CodersGroupO0 Sce CodersGroupO 0 qgTllUlawo4k 20 0y 1l 03 CodersGroup0O 1 g711Alaw 64k 20 O0 1 0 CodersGroubpO 2 g729 20 0 cL 0 NCodersGroupO Sample Phone Configuration Files Sample Files Below is a sample of the configuration files used by an 8400 phone during the course of the testing In this example we utilized MAC specific configuration for a phone with the MAC address of 00907a0cd96e Filename 00907a0cd96e cfg lt xml version 1 0 standalone yes gt lt APPLICATION APP_FILE_PATH sip 1ld CONFIG FILES srip 7O0l cfg fwd crg MISC FILES LOG FILE DIRECTORY OVERRIDES_DIRECTORY CONTACTS DIRECTORY 2 LICENSE DIRECTORY gt Filename sip_7001 cfg lt PHONE_CONE IG gt lt reg reg l address your extension number goes here reg l displayName your name goes here reg l label 2 your extension number goes here reg l auth userId your extension number goes here reg l auth password
81. ndex 1 55 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Module From Trunk To Trunk Channels Phone Number Trunk Group ID Use the dropdown list to select the correct module 1 23 1 30 for E1 Enter 100000 see note below User Tip Setting a sensible Phone Number The Phone Number is the starting point of a range of numbers that the Mediant Gateway uses internally When choosing a phone number choose a range of numbers that is outside the range of extensions used in your facility The range will be from the configured phone number to the phone number plus the number of DSO voice channels i e for a single T1 23 channels the Mediant Gateway would use extensions 100000 through 100022 We are using 100000 here as it is unlikely that any facility will have extensions of this length DO NOT USE EXTENSIONS THAT ARE USED ELSEWHERE IN THE SYSTEM 5 Press the Submit button To set unknown text to display if the Caller ID is not provided 56 1 Select the Configuration tab and navigate to VOIP GW and IP to IP Manipulations Source Number Tel IP 2 Adda source Trunk Group by entering 1 in the field and clicking the Add button Set or verify the following parameters Source IP Group Destination Prefix Source Prefix 1000xx This number is derived from the Phone Number entered in the Group Index for the Trunk Group configure
82. ne Code Line Build Out Loss Trace Level B8ZS O dB Full ISDN Trace to produce all messages in syslog Line Build Out Overwrite Framing Method OFF T1 FRAMING ESF CRC6 important to verify that this setting matches the PBX In many cases the PBX may not use CRC6 in which case select the appropriate variant from the dropdown menu ISDN Termination Side User Side PRIMARY D channel configuration 67 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes f Fa vl AudioCodes Search Mediant 1000 MSBG v Submit Burn pum mw Status Maintenance amp Diagnostics OBasic Full Sal system Svor Gl Network aTom Sl security 2l pst1n Licas State Machines Sl signaling HE Media services Gill applications Enabling Sl Control Network Elsp Definitions i coders And Profiles amp liGw and IP to IP asas alip Media 2 pata Scroll to m og nn Module ID Trunk ID Trunk Configuration State Inactive C Device Actions X A Home e Help General Settings Protocol Type B T1 QSIG Clock Master Auto Clock Trunk Priority b E Line Code pzs 1 1 1 1 wj Line Build Out Loss DB wj Trace Level Line Build Out Overwrite Framing Method ISDN Termination Side Q931 Layer Response Behavior Outgoing Calls Behavior Incoming Calls Behavior General Call Control Behav
83. nks and each Mediant Gateway can support up to four T1 modules but the number of PRIs is limited to four therefore the capacity of any single Mediant Gateway is 92 channels 23 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Additional Mediant Gateways can be added to increase capacity using the same formula as above In almost every scenario the trunk interface voice channels should not have a 1 1 mapping with telephony extensions Instead the trunk interface is configured to dynamically support more SIP end points than the actual channels In fact tying channels to specific extension is undesirable as it prevents features requiring more than one active line such as transfer forward hold etc Typical business handset usage during busy hours requires somewhere between 0 1 and 0 2 voice circuits per user extension to the PBX In other words each voice channel to the PBX from the Wi Fi handset users can support between 5 and 10 users In more traditional telephony terms each user requires between 100 and 200 milli Erlangs of capacity to the PBX Using the 100 milli Erlang calculation 230 handsets could be supported per T1 PRI which has 23 voice DSO channels Each Mediant Gateway has a simultaneous registration maximum of 600 so here again the usage factor is critical to accurate deployment capacity Features Tested and Validated The SpectraLink 8400 Series handsets
84. nly Sample board ini file Board Mediant 1000 MSBG Serial Number 3437322 olot Numbers i Software Version 6 20A 054 DSP Software Version 624AE3 gt 620 10 Board IP Address L72 29 102 137 Board subnet Mask 255 255 255 0 Board Default Gateway 172 29 102 1 Ram Size 512M Flash size 64M Num of DSP Cores 8 Num DSP Channels 48 Profile NONE Key features Board Type Mediant 1000 MSBG IP Media Conf VXML VoicePromptAnnounc H248 9 ExtVoicePrompt 1MB DSP Voice features IpmDetector Coders G723 G729 GSM FR G727 ILBC ElTrunks 4 TiTrunks 4 DATA features Routing FireWall amp VPN WAN Advanced Routing PSTN Protocols ISDN IUA 4 CAS Channel Type RTP DspCh 240 IPMediaDspCh 240 Security IPSEC MedraEncryption StrtongLneryption EneryptControlProtocol Control Protocols MGCP MEGACO SIP SASurvivability MSFT Default features Coders G711 G726 Slot 4 Module type of ports of DSPs P 1 FALC56 s 2 2 Empty 119 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 120 3 Empty r 4 Empty 5 Empty A 6 Empty SYSTEM Params syslogsServerIP 172 29 606 97 EnableSyslog 1 NTPServerIP 172 29 0 37 NTPServerUTCOffset 25200 ENABLEPARAMETERSMONITORING 1 ACETVICUNPSLUIOLOg tsveoty Sari Tdr or Nib owu y ry PM VEDSPUtil Va ow iu b BSP Params 3 TDMBusClockSource 4 PCMLawSelect Anal
85. ntationRestricted SourceNumberMapTel2Ip_ SrcTrunkGroupID SourceNumberMapTel2Ip SrcIPGroupID SourceNumDberMspleds2TDp 3 5 XXX 4 20964 Zoo Ou OY Zoar Unknown y Bog dr wes NSourceNumberMapTel2Ip suem ABRE JeUthPEerl 5 124 Sample Files PstnPrefix FORMAT PstnPrefix Index PstnPrefix DestPrefix PstnPrefix TrunkGroupId PstnPrefix SourcePrefix PstnPrefix SourceAddress PstnPrefix ProfileId PstnPrefix SrcIPGroupID PstnPrefix DestHostPrefix PstnunPrerix SrcHOStPrefix PstnPretix Trunklgd PGW Wet xe D zc b S WES Ga epe A COS See PstnPrefix p SS TABLE Ti unkoroudposLtemgs Uwe TrunkGroupSettings FORMAT TrunkGroupSettings Index TrunkGroupSettings TrunkGroupId TrunkGroupSettings ChannelSelectMode TrunkGroupSettings RegistrationMode TrunkGroupSettings GatewayName TrunkGroupSettings ContactUser TrunkGroupSettings ServingIPGroup TrunkGroupSettings MWIInterrogationType lrunkGeroup5ettaongogs 0 14 4 Z299y g y aly 2557 NTrunkGroupSettings po CUT TABLE Proxyset 9 ProxySet FORMAT ProxySet Index ProxySet EnableProxyKeepAlive ProxySet ProxyKeepAliveTime ProxySet ProxyLoadBalancingMethod ProxySet l sProxyHotSwap ProxySet SRD Proxyset Classiricationinput ProxySet ProxyRedundancyMode Proxyset O Uz O0 Oy UO Uz Uz L5 ProxySet TABLE SASRegistrationManipulation 125 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Com
86. og Params ControlProtocols Params AdminStateLockControl 0 MGCP Params MEGACO Params EP Num 0 EP Num 1 EP Num 2 EP Num 3 Oo 0 pP rn c EP Num 4 ebd naa epos PSTN Params TraceLevel 1 ProtocolType 23 FramingMethod D ISDNIBehavior 1073741824 PSTNReserved3 8 SS7 Params Voice Engine Params WEB Params LogoWidth 145 HIIPSCIphersScring tRBOATEXE SIP Params LOCALSIPPORT 5080 BCHANNELNEGOTIATION 0 CDRREPORTLEVEL 4 GWDEBUGLEVEL 7 ENABLEEARLYMEDIA ENABLEMWI 1 IPALERTTIMEOUT 60 TCPLOCALSIPPORT 5080 5081 LOCALISDNRBSOURCE 1 TLSLOCALSIPPORT SASDEFAULTGATEWAYIP 172 29 102 137 5080 ENABLESAS 1 SASLOCALSIPUDPPORT 5060 SASREGISTRATIONTIME 60 SASLOCALSIPTCPPORT 5060 SASLOCALSIPTLSPORT OUI SASBINDINGMODE 1 SASSURVIVABILITYMODE 1 Sample Files 121 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 122 FACILITYTRACE 1 SCTP Params VXML Params IPsec Params Audio Staging Params SNMP Params o ASA IRBLE Intertscelable InterfaceTable FORMAT InterfaceTable Index InterfaceTable ApplicationTypes InterfaceTable InterfaceMode InterfaceTable IPAddress InterfaceTable PrefixLength InterfaceTable Gateway InterfaceTable VlanID InterfaceTable InterfaceName Poter race La Me qc LO dede dz d i
87. on defined on the PBX as part of a block that belongs to the Mediant Gateway see Chapter 9 Section 7 Defining a Distance Steering Code DSC is sent to the Mediant Gateway and is not found to be currently registered or if that station was simply never built but happens to reside within the range of extensions defined on the PBX to be sent out to the Mediant Gateway If we do not perform this step the Mediant Gateway would send a call to an unregistered station back to the PBX The PBX would check its rules and send these calls back to the Mediant Gateway This could go on for some time In our testing this routing loop eventually resolved itself without eating up all of the bearer channels on the PRI and the calling party was presented with a re order tone However we can make more efficient use of our resources and provide callers with a better indicator of what has happened Options for handling such calls could include routing them to a vacant extension to a recorded announcement back on the PBX telling callers that they have dialed a number that is currently unavailable Or you could have them ring to a desk station somewhere Alternatively you could route them to a non existent number on the PBX and callers would simply be given a re order tone 1 Navigate to VOIP gt GW and IP to IP gt Manipulations gt Dest Number IP gt Tel 2 Adda Destination Index for each unique block of extensions you have defined on the Mediant Gateway
88. pt DLOP MG_CARD Response 34 Supl sh card Description This will be another available Loop Number in your system pick one appropriate to your environment Loop shelf and card number of your TMDI card For our example we used 004 0 04 3 Adding a PRI D channel The programming example below shows only the differences between the second and the first D channel we added using LD 17 Prompt ADAN MG Card DES DCHL 90 Response NEW DCH X Supl sh card ACODE2 XX Description Add a primary D channel any unused SDI port x 0 79 Primary D channel Number Choose a D Channel Number appropriate to your environment For our example we used D channel 34 Loop shelf and card number of your TMDI card For our example we used 004 0 04 A name for the D channel Use something appropriate for your installation The D channel Number you are assigning for this D channel For our example we used D channel 34 Expanding your System 4 Defining a PRI route The programming example below shows only the differences between the second and the first Route we added using LD 16 Prompt Response ROUT X DES ACODE2 ACOD XXXX Description Route number you wish to create For our example we matched the Route and D channel numbers and created ROUT 34 This is a name for the route You may call it whatever you want Trunk access code This will need to fit into your dialplan
89. quently configuration options for the SAS component and the PRI component of the Mediant Gateway must be configured 21 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes How Stand Alone Survivability Application Works The SAS application is an optional capability of the Mediant Gateway but is mandatory for the SpectraLink solution It is a robust solution originally designed for system redundancy but this document only describes its application to the SpectraLink solution SAS Emergency State The Mediant Gateway solution operates the SAS application permanently in the Outbound Proxy mode in the emergency state This means SpectraLink SIP handsets use the Mediant Gateway SAS application as a proxy and calls are routed via the Mediant Gateway trunk to the PBX AudioCodes Mediant Gateway Access points rar fa SpectraLink 8440 Wireless Handsets When the Mediant Gateway receives calls from a SIP device it searches its SAS registration database to locate the destination address according to AOR or Contact If the destination address is found in the SAS registration database the call is placed to the other SIP device and no PBX functionality is required If the destination address is not found i e it is not another SIP device registered on this Mediant Gateway the SAS application forwards the call to the core Mediant Gateway application which in turn
90. r Cat 5e two pair Category 5 UTP cable to any of the module s LAN ports 2 Attach the other end of the cable directly to the LAN network e g to a Ethernet switch or computer Connecting to E1 T1 Trunks The procedure below describes the cabling of the device s TRUNKS module interfaces i e E1 T1 trunks Use a T1 crossover cable T1 Crossover Cable Loopback Plug amp Note This is not included with the PBX T1 crossover cable T568B The image displayed shows the cross over cable pinout 1 HN BE forastandard T1 This cable should be plugged into jack provided by the Carrier and your Pss E your Smartjac 2 PBXtra s PRI card Sangoma A10X model of cards 4 B EN 4 Alternatively Smartronix example sells T1 E1 or 5 mM BS 5 ISDN PRI crossover adapters same wiring different 6 m ES 6 colors one is pale greenish white or mint the other is 7 NW Bcw 7 yelow omm za amp If purchasing an adapter make certain you get at least one crossover adapter Loopbacks are for testing T1 loopback plug RJ 45 Plug To protect against electrical shock and fire use a 26 AWG min wire to connect T1 or E1 ports to the PSTN To connect the digital trunk interfaces 1 Connect the E1 T1 trunk cables to the ports on the device s TRUNKS module s 2 Connect the other ends of the trunk cables to your PBX PSTN switch T SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deploymen
91. raLink 8400 Series handsets register as SIP telephones with the Mediant Gateway The test verified that calls could be routed through the Communication Server 1000 when PBX call routing was required i e when connecting to a telephone other than the handsets registered to the same Mediant Gateway The test also verified that the SpectraLink handsets were able to call each other without going through the PBX Basic telephony features were tested Who Should Read this Guide This guide is designed for Polycom system engineers who will be installing the AudioCodes devices and site based system administrators and network engineers who may need to alter the LAN to accommodate the equipment PBX administrators should be on hand to manage the PBX configuration requirements and test the system before its deployment Conventions Used in This Guide The following icons are used to alert you to various types of important information in this guide Name Icon Description Note The Note icon highlights information of interest or important information needed to be successful in accomplishing a procedure or to understand a concept Administrator The Administrator Tip icon highlights techniques shortcuts or productivity Tip related tips SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Name Icon Description The Caution icon highlights information you need to know to avoid a
92. ration is complete conduct a test of basic handset functionality following the following table These tests exercise the handsets connectivity with the Mediant Gateway without using the PBX link Registration Outgoing Call Incoming Call SIP URL Call Up to 6 call appearances per line Call Hold amp Resume Speaker amp Mute Do Not Disturb DND Transfer Attended Unattended After powering on the phone check the Mediant Gateway s AoR screen and check the handset s line registration status Dial another 8400 handset or SIP endpoint registered with the Mediant Gateway Verify that a call path is established The test does not require the PRI link Have another registered SIP endpoint call a registered 8400 ensure the handset rings and a call path is established The test does not require the PRI link Call an 8400 directly using the IP address This bypasses the Mediant Gateway If this call fails there may be basic network issues Each line registration supports by default 24 calls per line This may be changed using the configuration parameter When in call use the hold feature to hold the active call Retrieve the call using the resume button When in call try the handset mute and speakerphone capability Using the handset set the DND capability and try calling the handset it should not ring and the calling party should receive an busy tone If three wireless handsets are available set up a c
93. re we tell the system to disable loop 33 The preceding OK message tells us the system understood but it is still common practice to stat the loop again to verify it is truly in a disabled state OK ld 60 DITODO enll 33 OK 87 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 10 Working with the D Channel Not required Disabling a D channel This section is not required as part of the PRI turn up However you may need to disable the d channel to allow you to make configuration changes to it or in order to disable the Digital Loop The example below shows how to disable the D channel using LD 96 gt Id 96 DCHOO0 sdis dch 33 Here we disable D channel number 33 DCH 33 RLS CONFIRM TIME 0 25 11 26 07 2000 Enabling a D channel This section is not required as part of the PRI turn up In fact it would normally occur automatically when you enable the digital loop However you may find it reasonable to enable and disable just the d channel without bouncing the Digital Loop as well The example below shows how to enable the D channel using LD 96 gt jd 96 DCHOOO enl dch 33 DCH 33 EST CONFIRM TIME 0 33 13 26 07 2000 Note Test the configuration If you are not adding multiple T1 s PRI s then your configuration should be complete at this point and you should skip forward to the testing section to verify functionality
94. see that SAS is available 3 Click the Submit button 4 Use Device Actions to reset the Mediant Gateway User Tip The Lightning Bolt Icon Any parameter that has the lightning bolt symbol will require a reset in order to take effect f uu H E J i Y Ke A 7a UH A f Submit Q Burn Device Actions rv f Home Help d wt AudioCodes ecient 1000 MSG v Q M Wy e w Fl Status cations Enabling Search O Basic Full Enable SAS Enable v H system Svor HE Network aTom H Security amp llesTN E signaling media services S Applications Enabling JApplications Enabling H control Network E sip Definitions SE Coders And Profiles lGw and IP to IP osas EP Media H Data amp Submit 51 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Configure SAS 1 Select the Configuration tab and navigate to VOIP gt SAS gt Stand Alone Survivability r a AudioCodes Submit Burn Mediant 1000 MSBG v Q Device Actions v A Home G Help J Log off m a Status Configuration Malntenance amp Diagnostics Search O Basic Full H System Svor Network tom Gli Security Gl PSTN GS signaling Gli Media Services E Applications Enabling GS Control Network sip Definitions GS Coders And Profiles cw and IP to IP sas St
95. sert the required module into the empty slot use slots 1 5 for the T1 module aligning the module with the rails in the slot in the following module orientation depending on whether you are inserting it in the top or bottom row slots 33 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes o Top row slots ensure that the module is orientated such that the port number labels are located at the bottom of the module s front panel This module orientation is considered as facing up o Bottom row slots ensure that the module is orientated such that the port number labels are located at the top of the module s front panel This module orientation is considered as facing down 4 Push the module into the slot and press on it firmly to ensure it has been fully inserted 5 Using a flathead screwdriver tighten the module s mounting pins Connect to Power Connect to Computer Warning Do not connect the Mediant Gateway to the network Do not connect the Mediant Gateway to your corporate network before configuring it Connect the Mediant Gateway to the power supply e On the device s rear panel connect the left active 100 240V 50 60 Hz power socket to a standard electrical outlet using the supplied AC power cord Connect the Mediant Gateway to the PC to be used for initial configuration e Use your own network cable to connect the PC or laptop network port to
96. st was conducted on an Communications Server 1000 running version 5 50J However Polycom supports this solution on versions ranging from 5 0 to 6 1 The screens and parameters displayed in this document should be similar on all supported versions Network Topology The solution tested at the Polycom 8400 laboratories consisted of a Communications Server 1000 an AudioCodes 1000 Mediant Gateway and SpectraLink 8400 handsets Four different configurations were tested as shown in the following diagrams The handsets were already operational in the wireless network and that exact infrastructure is not directly relevant to this application note 18 The basic configuration Communications Server 1000 Ti Line Lom Mediant 1000 Gateway with one T1 module SpectraLink 440 Wireless Handsets The three expansion configuration options Communications Communication t n Server 1000 Server 1000 T1 Lines Mediant 1000 Gateway with two T1 modules act M Mediant 1000 Gateway with ane T1 module with two parts FEIN SpectraLink 440 Wireless Handsets SpectraLink 6440 Wireless Handsets Test Overview 19 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Communications Server 1000 Two Mediant 1000 Gateways Each with one T1 module AM opectraLink 6440 Wireless Handsets Why Q SIG When integrating
97. stinctive Ring N Y HD Voice Siren Codec N Y Per Line Authentication N Y 29 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Footnotes 1 Core Features Core Features reside locally in the handset but require some interaction with the Mediant Gateway and PBX These features work only as long as the phone is registered and turned on If the phone is turned off registered to a different user or moves out of range for an extended period of time calls to the handset are neither received nor forwarded When the phone is unavailable the Mediant Gateway must provide a fallback option for how to handle these calls We specify where to send calls like these in Chapter 3 section 12 Avoiding a Routing Loop 2 Incoming Outgoing calls Incoming Outgoing calls include to from another 8400 a TDM or proprietary VoIP desk phone and a trunk What happens during the timeout Necessarily we have to set a time period for the Mediant Gateway to realize that the handset is not available Any timeout creates a window of time where the phone could be turned off or out of range during which calls that come to it will not respond in the usual way The caller will hear only silence not a busy tone or a ring Too short a timeout will over burden the Mediant Gateway with repeated registration requests In this document we have recommended a 60 second timeout with the understanding th
98. t Application Notes 14 Enable Early Media To prevent clipping of audio when first connecting an IP call Early Media should be enabled You might notice this type of clipping when first connecting to an IVR or Voicemail system if this parameter is not enabled r 1 Select the Configuration tab and navigate to VOIP Coders and Profiles Tel Profile Settings 2 Set Enable Early Media to Enable ra AudioCodes Submit Burn Mediant 1000 MSBG aS Q 64 Basic 9 Full Device Actions 7 Log off aL 7 Status Configuration Maintenance amp Diagnostics Search w m system voir GSNetwork ToM security GSPSTN H Signaling media services E Applications Enabling GS Control Network W sIP Definitions Coders And Profiles Coders Coders Group Settings Tel Profile Settings LJIP Profile Settings l amp iGw and IP to IP osas iP Media ad Data E HI i E bI b HI HI l b Profile ID Profile Name Basic Parameterlist A E w Profile Parameters Profile Preference Fax Signaling Method Dynamic Jitter Buffer Minimum Delay msec Dynamic Jitter Buffer Optimization Factor RTP IP DiffServ Signaling DiffServ Voice Volume 32 to 31 dB DTMF Volume 31 to 0 dB Input Gain 32 to 31 dB Dial Plan Index Enable Digit Delivery Echo Canceler Fl
99. t Application Notes Connecting to Power The device can house up to two extractable power supply modules Power 1 and Power 2 each providing an AC power connector on the device s rear panel The dual power option provides the device with power redundancy Warning Protection against electrical shock e Units must be connected by service personnel to a socket outlet with a protective grounding connection e Use only the AC power cord supplied with the device Note Using both power units e f both power units are used for load sharing failure protection redundancy ensure that you connect each power supply unit to a different AC supply circuit e The two AC power sources must have the same ground potential Connect the device to the power supply On the device s rear panel connect the left active 100 240V 50 60 Hz power socket to a standard electrical outlet using the supplied AC power cord The front panel of the power supply module provides a LED labeled POWER that is lit green when the device is powered up If this LED is off a power supply problem may be present Color State Description The LED of each AC power supply is lit green when the power supply is operating correctly Off Failure disruption in the AC supply or the power is currently not being supplied to the device through the AC power supply entry 76 Chapter 8 Test Basic Functionality Once the Mediant Gateway configu
100. teway A brief summary of commands to use in the CS1000 is presented below in the Monitoring a D channel section of this Troubleshooting section Caution Toll fraud warning This configuration will increase your system s exposure to toll fraud Call Forward If users want to be able to Call Forward from extensions on the PBX to mobile extensions you need to set the Class of Service of the phone that is doing the forwarding to a CLS that does not Restrict Call Fwd Off Net 1 CS1000 Check parameters o Checkthe current CLS of the station by printing the TNB associated with the terminal The terminal needs to have a CLS of CFXA rather than CFXD to allow Call Forwarding Off Net 105 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Ensure with the customer that it is ok to toggle this field if all stations with this CLS that have the need to forward to extensions on the Mediant 1000 Gateway be modified to allow call forward off net For some customers this may be a toll fraud concern 2 CS1000 Change value O Ensure that stations have the correct NCLS and TGAR to allow dialing out the new route you have created Caller ID Program a 10 digit Caller ID In some cases you may wish to modify the Caller ID that you are sending In the examples used in this application note we were sending a four digit Caller ID because that is how we registered the
101. teway and Avaya Nortel Communications Server 1000 Deployment Application Notes http supportdocs polycom com PolycomService support global documents support setup maintena nce products voice SpectraLink 8400 Deployment Guide pdf The comprehensive Polycom UC Software Administrators Guide covers all configuration parameters for the 8400 Series Wireless Telephones It is available at http supportdocs polycom com PolycomService support global documents support setup maintena nce products voice UC Software Admin Guide v4 O 1 pdf Other documents pertaining to the SpectraLink 8400 Wireless Handsets are available at http support polycom com PolycomService support us support voice wi fi spectralink 8400 wireless html 12 Introduction AudioCodes References AudioCodes references are available at http www audiocodes com downloads Select the options as shown in the next screen to display a list of relevant documents S _ f X3 AudioCodes where to buy i 3 F Pid English Spanish Login Register Custom Search SEARCH Lll CORPORATE SOLUTIONS PRODUCTS PARTNERS NEWS amp EVENTS INVESTORS SERVICES Homepage gt Product Documentation amp Software gt Support Overview gt Professional Services Channel Services Product Warranty Information Repair Centers Customer Support Program gt Technical Training Product gt Documentation amp Software Web Based Technical Training Microsoft UC S
102. uces you to the Mediant Gateway and how it solves the problem of using Polycom SpectraLink 8400 Series SIP endpoints with a Communication Server 1000 PBX This solution was tested in the Polycom labs and the details of the test configuration and its results are covered here This Part also guides you through unpacking the Mediant Gateway and preparing it for configuration 15 Chapter 1 Test Overview The Polycom SpectraLink 8400 Series Wireless Handsets utilize standards based SIP telephony signaling In order to deploy these handsets in a facility that uses a legacy non SIP PBX call server a device that converts the signal as it passes between the handset and the PBX is required This document describes the Mediant Gateway solution and provides guidelines for provisioning the Mediant Gateway and PBX when used in conjunction with a Communications Server 1000 The Mediant Gateway provides a bridge between the SpectraLink 84xx wireless handsets and the Communications Server 1000 a PBX that offers traditional telephony interfaces such as T1 or E1 The Mediant Gateway transparently manages the protocol translation and interworking between the two systems enabling deployment of advanced wireless VOIP technology without a complete overhaul of an existing system Due to variations in facility systems many configuration options exist This document covers the basic setup that was tested in the Polycom laboratories and demonstrates the workabilit
103. ue hd mcum diea dy MON O InterfaceTable TABLE DspTemplates Ihis table contains hidden elements and will not be exposed Ihis table exists on board and will be saved during restarts aoe TABLE PREFIX 2 Sample Files PREFIX FORMAT PREFIX Index PREFIX DestinationPrefix PREFIX DestAddress PREFIX SourcePrefix PREFIX_Profileld PREFIX_MeteringCode PREFIX DestPort PREFIX SrcIPGroupID PREFIX DestHostPrefix PREFIX DestIPGroupID PREFIX SrcHostPrefix PREFIX IransportIype PREFIX oSrcrlrunkGroupIlID PREFIX D estSRD PREFIX QU Laaa Sa eLa pe Se De woo soU Ske y E e Sle ay i PREFIX ee TABLE IIPUNGEOHD oS TrunkGroup FORMAT TrunkGroup Index TrunkGroup TrunkGroupNum TrunkGroup FirstTrunkId TrunkGroup FirstBChannel TrunkGroup LastBChannel IrunkGroup FirstPhoneNumber TrunkGroup ProfileId TrunkGroup LastIrunkId ITrunkGroup Module Drunkoeroub Qt Ule 1900000 OO Oy 43 NTrunkGroup wka TABLE NumberMaplp2lel NumberMapIp2Tel FORMAT NumberMapIp2Tel Index NumberMapIp2Tel DestinationPrefix NumberMapIp2Tel SourcePrefix NumberMapIp2Tel SourceAddress NumberMapIp2Tel NumberType NumberMapIp2Tel NumberPlan NumberMapIp2Tel RemoveFromLeft NumberMapIp2Tel RemoveFrFromRight NumberMapIp2Tel LeaveFromRight NumberMapIp2Tel Prefix2Adq NumberMapIp2Tel Suffix2Add NumberMapIp2Tel IsPresentationRestricted NumberMapIp2Tel SrcTrunkGroupID NumberMapIp2Te
104. unications Server 1000 Deployment Application Notes 7 Defining a Distance Steering Code DSC This step describes the creation of a Distance Steering Code that we will use to direct the digits we provision on the Mediant Gateway out the RLI we defined In the below example we set the DSC to a value of 70 with a length of 4 digits This would result in the PBX sending any number of the form 70xx to the RLI we built in the last step You might build several different DSC s to allow for several different number ranges to all be provisioned on the Mediant Gateway The programming example below shows how to define the Distance Steering Code DSC using LD 87 For all other fields not listed in the example press RETURN to use default values Prompt REQ CUST FEAT TYPE DSC FLEN RLI 84 Response new 0 CDP DSC Description Create a new route list Customer Number Coordinated Dialing Plan Distance Steering Code Enter as much of the unique pattern as you can easily define This example is assuming that all extensions on the Mediant Gateway will be of the form 70xx and as such we entered a value of 70 for our DSC value If for example we wanted all 7xxx numbers to be sent to this RLI we would just use a 7 If we wanted only calls to numbers of the form 701x to go out this PRI we would use 701 Flexible Length number of digits This is the total length of the extensions you will be dialing Our example uses 4 di
105. up Remove Module will appear Click and follow the instructions Caution AX If you only have one T1 card you will get an error message as removing the card will make the Mediant Gateway inoperable and calls will be terminated not allowed If you need redundancy you will need two T1 cards Once the removal is done the slot title will display Digital Reserved To insert the new module double click the slot title and insert the new module The module will be recognized You may have to reboot the Mediant Gateway in order for the module to activate Appendix B Software Upgrade Procedure When you need to upgrade the software follow this procedure Obtain the software from your service representative It will be a cmp file Download or copy it to a location where you can retrieve it Use Device Actions and select Software Upgrade Wizard to open the wizard 7a UH Submit Burn Device Actions Home Help e Log off wi AudioCodes l Mediant 800 y Q a G M g Load Configuration File i Save Configuration File atus Configuration Maintenance 5 Diagnostics Reset Software Upgrade Wizard Search Opasic O Full al __ Aaa index H system Svor Application Type Interface Mode network _JIP Settings pns GSPSTN GS Media WAN Interface Name Not Configured Services G9 Applications Enabling GS Control Network sip Definitions H coders And Pro
106. upport Library Microsoft Training Glossary Product Documentation amp Software Note For some products you will need to be logged in in order to download files In orderto access partner specific documentation please select your relevant solution and refer to the downloads tab under the following direct URLs Avaya ww w audiocodes com avaya Broadsoft ww w audiocodes com broadsoft Genesys ww w audiocodes com genesys Microsoft ww w audiocodes com microsoft Skype ww w audiocodes com skype Please note you may need the generic AudioCodes product documents in addition to the solution partner specific guides and files Product Family Enterprise Access Media Gateways Product Group Digital Media Gateways Vv Product Mediant 1000 v Version 6 0 General Availability Vv Protocol SIP v Documentation Note Mediant Gateway DOCUMENTATION FEEDBACK We welcome your feedback Please use this form to tell us about any errors comments and suggestions regarding AudioCodes product documentation Please enter your details and we will contact you shortly Name Email Country Select v Product Type Choose v Protocol v n ONU LL s idd SW Version Documentation type w Throughout this guide the term Mediant Gateway refers to the AudioCodes Mediant 1000 MSBG Gateway 13 Part I The AudioCodes Solution Part introd
107. ur example we used 341 TN XX y DES ACODE2 Designator field for trunk Service route number and trunk member number For our example we RTMB X y used 33 24 since these new trunks will be the 24 through 46 members of the Route 6 Completing the Turn up of the PRI Follow the steps in the single PRI setup to enable and download this information to your TMDI card then enable the new Digital Loop you have built 95 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 7 Configure the Mediant Gateway On the Mediant Gateway side there are two possibilities the first is that we have a single T1 module with two PRI interfaces in it and the second is that we have two separate T1 modules each with a single PRI interface Trunk Group settings need to be changed depending on which system you are using a Change the Trunk Group settings Two PRI interfaces in one T1 module 1 Select the Configuration tab and navigate to VOIP gt GW and IP to IP gt Trunk Group gt Trunk Group 2 Change these settings Module From Trunk To Trunk Channels Phone Number Trunk Group ID Tel Profile ID e AudioCodes r uL 5 Status Search Select the module for the second PRI The same module as the first PRI 1 23 100024 Begin with the next available channel number Mediant 1000 M SBG v Submit eo Burn Device Actions v n Home e Help
108. ver IP Address IApplication Settings Syslog Server Port Syslog Settings Debug Level L Regional Settings Analog Ports Filter Certificates Trunks Ports Filter 1 Management T A vorp v Activity Types to Report via Activity Log Messages H pata Parameters Value Change Auxiliary Files Loading Device Reset Flash Memory Burning Device Software Update Access to Restricted Domains Non Authorized Access Sensitive Parameters Value Change S s S S S ST fS fI S Login and Logout v Submit 6 Click Submit 47 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes Set CDR Reporting CDR Call Data Record information is helpful when interpreting syslog traces Here again we set the option for the most robust reporting 1 Select the Configuration tab and navigate to VOIP gt SIP Definitions gt Advanced Parameters 2 Scroll down to the CDR and Debug section 3 Optionally you may set the CDR Server IP Address If not set it will log to the syslog server IP address set in the previous step 4 Set CDR Report Level to Start amp End amp Connect Call 5 Click Submit f ra w Submit Burn Device Actions w Home Help Log off 3 v AudioCodes Medianti000 Ms8G wA Q MEE e Mr Status iD E Confi
109. wn key Once you get a file with the correct key 1 Copy the key and paste it into the Add a Software Upgrade Key field key highlighted in yellow 2 Press the Add Key button 3 The key content appears in the display window Verify the key content meets the minimum requirements 4 Use Device Actions to Reset the Mediant Gateway 40 Initial Configuration of the Mediant Gateway 3 Disable DHCP Client and Server Disable the Device s DHCP Server In order to avoid conflict with another DHCP server during this initial configuration you must disable the DHCP server 1 Select the Configuration tab and navigate to Data gt Data Services gt DHCP Server 2 If Enabled click the pencil icon N to edit the settings 3 Click the down arrow as shown below and select the Disabled option Click OK l Submit Burn Device Actions v 4 Home e Help Log off CG AudioCodes muse oos O p Status coe EA Search IP Address Distribution DHCP Server M OO Disabled O Basic Full Start IP Address 2 _MIS DHCP Server End IP Address 192 system m Subnet Mask el ate WINS Server Swan Access Firewall and ACL Lease Time in Minutes Provide Host Name If Not Specified by Client HE Data Routing H objects and Rules H Data System fe AudioCodes Search i Status Configuration Maintenance 3 Diagnostics O Basic Fu
110. work Config of the pc to match the Mediant Gateway s default network settings i e 192 168 0 100 255 255 255 0 3 Open a browser and enter the IP address of the Mediant Gateway http 192 168 0 1 4 When prompted enter the default username Admin and password Admin Note the capital A 37 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes The Home screen The Home button opens the Home screen which displays information you may need as you proceed with configuration steps The below example shows a configured Mediant Gateway For more information about the Home screen see the User Guide The Home page shows the status of Mediant Gateway components Any component of the simulated product image can be clicked to display operational information or additional configuration options Verify the Firmware Version is 6 20A 054 If it is not this specific version follow the Software Upgrade Procedure in Appendix B Software Upgrade Procedure 7a w Submit Burn Device Actions v e Home Help g Log off w AudioCodes Modiant 1998 MG M Q E e aul P Contiguretion Maintenance amp Diagnostics Search O Basic Full t Gl System Hi VoIP HE Data General Information Trunk Digital Modules IP Address 172 29 102 137 Disable Subnet Mask 255 255 255 0 E sis Active OK dad Default Gateway
111. y s caller ID not Alice s displayed on his screen Alice also still show s Cindy s Caller ID AudioCodes Gateway B Wired Ethernet A Pee LI 9 ve ET aan s s a Scenario I s Ld Rosie 7 Ben transfers A IC e Alice to Dave Ben i Wired Ethernet 3 d E e Scenario 3 ore d in aae ipm ciim 2zz22277 press viel d ean6 Alice to Ben or r y TA Dave AN Fo Y s L4 se L me i Me d e T Scenario 2 Dave a En transfers Alice to Cindy a Da ve 28 Chapter 4 Unpacking and Familiarizing Yourself with the Mediant Gateway Package Contents Mediant Gateway shipments arrive with a large box for the Mediant Gateway and power cable and a smaller package containing the T1 module You will need to supply Ethernet cables and a T1 crossover cable for each T1 module deployed Front Panel Description Item Label Description 1 T1 Telephony modules 2 CRMX or CMX Hosts either the CRMX module for data routing or the CMX module CPU for VoIP Mediant Gateway functionality 3 Power 1 Optional Spare Power Supply module slot 4 Power 2 Main Power Supply module 5 Extractable Fan Tray module with a schematic displayed showing the chassis slot numbers T1 E1 Module The chassis supports up to four digital E1 T1 J1 modules The module is available in 1 2 or 4 span configurations providing RJ 48c ports not RJ45 Th
112. y of this solution For detailed configuration information as it applies to your facility please refer to the administrative or user manuals of the respective products This document does not cover other functionality of the Mediant Gateway how to configure the Communications Server 1000 how to deploy a WLAN or how to configure the SpectraLink 8400 Series Wireless Handsets for wireless connectivity These subjects are covered in other documents referenced below Results Overview During the compliance testing the Polycom SpectraLink 8440 84580 8452 was able to register as a SIP client endpoint with the Mediant Gateway which routed calls to the Communication Server 1000 only when PBX call routing was required The Polycom SpectraLink handsets were able to place and receive calls routed through the Communication Server 1000 and also place and receive calls with other 8400 Series endpoints through the Mediant Gateway without any PBX involvement The compliance tests focused on basic telephony features 17 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes The Test Equipment The following equipment and software were used during the lab test Table 1 Equipment Software Firmware Communications Server 1000 v 5 50J AudioCodes Mediant 1000 w SAS option v 6 20A 054 SpectraLink 8440 Handsets UCS 4 0 2 8017 Communication Server 1000 software version supported The te
113. ya and other PBX If left at O the Mediant Gateway will use ASN 1 encoding 3 Click Submit r z J as AudioCodes Mocdkant 4888 AASE v Submit Q Burn Device Actions w A Home G Help 7 s ua Configuration Maintenance g Diagnostics Search O Basic Full Q931 Layer Response Behavior E Bit Hex Value Bit Name avor 0x000001 NO STATUS ON UNKNOWN IE Sli Network 0x000002 NO STATUS ON INV OP IE aTom 0x000004 ACCEPT UNKNOWN FAC IE El Security 0x000080 SEND USER CONNECT ACK SPsTN 0x000200 EXPLICIT INTERFACE ID Licas State Machines 0x000800 ALWAYS EXPLICIT oe 0x008000 ACCEPT MU LAW Bless 0x010000 EXPLICIT PRES SCREENING Glill cervices 0x020000 STATUS INCOMPATIBLE STATE al Applications Enabling 0x040000 STATUS ERROR CAUSE I Control Network 0x080000 ACCEPT A LAW as p Definitions 0x200000 RESTART INDICATION S coders And Profiles 0x400000 FORCED RESTART Il Gw and IP to IP 0x40000000 QSI ENCODE INTEGER asas 0x80000000 SESS National Mode For Bch Maintenance Custom Mod SP Media D Data amp t EE 3 4 Use Device Actions to reset the Mediant Gateway 69 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 18 Changing the Password Please secure your system by changing the login username and password 1 Select the Configuration tab and navigate to System gt Management gt Web User
114. you will be taken to another part of this document Used for code fragments and parameter names This guide also uses a few writing conventions to distinguish conditional information Convention lt MACaddress gt Description Indicates that you must enter information specific to your installation phone or 10 network For example when you see lt MACaddress gt enter your phone s 12 digit MAC address If you see lt installed directory gt enter the path to your installation directory Indicates that you need to select an item from a menu For example Settings gt Basic indicates that you need to select Basic from the Settings menu Introduction Product Support Avaya Contact your Avaya service representative for help with configuration of the Avaya Nortel Communications Server 1000 The parameters recommended in this document assume familiarity with the equipment and are not meant to replace expert configuration knowledge Polycom Polycom wants you to have a successful installation If you have questions please contact the Customer Support Hotline at 1 800 POLYCOM 1 800 765 9266 The hotline is open Monday through Friday 6 a m to 6 p m Mountain time See Appendix D Information needed when you Contact Polycom Support for important information about how to get the most from your support call For Technical Support mailto technicalsupport polycom com For Knowledge Base http support polycom com
115. your PC s IP address to one that will be able to communicate with the Mediant Gateway s new IP address if required 2 Click the Home button The LAN icon should show green Under General Information double check the IP Address subnet mask and Default Gateway parameters are as expected f z J ra 7 v Submit Burn Device Actions w Home e Help cS Log off f 3 AudioCodes 7 Mediant 1000 MSBG Q x A w x a Status Configuration Maintenance g Diagnostics Search O Basic 9 Full H system Dvor HE Data m 1 Protocol Type SIP AIS Alarm Gateway Operational State UNLOCKED e E E E 45 SpectraLink 8400 Series with AudioCodes Gateway and Avaya Nortel Communications Server 1000 Deployment Application Notes 5 Set NTP settings A NTP server will provide necessary time service to your phones allow the Mediant Gateway to time stamp logs and assist in any troubleshooting should the need to investigate any issues ever arise 1 Select the Configuration tab and navigate to System gt Application Settings 2 Enter the NTP server IP address 3 Set NTP UTC offset to your local GMT time r fed AudioCodes Status Contiguration Malntenance amp Diagnostics Mediant 1000 MSBG Submit Burn w Q Device Actions w i Home e Help Search O Basic Full S system Application Settings ISyslog Settings R

Download Pdf Manuals

Related Search

Related Contents

AEMC PowerPad Model 3945-B Power Quality Analyzer  Composition Propriétés et caractéristiques Mode d`emploi  Chapter 5 Contacts  Graco 332564B User's Manual  ClinicalKey User Guide Edition 2.0  Fisher-Price J5293 User's Manual  

Copyright © All rights reserved. Failed to retrieve file