This is kind of hard to understand, but the normal process is you set the 2 phones so they can be "visited" or a "home phone of visitor" and then you set up Mobility PINs for the phones. If I sit down at 7000 and tell it I want to become 6000 I would enter a PIN number and that would "log-off" 6000 and pull all of it's features to 7000. During that time 6000 cannot be used because it is being used remotely, and if someone sits down at 6000 and tries to use it they have to cancel the mobility, which will then put 6000 back in service and it will no longer be controlled by 7000.

I do this all the time with my Openscape Desktop software - then I want to use phy phone on my computer I load the software and it logs off my phone so I can use it on my computer. If I go to a different building and enter my mobility PIN into a phone over there I can have my extension working at the phone where I'm sitting. In either case the phone that is being remote controlled cannot be used by anyone else. An extension can only be "logged in" one place at a time. It sounds like you are running into that situation where someone else messes with the phone and it logs you off at the remote location.

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

hi Donb

actually your correct. when it comes to licensing if i have a 300 IP phone with config local dummy number(phone is up and ready) and a deskhare local 900 users a total of 1100 license for this right? becausse they have 3 shifting on their work thats why we need this features login/logoff but the problem is phone home and visitors only. once you log your number to other station and and if someone try to log on to your existing phone the phone is back to normal locals.

any idea or any solution for my scenario if i have 900 users i only need license is 900 not 1100 because of the dummy number.
thanks
dreb

I might be mistaken, but I only thought you got charged for only devices that required an actual port. A phantom device being a "logged off" station doesn't count against the total (or someone will tell me I'm wrong, but I didn't think it did). In the new world, with the Comscendo licenses, a port is a port - so if you have 1000 comscendo licenses each one could be a phone, or a trunk or an announcement device, or whatever. I assume you did a DIS-CODEW; to see your actual license? You can also do DIS-VADSU; and it will tell you how many physical phones, trunks, whatever that you have currently in use.

If you have 1000 devices and 900 licenses, and you have to use them all at once for some reason you will run into a problem even if you use PINs to move numbers around. You can have "logged off" (phantom) station numbers, but you still have to have an appearance of that number on a physical phone, or you have to pull the number onto a physical phone with a PIN in order to use it, so you have to have one port per person no matter how you number them.

You might also want to look at DIS-DIMEN; (I think)and if it says you have 300 digital phones built and your maximum system capacity is set to 300, but you still have unused licenses available, you can actually bump that 300 up to 325 and build out a few more phones (if you have available ports). You have to be careful messing with those numbers though because that is the master memory allocation table for the entire system and you can cause major problems if you make big changes.

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

So I think your problem is that someone cancels the HFA Mobility and you don't want them to. A logs onto B, then someone tries to use A and cancels the mobility.

From documentation, you can prevent that with a PIN.


Password settings
For the mobile user a mobile password should be added. This password prevents the “forced logoff“ at the home station from being canceled without a password.

• optiPoint terminals
The password is assigned in the terminal Configuration menu, submenu “02=System”.

• OpenStage terminals
The password can be assigned via the WBM of the terminal (Administrator Pages > User mobility > Cancel mobility password) or directly at the terminal via the menu Admin > Password > Mobility.

Alternatively, you don't use the Mobile HFA feature, but just use feature "PIN and Follow-Me Network Wide". This would allow you to pin-on as extn A to extn B, and A would divert to B (if you use follow-me in one step classmark). Extn A does not log-off in this case, it stays working. Code for this is WABE APIN1 not MHFALGON. You can check PERSI COPIN for the exact config of what to do when APIN1 is used.

Or, if you are all hot desking, then you make every physical phone a 'dummy' number, and everyone's real number becomes a float extension, and you pin-on and pin-off as required (again with APIN1 code).

Feature Description/Feature Usage documentation describes these features in detail. Worth checking to see if they are on the download site used here.

Hi Donb And Moriendi
thanks for the help.

it's now clear on my mind.

dreb