DID ranges, circuit ID of the provider your porting from and carrier name. If these numbers are pots lines than skip the circuit ID, just provide the number and carrier.
All of this should be handled by your the carrier you are moving to but some do better than others so make sure you do constant checks with them.
If you are connecting two switches, either go with a tie trunk or IP trunk. Is it going to a Siemens to Cisco or are you replacing the Siemens with a Cisco? If you have to use ISDN, you will have to setup four or five digit dialing and utilize AAR. Then add the area code and prefix in the route pattern...on both sides.
The basic idea is to install working IP station next to the old Siemens stations. Once we know the IP stuff works then we will want to port the old Siemens station phone number over to the IP phone. Then we can remove the Siemens station.
Since you are porting your numbers, this indicates you are changing service providers for your CISCO IP system. Make the new service provider handle the porting. That is their job. Tell them what you need and make them do it.
Once all the DID ext and created either on user phones or on AA/ICD/CRA all you will need to do is move the existing PRI into a gateway that points all inbound Dial peers to CCM.
It really is that simple if you are in a DID env... The hard part is not porting the PRI but making sure every needed DID number is created and implemted properly on the new system.
If you are not changing geographic locations. NO NEED to port your PRI. If you do.. YOUR provider will handle this for you. But you can handle this as a circuit move. Much simpler on there end and less room for mistakes.
I know what you mean ccmuser but the existing telephone service at this site includes a standard T1 to the Siemens and many direct station POTS lines. The new system (VoIP) will utilize a PRI service with a completely new and larger numbering range. We plan to port only the existing (old) main or published numbers over to the new VoIP stations. This will keep the old published numbers working at the same physical locations plus upgrade and increase the size of the local telphone system services all in one shot.
That makes sense.. What I would do is work this project in two steps.. have them expand you did numbering range on the current circuit. test and make sure all importand new DID Dn's are there.. Then Take it and move into CCM. You just have less to troubleshoot at one time this way. May seem like a waste but for us it worked out very well. We removed about 15 G3(everyone please refrain comments) for CCm and pretty much found that to be the best procedure.
Good luck on the project. Sounds like either way you do it you should be fine...
I like your idea, but this(very)old Siemens system is maxed out in every way. Preparing this system or expanding it to accomodate the new services might not be cost or time efficient. What do you think?
I am not saying implement the new services you want to offer on old PBX just the new Did ranges coming from verizon and make sure the circuit is the way you want.. with the old system in place you basically have the ability to test that for free. Once the DID range and number forwarding is too you specs you can just move PRI into new system. Are they both t1 PRI? or is one using CAS or something like that? That may change my approach.
What this does if your building does not have 24 hr calling window is let you schedule down time a few nights before the move and allow you to test AA or ICD features with actuall gateway and PRI before you actually schedule your Live cutover.
The old switch uses a single standard T1 and the facility (a Hospital 24/7)also has many direct to station POTS lines that bypass the old switch. The new Call Manager will use PRI. Everthing including the POTS will have to change over to this PRI. I appreciate your feedback, this helps. Thanks.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.