I'm connecting 3 each 2k systems via msdn, clustered, everything is fine. We've placed a pair of 3300LXs between two of the 2ks, msdn into the 3300s and IP (xnet) between the 3300s. When I busy the main route (P2P msdn) to force traffic over the 3300s, the calling party sees "invalid digits" on the display and hears a fast busy. I'm sure it's something right in front of me - any suggestions? Thanks in advance!
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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Tandem Configuration 2k-3300
- Thread starter jazwinner
- Start date
- Thread starter
- #2
Sounds like an ARS problem, possibly in the ARS Digits Dialed or Digit Modification forms? If you have access to MOL, there's a "Technican's Toolbox" page in the Technical Support section, I believe there's a nice worksheet there that's helpful for visualizing ARS programming and finding hidden gems like you have.
I don't know what the official line is on the Route Op Network ID, but I've always set it up to match the CEID of the node. Also, beware, Route Op doesn't work very well over IP trunks, you may want to disable it altogether on the 3300's.
I don't know what the official line is on the Route Op Network ID, but I've always set it up to match the CEID of the node. Also, beware, Route Op doesn't work very well over IP trunks, you may want to disable it altogether on the 3300's.
is this xnet or ip trunking? Check your imat to ensure you allow data calls for the pri connectivity. You also could have programming issues if tdm xnet was used.
Also, the network id has no bearring on what you are doing here. The recommendation is to use your local cluster element digits, since all other controllers or 2ks would have ars for them. It is only really used for route optimization between controllers or 2k's.
Also, the network id has no bearring on what you are doing here. The recommendation is to use your local cluster element digits, since all other controllers or 2ks would have ars for them. It is only really used for route optimization between controllers or 2k's.
- Thread starter
- #6
Good info all, thank you. This is part of a 'clean-up' effort post ent-man upgrade (routing was done via rats-nest ARS prior to clustering). The 3300s are only used as gateway / failover route over fiber between a trio of 2000s (primary route is DS1 p2p). Volbackup, you indicate that an issue could present itself if tdm xnet is used. Can you elaborate? Final effort will be to migrate old consoles from 2ks (700s) to 5550s on the 3300s, so route op is of considerable importance. Thanks in advance.
- Status