How to force SIP trunks un-availble?

[f0netech]

I am reasonbly new to the organization I'm working for and this is my first postion where SIP trunks have been implemented.

S8720 servers, CM 5.1.2 and they have managed the SIP trunking primarily through the carrier (Sprint), as far as I've found there is use of session manager server. At the two main offices, SIP trunks are enabled with a PRI at each for backup. During a recent Sprint outtage, we were hoping to rely on the PRI's for calling by performing a standard 'busy' command on the SIP trunks, but much to everyone's surprise the outbound calls still tried to traverse out over the SIP trunks.

Is there another method required with SIP trunks to make them completely un-available? My first thought would be to change the FRL within the route patterns so that user's do not have permission, but there are many branch offices and would require a LOT of Route pattern changes before and after the fact.

Any suggestions?

 

[AvayaTier3]

busy the signaling-group, busy the trunk-group

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[montyzummer]

Follow the above advice and you can also add the pri trunk group in the sip route patterns to ensure they trip in fail over or all busy.

APSS (SME)
ACSS (SME)
ACIS (UC)