4.4 Site Tab

Each site’s (headquarters and remote offices) basic parameters that are to be used in the generation of the solution are defined in this tab.

•

Site data: extensions range, time zone, numbering plan information.

•

Application servers, the remote sites’ gateways and proxies.

•

Subscriber Data: basic data items related to the site’s subscribers.

•

Whether Local Toll Tables are used.

•

Number of channels (CAC) used in the WAN.

NOTE: Please refer to Section 2.5.1, “Solution Configuration” for more details.

•

Delta - When Delta generation on the Start tab is set to "Delta on OSV configuration" and the user clicks on "Generate Config", only sites that have the Delta value set to ’yes’ will be generated.

Information on how to use the Delta on OSV configuration capability:

–

Import your 8k configuration into WebCDC using the "Import OSV data (MP2)" button. You will also be asked to provide a copy of the OSCV node.cfg file. When this step is completed, the field Delta generation on the Start tab will be automatically switched to "Delta on OSV configuration".

–

On the Site tab, mark the Delta Site(s) to be generated by setting the respective value(s) to 'yes'.

–

Finish entering the configuration data for Delta on OSV configuration on the other tabs (i.e., Endpoints tab, Analog Adapters tab, etc.).

–

Generate delta configuration by clicking on the "Generate Config" button.

•

Site Name - For the site name following has to be taken into account:

–

The site name cannot be longer than 10 characters.

–

The site name has to be a valid DNS name, e.g. alphanumeric characters, a minus (-) and a period (.) are allowed.

•

Site Component in the Domain Name (FQDN) - The site component in the Domain Name (FQDN) is entered in this field. Typically for constructing the FQDN name one has: <hostname>.<site part>.<company domain name>
This is used for defining the FQDN of the proxy in the branch.

•

DNS SRV Record of the Site Proxy (DNS SRV) - The value in this cell refers to the DNS SRV of the Proxy.

–

For full proxy redudancy this field should be configured.

–

For OSEE solutions this field is being autogenerated and DNSSRV entries are used for redundancy purposes where possible.

–

For RA solutions the user should set up the DNS server manually.

If “Site Component in the Domain Name” IS filled and “DNS SRV Record Of The Site Proxy” IS also filled then:

–

In OSV script:

•

Proxy EPs are configured using <hostname>.<site_part>.<solution_domain> (FQDN record in DNS).

•

EPs behind the Site Proxy EP are configured using the <hostname>.<site_part>.<solution_domain> (FQDN record in DNS)

–

In DLS template:

•

The SIP Proxy/Gateway is configured using the “DNS SRV Record Of The Site Proxy” (DNSSRV record in DNS. Redudancy enabled).

–

In Proxy script:

•

The “DNS SRV Record Of The Site Proxy” is used.

Else if “Site Component in the Domain Name” IS filled and “DNS SRV Record Of The Site Proxy” IS NOT filled then:

–

In OSV script:

•

Proxy EPs are configures using <hostname>.<site_part>.<solution_domain> (FQDN record in DNS).

•

EPs behind Site Proxy EP are configured using the <hostname>.<site_part>.<solution_domain> (FQDN record in DNS)

–

In DLS template:

•

The SIP Proxy/Gateway is configured using the hostname.site_part.solution_domain
(FQDN record in DNS. No proxy redudancy for devices)

–

In Proxy script:

•

The <hostname>.<Site Component in the Domain Name>.<domainName> is used.

Else if “Site Component in the Domain Name” IS NOT filled and “DNS SRV Record Of The Site Proxy” IS filled then:

–

In OSV script:

•

Proxy EPs are configured using <hostname>.<site_part>.<solution_domain> (FQDN record in DNS)

•

EPs behind Site Proxy EP are configured using the <hostname>.<site_part>.<solution_domain> (FQDN record in DNS)

–

In DLS template:

•

The SIP Proxy/Gateway is configured using the "DNS SRV Record Of The Site Proxy" (DNSSRV record in DNS. Redudancy enabled)

–

In Proxy script:

•

The “DNS SRV Record Of The Site Proxy” is used

Else if “Site Component in the Domain Name" IS NOT filled and "DNS SRV Record Of The Site Proxy” IS NOT filled then:

–

In OSV script:

•

Proxy EPs are configured using IP address defined in Endpoints tab.

•

EPs behind Site Proxy EP are configured using IP addresses defined in Endpoints tab (if they are static registered).

–

In DLS template:

•

The SIP Proxy/Gateway is configured using IP address defined in Endpoints tab (No proxy redudancy for devices).

–

In Proxy script:

•

It is not defined.

•

Extension ranges - Comma separated list. The (internal or external) extension range for the subscribers.

These extension ranges can be part of the public extension ranges (these public ranges are given in the Endpoints tab) or not (private extensions).

CDC detects itself if the extension ranges overlap with the ones in the endpoint tab, and then we have public numbers, or if the extension range does not overlap with the extension range in the endpoint tab, and then we have private extensions.

If this field is left empty then this field is assumed to have the same values as the public extensions (all internal extensions are related to a public number)

•

Office Code for OpenScape Mobile feature - This is the Site Office Code used to construct the OSMO Subscribers range for a specific site. Length: 3-8 digits.

NOTE: If this field is left empty for a site, the OSMO subscribers will not be generated for this specific site even if the field "OpenScape Mobile Feature" is set to ’yes’ on Subscribers tab.

•

Access code for outgoing line - The code to dial outside. Typically 9 for US and 0 for the rest of the world.

•

Time Zone - The time zone of the Headquarters is used for the installation of the OSV system (node.cfg)

•

Make default subscribers for the extension range - If set to “yes” then subscribers are added according to the above given extension range of the site. For any other value the range of subscribers will not be created.

•

Make the created subscribers also OpenScape UC App. users - If “Make default subscribers for the extension range” is set to “yes” then this flag is set to “yes” too and the default added subscribers are made OpenScape UC App. users.

•

Make default OpenScape Mobile Subscribers -

•

Site prefix - For sites with open numbering or sites with private only numbers, a site prefix is entered. If no prefix is entered then it is assumed that all users have public numbers. A maximum of sever digits is allowed for the site prefix.

•

Local DNS server - In case you have a remote site with it's own DNS server (other than the OpenScape Branch), then you can enter the IP address of the DNS server that will be used as primary DNS server of that remote site's OpenScape Branch.

The DNS server(s) defined in the “IP” tab will be used as secondary. This is however optional.

If you leave this field empty, then the remote site's OpenScape Branch will use the DNS server(s) defined in the “IP” tab. Headquarters always use the DNS server in “IP” tab; thus this option is disabled.

•

Local NTP server - In case you do have a remote site with it's own NTP server other than the OpenScape Branch), then you can enter the IP address of the NTP server for that remote site.
This is however optional. If you leave this field empty, then the site will use the central NTP server IP Address as defined in the “IP” tab.

During the “generate all configuration files” the CDC will assign following NTP server for following devices:

IP Phones get the OpenScape Branch as NTP server. Gateways get the OpenScape Branch as NTP server. OpenScape Branch get the Local NTP server when filled in for this remote side, otherwise the central NTP server is used.

•

Backup Gateway for Local Gateway - The name must match a site name used. This is the backup gateway for the local gateway (found in local numbering plan, PNP).

•

Central Gateway - The name must match a site name, where the central GW is located. Central GW is found in the common numbering plan.

•

Default Device Type for the Subscribers (*) - If no device is chosen for a subscriber (“Device Type” in “Subscribers” tab) then the device type chosen here is taken for this subscriber.

•

Default Dialing Permissions for the Subscribers (*) - If no dialing permission is chosen for a subscriber (“Subscriber permissions” in “Subscribers” tab) then the dialing permissions chosen here is taken for this subscriber.

•

Default Prompt Language for the Subscribers (*) - If no prompt language is chosen for a subscriber (“Prompt Language” in “Subscribers” tab) then the prompt language chosen here is taken for this subscriber.

NOTE: WebCDC offers 3 different options for the English language: British English, American English, and English. If the last option (English) is set, WebCDC will automatically change the Prompt Language to British English, except if the Country Code in the Endpoints tab is set to 1 (US), where in this case it will be changed to American English.

•

Default Xpressions Language for the Subscribers - If no language is chosen for a subscriber (“Language” in “OpenScape Xpressions Data” tab) then the language chosen here is taken for this subscriber in Xpressions.

•

Second Language for Announcements (optional) - The option exists for supporting a second language. The language must also be installed on the media server.

•

Xpressions Direct Access Number - This call number is used to access the voicemail system (Xpressions) and is dialable from PSTN. Therefore it must be a valid DID number.

–

Each site should have direct access numbers defined.

–

If not provided, access numbers from the head quarter site shall be used which could be a long distance call to access the voice mail server from the sites other than headquarter.

•

Xpressions Guest/Forward Access Number - This call number is used for the call forwarding to Xpressions on the phones. On the phones which are controlled by the DLS server, there is a features XML Template. User can provision either DID number of fully defined Private number.

–

In the features template, there is the Xpressions call forward access number, so that the users can easily activate on their phone a call forward to their voicemail.

–

WebCDC will write this Xpressions callback Access Number automatically in the DLS miscellaneous Template (CDC_Template_<sitename>_misc.xml)

–

When these call numbers are empty for a site (non-HQ site), then the XPR call numbers of the HQ are used, which could be a long distance call to access the voice mail server from the sites other than headquarter.

•

Xpression Callback Access Number (UC Voicemail) - This call number is used for the MWI led on the phones. When the MWI led is on, and the MWI key is pressed, then the phone will call the Xpressions callback Access Number. User can provision either DID number of fully defined Private number.

–

WebCDC will write this Xpressions callback Access Number automatic in the DLS miscellaneous Template (CDC_Template_<sitename>_misc.xml).

–

Note: This number is used by UC for VoiceMail

•

Xpressions Transfer Access Number - User can provision either DID number of fully defined Private number.

•

Xpressions Trusted Transfer Mode Number - An optional parameter. WebCDC uses this value to populate the “RemTrustedDomainCallNumber” inside the CDC_XprConfigFile.xml script.

–

User can provision either DID number of fully defined Private number.

–

When empty for a (non-HQ) site, then the XPR call numbers of the HQ are used.

•

Media Server Conference Number - This is the dial-in number when the Media Server is used as conference bridge.

•

External Media Server Video Conference Number - This is the dial-in number of the External Media Server used for Video Conferences.

•

Operator Extension - This is a central operator that is connected when an option “0” is chosen in the Auto Attendant menu. Note: there needs to be an entry on the Subscriber tab for this extension.

•

Auto Attendant Public Number - The external number used to call the auto attendant.

•

Must Answer Number - The Must Answer Position (MAP) is an optional number, but if fulled in then it has to be an existing subscriber number (either a fully qualified public number or fully qualified private number). Usually the MAP is a subscriber that has a high availability like a reception desk or security.

•

Site Subnets - Subnet of the site, e.g. 10.235.100.0/24.

•

Use Local Toll Tables - Only applicable for the US.

–

“yes” -the local toll tables will be used to expand the destination codes for the local calling.

–

“no” - only national calling will be used towards the PSTN

–

If left blank, then default is “no” which means that only national calling will be used towards the PSTN.

NOTE: Additional information on LTT is available in the Solution Concept - Dial Plan Implementation with WebCDC Tool document.

•

Pbx migration routing - This setting is only applicable in Pbx Migration case when some subscribers have been migrated from existing PBX to OSV. This setting defines how the call to subscribers on PBX will be routed when called from another branch.

•

Do Carrier Codes need to be dialed? - This setting applies only for sites of countries where carrier code dialing is supported (e.g. Brazil).

–

When setting this field to Yes, the user needs to dial a carrier code to dial out to the PSTN. This carrier code is not remembered and will not be used on the outbound route. This should be used when users are frequently making mistakes when they have to dial carrier codes at home and then not have to dial them when at work.

–

When setting this field to No (default setting if left empty), the user does not need to dial a carrier code to dial out to the PSTN.

–

In any case the dialed carrier code is ignored and replaced with the presubscribed long distance carrier code entered on the Endpoints data tab, between the international or national prefix and the international or national number from the Endpoints data tab.

•

Default First Speed Dial List - Primary Speed Dial list for the site

•

Default Second Speed Dial List - Secondary Speed Dial list for the site

OpenScape Solution Set V10, Customer Data Collection with WebCDC V1, Planning Guide, Issue 2, ID: A31003-S11A0-P100-2-76A9

© 07/2024 Mitel Networks Corporation. - All rights reserved.
Mitel and the Mitel logo are trademarks of Mitel Networks Corporation. Unify and associated marks are trademarks of Unify Software and Solutions GmbH&Co. KG. All other trademarks herein are the property of their respective owners.