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.
I am currently having a problem configuring AAA for management access to our wireless controllers.Our active directory structure is as below: (note all domains are part of the same forest and full trusts between the domains)Root DomainAmericas domain...
HI im running 6.1(2) with LDAP integrationipphone field in ad contains our international intercluster dialing digits844XXXXX for a uk user 801XXXXX for US etc.Global Directory xmldirectory.jsp has been modified to lookup ipphone field in ad directly ...
HI have a strange issue where the dependancy records on a CSS that i want to delete shows that a Device Profile is dependant on the CSS.I can confirm that neither the device profile or any of the lines have this CSS configured.I have logged out those...
Major issue is CSCug18734 ENH: Citrix Receiver proxy on ASA support for backend Storefront serverWhich Basically means it doesnt work with Xendesktop 7 since the only front-end for it is StoreFront.Come on Cisco Fix the Bug!
Do you need to use two physical inferfaces?my spoke has a private ip and sits behind a ASA. i just want to NAT a public ip directly to the private ip of the router, but im having problems getting the tunnel established.has anyone got some example con...
I have tried Directory Lookup dial rules but this only seems to be applicable to Attendant Console.How is everyone else using presence on the GAL with AD integration?
6.1(2) with Active directory ldap integration.yes this is happening for all users. the moment i change the ipphone field to match the dn configured on the DN then presence status works fine.i want to know if there is a way that you can configure some...
Take it you never got your answer about the username and password.the strange thing is that cisco develops a salesforce.com call connected that uses tsp to control the phone, but they dont provide a proper solution. having users update tsp usernames ...
