Hi In terms of accessing the VM, just press the messages key on the handset, press *, then enter the voicemail mailbox number and pin. Barry Hesk Sent from Cisco Technical Support Android App ... View more

Hi Andrew I have a very similar issue once. Not sure if its the same as you, but in the end in turned out to be a bad NAT config on the ASA. I'd created a static NAT for an internal subnet that was doing overload NAT to the outside interface of the ASA.Of course this should have been a dynamic NAT rather than a static. My symptoms were exactly the same as yours. As soon as I corrected my NAT config, everything worked properly. HTH Barry Hesk Intrinsic Network Solutions ... View more

Port g2/0/20 is receiving a BDPU inbound that was issued by itself (i.e the ISP switch stack) on another of its ports (i.e. there is a loop / redundant path). This is pretty much the only reason that a port will go into BLK state. IMHO it would be a very bad idea to disable STP on that VLAN. If there is indeed a loop, as soon as you do this, everything will go down the toilet. I presume the ASAs are in routed (L3) mode, and not transparent (L2) mode? If they are transparent, then this changes this conversation somewhat.... In L2 mode, whilst ASAs don't generate BPDUs, they do forward them between interfaces. However, I'm pretty sure a standby ASA won't forward them, although from memory there were some bugs in this area in early releases of 8.2. In L3 mode, the ASA will just discard BPDUs, and can't create a L2 loop. Barry Hesk Intrinsic Network Solutions ... View more

And just as another thought... here's a left field guess. I reckon your old circuits were layer 2 tails (in the same VLAN) that terminate in your ISPs data centre, again on the same VLAN. This means that all devices in the same VLAN can always communicate with each other. I reckon your new circuits are layer 3 tails, and only one will be routed over at any given time (the current active circuit). This would explain why the "standby" ASA - whichever one it is - always shows its outside card as failed. Would explain the exact problem you are seeing. As I say, bit left field, but I reckon there is logic there... Barry Hesk Intrinsic Network Solutions ... View more

Hi Where I've seen ASA interfaces, particularly outside ones, showing as "failed" is where they can't actually communicate with each other. I'm not sure if its ICMP that is required between then, but I've certainly seen similar issues where the two ASA outside cards can't ping between each other. If you run a ping from ASA "B" to the outside address of ASA "A" does it work? I suspect not, and this is the route cause of your issue. If this is the case, then you'll need to get your ISP involved. HTH Barry Hesk Intrinsic Network Solutions ... View more

Hi Syed Sort of an update - Jabber for Android just doesn't work very well. It is a little bit embarassing having to explain this to my customers, but nobody at Cisco seems to be listening. It doesn't work on HTC-one for definite. There is a list of supported handsets on the Release Notes, but it is pretty poor. Most of the time "not supported" means it will probably work, but is not supported by Cisco. I can live with that. However with JFA, "not supported" means it doesn't actually work. The solution is very simple.  1. Deinstall Jabber for Android. 2. Install CSIPSimple. Works great. I went through a stage of testing new Jabber for Andoid releases to see if Cisco had fixed it, but have given up now. CSIPSimple does everything I need. Barry Hesk Intrinsic Network Solutions ... View more

Hi Tracee Pretty much correct. Up to version 9.x, everything under the covers was actually DLUs. Even if you ordered UCL or CUWL licenses, DLUs got shipped. This caused lots of confusion. As of version 9.x, everything is user based. End users within CUCM do NOT consume a license, only phones. In CUCM terms, a user, by and large is just a phone (which is allocated, or "owned" by a user) In CUC terms, a user is a mailbox. And as a slightly (but only slightly) tongue in cheek answer to your original question, no, nobody understands Cisco licensing for UC products. Not even Cisco themselves. I can state this categorically as I've just sat in on a conference call where Cisco attempted to explain the new ordering process for UCSS and it was very clear that they didn't understand how it all works either. Barry Hesk Intrinsic Network Solutions ... View more

Hi Carlos No, MeetMe under CME (or under CUCM) doesn't have any timer. When the Meetme call drops, is it for both internal and external callers, or just for external? I have seen an issue on SIP trunks where the call is torn down after 60 minutes due to reinvite timers. For internal callers MeetMe stayed up, however the external calls got torn down. HTH. Barry Hesk Intrinsic Network Solutions ... View more

Just found this http://sourceforge.net/projects/cipinventory/?source=dlp HTH Barry Hesk Intrinsic Network Solutions ... View more

No it won't. CUCM has no knowledge of a phone serial number. There are some 3rd party apps that do allow you to do this (UnifiedFX from memory is one). I also have a perl script that will do this for you. It's ugly but it works (at least it did last time I tested it). The perl script looks like: #!/usr/bin/perl $argument1 = $ARGV[0]; use LWP::Simple; $website_content = get($argument1); open LOGFILE, ">log.file"; print  LOGFILE $website_content; close LOGFILE; This connects to the web server on the phone, captures the home page, and writes to a file called "log.file". The IP address of the phone is passed to the script. The home page served by the phone contains the serial number. I then have a wrapper which calls the perl script, which I have written in a language called REXX - simply because my Perl is appalling. /* */ perl_exe="c:\strawberry\perl\bin\perl.exe" perl_file="c:\strawberry\perl\bin\web.pl" file_name="c:\strawberry\perl\bin\log.file" do i = 12 to 41   target="10.150.108."||i   ping target "-w 1000 -n 3 > DUMMY"   if rc=0 then do      webtarget="http://"||target      perl_exe perl_file webtarget      do while lines(file_name) > 0         s=""         junk = linein(file_name)         s=s||junk      end      parse var junk . "Serial Number" rest      parse var rest . "" Serial_Number "" rest      say Serial_Number      rc = stream(file_name, "c", "close")   end   else do   end end fs So the attached scans IP Addresses 10.150.108.12 -> 41. It pings them first, and if they respond calls the Perl stub to capture the web page. The REXX wrapper then goes through the file, and looks for the starting "Serial Number" and extracts it. As I say, ugly, but it works. HTH Barry Hesk Intrinsic Network Solutions ... View more

Tony Ensure you have multicasting enabled on the WLC. by default, a lot of Apple related stuff doesn't work due to their (IMHO horrible) use of multicast with the (equally horrible) Bonjour protocol. Apple TV is another example of an application that doesn't work without enabling multicast support on the controller. http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_tech_note09186a0080bb1d7c.shtml Barry Hesk Intrinsic Network Solutions ... View more