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.
Out of curiosity, is there an easier way of keeping Firepower updated on application needs when ports change? That or even the initial opening of ports? For example: I will be soon migrating my phone service to Webex Calling from on-prem. The port...
We are in the process of changing from using on-prem CUCM to Webex Calling. My webex client was logged into the CUCM, but that server has been deprovisioned. The dang client app refuses to allow me to log out of using CUCM and log into webex callin...
This has got to be something silly I did. I recently had a bunch of work done by a third party to update our calling structure. Somewhere along the way, when making outgoing calls, there is an extra 1 tacked onto the number. For example:My desk ph...
This is a new one on me. We just finished updating our dialing plans and everything and ever since there are some cell phone numbers that if I call from my VoIP phone to the cell phone, it goes directly to their voicemail. If I call the same number...
I am running a full switching network. My cores are all 9504 and my access layers are all 9200 and 9300s. I have approx 50 vlans. All vlans can see and ping each other and there is nothing filtering traffic. Every guide I can find is from way bac...
I had to go into my 9200 and specify the following (lines 16-31 were unused for me at the time). Once I specifically set that group it started working like a charm and the vty error disappeared.line vty 16 31access-class MERAKI_VTY_IN inaccess-class...
I finally found it. Someone unchecked the "Use external mask" checkbox in the routing pattern. Amazing that something so little could cause so much heartache.
This is under route groups, route group members, trunk configuration.I understand there are lots of places. That is what is frustrating me most I think. So many places to look and I get lost in the sea of areas and sub areas and linked areas.
DNA shows the correct digits being sent. Both called and calling transformations are blank. Everything is the default in the route list and groups. I did just see in the sip trunk config there is a prefix of +1. Could that be it?
I had a whole answer typed up and forgot to actually post it. I didn't realize that I could go past the version that matched up with my version of call manager. I went ahead and upgraded PCD to the latest 12.6.1 and I'll see if it helps the next tim...
