The Adtran community holiday season is starting next week! The holiday period will span from December 21, 2024 to January 6, 2025. During this time, responses to feedback form submissions may be delayed. If you are encountering product issues, you can reach out to Adtran support at any time.
cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Anonymous
Not applicable

how to re route tfn or did calls to specific t1

Jump to solution

I am using TA908e with the latest firmware.

I have configured 2 t1 as pri idsn circuits and 1 sip provider. I would like to route inbound calls from certain DID/TFN to a specific t1 pri/isdn port. Is this doable?

0 Kudos
1 Solution

Accepted Solutions
jayh
Honored Contributor
Honored Contributor

Re: how to re route tfn or did calls to specific t1

Jump to solution

This is done in the voice grouped-trunk section of the configuration. Assign each PRI a different trunk number. Create a voice grouped-trunk referencing each trunk and list the matching DIDs that you want routed to that PRI under it. You can also assign a cost metric to each so that if one PRI is busy or down the other will be used as a backup.

You can also route calls based on the originating number rather than the destination using SABR (Source ANI-Based Routing). Details here: https://supportforums.adtran.com/docs/DOC-1862

View solution in original post

0 Kudos
1 Reply
jayh
Honored Contributor
Honored Contributor

Re: how to re route tfn or did calls to specific t1

Jump to solution

This is done in the voice grouped-trunk section of the configuration. Assign each PRI a different trunk number. Create a voice grouped-trunk referencing each trunk and list the matching DIDs that you want routed to that PRI under it. You can also assign a cost metric to each so that if one PRI is busy or down the other will be used as a backup.

You can also route calls based on the originating number rather than the destination using SABR (Source ANI-Based Routing). Details here: https://supportforums.adtran.com/docs/DOC-1862

0 Kudos