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!

DID in one office pointing to different office

Status
Not open for further replies.

coniglio

Technical User
Jun 17, 2003
1,886
US
I need to set up a DID in my NJ office that, when dialed by our clients, routs to my White Plains office. I just built a DMI table to convert one DID (which conflicts with SPRE code) to an unused DN. I then build that DN as an ACD queue and NCFW'd it to 91914-xxx-yyyy. When I call the NJ DID I am getting NJ receptionist, not White Plains. I am guessing there's some type of restriction blocking this call from going out. I don't want to start unrestricting a whole lot of stuff, plus I really don't know how to anyway. what is the safest way to set this up? thank you.
 
FIRST MAKE SURE YOUR DID TRUNKS HAVE A NCOS THAT CAN CALL LD, THEN IN THE CDB THERE IS A OPTION FOR TRUNK TO TRUNK

OLD ROLMEN WORKING ON NORTELS
 
an option for trunk to trunk what? what am I looking for? and if I change the trunk NCOS to call long distance, will i be opening myself up to the possibility of lots of fraud?
 
try to create a phantom DN and then FTR DCFW x yyyyy on it.
yyyyy will be a White Plains office number.
Trunk to trunk connection option have to enabled in LD 15 NET_DATA.
 
you mean build it as a 500 port? why not as an ACD queue that NCFWs to white plains #? which didn't work, by the way, cause I got the NJ attendant, so that's what made me think something in the trunks is restricting call. But i still don't have the answer regarding unrestricting trunks. WILL I BE SETTING MYSELF UP FOR MAJOR TOLL FRAUD?
 
if you have r25.40 try to enable Plugin 27 "DID to DID calls intercept to ATT"
 
i haven't the first idea what plugin 27 is. And the switch that the number is going to be in is NOT 25.40. The switch where it's going to point IS 25.40. Any other suggestions? I am still trying to find out about trunk to trunk transfer and toll fraud.
 
if I allow trunk-to-trunk transfer and whatever else has been suggested in order to make this one New Jersey DID telephone actually ring in my White Plains office, will I be setting my PBX up for the possibility of toll fraud? i really need to know. Thank you.
 
tcom,

To prevent toll-fraud, instead of opening up your LD trunks with a higher NCOS, I would break out your phone number in BARS.

Right now, your LD trunks have what NCOS?

In Load 90, 1914 point to an RLI which has what FRL?

I would out 1914 in LD 90...Then break it down to only allow the 1914 XXX XXXX out via and RLI with a low enough FRL to allow it out your LD trunks and not get blocked by the NCOS of the trunks.

This way you only have one specific phone number that is "opened up"

Fonchick
 
i can do that with ARRN i think. i did that for another number in new york. It's much much easier than breaking down the entire SPN. I just didn't want to do it that way because the number I'd be allowing is the white plains office number. But do I still need to worry about trunk-to-trunk transfer? because the call will NOT be originating FROM my New Jersey office. It will be dialed from OUTSIDE the firm to a DID on my NEW JERSEY circuit, which then hopefully will go BACK OUT to WHITE PLAINS. So I'm not even sure now if the whole SPN breakdown will even help. I appreciate your advice. Thank you.
 
pls ask your tech support for patch
I'm working in europe, and against this (DID to DID connection on EUROISDN ) we have a patch
 
Do you have CDP package? if so you should be able to use a DSC (DISTANT STERRING CODE) to route the call,
1)set up a DMI in LD 86 TO DELETE THE DSC (DID EXT)and insert nunber to dial
2)SETUP A NEW RLI using the outgoing trunk route
BE SURE THAT THE NCOS OF THE INCOMING TRUNK CAN ACCESS IT
3)PROGRAM THE DID EXT AS A DSC IN LD 87 AND POINT TO THE NEW RLI.
REFER TO COORDINATED DIALING IN NTP'S

NORTIC

 
you just mentioned "be sure NCOS of incoming trunk can access it" and that is the whole point. I know how to do CDP, phantom 500 port, ACD, etc. It's the changing of the NCOS on the trunk that concerns me. I don't want to do ANYTHING that can even POSSIBLY allow someone to hack into my PBX and call Kuala Lumpur.
 
you just need to match the incoming route NCOS to the RLI'S FRL PROMPT

NORTIC
 
so leave the incoming route's NCOS as is and just create a new RLI with the White Plains DID broken down as an AARN and have the FRL on that route equal the NCOS (yes, the NCOSs equal the FRLs)? no toll fraud?
 
TCOM,

I DON'T KNOW EVERY DETAIL AT YOUR SITE, BUT IT WORKS FOR ME,

YOU'LL HAVE TO TEST FOR TOLL FRAUD YOURSELF

EACH SITE CAN HAVE TO MANY VARIBLES FOR ME TO SAY YOU WON'T HAVE TROUBLE.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top