Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

QSIG to old school DCS tandem not working

Status
Not open for further replies.

1Jumbo

Technical User
Sep 30, 2004
125
US
Here is the scenario. The customer has a CM 12.1.1 at the MAIN location and a DEFINITY 4.8.0 at FACTORY site. They are connected with old school DCS on a T1 (not PRI). Calls work great both directions.

The customer added a new location with a Shoretel system. The connection between Shoretel and MAIN is QSIG. Calls from Shoretel to MAIN work great and vice versa. However, calls between Shoretel and FACTORY fail in both directions. MAIN should be acting like a tandem switch but it does not work.

If I make a test call from Shoretel to MAIN I see the system send 4 digit extensions on a list trace and the call goes through. If I test across the MAIN-FACTORY link, I see the 4 digit call go through on the DCS trunk group as well.

If I list trace either the Shoretel-MAIN trunk group or the MAIN-FACTORY trunk group while dialing from Shoretel to FACTORY, the system sends 4 digits and immediately disconnects. I am not seeing an error code.

The phones at FACTORY are UDP extensions in the MAIN switch using AAR to get routed.

I believe I'm missing some programming to make the call tandem through. I have played with the tandem routing table, route patterns, etc.

As a test, I made a small vector in the MAIN switch to collect 4 digits and route to the number. If I call that vector's VDN from Shoretel and insert the digits for an extension at FACTORY, the call goes through so I assume it is not a trunk-to-trunk issue.

Any ideas or suggestions?
 
Have the Shoretel extensions been added to the Factory UDP table? Usually with DCS, you use AAR to insert a prefix code that gets deleted in the Route Pattern.

Kevin
 
I had been so concerned getting calls to go one way that we hadn't really worked on that switch. I added it and we have been able to make calls one way (Shoretel to Factory). Now we have to wait until tomorrow to test the other direction.

Thanks! Looking good for now. Solution: All UDP tables have to be completed with all affected stations.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top