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.
Hi there, I am experiencing a problem with call forwarding. When person A is called and he has configured forwarding to person B, and the person B does not answer, the call is then forwarded to the reception in a different city. I have no clue where ...
Hi there,I am having a simple WAAS deployment with central site and remote site connected via 2mb LL. For redirection I'm using wccp on a separate VLAN on LL routers.I can see plenty of statistics regarding optimization of various kind of traffic, eg...
Hi there,Recently I have deployed WAAS for just one site, and I am a bit concerned as majority of the traffic falls into "Other Traffic" category. I've discovered this is just a file transfer between XP desktops and a W2003 server. Why it's categoriz...
Hi there,I am having a strange problem with Attendant Console, when a receptionist is trying to forward a call, one of the names starting from M appears between, let's say S (it is not sorted correctly).Any ideas why?Thanks
It is set to Forward Busy & No Answer to Voicemail. Forward All is cleared.We're using CCM4.0, and the problem seems to be global, all phones are affected.When you call directly PersonB and he doesn't answer - the call is forwarded to VoiceMail Port....
I've upgraded to 4.0.10 and it started working today! That's good, thanks for your help. BTW I've got enterprise licenses anyway. It could be that starting from certain release WAFS won't be working on transport licenses...
I've just had a chat with Cisco PreSales guy, he said that for a moment they don't distinguish between licenses.With regards to configs, I think I've setup everything correctly as the guide says, otherwise won't be asking :))thanks for your help anyw...
Thanks for your input.We are running ver. 4.0.7, a standard w2003 server and xp workstations.I can see plenty of cifs connections, the source IP is in the remote site, but the destination is the actual server in central site, not the core wafs device...
