Expressway Search Rule not working as expected

[Bill]

I am trying to configure Expressways to accept an inbound call from a remote party, and send to Call Manager.
But on the Exp-E, the call is not matching my Search Rule as I thought it would.
The Exp-E, it is matching the Default Zone, and rejecting the call.
Calls never make it to the Exp-C.

These are Expressways C and E (not VCS) setup for MRA and B2B, running X15.2
I am adding this new service for 9Line E911.

I have created all new Zones for this between Exp-C and E.
For the Exp-E, these are the Zone names, and where they are used.
Traversal Zone 9Line is between Exp-C <> Exp-E
Neighbor Zone 9Line is between Exp-E <> 9Line

My search rule seems pretty simple.
If a SIP call comes in on Neighbor Zone 9Line, send it to Traversal Zone 9Line.

The call is coming in on Neighbor Zone 9Line, but being sent to the Default Zone.
I do not know why.

I have attached a Word doc with some screenshots.

Thanks

[Roger Kallberg]

If I were to guess I would think that the inbound call is matching rule 30 before rule 140. Try lowering the priority on your rule from 140 to something lower than 30 and test again.

[Bill]

That was my first thought too, but rule 30 is disabled.

[Mark-9Line]

Hi Bill, Mark with 9Line here. We would be happy to help if you want to open a ticket with us.  I’ll be on the lookout for your case. 

Best,

-Mark

[Bill]

I will do that Mark.

Thank you