Archived:CTelephony::DialNewCall() API gives connection error in dual mode (Known Issue)

Archived: This article is archived because it is not considered relevant for third-party developers creating commercial solutions today. If you think this article is still relevant, let us know by adding the template {{ReviewForRemovalFromArchive|user=~~~~|write your reason here}}.

Fixed in new later firmware version.

Article Metadata

---

Tested with

Devices(s): S60 3rd Edition 3G devices

---

Compatibility

Platform(s): S60 3rd Edition
3rd Edition, FP1

---

Article

Created: copyeditor (14 Feb 2008)

Last edited: hamishwillee (09 May 2012)

Description

After programmatically hanging up an outgoing call created by the user or by another application, (using, for example, CPhCltCommandHandler::Chup() or the Phone Client API), an attempt to create a new call with CTelephony:DialNewCall() may fail.

When the device is in a 3G network and a new call is established immediately after the previous call has been terminated, call creation may fail with the telephony application displaying a Disconnected note. Note that this behavior has only been observed in 3G networks when using a device in 2/3G dual mode.

Solution

No known solutions for 3G (dual) network mode, however adding a delay between hangup and call creation increases the success rate. It has been also observed that new firmware versions do not have this problem anymore; for example, the issue cannot be reproduced with Nokia N95 sw v20.0.015.

Note: This known issue was originally created by Krugliy and has been verified by Nokia Developer.