Archived:CTelephony::DialNewCall() API gives connection error in dual mode (Known Issue)
hamishwillee
(Talk | contribs) m (Text replace - "Category:S60 3rd Edition, Feature Pack 1" to "Category:S60 3rd Edition FP1") |
hamishwillee
(Talk | contribs) m (moved CTelephony::DialNewCall() API gives connection error in dual mode (Known Issue) to Archived:CTelephony::DialNewCall() API gives connection error in dual mode (Known Issue)) |
||
| (One intermediate revision by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | |||
{{Archived|timestamp=20120216102337|user=roy.debjit|Fixed in new later firmware version.}} | {{Archived|timestamp=20120216102337|user=roy.debjit|Fixed in new later firmware version.}} | ||
| + | [[Category:Known Issue]][[Category:Symbian C++]][[Category:Telephony]][[Category:S60 3rd Edition (initial release)]][[Category:S60 3rd Edition FP1]] | ||
{{ArticleMetaData <!-- v1.2 --> | {{ArticleMetaData <!-- v1.2 --> | ||
|sourcecode= <!-- Link to example source code (e.g. [[Media:The Code Example ZIP.zip]]) --> | |sourcecode= <!-- Link to example source code (e.g. [[Media:The Code Example ZIP.zip]]) --> | ||
Latest revision as of 09:41, 15 June 2012
Fixed in new later firmware version.
Article Metadata
Tested with
Compatibility
3rd Edition, FP1
Article
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.
