oozenoz

jitter itself is a measure of changes in signal characteristics (frequency, pulse duration, etc.) that you don't have all zeroes means there is some variance in the signal; but it does not mean that it's destroying the connection. if you can make a call from one side to the other (both directions) and can talk, then i wouldn't worry much about it because frame is not a perfect transmission protocol - and i certainly wouldn't think it's causing your issue with the coverage path not being followed.

it's been my experience that coverage not being followed is the result of a conflict of restrictions, where a certain type of call is not allowed to be routed to a coverage point, such as internal calls may be forwarded and external may not. i can't think of anything on a gateway interface that would cause this, and since you aren't using trunks and the extensions are of the same cor/cor, that's the only place i can think to look.

honestly, at this point i would suggest you contact your business partner and if necessary ask them to get avaya tier 3 involved.

__________________
- calvin