IP Softphone not releasing to 6424

[mmcalli]

When I choose "Exit and Logoff" my softphone(V5), it is not releasing control back to my 6424 physical phone. I've tried:
1) busy and release of my station number
2) busy medpro board,
ch ip-int and changed medpro to N,
issue "reset board 01b01"(medpro),
cha ip-int and changed medpro to yes,
release medpro board.
I think I got this way from doing some softphone testing from home this weekend--and it was having troubles. Luckily I can open softphone here and use it just fine now with my new USB headset--which makes a world of difference.

What's the trick here? Thanks for any suggestions.

 

[mmcalli]

I discovered alarms on Medpropt's #'s 5,6,7,8 and ran some tests and finally removed and reseated the card--this cleared the errors but did not release control back to my physical extension. The softphone is working great but I'd like to be able to use my desk phone too!

 

[mmcalli]

I've got my phone back after assigning associate and disassociate FAC's for PSA (personal Station Access) and using the associate code on my physical station. Is it an expected result that one needs to reassociate the physical phone to your extension after exiting the softphone application? I'm sure in my earlier testing that upon exiting the softphone app, my physical station was returned to it's normal state. I'm using road-warrior mode and currently using V5 with the service pack. Hmmm, that is a recent change--wonder if it's related??

 

[mcopini]

Let me see if I get this: You're using Softphone in Road-warrior mode, which means that all voice is over IP. Where does the digital station 6424 fit in? If you administer an extension to be an IP-softphone, it can never be a fysical digital phone at the same time. This is not a bug but just a configuration thing. The station you log in to with softphone is always an x-port station with the field softphone set to yes and cannot be a fysically existing digital phoneset at the same time. So it was never intended to 'give the controls back' to the station after logging off...


Kind Regards,
Maarten Copini

http://www.effecta.nl

Home is were you end up when you've got nothing better to do

 

[lopes1211]

Mine works fine with R5 Softphone, R10 Definity. I have an 8434DX assigned to a dcp port with softphone flagged yes. When I'm home, I log in the softphone app and receive the warning that the extension I'm trying to use is already assigned on a dcp port. I select OK and disassociates the DCP set, and off I go as roadwarrior. When logging out of softphone, it reassigns the same DCP port back to the 8434DX so it works again in the office. What version of PBX?

-CL

 

[BuckWeet]

This has happened every since R4 for us. We're r9.5.

Basically his problem is that he is logging into the the PBX as his real extension #, and unless you logoff successfully from IP softphone, the switch will not reassociate the station back to the DCP set.. I guess basically the switch isn't seeing the disassociate message and not reassociating the DCP set..

I don't know of a fix for this, we have been making different extenstions and using bridged appearances to get around this..


BuckWeet

 

[lopes1211]

Try using logoff instead of exit/logoff. After all of the sucessful messages, then exit.

-CL

 

[mmcalli]

Sorryfor the delay folks--I've been out from work for a week.
MCopini,
I'm trying to do the same thing as Lopes1211--take control of a physical station when at home and releasing control back to the physical extension after logging off.

Lopes1211,
You've got the scenario down except I'm using a 6424D+M at work and we're running V9.5 software on the PBX. I'm wondering if there is a problem in that my station at work has a data module associated with it for PBX administration in case of network problems. I'll have to try removing that and see if it helps. I'll also try the Logoff then Exit strategy instead of Exit&Logoff selection.

Buckweet,
You've nailed the issue too! Are you using V5 Softphone now and still have that problem? What's weird is that when I was first playing with it at work--the disassociation seemed to be working fine but now it doesn't. I'm going to try Lopes1211's suggestion tomorrow and removing the data module from the equation.

Thanks for the thoughts--any more suggestions?

 

[mrjedi]

you need to run either R3 or R2 to work properly. We are running on 9.5 and I have users on R2 4 and 5. 4 and 5 gives that problem, but I run on R2 and it works fine. Not sure where you can get a copy of it though.

 

[joel7]

CL, I would imagine that you are using some sort of VPN to get onto your office network from home. What VPN are you using? Were using Watchguard but were still having problems using the Softphone through our VPN even when we assign the IP that the VPN client is giving the machine.

Joel

 

[lopes1211]

Lucent IPSEC is our VPN. I do know you cannot flag a phone as "softphone" if it has a data module assigned. The data mod may be the issue. Retest with a phone which doesn't have a data mod assigned.

-CL

 

[mmcalli]

Found this little nugget in Avaya's Softphone User’s Guide
of all places---


Un-Registration/Logoff
When you are done with your DEFINITY Softphone or done with DoLAN, you can un-register by
performing the following:
Go to your task bar and look for a ‘handset and telephone’ symbol. 2) Now ‘right Click’ on the symbol
and select logoff.
For all users – un-registration does not return control to your DCP phone. In order to get control of your
DCP set back you must do the following:
1) Dial PSA FAC – user then receives dial tone again
2) Dial your extension number (DCP set that you want to get back control of) followed by a
‘#’
3) Dial your personal station password (security code) followed by ‘#’
Note:
if your extension is AWOH (administered without hardware) you will not have to perform the
above steps 3 through 5. - never dial the PSA Associate code unless steps 1 or 2 above have
been done first.

However, I've managed to Exit and Logoff before and had it auto-reassociate. Must be one of those sometimes things.