Hi, thank you for all your answer, they were all very helpfull. I didn't know you could set caller input inside a user's extension. It is now working. I have, as you suggested set up an operator handler for each site and updated users to be redirected according the site they are in. ... View more

Hi, I had the same issue. I found this in the CLi guide. It was very frustrating for me also. Example Changes the Smartport type from unknown to default and resumes the Smartport feature on port 1. switchxxxxxx(config)interface gi1/1/1 switchxxxxxx(conf-if)#macro auto resume ... View more

You should ckeck this bug, if in the directory users do not have their extension as their telephone number (if you use E.164,etc) , BLF won't work. No work around. CSCtd74932 Bug Details Enhancement: BLF and E.164 directory numbers. Symptom: In order for BLF to be displayed we need  to match EXACTLY the DN as configured in the DN admin pages of callmanager and  the telephone number as imported from the Active directory Currently  there is no possibility to partially match telephone number that is configured  for example in E.164 format This is a problem because most organizations  have the E.164 number configured in AD, which is imported to callmanager and  attendant console but the DN in callmanager is configured as 4 or 5  digits The BLF will not work this  way Conditions: When AD has the full E.164 number  configured and the DN configured in callmanager is a partial match of the E.164  number Workaround: No known workaround http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtd74932 ... View more

I must add that in my experience we have seen that a ContactQueueDetail record is not added to the DB util the call has ended, this is an issue for real time reporting. We have found no way of pulling data of the DB to see in what CSQ an agent is answering the call (we can't know until he hangs up) =( ... View more