Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Question on the norm of SCN and base extension setup

Status
Not open for further replies.

mikedphones

Vendor
Joined
Oct 11, 2005
Messages
467
Location
US
This may be really obvious, but in general if you guys have two sites in an SCN setup and the 80% of the people never move, but the other 20% log in and out at each site, what's the best way to set the whole thing up? I was thinking of one of the following:

1. Site A is considered the main with VM PRO. Make all base extensions (they are all DS) 500s (like 501-532. Make site B base extensions all 600s (like 601-632). Build all user profiles on the Site system and have exactly the same user rights built at both sites.


2. Same as option 1 above, BUT for the 80% of the people who never move, put their user profiles on the system they are native to and make their base extension the same as their user extension.

Is there another way or a variation of these that should be considered "the norm" ?





 
Sorry,

I should have said that all users are in the 100 range. So user profiles would be 100-132 in this example. The reference to base extensions at site A being 500-532 and Site B being 600-632 was to illustrate no conflicts.

 
Users who don't move should have the same base extension as their user extension on the system they are "at home".

That way you ensure that 80% of the user's stay registered and reachable even if you have to reboot the system.
 
I do almost nothing else as SCN installs (most standalone systems are Panasonic = a lot cheaper) and basically there are only a few rules to follow:
1 Each line must have a unique outgoing ID over all sites
2 System names must not match any other name
3 User and group names must be unique
4 Hot desk users don't need a extension
5 no need for a "site specific" numbering plan
6 system timers must be equal
7 if used (I mostly don't) then User rights must be the same on all sites
8 ICR DDI numbers are used for sending the outgoing ID if the traget is a user, that can be a problem for hotdesk users, keep that in mind
 
Thank you both.

I guess my question was more about where to build user profiles for the hotdesk users. It sounds like their user profiles should be built on the main system (Site A) and the Site B and subsequent future systems have no actual users built (unless they are specific to that site and never hotdesking, in which case their user and base extensions are set the same). Does this sound reasonable?

Intrigrant, Regarding ICR DDI, in this case they actually have POTS lines at both sites, but if they had a PRI with DID, for outbound calls are you saying this is a potential problem? Can you explain further?
 
I always create the users at the site they are most of the time and/or where they have their main office. If they don't have a personal main site then I would usually create them at the overall main site.

Nevertheless in some cases you can think about mixing them if it works better with licensing.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top