We currently have 2 PRIs, with 2 separate trunks, one is allocated for Our Customers (Incoming Call Handling Only) (For reference T-#1) and one for employees (with DIDs) (T-#2).
Starting on the first of this year, one of our “800” numbers started giving a busy signal (all others working fine). However, when I placed a call to the hard number is worked fine; for example, I dialed the 10 digit line that is “Behind” the 800 number it lands on T#2 instead of T#1.
I figured AT&T got some routing jacked up during some year-end maintenance or cleanup. The AT&T tech said the routing looks find on their end and that the “800” number is trying to route to the T-1 and is not being accepted. Since I have other 800 numbers up and running on the same truck & card, it seems odd to me that AT&T is blaming my PBX and the DNIS number (which has been confirmed in the Incoming Call Handing Field).
I’m kind of brain dumping right now, so I’m sure you’ll have questions.
The bottom line is, both trunks are showing all ports up and running. I have tested both cards and they passed all tests. All other 800 numbers are routing properly across T#1, yet only one is getting a busy. The have temporarily placed the malfunctioning 800 number on “Service Assurance” and are routing it to the DID on T-2.
I’ve never really had to work much at mapping 800 numbers. All I’ve done in the past is entered a DID or DNIS number in the call handling area of the trunk and it worked. Am I missing something or is the tester at AT&T jacked up?
Starting on the first of this year, one of our “800” numbers started giving a busy signal (all others working fine). However, when I placed a call to the hard number is worked fine; for example, I dialed the 10 digit line that is “Behind” the 800 number it lands on T#2 instead of T#1.
I figured AT&T got some routing jacked up during some year-end maintenance or cleanup. The AT&T tech said the routing looks find on their end and that the “800” number is trying to route to the T-1 and is not being accepted. Since I have other 800 numbers up and running on the same truck & card, it seems odd to me that AT&T is blaming my PBX and the DNIS number (which has been confirmed in the Incoming Call Handing Field).
I’m kind of brain dumping right now, so I’m sure you’ll have questions.
The bottom line is, both trunks are showing all ports up and running. I have tested both cards and they passed all tests. All other 800 numbers are routing properly across T#1, yet only one is getting a busy. The have temporarily placed the malfunctioning 800 number on “Service Assurance” and are routing it to the DID on T-2.
I’ve never really had to work much at mapping 800 numbers. All I’ve done in the past is entered a DID or DNIS number in the call handling area of the trunk and it worked. Am I missing something or is the tester at AT&T jacked up?