Cisco.IP.Telephony.Planning.Design.Implementation.Operation.and.Optimization [Electronic resources] نسخه متنی

اینجــــا یک کتابخانه دیجیتالی است

با بیش از 100000 منبع الکترونیکی رایگان به زبان فارسی ، عربی و انگلیسی

Cisco.IP.Telephony.Planning.Design.Implementation.Operation.and.Optimization [Electronic resources] - نسخه متنی

Tebyan

| نمايش فراداده ، افزودن یک نقد و بررسی
افزودن به کتابخانه شخصی
ارسال به دوستان
جستجو در متن کتاب
بیشتر
تنظیمات قلم

فونت

اندازه قلم

+ - پیش فرض

حالت نمایش

روز نیمروز شب
جستجو در لغت نامه
بیشتر
لیست موضوعات
توضیحات
افزودن یادداشت جدید







Call-Routing and Dial Plan Requirements


Gathering call-routing and dial plan requirements is an important step in the IPT design phase. The requirements collected here dictate how to plan for route patterns, partitions, route groups, and route list designs in CallManager.

The first step is to gather the information on the existing numbering plan, as shown in Tables E-8 through E-10. If you have collected this information earlier, you can use that information; otherwise, gather this information before starting the dial plan design on the CallManager.

Table E-8. Existing Numbering Plan

Site Name

On-Net Site Access Code

No. of Digits in Station Numbering Plan

DID Ranges

Station Directory Numbering Ranges

Telephony Feature Pilot Numbers

Site-Level DID

No. of CoRs Required

Table E-9. Dial Plan Requirements

No.

Question

Answer

1

Are there any conflicts with current legacy numbering ranges? If yes, identify them and work on the dial plan to resolve them.

Yes

No

2

Do you have any conflicts of dialing plans with other locations?

When you are migrating from a distributed PBX or key system (A key system is a multiline phone system with basic features such as conferencing, transfer, or intercom. You can think of the key system as a scaled down version of the PBX system.) deployment to a centralized IPT deployment, you need to identify how many digits are used in each site for local dialing. If there is a conflict in the numbering plans between the sites, you should consider increasing the number of digits required to avoid the overlapped numbering ranges.

Yes

No

3

Do you want to retain the existing dialing behavior?

Yes

No

4

Is digit translation needed? (Example: Prefix digits, discard digits, append digits, changing the calling party/called party number and so on.)

Yes

No

Specify:

5

Do you have a toll-free number requirement?

Yes

No

Specify:

Table E-10. Call-Routing Requirements for Site 1

No.

Type of Calls

Call-Routing Preferences, in Order of Priority

1

Local

    Local gateway

    Central site gateway via IP WAN

Emergency

Local gateways only

Long distance

    Local gateway

    Central site gateway via IP WAN

International

    Central site gateway via IP WAN

    Local gateway

    Remote site 2 gateways

Toll bypass

    Central site gateway via IP WAN

    Site 2 gateways

    Local gateway

To international offices

    Central site gateway via IP WAN

    Local gateway


Notes/Comments


List the DID requirements. DID is a PBX or Centrex feature that permits outside calls to be placed directly to a station line without use of an operator.


/ 130