trunk setup frustration

[dandenson]

using bandwidth.com.

If i have a site with a few dozen DID's, it's quite a pain to setup 2 trunks and having 2 trunks with identical DIDs causes confusion through inbound rules and call routing.

It would be absolutely ideal to have a trunk have the option for multiple IP addresses. Remove all the frustration.

 

[AWS2P]

Hi ,
what is the problem ? you need to use two trunks and want same config on both?

What for ? to be sure to have calls ?

Trunk is not the only part of puzzle, phone failure can be caused by lot of others part, link internet provider, computer, router, switch, power ......

So double trunk change nearly nothing if this is the only secure part of SIP chain.

 

[dandenson]

When the upstream provider sources calls from 2 different IPs, you need trunks for each. Simple as that.

 

[cobaltit]

When the upstream provider sources calls from 2 different IPs, you need trunks for each. Simple as that.

When using IP authentication

 

[dandenson]

yes, sorry, excuse the assumption that readers knew bandwidth.com is IP based.

 

[BrenttG]

SIPTrunk.com also requires this even though they are digest based, because they provide a secondary trunk for failover from an alternate datacenter. We are actually hoping for a DID import from CSV feature, so we can import a list of additional DIDs to each trunk from CSV, as sometimes we have to setup systems with 50-100 DIDs, x 2 trunks, a lot of menial time operating the 10 key.