Hi Richard,
Sorry for the late reply. The backtraces show a really strange situation
- some processing context getting to NULL somewhere along the handling
of that 503 reply.
What I suspect is that you are using in failure route some functions
that are reseting this processing context -
Hi,
I've done some more testing and the carrier is now responding with a
shorter message, despite them saying nothing was wrong. and the crashing
isn't happening.
Therefore I'm unable to reproduce the original error on our live system.
I've put the node back into service and I'm monitoring
I've some more back traces.
this could be a resource problem. The back story is we want to check for
channel limits and Rate limits for all calls. Channel limit hits should
failover to the next gateway and rate limits should delat for up to 2
seconds before failing over to the next gateway.
