SX2K Intermachine Traffic Choke 1

[MitelInMyBlood]

Scenario: 2 SX2K machines in tandem with a single 6-channel CEPT route (not a list) between them. Purpose is to limit the number of concurrent **TRUNK** calls to a specific extension. In other words, a traffic choke.

The idea is to be able to send the Q.931 reason code upstream (over PRI) to the IXC whenever congestion is encountered on the 6-channel intermachine span (between the sx2k's).

The customer wants special intercept treatment (a custom recording) which the IXC said they can do.

The problem is the upstream 2K seems to auto-queue or camp-on to that trunk group whenever it's full and we don't want that to happen. If I manbusy the trunk group then it works, but if I manbusy only 5 of the 6 trunks and have a valid call on trunk #6 all subsequent calls camp on to the TG waiting for an available trunk. I thought we did this years ago but apparently I didn't take good notes on what I had to do.

Any suggestions? (auto camp-on timer is blank)
Thanks.

 

[MitelInMyBlood]

Nudge - anyone??

 

[becca1jane]

What about setting up a route list and having the second route in the list be able to route the callers to the recording when the first route is busy. If you have any trunks looped back into the system this is easy to do with digit mod, otherwise if you aren't using intercept handling you could set up the second route to be toll-denied and route the call to the dn of the recording.

 

[MitelInMyBlood]

Thanks for the idea. Yes, the 1st plan would work and may be a solution if the client presses me. The desired plan was to halt the traffic externally to avoid the toll charge but seems the only way to do that is order a dedicated PRI equipped w/only 6 channels. Seems like stepping over dollars to pick up dimes if you ask me. Also the IXC wants a $600 setup chg + $150 monthly + .06 per call for custom intercept treatment and this .06 applies to all traffic presented to the trunk group, not just those that choke. I'm going to see if I can sell 'em on -not- doing it.
Thanks again for the idea.