2 Replies Latest reply on Nov 19, 2013 11:38 AM by david

    Netvanta 6242 trunk to trunk routing question

    voiceman55 New Member

      Hello,

       

      I have a NV6242 that is connected to the telco via two PRIs on one side, and via SIP trunks towards SBCs on the other.

      While doing initial test, I was able to get one PRI up in service and originate successful calls from the PSTN towards the SBC and vice versa (trunk-trunk call).

       

      Now here is the fun part about how the gateway should behave:

       

      1. Calls from the PRIs (originating from PSTN) should simply be automatically passed as-is to the SBCs (via SIP Trunks) regardless of the dialed TN.
      2. Calls from the SBCs (originates from the SIP Trunk) should be terminated on either one of the  PRIs based on the dialed number.   The key differentiator is the NPA dialed.

       

      Here is an example for item 2:

      PRI-1 (voice trunk T01) will only accept calls placed to TNs in NPA "200" (like 200-555-1212)  *and* if the PRI is full, calls will overflow into PRI-2.

      PRI-2 (voice trunk T02) will accept calls to both NPA "200" and "201".  However a call to NPA 200 should first be tried on PRI-1 then overflow here.

       

      It is worth noting that the SBC trunk is defined as voice trunk "S01".

       

      Could anyone help me with a template that would do just that ?

       

      Also,  is there a way to add SIP headers towards the SBC adding information on the voice trunkgroup/PRI that was used as the origination point ?

      Is it possible for the SBC to influence routing to a particular voice trunkgroup/PRI  with the use of SIP headers ?

       

      Thank you!

        • Re: Netvanta 6242 trunk to trunk routing question
          david Employee

          Voiceman55,

           

          Thanks for posting.  Below is an example of the relevant portions of the configuration that match your requirements for call routing.

           

          voice trunk T01 type isdn

          !

          voice trunk T02 type isdn

          !

          voice trunk T03 type sip

            sip-server primary <SIP server IP address>

          !

          voice grouped-trunk PRI1

            trunk T01

            accept 200-NXX-XXXX cost 0

          !

          voice grouped-trunk PRI2

            trunk T02

            accept 200-NXX-XXXX cost 10

            accept 201-NXX-XXXX cost 0

          We also have a trunk group identifier feature (RFC 4904), that when combined with Source and ANI Based Routing (SABR) and two separate SIP trunks, can provide information regarding the source trunk.  Below is an example showing the relevant configuration.

           

          voice trunk-list PRI1

            trunk T01

          !

          voice trunk-list PRI2

            trunk T02

          !

          voice trunk T01 type isdn

          !

          voice trunk T02 type isdn

          !

          voice trunk T03 type sip

            sip-server primary <SIP server IP address>

            trunk-group-id <label> <context>

          !

          voice trunk T04 type sip

            sip-server primary <SIP server IP address>

            trunk-group-id <label> <context>

          !

          voice grouped-trunk SIP1

            trunk T03

            accept $ cost 0

            permit list PRI1

          !

          voice grouped-trunk SIP2

            trunk T04

            accept $ cost 0

            permit list PRI2

          Our guide Trunk Group Identifier Quick Configuration Guide goes over the Trunk Group ID feature.



          Hope this helps,

          David

          • Re: Netvanta 6242 trunk to trunk routing question
            david Employee

            Voiceman55,

             

            I went ahead and flagged the "Correct Answer" on this post to make it more visible and help other members of the community find solutions more easily. If you don't feel like the answer I marked was correct, feel free to come back to this post and unmark it with the applicable buttons.  If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.

             

            Thanks,

            David