Field Summary
private boolean	anchoringNotificationEnabled
private String	announcementUri
CallAnchoringNotificationType	ANNOUNCEMENT
CallAnchoringNotificationType	DTMF_TONES
CallAnchoringNotificationType	NONE
private String	dtmfTones
private CallAnchoringNotificationType	notificationType
private TermAnchoringPolicy	termAnchoringPolicy
TermAnchoringPolicy	UNCONDITIONAL
TermAnchoringPolicy	WIFI_REGISTERED

Field Detail

anchoringNotificationEnabled

private boolean anchoringNotificationEnabled

the anchoringNotificationEnabled flag indicates whether (TRUE) call
anchoring notification is required such that the subscriber should hear an
audible indication that the call has been anchored. The indication may be
delivered as an announcement (based on an announcement URI) or via a DTMF
tones pattern.
NOTE: The call anchoring notification may also be used to indicate to a
subscriber what identity is currently active on terminating calls

Multiplicity:

announcementUri

private String announcementUri

The announcementUri attribute contains the URI of the announcement which should be played to the client to indicate that the call has been anchored to the CSN. MCS plays the annoucement only when the announcementEnabled flag is set (TRUE).
Constraints:
- must not be null if anchoringNotificationEnabled == true and notificationType == ANNOUNCEMENT
- see Uri constraints
Default:
- none
Clone:
- yes, verbatim

Multiplicity:

dtmfTones

private String dtmfTones

The dtmfTones attribute contains the DTMF tones which should be generated by the CallAnchoring capability to indicate to the client that a call has been anchored to the CSN. The dtmfTones are only generated when the dtmfTonesEnabled flag is set (TRUE). The DTMF tones are specified by defining the tone 0,1,2,3,4,5,6,7,8,9,*,# then specifying the duration (in milliseconds) of the tone. As such, tone lists are specified as :-: using "-" as a separator for the tones and ":" as a separator for the duration. (See regular expression for further details). An example tone specification is 1:2-*:4-4:2
Constraints:
- [\d\#\*]:\d{1,5}(-[\d\#\*]:\d{1,5})*
- must not be null if anchoringNotificationEnabled == true and notificationType == DTMF_TONES
Default:
- none
Clone:
- yes, verbatim

Multiplicity:

notificationType

private CallAnchoringNotificationType notificationType

the anchoringNotificationType indicates what mechanism should be used to
notify the subscriber that the call has been anchored.
Constraints:
- must "DTMF_TONES" | "ANNOUNCEMENT"
- must be NONE if anchoringNotificationEnabled == FALSE
- must not be NONE if anchoringNotificationEnabled == TRUE
Default:
- DTMF_TONES
Clone:
- yes, verbatim

Multiplicity:

termAnchoringPolicy

private TermAnchoringPolicy termAnchoringPolicy

TermAnchoringPolicy describes whether Subscriber terminated calls should be anchored to the CSN. The policy is ONLY applied currently in cases where the Subscriber has ONLY a single dual mode device. The policy allows the CSN to tune anchoring so as to support not anchoring Subscriber terminated calls in cases when the Subscriber is roaming. As such, not anchoring avoid backhauling the call to the Subscriber's home network when the Subscriber is roaming.
Possible values for the TermAnchoringPolicy are:
- WIFI_REGISTERED: Only anchor the call if the ONLY device provisioned against the Subscriber is a dual mode device and the WiFi Endpoint status is ON_LINE (i.e. registered)
- UNCONDITIONAL: Anchor the call regardless of the dual mode WiFi Endpoint status
TerminationAnchoringPolicy was originally introduced for France Telecom in Release 3.3.1 as "selective anchoring" CR180
Constraints:
- "WIFI_REGISTERED" | "UNCONDITIONAL"
Default:
- "UNCONDITIONAL"
Clone:
- yes, verbatim

Multiplicity:

Class

Tree

PREV CLASS NEXT CLASS

FRAMES NO FRAMES

SUMMARY: INNER | FIELD | CONSTR | METHOD

DETAIL: FIELD | CONSTR | METHOD