Limit SIP Trunk Outbound Over-use

[bluewhite4]

Does anyone know of a way to limit the number of outbound calls on a SIP peer profile? We've got a SIP link, for 4 DID's and then long distance, using 7 trunks. We want to limit the number of sip trunks used for outbound long distance to 3, with roll-over to the PRI, so that we try and maintain 4 SIP trunks for incoming calls. Any ideas?

[brantn]

Someone correct me if I am wrong but there is no way to limit SIP trunks. However as far as failover goes just make a route list in ARS with the second route being the pri.

[v2win]

Could you build 2 SIP Peer profiles?

One with 3 trunks and one with 4 trunks with the same registration information.

In ARS point your outbound to the profile with 3 trunks.

Might work

[rutger]

Could you build 2 SIP Peer profiles?

One with 3 trunks and one with 4 trunks with the same registration information.

In ARS point your outbound to the profile with 3 trunks.

Might work

That should work, depending on your provider. A nicer option might be to make a loopback ip trunk. So an ip trunk towards the controller itself. You can limit the number of trunks on this. You can route your outbound traffic through this. If all channels are used, and you want it to switch to your 2nd route, you should use a route list with the loopback trunk 1st and 2nd isdn.

You would need ip networking/enterprise lic for this to work....

[ralph]

Great solution rutger.
Somehow in the back of my mind I was thinking along those lines but it just didn't gel until you put it out there.

Ralph

[brantn]

As far as double registration you would have to check with your peer most of them only allow siingle registrations or I should say a double registration overwrites the first one (ie register xlite as an extension it will overwrite the first one).