Hi Kai,
>>> + array{dict,array{dict}} QosFilters [readonly, optional]
>>> +
>>> + Information about the QoSes and associated Packet
>>> + Filters for the Default PDN and it's dedicated bearers.
>>> + It is organized as a list of QoS definitions with
>>> + a list of corresponding packet filters.
>>
>> We really need to understand what the IMS application will need. If
>> this is about codecs or other things, then maybe oFono should give codec
>> advise directly. Proposals are welcome. Right now this looks like going
>> overboard.
>
> this is used e.g. for SDP preconditions mechanism used in IMS:
> http://www.faqs.org/rfcs/rfc3312.html
>
> The QoS is signalled on a per port/media basis, so relaying
> the packet-filters seems like a sane approach to me (cannot really
> say the same about 3312, but that's a different thing ;P).
OK, good to hear.
The 27007 spec specifies the following responses related to TFT/QoS:
+CGTFTRDP: <cid>,<packet filter identifier>,<evaluation precedence index>,
<source address and subnet mask>,<protocol number (ipv4) / next header (ipv6)>,
<destination port range>, <source port range>,<ipsec security
parameter index (spi)>,
<type of service (tos) (ipv4) and mask / traffic class (ipv6) and mask>,
<flow label (ipv6)>,<direction>,<NW packet filter Identifier>
+CGEQOSRDP: <cid>,<QCI>,[<DL_GBR>,<UL_GBR>],[<DL_MBR>,<UL_MBR>]
I tried to pick the minimal set of interesting parameters,
but I would really love some feedback on this from someone who knows
more about the IMS requirements here.
Regards,
Sjur
_______________________________________________
ofono mailing list
[email protected]
http://lists.ofono.org/listinfo/ofono
