|
Joined: Apr 2005
Posts: 51
Member
|
Member
Joined: Apr 2005
Posts: 51 |
Qwest says it's our Axxess System (ver 9) causing a fast busy when calling into our new LD T1 we just got installed.
The circuit works fine for outbound, so I presume the card is OK.
The tech from Qwest asks if we need it set for "Real Time ANI" and says it is either *DNIS or *DNIS*ANI - I have no clue which is needed or how to set it in our system.
I don't trust Qwest when they say it's our system, and how could our Inter-tel system throw a Fast Busy signal?
The tech also says it's hitting our trunk group setup in the system, but our Real-Time Reporter doesn't show a call coming in and how can they see the trunk in our system?
I got the trunk group setup to hit our call routing table for inbound calls and the tech gave me the DNIS the call is supposed to be coming in on, but it never gets that far - I don't think.
Any ideas or thoughts? I'm not all that familiar with T1 settings, so maybe it is something on my end. All help is truly appreciated.
Rx
|
|
|
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: Dec 2007
Posts: 115
Member
|
Member
Joined: Dec 2007
Posts: 115 |
it's done at the individual trunk screen, service type, we are running one that is DNIS...hope that helps. if your t1's don't match on everyting, signalling, framing, etc it will throw a busy-back out, it's offline.
|
|
|
|
Joined: May 2009
Posts: 1,198
Member
|
Member
Joined: May 2009
Posts: 1,198 |
It's a matter of matching your T1 settings with what the carrier is sending. Sometimes the hardest part is speaking the same language, so you can figure out what those settings are!
Since you mention ANI, let’s start there. Automatic Number Identification (ANI) is basically caller ID, the number that the call originates from. Dialed Number Identification Service (DNIS) is the number that the caller dialed, one of your numbers riding the T1. When combined, you can identify and route the inbound calls. The most common format is *ANI*DNIS*, so let’s go down that path.
Starting at the beginning, go to the T1 card under System/Cabinets. Assign each circuit as an E&M trunk. Double click on the trunk, and you’ll see more options. Start Type will most likely be Wink, check with your carrier to confirm. For service type, select *ANI*DNIS*. Under Number of Digits to Receive, enter the number of digits being sent by the carrier. This number should match the number of digits entered in your Call Routing Table.
In the Call Routing Table, make sure the last two entries are + and E. Label + as DNIS RANGE and E as NO DNIS. If the carrier presents calls with the wrong DNIS or no DNIS, this will help you identify the problem.
|
|
|
|
Joined: Apr 2005
Posts: 51
Member
|
Member
Joined: Apr 2005
Posts: 51 |
The Qwest tech called me this morning and confessed to not having the T1 set correctly to what I specified. She did the changes and it works perfectly now.
I figured that what it was, but I do appreciate the info and assistance.
Do we need to mark this day on the calendar? Telco actually admitted to have done something wrong AND corrected the mistake within 48 hours! Never thought I would experience such a thing.
Thanks all,
Rx
|
|
|
Forums84
Topics94,514
Posts639,943
Members49,846
|
Most Online5,661 May 23rd, 2018
|
|
1 members (R4+Z),
139
guests, and
31
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|