OWS Problem

[meltitdown]

I have 3 operators setup in 3 different lims with the same problem. They are intermitantly made unavailible. I notice if I try to start the signal log for the CT adapter they are forced unavailible as well. The AS parameters for forced unavailiblity are set to large values.

DNA 5.1
BC11sp13

3 x CT adapters = R6A

1 x ROF1375334/2 R5A
2 x ROF1375334/3 R2A

Does anyone have any ideas?

 

[Kressmark]

Hi,

I do not have any ideas directly related to your problem.

However, there are newer versions than R6A of the CT adapter available.

/mk

 

[hadokk]

Hi!

Just a small idea, what kind of phones do you use together with the CT-adaptor for your OWS? DBC 222 01 / DBC 220 01 (Dialog 4220 / 4222)?

We’ve really bad experiences from using this models connected to CT-adaptor in OWS environment at several installations. Causing lot's of disconnections and interrupts between MD and CT-adaptor/PBX-service/Phone with the Dialog 42*0-seriese phones.

In the “windows eventlog” PBX-service logs all interrupts between MD<->CT-adaptor <->Phone <-> PbxService if this particular problem occurs.

/Hadokk

 

[Kressmark]

Hi,

If you are using an DBC 220 01 with a CT adapter and OWS make sure that the phone is at least revision DBC 220 01 / XXXXX R2C. There is a service advice issued from Ericsson about these problems.

/mk

 

[hadokk]

I've also seen the service advice "12/0062-FCP 107 242 REV B" with the recommendation of using at least rev. DBC 220 01 / XXXXX R2C in OWS environments. But I can still establish a fact that we've several times got BIG problems with the connection between OWS and MD when we are using phones with proper rev. (DBC 220 01 / XXXXX R2C). Problems that in fact immediately disappears when we are changing the phones to the old series (e.g DBC 202 01 / Dialog 3212).

/H

 

[meltitdown]

Thanks for all your replys...I am using DBC 202 01 phones for all the OWS's.