لطفا منتظر باشید ...
Legacy PBX Integration Requirements
If integration of CallManager with a legacy PBX system is a requirement, obtain the information detailed in Table E-4. Table E-4 shows some sample data that will help you to understand the type of information that needs to be gathered.
| Site Name | PBX Type/Software version | IPT TransformationIntegration/Full Migration? | IPT Users/PBX Users | Integration Trunk Type/Number of Trunks | Type of Gateway Required from Cisco/Software Version for Integration |
|---|---|---|---|---|---|
| Detroit | Definity | Integration | 200 (IPT)/100 (PBX) | T1-PRI/1 | WS-X-6608-T1/PCG00000 |
| New York | Siemens | Full Migration | 300 (IPT)/0 (PBX) | Not Applicable | Not Applicable |
Notes/Comments
You can use the information collected from Table C-1 in Appendix C, "IPT Planning Phase: Telecom Infrastructure Analysis Questionnaire," to fill out part of Table E-4. After you have the PBX details for each site, you can decide on the voice gateway model and the appropriate software version required on the voice gateway for successful integration. In case of integration with an IPT system, the existing trunks currently terminating on the PBX will be divided between the PBX and the voice gateway according to the user split ratio to preserve busy hour call attempts (BHCA).For example, in Table E-4, for the Detroit site, the Definity PBX system needs to be integrated with the IPT system. Out of 300 users, 200 users will be migrated to the IPT system, and 100 users will be retained on the PBX system. Currently, the PBX has three T1-PRI trunks interfacing the PSTN. To preserve BHCA, during integration, two trunks will be moved to the voice gateway interfacing the PSTN.You need to determine the approximate call volume between the users on the IPT system and the users remaining on the PBX system. This information is useful to size the trunks required between the PBX system and the voice gateway. The sample Detroit site information provided in Table E-4 uses one PRI trunk.
