Session Agent Taken out of service
Hi
What reason would the SBC take a session agent oos? I have one SA OOS- when i disabled it saved activated - and then changed the state back to enabled saved activated it came back in service- this is the second time i have seen this with 2 different session agents- what would cause this? Is there maybe a limitation on the amount of session agents?
Thanks