Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
This document should help, but I think your issue is that the @ wildcard is the closest match, so your call is hitting that route pattern. That's why when you change 0.0044! to 2.0044! it works.http://www.cisco.com/en/US/partner/products/sw/voicesw/p...
Have you tried deleting and recreating the FXO ports in CallManager on the gateway configuration page, etc? If so, its possible you have a bad FXO card. I ran into almost the exam same issue at a customers site and it was a bad FXO card (confirmed by...
