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!

conflict timer

Status
Not open for further replies.

jazwinner

Technical User
Feb 20, 2007
70
US
Is the conflict timer effective at resolving trunk access (ars) "9" versus 4 digit DID stations (DNs) 9XXX?
 
We need a little more information. What type of trunks are you using? There are a number of timers to use to assure that the circuit is indeed idle before attempting additional calls.

NO GOOD DEED GOES UNPUNISHED!
 
Depends on what you mean by effective.

Does it work - Yes

Do users like waiting 3-5 seconds before the 9XXX extension rings - NO!



*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.
 
BWT via PRI, inbound are DID or DNIS (4-digit). Bulk of DN range is 7xxx, but there are also 9xxx (POTS <fax lines> that were ported). AS of now the Trunk Service incoming digit mod strips 1st digit and inserts a '7'; the 7xxx route to matching 7xxx DNs on stations, the 9xxx route to other 7xxx ONS ports. Outbound first dig is '9'. It's no big deal, but the site is quite remote, and the digit translation is confusing to the users/admin folks. They would like all station DNs to match incoming dialed digits.
 
Have you thought about changing the ARS access digit from "9" to "8"?

**************************************
Insert Witty Signature Here.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top