Hybrid OpenScape4K system + wifi handsets?

[tonymcd]

Inherited support of a phone system (Unify OpenScape 4000K) that has capacity to support wifi handsets and there are a number available for use.
I understand they will need to be programmed and some system setup to make operational?
Can anyone expand/shed any light/offer guidance or assistance on this please?

As always.... much appreciated in advance

 

[sbcsu]

That is a big ask Tony!
What part are you stuck on ?
Did you get any handover from the previous maintainer ?
Any notes on site ?
Do you need to register handsets today ?

 

[tonymcd]

I realise and thus was shocked but reassured to get a reply so soon.

Setting up from scratch which I know is a significant task, I dont need blow by blow or 'how to' guidance you will be pleased to hear. Ideally I want to understanding why colleagues suggest to contemplate this is so expensive.
For the solution programmer Unify have quoted 18k alone? Is this realistic and even correct or accurate?

Failing using the prime solution could something else be utilised with the same end result on OS4K system?

Thanks

 

[sbcsu]

So 18K for what exactly ?
If you need to add WL3 handsets and you already have some connected then it should be a case of opening the software tools and setting up new handsets.

What happened to the 'old' maintainer ?
Are there any courses you could go on ?

Do you have the software(s) to connect and modify the system ?

I presume you are in North America - there should be courses available in Boca Raton - Don should advise - hopefully he will log on and reply shortly.

 

[tonymcd]

The 18K was specifically suggested to be the cost of the programmer for the handsets?
Currently the OS4K system is inactive and there are no WL3 handsets programmed for reasons mentioned earlier.
Maintainer are still available and willing to follow up initial quote of 18K, as regards courses possibly.

I am guessing the software to connect up and program is the programmer I have earlier referred to(not sure)?
Not in US but UK, Unify still active as a subsidiary of Atos now. Honestly not an OEM that readily rolls off the tongue when talking about VOIP in the UK. I am personally more familiar with Avaya, Cisco, ShoreTel....

Sounds like I am driving a very powerful car with no brakes very fast in the dark and no lights on...

Thanks

 

[donb01]

I have a hybrid 4K and I inherited a box of WL2 handsets a few years ago. I was messing with them last year and had one working on my regular office extension, but I had a number of issues. The first issue is the phones didn't (don't) support PEAP or LEAP or whatever stupid proprietary Cisco protocol we were using on the network, so I got them to set up a hidden "phones" network with more simple authentication on it. I had that working, but before I could hop on the DLS and update the firmware on that handset we were having some network Auth issues and my boss kissed butt and gave out that SSID until they fixed it, and then of course everyone was using it so they deleted it. After that I got busy and never looked at it again since. Hopefully you have either newer hardware or more current firmware than I had!

The actual config of the phone one you get it on the network and can use its WBM is not horribly difficult, but some of the words they use for some of the menu items do not make it crystal clear what they do. Do remember to save after making changes - it you just "X" out of the webpage it doesn't know to save your changes!!


Don Bruechert, Voice Comm Analyst II
CareTech Solutions @ Holy Family Memorial
Manitowoc, WI, USA

 

[tonymcd]

Thanks Don,
Pretty sure we have WL3 handsets.

Unify have used a preferred sub-contractor that we have engaged with to simply get the system up and operational - its been 'mothballed' for 2 years. Step 1 is to upgrade to latest OS, which coincides with infrastructure upgrade to ver 6.0 vmware environment not long ago.

Work in public sector - so funds are very tight, regularly non-existent...any excesses of cost will result in this whole thing being canned. Rather unfortunate and alarming as around 200k has already been spent on it!

Thanks

 

[sbcsu]

Beeston in Nottingham so would be your best bet. (The old Plessey GEC Factory)
They still do courses there and are very helpful.
The WL3 are recommended rather than WL2.
The WL3 are actually Ascom phones but they work fine on the 4K.
There will be/are independent maintainers that could assist but an official one would have access to software for upgrading etc.

If it were me I would be talking with the Project Manager of how 200K has been spend but still not functioning and get at least the system up and running.

 

[member 1453342]

There are two sides to the problem, the OS4K and the handsets.

First you need the OS4K to provide SIP connectivity (which should work to any SIP device like a Unify WL3 or wired handset, or any other third party SIP device/soft client). If you have physical shelves you need (a) an STMI card configuring for SIP extensions and (b) some SIP extensions adding in the telephony DB. If you have a software shelf like an Access 500 or something running in ESX, the STMI becomes a vSTMI but the principal is the same... the (virtual) card would need to be added, and some SIP extensions added into the DB. The STMI or vSTMI is given an IP address and your SIP client would register to it.

Second, you need the WL3s configuring to register on the STMI card. This requires the programming module to configure the phones (an Ascom'ism). Other SIP handsets will work but the WL3 uses Unify firmware and is fully supported. In your post you say the OS4K has the capacity to support wifi handsets. To be clear, the OS4K is supporting SIP handsets which happen to register to STMI over your wifi. 4K neither knows nor cares about the WLAN.

There is not a large amount of work here, configuring each physical handset will be the brunt of it. You could do that yourself once the OS4K is configured for SIP. Some of your cost may be for a physical STMI card which you need to provide the SIP connectivity.

>>Unify still active as a subsidiary of Atos now. Honestly not an OEM that readily rolls off the tongue when talking about VOIP in the UK
Siemens now Unify VOIP kit is rock solid, it'll do the job when it's configured right - and when your network is up to scratch. Don't forget that bit. Make sure your QoS is configured on the OS4K, the handsets, and in your network.

Training department is now in Milton Keynes.

 

[tonymcd]

Moriendi,
Thank you for the extensive and detailed description it is very useful.
I am now at the point of actually moving forward on this action to enable the WL3's.
We have instructed a sub contractor who is currently doing the majority of this work.
I am peering over the should when possible.

Thank you

 

[tonymcd]

The action led very quickly to inaction, it remained on the back burner with no hope of resurrection.
Until....the prospect of a wireless device appeared to be of interest, too good an opportunity to miss...
I have now been summarily issued with - software from Unify, a cradle, list of system settings and tasked to configure 2 x units immediately.
In addition I need to (positively?) update by lunchtime today on my progress, no pressure really then...?

 

[sbcsu]

So you are going to add one WL3 handset to the HiPath 4000 today ?

CHA-ZAND:OPTLOAD;
has to be completed or SIP extensions will not load.

Add in a SIP extension card or part of a card (STMI or STMIX or vSTMI)

Add the SIP extension

Update the software on the WL3 using the USB dock.

Change the settings on the WL3 to tell it Gateway and SIP card and extension number.

 

[tonymcd]

sbcsu,
Really appreciate your lightening response and assistance on this
With the cradle I can update and save templates and push to device.
I can access DLS and have some credentials to get to other things.
The 3 WL3's are pre-configured WL3's thus no need to setup - already done.
Where I am struggling is to find Gateway and SIP card info? Any clues?
Cheers

 

[sbcsu]

The SIP Card info is the IP address of the HiPath or OSV card that has the WL3 extension setup.
If there are any other SIP handsets on your system then they probably have the same SIP Card IP address

Looking at WL3 configs I don't see 'Gateway' however if it is under Network then it is the IP address of the default Gateway of the current IP address of the phone.

 

[tonymcd]

sbcsu,
I guessed you will have sussed by now I am the first to ever connect sadly no comparison device(s), but hey what can you do about that
Shall poke around in configs and documentation where I presume I will eventually find the info I need.

Thanks

 

[sbcsu]

Tony - if you do have access to the system look at the boards
On ComWin/Expert Access that is
DIS-BCSU;

Then you are searching for 'SIP'
It should be similar on the Assistant - Configuration Management/System Data/Board/Board then Search / Object List and then Board Name
You are looking for STMI or STMIX or VHG3500
If you scroll over to the right you should see SIP and the IP Address