Phantom Call On Line 1

[prflash]

I have an IPO 3.2 (59). The site is constantly complaining of calls being stuck on the first line of the phone. I had one of the client put me on hold and pick the line up and when they do they hear a faint beep then silence. The only way I have been able to clear this is a restart of the IPO. The trouble seems to jump from ext to ext.

Anybody experience this before.

Prflash

 

[telepaul]

Are you using a gsm gateway? as5xxx?

 

[prflash]

No we are not.

 

[IPOfficeIreland]

have you ever heard of gsm gateway? as5xxx?

 

[TomMills]

i had this on 3.2 cant remem ber the version tho. upgraded and all was fine

 

[jamie77]

I've seen this on 3.2(59). Deleting the CA keys and putting them back made it go away.

Jamie Green

ACA:Implement - IP Office
ACS:Implement - IP Office

Football is not a matter of life and death-It is far more important!!!!

 

[prflash]

I have tried to upgrade the system to (61) but had the same issue. I will try removing CA next time.

Prflash

 

[alexaa17]

Upgrade to 3.2.65, issue fixed in that release permanently

 

[prflash]

I will attempt to upgrade to (65) but let me throw a curveball here. I also noticed that the status light on the unit was not green. It was like a yellow/green. I also noticed that for some reason i would see the same extension/user twice in the config. I would see this in both the ext tab and the user tab. Then I would see the same ext in a hunt group twice. I setup a test IPO with the same config on a brand nw system outta the box and still didnt get a solid green status on the Digital Mod. I looked at all my other systems and they all show a solid green status lamp. One thing is i didnt load the config from the problem site onto my test IPO. I just used the default config. Someone hinted to me that it could be the power supply causing this issue. I am going nuts about this.

Prflash

 

[alexaa17]

is digital module on a matching release as main CU. So, if you open control units field and IP406, SOE, 412, etc., show 3.2.(xx)...digital module should be 5.2.(xx)?

 

[prflash]

On my test system I upgraded the IPO to 3.2.65 and the status light on the Digital Mod still is not a solid green. I then upgraded the system to 4.0 and walla the status light turned a solid green. So I am thinking that these unis are coming from our vendor and the software version on them does not work well with older versions. They work but trouble will arise. Now all I have to do is convince management that we should upgrade to 4.0 which they probably will not approve since the last time we did this it was a catastrophe.

Prflash

 

[alexaa17]

It is not really a problem, new modules get shipped with 6.1.xx release, so you have to you IP Office Manager 6.1.xx or greater to see modules. If you want to keep you 3.2.65 version on existing system, Use your 6.1.xx manager to downgrade digital to 4.1.xx and you should be all set

 

[mattKnight]

It is not really a problem, new modules get shipped with 6.1.xx release, so you have to you IP Office Manager 6.1.xx or greater to see modules. If you want to keep you 3.2.65 version on existing system, Use your 6.1.xx manager to downgrade digital to 4.1.xx and you should be all set

WRONG WRONG WRONG
do not forget that all expansion unit firmwares are 2 full versions ahead i.e. 3.1.65 main unit and 5.1.65 expansions.

All expansion units are shipped with firmware 4.1.31. This is the lowest firmware available and is part of the manager 2.1.31 load.

With virtually any deployed system, you will have to upgrade the expansion unit to match.

Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[alexaa17]

After prflash upgraded his sustem to 4.0, he could see module (light stopped blinking orange/green per above thread), doesn't it mean that dig module was not on 5.2.xx, but above that firmware release. Since he upgraded to 4.0(mentioned above), module had to have been 6.0.xx firmware or below, but above 5.2.xx because he could not see it in 5.2.65 manager. Wasn't it, mattKnight?

 

[alexaa17]

I should correct myself on downgrading from 6.1.xx to 5.2.65 firmware of the dig module since IPO version is 3.2.65

 

[prflash]

Update:

I found another digital Mod in our warehouse and ooked that one to the IPO which I downgraded to 3.2.65 and the status light was solid green. But the version on that unit was 3.1.48. I looked at the 2 unit and they look exactly alike except that I am pretty sure that the one that is working was probably shipped with older version of software.
So one of our other techs is down at Fla. and he installed the second module with the current software and still the status lamp on both modules show amber/green. I then was able to find one of our IPO's out there with the 3.1 software and remotely downgraded the mods to 3.1.48 and same result. The system is working but the modules are amber/green status.

This is blowing me away.

prflash

 

[tlpeter]

The color of the led is not a good thing to look at !!!
If the led is broken it can show any color !!!
Hook up a DTE cable and look for strange messages

ACA - Implement IP Office
ACS - Implement IP Office
ACA - Voice Services Management
______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!