Denial Even 1195: Circ/Channel Unavail D1=0x3c

[fluffheadsr]

Recently users started reporting outgoing/incoming calls failing(fast busy)...

When making an outbound call and doing a list trace tac

i am getting a denial even 1195: Circ/channel unavail D1=0x3c D2=0x18022c

problem is I can't seem to find any information on this specific denial event. 0x3c does not exist in the manual that I have. Any assistance would be appreciated. Until last friday it was working just fine.

s8300/G450/digital 2420 end points.

 

[gabber4858]

Do you get any system alarms or errors for that DS1? I would check the alarms and look for cleared alarms and errors for that day, also list meas ds1 XXXX. If the DS1 is taking errors, its probably a carrier issue. It could be a bad card, cable, CSU/DSU, etc, but the errors will dictate where to start. Dig into the errors and post back what you see.

 

[BIS]

Can't help you, but would be interested in the responses.

Recently one of our sites in France has been getting this issue on outbound calls as well.

denial event 1190: No circ/chan avail D1=0x8796 D2=0x722

There are plenty of channels available, so I am guessing it might be DS1 MM related or the provider is doing something that gives us glare (if that is even possible on PRI trunks). Problem is it is sporadic, a station experiencing this will work perfectly 2 minutes later...

 

[calhoony]

is this a PRI,,,is the signaling group in service,,,maybe the D channel/channels are down

 

[fluffheadsr]

it is a PRI, D-Channels are up

 

[kennyt3]

On the route pattern that you use for the calls try making the LAR field REHU, this may help you work around this issue.

 

[BIS]

could you explain why?

 

[kennyt3]

The REHU settings will allow the PBX to try the call again on the current routing preference for another trunk and try the call again. Most likely the provider is telling the PBX that the circuit/channel (b-channel) is unavailable for that call (that's why you get the Denial Event) possibly because they intend to use it for a different call. I've seen this issue before and by setting the REHU field on the route pattern it helped by immediately retrying the call on a different b-channel. HTH

 

[BIS]

Thanks! That makes sense, and I will try this and let you know the outcome.