Virtual Office - Licesing

Or Licensing even ;-)

It depends on how your are going to be using the virtual office.

If you have 2 sites, and you want users from site A to be able to travel to site B and do a virtual office login, then you just need a single license for each physical phone at sites A and B.

If you have 1 site and you want users to be able to go to any phone and log in (sometimes called hotelling), then you will need a license for the physical phone, and a license for the virtual phone

Thanks for the advice, however i have had an email back with the text below, hopefully the Engineer can take a look and see if it works.



Notice:
This bulletin replaces bulletin 2007008289.1. This update has
been issued to communicate some new information regarding
the issue.
BULLETIN ID: 2007008289, Rev 2
PUBLISHED: 2007-09-14
STATUS: Retired
REGION: APAC
CALA
EMEA
GC
NA
PRIORITY: Information
TYPE: Bulletin
Reissue Reason:
Re-issue as a Technical Bulletin
Background:
This bulletin is to clarify the operation and implementation of the Basic Emergency Service when VO Logged Out feature
introduced in CS 1000 Release 5.00W.
Analysis:
Environment PRIOR to CS 1000 Release 5.00W
Customers using Virtual Office required that IP sets in a logged out state have the ability to make an emergency call. The
workaround was to provide double the number of IP User ISMs needed on the system, with the channel/customer given
the undertaking that the extra licenses would only be used for defining locked down, base profiles that would always be
logged in on the sets to allow an emergency call to be made.
Environment with CS 1000 Release 5.00W
No actual change in the licensing requirements in regards to Virtual Office was introduced however additional functionality
was added allowing basic emergency calls from IP sets in a Virtual Office Logged Out state.
To accomplish this, a new device type of VOLO was added. Anytime a user attempts to make a call from an IP set in a
Virtual Office Logged Out state, a VOLO TN is temporarily assigned to the IP set. If the number dialled matches one of
the defined ESA ESDN numbers on the system then the call is allowed. All other calls receive overflow tone and the
VOLO device is then released. VOLO devices are pooled resources with the system administrator able to define a pool of
up to 255 VOLO devices.
The following configuration rules for VOLO TNs apply:
* VOLO TNs are built on Virtual Loops therefore proper engineering consideration must be given to the overall system
capacity design.
* IP phones can not register directly to a VOLO TN. The default TN stored in the IP Phones NVRAM must be a normal IP
phone virtual TN requiring an IP user license.
* VOLO TNs must be a contiguous TN block
* The VOLO TN block must first be defined in Overlay LD 24
.
>TECHNICAL SUPPORT
. TECHNICAL BULLETIN
.
.
Clarification on Basic Emergency Service when VO Logged OutExample:
VOLO_COUNT aaa
VOLO_FIRST_TN l s c u
VOLO_CALBK_TIM bb
Where aaa is the number of VOLO TNs desired up to a maximum of 255, l s c u is the Loop Shelf Card and Unit of the
first VOLO TN, and bb is the number of minutes the callback timer will remain active after a call to a valid ESDN.
Recommendations:
The CS 1000 system must still be configured with a sufficient number of IP ISMs to provide IP User and IP Station
connectivity; however the number of licenses consumed is significantly reduced with the VOLO functionality.
For example:
Customer has a total of 1000 IP users with 800 users with desks in the office and the remaining 200 users using 100
touch-down stations.
The total number of IP licenses required would be 1000 to provide a profile for each user broken down as follows:
800 IP Users with physical IP Phones
100 IP Users provisioned against the 100 touch-down cube phones and then logged out
100 IP Users provisioned with no physical phones
Prior to CS 1000 Release 5.0, an extra 100 IP ISMs would have been required for the touch-down cube IP Phones to
provide Emergency Access Service while in a VO logged out state.
Required Actions:
PEP required preventing VOLO TNs from decrementing the IP ISM count
It was noticed very shortly after CS 1000 Release 5.00W GA that when a VOLO device was configured on the system, an
IP User ISM was used, which was not the intent. MPLR24386 resolves this issue and allows VOLO TNs to be provisioned
without decrementing the IP User ISM count.
Special instructions are included with MPLR24386 to recover the ISMs lost for those systems that already have VOLO
TNs configured.
Attachments:
There are no attachments for this bulletin
Footer Information:
Retirement Reason:
Auto-Retired due to Reissue of Bulletin. Re-issued as 2007008289.3.
For Additional Information:
For additional information contact Mark Fletcher at fletch@notrtel.com referencing this bulletin in the subject header.
Products and Releases:
The information in this bulletin is intended to be used with the following products and associated releases:
PRODUCT RELEASE
Enterprise VoIP-Core-CS 1000E 05.00W
CLARIFICATION ON BASIC EMERGENCY SERVICE WHEN VO LOGGED OUT 2007008289, REV 2

There is a patch out MPLR25003 that allows a phone to register aginst TN 0-0-0-0 and Node 0000.

This effectivly allows you to have phones out there with no TN provisioned, therefore not using an ISM.

There are several restrictions and interactions that need to be reviewed, however this patch has been effective in many cases. The patch is listed in the ESPL, but requires a GNTS ticket to obtain it.

Limitations for MPLR25003:
--------------------------
1. Only cookie support sets are covered by this feature.
2. The following limitations are related to the SS real-time capacity limits and can not be changed:
- The TPS supports a maximum of 5.000 IP Phones on each Signaling Server (NN43001-312_01.07_SgSvinCfg.pdf page 20). So, the number of users is
limited by the system configuration.
- When 10.000 sets are put in logged out state during Midnight Routine they will be logged out in 2 hours (Every Signaling Server (SS) process about 30 sets per second. 5.000 sets are registered per SS. So, two SS can process up to 60 sets per second. It take about 2 hours (111 minutes) to put all the sets in the logged out state).
- When 10.000 sets are starting to logging in at the same time they will be logged in 2 hours. (5.000 sets are registered per SS. 30 sets only are processed per second. The interval between login retries is about 5-15 seconds (manual or automatic login). It takes about 83 minutes to put all the sets in logged in state.). Some of the sets will be in logged out state during 2 hours.
3. In case of the ESA call from the set which is logged out using Default VO feature the Customer and zone numbers is set equal to 0 for this set. So, the TN is selected from the ESTN pool for Customer 0.
Only Internal LIS is supported. Ensure package 336 is enabled. External LIS is not supported.
4. When the set is registered on TN 0-0-0-0, and a user do Virtual Login on that set there is no current zone of the host IP set, so the configured zone will be used by the VO set when the user makes an outgoing call.


--
Fletch

Nortel Emergency Services PLM

Check out this month's E911 Talk podcast at Nortel E911 Talk Podcast