Cisco IOS 12.4(15)T – A warning for all
A short while ago I discussed the merits of Cisco’s CallManager Express 4.0 software, over their previous 3.3 release which I had been using. It really was a big improvement, but alas there was still some functionality missing that I really required (namely the ‘blf-speed-dial’ command.)
So the hunt began, and seemingly not long before we’d started looking, Cisco had released IOS version 12.4(15)T, which indeed comes with CME 4.1 bundled in the appropriate voice-related featuresets. I chose this release, as the only alternative was an earlier X release. And I’m still quite un-sure of X releases, as it happens.
Now for the severe warning:
Do NOT attempt to register an Snom 360 SIP phone to the SIP registar with this release. We’ve tested a few non-Cisco SIP phones so far, all with varying degrees of success (the Grandstream GXP2000 worked well, though it’s far from usuable*), but the Snom actually caused the router to crash and reboot each time it attempted to register.
Strange but true – a SIP phone registering caused the router (a 2811) to bomb-out and restart at least six times before I realised what was going on. I guess there’s one reason why the more experienced Cisco geeks shy well away from T-train releases…
To make matters worse, I’ve found another strange, yet seemingly harmless bug with this new image. Whenever a call is made, and it doesn’t matter where it’s orginated or destined for; as soon as the call is answered the CLID is suffixed with seemingly random crap. Due to the fact that most of it is garbage, with the rest resembling bits of caller IDs from previous calls, I’d hazard a guess that this is some sort of memory over/underflow issue (but I’m no experienced programmer, so feel free to correct me.)
I’m also not sure whether it’s the IOS release, or CME 4.1 which is causing the problem. I’ve not had the 12.4(11)XJ3 release to test it with, and I’m more-likely to push fowards instead of backwards as there’s since been a newer IOS released with CME 4.2 and I’m hoping it will solve the problem. The only problem is, it’s another X release. 
What I do know though, is that changing the 7960 firmware load makes no difference what-so-ever. I’ve tested 8.0(5.0) (which happens to be the recommended version for use with CME 4.1), 8.0(6.0) and even 8.0(4.0) with no change in behaviour. The only thing I can attest to is that the Grandstream SIP phone I’m using for testing purposes doesn’t exhibit the same problem. That’s one yay for SIP, at least. 
If anyone out there is experiencing the same problem, then please let me know any possible solutions that I could test! 
*The Grandstream can currently dial extensions registered to both CME, and our Asterisk gateway but as for calling externally – I merely receive a 403 error. Maybe I need to keep playing with it, but I don’t think Cisco’s implementation of SIP still particularly favourable…
Hi tom,
i also work HARD with CME 4.1 and currently i’m testing SIP features.
i’ve tested grandstream HT, GXP2000 and Thomson ST2030 basic calls with success.
i don’t know about your CLID problem but you will hard debug the trouble
.
I’ve also some strange problem with 12.4(11)XJ3 release, everyday the router reboot. really strange
but maybe the problem is caused by my particular configuration i’ve done
CME+IP-to-IP+TCL B-ACD with g711/g729 transcoding.
lot of feature with third party SIP phones are not working, like parking, Music On Hold, FAC and more.
I’ve a question for you maybe you know how to monitor a SIP phone from a skinny IP phone,with monitor i mean for example the “m” flag of button command with ephone. Is it possibile to monitor a SIP dn from a skinny ip phone? maybe with blf-speed-dial but it’s not totally clear to me how it works. Ok if i use “allow watch” command on a “voice register dn” how can i monitor this phone from a skinny ip phone button?
sometimes… cisco sux
bye
Hi tele, thanks for your comments – very much appreciated! It’s good to know someone else is having fun too
It is also good to know you haven’t had the CLID issue with 12.4(11)XJ3! Hopefuly the 12.4(11)XW2 release (CME 4.2) will fix this too.
Have you been able to make a non-Cisco SIP phone follow your voice dial-peers? I have a dial-peer with the destination-pattern .T, and the Grandstream will not use it. I just get ’403: Not implemented’
dial-peer voice 2 voip
translation-profile outgoing fakePSTN
destination-pattern .T
redirect ip2ip
session protocol sipv2
session target ipv4:xxx.xxx.xxx.xxx
session transport udp
dtmf-relay rtp-nte
codec g711ulaw
How is your SIP dialing implemented?
To answer your question on monitoring phones, I was only able to monitor with blf-speed-dials, but I can monitor SIP (Mitel, Grandstream etc.) from a SCCP Cisco 7960 just fine. Here’s some config that might help:
!
presence
presence call-list
max-subscription 144
!
sip-ua
presence enable
!
And of course make sure you allow all phones to be watched – I used a template for the ephones.
Hope it helps!
Hi! yes outgoing dialing works great, i’m using 9number for outgoing calls from my extensions.
voice translation-rule 2
rule 1 /^9/ //
!
voice translation-profile TO-PSTN
translate called 2
!
dial-peer voice 10 voip
translation-profile outgoing TO-PSTN
destination-pattern 9.T
voice-class codec 1
session protocol sipv2
session target sip-server
clid network-number 010449051
outgoing works without problem, you should activate some “debug ccsip all” for see what happen.
activate also “debug voice dialpeer” look if the correct outgoing dialpeer is matched.
Are you reciving the 403 Not Implemented from the Cisco? hmm 403 should be “Forbidden” the 501 is “Not Implemented”.
If you want send to me the trace and i’ll look with you to find a solution.
About the monitor line yes, i’ve already activated the presence stuff. now what is not clear to me is how to monitor a line, for give you an example:
52 ext (Non-Cisco SIP phone)
100 ext (SCCP 7960 Phone with 6 line)
i want to monitor ext 52 from the second button of the 7960. how can i do it?
thank you very much!
i was glad to find your blog about the CCME and other networking/sysadmin stuff
Hi Tele!
When I am back in the office, I will have another look at my voice config. I believe I can reach some dial-peers, but not others. I will need to run some SIP debug, and also checkout the messages from the Asterisk gateway.
(I know the error was 403, but I used to get 501 .. So it is ‘Forbidden’.)
Monitor lines:
!
ephone 1
mac-address 1234.5678.9ABC
description Cisco 7960
blf-speed-dial 1 52 label “Non-Cisco SIP phone”
!
Restart the ephone and it should work – if you want to space the speed dials away from your lines, you can start your numbering at ’2′ for the blf-speed-dial identifier, and it will leave a line blank.
I’m very glad you are finding it helpful! I can only hope that more people find some help here too
Yes this is what i did for monitor lines i’ve read in the documentation that blf-speed-dial use the first button unused.
I was blocked by the fact that when i restart the IP phone there is no new entry on the display.
this the debug when the phone boot up:
Jul 26 07:01:07.723: %IPPHONE-6-REG_ALARM: 25: Name=SEP001B535C960A Load=7.2(T0.23) Last=Inizialized
Jul 26 07:01:07.723: %IPPHONE-6-REGISTER: ephone-3:SEP001B535C960A IP:192.168.1.110 Socket:1 DeviceType:Phone has registered.
Jul 26 07:01:07.779: ephone-3[1][SEP001B535C960A]:skinny_unsubscribe_blf
Jul 26 07:01:07.783: ephone-3[1][SEP001B535C960A]:BLF speed dial buttons starts [4]
Jul 26 07:01:07.783: ephone-3[1][SEP001B535C960A]:BLF speed dial buttons index [1]
hmmm maybe the problem is the firmware of the IP phone? i’m using version 7.2.
I’ll work on it. bye
Yes was a firmware problem, now it works!
hope talk to you soon tom, thanks for help.
if you want i can leave to you my MSN or jabber ID so we can remain in contact.
bye
Yep! Cisco recommend that a 7960 use firmware release 8.0(5.0) for CME 4.1. I’ve tested 8.0(4.0) and 8.0(6.0) as well and they all work fine (with BLF support too). 8.0(6.0) is good for CME 4.2 as well!
Yes, MSN would be beneficial I think. E-mail me your MSN address on tom #at# ninjabadger #dot# net, and I’ll add you!