1 Accepted Solution
Accepted Solutions
When migrating from NEC PBX to Cisco Unified Communications Manager (CUCM), you’ll need to gather several key pieces of information to ensure a successful transition. Here are the few details:
- NEC PBX Configuration:
- Trunk Types: Identify the types of trunks (e.g., E1, T1, SIP) used for external connectivity.
- Dial Plans: Understand the dial plan, numbering schemes, and call routing rules in the NEC system.
- Feature Codes: Note any feature codes (e.g., voicemail access, call forwarding) used by users.
- NEC PBX Hardware and Interfaces:
- Gather information about the hardware components, such as the PBX model, interface cards, and available ports.
- Identify the interfaces (E1/T1, analog, SIP) connecting the NEC PBX to the outside world (PSTN or other networks).
- User Extensions and Voicemail:
- Document user extensions (internal numbers) and associated features (e.g., voicemail, call forwarding).
- Understand how voicemail is handled (built-in or external system).
- Call Routing Patterns:
- Analyze call routing patterns within the NEC PBX, including local, long-distance, and international calls.
- Note any special routing rules or translations.
- Voice Gateways (VGs):
- If using Cisco VGs, gather details about the VGs (e.g., model, interfaces, protocols).
- Network Topology:
- Map the network topology, including IP addresses, subnets, and gateways.
- Identify any firewalls, routers, or other network devices involved in call routing.
- CUCM Configuration:
- Prepare the CUCM environment:
- Server Details: Know the CUCM server names, IP addresses, and versions.
- Device Pools: Set up device pools for phones and gateways.
- Route Patterns: Create route patterns to match the NEC dial plan.
- Trunk Configuration: Configure required trunks.
- User Configuration: Configure users and devices to match the NEC configurations.
- NEC and CUCM SIP Trunk:
- Plan for migrating users: Move users batch by batch
When migrating from NEC PBX to Cisco Unified Communications Manager (CUCM), you’ll need to gather several key pieces of information to ensure a successful transition. Here are the few details:
- NEC PBX Configuration:
- Trunk Types: Identify the types of trunks (e.g., E1, T1, SIP) used for external connectivity.
- Dial Plans: Understand the dial plan, numbering schemes, and call routing rules in the NEC system.
- Feature Codes: Note any feature codes (e.g., voicemail access, call forwarding) used by users.
- NEC PBX Hardware and Interfaces:
- Gather information about the hardware components, such as the PBX model, interface cards, and available ports.
- Identify the interfaces (E1/T1, analog, SIP) connecting the NEC PBX to the outside world (PSTN or other networks).
- User Extensions and Voicemail:
- Document user extensions (internal numbers) and associated features (e.g., voicemail, call forwarding).
- Understand how voicemail is handled (built-in or external system).
- Call Routing Patterns:
- Analyze call routing patterns within the NEC PBX, including local, long-distance, and international calls.
- Note any special routing rules or translations.
- Voice Gateways (VGs):
- If using Cisco VGs, gather details about the VGs (e.g., model, interfaces, protocols).
- Network Topology:
- Map the network topology, including IP addresses, subnets, and gateways.
- Identify any firewalls, routers, or other network devices involved in call routing.
- CUCM Configuration:
- Prepare the CUCM environment:
- Server Details: Know the CUCM server names, IP addresses, and versions.
- Device Pools: Set up device pools for phones and gateways.
- Route Patterns: Create route patterns to match the NEC dial plan.
- Trunk Configuration: Configure required trunks.
- User Configuration: Configure users and devices to match the NEC configurations.
- NEC and CUCM SIP Trunk:
- Plan for migrating users: Move users batch by batch
