Technical Information Bulletin Number: ATIB - 1036 System: ipecs 50/100/300/600/1200 PHASE 5.5 (&6.0) Topic: Configuring SIP CO trunks & SIP extensions Product Support Group
ATIB 1036 Configuring Sip REVISION HISTORY ISSUE DATE BY CHANGES Draft 8/05/09 R. Pope 1.0 22/05/09 R. Pope Initial release 1.1 13/07/09 R. Pope PGM111~113 opt 56 added Table removed from Appendix A 1.2 27/07/09 R. Pope Add further reading 1.3 7/3/11 W. Smith Add additional documents to zip file. 1.4 26/11/12 W. Smith 5.5 update & remove additional docs. TABLE OF CONTENTS 1. Introduction... 3 2. Prerequisites... 5 2.1 IPECS system requirements... 5 2.2 IP requirements... 5 2.3 Sip account requirements:... 5 3. Connecting to more than one SIP provider... 6 4. Bandwidth considerations... 6 5. Quality of Service (QoS)... 6 6. SIP Trunks:... 7 6.1 Programming... 7 6.2 Setting the LCR... 11 7. SIP Extensions... 12 7.1 Programming... 12 7.2 Setting an individual codec... 14 7.3 Registering x-lite (on-site).... 14 8. Appendix A... 18 9. Appendix B... 19 www.ariatech.com.au Page 2 Version 1.4 Published 26-11-2012
1. Introduction With the ever growing popularity of SIP (Session Initiation Protocol) as a trunking and extension options this document has been written in order to assist you (the installer) to configure an IPECS to take advantage of these alternatives. It is worth noting that some areas of early SIP protocol (RFC2543) were loosely written and as such there is no guarantee that a given service provider using RFC2543 will operate with an IPECS. Whist the newer RFC3261 has tightened the protocol some providers still use RFC2543. Note: Proprietary SIP services such as Skype are not supported. (However Skype in the future may have new compatible services available if a provider such as Skype releases a product that they indicate as suitable for the LIK it is up to the provider to support their claims.) See Appendix A for listings of known compatible SIP providers. Also see individual SIP provider Guides on the dealer web: HOME > PRODUCT INFO > LG-Ericsson - ipecs Solutions > SIP Trunking When working on an in production system the IPECS administrator and end customer s Network Administrator must estimated the deployment time and how long the system is expected to be unavailable. To ensure minimal disruption it is strongly advised that you negotiate a time outside normal business hours to make these changes. Please note the under no circumstance is the SIP port* to be published to the internet. NAPT is a major security issue for most companies. Please consider a secure VPN solution as terminus a quo. From this standpoint NAPT is not recommended/supported by Aria technologies. Routers mentioned in this ATIB are purely incidental. Aria Technologies does not recommend a particular brand or model. Upgrading & replacing routers and running network protocol analyzers (e.g. wireshark) is a standard IT administration process of troubleshooting which may be required to add connectivity. Please note this is not at our direction but may be a suggestion. Aria Technologies is not responsible for a customer s network. * We have not listed the port (50..) here to reduce the temptation even though it is common knowledge.
Basic network lay out SIP Handset LG-Nortel IPECS SIP service provider Router Internet PSTN
2. Prerequisites IPECS Phase 5.5 Training and working knowledge on IPECS Phase 5 system. IP Networking Knowledge: Working knowledge in switches & routers. 2.1 IPECS system requirements IPECS 50 MFIM 50 with 5.5Gz or greater Onboard VOIP or VOIM8/24 IPECS 100 MFIM 100 with 5.5Gz or greater Onboard VOIP or VOIM8/24 IPECS 300 MFIM 300 with 5.5Gzr or greater Onboard VOIP or VOIM8/24 IPECS 600 MFIM 600 with 5.5Gz or greater VOIM8/24 IPECS 1200 MFIM 1200 with 5.5Gz or greater VOIM8/24 2.2 IP requirements Business Grade DSL connection (SHDSL) with sufficient bandwidth to support the required maximum number of simultaneous calls with the maximum codec in use. Some SIP providers require a static IP address. VPN/WAN if off-net access or remote SIP extensions are required. Important: It s important that you evaluate the WAN link and upgrade to meet minimum bandwidth requirements where necessary. 2.3 Sip account requirements: 1. SIP Proxy Server Address. 2. Domain Address (in some cases it will be same as SIP Proxy address). 3. Type of Codec your provider supports (at least 2). 4. SIP Account Registration details (normally a user name and password). 5. Number of simultaneous SIP calls supported per SIP account. 6. Whether your Server Provider supports Multiple SIP channels in single SIP Account. Important: Make sure you have met all six of the above criteria before you begin.
3. Connecting to more than one SIP provider It will occasionally be requested that you setup connections to more than one SIP provider. The ipecs 5.5/6.0 can support multiple SIP providers on the one LAN connection and on the one VOIP module (onboard or VOIM). However in early software additional VIOM 8/24 was required per service. If your SIP accounts are multi-channel and/or are connected via a separate internet connections you may require an additional VOIM. 4. Bandwidth considerations When planning any VoIP installation it is important to consider the bandwidth required to carry the required number of speech channels, as well as all other traffic required at the customer s site. The Aria VOIBE card supports three different Codec s for speech compression. For optimum voice quality it is recommended that the G.711 Codec be used. Bandwidth requirements: Codec Audio Bandwidth Total Bandwidth G.723.1 6.3 kbit/s 27.2 kbit/s G.729 8 kbit/s 39.2 kbit/s G.729a 8 kbit/s 39.2 kbit/s G.711 ALAW/UL AW 64 kbit/s 95.2 kbit/s DTMF or fax tones may not be transported reliably with these CODECs To ensure that the best use is made of the available bandwidth you may need to allocate fewer than the maximum available VOIM channels. Any remaining capacity on the card will be available for future SIP expansion. 5. Quality of Service (QoS) If your customer is intending using a single DSL link to carry voice and data then QoS must be implemented on both the router and the DSL link. The ramifications of not implementing QoS could be anything from derogation of voice quality to calls being dropped and potentially missed, this can not be emphasized to much.
6. SIP Trunks: 6.1 Programming. 1. Backup the current IPECS system configuration (you were going to do this anyway, weren't you?). 2. Log into IPECS PGM 102~103 and check/set the following: i. MFIM IP address and subnet mask ii. MFIM gateway address iii. VOIM IP address iv. VOIM sequence number v. VOIM line numbers vi. MFIM and VOIM firmware versions MUST be current versions i ii vii vi iv v iii vii. System IP Range MUST be in the same subnet. 3. Set the required VOIM lines to the following in PGM 140~142: i. CO type to DID ii. CO/IP group set to a previously unused line group iii. Set CO VOIP mode to SIP
4. Program each SIP extension from your service provider in PGM 126 (Station SIP attributes) with the following information: i.e. 600, 601, 602, etc... i. Registration User ID ii. Authentication User ID iii. Authentication User password iv. Set 'User ID register' to 'Register' v. Set 'User ID usage' to 'on' vi. Set 'DID Digit Masking' as per programming manual example 1 using user ID 1
More UIDs can be added as needed. example 2 using user ID 2 Tip: Keeping your numbering consecutive will allow you to find entries easily. 5. Enter PGM133 and using the sequence number from step 2. sub step iv. Access the SIP G/W attributes and enter the following parameters: i. Proxy server address, can be text or numerical. ii. Primary DNS server address, numeric. 5.5/6.0 This is now programmed in PGM210 iii. Secondary DNS server address, numeric. (optional) iv. Domain v. Registration UID Range, all entries from PGM126 vi. DTMF type set as 2833 (if supported by the SIP provider), else leave as 'INBAND'.
i ii iii iv v vi Note: This program is the only location where a DNS (Domain Name Service) server is present, without it the domain address (i.e. serv.com.au) will not be resolved and the IPECS won't find the SIP provider. I've shown a Telstra DNS, your customer may have a preference of their own. 6. In program 111~113 item 56 'SIP USER TABLE INDEX' set this parameter for the SIP UID table (PGM126) that associates to the number dialed for that extension or the main number. 7. Now this section of programming is complete backup the IPECS system configuration, using a different file name from the one used in step one, and reset the VOIM.
8. Test the SIP circuit by seizing a line (line 15 to 22 in my example) and making a call. Now that you re confident that the SIP trunks work you can step onto setting the LCR to create a line access code. 6.2 Setting the LCR In this example we are going to set the IPECS to access your SIP lines (group 2) by dialing the digit 3 you could of course use any available digit. 1. Check PGMs 221 and 222 for existing entries and plan your LCR accordingly. 2. Enter PGM 220 (LCR Control Attribute) and set LCR Access Mode to 'Internal, Loop, Direct CO and Direct Loop LCR'. 3. Enter PGM 221 (LCR Leading Digit Table) and enter the following data, I've used index '0', you may have to use another; i. Compared Digits = '3' ii. DMT = 000000 (again, I've used DMT '0', you may have to use another).
4. Enter PGM 222 (LCR Digit Modification Table) and enter the CO/IP group set to how you programmed line groups in PGM140~142. 5. Now this programming is complete backup the IPECS system configuration, using a different file name from the ones used in steps one and six. 7. SIP Extensions With the addition of SIP extension capability to the IPECS your customer is able to take advantage of a wider range of devices which can be used as IPECS extensions. An example of such devices could be a PDA with a SIP phone, hands free conference phone or a remote device such as a PC with a SIP phone. Of course this opens connectivity to thousands of devices which Aria Technologies could not conceivably test. This section will discuss configuring the settings within the IPECS MFIM and configuring x-lite (a free SIP client) to connect to the IPECS. See Quick Help Guide Q511 on the dealer website for more information. Warning: Do not use NAT port forwarding. For remote requirements use VPN. 7.1 Programming 1. Backup current system database. 2. PGM102 System IP Range MUST be in the same subnet as the MFIM. 3. Check that the IPECS has sufficient SIP extension licenses.
You will need to set a Maintenance password to access the Lock Key Install section. 4. Enter a user ID in PGM 443 Station User Login. This does not need to be the extension number however for good housekeeping it is advisable. Enter a strong password & the next available station number. 5. Enter a unique password into the password field. Once you have saved this the password field will appear empty so keep a record of the password. If you loose the password you can re-write it. Once the device has successfully registered its extension number will appear in the Registered Number column. Note: Each station user requires their own login and that the login must be prefixed with sip:. I.E. ID 1234 would be entered as sip:1234 Not required for 5.5/6.0 just enter ID number. This is enough programming to enable a SIP device/s to register to the IPECS. Next we will select a codec (optional) that differs from the system default codec. This would be useful for devices connected on a WAN or through the Internet.
6. PGM 211 Set 407 Authentication to ON. (Systems with 5.5Ed or newer at default will be ON.) 7. Set appropriate COS dialling restriction levels and test. PGM 116 & 224 7.2 Setting an individual codec 1. Check the SIP extension sequence number in PGM102~103. 2. Using the sequence number from step 4 enter PGM 132 Board Based Attributes and select a suitable codec for that SIP device. 7.3 Registering x-lite (on-site). X-lite is an invaluable tool for testing SIP and is by no meens the only client that can communicate with the IPECS. Here we will configure the x-lite client to connect in order to prove that the SIP extension will connect and work. Note: This product is developed by a third party so Aria Technologies has no control on version releases which may affect the instructions below. 1. Download x-lite from http://www.counterpath.net/x-lite.html&active=4 and install on your PC. 2. Once installed execute the client and wait for it to open. The first time you run x-lite there won t be an account set for it to connect to.
3. Click on the button and select SIP account settings from the drop down menu. 4. The accounts dialogue box will display, click the add button in order to create the account for the IPECS.
5. Enter the following information: i. Display name (this will overwrite the Station Name where programmed). ii. User name from PGM 443 (without the sip: prefix). iii. Password from PGM 443. iv. Authorisation user name again from PGM 443 (without the sip: prefix). v. Domain and Proxy are the same and they are the IP address of the VOIM/MFIM.
6. Click OK then Close and the x-lite will now register to the IPECS with a READY message in the top left corner. Each SIP extension uses an available MFIM VOIP or a VOIM VOIP channel when in use. If more extensions than channels are provisioned this will limit the amount of concurrent conversations available within that device.
8. Appendix A Available from the Aria Technologies web site is a current list of tested/approved SIP service providers. www.ariatech.com.au/sip At last count there were over four hundred and twenty SIP service providers in Australia. For a nominal fee Aria Technologies can test any SIP service provider upon request and approval. Both a report and an invoice will be sent to the company requesting such services.
9. Appendix B Some examples of DNS servers within Australia iinet: 203.0.178.191 Optus: 203.2.75.132 Telstra Primary: 203.50.2.71 Telstra Secondary: 139.130.4.4 Netspace Primary: 203.10.110.101 Netspace Secondary: 203.17.103.1 UUNET: 203.2.192.124 Netspace Primary: 210.15.254.240, Secondary: 210.15.254.241 GPM: Home: 202.44.170.21 Business: 202.91.192.81 and 202.91.192.82 OzForces Primary: 203.17.15.201, Secondary: 203.17.15.202 Telstra: 61.9.128.13, 61.9.128.14, 61.9.128.15, 61.9.128.16 Optus: 198.142.0.51, 203.2.75.132 Shaw Primary: 24.64.223.212, Secondary: 24.64.223.195 iinet: 203.0.178.191 Alphalink Primary: 203.24.205.1, Secondary: 203.24.205.2 Connexus Primary: 203.12.22.10, Secondary: 203.12.22.20 CyberLink: 202.154.92.35 Dodo Primary: DNS1.DODO.COM.AU, Secondary: DNS2.DODO.COM.AU i-green Primary: 202.129.64.194, Secondary: 202.129.64.198 NetSpeed Primary: 203.31.48.7, Secondary: 203.56.186.7 NetXP Primary: 202.94.33.10, Secondary: 202.94.33.2 OzEmail Primary: 203.2.193.124, Secondary: 203.2.192.124 PacificInternet Primary: 61.8.0.113, Secondary: 210.23.129.34 Swiftel Primary: 218.214.17.1, Secondary: 202.154.92.35 TPG Primary: 203.12.160.35, Secondary: 203.12.160.36 WebOne Primary: 210.9.240.33, Secondary: 210.8.44.1 WestNet Primary: 206.24.6.2, Secondary: 206.24.6.9