18 on the device, the <filepath>.TSY</filepath> may support a single mode for |
18 on the device, the <filepath>.TSY</filepath> may support a single mode for |
19 example GSM or be multimode. </p> |
19 example GSM or be multimode. </p> |
20 <p>The following diagram shows these component relationships: </p> |
20 <p>The following diagram shows these component relationships: </p> |
21 <fig id="GUID-9006D69B-605B-554C-9836-155062098DE8"> |
21 <fig id="GUID-9006D69B-605B-554C-9836-155062098DE8"> |
22 <title> Multimode ETel component architecture </title> |
22 <title> Multimode ETel component architecture </title> |
23 <image href="GUID-E55B3ACD-4651-5FBD-AC9F-511E5CBCC0C9_d0e46311_href.png" placement="inline"/> |
23 <image href="GUID-E55B3ACD-4651-5FBD-AC9F-511E5CBCC0C9_d0e50545_href.png" placement="inline"/> |
24 </fig> |
24 </fig> |
25 <p>Much of the functionality defined in Multimode ETel is <i>optional</i>, |
25 <p>Much of the functionality defined in Multimode ETel is <i>optional</i>, |
26 meaning that a .TSY is not required to support it. Clients should use the |
26 meaning that a .TSY is not required to support it. Clients should use the |
27 capability-checking interfaces supplied by Multimode ETel to ensure that such |
27 capability-checking interfaces supplied by Multimode ETel to ensure that such |
28 functionality is available before attempting to use it. </p> |
28 functionality is available before attempting to use it. </p> |
29 <section id="GUID-68CA7D2A-AB2E-4ADC-9286-337D6D15D34F"><title>Description</title> <p>The diagram below shows the key classes |
29 <section id="GUID-68CA7D2A-AB2E-4ADC-9286-337D6D15D34F"><title>Description</title> <p>The diagram below shows the key classes |
30 in the Core and Multimode APIs and their inheritance relationships. The top |
30 in the Core and Multimode APIs and their inheritance relationships. The top |
31 package is ETel Core, the lower package is Multimode ETel. </p> <fig id="GUID-90475AD2-04DF-5ECE-BA0D-28FD9500E6AB"> |
31 package is ETel Core, the lower package is Multimode ETel. </p> <fig id="GUID-90475AD2-04DF-5ECE-BA0D-28FD9500E6AB"> |
32 <title> Multimode ETel key classes </title> |
32 <title> Multimode ETel key classes </title> |
33 <image href="GUID-9147F8AF-01B3-5110-8FE7-A6318B5048D9_d0e46332_href.png" placement="inline"/> |
33 <image href="GUID-9147F8AF-01B3-5110-8FE7-A6318B5048D9_d0e50566_href.png" placement="inline"/> |
34 </fig> <p>The key Multimode ETel classes are R-classes. The purpose of these |
34 </fig> <p>The key Multimode ETel classes are R-classes. The purpose of these |
35 classes is to communicate with the telephony server. All of the classes shown |
35 classes is to communicate with the telephony server. All of the classes shown |
36 derive, directly or indirectly, from <xref href="GUID-9CE46AD7-722E-3831-A359-C90A350E931D.dita"><apiname>RTelSubSessionBase</apiname></xref>, |
36 derive, directly or indirectly, from <xref href="GUID-9CE46AD7-722E-3831-A359-C90A350E931D.dita"><apiname>RTelSubSessionBase</apiname></xref>, |
37 which manages a sub-session to the telephony server. </p> <p>The classes are |
37 which manages a sub-session to the telephony server. </p> <p>The classes are |
38 summarised below: </p> <ul> |
38 summarised below: </p> <ul> |