Avaya Mobile Communications Client User Manual

NN42030-400
Nortel Mobile Communication 3100 Portfolio
Nortel Mobile Communication Client 3100 for Windows Mobile
Release Notes
Standard 02.01 May 2008
3

Content s

How to get help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Finding the latest updates on the Nortel web site 5 Getting help from the Nortel web site 5 Getting help over the phone from a Nortel Solutions Center 5 Getting help from a specialist by using an Express Routing Code 6 Getting help through a Nortel distributor or reseller 6
Release 2.1 for CS1000 build 125 and Admin Tool (Load 23139) for
Mobile Communication Client 3100 . . . . . . . . . . . . . . . . . . . . . . . .7
Supported features 7 Updates 7 Limitations 8
NN42030-400 MCC 3100 for Windows Mobile Standard 02.01 May 2008
4
NN42030-400 MCC 3100 for Windows Mobile Standard 02.01 May 2008

How to get help 1

This chapter explains how to get help for Nortel products and services.

Finding the latest updates on the Nortel web site

The content of this documentation was current at the time the product was released. To check for updates to the latest documentation and software for Mobile Communication Client (MCC) 3100, go to
www.nortel.com/support.

Getting help from the Nortel web site

The best way to get technical support for Nortel products is from the Nortel Technical Support web site:
www.nortel.com/support
This site provides quick access to software, documentation, bulletins, and tools to address issues with Nortel products. From this site, you can:
download software, documentation, and product bulletins
search the Technical Support Web site and the Nortel Knowledge Base for answers to technical issues
sign up for automatic notification of new software and documentation for Nortel equipment
open and manage technical support cases

Getting help over the phone from a Nortel Solutions Center

If you do not find the information you require on the Nortel Technical Support web site, and you have a Nortel support contract, you can also get help over the phone from a Nortel Solutions Center.
In North America, call 1-800-4NORTEL (1-800-466-7835).
Nortel Mobile Communication Client 3100 for Windows Mobile Release Notes
6
Outside North America, go to the following web site to obtain the phone number for your region:
www.nortel.com/callus

Getting help from a specialist by using an Express Routing Code

To access some Nortel Technical Solutions Centers, you can use an Express Routing Code (ERC) to quickly route your call to a specialist in your Nortel product or service. To locate the ERC for your product or service, go to:
www.nortel.com/erc

Getting help through a Nortel distributor or reseller

If you purchased a service contract for your Nortel product from a distributor or authorized reseller, contact the technical support staff for that distributor or reseller.
NN42030-400 MCC 3100 for Windows Mobile Standard 02.01 May 2008

Release 2.1 for CS1000 build 125 and Admin Tool (Load 23139) for Mobile Communication Client 3100 2

Date: May 09, 2008 Release: 2.1 Build: CS 1000 125

Supported features

MCC 3100 Release 2.1 does not introduce new software for the Mobile Communication Client 3100 for Windows Mobile Dual Mode; you use the Release 2.0 software.
MCS5100 and CS1K R5.0 support
incoming and outgoing Wireless Fidelity (WiFi) and cellular calls
Call hold
Blind Call Transfer
Short Message Service (SMS)
Instant Messaging (IM)
3-way conference for MCS 5100
CS 1000 SIP registration—with or without Authorization challenge from the CS 1000 registration server
Attention: With MCC 3100 load 2.1.0.115, you require an additional license to enable the VPN.

Updates

This ISO image contains MCC 3100 load 2.1.0.125 and Admin Tool load 23139. The following issue has been resolved:
Q01764010: vi: MCC-BB called sender MCS MCC-WM from CP via SIP trunk, no speech path
Nortel Mobile Communication Client 3100 for Windows Mobile Release Notes

Limitations

PR7063: Half Duplex on HP iPAQ—There is no technical solution to the ear piece issue on HP iPAQ hw69xx devices. The half duplex audio issue is caused by this technical limitation.
PR6524: Side effects of resolution of ear piece limitation on HTC TyTN family of devices—The voice of VoIP over WiFi calls on MC comes out from the speaker on the back of mobile device. FHT has devised a solution to redirect voice path of VoIP calls to the ear piece on the HTC TyTN family devices as the preferred audio output path. FHT has validated that the MC user will have identical user experience between a Cellular call and VoIP call on the MC supported handsets, with the following noted side effects:
— Cellular call audio mode (hairpiece or speaker) override—
applies only to GSM devices because of PR5123 noted below.
When MC is in a WiFi call in the speaker mode, an incoming Cellular call will disable the speaker mode of the WiFi call. The user has to re-select the speaker mode of the WiFi call to continue the WiFi call on the speaker. This situation happens even the Cellular call is declined by the user.
8
When there is a Cellular call on hold in the hairpiece mode, and at the same time there is a WiFi call in progress in the speaker mode, the termination of the Cellular call will automatically change the WiFi call from the speaker mode to hairpiece mode. Again, the user has to re-enable the speaker mode to continue the WiFi call on speaker.
When there is a Cellular call on hold in the speaker mode, and at the same time there is a WiFi call in progress in the hairpiece mode, the termination of the Cellular call will automatically change the WiFi call from hairpiece mode to speaker mode. The user will have change the call to hairpiece mode to continue the WiFi call with privacy.
— For VoIP calls, the locally generated tones by MC are always
played via the speaker. The far-end generated audio, such as trunk generated ringback, will be played via the hairpiece. The locally generated tones include Ringback Tone, MoH, ROT, SPDT, Dial Tone, Busy Tone and Service Set Tone.
PR5123: CDMA device/network limitations
— Only one call session is seen in Call Session Window
Due to the limitation of CDMA network in incoming call presentation, two call sessions are always presented as a single call, even one is on hold and one active. As a result, the call session window only lists the first incoming call. This
NN42030-400 MCC 3100 for Windows Mobile Standard 02.01 May 2008
behavior will be corrected in MC software in the next update release
— Call hold between calls from both CDMA and WiFi side
In a CDMA network, there is not a notion of true "Hold" (or Hard Hold). Instead a "soft hold" in supported. With "soft hold", CDMA networks side only honors the client side "Call Hold" request for 30 seconds. Once the call is held for more than 30 seconds, and there is no new CDMA call being made or answered, CDMA network will make the held call active without any notification. As a result, it is impossible to support call hold involving both CDMA and WiFi side at the same time. Therefore, a safe guard is implemented to prevent new incoming call from either network once there is a call established in the other network. This issue doesn't apply to the same GSM/WiFi operations.
— When in the CDMA side call waiting feature without Caller Id
subscription, MC does not give a incoming call Pop-up, but only gives a beep. Although the user experience is identical to that on single mode CDMA devices using the call waiting feature, with or without Caller Id subscription, the MC application for GSM network offers better user experience
9
PR5292: Click to "Call Home" or "Call Work" doesn't work from Outlook Contacts
Because of WM5 hard-coded link to invoke MS native dialer from these menu links, the call action is not directed to the FHT MC application. Use the MC provided menu links, which are located at the lower portion of the same menu
PR5289: Mobile carrier dependent presentation of "+" and/or "1" in incoming call log cannot be used directly to return the call from call log via the SIP side.
Different mobile carriers use different prefix presentations in Call Id of the incoming call. For example, Rogers Wireless always prefixes "+1" to any incoming call, local or long distance, while Bell Mobility does not prefix any digits. It introduces dependency on the SIP side network to be able to determine which combination of area code + exchange code is a long distance number or a local number, before the call is presented to the PSTN network by the SIP server.
The landline-based PSTN network is sensitive to the use of "1" prefix when it is only a local call. MC alone does not have this knowledge about the device. But MC provides a pop-up to allow the user to call, from call log, with or without the long distance prefix. The user makes the final selection of what number to use to make
Nortel Mobile Communication Client 3100 for Windows Mobile Release Notes
a call. The "+" sign is removed automatically in the dial string which is presented to the user to confirm.
R5773: Call log shows incorrect two simultaneous call activities after far-end terminates held call
When with two cellular calls, one being held and one active, there are two call log entries in Call Log. If the held party terminates the call, the log entry still shows two calls, one active and one held. This is due to the device TAPI interface does not deliver such notification of far-end termination of the held call in time for MC to process and update the view. Thus MC is not able to update the Call Log and Session views accordingly. The MC error in not updating the views will be fixed for the situation where all calls are terminated and the pending events are delivered in the next update release.
PR5297: MC display not updated correctly when soft-keyboard is used and screen orientation is changed from portrait to landscape mode
This is recognized as a display update issue, and will be fixed in the next maintenance release. In the mean time, to work around the issue, close the soft keyboard, and change to a different screen orientation. Then change back to the original screen orientation that initially encountered this problem.
10
PR6510: MC does not support Bluetooth Call Swap
Some BT devices support advanced BT call features. MC does not support the features available for selected devices, but rather it supports the basic Bluetooth specification supported by most devices
NN42030-400 MCC 3100 for Windows Mobile Standard 02.01 May 2008
Nortel Mobile Communication 3100 Portfolio
Nortel Mobile Communication Client 3100 for Windows Mobile
Release Notes
Copyright © 2007–2008 Nortel Networks. All Rights Reserved.
Sourced in Canada
LEGAL NOTICE
While the information in this document is believed to be accurate and reliable, except as otherwise expressly agreed to in writing NORTEL PROVIDES THIS DOCUMENT "AS IS" WITHOUT WARRANTY OR CONDITION OF ANY KIND, EITHER EXPRESS OR IMPLIED. The information and/or products described in this document are subject to change without notice.
Nortel, Nortel (Logo), the Globemark, SL-1, Meridian 1, and Succession are trademarks of Nortel Networks.
All other trademarks are the property of their respective owners.
To provide feedback or report a problem in this document, go to
www.nortel.com/documentfeedback
.
Publication number: NN42030-400 Product release: MCC 3100 for Windows Mobile Document version: Standard 02.01 Date: May 2008
Loading...