Yes, the call pattern on the outbound route to the IAX has 2xx as well as specifically 2200, I know I can use 2xxx, but there are potentially some 2XXX groups on the local pbx ( PBX1 ) but none conflicting of course.
They get an all circuits busy message when calling the ring group accross.
PBX2 doesn’t show the call attempt on the CDR.
Additionally the local caller Ext 100 (PBX1) does have access to the route.
When I tried to do some IAX debugging I did see this on the calling PBX (PBX1):
Confirm that the context is from-internal on the trunk at PBX2. It that’s correct (or fixing it doesn’t help), post the Asterisk log on PBX2 for the failing call.
It looks like the context=from-internal is making the difference.
The calls to extensions was working perfectly, but to ring groups was not.
(For reference context=default was what we were using before, this is in the inbound IAX configuration.)