|
Joined: May 2015
Posts: 4
Member
|
Member
Joined: May 2015
Posts: 4 |
My company recently upgraded the amount of trunk lines for our Strata CTX 670 system. The phone company threw in a block of DID numbers with the upgrade. I have programmed a separate block of DID numbers into the system using eManager in the past and did not run into any issues. But when I try programming this block the same way, it only works for the first number in the block. Every other number simply goes to the same destination as the first number in the block. Any ideas on what is going on here? Thanks, Bill
|
|
|
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: Jun 2010
Posts: 32
Member
|
Member
Joined: Jun 2010
Posts: 32 |
What kind of circuit do you have coming into the system? Analog DID, T1, PRI?
Did you add them all at the same time? IF so, you need to manually reroute each phone number to the destination.
TRUCK>DID>select your ILG>LIST
click on a DID and insert the DAY1, DAY2, and NIGHT destination
submit.
|
|
|
|
Joined: May 2015
Posts: 4
Member
|
Member
Joined: May 2015
Posts: 4 |
Hi ballsie, thanks for the reply. Sorry I forgot to specify, it is ISDN PRI. Yes, I have manually rerouted each number to different destinations. Since the first number in the block (7600) can be successfully rerouted to any extension I choose, I know that they are using the correct ILG. What I can't figure out is why the second, third, fourth (7601, 7602, etc) numbers also go to the first destination. So if I tell 7600 to go to extension 1234, then 7601-7699 all go to 1234 as well. If I change the destination of 7600 to go to ext. 1111, then 7601-7699 all route to ext 1111, even though all I changed was the DAY1, DAY2, and NIGHT destination of 7600. I can change the destination on any given number in the first block of DID's that was given to us no problem; I have successfully rerouted multiple numbers in that block. With this particular block of DID's however, it all goes to whatever destination you set for the first number... this one definitely has me stumped!
Last edited by BillyJames; 05/25/15 01:12 AM.
|
|
|
|
Joined: Mar 2010
Posts: 228
Member
|
Member
Joined: Mar 2010
Posts: 228 |
Sounds like all of the DID's are presenting the same number to the CIX. Have you contacted the provider to make sure things are good on their end?
Jason
Toshiba/Avaya/Nortel Installations and Service.
Honeywell-Paradox-Kantech-Keyscan-HIKvision Access control and CCTV
|
|
|
|
Joined: May 2015
Posts: 4
Member
|
Member
Joined: May 2015
Posts: 4 |
Hi Jason, I have contacted the provider and they have given me this info: "messages being passed include a “From” field, a “Caller-ID” field and a “Called-ID” field. The “From” shows 7600 as the entire block is under that account, but the “called-id” field should show the correct number dialed. Is it possible to have the PBX look at the “called-id” field instead?" As far as I know, it is not possible through Strata Network eManager to tell the CIX to look at a different field... does anyone know of a way to do this?
|
|
|
|
Joined: Feb 2005
Posts: 1,037
Member
|
Member
Joined: Feb 2005
Posts: 1,037 |
I'd get a hold of the provider and let them know the previous DID #'s work fine and are able to be assigned and THEY need to get the second block just added to be configured as the first group. Unless I'm reading this wrong the problem is all provider?
Possibly they were ordered incorrectly?
|
|
|
|
Joined: Jun 2003
Posts: 3,273 Likes: 1
Moderator-Toshiba
|
Moderator-Toshiba
Joined: Jun 2003
Posts: 3,273 Likes: 1 |
It sounds like they are sending you 7600 as the DID digits no matter what DID number the call is coming in on. For a definitive answer, hook up to the PRI card with a PPTC9 and you can see what DID digits they are sending you.
|
|
|
|
Joined: May 2015
Posts: 4
Member
|
Member
Joined: May 2015
Posts: 4 |
After much time spent sorting this out with the provider, they finally agreed that the problem was on their end and configured the block correctly. Problem solved! It now works as it should. Thanks for all the great feedback :-)
|
|
|
Forums84
Topics94,526
Posts640,015
Members49,852
|
Most Online5,661 May 23rd, 2018
|
|
|
|