0 Replies Latest reply on Oct 28, 2015 6:43 PM by jayh

    TA900e with two PRIs in one trunk - inconsistency between CLI and GUI

    jayh Hall_of_Fame

      Scenario: We have a TA900e Gen. 3 where we are delivering two PRIs to a customer PBX for a total of 46 talk paths as one bundle. When we configure using the CLI we build it as follows:

       

      !

      interface t1 0/3

        description Handoff to PBX

        tdm-group 1 timeslots 1-24 speed 64

        no shutdown

      !

      interface t1 0/4

        description Handoff to PBX #2

        tdm-group 1 timeslots 1-24 speed 64

        no shutdown

      !

      interface pri 1

        description pri 1

        isdn name-delivery setup

        connect t1 0/3 tdm-group 1

        digits-transferred 4

        role network b-channel-restarts enable

        no shutdown

      !

      interface pri 2

        description pri 2

        isdn name-delivery setup

        connect t1 0/4 tdm-group 1

        digits-transferred 4

        role network b-channel-restarts enable

        no shutdown

      !

      !

      [snip]

      !

      !

      isdn-group 1

        connect pri 1

        connect pri 2

      !

      !

      [snip]

      !

      !

      voice trunk T01 type isdn

        description "ISDN-PBX"

        resource-selection linear ascending

        connect isdn-group 1

        no early-cut-through

        modem-passthrough

        rtp delay-mode adaptive

      !

      !

      Notice how both PRIs are bundled into one isdn-group and there is one voice trunk connected to isdn-group 1.

       

      In the GUI, however, the voice trunk drop-down doesn't have the option to connect to the isdn-group, just a single individual PRI interface:

       

      Screen Shot 2015-10-28 at 6.29.51 PM.png

       

      In the GUI voice trunk setup, one can't select the isdn-group. The only way to make it work is to configure a separate trunk for each PRI and then include both trunks in the voice grouped-trunk for inbound calls. This breaks circular hunt as the first trunk in the grouped-trunk will go circular until it's full and then and only then will the second trunk be used.

       

      We haven't finished conclusive testing but it looks like when using the CLI method we *may* not be able to take calls on the second PRI.

       

      It makes sense to group the physical interfaces into an isdn-group and then connect the group to the trunk, but is this the right way to do it?

       

      Why does the CLI use the isdn-group and the GUI use the physical PRI interface?