Package mcs
mcs package contains the Mobile Continuity Service and its associated subscription/preferences artifacts

 
Class Diagram Summary
mcsmcs package contains the Mobile Continuity Service and its associated subscription/preferences artifacts
 
Note Summary
Unknown Name 
Unknown Name 
Unknown Name 
Unknown Name 

 
Class Summary
AutoReconnectPref 
CallAnchoringPref 
CallForwardingPref 
ConferencePref 
DcePref 
HandoverPref 
McsIdentityPref 
McsService 
McsServiceDefinition 
McsSubscriberPref 
McsSubscription 
MimPref 
MobileExtensionPref 
MwiPref 
PersonalHandbackPref 
PersonalPickupPref 
PickupPref 
RingingDeviceSet 
RingingDeviceSetEntry 
RingingPref 
RingingSchedule 
RingingScheduleEntry 
SmsPref 
VmForwardingPref 
VpnPref 

 
Instance Specification Summary
InstanceSpecification1 
Package Elements Detail
InstanceSpecification1
Visibility:
private
 

Unknown Name
Note text:
RingingPref.ringbackAnnouncementUri ask Boris about media server support (will the uri format suffice?)
Does the SMPP and SMOIP domain have to be a specific domain type? e.g. CELLULAR, DIRECT
 

Unknown Name
Note text:
sequential termination attempt enabled - flag set to indicate whether to rely on Endpoint presence when estblishing calls. When the flag is set the wifiNotReachableTimeout is used to try the device for a short period
- what happened to
 

Unknown Name
Note text:
Subscription and Pref details TBD based on blending of 3.4.1 MCS attributes with 3.5 feature updates
 

Unknown Name
Note text:
parameters with _ prefix were placed from 3.4 console but not specified in the FS.
Cellular network type may be a Two Stage Dialing attribute
Should ringback announcement uri be per identity?
Should the auto reconnect capability prefs be Subscriber based instead of identity?