From: Arun Ravindran <ext-arun.1.ravindran@nokia.com>
To: ofono@ofono.org
Subject: Re: [RFCv3] doc: Proposal for LTE/IMS API
Date: Wed, 02 Mar 2011 13:18:12 +0200 [thread overview]
Message-ID: <4D6E2774.4000803@nokia.com> (raw)
In-Reply-To: <1297377234-5056-1-git-send-email-sjurbren@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
Hi Sjur
> +
> + boolean VoiceOverPs [readonly]
> +
> + IMS voice is enabled by network
> + Related AT command: AT+CIREP.
> +
> + string CsHandoverProgress [readonly, optional]
> +
> + Indicates the handover progress status during a CS
> + fallback procedure. The possible values are:
> + "started" - CS Fallback procedure has started
> + "complete" - CS Fallback procedure has completed
> + "failure" - CS Fallback has failed
> + "idle" - No CS call or fallback is ongoing
> +
> + Related AT URC: +CIREP
> +
+CIREP reports SRVCC and IMSVOPS events (27.007). As per 23.216, SRVCC
is basically a handover of CS voice call anchored in IMS to CS domain.
But the property values for csHandoverProgress descriptions says "CS
Fall back procedure", which i think is wrong. How about changing "CS
Fallback" to "PS-CS SRVCC Handover"
CS fall back and SRVCC are not the same, to my understanding. For SRVCC
the call should be based in IMS and it is a handover, and CSFB happens
not during call, but before it.
Correct me if i am wrong.
regards
Arun
next prev parent reply other threads:[~2011-03-02 11:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-10 22:33 [RFCv3] doc: Proposal for LTE/IMS API Sjur =?unknown-8bit?q?Br=C3=A6ndeland?=
2011-02-15 14:02 ` Pekka Pessi
2011-03-02 11:18 ` Arun Ravindran [this message]
2011-03-03 15:29 ` Arun Ravindran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D6E2774.4000803@nokia.com \
--to=ext-arun.1.ravindran@nokia.com \
--cc=ofono@ofono.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.