SLMC24 Card

[thepfy]

Hello,

Does anyone know anything about SLMC24 Cards?
I believe they are the replacement for SLC24 cards but I don't know what the difference is.
We were supposed to have one fitted today but Unify wasn't sure about whether the configuration was the same as the SLC24
(We asked for an additional SLC24 but they have provided a SLMC24).

 

[sbcsu]

There is an SLMAC24 - 24 way Analog extension card ?
SLC24 is DECT as you know

 

[thepfy]

Hi SBCSU,

It's definitely a SLMC24 and it is a DECT card bur neither the Telent engineer fitting it or the remote engineer knew anything about it.
Remote (Unify) wanted to check up as they hadn't dealt with one before.
The front GPS ports are in a slightly different position than the SLC24 and come as uncovered RJ45.

I cannot see anything on the Unify site or via the customer portal but I don't have the engineers access to firmware etc on the Unify site.

 

[sbcsu]

What is the Part Number written on it ?
Is it visible when you DIS-BCSU; ?

 

[Moriendi]

It's the replacement for SLC24. SLC24 is now end of life. Differences to SLC24 are that BS3 are not supported (they are old base stations, not delivered for a long time), and it contains on board hardware to assist with ISS, where you sync to another 4K node for seamless handover. It's released from V7 R2/V8 R0 and is a straight swap for SLC24, i.e if an SLC24 fails, SLMC can be used to replace.

 

[thepfy]

Thanks,

The Card is S30810-Q2344-X

 

[GZgidnick]

I just finished implementing new SLMC CMI DECT for a customer.
I had massive issues building the system. Would not activate more than 2 cards.
The only way to build it was.... build the DECT first and than add the SLMC's one by one.

Now, the only difference I can spot between SLC and SLMC is the built in GPS I/O modules.
From configuration perspective it is all the same as with SLC. You obviously now need select different board type.
That's it.

When swapping SLC for SLMC in CAT Tool you have to change the board type or do it manually in AMO:
CHANGE-BCSU:TYPE=PARTNO,LTG=1,LTU=3,SLOT=11,PARTNO2="Q2344-X";
CHANGE-ZAND:TYPE=LOADWARE,LWTYPE="SLCU",LWVAR=4;

DECT IP is so much better then CMI, there is simply no comparison there.

 

[thepfy]

There are advantages for DECT over wireless.
In case of Wireless / Computer Network outages, the DECT phones will still work
The base stations are powered by the card, so if there is a power outage in an area the base stations and DECT phones will still work.

That's why we use them in a hospital.

The area covered by a single Base Station is larger than WiFi will cover as well.

 

[sbcsu]

I also prefer the DECT due to the HiPath Feature integration (the menu on the phone) rather than a SIP integration on a WiFi phone.
Further the call quality to my ears is better/clearer.
In a hospital environment you are in control of the DECT card but more often than not there is someone else in control of the wireless access points.

 

[Moriendi]

Users with 4K DECT generally give excellent feedback. I know a user that trialled 4K DECT, then cancelled their 3rd party DECT installation which had been in the pipeline before they went to 4K and switched to 4K CMI. They were impressed with it and rightly so. HFA features on a rock solid cordless handset. What's not to like? You're not relying on LAN or WIFI for anything, it hardly ever goes wrong, it just sits there and works. I've not heard of any problems with SLMC like can't activate more than two cards, but if that error is there you can be sure they'll fix it because development support on 4K is excellent. SLMC is a brand new card, sure there may be a bug or two, but it'll get fixed.

 

[GZgidnick]

I thing you are confusing Wifi with DECT IP. Entirely different worlds.
DECT IP integrates with the 4K using SIP, natively not via trunk.
All DECT subscribers on the 4K are configured as UFIP rather than the old CMI. That't about the differences.
The Base Stations are again, DECT. Not WIFI. The Cordless phones are again DECT and not WIFI. They connect to the DECT Base Stations same as with the old CMI.

I've heard that comment re network outages many times from tech and customers alike. I think this is more generation thing than technical thing. Mature engineers already have established trust bond with mature and proven systems. In their eyes, tried and proven is much better then taking risk with new systems and technologies alike.

If DECT is considered to be crucial system such as in Hospital, why not powering the switches running the DECT BS & DECT IP Server/s from the same power supply used to power your 4K? Then if your DECT goes down, the 4K goes down and vice versa . You can't run CMI DECT without 4K can you? - Same applies here.

DECT IP scales so much more than CMI DECT and makes it so much more elegantly. Cost effectiveness being just another of its virtues.

 

[Moriendi]

I wouldn't say "All DECT subscribers on the 4K are configured as UFIP rather than the old CMI. That't about the differences."

To use DECT IP your data network must meet all VOIP requirements, and not everybody's does (although they'll tell you it does). Sure you've got DECT to the base station, but then you're using VOIP on customer network to get that base station talking to the 4K. And that's a huge difference. You've now got two things to manage instead of one. User has a poor quality call? Data team say "PABX issue. Nothing wrong with the LAN!" etc etc. OSV has to implement DECT this way, 4K can also do it this way, but 4K can also provide TDM all the way back to 4K - rock solid. Only needs 1 pair to bring a base station in service. Add one or two more pairs for more capacity.

Cordless IP will meet some scenarios where LAN is already deployed, easier to just hop on the LAN rather than install new line & plant for sure. But if you don't want the hassle of VOIP muddying your DECT waters, stick with SLCs.

I cannot agree at all with your comment about scalability. It's more elegant? No chance. With DECT IP you need to know where you're going before you start. You have three options, small, server, or large system. Small system only supports 10 BS and 10 phone calls, with ~50? logged on phones. So move up to server based system. Now you've got a linux server in the mix (hope it doesn't crash), with up to 50 BS and 50 calls. Need more? Large system. 3000 BS max, but now you need a management server and up to 100 media servers. That's right, up to 100 media servers. Wow, what just happened? Should have gone pure DECT on 4K SLCs is what just happened.

4K scalability is much easier, Install 1 SLC, you get 24 BS ports, up to 16 individual BS, and ~120 handsets. Need more? Add another SLC. Need more? Add another SLC. Need more? Add another SLC. Oh God I'm bored, it's too easy, up to 48 SLC's per 4K, over 3000 handsets per 4K. It should be enough for anyone but if it's not, add another 4K, certainly won't take as much room as your media server marathon and 4K offers seamless handover between nodes with ISS. There are some monster 4K DECT installations across Europe, I would be very surprised if DECT IP had anything similarly sized. It may get there, but I'd feel sorry for anyone filling their comms room with media servers when they could have had it all internal on 4K SLC cards. Nice and easy maintenance too - from connection to 4K you can do the lot, all in one box.. no hassle with multiple external servers.

For sure, small branch office that needs a bit of cordless, DECT IP no problem. Campus wide and life & limb? Difficult sell if you're able to use 4K DECT.

 

[GZgidnick]

Considering that Media Servers will fill up the cabinet (virtualization is in the pipe btw) what will your LTUs do?
Have you counted how many LTUs you need to fit your 48 SLC cards? For overcrowded DECT deployment, 3000 handsets, you wouldn't want to fit more than 2 SLCs per LTUs considering timeslots hard limitations would you.
Even if you are generous and put 3 SLCs per LTUs you need need 17 LTUs.
One LTU is 10 RU. Do the math. - You need at least 5 45RU cabinets.

What makes you think that seamless handover is not possible with DECT IP?

Also, why would you think that the linux server would crash? 4K is a linux server as well, it doesn't crashes that often does it. But even if it does, you have option for HA deployment.

I fully agree that DECT IP is not fit for all, and you have old hospitals with old wiring where DECT CMI just makes sense and blends in perfectly. And is an old and proven system. One of the best out there.
But does that mean that you would sell DECT CMI to a new and modern organization? One that already have virtualized 90% of its processing capacity and has rock solid ethernet infrastructure? - NO of course! Because MDF's are things of the past. So is DECT CMI.