|
Joined: Oct 2005
Posts: 52
Member
|
Member
Joined: Oct 2005
Posts: 52 |
We have implemented a new VOIP solution to one of our new buildings. The users were previously on our Toshiba system CIX670 with 56xx extensions. We have connected our new system via a SIP trunk and gave the users on the new system 56xx extension. Then went back and removed the DIDs and Extensions off of the Toshiba system.
We are looking for a way to get people to just dial 56xx and it would still ring on the new system. In order to do this currently, we would have to dial a 6 first to pickup a OLG setup for SIP. If we try to doing from another building that has a CIX670 as well, they have to dial the Network ID, then 6, then the extension.
I tried adding a 56xx as a Exception, but it gets to dialing 56, then the next number hit, it goes busy.
Is there anyway to trick the system out to automatically put the information in and the user can still dial the 4 digit extension? Someone suggested putting a speed dial button on the phone and make it a 2 step process.
I was going to create a LCR and with 56xx analyzed digits, then have it go out a specific route group. I was going to setup 5, as a number to access our LCR, but the system will not let us create a that.
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Feb 2007
Posts: 1,314
Member
|
Member
Joined: Feb 2007
Posts: 1,314 |
You cannot set up 5 as LCR access because your ext's on the Toshiba start with 5. How about setting up pilot DN's, set up 56xx for the pilot and set dialing digits to 656xx. You would have to create one for each remote ext though.
|
|
|
|
Joined: Oct 2005
Posts: 52
Member
|
Member
Joined: Oct 2005
Posts: 52 |
Is there a limit to how many Pilot DNs you can have and can you import those like you can with DIDs and regular extensions?
|
|
|
|
Joined: Dec 2006
Posts: 810
Member
|
Member
Joined: Dec 2006
Posts: 810 |
You might be able to setup another node id in ctx and make that node id access the sip olg. Then you can create network dn's on the new node. I've done this with a CIX connected to an NEC NEAX 2000 over a T-1 tie line. I don't see why it wouldn't work with a SIP trunk as well but can't say for sure. It's worth a shot.
Pat Austin Teleco Inc. Product Manager/Sales Engineer Adtran ATSP TCTE/CTP Certified Teleco Homepage
|
|
|
|
Joined: Oct 2005
Posts: 52
Member
|
Member
Joined: Oct 2005
Posts: 52 |
After looking through the manual, it looks like there is a limit to the amount of Pilot DNs you have. With a CIX670 Basic it is 100, and on the CIX670 expanded it is 256.
With Network DNs, it looks like you can have up to 3000 with the CIX670.
I was able to get the Pilot DN up and running quickly. I didn't have the time to create another Node ID and try it that way.
|
|
|
|
Joined: Oct 2005
Posts: 52
Member
|
Member
Joined: Oct 2005
Posts: 52 |
We have two building tied together with Toshiba CIX670's and a new building on a Cisco VOIP.
Site A with the MIPU Card for SIP... If I dial 6, to pickup the sip line, then the extension on the cisco side it works. If I add a Pilot DN and have it point to 656xx it does not work. I tried creating a new Node ID, but that didn't seem to be working. If I set it up right.
What I did, was going to the site A, and add a flex access code to pick up the node id. Then went to Node ID under StrataNet and added that second number in. Create a Route Plan Analysis, then added and test a bunch of Insert Leading digit combinations. No Luck.
------------ One way that I could get to work, but not sure how much bottle necking is going on is.... Create a Piliot DN on a remote site and add leading digits like you would manually dial, then at the other building add a network dn to point to that node id of the pilot dn.
So that call flow would go from Building A with the MIPU card, to building B, then back to A, then through the internet or how ever it gets routed.
|
|
|
|
Joined: Feb 2007
Posts: 1,314
Member
|
Member
Joined: Feb 2007
Posts: 1,314 |
I know this is probably a question that is too complicated to answer specifically but Im curious as to why you would go with the two platforms and not just stick with either all Toshiba or all Cisco? It sounds like you have a decent data pipe from one building to another and Im certain it would be easier to implement just one system throughout than to try tie two different systems together.
|
|
|
|
Joined: Oct 2005
Posts: 52
Member
|
Member
Joined: Oct 2005
Posts: 52 |
We originally had 4 buildings that have been around for awhile. Two of the main buildings had the CIX670 and the two smaller ones had the CIX100. We recently purchased a new building and moved bodies around and decided to implement a Cisco VOIP solutions because of all the features that it can offer.
Our long term goal is to migrate to all Cisco, but they are $$$$.
You are right though about try to integrate two separate systems. I have done a lot with the small business sized Nortel CICS systems and am picking up on the Toshiba system for my new job.
|
|
|
|
Joined: Sep 2004
Posts: 2,017
Former Moderator-Toshiba, Request an Installer
|
Former Moderator-Toshiba, Request an Installer
Joined: Sep 2004
Posts: 2,017 |
Get another CIX100 for the new building and tie them all together with StrataNet. What are the Cisco features of which you speak?
|
|
|
|
Joined: Jul 2006
Posts: 728
Member
|
Member
Joined: Jul 2006
Posts: 728 |
Originally posted by blkphtm: decided to implement a Cisco VOIP solutions because of all the features that it can offer.
Funny thing is the Cisco cannot do anything any better than the Toshiba or any other PBX system out there... Cisco is over rated in the PBX business. Don't get me wrong, they have gotten better but I even have IP systems that wipe the floor with Cisco for half the price.
|
|
|
Forums84
Topics94,490
Posts639,855
Members49,833
|
Most Online5,661 May 23rd, 2018
|
|
|
|