- As per TR181, there could be one or more unique keys for each
multi-instance object. Added support to get the unique keys
associated with the multi-instance object.
- Changes for generate_source_code.sh to have unique keys as
extra object parameter.
- Device.WiFi.Radio.1.SupportedStandards : fix its value
- Device.WiFi.EndPoint.1.WPS.ConfigMethodsEnabled : fix its set value
- Device.WiFi.EndPoint.1.WPS.PIN : fix its set value
- Device.WiFi.EndPoint. : fix segfault when calling delete_obj all
This is l3 QinQ basically, the support is added for the provider bridge
residential domain scenario, details as mentioned in tr181 issue 2,
amendment 13 as follows:
In the Residential Domain scenario untagged traffic is routed from the Ethernet and SSIDa
interfaces and tagged with a customer VLAN tag (C-TAG) of VLANa and then double tagged
with a Service Provider VLAN tag (S-TAG) of VLANx. This requires the use of:
• 802.1d Bridge instance: This object bridges the residential domain traffic to the Router.
• Layer3 Forwarding Rule: This object ensures that traffic between the Bridge and
VLANTermination objects is forwarded to the correct interface. The Rule utilizes the IP
Interfaces of the Bridge (IP Intf: Bridge_a) and Residential Domain (IP Intf: Residential)
• VLANTermination object (C-TAG): The C-TAG is applied and removed for traffic
egress and ingress to the IP Intf: Residential interface.
• VLANTermination object (S-TAG): The S-TAG is applied and removed for traffic from
and to the C-VLAN termination object.
Both config and end to end traffic after setup have been tested.
Note: partially resolves ticket #3101
The major changes are for more TR-104 compliant.
- Changes those static objects to dynamic ones although they can have only one instance
- Make some paraters' values compliant to the data model
Device.Services.VoiceService.{i}.SIP.Network.{i}.Enable
Device.Services.VoiceService.{i}.VoIPProfile.{i}.RTP.SRTP.KeyingMethods
Device.Services.VoiceService.{i}.VoIPProfile.{i}.RTP.SRTP.EncryptionKeySizes
Note that KeyingMethods and EncryptionKeySizes are not configurable in Asterisk
so writting to these two parameters will return FAULT_9000.
