search for: enaged

..."Busy here" back from 123.123.123.123 -- SIP/sip-outbound-af71 is busy == Everyone is busy/congested at this time This is what we want as it then send the call to priority n+101 and we can handle it any way we want from there. However if the outbound call is made via the PRI to an enaged number it simply plays an enaged signal to the caller and never progresses to priority n+101. Anyone have any suggestions?

...here" back from 123.123.123.123 -- SIP/sip-outbound-af71 is busy == Everyone is busy/congested at this time This is what we want as it then send the call to priority n+101 and we can handle it any way we want from there. However if the outbound call is made via the PRI (Zap channel) to an enaged number it simply plays an enaged signal to the caller and never progresses to priority n+101. Anyone have any suggestions?

...here" back from 123.123.123.123 -- SIP/sip-outbound-af71 is busy == Everyone is busy/congested at this time This is what we want as it then send the call to priority n+101 and we can handle it any way we want from there. However if the outbound call is made via the PRI (Zap channel) to an enaged number it simply plays an enaged signal to the caller and never progresses past the Dial priority. I know for a fact the call is not actually being answered, because I get the following onthe console. Executing Dial("SIP/1001-270b", "Zap/g1/123456789") in new stack -- Calle...