cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
New Contributor II

Routing Multiple FXS ports to Respective SIP Trunks

Jump to solution

Here is the basic setup:

We have a cloud PBX, and do SIP Trunking.

We are installing in a condo complex, putting a 908 in each building to handle the 8 condo units in the building. Each unit is a separate SIP Trunk on the PBX.

On the Adtran 908, I have (8) different SIP trunks configured. They are all configured T01-T08.

Each FXS port is assigned to a user - the user in this case being a 10 digit TN. Each FXS port is set to register its respective Trunk (i.e. FXS0/1 registers T01, and so on)

All the SIP Trunks register.

My issue is this:

When I call out from any ports, they always seem to go out T01, instead of there respective trunks. How can this be solved? I have tried several ways, and not had any luck.

Thank you for any help you may be able to provide

0 Kudos
Reply
1 Solution

Accepted Solutions
Highlighted
Honored Contributor
Honored Contributor

Re: Routing Multiple FXS ports to Respective SIP Trunks

Jump to solution

Why a separate SIP trunk for each FXS?  The same trunk can handle all FXS ports and allow them to register separately by SIP identity, or you can register the trunk as a pilot.  Your cloud PBX can sort and bill the calls based on ANI. 

If you really want to do this, you can use SABR.

voice ani-list fxs1-ani-list

  ani 3125550101

voice ani-list fxs2-ani-list

  ani 3125550102

...and so on, then

voice grouped-trunk sip1-tg

  trunk T01

  [rest of configuration]

  permit list fxs1-ani-list

voice grouped-trunk sip2-tg

  trunk T02

  [rest of configuration]

  permit list fxs2-ani-list

...and so on

View solution in original post

0 Kudos
Reply
3 Replies
Highlighted
Honored Contributor
Honored Contributor

Re: Routing Multiple FXS ports to Respective SIP Trunks

Jump to solution

Why a separate SIP trunk for each FXS?  The same trunk can handle all FXS ports and allow them to register separately by SIP identity, or you can register the trunk as a pilot.  Your cloud PBX can sort and bill the calls based on ANI. 

If you really want to do this, you can use SABR.

voice ani-list fxs1-ani-list

  ani 3125550101

voice ani-list fxs2-ani-list

  ani 3125550102

...and so on, then

voice grouped-trunk sip1-tg

  trunk T01

  [rest of configuration]

  permit list fxs1-ani-list

voice grouped-trunk sip2-tg

  trunk T02

  [rest of configuration]

  permit list fxs2-ani-list

...and so on

View solution in original post

0 Kudos
Reply
Highlighted
New Contributor II

Re: Routing Multiple FXS ports to Respective SIP Trunks

Jump to solution

I fully agree with your statement above... you would think the cloud PBX would allow this, but it doesn't. It allots a whole new account for each channel since they are different customers. So the traffic has to come in and go out the proper SIP. I will attempt this later today on my trial Adtran. Thank you so much for your help!

0 Kudos
Reply
Highlighted
New Contributor II

Re: Routing Multiple FXS ports to Respective SIP Trunks

Jump to solution

This worked perfect! Thank you for your help!

0 Kudos
Reply