Text Messaging Configuration Guide Release 2.1

Transcription

1 Text Messaging Configuration Guide Release Issue 2.1 January 2005

2 Copyright , Avaya Inc. All Rights Reserved Notice Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change. Warranty Avaya Inc. provides a limited warranty on this product. Refer to your sales agreement to establish the terms of the limited warranty. In addition, Avaya s standard warranty language as well as information regarding support for this product, while under warranty, is available through the following Web site: Trademarks DEFINITY is a registered trademark of Avaya, Inc. MultiVantage is a trademark of Avaya, Inc. Windows, Windows 2000, and Windows NT are trademarks or registered trademarks of Microsoft Corporation. Preventing Toll Fraud Toll fraud is the unauthorized use of your telecommunications system by an unauthorized party (for example, a person who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf). Be aware that there may be a risk of toll fraud associated with your system and that, if toll fraud occurs, it can result in substantial additional charges for your telecommunications services. Avaya Fraud Intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, in the United States and Canada, call the Technical Service Center's Toll Fraud Intervention Hotline at Disclaimer Avaya is not responsible for any modifications, additions or deletions to the original published version of this documentation unless such modifications, additions or deletions were performed by Avaya. Customer and/or End User agree to indemnify and hold harmless Avaya, Avaya's agents, servants and employees against all claims, lawsuits, demands and judgments arising out of, or in connection with, subsequent modifications, additions or deletions to this documentation to the extent made by the Customer or End User. How to Get Help For additional support telephone numbers, go to the Avaya support Web site: If you are: Within the United States, click the Escalation Management link. Then click the appropriate link for the type of support you need. Outside the United States, click the Escalation Management link. Then click the International Services link that includes telephone numbers for the international Centers of Excellence. Providing Telecommunications Security Telecommunications security (of voice, data, and/or video communications) is the prevention of any type of intrusion to (that is, either unauthorized or malicious access to or use of) your company's telecommunications equipment by some party. Your company's telecommunications equipment includes both this Avaya product and any other voice/data/video equipment that could be accessed via this Avaya product (that is, networked equipment ). An outside party is anyone who is not a corporate employee, agent, subcontractor, or is not working on your company's behalf. Whereas, a malicious party is anyone (including someone who may be otherwise authorized) who accesses your telecommunications equipment with either malicious or mischievous intent. Such intrusions may be either to/through synchronous (timemultiplexed and/or circuit-based) or asynchronous (character-, message-, or packet-based) equipment or interfaces for reasons of: Utilization (of capabilities special to the accessed equipment) Theft (such as, of intellectual property, financial assets, or toll facility access) Eavesdropping (privacy invasions to humans) Mischief (troubling, but apparently innocuous, tampering) Harm (such as harmful tampering, data loss or alteration, regardless of motive or intent) Be aware that there may be a risk of unauthorized intrusions associated with your system and/or its networked equipment. Also realize that, if such an intrusion should occur, it could result in a variety of losses to your company (including but not limited to, human/data privacy, intellectual property, material assets, financial resources, labor costs, and/or legal costs). Responsibility for Your Company s Telecommunications Security The final responsibility for securing both this system and its networked equipment rests with you - Avaya s customer system administrator, your telecommunications peers, and your managers. Base the fulfillment of your responsibility on acquired knowledge and resources from a variety of sources including but not limited to: Installation documents System administration documents Security documents Hardware-/software-based security tools Shared information between you and your peers Telecommunications security experts To prevent intrusions to your telecommunications equipment, you and your peers should carefully program and configure: Your Avaya-provided telecommunications systems and their interfaces Your Avaya-provided software applications, as well as their underlying hardware/software platforms and interfaces Any other equipment networked to your Avaya products TCP/IP Facilities Customers may experience differences in product performance, reliability and security depending upon network configurations/design and topologies, even when the product performs as warranted. Standards Compliance Avaya Inc. is not responsible for any radio or television interference caused by unauthorized modifications of this equipment or the substitution or attachment of connecting cables and equipment other than those specified by Avaya Inc. The correction of interference caused by such unauthorized modifications, substitution or attachment will be the responsibility of the user. Pursuant to Part 15 of the Federal Communications Commission (FCC) Rules, the user is cautioned that changes or modifications not expressly approved by Avaya Inc. could void the user s authority to operate this equipment. To order copies of this and other documents: Call: Avaya Publications Center Voice or FAX or Write: Globalware Solutions 200 Ward Hill Avenue Haverhill, MA USA Attention: Avaya Account Management totalware@gwsmail.com For the most current versions of documentation, go to the Avaya support Web site:

3 Avaya Text Messaging enables Avaya IP Telephone users (4620, 4620SW, 4610SW) to send and receive Short Message Service (SMS) text messages that are transcoded for display by the Avaya Phone Application Gateway (AG). Messages can be sent between IP phones and between IP phones and mobile devices that support text messaging. Text Messaging features include: Text Messaging users can choose from saved messages and addresses, or enter new information that will be saved. Saved messages include those that a user has sent and messages that are pre-configured by the administrator. Users can receive and reply to messages during a phone call. A user s Inbox and Outbox can contain a total of 100 messages. For text messaging between IP phones, no configuration is required. Text Messaging is included with your AG license and appears on the Voice Office menu by default. The AG connects to your network as follows: For text messaging between IP phones and mobile phones, you must configure the DNS server, SMTP server, and the AG. You might also need to configure your mail server. Text Messaging Configuration Guide 3

4 Removing Text Messaging from the Voice Office Menu The following topics describe how to configure the connection and operation of Text Messaging for Avaya IP telephones: Removing Text Messaging from the Voice Office Menu, page 4 Configuring the Avaya File Server Script, page 5 Configuring Text Messaging Between IP Phones, page 5 Configuring Text Messaging Between IP Phones and Mobile Phones, page 7 Note The AG distribution includes a document, Using Text Messaging on Avaya IP Telephones, that you can change as needed and distribute to IP phone users. The document explains how to use the Text Messaging application. Removing Text Messaging from the Voice Office Menu Note For more information on customizing the menus that display on IP phones, refer to the IP Phone Menu Configuration Guide. If you do not want to give your IP phone users access to Text Messaging, remove it from the Voice Office menu as follows. To remove Text Messaging from the Voice Office menu: 1 Open the Avaya AG Administration Tool: From a web browser, enter the URL 2 Go to the Operation > Voice Office > Menu page. 3 Clear the checkbox for Show Text Messaging. 4 Click Submit. 4 Text Messaging Configuration Guide

5 Configuring the Avaya File Server Script Configuring the Avaya File Server Script For information on configuring the Avaya file server script (46xxsettings.txt) so that phones can connect to the AG, refer to the guide Configuring Avaya IP Phone Connections to the Phone Application Gateway. If the script file is not properly configured so that a phone can connect to the AG, attempts to connect to Text Messaging from a phone will result in the error: Mailbox busy, please wait. Configuring Text Messaging Between IP Phones If your site supports text messaging between IP phones only (and not also between IP phones and mobile phones), there is no required configuration. The AG relays text messages between IP phones, provided that the recipient s extension is registered on the AG. Text message addresses are in the form extension@domain, where domain is the fully-qualified domain such as AG.domain.com or AGIPAddress. It is recommended that you predefine up to 10 system messages for your IP phone users. By pre-defining messages, you enable IP phone users to quickly send common messages without having to type the message text. Your IP phone users might find messages such as the following useful: Meeting in 10 minutes, Leaving now, Want to go to lunch?, I m in a meeting, We won the deal!. Your pre-defined messages appear in the System Messages list in the Text Messaging display. To pre-define text messages: 1 Open the Avaya AG Administration Tool: From a web browser, enter the URL 2 Go to the Operation > Voice Office > Text Messaging page. Text Messaging Configuration Guide 5

6 Configuring Text Messaging Between IP Phones 3 Enter up to ten messages that will be available to IP phone users. These messages will be available to IP phone users regardless of the destination of the message (IP phone or mobile phone). 4 Click Submit. 6 Text Messaging Configuration Guide

7 Configuring Text Messaging Between IP Phones and Mobile Phones Configuring DNS By default, Text Messaging is configured only for messaging between IP phones. To enable your IP phone users to send messages to and receive messages from mobile phones, you must perform the configuration described in the following sections: Configuring DNS, page 7 Configuring Your SMTP Server, page 7 Configuring the AG to Send Messages to Mobile Phones, page 11 The AG sends messages to mobile phone carriers through . The addresses of text messages to mobile phones are in the form iptel.company.com. Your DNS server requires the following configuration to enable message delivery to mobile phones: An A (Address) record for the AG to map its host name to its IP address. An MX (Mail Exchange) record for your text-telephony domain. MX records are used for delivering mail to users on your domain. To configure your DNS server: 1 Choose a fully qualified domain, such as iptel.company.com. 2 In your DNS Server, add an A record for the AG. 3 In your DNS Server, add an MX record that points your domain to the DNS A record for your AG. Configuring Your SMTP Server For outgoing text messages to mobile phones, the AG sends the messages to the SMTP server that handles outgoing . The AG sends with a text message the outgoing domain, used by the SMTP server to determine the appropriate carrier. Text Messaging Configuration Guide 7

8 To enable outgoing text messages to mobile phones, you must perform the following configuration: The SMTP server must be configured to allow s from the AG. You configure the AG to communicate with the outgoing SMTP server, as described in Configuring the AG to Send Messages to Mobile Phones, page 11. For incoming text messages from mobile phones, the domain name of the AG needs to be resolvable by the SMTP server that is relaying the message to the AG. You can configure your SMTP server in a variety of ways. For example: You can configure the SMTP server to send incoming messages to the AG. For this configuration, you need to configure the AG as an server on your internal LAN, set up to receive messages on the Outgoing Domain specified in Configuring the AG to Send Messages to Mobile Phones, page 11. Note For this configuration, make sure that s intended for IP phones are directed to port 25 on the AG. You can configure the SMTP server to send incoming messages to your server (such as Exchange or QMail). In this configuration, the SMTP must be configured to filter and route the text messages to the mail server. 8 Text Messaging Configuration Guide

9 The following sections provide the general steps for configuring mail servers for Text Messaging: Configuring Microsoft Exchange 2000/2003, page 9 Configuring QMail, page 11 Configuring Microsoft Exchange 2000/2003 The following procedures are examples; the names of your Administrative Groups and Server may differ. To configure your Exchange server to allow the AG to send via SMTP: 1 Open the Exchange System Manager. 2 Expand Administrative Groups > First Administrative Group > Servers > Your_Server_Name. 3 Expand Protocols > SMTP. 4 Right-click Default SMTP Virtual Server, and then open Properties. 5 Click the Access Tab, and then click the Relay button. 6 If the option Only this list below is not selected, skip to step 9. 7 Click the Add button. 8 Select Single Computer and enter the IP Address of the AG. 9 Click OK until all dialogs are closed. Text Messaging Configuration Guide 9

10 To configure your Exchange server to forward to the AG: 1 Open the Exchange System Manager. 2 Expand Recipients, and then right-click Recipient Policies. 3 Choose New > Recipient Policy. 4 Select the Addresses checkbox and click OK. 5 Enter a name, such as IP Phones. 6 Under Address Policies, click the New button. 7 Select SMTP Address and click OK. 8 Enter the address domain with symbol, for 9 Clear the This Exchange Organization is responsible checkbox and click OK. 10 Select the box next to the domain you added, and then click Set as Primary. 11 Remove or uncheck all of the other SMTP addresses in the dialog, except for the X400 address. 12 Expand Administrative Groups > First Administrative Group > Routing Groups. 13 Right-click Connectors, choose New > SMTP Connector, and enter a name for the connector, such as IP Phones. 14 Choose Forward all mail through this connector to the following smart hosts. 15 Enter the IP address or host name of the AG in the space provided, encapsulating it in brackets, such as [ag.company.com] or [ ]. 16 Under Local Bridgehead, click Add. 17 Select your local SMTP virtual server from the list and click OK. 18 Click the Address Space tab, click Add, choose SMTP, and then click OK. 19 Enter the domain, without symbol. For example: iptel.company.com. 20 Select the Allow messages to be relayed to these domains checkbox. 21 Click OK to close all of the dialogs. 10 Text Messaging Configuration Guide

11 Configuring QMail To allow your QMail server to forward to the AG and allow the AG to relay via the QMail Server: 1 Add an entry to the /var/qmail/control/smtproutes file for the new domain. For example: iptel.company.com:ag_ip_address 2 Add the domain (such as iptel.company.com) to the end of /var/qmail/control/rcpthosts. 3 Restart QMail. Note The QMail server must have a route to the AG. Configuring the AG to Send Messages to Mobile Phones To configure the AG to send text messages to mobile phones, you must specify the SMTP server used to send messages to mobile phones as well as your site s outgoing mail address domain (such as iptel.company.com). You can also pre-define carrier names that IP phone users can quickly select from the Text Messaging screen. To send a text message to a mobile phone, the AG must know the carrier for that phone number. The first time that an IP phone user tries to send a text message to a particular mobile phone number, the user will be prompted select a carrier domain from the list of carriers that you have provided on the Text Messaging page in the Administration Tool. If the mobile phone number s carrier is not on that list, the user must enter the carrier domain. Once a text message has been sent to a particular mobile phone number, that number and its carrier domain are stored in the AG and IP phone users can send text messages to that number by simply entering the number. To simplify text messaging for your users, we encourage you to determine the top carriers that your users will need and enter those domains in the Text Messaging page. For a comprehensive list of carrier domains, refer to Carrier Domain Reference, page 13. For IP phone users with mobile phones, encourage those users to send a text message from their IP phone to their mobile phone. By doing that, the user ensures that no one will have to know their carrier in order to send an initial message. Text Messaging Configuration Guide 11

12 To configure Text Messaging for use with mobile phones: 1 Open the Avaya AG Administration Tool: From a web browser, enter the URL 2 Go to the Operation > Voice Office > Text Messaging page. 3 Select the Enable Text Messaging checkbox. 4 Enter the IP address and port number of the outgoing SMTP server to be used to send text messages to mobile phones. For example, this might be your Exchange SMTP virtual server. 5 Enter your site s outgoing mail address. For example, if your outgoing messages are formatted as extension@domain (1234@iptel.company.com), enter the domain portion in the Outgoing Domain field. 6 Enter up to ten messages that will be available to IP phone users. 12 Text Messaging Configuration Guide

13 By pre-defining messages, you enable IP phone users to quickly send common messages without having to type the message text. Your IP phone users might find messages such as the following useful: Meeting in 10 minutes, Leaving now, Want to go to lunch?, I m in a meeting. Your pre-defined messages appear in the System Messages list in the Text Messaging display. 7 Enter up to ten domains that will be available to IP phone users. A few of the more widely-used domains are listed in the next section. If an IP phone user needs a domain that is not already listed in SMTP Default Domains, a user will have to enter the domain before sending the first text message to that particular number. 8 Click Submit. Carrier Domain Reference Company Name SMTP Format 3 River Wireless phonenumber@sms.3rivers.net ACS Wireless phonenumber@paging.acswireless.com Advantage Communications 10digitpagernumber@advantagepaging.com Airtouch Pagers 10digitpagernumber@myairmail.com Airtouch Pagers 10digitpagernumber@alphapage.airtouch.com Airtouch Pagers 10digitpagernumber@airtouch.net Airtouch Pagers 10digitpagernumber@airtouchpaging.com AlphNow pin@alphanow.net Alltel 10digitphonenumber@alltelmessage.com Alltel PCS 10digitphonenumber@message.alltel.com Ameritech Paging 10digitpagernumber@paging.acswireless.com Ameritech Paging 10digitpagernumber@pageapi.com Ameritech Clearpath 10digitpagernumber@clearpath.acswireless.com Andhra Pradesh Airtel phonenumber@airtelap.com Arch Pagers (PageNet) 10digitpagernumber@archwireless.net Arch Pagers (PageNet) 10digitpagernumber@epage.arch.com Text Messaging Configuration Guide 13

14 Company Name Arch Pagers (PageNet) AT&T PCS AT&T Pocketnet PCS Beepwear BeeLine GSM Bell Atlantic Bell Canada Bell Canada Bell Mobility Bell South (Blackberry) Bell South Bell South Bell South Bell South Bell South Mobility Bluegrass Cellular BPL mobile Carolina Mobile Communications Cellular One East Coast Cellular One South West Cellular One PCS Cellular One Cellular One Cellular One Cellular One Cellular One Cellular One Cellular South SMTP Format Text Messaging Configuration Guide

15 Company Name Central Vermont Communications CenturyTel Chennai RPG Cellular Chennai Skycell / Airtel Cincinnati Bell Cingular Wireless Cingular Wireless Cingular Wireless Clearnet Comcast Communication Specialists Communication Specialist Companies Comviq Cook Paging Corr Wireless Communications Delhi Aritel Delhi Hutch Digi-Page / Page Kansas Dobson Cellular Systems Dobson-Alex Wireless / Dobson-Cellular One DT T-Mobile Edge Wireless EMT Escotel Fido GCS Paging Goa BPLMobil SMTP Format 10digitpagernumber@cvcpaging.com phonenumber@messaging.centurytel.net phonenumber@rpgmail.net phonenumber@airtelchennai.com phonenumber@mobile.att.net 10digitphonenumber@mycingular.textmsg.com 10digitphonenumber@mobile.mycingular.com 10digitphonenumber@mobile.mycingular.net phonenumber@msg.clearnet.com phonenumber@comcastpcs.textmsg.com 7digitpin@pageme.comspeco.net pin@pager.comspeco.com number@sms.comviq.se 10digitpagernumber@cookmail.com phonenumber@corrwireless.net phonenumber@airtelmail.com phonenumber@delhi.hutch.co.in 10digitpagernumber@page.hit.net phonenumber@mobile.dobson.net phonenumber@mobile.cellularone.com phonenumber@t-mobile-sms.de phonenumber@sms.edgewireless.com phonenumber@sms.emt.ee phonenumber@escotelmobile.com phonenumber@fido.ca pagernumber@webpager.us phonenumber@bplmobile.com Text Messaging Configuration Guide 15

16 Company Name Golden Telecom GrayLink / Porta-Phone GTE GTE GTE Gujarat Celforce Houston Cellular Idea Cellular Infopage Systems Inland Cellular Telephone The Indiana Paging Co JSM Tele-Page Kerala Escotel Kolkata Airtel Kyivstar Lauttamus Communication LMT Maharashtra BPL Mobile Maharashtra Idea Cellular Manitoba Telecom Systems MCI Phone MCI Meteor Metrocall Metrocall 2-way Metro PCS Metro PCS Microcell SMTP Format phonenumber@sms.goldentele.com 10digitpagernumber@epage.porta-phone.com number@airmessage.net number@gte.pagegate.net 10digitphonenumber@messagealert.com phonenumber@celforce.com number@text.houstoncellular.net phonenumber@ideacellular.net pinnumber@page.infopagesystems.com phonenumber@inlandlink.com last4digits@pager.tdspager.com pinnumber@jsmtel.com phonenumber@escotelmobile.com phonenumber@airtelkol.com number@smsmail.lmt.lv pagernumber@e-page.net phonenumber@smsmail.lmt.lv phonenumber@bplmobile.com phonenumber@ideacellular.net phonenumber@text.mtsmobility.com phonenumber@mci.com phonenumber@pagemci.com phonenumber@mymeteor.ie 10digitpagernumber@page.metrocall.com 10digitpagernumber@my2way.com 10digitphonenumber@mymetropcs.com 10digitphonenumber@metorpcs.sms.us phonenumber@fido.ca 16 Text Messaging Configuration Guide

17 Company Name Midwest Wireless MiWorld Mobilecomm Mobileone Mobilfone Mobility Bermuda Mobistar Belgium Mobitel Tanzania Mobtel Srbija Morris Wireless Motient Movistar Mumbai BPL Mobile Mumbai Orange NBTel Netcom Nextel Nextel Nextel NPI Wireless Ntelos Omnipoint Omnipoint One Connect Austria OnlineBeep Optus Mobile Orange Orange - NL / Dutchtone SMTP Format phonenumber@clearlydigital.com phonenumber@m1.com.sg number@mobilecomm.net phonenumber@m1.com.sg phonenumber@page.mobilfone.com phonenumber@ml.bm phonenumber@mobistar.be phonenumber@sms.co.tz phonenumber@mobtel.co.yu 10digitpagernumber@beepone.net number@isp.com number@correo.movistar.net phonenumber@bplmobile.com phonenumber@orang .co.in number@wirefree.informe.ca phonenumber@sms.netcom.no 10digitphonenumber@messaging.nextel.com 10digitphonenumber@page.nextel.com 10digitphonenumber@nextel.com.br phonenumber@npiwireless.com number@pcs.ntelos.com number@omnipoint.com 10digitphonenumber@omnipointpcs.com phonenumber@on .at 10digitphonenumber@onlinebeep.net phonenumber@optusmobile.com.au phonenumber@orange.net phonenumber@sms.orange.nl Text Messaging Configuration Guide 17

18 Company Name Oskar P&T Luxembourg Pacific Bell PageMart PageMart Advanced /2way PageMart Canada PageNet Canada PageOne NorthWest PCS One Pioneer / Enid Cellular PlusGSM Pondicherry BPL Mobile Powertel Price Communications Primco Primtel ProPage Public Service Cellular Qwest RAM Page Rogers AT&T Wireless Rogers Canada Safaricom Satelindo GSM Satellink SBC Ameritech Paging SCS-900 SFR France SMTP Format phonenumber@mujoskar.cz phonenumber@sms.luxgsm.lu phonenumber@pacbellpcs.net 7digitpinnumber@pagemart.net 10digitpagernumber@airmessage.net 10digitpagernumber@pmcl.net phonenumber@pagegate.pagenet.ca 10digitnumber@page1nw.com phonenumber@pcsone.net phonenumber@msg.pioneerenidcellular.com phonenumber@text.plusgsm.pl phonenumber@bplmobile.com phonenumber@voicestream.net phonenumber@mobilecell1se.com number@primeco@textmsg.com phonenumber@sms.primtel.ru 7digitpagernumber@page.propage.net phonenumber@sms.pscel.com 10digitphonenumber@qwestmp.com number@ram-page.com phonenumber@pcs.rogers.com 10digitphonenumber@pcs.rogers.com phonenumber@safaricomsms.com phonenumber@satelindogsm.com 10digitpagernumber.pageme@satellink.net 10digitpagernumber@paging.acswireless.com phonenumber@scs-900.ru phonenumber@sfr.fr 18 Text Messaging Configuration Guide

19 Company Name Skytel Pagers Skytel Pagers Simple Freedom Smart Telecom Southern LINC Southwestern Bell Sprint Sprint PCS ST Paging SunCom SunCom Sunrise Mobile Sunrise Mobile Surewest Communications Swisscom T-Mobile T-Mobile T-Mobile Austria T-Mobile Germany T-Mobile UK Tamil Nadu BPL Mobile Tele2 Latvia Telefonica Movistar Telenor Teletouch Telia Denmark Telus TIM SMTP Format Text Messaging Configuration Guide 19

20 Company Name SMTP Format Triton TSR Wireless TSR Wireless Unicel Uraltel US Cellular US Cellular US West Uttar Pradesh Escotel Verizon Pagers Verizon PCS Verizon PCS Vessotel Virgin Mobile Vodafone Italy Vodafone Japan Vodafone Japan Vodafone Japan Vodafone Spain Vodafone UK VoiceStream / T-Mobile 10digitphonenumber@voicestream.net WebLink Wireless pagernumber@airmessage.net WebLink Wireless pagernumber@pagemart.net West Central Wireless phonenumber@sms.wcc.net Western Wireless phonenumber@cellularonewest.com Wyndtell number@wyndtell.com 20 Text Messaging Configuration Guide