Search results for query: *

I have given up trying to understand the issue...I was able to get all my users moved to an alternate ASA with no problems, then suddenly a single user started experiencing the same issue on the alternate ASA and had to be moved back. I still believe this is Comcast but I've had no luck working...

Nurban, glad to hear this is working for you, unfortunately not the case here. After upgrading our second ASA to 8.2.X the problem still exists so it seems like it's the path rather than the ASA code. So we are going to move all VPN phones to second ASA, but I'll keep pushing Comcast (though I...

OK, after several hours no the phone with Cisco and Comcast I have a little more insight into our problem. We are experiencing the issue on one of two ASA's, the difference between them being geography and code version (problem ASA running 8.0 code working ASA 8.2 code). We verified that port...

Thanks Nurban! Regarding your post about protocol 50 issue, did you have ticket open with them? I can't seem to get past level 1, they won't escalate since they don't understand the problem. Maybe if there was an old ticket I could reference it might help convince them I'm not crazy...

We are experiencing the exact same issue with Comcast users as of last Thursday am. Was anyone able to resolve the issue or did comcast finally push a change? Any help would be appreciated!

I recreated the subnet and placed my current settings file on a tftp server which did allow the phones to pick up the new Call Server IP and I can register them with the IP office. I enabled the setting 'SET PROCSTAT 0' in the settings file but still the '* to program' does not appear and I'm...

Thanks for the replies, I was afraid of that. Unfortunately the edit button only let's me change the VPN settings not the callsv or filesv IP's. I will try and get a tftp server setup with the old file server IP and a new settings file, hopefully that will do the trick. Thanks again.

After moving our IP office to a new IP/location I am unable to modify the configuration of several 5610 VPN phones to point to the new IP office IP address. The '* to program' does not display and the 'mute 25327' or 'mute 73738' do not work. This likely was caused by a temporary change in the...