sithlord99us

Good Afternoon, All.

I am completely baffled. I upgraded our IP Office 403 from 2.1 to 3.2 (55) like a good admin but now I lost the ability to place people on hold and then retrieve them. I can also no longer park and retrieve a call from an Avaya phone (4620). Here's more infrastructure information:

This IP Office connects to our main Definity system on one IP trunk and this is the same trunk that the call gets put on when a call is placed on hold or call park/retrieve.

When someone tries to retrieve a call from an Avaya phone, it connects, then drops the call with the following error:

2310019mS CALL:2008/04/0110:56,00:00:00,000,47002,O,470020,Retrieve470020 #,UserA,,,1,,""n/a,0
2310020mS PRN: CMExtnHandler::CallLost: call=ffca937c, callid.id=1239561; cause=CMCauseReplaceCurrentCall[136], gone=1
2310021mS CMCallEvt: v=2 State, new=Connected old=Parked,0,0,Astate
2310023mS CMCallEvt: v=2 State, new=Connected old=Connected,0,0,BState
2310024mS CMExtnEvt: v=15 State, new=Connected old=Dialling,0,0,
2310027mS CMExtnEvt: v=15 State, new=Connected old=Connected,0,0,
2310028mS PRN: Setting bchan for extn 47002 to {250,9068} - was {0,0}
2310030mS CMCallEvt: v=2 State, new=Connected old=Connected,0,0,BState
2310031mS CMCallEvt: v=2 State, new=Connected old=Connected,0,0,Astate
2310032mS CMExtnEvt: v=15 State, new=Connected old=Connected,0,0,
2310037mS PRN: **** Call has been deleted - drop call(2).

Anyone interested in helping?

Thank you,
Steve

Phone dude

What release 2.1 did you go from?

I did have this problem when upgrading a 406. The conversion did not make the phones have the same park buttons.

In 1 release it called the feature "Park Call" and the other release was "Call Park". Try deleting the park buttons on 2 phones, merge the config, reopen and put the buttons back on the 2 phones and merge again. Then try testing those 2 phones only. If it works, that is what has happened and you will need to delete and reprogram all park buttons.

__________________
www.telemanuals.com

PBXtech.info

 

Phone dude

OH. I also, off a hunch, saw that the most current maint release is 3.2.61. Try upgrading to that first. Never know, might fix it.

__________________
www.telemanuals.com

sithlord99us

Excitedly I tried the delete/reboot/add procedure to no avail. I did do a trace from our Definity station down to the IP Office and receive "denial event 2306: Reject outbound OLC". The first thing I did was google that and got no help. I guess that's where you gurus come in again.

In summation: I have an IP Office 403 that I upgraded from 2.1 (27) to 3.2 (55) and now cannot retrieve parked calls and when someone is placed on hold and then picked back up, the phone connects (per Call Status) but cannot hear anything from either side.

Thank you for your help.

Phone dude

Try upgrading the system. If you arent comfortable with this, call a vendor in to do it.

A good vendor will have have tech support from their distributor, and, if there is still a problem after the upgrade, they can get a ticket opened with tierIII/IV.

__________________
www.telemanuals.com

sithlord99us

I have no problems with the upgrade, but I assume the only way I can get the 403 bin file is by downloading the entire 4.1 Admin. CD... Is this correct?

BTW: I've upgraded other sites to 3.2(55) from 2.1 and didn't have these problems. This is why it's so frustrating.

PBXtech.info

 

Phone dude

Upgrade all the way to 3.2.61.

If you download the "bin files" it has all the upgrade files for all control units.

__________________
www.telemanuals.com

sithlord99us

Ok. I downloaded the 4.1 CD, copied the bin files to the appropriate server and am unable to upgrade my IP Office to a later version than 3.2 (55) because it is a 403. There isn't a bin for that IPO, only 401 and 406.

With all that being said, I got this to work on a different branch location with the exact same equipment: IP 403, connecting to our Definity system.

I compared the IPO configuration, side-by-side with the one that does work and they are identical.

Anymore help would be greatly appreciated.

Thank you.

Phone dude

asper post above

__________________
www.telemanuals.com

sithlord99us

Good Morning.

As it turns out, changing the signaling for the extensions on my IP Office corrected this problem. I can't really explain why because I don't know and I am not a fan of Voodoo fixes but all is running now.

Thank you, everyone, for your suggestions.