LibPRI
  1. LibPRI
  2. PRI-39

[patch] encode and decode Low Layer Compatibility

    Details

    • Type: New Feature New Feature
    • Status: Open
    • Severity: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Target Release Version/s: None
    • Component/s: NewFeature
    • Labels:
      None
    • Mantis ID:
      13055
    • Regression:
      No

      Description

      Hi!

      This patch adds support for encoding and decoding of the low layer comaptibility IE.

                • ADDITIONAL INFORMATION ******

      This for example can be used to signal H324M videocalls in LLC instead of Bearer Capability. Sample Usage: together with ASTERISK-9891

        Issue Links

          Activity

          Hide
          klaus3000 added a comment -

          FYI: I am reworking this patch at the moment ...

          Show
          klaus3000 added a comment - FYI: I am reworking this patch at the moment ...
          Hide
          Tilghman Lesher added a comment -

          There is currently a branch with progress made already:
          /libpri/team/group/issue10217

          It would probably be best if you made your changes against this branch directly.

          Show
          Tilghman Lesher added a comment - There is currently a branch with progress made already: /libpri/team/group/issue10217 It would probably be best if you made your changes against this branch directly.
          Hide
          klaus3000 added a comment -

          looks great, full LLC support. Is there also somewhere a branch which shows how to use this from Asterisk/chan_dahdi?

          How is the LLC negotiation triggerd from within Asterisk?

          Show
          klaus3000 added a comment - looks great, full LLC support. Is there also somewhere a branch which shows how to use this from Asterisk/chan_dahdi? How is the LLC negotiation triggerd from within Asterisk?
          Hide
          Tilghman Lesher added a comment -

          That is all still being worked on, but the general gist is that the structure will be exposed through the libpri header. Still to be determined is how the information propagates through multiple channel drivers, as well as how we ensure that the information from LLC stays consistent with bearer information.

          Show
          Tilghman Lesher added a comment - That is all still being worked on, but the general gist is that the structure will be exposed through the libpri header. Still to be determined is how the information propagates through multiple channel drivers, as well as how we ensure that the information from LLC stays consistent with bearer information.
          Hide
          klaus3000 added a comment -

          just as a note: I think bearer information and LLC can differ a little bit. I once had the problem that the switch accepted a H324M SETUP message only if the UL1 was only present in LLC, but not in BI.

          Show
          klaus3000 added a comment - just as a note: I think bearer information and LLC can differ a little bit. I once had the problem that the switch accepted a H324M SETUP message only if the UL1 was only present in LLC, but not in BI.
          Hide
          Tilghman Lesher added a comment -

          Please see Q.931, Appendix I, Item I.2.5 (page 274 in 05/98), first paragraph: "There shall be no contradiction of information between the Low layer compatibility and the Bearer capability at the originating side." and second paragraph: "If as a result of duplication, a contradiction occurs between the Bearer capability information element and the Low layer compatibility information element at the terminating side, the receiving entity shall ignore the conflicting information in the Low layer compatibility information element."

          Show
          Tilghman Lesher added a comment - Please see Q.931, Appendix I, Item I.2.5 (page 274 in 05/98), first paragraph: "There shall be no contradiction of information between the Low layer compatibility and the Bearer capability at the originating side." and second paragraph: "If as a result of duplication, a contradiction occurs between the Bearer capability information element and the Low layer compatibility information element at the terminating side, the receiving entity shall ignore the conflicting information in the Low layer compatibility information element."
          Hide
          klaus3000 added a comment -

          Ok. This makes it clearly that if for example UL1 is present in BC and LLC, its value must be the same. But if UL1 is for example only present in LCC, but not in BC - is this a contradiction?

          I only know that I once hat the problem with H324M in UL1 in BC.

          Show
          klaus3000 added a comment - Ok. This makes it clearly that if for example UL1 is present in BC and LLC, its value must be the same. But if UL1 is for example only present in LCC, but not in BC - is this a contradiction? I only know that I once hat the problem with H324M in UL1 in BC.

            People

            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development