My upstream sends a "Account in Use 156" when the sessions are maxed out.
I would simply like to inform the user instead of the rewrite to NORMAL_CLEARING (480) which causes the user to false panic.
I have modified an existing outbound route with an extra group to handle the action as follows:
At log point 1, the Freeswitch log successfully writes "Hello .... Account in Use 156"
But on the condition point 2, there is no value attached to the variable resulting in a FAIL on match:
I have tried setting the second condition to have an Inline of True, and I have tried exporting a new variable in group 1 and checking that. The exported variable also has no value on condition check.
Could someone suggest how I could use these variables in post-call check to see if the call failed due to max sessions?
Thanks all!
I would simply like to inform the user instead of the rewrite to NORMAL_CLEARING (480) which causes the user to false panic.
I have modified an existing outbound route with an extra group to handle the action as follows:
At log point 1, the Freeswitch log successfully writes "Hello .... Account in Use 156"
But on the condition point 2, there is no value attached to the variable resulting in a FAIL on match:
I have tried setting the second condition to have an Inline of True, and I have tried exporting a new variable in group 1 and checking that. The exported variable also has no value on condition check.
Could someone suggest how I could use these variables in post-call check to see if the call failed due to max sessions?
Thanks all!