| | | | SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
|
|
network
public class Device
Device represents the tool through which the Subscriber communicates. Devices are provisionable and clonable.
Links:
Kernel Association is controlled by
A Device may be controlled by zero or more Client applications. A Client may only control a single Device.
Constraints:
- see Client constraints
Default:
- none
Clone:
- no, this is not a provisionable attribute
Associates type:
association
Client cardinality:
1
Client navigability:
NOT NAVIGABLE
Client visibility:
private
Supplier cardinality:
0..*
Supplier navigability:
NAVIGABLE
Supplier visibility:
private
Custom properties
associates:
network.Client
Kernel Association Association Link
A Device defines the Indentity which should be used for cases when communications are originated from the Device.
Label: Originating Identity
Constraints:
- must be a valid Identity
- see Identity constraints
Default:
- none
Clone:
- yes, deep. The cloned Device references the cloned Identity (the cloned Identity of the same name)
Associates type:
association
Client cardinality:
0..*
Client navigability:
NOT NAVIGABLE
Client visibility:
private
Supplier cardinality:
1
Supplier navigability:
NAVIGABLE
Supplier visibility:
private
Kernel Association Association Link
A Device may manifest multiple Endpoints. For example a dual-mode device manifests an IP Endpoint and a mobile Endpoint. An Endpoint may be manifested by exaclty one Device.
Constraints:
- see Endpoint constraints
Default:
- none
Clone:
- yes deep. The cloned Device references a deep clone of each of the Endpoints
Associates type:
aggregation
Client cardinality:
1
Client navigability:
NOT NAVIGABLE
Client visibility:
private
Supplier cardinality:
0..*
Supplier navigability:
NAVIGABLE
Supplier visibility:
private
Custom properties
associates:
Endpoint
link:
aggregation
| Nested Class Summary |
public class |
Origin |
| Field Summary |
private List |
|
private Collection |
|
private String |
|
private Origin |
|
Origin |
AGENT_PROVIDED |
Origin |
SUBSCRIBER_PROVIDED |
|
|
private boolean |
|
private List clients
A Device may be controlled by zero or more Client applications. A Client may only control a single Device.
Constraints:
- see Client constraints
Default:
- none
Clone:
- no, this is not a provisionable attribute
Multiplicity:
1
Custom properties
associates:
network.Client
private Collection endpoints
A Device may manifest multiple Endpoints. For example a dual-mode device manifests an IP Endpoint and a mobile Endpoint. An Endpoint may be manifested by exaclty one Device.
Constraints:
- see Endpoint constraints
Default:
- none
Clone:
- yes deep. The cloned Device references a deep clone of each of the Endpoints
Multiplicity:
1
Custom properties
associates:
Endpoint
private String name
The name attribute uniquely identifies the Device within the Subscriber in human readable form.
Constraints:
- .{1,64}
- must be unique within the Subscriber
- may not be null
Default:
- the name attribute may be populated with the concatination of the Device Endpoint addresses by default
Clone:
- yes, verbatim
Multiplicity:
1
private Origin origin
origin represents the source of the device provisioning information as
provided by the subscriber or the the provisioning agents.
Constraints:
- "AGENT_PROVIDED" | "SUBSCRIBER_PROVIDED"
Default:
- "AGENT_PROVIDED"
Clone:
- yes, verbatim
Multiplicity:
1
A Device defines the Indentity which should be used for cases when communications are originated from the Device.
Label: Originating Identity
Constraints:
- must be a valid Identity
- see Identity constraints
Default:
- none
Clone:
- yes, deep. The cloned Device references the cloned Identity (the cloned Identity of the same name)
Multiplicity:
1
private boolean securePickupEnabled
securePickupEnabled is a flag that indicates whether (TRUE) the subscriber must terminate the original call leg prior to the pickup being completed, or (FALSE) that the pickup should be performed immediately. NOTE: Similarly to Endpoint.ringEnabled this attribute is actually a service parameter of the MCS pickup capability. For provisioning simplicity is has been added to the Device in Release 3.5.
Contraints:
- none
Default:
- false
Clone:
- yes, verbatim
Multiplicity:
1
| | | | SUMMARY: INNER | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
|
|