Cisco CUCM 5 and 6 bug

The latest bug to hit my inbox is that apparently when CUCM 5 and 6 hits 248 days of uptime, it can crash horribly. Cisco's advice is to reboot the CUCM servers before they hit the 248 day uptime counter. Resetting them effectively resets the counter.

Very very worrying.

Cisco Presence

It's been a while since we tackled Presence due to the instability of older clients and the CUPS server behind it. However now we're starting to see that the client especially, has come a long way.

I've always believed that CUPC is the pinnacle of how Unified Communications (from a Cisco point of view at least) should work, and just so happens to be the tool of choice to sell other Cisco products into a customer's network because of it's ability to tie everything together.

Below is a brilliant video of how it works.

Cisco Unified Personal Communicator Video Data Sheet @ Yahoo!7 Video

caller-id enable

Hi all,

Just an interesting case that came up very recently where a customer had 'caller-id enable' on all of their FXS ports on a VG224. The result was that calls to analog phones on the VG224 would not answer correctly if you picked up the phone during the first two phones. This is because the gateway is incorrectly configured to send caller-id signal in the analog stream. Turn it off to alleviate the symptom.

How to channelise PRI circuits with MGCP

MGCP doesn't properly support channelised E1 or T1 circuits, in that you can only specify circuits that have the full 30 or 23 channels respectively, rather than an E1 that only has 8 channels from the TELCO.

You can use the following guide from Cisco to get channelised PRI to work in CallManager, simply by creating a full T1 or E1 with the full amount of channels, and then use the guide to busy out the channels that aren't required/available from the TELCO. You can also use the same feature to disable individual channels when troubleshooting:

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_configuration_example09186a008076f8d2.shtml

iPhone vs HTC Touch Diamond

Hey all.

I felt compelled to write about this as I am now the (proud) owner of both phones - as work saw fit to give me a work phone!

I felt quite angered at some of the reviews i'd seen of certain presenters views on these devices, because it mainly comes down to what people think of them on first impressions. I feel it's very wrong of the presenters to review a phone in this way! Asking most people in the street about which device to go for, they'll pick the iPhone 95% of the time because it looks swish. Just because it's a nice interface and the buttons wobble in a funny way when you hold your pinky on it, does not a great phone make.

I would even go as far to say that they're pretty biased in favour of the iPhone. It may be a pretty off-the-cuff thing to say but if you think about it, loads of businesses will now go for the iPhone as a business tool based on what the media has said about it (Plus it now 'does' Activesync), and when it gets filtered down to techies like me, we'll be bitterly disappointed...

So here's some views/criticisms from a technical perspective:

• Google Maps on the iPhone is great, but I have full blown TomTom on my HTC Touch Diamond and it works brilliantly. People keep wanting to go on about how great a free app is on the iPhone when the Diamond has had it for ages too, and has an uncomplicated method for installing better apps for the job.


• Everything costs money on the iPhone. I went out and got Mobile Putty, a command line program, and some ping/test tools for the Diamond for free. Most important of all I got RDP for the Diamond for free too. All of the above for the iPhone costs cash.


• The iPhone hides all the important settings. For instance I want to change the behaviour of the auto-lock feature when on battery compared to when on charge? Nada. I could have fettled with this stuff on the Diamond to my heart's content.


• The iPhone is massive. Why on Earth does it have to be so big?


• I don't think I can tether my iPhone to my laptop and use it as a modem - if I can it'll probably cost cash again. With the Diamond I simply plug it into the laptop, start ICS on the phone and woohoo I have HSDPA internet without running anything more than Activesync.


• I can take the battery off my Diamond when it cocks up. The iPhone has locked up more times than my Diamond has.


• I can't write my own apps for the iPhone easily.


• No integration on the iPhone with OneNote.


• The signal strength on the iPhone is simply awful. We're sending the Sales team out with these phones and all they do is complain that while the phone has lots of whizz-bang features, you can't actually make a phone call.
  

So there you go, a techie-biased view of the iPhone's faults.

Buy a diamond instead.

CallManager 7 revs up

News has just hit my inbox that the SRND for CallManager 7 is now available:

CallManager 7 SRND

If you're lucky enough to have Partner E-Learning, there's 35 hours of free video training on it :)

If only I had that much time...

proji.co.uk

Cock a doodle doo! My good friend's site www.proji.co.uk has now gone live and unleashed to the world! Expect some great posts on technology and commentary/reviews on everything you should know about when it comes to gadgets, software, hardware and other cool stuff.

The link on the right also takes you there. Peace be the journey.

Yet more issues with CallManager 6.0

Yet another bug with Cisco CallManager 6.0. Sigh. This was identified in version UCOS_ES_6.0.1.3103-1.

We found similarly to a previous post that when we tried to dial out, we got the following debug with "Bearer/channel not available". However we found in that this instance, changing the CLID made no difference, we verified that the customer had specified the correct number of B channels on their PRI, and attempts to use commands such as "bchan-order ascending" made no difference.

*Jan 26 09:01:29.606: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Calling num 01234115200*Jan 26 09:01:29.610: ISDN Se0/0/0:15 Q931: Applying typeplan for sw-type 0x12 is 0x0 0x0, Called num 07989163892*Jan 26 09:01:29.610: ISDN Se0/0/0:15 Q931: TX -> SETUP pd = 8 callref = 0x0117 Bearer Capability i = 0x8090A3 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA98399 Exclusive, Channel 25 Progress Ind i = 0x8183 - Origination address is non-ISDN Calling Party Number i = 0x0081, '01234115200' Plan:Unknown, Type:Unknown Called Party Number i = 0x80, '07989163892' Plan:Unknown, Type:Unknown*Jan 26 09:01:29.822: ISDN Se0/0/0:15 Q931: RX <- CALL_PROC pd = 8 callref = 0x8117 Channel ID i = 0xA98399 Exclusive, Channel 25 Notification Ind i = 0xE8*Jan 26 09:01:33.614: ISDN Se0/0/0:15 Q931: RX <- ALERTING pd = 8 callref = 0x8117*Jan 26 09:01:33.654: ISDN Se0/0/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x0117 Cause i = 0x80AC - Requested circuit/channel not available*Jan 26 09:01:33.830: ISDN Se0/0/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x8117*Jan 26 09:01:33.834: ISDN Se0/0/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x0117

As it turned out, we were using 7945 and 7965 phones (Which id never seen before, though are worth the money over a 7961 etc!). Turning off G.722 Wideband codec on the phone fixed the problem! You may wish to think about changing the Enterprise parameter and resetting all phones if you aren't going to use this codec in your enterprise.

First impressions of the new HTC Diamond

Yes ladies and gentlemen, I have yet again upgraded early due to my irrational attraction to shiny things.

I'll try to keep this brief as I have a steak under the grill (And you can find stuff like this all over the web):

• This device is sexy! In fact it's the first HTC device that I really think will attract the consumer rather than the businessman. It's feature-packed, easy to use, has a much better camera (though still no flash), and it doesn't cost iPhone prices...
• The built in GPS is somewhat fiddly to get going with TomTom but is a great addition
• The device attracts scratches - you'll find it difficult to sell this on Ebay "scratch free" after you've owned it for a while. Bear that in mind!
• The battery life is terrible (I think i've got a phone from a bad batch) and has lasted as little as a day with light useage. Some are suggesting that this is down to the ROM being used and it may be updated soon if enough people complain about it.
• Internet Connection Sharing works brilliantly with Vista, and allowed me to get up to great speeds on my laptop using the phone as a modem.

More issues with CallManager 6.0

I recently rolled out CallManager 6.0 for a customer and rather disappointingly we ended up having to apply an Engineering Special patch to fix the problems. Rather alarmingly, we found these bugs in version 6.0.1.3000-7:

• Attendant Console is unable to allow you to select a Device Profile (Unable to change MAC address) however Attendant Console works fine when you choose to use a phone that is statically configured rather than using Extension Mobility.
• Adding a new Device Profile to CallManager causes ccm.exe (or the Linux equivalant at least) to hang. Symptoms include CFWD state unchangeable, and attempting to log in/out of Extension Mobility causes the phone to endlessly say 'registering'.
• Device profile Service URL is being overwritten by the actual devices' SURL. The symptom presents itself as the service URL that was being shown on the phone when the phone is EM logged out can still be seen when the phone has been logged into EM.

What's disappointing is that all three of these bugs were fixed in previous versions of CallManager 6, and somehow Cisco has allowed these bugs to get through to a later version. Does it have something to say about their Quality Control procedures???

Anyway. These bugs are all fixed in ES UCOS_ES_6.0.1.3103-1 or CallManager 6.1. Speak to Cisco TAC for further assistance.